The Short Stack

A simple, four-layer operating rhythm that holds transformation teams together.

There is no shortage of advice on how to run a productive team. Frameworks, methodologies, certifications. And yet, most teams still feel like they are sprinting on a treadmill. Busy and not quite sure if they are winning.The problem usually isn't effort. It is structure.

This is especially true for transformation teams — the ones building something new, navigating ambiguity, and operating without a clear playbook. These teams don't lack commitment. They lack rhythm. And without rhythm, even the most talented group of people will default to the one thing that feels productive but rarely is: more meetings.

The ‘Short Stack’ is a simple, four-layer operating rhythm that works for transformation teams. Like a short stack of pancakes, the beauty is in the layers. Each one is distinct. Each one has a job. And together, they hold the team. 

Why Most Team Systems Fall Apart

Before we get into the stack, it is worth naming the problem... Most teams do not design their operating rhythm — they accumulate it. A standup meeting gets added here. A steering group spun up there. A weekly sync that nobody quite remembers the purpose of. Before long, the calendar is full and the team is exhausted, but alignment remains elusive.

This is additive bias at work — see The "Add More" Trap. We bolt on new rituals without ever auditing the foundation. The result is accretion without intention: a team operating system that grew like a coral reef — slowly, organically, and completely unplanned.

When you are building something new, or transforming something that already exists, this is fatal. Ambiguity is already working against you. The last thing you need is a meeting structure that adds noise instead of cutting through it.

Introducing the Stack

Think of your team's operating rhythm as a short stack. Four layers. Each one intentional. Each one reinforcing the next.

No layer works in isolation. Strategy without governance stalls. Governance without action-oriented meetings loses touch with reality. Action without reflection just accelerates in the wrong direction. The layers are designed to work together. 

Layer 1: Strategy

Where are we going, and why?

Strategy is the foundation. Everything else in the stack points back to it.

For transformation teams, this layer is especially fragile — because strategy in ambiguous environments is not static. It shifts. It gets pressure-tested. It sometimes gets scrapped entirely. That's not failure; that's the work.

The job of this layer is not to produce a polished slide deck that lives in a shared drive. It is to give the team a living north star — something clear enough that every person on the team can articulate it in a sentence, and sharp enough to serve as a filter when priorities compete.

Strategy is too often treated as something that happens to a team rather than with one. A group of executives convenes, a direction is set, and the output cascades downward — polished, confident, and frequently disconnected from the reality of the people doing the actual work. The problem with that is that you've just locked out your best quality control ... The people closest to the work are not just your worker bees — they are your stress testers. They will find the gaps in the logic, the assumptions you did not know you were making, and the dependencies leadership couldn't see from above. That feedback doesn't undermine the vision. It sharpens it.

Leadership should set the vision — the north star, the "why we're here," the general direction of travel. But that goal needs to survive contact with the people tasked with achieving it. Build in the feedback loops. Create the conditions — deliberately facilitated sessions, with the proper pre-work (not a blank whiteboard and good intentions), where the team can push back, pressure test, and yes, occasionally redirect. A goal that can't withstand scrutiny from your own team won't survive contact with reality either. 

Set the strategy once a year. Edit it at the midyear point; and that edit? It happens in a retrospective. More on that in Layer 4.

Layer 2: Governance & Decision Making

Who decides what — and how fast?

This is the most under-designed layer in almost every team I have encountered. And it is the one that causes the most pain...

Slow decisions are not a people problem. They are a structure one. When decision rights are unclear, everything defaults upward — to the most senior person in the room or perhaps to an executive. The result is bottlenecks dressed up as due diligence.

For transformation teams, this is particularly acute. You are making consequential calls in conditions of uncertainty, often without precedent to lean on. The teams that move well are not necessarily smarter — they are clearer on the micro decisions they are willing to make and learn from. They know who owns what. They know when to escalate and when to just decide.

Good governance is not bureaucracy. Actually the opposite — it is what makes speed possible. You just have to take the time to design it...

Layer 3: Action & Work in Progress Meetings

Are we moving? Are we unblocked?

This is the layer most teams accumulate (the coral), and under-design. That over-investment and lack of proper architecture leads over time to a mashup of 1-1s, stand-up meetings, scrums, weekly syncs all piled on top of each other. All doing similar things but not quite. 

The two most underrated tool in a team leader's arsenal is not a framework or a methodology — it's the 1-1 & Work in Progress Meeting (WIPs). 

Done well, a regular 1-1 is where blockers get surfaced before they become problems, where context gets shared before it becomes confusion, and where the individual gets the attention they need to keep moving. Done poorly, it's a status update. A good 1-1 is led by the team member, not the leader. It's forward-looking ... always highlighting what is in the way, what is needed, and what is next ... not a recap of what already happened. Keep them regular, keep them short, and resist the temptation to fill the time. Silence in a 1-1 is usually something worth digging into.

The Work is Progress (WIPs) meeting is where individual momentum becomes collective momentum. Its job is simple: keep work moving across the team. Surface What is stuck, clarify what is unclear, unblock work and get out... The trap most teams fall into is letting these types of meetings drift into status theatre — a round-the-room recital of updates that nobody needed to hear out loud. Or they give into the temptation to use the time to think out loud . Resist it. Thinking out loud has its place ... it's just not here.

If someone leaves your WIP meeting unclear on what they are doing next, the meeting failed — regardless of how long it ran or how many people attended. Keep these meetings short (45 min max). Keep them action-oriented. And kill them the moment they stop doing their job.

Layer 4: Retrospectives

Are we learning — or just repeating?

The layer most teams skip. And yet it is the layer that can bring calm to the chaos of transformation type work. 

Retrospectives have a reputation problem. They are often treated as a formality — a box to check at the end of a quarter or Objective and Key Results (OKR) cycle before everyone moves on to the next one. Done poorly, they're a venting session, done well, they are one of the most powerful tools a team has.

For transformation teams, learning is the work. You are, by definition, operating in territory that has not been fully mapped. Every iteration is data. Every missed KR is a signal. The teams that compound their learning — that actually change how they work, not just what they are working on — are the ones that build something that lasts.

Treat retrospectives like a competitive advantage. Because they are.

The Syrup Test ...

To make sure your layers are sufficiently sticky run this quick gut check:

1. Can everyone on your team name the top strategic priority right now? [Layer 1: Strategy]
2. Was the last decision your team made slowed down by unclear ownership?[Layer 2: Governance]
3. How many blockers from last week's meeting are still open this week? [Layer 3: WIPs & Action]
4. Name one thing your team is doing differently today because of a retrospective? [Layer 4: Retrospective]

If any of those land uncomfortably, you know it’s time to stop and change how your team works... 

Structure beats hustle. Build your stack.