Process Adoption: Why Tool Rollouts Stall

Last updated: November 4, 2026

A project management platform can be introduced, explained and made available without becoming part of how teams deliver work. According to Wrike, the obstacle is often not employee unwillingness but a setup that makes the platform harder to use than the tools people already know.

That distinction matters to project managers and team leads. A busy platform is not necessarily a useful one.

• Wrike says usage weakens when software introduces extra work without simplifying employees’ responsibilities.
• The company separates regular platform use from compliance with the process the organization has chosen.
• UK digital marketing agency Jellyfish paired a gradual rollout with workflow configuration and integration with its Salesforce/FinancialForce environment, now called Certinia.
• Wrike reports that automatic assignments, scheduled prompts and real-time dashboards helped Jellyfish reduce manual coordination, status meetings and approval delays.

Jellyfish moved beyond a feature tour

Wrike’s account of Jellyfish’s transition begins with a familiar problem. Before Wrike, the agency distributed work among task-tracking products, spreadsheets and email. As a result, staff could not easily determine the status of projects and spent more time reconciling information.

Sarah Wagner, Customer Success Director of Creative and Experience at Jellyfish, led the transition through a gradual rollout. The structure gave staff time to adjust and was intended to limit resistance rather than force an abrupt change.

The resulting implementation covered more than individual tasks. Teams now use Wrike for campaign planning, task distribution and approvals. The agency has also connected Wrike with its Salesforce/FinancialForce instance, now called Certinia, to keep information synchronized across the systems.

Automatic task distribution and prompts handle routine coordination. Real-time dashboards provide visibility into progress and resource allocation. Wrike says this setup has decreased the time employees devote to chasing updates, holding frequent status discussions and completing lengthy approval cycles.

The wider lesson is not that every agency needs this vendor or a similar setup. It is that employees are more likely to follow a process when the platform offers a clearer and more convenient path through it.

Access is not the same as adoption

Giving employees access and walking them through a product’s features do not guarantee that the platform will shape their daily work. When following the new system takes more effort than working in familiar applications, employees have a practical reason to step away from it.

That makes platform activity an incomplete success measure. Frequent use can coexist with poor process compliance: someone may sign in every day but still fail to provide information another team needs to continue.

The administrator then becomes a human processing layer. They chase incomplete submissions, prompt people to update their work and identify tasks that ought to move forward without manual intervention. The problem may not be resistance to change. It may be that the required behavior is cumbersome within the tool.

This is why more training is rarely a complete answer. Training explains what a platform can do, but it does not eliminate duplicated data entry, unclear responsibility or unnecessary handoffs.

Workflow design beats a longer reminder list

Begin with one recurring workflow that repeatedly draws administrative attention. Work with the employees performing the process to determine which details are missing, where responsibility becomes unclear and which decisions can be handled automatically.

Wrike says workflow requirements and routine prompts can be embedded in the system, reducing the need for someone to coordinate every stage. A request form, for example, can capture the information a receiving team needs and use it to create work, assign owners and trigger the next step.

Conditional questions can make forms more relevant. Someone requesting a landing page can answer questions suited to that asset without seeing prompts intended for unrelated deliverables. Keeping the form focused matters because unnecessary fields create another obstacle to submission.

The configuration should mirror the way employees have decided to operate, while preserving room for exceptions. A workflow with no flexibility can frustrate teams when every case is identical. One without clear boundaries can leave ambiguity everywhere. The objective is to clarify the normal route without making unusual but legitimate situations impossible.

Where a campaign request breaks down

Imagine a regional marketing manager seeking a landing page and a promotional email. The creative team handles production, a reviewer checks the assets and marketing operations publishes the campaign.

If the request arrives through email, it may leave out the target audience, launch date or brand materials. The creative team must then contact the requester for clarification before production can start. Information exists somewhere, but the handoff remains incomplete.

A focused Wrike request form can collect the necessary details at submission. Those answers can then populate the work, identify the responsible team and begin the agreed sequence. Wrike workflows can also place requirements and recurring prompts into reusable blueprints, so employees do not need to reconstruct the same coordination for every campaign.

This is an illustrative example, not a documented Jellyfish configuration. Teams should configure their own process around the work they have examined and tested. The important detail is where clarification becomes necessary: the goal is to resolve that gap before an administrator must intervene.

Decision checklist

Before expanding a rollout, project leaders should evaluate the workflow with the employees doing the work:

• Does the request ask only for information the receiving team needs to begin?
• Are responsibility, assignments and recurring requirements built into the process?
• Can employees complete routine handoffs without asking an administrator for direction?
• Are prompts limited to genuine exceptions rather than compensating for poor workflow design?
• Can managers understand progress and resource allocation without scheduling another status discussion?
• Has a small group tested the revised workflow, with reviewers checking incomplete submissions, manual coordination and delayed handoffs?

What to watch next

Adoption depends on the design of the work, not the quality of the launch presentation. Employees tend to remain in a platform when it helps them complete their responsibilities more easily and gives their teammates what they need.

Login counts alone will not show whether the system is functioning. Leaders should also examine whether necessary information is supplied once, work can pass between teams without repeated follow-up and progress can be understood without another meeting. Those are more revealing signs of operational adoption than raw platform activity.

There is also a trade-off between consistency and flexibility. A workflow built only around the standard sequence can drive employees back to informal channels whenever reality differs. A workflow with too few rules can leave teams with the administrative burden they intended to eliminate. The better approach is to identify a process that demonstrably needs improvement, test a focused change with the people who perform it and adjust based on what happens.

Key takeaways

• Measure process compliance and handoff quality, not platform activity alone.
• Configure the workflow before adding more reminders.
• Pilot changes with the people performing the handoffs.
• Use visible progress data to reduce status chasing and administrative recovery.
• Preserve deliberate flexibility where recurring processes cannot follow one identical path.