Lesson 30: Publish One Real Result, Then Name the Next Flow
Thirty lessons ago I said predictability creates leverage and speed is just a bonus. This is where that argument finishes.
You’ve mapped a flow and watched the work happen. You’ve picked a signal and defended it. You’ve installed a small artifact, piloted it, documented it, drilled against it, automated a piece of it, and handed it to someone else to carry. That’s a system.
One thing remains, and teams skip it more often than any other step in this loop: telling people it worked, and saying what you’re doing next.
The Rule: Adoption Follows Evidence, Not Instruction
You cannot mandate operational change across an organization. I’ve watched people try. What actually spreads a practice is another team seeing a measured result and deciding they want it.
So publish. Headline number, the human story in a sentence, and the next flow you’re going after. Then invite people in.
A Real Example: Two Volunteers
The billing win was real and it was isolated. Good numbers, one team, no wider effect.
I wrote a short internal post. The headline was plain: rollbacks down seventy percent, here’s how, and we’re going after onboarding next. Underneath it, one human sentence – the release team had stopped dreading Fridays. Then an open invitation to a thirty-minute kickoff, with the templates attached.
Two teams volunteered. Not because anyone told them to. Because a measured result plus an open door is a much stronger argument than any strategy memo.
Both subsequent pilots ran faster than the original, and the reason wasn’t the templates. It was that the people running them had chosen to be there.
How To Do This Yourself
Keep the post short – under three hundred words:
- The headline metric, stated plainly, with the time window attached. “Down seventy percent over ninety days,” not “significantly reduced.”
- The human story in one sentence. What it’s like to work there now compared to before.
- What you’re attacking next, named specifically.
- An open invitation – a thirty-minute kickoff, templates attached, anyone welcome.
Post it where people already are, not in a document repository. And be honest about what didn’t work; a post that admits a rough edge gets believed, and a post that reads as flawless gets quietly discounted.
The Honest Lesson
Publicity is where I’ve seen good operators lose credibility fastest, and it’s almost always the same mistake: announcing before the number holds.
A result at three weeks is a promising signal. A result at ninety days is a finding. Announce at three weeks and you’ll spend the next month explaining a regression, and the team that was going to copy you won’t.
The other failure is tone. Boasting without data creates skepticism, and skepticism is expensive to unwind. State the measurement, credit the people who did the work by name, and leave the adjectives out. The number carries the argument. It doesn’t need help.
Closing the Loop – and Starting It Again
That’s the thirty lessons.
If you take one thing from all of it, take this: nothing here was clever. There’s no framework in this series that couldn’t be explained to a new team member in ten minutes. A whiteboard. One metric. A three-line checklist. A twenty-minute meeting. Two phone calls. A page and a half of what we learned.
Small artifacts, short rituals, relentless accountability. That’s the whole method, and it works precisely because it’s small enough that people keep doing it when things get difficult.
The loop doesn’t end. Publish what you learned, pick the next thing that’s hurting, and run the same disciplined thirty days again. The second time is faster. The third time it stops feeling like a project and starts feeling like how you work.
Pick your next flow this week. You already know which one it is – it’s the one you thought of while reading this.
Thank you for reading all thirty.
– Babajide Agbaje