Raising the bar you missed: rebuilding a team's analytical capability
Not every study in this library starts with someone else’s problem. This one starts with a review I owned that fell short, and with the uncomfortable reason why.
The situation
I owned the Monthly Business Review for an organization of more than 200 people that was growing 50 percent while restructuring, with real turnover in the leadership ranks. One review missed the director’s bar on quality, precision, and clarity. Newer leaders were unsure how to turn data into a defensible narrative, and the honest root cause sat with me: I had indexed on conforming to the team’s established way of building the review rather than trusting my own instincts about what excellent looked like.
What I did
I ran a post-mortem with the contributors to locate the gaps, without turning it into a search for someone to blame. The problems were structural. The review drowned decision-relevant insight in exhaustive detail, and the people assembling it had never been taught how to move from data to analysis to narrative.
So we rebuilt the process and, more importantly, the capability. I streamlined the review to actionable metrics and insights. I wrote a playbook covering expectations, timelines, and the path from data to analysis to narrative, so the standard lived somewhere other than my head. I ran a workshop for the newer leaders on the business metrics themselves and on the harder skill underneath: how to extract an insight and report it out, meaning what matters, why it matters, and the action it implies. And I added a pre-review checkpoint to align drafts before anything reached the director, because feedback delivered in the room is a correction, while feedback delivered before the room is coaching.
What happened
The next review was markedly stronger, and the director said so directly. The leaders I coached gained confidence and autonomy, which mattered more than any single review. And senior global vice presidents adopted the quarterly version as the standard for other robotics teams. The playbook outlived my tenure, which is the test I hold capability work to.
The tempting version of this story is that I inherited a weak process and fixed it. The true version is that I deferred to an inherited process against my own judgment, and the miss was the bill for that deference. The fix that lasted was not a better deck. It was a team that could tell a defensible story with data, and a written standard that did not depend on me being in the room.