Management consulting has built an entire industry around a mandate it frequently cannot fulfil on its own: identifying the correct problem. Diagnosis and execution are typically treated as separate disciplines, often billed as separate engagements, and the space between them is where much of the value quietly disappears.
This pattern has a name worth using: symptom hiring. An organisation experiences a business problem in one visible location — declining revenue, a stalled market entry, weakening brand equity — and appoints an advisor scoped narrowly to that location. The advisor executes the mandate competently. The underlying condition resurfaces elsewhere. The engagement, by design, does not extend to the question of why.
Consider a familiar sequence. A business engages a consultancy to address slowing growth. The engagement produces a market-entry strategy: sound analysis, credible recommendations, a well-constructed deck. Six months later, growth has not materially changed, because the strategy was never operationalised. No one owned the translation of recommendations into a revised operating model, incentive structure, or customer-facing process. A second engagement is then commissioned, this time for “implementation support” — effectively re-diagnosing a problem the first engagement was already meant to solve.
This is the default operating model for how most organisations, and particularly small and mid-sized ones, purchase advisory expertise. Not because leadership is careless, but because the industry serving them was structured around discrete, sellable engagements. A bounded scope is what gets commissioned.
A related version of this occurs earlier in a business’s life, before there is a market to diagnose. CB Insights has spent over a decade cataloguing why startups fail, revisiting the same question across hundreds of post-mortems. The reason that consistently tops the list is not capital exhaustion or poor timing. It is “no market need” — cited in roughly a third to over 40% of failures, depending on the year of the report examined. This is, functionally, a failure at the diagnostic stage. Execution was rarely the deficiency; the harder question of whether the venture warranted building was the one left unasked, and no amount of subsequent execution corrects for a question never posed.
The coordination burden facing management has grown alongside this fragmentation. In 2011, chiefmartec’s annual count of marketing technology products stood at approximately 150. By 2025, that figure had exceeded 15,000 — roughly a hundredfold increase in a little over a decade. This is not evidence of a more capable ecosystem. It is evidence of specialised functions multiplying faster than any single actor’s ability to coordinate them, which is precisely the coordination role management consulting was originally conceived to provide.
There is a structural explanation for why the industry organised itself around narrow mandates, and economics supplies a term for part of it: the principal-agent problem. The consultant — the agent — is engaged by the client, the principal, but their incentives are not perfectly aligned. The agent is compensated for delivering the scoped recommendation well. Not for informing the client that the scope itself was misconceived. Raising that possibility risks the engagement, and consequently it is often left unraised. A market-entry study is a defensible, billable mandate. “We will not tell you what is wrong until we have examined the business as a whole” is a considerably harder proposition to sell, because it requires trust in advance of a deliverable.
None of this suggests the narrower work is without merit. The market-entry study is likely rigorous. The recommendations are likely sound. Assessed in isolation, these engagements succeed with some regularity — which is precisely what obscures the pattern from within the organisation commissioning them. Each invoice, considered independently, appears to represent value delivered.
The industry’s own literature on this problem is worth examining closely, because it illustrates the same failure at one remove. A widely circulated claim — traced to a 1999 Fortune article — holds that roughly 70% of CEO failures result from poor execution rather than flawed strategy. It has been repeated across business publications for two decades. A more recent academic review, published via Cambridge University Press, examined the evidentiary basis for figures of this kind and found the underlying estimates “outdated, fragmentary, fragile or just absent,” with reported failure rates ranging so widely across studies — from roughly 7% to 90% depending on definition and methodology — that no single reliable figure could reasonably be defended. The review’s conclusion was direct: considerable caution is warranted before such estimates are used to justify changes in management practice. The irony is difficult to overstate. An industry built on rigorous diagnosis has, for two decades, relied on a diagnostic claim about itself that would not survive its own methodology.
At TRD, every engagement runs through the same five phases, regardless of the mandate the client believes they are commissioning: Discover, Define, Design, Develop, Deploy. This is not a branding methodology adapted for consulting use. It sits above both functions, by design.
Discover constitutes the diagnostic phase proper — an examination of how the business actually operates, as distinct from its documented structure. Where decisions stall. What the customer experiences, as distinct from what internal materials describe.
[Read More: What is a DPR Report? A Complete Guide to DPR (Detailed Project Report) ]
Define is where the substantive diagnosis occurs, and it is the phase most engagements bypass. This is where the actual problem is named, rather than the symptom presented at the outset. A client requests a rebrand. Frequently, the brand was never the issue — the underlying business model was — and no amount of visual redesign was ever going to address that.
Design and Develop constitute the recommendation and build phases: the strategy is formulated, the solution constructed. Deploy is the phase the strategy-execution literature above is, in effect, describing the absence of — implementation within a live business, training the organisation to operate the change, and remaining present long enough to observe and correct what fails in the first weeks.
This is not the faster path, and presenting it as such would misrepresent the trade-off. A narrowly scoped consultancy can deliver a recommendation within weeks. The Discover phase alone can require comparable time, because it involves examining a business’s finances, systems, brand, and market position concurrently, rather than responding to a brief limited to one of these.
Speed, however, is not the correct optimisation target for an organisation accumulating uncoordinated engagements year over year. Coherence is the relevant objective, and coherence is precisely what symptom hiring is structurally unable to produce, regardless of the competence of any individual advisor.
The clearest indicator that an organisation faces this problem is straightforward: each individual engagement appears, on its own terms, to have succeeded, and the business has still not materially moved.
That is not several small problems. It is one problem, presented under several names, invoiced separately.
What TRD means by business lifecycle management follows from this directly. The firm does not conclude an engagement and exit. It remains engaged as the business progresses — from an untested idea, to a built product, to a market launch, to whatever growth subsequently requires — supplying the specific resource each stage genuinely requires, rather than the service the firm happens to offer by default.
At ideation, this takes the form of feasibility analysis and financial modelling: establishing whether the venture is viable before capital is committed. At the build stage, it is systems, brand, and product design, developed as a single coordinated effort rather than sequentially across unconnected advisors. At launch, it is a go-to-market strategy and the marketing channels genuinely suited to the business, rather than those most readily sold. At growth, it is the ongoing systems and brand infrastructure required to prevent the organisation from outgrowing its original design — a common failure mode, and one whose consequences typically surface in an unrelated part of the business well before the cause is identified.
The advisory relationship remains constant throughout. The nature of the work changes because the stage changes.
This is also the underlying logic of the 5D model. Discover and Define are not diagnostic exercises conducted once, at the outset of an engagement, and then archived. They recur at every transition to a new organisational stage, because what an early-stage venture needs to establish about itself differs substantively from what an organisation two years into a growth phase needs to establish. Design and Develop construct that stage’s specific response. Deploy embeds it within a business that continues to operate throughout implementation — a materially more demanding undertaking than producing a recommendation in isolation.
This is not, on examination, a more complex way to structure advisory work. It is the more coherent one. The genuinely complex arrangement is a distinct advisor for each stage of an organisation’s development, sustained by the assumption that someone, somewhere, is reconciling how the individual pieces accumulate.
