Start at the top with a strategy around spaces. Consider how your organization is structured; functionally, geographically, departmentally? Each team should have their own space in Wrike to work. At the next level are folders, which are used to organize the work of that team/department space. A solid foundation of folders might include "Admin", "Projects", "Requests", and "Archive". These folders house the projects and tasks the team is using to get work done. You can add tasks to any item in your account and tag these tasks with multiple folders, projects, and spaces so the same tasks are visible in all of them.

General guidelines:

• Brainstorm who needs to see what and create spaces based on that. Departments (and potentially teams) probably need their own spaces.
• Use prefixes or a numbering system when working with repeatable projects.
• Set account-wide guidelines for creating spaces and make sure each space has admins who understand their role.

The most important thing to remember is to iterate. Your company is unique and you should listen to your team and make changes based on what works for you. The course 302 Organize a Space will give you a detailed template for building out a space.

There are many correct perspectives on this. Subtasks live within tasks and are great for dividing tasks into smaller action items. When all subtasks are completed, Wrike will ask you to complete the parent tasks, so you will know that the work is finished.

If you find that you have tasks > subtask > subtask, you should probably reevaluate your structure and see if you can remove a layer - either by using projects, folders, or by creating checklists within a task.

You can separate, segment, and control what everyone sees and can do in Wrike. First, the type of user (licenses) controls what a user can do. Admins, regular users, external users, and collaborators all have different access to features. Next, check the sharing settings for the space/folder/project/task in question. If it is not shared with someone, they cannot see it. Finally, control what people see and do by using Access Roles. There are 4 default roles: Full, Editor, Limited, and Read Only.

*Admins on Enterprise account can customize existing roles and create additional roles with a new set of permissions.

Driving Wrike adoption is really about change management*.

• Identify a core group of Wrike champions who can help answer questions, decide strategy, and implement changes (i.e. switching to using Wrike).
• Understand reservations (why people don't want to use Wrike) and highlight value (tell people what Wrike will help with).
• Listen to your team - find out how Wrike can help departments and then show them how to achieve what they need.
• Use Wrike Discover - taking Discover courses help drive adoption, use it as a resource to help train your team.

*There's a lot out there about change management, apart from online resources, you can always ask questions in our Community.