The 71-Hour Diagnosis: How a Time-Boxed Engagement Reveals What Years of Growth Can Hide
Seventy-one hours. Not seventy. Not eighty. Seventy-one.
The number is a prime. It does not divide evenly into anything. And that is entirely the point.
Most targets in business are made up. The 10 percent growth goal, the five percent efficiency improvement, the ninety-day sprint. Someone picked a number, called it a benchmark, and everyone agreed to chase it. The origin story is almost always the same: a gut call dressed up as data. So when it came time to define the shape of a diagnostic engagement, seventy-one felt right precisely because it refuses to look tidy. It is not a full work week. It is not a round number. It does not invite the kind of false comfort that round numbers bring. It invites a question instead: where did that come from? And that question, it turns out, is exactly the right energy to bring into a company that thinks it already has its systems figured out.
## The Number Is Not the Point. The Constraint Is.
There is something that happens when time is finite and the stakes are clear. People stop performing and start telling the truth.
Seventy-one hours spread across roughly a month is not enough time to pretend. It is enough time to listen, observe, map, and surface what has been quietly breaking underneath the revenue growth. It is enough time to find the one person in the organization who holds all the tribal knowledge that never made it into any document, the one whose name gets whispered when something goes catastrophically sideways: "I don't know, go find so-and-so."
Every scaling company has that person. Usually more than one. And the fact that the company's continuity depends on their availability, their memory, and their willingness to pick up the phone at eleven on a Tuesday, that is not a talent story. That is an infrastructure failure waiting to happen.
The seventy-one hours exist to catch that before Murphy does.
The engagement is structured in phases that build on each other. The first is straightforward: get to know the people. Not their job titles, not their org chart position, but their actual daily reality. The second is understanding what they do, the real processes, not the documented ones. The third, and the one that matters most, is extracting tacit knowledge. The stuff that lives between the lines of any process document. The judgment calls, the workarounds, the "we always do it this way because" explanations that reveal more about how a business actually runs than any slide deck ever could.
That third layer is where the real diagnostic work happens.
## What the Documents Cannot Tell You
Here is something that shows up in almost every engagement: there is a document. There is always a document. It was created by the first person who thought to write the process down, probably in the early days when the team was small and everything felt manageable. It is technically still there, buried in a shared drive that no one has opened in the better part of a year. It has not been updated since the person who wrote it moved on. And the four people hired since then? They figured things out by asking around, absorbing habits from teammates, and improvising when no one had an answer. The process lives in their heads now, not in the document.
This is not a failure of discipline. It is a scaling problem. Things move faster than documentation can keep up with, and no one gets rewarded for updating a process doc when there are actual fires to put out.
The diagnostic work is not about judging any of that. It is about getting it on paper before growth makes the gap expensive.
And here is the method that actually makes that work: you do not come in with your own language. You do not show up with frameworks and terminology that make sense to you and expect people to translate on the spot. That kills the trust before it has a chance to build. Instead, you listen. You take their words, map their reality back to them in the language they used, and only then do you start having a conversation about what to improve.
This lesson came from a real moment, early in a career spent learning industries from the inside out. Trying to understand hydraulic fracturing as someone trained in cementing, an engineer explaining the process kept getting frustrated because the questions kept pulling the conversation back toward familiar cement terminology. The instinct was to find a translation, to map the new thing onto the known thing. But that was the wrong move. The right move was to learn the language as spoken, do the internal gymnastics quietly, and speak it back correctly. Once that shift happened, the whole conversation changed.
That dynamic plays out in every company engagement. When people hear their own words reflected back, something relaxes. The guard comes down. They stop giving the polished answer and start giving the real one.
## The System Behind the Method
The honest question underneath all of this is: what does it look like when this becomes repeatable? Because a diagnostic that only works when one specific person is in the room is not a system. It is a dependency. And dependencies are exactly what the seventy-one hours are designed to eliminate.
Making this into a transferable framework means answering a set of very practical questions. How do you conduct the interviews? What questions unlock the tacit knowledge versus the surface-level answers? How do you code and categorize what you hear? When does AI help with the analysis, and when does critical thinking need to take the wheel? How do you synthesize across functions when finance, sales, and operations are all describing the same problem in completely different languages?
These are not abstract methodological questions. They are the difference between a process that scales and one that collapses the moment the original practitioner is unavailable. Reproducibility is the whole game. If the method cannot be documented, taught, and handed off with confidence, then it is just another piece of tribal knowledge waiting to become a liability.
The irony is not lost on anyone who has done this work: the diagnostic designed to surface undocumented knowledge must itself be thoroughly documented to be worth anything at scale.
## The Real Thing Being Built
At its core, the seventy-one hours are not a consulting engagement. They are a trust-building exercise with a deliverable attached.
The goal is not to walk in and tell a company what is wrong with them. People resist that, and they should. The goal is to listen long enough and carefully enough that when the map gets drawn and the recommendations get made, none of it sounds foreign. It sounds like the company's own thinking, clarified and organized. Because it is. The words on the page came from the people in the rooms. The analysis just connected what they already knew but could not see all at once.
When that happens, something shifts. Alignment becomes easier. Change becomes less threatening. And the systems that get built in the aftermath actually get used, because the people who have to live inside them helped build the language they are written in.
Seventy-one hours. A prime number. Nothing divides it cleanly. But it is enough time, when used right, to find everything that is quietly waiting to go wrong, and give it somewhere better to live.
Toodle-oo for now.