For Team, Programme & Leadership
Most delivery problems aren't complicated. They're just ignored.
For 31 days, we shared the small, unglamorous practices that high-performing teams, programmes and leaders actually use - not the theory, not the frameworks, just the things that work.
If any of these hit a nerve, that's usually a sign there's something worth a conversation.
Mastery March
Day 1 - Team: Limit WIP Like You Mean It
The fastest teams don’t start more work.
They finish more work.
Try this this week:
• Count how many items are actively in play
• Compare that number to your team size
• If it’s higher, pause new starts
• Finish something before pulling something new
If everything is moving, nothing is finishing.
Benefits you’ll see:
🏁 Greater focus
🏁 Faster flow
🏁 More predictable delivery
Remember: Finish more. Start less.
Day 2 – Leadership: The One-Line Strategy Test
Aligned delivery starts with aligned leadership.
Clarity travels.
Try this this week:
• Ask each executive to write the strategy in one sentence
• It's important to keep it simepl, no slides or long explanations
• Compare the answers
Notice where they differ.
Small gaps at the top become big gaps in delivery.
Benefits you’ll see:
🚀Clearer decision-making
🚀Fewer conflicting priorities
🚀Less execution friction
Remember: Alignment reduces noise.
Day 3 – 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗲: Kill One Zombie Initiative
Strong portfolios aren’t busier.
They’re clearer.
𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• List every active initiative
• Highlight the ones without a measurable outcome
• Ask: “If we were starting today, would we fund this?”
• Stop one
Just one. - If everything continues, nothing improves.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
👉 Sharper strategic focus
👉 Freed-up capacity
👉 Clearer priorities
Remember: Progress often starts with stopping.
Day 4 – 𝗧𝗲𝗮𝗺: Turn KPIs into Experiments
High-performing teams don’t just report metrics. - They use them to learn.
𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Take one organisational KPI
• Ask: “What could we try this month to influence this?”
• Pick one idea
• Time-box it
• Measure
• Repeat
Stop reporting. Start experimenting.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
📣 Strategy translated into action
📣 Faster feedback loops
📣 Clearer connection between effort and outcomes
Remember: Metrics should drive behaviour, not just dashboards.
Day 5 – 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽: Ask “What Stops?”
Focused organisations don’t add endlessly.
They choose deliberately.
𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• When a new initiative is proposed, don’t ask “Can we fit this in?”
• Ask: “What stops?”
• Make the trade-off visible
• Force the choice
Capacity is finite. Strategy requires subtraction.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🎯 Clearer priorities
🎯 Reduced overload
🎯 Stronger execution
Remember: Strategy is defined as much by what you stop as what you start.
Day 6 – 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗲: Make Portfolio WIP Visible
High-performing portfolios don’t hide work in slide decks.
They make it visible.
𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Create a visible list of all strategic initiatives
• Show owner, intended outcome and status
• Highlight blocked work
• Review weekly, not quarterly
If teams visualise flow, portfolios should too.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
✔ Reduced duplication
✔ Faster identification of bottlenecks
✔ Clearer trade-offs
Remember: Work you can’t see is work you can’t manage.
Day 7 – 𝗧𝗲𝗮𝗺: Make Blockers Visible Daily
High-performing teams don’t ignore delays. - They expose them.
𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Add a visible “Blocked” column
• Track how long items sit there
• Escalate blockers within 24 hours
• Measure blocked time as seriously as cycle time
Silence hides delay. Visibility drives action.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
⚡️ Faster resolution of issues
⚡️ Reduced hidden wait time
⚡️ Improved leadership responsiveness
Remember: What waits quietly costs the most.
Day 8 – Programme: 𝗠𝗮𝗽 𝗕𝗮𝗰𝗸𝗹𝗼𝗴 𝘁𝗼 𝘁𝗵𝗲 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆
If work cannot be traced to strategy, it is optional.
Optional work clogs portfolios.
𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Pick three active initiatives
• Map each one to a strategic objective
• Tighten any vague links
• Challenge anything you cannot clearly connect
Assumption is not alignment. Evidence is.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
👀 Sharper portfolio focus
👀 Clearer prioritisation conversations
👀 Reduced strategic drift
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: If everything is strategic, nothing is.
Day 9 – Leadership: 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗟𝗮𝘁𝗲𝗻𝗰𝘆
Work slows down when decisions slow down.
Delivery rarely stalls because teams cannot execute.
It stalls because decisions are slow.
𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Track when teams request a decision
• Track when the decision is made
• Calculate the delay
• Remove one recurring bottleneck
What gets measured gets improved.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
• Faster across initiative execution
• Reduced hidden waiting time
• Greater leadership involvement
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Slow decisions are expensive decisions.
Day 10 – Team: 𝗥𝗲𝘁𝗿𝗼𝘀 𝗙𝗼𝗰𝘂𝘀𝗲𝗱 𝗼𝗻 𝗜𝗺𝗽𝗮𝗰𝘁, 𝗡𝗼𝘁 𝗙𝗲𝗲𝗹𝗶𝗻𝗴𝘀
Most retros become therapy sessions.
“How did we feel?”
“What frustrated us?”
“What annoyed us?”
Those questions matter. - But they are not enough.
High-performing teams don’t just reflect on feelings.
They reflect on impact.
𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Start with “What impact did we have this sprint?”
• Review outcome metrics before opinions
• Ask “What did we change in the system?”
• End with one experiment tied to a measurable result
Not a vague improvement.
A measurable shift.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🏆 Conversations become sharper
🏆 Experiments become clearer
🏆 Improvement starts compounding
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Feelings surface symptoms. Impact exposes causes.
Day 11 – Programme: 𝗗𝗲𝗳𝗶𝗻𝗲 𝗢𝘂𝘁𝗰𝗼𝗺𝗲 𝗘𝘃𝗶𝗱𝗲𝗻𝗰𝗲
Funding outputs is easy - Funding outcomes requires courage.
Before approving new work, define what success actually looks like.
𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Define the metric that must move
• Define the target you expect to hit
• Define the timeframe for impact
• Define how you will attribute the result
No metric. No movement. No approval.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
👓 Stronger investment decisions
👓 Clearer accountability
👓 Higher return on delivery effort
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Clarity before investment increases ROI after delivery.
Day 12 – Leadership: 𝗕𝗼𝗿𝗶𝗻𝗴 𝗼𝗿 𝗨𝘀𝗲𝗹𝗲𝘀𝘀 𝗘𝘅𝗲𝗰 𝗠𝗲𝗲𝘁𝗶𝗻𝗴𝘀
If your exec meeting is report-heavy, it is lagging reality.
Leadership time is too expensive for status updates.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
1. Send reports as pre-read and spend the first 15 mins silently re-reading
2. Spend the remainng meeting on decisions
3. Track decisions made in the meeting
Meetings should move work forward, not replay it.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
⚡ Faster strategic decisions
⚡ Reduced reporting fatigue
⚡ Clearer executive accountability
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Leadership time is a strategic asset. Use it for decisions, not information.
Day 13 – Team: 𝗥𝗲𝗱𝘂𝗰𝗲 𝗛𝗮𝗻𝗱𝗼𝗳𝗳𝘀
Every handoff adds risk.
Every transfer increases delay, confusion, and rework.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
1. Count the handoffs in a typical feature
2. Identify where ownership shifts
3. Remove one unnecessary handoff
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🚀 Reduced misunderstandings
🚀 Higher quality outcomes
🚀 Faster end-to-end delivery
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Fragmented ownership equals fragments results.
Day 14 – Programme: 𝗠𝗮𝗽 𝗗𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝗶𝗲𝘀 𝗘𝘅𝗽𝗹𝗶𝗰𝗶𝘁𝗹𝘆
Hidden dependencies create hidden delays.
If they are not visible, they cannot be managed.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
1. Map cross-team dependencies
2. Assign a clear owner for each one
3. Remove one recurring dependency
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🎯 Fewer last-minute blockers
🎯 Smoother cross-team delivery
🎯 Reduced coordination overhead
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: What is hidden will slow you down.
Day 15 – Leadership: 𝗧𝘄𝗼 𝗗𝗿𝗶𝘃𝗲𝗿𝘀 𝗢𝗻𝗲 𝗖𝗮𝗿
You know what really destroys alignment? Competing incentives.
If leadership measures in different directions then teams pull in different directions.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Put the executive KPIs on one page
• Circle the ones that push in opposite directions
• Ask: “Which one wins when they conflict?” collaboration
If there isn’t a clear answer, the organisation will decide for you.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🎯 Easier decisions when priorities collide
🎯 Teams will be able to self manage
🎯 Fewer “but Lucille told me to work on this" conversations
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: If you have two drivers, you have no drivers.
Day 16 – Team: 𝗪𝗵𝗲𝗿𝗲 𝗜𝘀 𝗪𝗼𝗿𝗸 𝗔𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗪𝗮𝗶𝘁𝗶𝗻𝗴?
Most teams think their problem dev speed. It isn’t.
It’s.......... waiting.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Pick a few recently finished work items
• Write down how long each took end-to-end
• Now estimate how much of that time was actual work
You've just done your first rudamental process efficiany diagram, which Jeff Sutherland says is the first step to Finishing Earlier.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🚀 Massive Productivity Gains
🚀 Significantly Faster Error Resolution
🚀 Improved team morale
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Work doesn't move slowly. It waits slowly.
Day 17 – Programme: 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝘆 𝗥𝗲𝘀𝗲𝘁
Priorities drift, deal with it. Work that made sense months ago is quietly consuming capacity.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Take your current top 5 initiatives
• Ask: “If we started this today, would it still be top priority?”
• If the answer is no, stop giving it the most capacity
Inertia is the most common portfolio decision.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🧭 You'll get capacity or what matters now
🧭 Teams get a sense of purpose
🧭 Fewer “why are we still doing this Karen?” conversations
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Old priorities rarely retire themselves.
Day 18 – 𝗗𝗲𝗳𝗶𝗻𝗲 𝗪𝗶𝗻𝗻𝗶𝗻𝗴
Most organisations think they’ve defined success.
Until you ask five people.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Ask five leaders: “What does success look like this quarter?”
• Compare the answers
• Create one version and make it explicit
Misalignment isn’t obvious until you surface it.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
⚡ Strategic advantage
⚡ Less wasted effort
⚡ Clearer direction across teams
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: You can't achieve what you can't define
Day 19 – 𝗦𝗶𝗹𝗲𝗻𝗰𝗲 𝗕𝗿𝗲𝗲𝗱𝘀 𝗦𝗶𝗹𝗲𝗻𝗰𝗲.
Silence is expensive.
If people don't speak up, your risks are already late.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• At your next retro ask: “What are we not saying?”
• Wait. Don’t fill the silence.
• When something is raised, don’t explain it and dont defend it
If nothing is said, that’s your signal.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🔍 Risks raised before they become issues
🔍 Fewer late surprises
🔍 Less time spent fixing avoidable problems
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: The problem you don’t hear is the one that costs you.
Day 20 – Programme: 𝗙𝘂𝗻𝗱 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝘀, 𝗡𝗼𝘁 𝗣𝗿𝗼𝗷𝗲𝗰𝘁𝘀
Projects end. Products evolve.
Why waste time trying to fund phase 2 of a project. Fund the product, and you can stop at any time.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Measure how long it takes to approve funding for a project
• Compare it to how long it takes to deliver the first feature
• If funding is slower, that’s your bottleneck
Speed of funding = speed of progress.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🔁 Faster continuation of valuable work
🔁 Less stop/start waste between phases
🔁 Delivery pace set by teams, not approvals
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: If you're still reading these comment for a free burger.
Day 21 – Leadership: 𝗡𝗮𝗿𝗿𝗮𝘁𝗶𝘃𝗲 𝗖𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝗰𝘆
Strategy must sound the same everywhere.
If leaders describe strategy differently, teams will interpret it differently.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
Listen to how leaders explain the strategy
Compare the messages across the leadership team
Align the language and narrative
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🗣️ Clearer organisational direction
🗣️ Stronger alignment across teams
🗣️ Greater belief in the strategy
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Consistency builds belief.
Day 22 - 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗰𝗮𝗽𝗮𝗰𝗶𝘁𝘆 𝗶𝘀 𝗳𝗶𝗰𝘁𝗶𝗼𝗻.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Write down actual team capacity (hours or points it doesn't really matter)
• Subtract meetings, support, and interruptions and other known stuff
• Plan only what fits, not what sounds impressive
The gap is your overload.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
📉 Fewer over-commitments
📉 Less hidden burnout
📉 More realistic delivery
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: If you don’t see capacity, you will exceed it.
Day 23 – Leadership: 𝗔𝗰𝗰𝗼𝘂𝗻𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗖𝗹𝗮𝗿𝗶𝘁𝘆
Decisions stall when many people share accoubtability
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Take your top 5 initiatives
• Ask: “Who makes the final call on this?”
• If you hear “we” or “it depends”, you’ve found the delay
Decisions don’t fail. Ownership does.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
⚡ Faster decisions without escalation
⚡ Less waiting for alignment
⚡ Clear accountability when things go wrong
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: If two people decide, no one decides
Day 24 - 𝗛𝗶𝗱𝗱𝗲𝗻 𝗱𝗶𝘀𝘁𝗿𝗮𝗰𝘁𝗶𝗼𝗻𝘀
Focus isn’t found- it’s protected.
Every interruption steals momentum, and divided attention quietly kills velocity.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Count the number of times developers get interrupted from someone outside the team
• Count the number of different items each developer is working on at the same time
• If either of these numbers is above 3 then bring it up in the retro More work doesn’t mean more output.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🚀 Faster completion of work
🚀 Less rework from switching
🚀 Higher quality outcomes
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Divided attention delivers divided results.
Day 25 – 𝗶𝗺𝗽𝗿𝗼𝘃𝗲, 𝗼𝗿 𝗮𝘁 𝗹𝗲𝗮𝘀𝘁 𝘁𝗿𝘆 𝘁𝗼.
Delivery without learning is just output
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• For each "done" ticket ask: “What did we learn?”
• At the retro ask: “What did we learn?”
• After the demo ask: “What did we learn?”
Learning is the real progress.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🧠 Better decisions over time
🧠 Less wasted delivery
🧠 Faster adaptation to reality
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: If nothing was learned, nothing will change.
Day 26 – Leadership: 𝗠𝗮𝗸𝗲 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝘆 𝗪𝗲𝗲𝗸𝗹𝘆
Strategy ignored weekly becomes irrelevant monthly.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Bring the top strategic metric into your Sprint Demo
• Ask: "What did we have on it?"
• If none, why not?
If nothing changes, it’s not a strategy, it's documentation.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
📊 Real change
📊 Needles Moving
📊 Team Ownership
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Strategy only matters if it matters
Day 27 – Team: 𝗦𝗺𝗮𝗹𝗹 𝗜𝗺𝗽𝗿𝗼𝘃𝗲𝗺𝗲𝗻𝘁𝘀 𝗖𝗼𝗺𝗽𝗼𝘂𝗻𝗱
Big changes are rare. Small ones stack.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• Notice one thing that slowed you down today
• Fix it before the end of the day
• Do the same tomorrow
Improvement is a habit, not an event.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
📈 Continuous performance gains
📈 Less resistance to change
📈 Sustainable improvement
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Marginal gains is a habit, not an event.
Day 28 – 𝗪𝗼𝗿𝗸 𝗶𝘀𝗻'𝘁 𝗹𝗶𝗸𝗲 𝘄𝗶𝗻𝗲, 𝗶𝘁 𝗱𝗼𝗲𝘀𝗻'𝘁 𝗴𝗲𝘁 𝗯𝗲𝘁𝘁𝗲𝗿 𝘄𝗶𝘁𝗵 𝗮𝗴𝗲.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• List all active initiatives
• Highlight the oldest
• Ask: “What is this waiting on?”
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
⏳ Hidden blockers surfaced earlier
⏳ Less time spent on stuck work
⏳ Faster movement across the portfolio
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: Inventroy cost money.
Day 29 – Team: Unclear Acceptance Criteria is a Tax You Keep Paying
Rework isn't a skills problem.
Most of the time, it's a clarity problem.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
Pick 3 recently completed tickets
Ask: "Was it clear what 'done' meant before anyone started?"
If the answer is no or maybe - write one sentence of acceptance criteria for your next ticket before it enters the sprint
One sentence. That's it. Done means done only if everyone agreed what done meant.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂'𝗹𝗹 𝘀𝗲𝗲:
✅ Less rework and back-and-forth
✅ Fewer "that's not what I meant" conversations
✅ Faster sign-off from stakeholders
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: If you don't know where the wall is, you'll keep painting it.
Day 30 – 𝗔𝗿𝗲 𝘆𝗼𝘂 𝗮 𝗹𝗲𝗮𝗱𝗲𝗿? 𝗗𝗼 𝘆𝗼𝘂 𝗰𝗿𝗲𝗮𝘁𝗲 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝗲𝘀, 𝗼𝗿 𝗮𝗿𝗲 𝘆𝗼𝘂 𝗮 𝗯𝗼𝘁𝘁𝗹𝗲𝗻𝗲𝗰𝗸?
Even good leaders can create overload.
𝟯 𝗹𝗶𝘁𝘁𝗹𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗼 𝘁𝗿𝘆 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸:
• List the active strategic initiatives
• Circle the ones you personally review every week
• If it’s more than 3, you are the bottleneck
Your attention sets the system’s limits.
𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝘆𝗼𝘂’𝗹𝗹 𝘀𝗲𝗲:
🎯 Clearer priorities at the team level
🎯 Less initiative context switching
🎯 Faster progress on what actually matters
𝙈𝙧. 𝙈𝙞𝙮𝙖𝙜𝙞 𝙨𝙖𝙮𝙨: If everything has your attention, nothing has your focus.
Day 31 – The Frozen Middle
You've heard of water-scrum-fall. But what about ag-water-gile? Doesn't wuite have the same ring to it.
Are you agile at the top and agile at the bottom but have a frozen middle?
Strategy gets lost when middle management is incentivised by old-school KPIs while teams are told to be "agile."
3 little things to try this week:
• Identify one "command-and-control" reporting requirement
• Ask: “Does this metric help the team or just provide a 'status'?”
• Replace one status update with a shared, transparent dashboard
Unfreeze the middle to let the value flow.
Benefits you’ll see:
❄️ Authentic agility, not "Fake Agile"
❄️ Higher trust in the process
❄️ More ice for your drinks
Mr. Miyagi says: With ice, it's all in the hips
