It's Monday, 9:15. Your team is at their desks. The calendar is full, Teams is loud, and somewhere in a shared drive there's a strategy document you signed off on three months ago.
Here's the only question that matters: is anything happening in this room right now because of that document?
Not "is the team aware of the strategy." Set aside the all-hands rhetoric and the comms plan. Is the work on their screens at 9:15 on a Monday different than it would have been if the strategy had never been written?
For most organizations, the honest answer is no.
That's the gap this article is about. And here is a five-question test you can run this week to see exactly how wide it is in yours.
What the Monday Morning Test is (and isn't)
The Monday Morning Test is a diagnostic, not a culture audit and not an engagement survey. Those things measure how people feel about the strategy. This measures whether the strategy has actually changed what they do.
The difference is important. A team can feel aligned, quote the strategy back to you word for word, and still spend every Monday doing the same work they did before the strategy existed. Feeling aligned is cheap. Deprioritizing something last week because of the strategy is not.
You are looking for evidence of changed behavior. Specifically, changed decisions. Strategy is a pattern of choices, and if the pattern of choices hasn't shifted since the strategy was announced, the strategy hasn't landed. It's still sitting in the deck.
The test works because it avoids abstraction. You can't answer these five questions with a vision statement. You have to point at something that actually happened last week, or admit that nothing did.
The five questions
Ask these to anyone with a role in executing the strategy. Ideally, ask them to five different people at three different levels (exec, middle management, individual contributor) and compare the answers. The hardest signal to interpret is agreement at the top and silence everywhere else.
Question 1: What did you deprioritize last week because of the strategy?
A real strategy is a set of choices about what you will not do, so that you can do a smaller set of things well. If nothing got deprioritized, dropped, paused, or pushed out last week, then the strategy is not constraining anything. It's running in parallel with business as usual, not instead of it.
Watch out for "we're still doing everything, just with more focus." More focus is not a trade-off. A trade-off is when a named initiative, customer segment, feature, or workstream is explicitly moved off the table because the strategy says it's no longer a priority.
If you hear "nothing" from three people in a row, you don't have a strategy. You have a wish list with a cover page.
Question 2: Who's accountable for the #1 strategic priority, and what did they decide on Friday?
Every real strategy has a top priority. Someone owns that priority. If the strategy has landed, that owner is making decisions about it on a rolling basis, and those decisions are visible to the people executing the work.
Ask: who is the owner? Then ask: what did they decide on Friday? (Or any recent day.) If nobody can name the owner, the strategy is unowned. If the owner exists but nobody can name a recent decision, the owner is a title, not a role. The priority is sitting in their inbox waiting for "time to think about strategy."
This gets labeled a strategy failure. It isn't. The owner doesn't have the authority, the decision forum, or the cadence to act. Operating model work picks up here, and I'll come back to it in question 5.
Question 3: What changed in how you spend your time since the strategy was announced?
This one works backwards. Instead of asking "are you executing the strategy," you ask "has your time shifted." If the strategy has landed, time has moved. Meetings, reviews, deliverables, customer conversations. Something on someone's calendar looks different now than it did before.
"Nothing really, we're still doing the same things." That's the clearest signal that the strategy is ambient. It exists in the air but hasn't touched the ground.
Compare that with: "I stopped attending these three reviews, I'm now spending Tuesdays with the account team instead of with engineering, and our weekly planning meeting starts with the strategic objective instead of the sprint backlog." That's a strategy that is running the week.
Question 4: Which customer segment or opportunity are you now saying no to?
If you've read Richard Rumelt's Good Strategy Bad Strategy, you know a real strategy rests on a diagnosis of what matters and what doesn't. That diagnosis shows up as a visible decision to say no to a customer segment, a market, a feature request, or a partnership that would previously have been in scope.
If the answer is "we're trying to serve everyone well" or "we don't really turn business away," you have two problems. First, the diagnosis is missing or wasn't specific enough to create implications. Second, the commercial side of the organization doesn't believe the strategy is real enough to lose revenue over. And if they don't believe it, nobody else will.
The answer doesn't have to be dramatic. A sales team can politely decline a deal that doesn't fit the new focus, and that counts. So does a product team pushing back on a feature request that leadership loved a year ago. But something has to be rejected. Strategy without rejection is just aspiration with a roadmap.
Question 5: What structure changed to make the strategy executable?
I saved this one for last because it explains the others. A strategy can fail questions 1 through 4 for one reason: the organization's structure, decision rights, budget lines, meeting cadence, and role definitions still belong to the old strategy. Nothing was redesigned to make the new one possible.
Ask: what changed in how decisions get made? Who has new authority? Which committees dissolved? Which budgets were reallocated? Which meetings were canceled and which were created? If the answer is "nothing structural, we just communicated the new direction," you've found the root cause of everything else.
This is the hardest answer to get honest. People will often say "we added a new OKR" or "we created a task force." Neither of those count. An OKR is a measurement overlay on existing structure. A task force is a side project that avoids confronting structure. Structural change looks like: a role was created or eliminated, a decision that used to require a committee now belongs to a single owner, a budget line was moved from one function to another, a standing meeting was deleted.
If no structural answer exists, the strategy is being executed against the operating model of the previous strategy. That's the translation gap, and no amount of alignment workshops will close it.
How to read the answers
Run the five questions with at least five people at different levels. Then look for two patterns.
First, hunt for hollow agreement. If every exec gives a confident answer and every individual contributor says "I haven't really noticed anything different," the strategy exists in the leadership layer and stops there. I see this constantly, and it's fixable, because the problem isn't the strategy. It's the machinery between the exec floor and the work floor. That machinery is the operating model.
Second, look for contradictions on the same question. If two people name different owners for the #1 priority, the strategy has no home. If two people name different things they deprioritized, there's no shared understanding of the trade-offs. These contradictions are more useful than hollow agreement because they're specific and they point at named gaps you can close.
The goal is not to find someone to blame. The goal is to locate the exact point where the strategy stops being real. That point is almost never in the strategy document itself. It's somewhere in the transition from deck to calendar, in the gap between a named priority and someone with the authority to act on it today.
What to do with the diagnosis
If you run this test and the answers are mostly silent, you have three options, in order of how quickly they produce changed behavior.
The fastest is to make one structural change this week. Not a plan to change structure. An actual change: delete a meeting, move a budget line, assign a named owner with authority and cadence. Structural change, even small, creates the conditions for questions 1 through 4 to start having real answers.
The second is to write down your three actual trade-offs in one sentence each and publish them. Not the strategy. The trade-offs. "We are saying no to X. We are deprioritizing Y. We are not serving Z." This is uncomfortable on purpose. If you can't write the three sentences, the strategy isn't specific enough yet, which is useful to know.
The third, and slowest but most durable, is to redesign the operating model to match the strategy. This is the work I cover in my Operating Model series, and it's the layer most organizations skip because it's harder than writing a new deck. It's also the layer where strategy actually becomes execution.
The test runs in fifteen minutes
The Monday Morning Test takes less time than most status meetings. You can run it this week. You don't need permission, a workshop, a consultant, or a new framework. You need five people and five honest questions.
If the answers make you uncomfortable, that is the test working. Discomfort is a better signal than confident abstraction. It means you've located the gap between the strategy you announced and the organization actually executing.
The next step isn't to rewrite the strategy. It's to change one structural thing so that next Monday, the answers are different.
I'm Jenni. Most strategies stay vague. I help organizations define what their strategy actually means in practice, then build the operating models, processes, and concepts to execute it. Founder of Digital Rebel.