Every organization that hires a consulting firm to plan a cross-functional program has already produced work: decks, charters, roadmaps, governance documents, maybe a Confluence space with three hundred pages nobody has opened in months. Our first step is to read what already exists, compile it into a single inventory, and use it as the foundation for everything that follows. That choice shapes the entire engagement.
What We’re Looking For
The intake step produces a structured baseline. We’re looking for two things:
- Where the existing artifacts agree and where they contradict. A charter that says the program is “technology-led” and a roadmap that sequences business process changes first reveals how aligned the leadership team actually is.
- What is missing. The gaps in existing documentation reveal the questions nobody has answered yet (i.e., the dependencies nobody mapped and the constraints nobody documented).
We’re also paying attention to the language the organization uses to describe its own work. When we reflect the program back to leadership using the organization’s own vocabulary, it signals that the engagement is building on what came before rather than replacing it.
That baseline (i.e., what exists, where it connects, where the gaps are) becomes the starting point for every session that follows. It’s also the raw material for the landscape brief the board needs.
Why This Looks Different from Discovery
A client who’s been through a consulting engagement before has probably experienced a three-week discovery phase that produced a current-state assessment. It started with interviews, continued with workshops, and finished with a slide deck full of findings and recommendations. What you got was billable hours that feel like the consulting team is learning on your dime.
We’re documenting what exists rather than diagnosing what’s wrong, and that distinction changes the power dynamic. Documentation puts us in the position of organizer, reflecting the organization’s own work back in a structured way so the gaps become visible without anyone pointing fingers.
When the team sees a Workstream Hierarchy that organizes their prior work into a clean structure, the reaction is recognition: they built most of it, and the consulting team made it legible.
Handling the Political Reality
The client’s team built those charters and roadmaps. They know the documents are imperfect. Bringing in an outsider to review them carries an implicit judgment.
We treat intake as documentation rather than diagnosis: we’re not grading the work, we’re organizing it so the gaps show up on their own. We review artifacts without reacting to quality issues; the value we communicate is confidence that there’s a path forward. The things that are missing become apparent once the existing work is organized. Nobody needs to be told.
Sometimes the “roadmap” is a slide deck someone made for a board meeting two quarters ago and the “charter” is a paragraph in an email. The gap between what the organization says it has and what it actually has is one of the most valuable data points intake produces: it tells us where the real planning work needs to focus.
How that gap gets surfaced matters. We build the Workstream Hierarchy from whatever exists, and the missing pieces become structurally obvious. The client sees it without anyone saying it. Handled well, that moment builds trust because we understood the situation without making it a confrontation: making the invisible visible without making anyone feel exposed.
The room’s willingness to engage honestly for the next twelve weeks depends on how the first week goes. When the organization’s existing work is taken seriously (i.e., compiled and built upon), we earn collaboration.
The Case Against Starting from Scratch
Starting from scratch throws away institutional knowledge. The organization’s existing artifacts, even the flawed ones, contain decisions that were made for reasons. A roadmap that front-loads business process work before technology deployment might look like poor sequencing until we learn that the R&D team has active clinical trials that can’t be disrupted during Phase III enrollment and a regulatory submission window in Q2. That constraint is embedded in the existing plan. A blank whiteboard wouldn’t surface it until week six, when it’s too late to adjust.
Starting with what exists also changes ownership. When we build on the organization’s prior work, the leadership team sees continuity. The plan that emerges in week four feels like an evolution of their thinking, and that distinction determines whether the team executes the plan after the engagement ends or lets it collect dust alongside the last one.
The next time a consulting firm walks in and asks to start with a blank whiteboard, it’s worth asking what they plan to do with the three years of work already on the shelf.
