The people managing the work don't know what's wrong with it.

If you want to know what's broken in a firm, don't ask the people running it. Ask the people doing it.

This sounds obvious. It almost never happens in practice.

Standard consulting discovery works by interviewing leadership. C-suite, VPs, directors. The people with a view of the organizational chart. Those people can tell you what the firm does, how it's structured, what the strategic priorities are. What they cannot tell you is how the work actually happens on a Wednesday afternoon in March when three things are late and nobody wants to be the one to say so.

The VP you'll meet first is almost always sharp, well-briefed, generous with time. She'll describe the firm's biggest pain points fluently. The proposal workload is a drag on senior staff. Compliance is a bottleneck. Project reporting is soft. Knowledge transfer is informal. She'll have data on all of it. She'll be right about every category.

She'll be right in the way the label on a medicine bottle is right. The label tells you what's inside. It does not tell you what it feels like to take it.

The actual texture of the pain shows up in conversations that happen later. Not with the VP. With the people inside the processes.

Every firm has a senior person whose role has quietly become being a human search index. She's the one who knows where the historical data lives, which documents are current, what the revised client preferences are, where the relevant precedents sit. New team members ask her. Senior colleagues ask her. Leadership asks her. She spends a significant share of her week pointing people to information. That share is invisible from above because from the outside it looks like collaboration. She's talking to people all day. What she's doing is retrieving.

Every firm has someone carrying institutional data in personal spreadsheets. Years of project actuals, rate benchmarks, margin data, lessons learned. When leadership wants to know what something cost three years ago, they ask him. When there's a partner meeting coming up, they ask him. This is known to leadership as "our reporting function" or "our controls process." What is not known is that when he takes a vacation, the function stops. When he retires, the knowledge walks out. He is the system.

Every firm has someone running an unofficial project in the margins of their day job. A team member who got frustrated with an existing tool and started building a better one in their spare time. Someone who made a template everyone uses but nobody above them knows exists. Someone who automated a process that saves six hours a week and hasn't told anyone. The results are real. Nobody above has noticed because the numbers aren't big enough to show up in quarterly reports yet. If you don't ask directly what people are working on that isn't on the org chart, you don't find it.

None of these patterns appear in a VP's description of the firm. They're not hidden. They're just invisible from that vantage point.

The pattern repeats in every firm we've worked with. Leadership sees the shape of the problem. The people inside the process feel the texture. You cannot build a system for the texture based on a description of the shape.

This is why our discovery phase takes fifty-plus hours inside a firm instead of fifteen. The first twenty hours get you what leadership knows. Hours twenty through fifty get you what leadership doesn't. The difference isn't volume. It's access. By the time we've spent enough time inside a firm that the senior designer feels comfortable saying she's essentially an information desk, we have the kind of information that actually builds useful systems. Before that point, we have category labels.

This also explains why so many AI assessments produce generic results. The consultant interviewed the people at the top, the top described the firm correctly, and the consultant produced a document that matches the description. Everyone feels good about the alignment. Then the recommendations get implemented and they miss the actual pain because the actual pain was never surfaced.

The fix isn't more sophisticated methodology. It's more time with more people lower in the org. A consulting firm that can't justify those hours inside the budget is either charging wrong or scoping wrong. More likely, both.

When we present findings to leadership at the end of a discovery engagement, the most common reaction is recognition. "I had a sense this was happening but I couldn't have told you that clearly." That reaction is the real deliverable. Not the document. The moment of recognition. That moment only happens when leadership is hearing from their own people, through us, at a level of specificity that their own org structure doesn't usually surface.

The people managing the work know what it looks like. The people doing it know what's wrong with it. A good discovery reaches both.