Reimagine: Momentum Is Not the Same as Motion
A lot of teams confuse motion with momentum.
Motion is activity. It looks like meetings, messages, task updates, status reports, comments, check-ins, and “just circling back” emails.
Momentum is different.
Momentum means the work is moving in a clear direction with enough ownership, visibility, and decision clarity to keep progressing without constant rescue.
That distinction matters because a team can be very active and still not be moving well. A decision can be discussed in three meetings and still not land. A task can have an owner and still have no visible next action. A stakeholder thread can be full of replies and still leave the team unclear on what actually changed.
That is where PMs often become the human reminder engine.
They remember what everyone else forgot. They chase the decision. They re-state the next step. They remind the owner. They reopen the thread. They translate the meeting into action.
There is real skill in that. Good PMs know how to create movement when work gets messy.
But the better question is not, “How do I chase this better?”
The better question is, “Why does this need to be chased every time?”
That is the modernize moment.
Because when the same follow-up keeps repeating, the issue may not be the individual. It may be that the system does not make the next move visible enough, owned enough, or easy enough to act on.
The old way is to chase harder.
The modern way is to build a system that makes momentum easier to repeat.
Modernize: Build a Momentum System, Not a Follow-Up Habit
Modern work is noisy by default.
Microsoft’s 2025 Work Trend research points to a workday shaped by interruptions, meetings, messages, and fragmented attention. For PMs, the lesson is clear: project momentum cannot depend on everyone remembering everything across chats, emails, meeting notes, and side conversations.
The system has to carry more of the work.
Gartner’s productivity research reinforces a similar point: productivity is not just more activity. It is quality, consistency, and value creation. For project professionals, that means better systems should help teams move toward outcomes, not just produce more updates.
A momentum system does not need to be complicated. It just needs to make the important things harder to lose.
The strongest version usually has three parts.
- First, it gives decisions a visible home. Open decisions are one of the biggest sources of hidden project drag. When a decision lives in someone’s memory or a long chat thread, it becomes easy to avoid, delay, or misunderstand.
- Second, it makes next moves easy to find. Project work slows down when action items are scattered across meeting notes, inboxes, and “I thought you had it” assumptions. A better system captures next moves in one place with owners and dates.
- Third, it creates a repeatable review rhythm. Momentum improves when the team has a simple cadence for asking: What moved? What is stuck? What needs a decision?
That is the point of modern PM systems.
They do not remove the PM from leadership. They make leadership less dependent on constant manual chasing.
The PM still guides the work. The PM still reads the signals. The PM still helps the team make smarter moves.
But the system starts carrying more of the follow-up. That is how momentum becomes repeatable.
|
|
Signal 1: The Infinite Workday Is Breaking Focus:
|
|
|
Signal 2: Productivity Needs Better Work Design:
|
Deliver: Build a Teams Momentum Loop
Here is the practical move for this week: build a simple Teams Momentum Loop.
Use this when project follow-up is scattered across Teams chats, meeting notes, side conversations, email threads, and “just checking in” messages.
The goal is not to create another place for noise. The goal is to create one lightweight system where momentum gets captured, assigned, reminded, and reviewed.
Set up a dedicated Microsoft Teams channel called: "Project Momentum"
Then organize it around three lanes.
- ONE - Decisions Needed: Use a pinned thread or channel post for open decisions that could slow the work down.
- Keep each decision simple: [DECISION] What needs to be decided? Owner: Who decides or drives it? Due: When does it need to land? Status: Open / Waiting / Decided
If a choice is blocking movement, it needs to be visible enough for the team to act on it.
- TWO - Next Moves: Use Planner in Teams, meeting notes, or a pinned channel post to capture follow-up tasks with owners and dates.
- Keep each next move simple: [NEXT MOVE] What needs to happen? Owner: Who owns it? Due: When is it needed? Related decision/blocker: What is it connected to?
This helps prevent the classic project problem where everyone leaves the meeting feeling aligned, but the next step slowly fades into chat history.
- THREE - Weekly Momentum Check: Use Teams Workflows to automate a recurring weekly reminder in the channel.
- The message can be simple: Weekly Momentum Check What moved? What is stuck? What needs a decision?
This is the heartbeat of the system. It creates a small, repeatable moment where the team can surface movement, friction, and decisions without waiting for the PM to chase every thread individually.
Together, this creates a lightweight loop:
Decision → Owner → Due date → Reminder → Review
Do not make this another status channel. Make it a momentum channel.
The PM still leads the system, but the system starts carrying more of the follow-up. Decisions become visible. Next moves have a home. Momentum gets reviewed on a rhythm.
That is how you stop chasing every thread and start making momentum repeatable.
The System Advantage:
The goal is not to chase harder. The goal is to build a system where the next move is easier to see, own, and act on.
Try this move this week and build one place where project momentum becomes visible.
