A project can have a clear plan, strong kickoff, defined owners, and realistic deadlines—and still lose momentum two weeks later.
The issue is not always the plan.
Sometimes the team understands what is changing but has not yet made the shift from:
“We agreed to do this.”
to:
“This is now how we work.”
That transition is the missing middle between planning and execution.
The work does not end at launch
Kickoffs are designed to create clarity.
They help teams understand:
- the purpose of the project
- the intended outcome
- who owns what
- what happens next
But understanding a new process and consistently using it are not the same thing.
After the kickoff meeting, people return to existing habits, urgent work, full calendars, and the tools they already know. Requests may still arrive through email. Decisions may continue in Slack. Updates may happen in meetings but never make it back into Asana.
The project is technically active, but the new way of working has not yet become routine.
This is especially easy to miss on remote teams.
In an office, someone may notice confusion, answer a quick question, or see that people are using the process differently than expected. Remotely, silence can look like alignment until a deadline arrives.
A project owner is not always an adoption owner
One of the most important distinctions I have been thinking about is that owning the project is not always the same as owning the change.
The project owner may be responsible for the outcome, timeline, and deliverables.
But someone also needs to pay attention to whether the team is:
- Completing work in the new workflow
- Returning to old habits
- Encountering unclear steps
- Working around the process
- Raising feedback early enough to act on it
Without that support, the workflow may exist in Asana while the real work continues somewhere else.
The system may not need more
I have experienced this in my own implementation work.
A workflow can make complete sense during planning and still struggle to become part of the team’s daily behavior. My instinct has sometimes been to add more detail, more structure, or more reminders.
But stalled adoption does not always mean the system needs more.
It may need a clearer bridge between launch and routine use.
For example, imagine a team launches a new cross-functional project tracker in Asana.
The kickoff goes well. Owners are assigned. Everyone agrees to update their work in the project.
Two weeks later, some tasks are current, others have no updates, and key decisions are still being made in Slack.
The answer may not be to rebuild the tracker.
It may be to clarify what belongs in Asana, simplify one or two fields, establish a regular status rhythm, and consistently bring side-channel decisions back into the project.
A four-part path from launch to adoption
I have been thinking about the missing middle through four stages:
1. Launch
Create shared understanding around the purpose, outcome, ownership, and first actions.
The first task should be clear enough that people know exactly how to begin.
2. Reinforce
Create lightweight touchpoints that bring the team back to the workflow.
That might include status updates, recurring review tasks, meeting agendas linked to the project, or clear reminders about where updates and decisions should live.
3. Learn
Pay attention to what actual use reveals.
Where are tasks stalling? Which fields are being ignored? What questions keep coming up? What work still happens in Slack, documents, or inboxes?
The goal is not to chase every small complaint. It is to identify patterns that affect adoption.
4. Normalize
Make the new process part of regular work.
This means consistently redirecting updates into Asana, closing the loop when feedback leads to a change, and reinforcing the workflow until it no longer feels new.
Support the change without over-managing it
Helping a project gain traction does not require constant meetings, repeated redesigns, or following up on every task individually.
Often, the better question is:
What is the smallest amount of support this team needs to keep moving?
That could be:
- A clearer first step
- One recurring status update
- A visible place for questions
- Fewer required fields
- A scheduled adoption check
- Consistent redirection away from side channels
- Acknowledgement when team feedback improves the process
The goal is not to manage every interaction.
It is to remove enough friction that the new way of working has a real chance to become the normal one.
A strong kickoff creates understanding.
Adoption requires reinforcement, feedback, and time.
Think about a project or workflow your team launched in Asana: where did momentum begin to fade, and what specific action helped—or could have helped—move the team from agreement into consistent use?