FAQs

FAQ

Discover the answers to some of the most frequently asked questions about the Wrike Deployment process.

How do you define “process”?

A process is defined as the actions taken to initiate, execute, and close out one project type (e.g. New Product Launch, Marketing campaign, Client engagement, etc.). The process can cross multiple teams and the focus, for the Deployment Team, is on the process, itself, and the team that owns that process, regardless of work styles and viewpoints across other teams which may be involved. 

Example statement: A situation wherein multiple teams collaborate to complete a series of projects or processes owned by those multiple teams, supporting a larger initiative is NOT 1 process. This would be considered multiple processes - individual outcomes executed by independent teams to support the larger initiative. An initiative might be considered achieved even if one of the individual outcomes is not completed.

Example statement: A situation wherein a clearly defined deliverable or outcome consists of multiple phases involving multiple teams but is completely owned and overseen by one team or department is considered a single process (e.g. development of a new product which involves development, marketing, enablement, sales, distribution, etc.). A deliverable cannot be considered complete unless all individual pieces are completed as well and the outcome is owned by a New Product Development team or PMO.

How many people should be on the Deployment Team?

It depends on the number of teams we will be deploying in Wrike. Ideally, we will be looking to have a champion and an SME (Subject Matter Expert) per each team and process that we are adding to Wrike. If we want to be more specific - appoint at least one Champion for every 5 users in your account.

How many sessions per week will there be? Can we have sessions every day?

We can move as fast as you like, however, it is important to mention that homework will be assigned to the Deployment Team after each session. If your team has time on their hands and can accomplish the homework quickly, your PSC will try to match your speed. We recommend a cadence of at least one session per week, though some weeks may need more than one session to meet the deployment deadline.

How long will it take to deploy Wrike?

This will depend on the time and resources available to you. The Statement of Work, as agreed upon by both parties, will define the delivery time frame. Standard deployments can take anywhere from 75 to 150 days while complex, custom deployments crossing multiple teams and processes across multiple geographies can take longer. Ultimately, the primary factor determining the duration of your deployment is the availability of your team for sessions with the PSC and time to complete the homework between sessions.

We don’t have time to build the workspace, can you do this for us?

We encourage our customers to actively participate in Wrike deployment, adoption, and rollout. Implementation of a Platform like Wrike involves a significant amount of change (depending on your organization’s previous experience with similar platforms and products). Change supported and led from within is usually change that sticks. Our goal is to support you and enable you throughout the way and your knowledge of the organization and existing processes are invaluable on this journey to successful Wrike adoption and implementation. Having said that, we understand that some teams simply don’t have the bandwidth to do the sessions and homework in a timely fashion. In those circumstances, we are happy to discuss a customized approach to your Wrike deployment.

We need to integrate Wrike into all our systems straight away, can we do this?

Our Solution Architects are ready and willing to discuss Wrike integrations. To the extent Wrike’s pre-built connectors do not meet the full need, they will facilitate a technical scoping discussion with your systems experts during which they will evaluate the level of effort required to achieve this task and provide a related estimate and Statement of Work (SOW). We generally recommend that the Wrike Workspace be configured and tested prior to building any integrations.

We need to transfer all the data from our current Work Management Platform, can you help us?

Wrike Solution Architects are happy to discuss your data migration requirements and provide an estimate of effort and cost along with an SOW for this type of work.