Review and learn

The last move in the loop is the one teams skip most: stopping to learn. Done well, it is what turns one project’s lessons into the next project’s defaults.

Accountability is a way to work, not a punishment

A person is accountable when they:

• understand the goal
• agree to the next step
• give honest updates
• raise risk early
• ask for help when needed
• follow through, or explain why they cannot
• learn from mistakes

A manager is accountable when they:

• set clear goals
• make priorities clear
• give people the tools they need
• respond to issues fairly
• make decisions when needed
• address repeated problems

Read those two lists together and the point is obvious: accountability is shared. It is not something managers do to people; it is how both sides hold up their end.

Early warning is part of follow-through

Following through does not mean never missing. It means you raise the risk early — a Yellow before a Red, a Red before a missed deadline — so the team can still act. Quiet failure is the opposite of accountability, even when the intention was good.

A look-back that earns its hour

A review is only worth running if it changes something. Keep it simple:

• What were we trying to make true?
• What actually happened?
• Where did the system help or get in the way?
• What is the one change we will carry into the next round?

If the same problem shows up here that showed up last time, that is your signal: the change from the last look-back never actually got made.

Try it on real work

Run a short look-back on something that just finished — good or bad — and force it to end with one specific change and an owner for that change. The Look-Back Review template keeps it tight.