Author: Ivan Mechev
Last updated: 17 Feb. 2026
Justin’s article explains why Betty is a narrative-driven organization. This page answers a practical question: if MBRs are the engine of compounding improvement, what exactly are they and how do we run them properly?
An MBR is a written monthly memo produced by a business owner. It explains what happened, why it happened, what was learned, and what changes next. It is not a slide deck. It is not a KPI export. It is structured thinking captured in writing.
The purpose of an MBR is not to report activity. The purpose is to create clarity. At the end of reading one, a leader should understand the current state of the function, the trajectory it is on, and the decisions that matter next.
Over time, these documents create a record of how the business learns. Each month builds on the previous one. Insights accumulate. Mistakes become visible. Decisions become easier.
Importantly, the clarity is not only for the reader. It is also for the author. Writing an MBR forces the business owner to step back from the day-to-day noise and make sense of what actually happened.
Every MBR follows the same backbone. The sections are consistent so that thinking becomes comparable across teams.
Scorecard.
This is the small set of KPIs that define whether the function is winning or losing. Numbers without interpretation are noise.
Each metric must answer three questions:
Milestones.
What was shipped, launched, or completed during the month? These are meaningful progress markers, not task lists. The reader should see progress, not activity.
Wins and misses.
Where did execution outperform expectations? Where did it fall short? Misses are not cosmetic. They are diagnostic. If something underperformed, the MBR must explain why and what changes as a result.
Mindshifts.