Method

Understand it. Fix it. Prove it worked.

Most operational improvement fails in a predictable way: someone buys a solution before anyone has established the problem. The MDS cycle is arranged so that cannot happen — diagnosis precedes design, design precedes purchase, and verification closes the loop.

01 — The cycle

Seven stages, in order.

Engagements can stop after any stage. Many stop after the second — which is a good outcome, not a lost sale, because the client leaves holding a map of their own operation and a ranked list of what it costs them.

  • 01  Audit

    The operation is mapped as it actually runs. Interviews with the people doing the work, inventory of every system and spreadsheet in use, the manual workarounds invented to keep things moving, and the points where information stops travelling. Nothing is changed, purchased or recommended at this stage.

    Ends with: a process map, a system inventory, and a time-and-cost baseline that everything later is measured against.

  • 02  Diagnose

    Symptoms traced to structural causes and ranked by what they actually cost. A missed follow-up is a symptom; the cause is that no system owns the handoff. Fixing the symptom buys a month. Fixing the cause is the engagement.

    Ends with: a ranked friction register, root causes, quantified cost per bottleneck, and a clear statement of what to leave alone.

  • 03  Architect

    The target operating state is designed before anything is bought: which system holds the record of truth, how data moves, what is automated, what stays deliberately human, and in what order the work is built. Dependencies are made explicit so the sequence survives contact with reality.

    Ends with: a target-state map, a system-of-record decision, an integration and data plan, and a sequenced build plan.

  • 04  Integrate

    The designed system is built. Existing tools connected where they can be, replaced where they cannot. Manual handoffs automated. AI applied where it removes measurable labour and declined where it would only add a subscription line. Migration planned so history is not lost in the move.

    Ends with: systems exchanging data directly, automated handoffs in production, and a completed cutover.

  • 05  Coordinate

    People, vendors, contractors, schedules and dependencies brought under one coordinating structure. A change in one place becomes information everywhere it matters. This is the stage that software-only firms do not offer, because it is not software — it is somebody owning the handoffs.

    Ends with: one schedule of record, vendor coordination under a named owner, and a single authoritative answer to "where does this stand?"

  • 06  Execute

    Physical implementation: site operations, transport, materials and equipment, field coordination, and the daily driving of the work. Plans get amended here, because this is where they meet conditions. MDS operates at this layer rather than handing over a document and departing.

    Ends with: the work done, issues escalated on a defined path rather than by chance.

  • 07  Verify

    Measurement against the stage-one baseline. What improved is stated with the number attached; what did not improve is stated just as plainly and gets a correction pass. The engagement closes with documentation the client's own team can operate from.

    Ends with: measured results, a correction pass where needed, and handover.

02 — Engagement

How the work is structured.

The shape of a typical engagement. Scope and duration are set per client.
Scoping conversation A conversation, at no charge, to establish whether there is a real problem here and whether MDS is the right party to solve it. Sometimes the answer is no, and it gets said in that conversation rather than after an invoice.
Audit engagement Fixed scope, fixed fee, agreed in writing before it starts. Delivered as a document and a working session. It stands alone — the findings are yours whether or not you continue.
Build and integration Priced against the sequenced plan produced in the architect stage. Broken into stages with their own acceptance, so the client can stop between stages without stranding the work.
Coordination and execution Ongoing operational engagement where MDS holds the coordinating role — schedules, vendors, dependencies, field execution — rather than advising someone else who holds it.
Verification Included in every engagement rather than sold as an extra, because an unverified system is not a deliverable.
03 — Operating rules

Five rules we hold ourselves to.

  • Diagnosis before prescription

    No tool is recommended, and no system is designed, before the current operation has been mapped and measured. A recommendation made without a baseline is a preference.

  • The baseline is captured first or not at all

    If the current state is not measured before the change, no honest claim can be made about the change afterwards. This is why stage one is not optional.

  • Technology is a component, not the pitch

    AI and automation are used where they do measurable work. Where a process problem can be solved by deleting a step rather than automating it, the step gets deleted.

  • The client owns the system

    Documentation, access and operating knowledge transfer at handover. An engagement that leaves a client dependent on the firm that built the system has failed on a dimension nobody put in the contract.

  • Bad news arrives early

    Overruns, wrong assumptions and things that did not work get reported when they are discovered, at the size they are then. Held long enough, every one of them gets more expensive.

04 — Limits

What MDS does not do.

A capability list that has no edges is not a capability list. These are the edges.

  • We are not a software vendor

    MDS does not sell a platform and is not paid by the tools it recommends. Where a client is better served by software already on the market, that is the recommendation, and MDS integrates it rather than competing with it.

  • We do not provide regulated professional advice

    Legal, accounting, tax, engineering sign-off and other licensed opinions come from licensed professionals. MDS coordinates around those requirements; it does not substitute for them.

  • We do not take engagements we cannot verify

    If the outcome cannot be measured — because the baseline is unobtainable or the objective is undefined — that gets raised before the work starts rather than discovered at the end.

  • We do not staff your org chart

    MDS coordinates, integrates and executes. It is not a staffing agency and does not place permanent headcount.

05 — Start

The first stage is a conversation.

Tell us what the operation looks like and where it feels heaviest. If there is a real problem here we will say so, and if there is not, we will say that too.

Request an Operational Audit What the audit covers