Solo Expert vs. Consultant Army

However, the core tension within modern strategy lies between this desire for the safety of the army and the structural necessity of the "Solo Expert" or the deep wedge approach. While the large firm sells the comfort of a methodology, the surgical expert offers the efficacy of an outcome-driven artifact. Organizations consistently find themselves caught in a loop where they hire the army to "sense" the environment, yet they lack the precise expertise to "seize" the opportunities identified or to "reconfigure" their internal assets to meet them. The gap between this perception of security and the reality of execution is where strategic value is routinely incinerated.

In the corporate psyche, there is a dangerous conflation of project management with strategic transformation. Organizations believe they are buying a future state, but they are often merely purchasing a temporary augmentation of their administrative overhead. The uncomfortable truth is that many large-scale initiatives are staffed not for domain depth, but for billable volume. The army arrives with smart generalists who follow a rigorous playbook but often learn the nuances of the client’s industry on the client’s time. This results in massive slide decks and assessment reports that provide the illusion of progress without the mechanics of change, creating systems so complex they require the army to stay on-site just to maintain them.

This systematic underestimation of domain depth leads directly to a primary cause of organizational failure: the prioritization of short-term goals over long-term competitive advantage. True competitive advantage is often ignored by project teams who focus only on direct, immediate objectives. Initiatives fail not because the Gantt chart was wrong, but because the organization’s dynamic capabilities—its ability to sense, seize, and transform—are treated as static bureaucratic functions rather than active competitive tools.

Real-world challenges further complicate this execution gap, starting with the pervasive trap of "imaginary precision." Project portfolio management models often require a degree of information precision that far exceeds the organization's ability to produce it. These exotic methods are frequently thwarted by the very poor quality of data inputs. When information is unreliable, governance becomes a performance rather than a decision engine. Ownership is often fragmented across matrix structures where, in reality, "he who shouts the loudest" dictates resource allocation, regardless of the strategic alignment documented in a strategy map.

Resistance to change in these environments is often a rational response to a governance system that feels like "policing" rather than support. When the Project Management Office (PMO) is perceived as an external auditor, project managers learn to hide unattractive data and attach failing projects to major strategic initiatives to ensure continued funding. This creates a culture of path-dependent evolution, where the organization continues to do what it has always done because the cost of stopping an "in-flight" project is seen as too high a political price for sponsors to pay.

Companies continue to rely on the "Consultant Army" as a structural necessity rather than a purely tactical choice. The army provides a buffer for the executive team—a standardized methodology that can be cited if the initiative fails. Furthermore, in highly "projectified" firms, internal staff are often tied up in legacy systems and operational fires, making the external team the only vehicle for resource reconfiguration. They provide a temporary form of organizing that bypasses internal silos, even if they lack the epistemic depth required for true innovation.

A recurring failure pattern emerges when companies mistake "tooling" for transformation. Implementing an enterprise-wide project management system does not create a dynamic capability. In fact, in turbulent or recessionary conditions, organizations often respond by making their processes more detailed, highly analytic, and centrally controlled, which ironically reduces the very individual discretion and agility they need to survive. They focus on the "what" of the portfolio—the list of projects—and ignore the "how" of the project ecology.

The topic of portfolio performance should actually be understood through the lens of a train schedule rather than a fixed funnel. In a fixed funnel, everything must be known and selected at the start; in a train schedule model, the departure dates and capacities are known, but the specific content is added and reconfigured as the train moves toward its destination. This allows the organization to postpone high-risk decisions until more information is available, minimizing the waste of "scoping out" features that the market never actually required.

The ultimate conceptual takeaway for any leader navigating a transformation is that organizational resilience is not found in the scale of the process, but in the depth of the wedge. Successful strategy implementation is not the result of following a monolithic playbook; it is the result of surgical interventions by experts who lead with outcomes and artifacts, coupled with a leadership team capable of the uncomfortable reconfiguration of its own resources. The Consultant Army can document your current state, but only the Solo Expert—internal or external—can help you navigate the uncertainty of your future. Success requires a shift from managing a list of components to cultivating a project ecology that rewards flexibility, accepts uncertainty as a built-in feature, and has the courage to kill poor projects before they become a permanent part of the organizational landscape.

Based on the academic literature provided, here are the five most relevant sources concerning the structural tension between standardized scale and surgical expertise in transformation:

1. Project Portfolios in Dynamic Environments: Organizing for Uncertainty (Petit & Hobbs)

2. The Project Management Office and its Contribution to Project Portfolio Performance (Revista Gestão e Planejamento, 2023)

3. A Dynamic Capabilities Perspective of IS Project Portfolio Management (Open Research Online)

4. Management of Project Portfolios (Research@CBS)

5. Project Ecologies: A Contextual View on Temporary Organizations (Grabher & Ibert)