Who I Am and Why Process Consolidation Matters

Process consolidation, defined plainly, is the deliberate work of identifying which workflows from two merging entities survive, which are retired, and which must be rebuilt from scratch. I have spent my career doing exactly that — mapping the invisible architecture of organisations and finding the seams where duplication quietly drains resources. The uncomfortable truth most firms discover too late is that a merger's real cost is rarely the transaction itself; it lives inside the operational friction that follows. I built this practice around a single conviction: that friction is measurable, and measurable problems are solvable.

strategist mapping merger process

A Data-Driven Starting Point

Every engagement begins with what I call a Process Inventory — a structured audit that counts, categorises, and scores every workflow across both organisations before a single decision is made. Think of it as a building survey before a renovation: you would not knock down a wall without knowing whether it is load-bearing. The same logic applies here, and the numbers from that inventory drive every recommendation that follows.

teams collaborating on integration plan

Cause, Effect, and Honest Advice

Redundant approval chains cause delays; delays cause missed commitments; missed commitments erode the trust that made the merger worthwhile in the first place. I trace those chains back to their source and say plainly what needs to change, even when the answer is inconvenient. Budget-conscious organisations appreciate that candour, because it means effort is directed at root causes rather than symptoms.

director reviewing integration analytics

Methodology Built for Practicality

My three-phase Consolidation Framework — Assess, Align, Activate — moves organisations from diagnostic clarity through stakeholder alignment to live implementation. Each phase produces a tangible deliverable: a scored process map, a prioritised integration roadmap, and a monitored transition plan. No phase begins until the previous one is signed off, which keeps scope from expanding and budgets from drifting.

Honest methods, measurable outcomes, and a deliberate pace that respects the complexity of combining two organisations into one coherent operation

The Principles Behind My Approach to Post-Merger Process Work

I do not arrive with a pre-packaged answer and work backwards to justify it. I arrive with a structured set of questions and let the evidence build the case.
The analogy I return to most often is cartography. Before a navigator can plot a route, they need an accurate map — not an optimistic one, and not a borrowed one from a different terrain. Post-merger process work demands the same rigour: the map of your combined organisation must reflect what is actually happening, not what the org chart suggests should be happening. That gap, in my experience, is where the most costly inefficiencies hide.
Because I work primarily with organisations that are watching every dollar of integration spend, I have developed a strong habit of sequencing recommendations by impact-to-effort ratio. The highest-value changes — those that reduce friction quickly without requiring a technology overhaul — surface first. More complex structural changes are staged across a realistic timeline, so the organisation builds momentum rather than exhaustion.
Transparency is not a value I display on a slide deck; it is a working method. Every finding from the Process Inventory is shared with the client team in full, including the findings that reflect poorly on inherited decisions. An organisation that understands why a problem exists is far better equipped to solve it than one that has simply been handed a to-do list without context.

What Working With Me Actually Looks Like in Practice

From the first scoping call through to the final transition review, here is how I structure the work so that nothing important falls through the gaps
A merger creates a kind of organisational double vision: two teams, two sets of tools, two ways of describing the same task. My job is to resolve that double vision into a single, coherent operating picture.
01

The engagement begins with a scoping conversation — not a sales pitch, but a genuine diagnostic exchange. I ask about the size of each legacy organisation, the nature of the overlap, the timeline pressure, and the budget envelope. Those four variables shape everything that follows, and I would rather surface a mismatch in week one than discover it in week eight.

02

Once scope is agreed, the Process Inventory begins. This is the most time-intensive phase, and deliberately so. My lead consultant works alongside your operational teams to document workflows at the task level, not the department level. The difference matters: two departments can share a name and perform entirely different functions, and a department-level view will miss that entirely.

03

The Align phase translates the inventory findings into a prioritised roadmap. I present this roadmap in a structured review session with your senior stakeholders, walking through the cause-and-effect logic behind each recommendation. Nothing is implemented until your team has interrogated the reasoning and agreed the sequence. That sign-off process is not a formality — it is the mechanism that keeps the project on budget.

My Commitment to Practical Clarity

consultant delivering final integration package

There is a version of this work that produces impressive-looking deliverables and very little actual change. I have seen it, and I find it genuinely frustrating — not least because it tends to be expensive. The practice I have built is oriented around the opposite: modest documentation, clear decisions, and a transition plan that your operations director can run without a full-time consultant in the room. That last point is important. The goal of every engagement is to make my continued involvement unnecessary. A consolidated process architecture should be self-sustaining, understood by the people who operate it, and documented well enough to onboard new staff without tribal knowledge. When I hand over the final Activation package, it contains not just the integrated process maps but the rationale behind every structural decision — so that six months later, when a new team member asks why things work the way they do, there is a written answer waiting for them.

The Beliefs That Shape Every Engagement I Take On

These are not aspirational statements drafted for a website; they are the working assumptions I bring to every Process Inventory, every roadmap review, and every difficult conversation with a client stakeholder

Measurement precedes every recommendation I make

I do not recommend retiring a process until I have counted how many people use it, how often, and at what cost. That sequencing — measure first, conclude second — is the single habit that separates useful advice from expensive opinion. The numbers do not always tell a comfortable story, but they always tell an honest one, and honest information is what a budget-conscious organisation actually needs.

Cause and effect must be traced all the way back

A duplicated approval step is a symptom, not a root cause. I follow the chain backwards until I find the structural decision — usually made during a previous reorganisation — that created the duplication in the first place. Treating symptoms without understanding their origin is like patching a roof without finding the source of the leak: the problem migrates rather than disappears.

Transparency with clients is a working method, not a value statement

Every finding from the Process Inventory is shared in full, including the findings that reflect poorly on decisions made before I arrived. Selective disclosure might feel kinder in the short term, but it leaves organisations solving the wrong problems with the right energy. I would rather have a difficult conversation in week two than a costly rework in month six.

Simplicity is a discipline, not a default

Simpler processes are not automatically better processes — sometimes complexity is load-bearing, and removing it causes structural failure. The discipline I apply is to ask, for every layer of complexity: is this complexity earning its cost? If the answer is yes, it stays. If the answer is no, it goes. That question, asked rigorously across an entire process architecture, tends to produce significant savings without sacrificing resilience.

A Few Things I Think Are Worth Saying Plainly About This Kind of Work

Post-merger process consolidation is not a tidy project with a clean finish line — it is a sustained effort that rewards patience, rigour, and a willingness to say uncomfortable things out loud

Here are the working truths I have come to hold after years of doing this, stated without the softening language that usually accompanies them.

Four Reasons Organisations Choose to Work With Me

I am not the only person who does this work, and I would not claim otherwise. What I can say is that the organisations who engage me tend to cite the same reasons when they explain why they reached out — and those reasons are worth stating directly, because they help both of us decide whether the fit is right before the first invoice is raised.
    1

    Sequenced by budget impact first

    Every roadmap I produce orders recommendations by the ratio of friction reduction to implementation cost. The changes that deliver the most operational relief for the least expenditure appear first, so organisations see tangible improvement without committing the full integration budget upfront.

    2

    No phase begins without sign-off

    The three-phase Consolidation Framework is gate-controlled: each phase produces a deliverable, and the next phase does not begin until that deliverable is reviewed and approved. This structure prevents scope from drifting and keeps the engagement on the timeline and budget agreed at the outset.

    3

    Documentation built for internal ownership

    The final Activation package is written for your operations team, not for me. Every process map includes a plain-language rationale so that new staff can understand the decisions behind the architecture without needing to consult the original engagement records.

    4

    Findings shared in full, always

    I do not filter the Process Inventory before presenting it. Every finding — including the ones that reflect poorly on inherited structures — is included in the client report. Organisations that understand the full picture make better decisions about where to focus their integration effort and their budget.

About This Practice

I founded this practice on a single observation: the operational cost of a poorly consolidated merger almost always exceeds the cost of doing the consolidation work properly in the first place. That arithmetic is not complicated, but it is consistently underestimated — and the underestimation tends to be most painful for organisations that were already watching their budgets carefully.

The work I do sits at the intersection of operational analysis and organisational honesty. I map what is actually happening, trace the causes of what is going wrong, and produce a sequenced plan for making it better — one that your team can own and sustain without ongoing external support.

If you are in the middle of a merger integration and the process landscape feels more tangled than it should, I would be glad to have a scoping conversation. Please feel free to visit the contact page and send through a brief description of where you are in the process.

founder reviewing merger strategy documents

How This Site Uses Cookies

This website uses cookies to ensure core functionality operates correctly and to collect anonymised data about how visitors interact with its pages. No personal information is shared with third parties for marketing purposes. You may accept all cookies, reject non-essential cookies, or manage your preferences through your browser settings at any time.

Strictly Necessary Cookies

These cookies are required for the website to function correctly and cannot be disabled without affecting core page features.

Performance and Analytics

Anonymised cookies that help understand how visitors use the site, enabling ongoing improvements to content and structure.

Functionality Cookies

These cookies remember your preferences and display settings to improve your experience across pages on this site.

Third-Party Cookies

Some pages may load content from third-party providers that set their own cookies, governed by their respective privacy policies.