Discover: mapping a system across a wall of diagramsDiagnose: reading dashboards to locate the problemDesign: wireframes and interface work for the solutionDeliver: shipping the finished productEvolve: continuous improvement after launchAn operation moving from paper and habit to software
Map · Sequence · Deliver

Digital transformation

Transformation measured in shipped changes rather than in slide decks. The programmes that fail are not the ones with the wrong strategy; they are the ones where eighteen months pass before anybody outside the programme can see a single difference.

  • 90
    Days to first change
  • Map
    Before any roadmap
  • Stop
    Available each phase
  • Your
    Team runs it after

Sectors that trust us

What is transformation?

Transformation is changing how a business runs, not only which software it uses, which is why it is mostly a sequencing problem. The technology choices are usually obvious within a week; the hard question is which change goes first.

Is this a programme, or just a pile of projects?
Projects, sequenced, with a map that explains the order. A programme with one end date hides which parts are load-bearing, and when the date slips everything slips together.
Strategy or delivery?
Both, by the same people. The team that writes the map builds the first phase, which keeps the plan tied to what can actually be built.

Why programmes stall

Where programmes stall, and how ours keep moving.

How they stall

  • Months of discovery before anything is delivered.

  • One end date, so nothing can be separated out.

  • The map is a destination with no stated order.

  • External delivery, so nothing is learnt inside.

  • Sponsors see reports, never a changed process.

  • Supplier contracts are discovered mid-sequence.

How we sequence

  • A visible change inside the first ninety days.

  • Phases that each stand alone and each ship.

  • The order is argued for, in writing, up front.

  • Your team delivers more of each phase.

  • Progress is measured in changes, not documents.

  • Renewal dates are on the map from week one.

What changes

Transformation, cut into phases that can each ship alone.

What the phases run on

From the ERP you run to the cloud ahead.

  • AWS
  • Microsoft Azure
  • SAP S/4HANA
  • Microsoft Dynamics 365
  • Salesforce
  • PostgreSQL
  • Kafka
  • Power BI

Why SiaSol

The map takes three weeks, and everything after it is software.

The people who write the map build the first phase themselves, and your own team delivers a larger share of every phase after it, until the last phase is entirely yours.

  • Ninety-day result

    Something visible outside the programme itself, not a progress report.

  • Stoppable phases

    Each one stands alone and ships; stopping is a decision, not a failure.

  • Order explained

    The order is argued for in writing before any work starts, and revisited.

  • Capability moves

    Your team leads by the last phase, or the capability never transferred.

How it works · our method

The SiaSol five-phase method, applied to this service.

  1. 01

    Discover

    Most technology projects fail long before the first line of code — they fail at the question.

  2. 02

    Diagnose

    Every slow process has an owner and a cost.

  3. 03

    Design

    Architecture is a set of decisions you live with.

  4. 04

    Deliver

    Software not in production is just cost.

  5. 05

    Evolve

    The handover is the point, not the end.

Cost & engagement

Transformation: cost and phases

Cost is quoted per phase from a map we build first, and the map carries a fixed price of its own. A single multi-year number cannot be stopped sensibly, so we never quote one.

  • Fixed · three to four weeks

    Map and order

    The current state, the sequence, and a number against each phase.

  • Per phase · fixed after the map

    One phase

    Delivered, measured, and visible outside the programme.

  • Monthly · dedicated

    Embedded team

    A standing team working the map alongside your own.

Proof

Programmes delivered, and what moved

FAQ

What to ask about Digital transformation.

01How long does a transformation take?

The map takes three to four weeks and each phase four to ten. A typical estate runs eighteen months to three years, but the number that matters is ninety days, because that is when you find out whether the programme can actually deliver anything.

02Can we stop partway through?

At any phase boundary, and the phases are designed so that stopping leaves working systems rather than foundations. That is why we refuse to quote a programme as one number: a single price makes stopping look like failure when it is often right.

03Who does the actual delivery work?

We do most of phase one and progressively less of each phase after it, which is written into the plan as a share rather than left as an intention. By the last phase your team should lead and we should review, or the capability never moved.

04Do you work with our existing suppliers?

Yes, and the map includes them whether or not that is comfortable. A sequence that ignores a supplier contract with two years left is not a sequence, and the renewal dates are often the biggest constraint on what order anything can happen in.

05What if the strategy changes mid-programme?

The map is reordered, which is cheap because the phases were separable to begin with. This happens on most programmes longer than a year, and designing for it is the difference between a change of direction and a write-off of the work done so far.

06How do you measure whether it worked?

With two or three numbers chosen before phase one and measured as a baseline first, so a later improvement can be shown rather than asserted. Programmes that pick their measures afterwards tend to pick the ones that moved, which proves nothing.

07What happens when the programme ends?

Your team is already running it, because the delivery share moved across phase by phase rather than at the end. The closing deliverable is a dated document and a walkthrough, plus an optional support arrangement most clients take for one quarter.

Related services

Part of a wider transformation

Learn more

From the journal

Ready to see a change in ninety days?

Tell us what has to be different in a year, and what has already been tried. We come back with a map and an order.

Book the map