01Open question
Earning credibility before changing how a team works
Reporting and cadence are operating infrastructure, and waiting makes the eventual intervention more expensive. On day one, though, nobody reports to you and nobody wants your operating model. By the time they do, the problems it would have prevented have already happened.
One approach is to solve one visible thing first and spend the credit right away. I lean toward sequencing the tension rather than removing it, which makes timing a discipline in its own right. Going early costs credibility you have not earned yet, and going late costs the problems you could have caught.
From · AMC Networks case study
02Open question
Making the cost of the status quo visible
At AMC, every proposed change was weighed against its implementation cost and almost nothing against the cost of continuing as-is. That cost is spread thinly across everyone’s week and appears on no line item.
Put the two costs side by side. The open question is whether the cost of the status quo can ever be measured with the same rigor as an implementation budget, or whether making it visible at all is most of the win. A visible estimate invites argument about the estimate, but an invisible cost never gets argued at all.
From · AMC Networks case study. The Kaseya case study covers the related question of what to make common.
03Decision
Knowing when to retire a quality check
Most of the checks in my system exist because something failed. That is a defensible way to grow a quality layer, and it is also a process with no natural stopping point.
I treat each fabrication as a specific defect with a cause, a reproduction case and an encodable fix, so the same class of error is caught if it recurs. The quality layer mostly grows, and checks that stop earning their cost get retired. A check costs time on every run in exchange for preventing an error that happened once. Pricing that trade is the harder discipline, and knowing when to retire a check is part of it.
From · KLJ Ventures case study
04Note
The different businesses implied by one revenue target
In a client analysis I laid out 3 illustrative revenue compositions that would each reach the same target. They were labeled as illustrations, not forecasts or recommendations.
The useful finding was not which composition to pick: each implied a different hiring plan and a different story at the next financing.
From · KLJ Ventures case study
Hiring for a Chief of Staff or Strategy & Operations leader?
Let’s discuss the role.