Most small businesses start a digital transformation with a shopping list: a new CRM, an accounting system, maybe an app. A roadmap starts somewhere else. It asks what needs to change, in what order, and how you will know it worked, before anyone signs a contract.
At Simple Scalable Solutions we use an eight-stage roadmap we call the 8 D's: Discover, Define, Design, Develop, Deliver, Drive, Document and Diversify. This post walks through each stage with the questions to ask, what you should have in hand at the end of it, and the shortcut that tempts almost everyone. You can use it to plan a new project or to check one that is already under way.
Key Takeaways
- A roadmap puts the problem, the people and the process ahead of the tools; a shopping list does the opposite.
- The 8 D's run in pairs: understand (Discover, Define), build (Design, Develop), launch (Deliver, Drive) and learn (Document, Diversify).
- Every stage should end with a tangible deliverable, so you can see whether it was actually finished.
- The most expensive shortcuts usually happen early (skipping Discover) and late (stopping at go-live without Drive).
Why a roadmap beats a shopping list
A roadmap beats a shopping list because software solves a problem only when the problem has been named first. Buying tools first tends to automate whatever you do today, including the parts that do not work.
The track record of digital change is sobering. A 2018 McKinsey survey of 1,793 respondents found that only 16 percent said their digital transformations had both improved performance and equipped the organisation to sustain those gains. The same survey had a more encouraging finding for smaller firms: organisations with fewer than 100 employees were 2.7 times more likely to report success than those with more than 50,000.
That makes sense. Small businesses can move faster and get everyone in one room. What they often lack is a sequence. Our article on why digital transformation fails explains the people and purpose side; the roadmap below is the order of work.
Here is the whole thing at a glance.
| Stage | Core question | Deliverable |
|---|---|---|
| Discover | What is really going on? | Findings on needs and opportunities |
| Define | What exactly will we change, and why? | Scope, objectives and success measures |
| Design | What should the new way of working look like? | Future process plus a solution design |
| Develop | Does the solution do what we designed? | Configured, tested solution |
| Deliver | Can people use it in real work? | Live system, migrated data, trained users |
| Drive | Are people actually using it? | Adoption measures and fixes |
| Document | What did we learn and achieve? | Results against objectives, feedback, guides |
| Diversify | Where do we take this next? | Next priorities and expansion plan |
Discover and Define: needs, scope and objectives
The first two stages decide whether everything after them is aimed at the right target.
Discover: identify needs and opportunities
Discover is where you find out how the business really runs, not how the org chart says it runs. That means talking to the people who do the work, watching processes end to end and looking at where time, money and customers leak away.
Questions to ask:
- Where do things wait, get re-typed or fall through the cracks?
- What do customers complain about, and what do staff complain about?
- Which problems cost the most, in money, time or goodwill?
- What has been tried before, and why did it stall?
Deliverable: a short findings document listing the main problems and opportunities, with rough evidence for each.
The tempting shortcut: asking only the owner or managers. Leaders see results; frontline staff see the workarounds that produce them.
Define: project scope and objectives
Define turns findings into a commitment. You choose which problems this project will tackle, which it will not, and what success looks like in measurable terms.
A good objective sounds like "cut quote turnaround from three days to one" rather than "implement a new CRM". The tool is a means; the objective is the outcome.
Deliverable: a one or two page scope document with objectives, measures, budget range, timeline, an owner and a clear list of what is out of scope.
The tempting shortcut: leaving scope vague so that everything can fit in later. Vague scope is how a three-month project becomes a year-long one.
Design and Develop: solutions built around the process
Design and Develop are where most people think the "real work" happens. They go faster and cheaper when Discover and Define were done properly.
Design: solutions and strategies
Design starts with the process, not the screens. Map how work should flow in future, decide which steps can be removed or simplified, and only then decide which tools support each step. This is also where you choose between configuring an off-the-shelf tool, connecting existing systems or building something custom.
Questions to ask:
- What is the simplest version of this process that still works?
- Which existing tools can we keep?
- What data do we need, and where should it live?
- Who will be affected, and how will their day change?
Deliverable: a future-state process map and a solution design that ties each requirement to how it will be met.
The tempting shortcut: copying the old process into the new system. You end up paying for software that preserves the old problems.
Develop: build and customise solutions
Develop is configuring, building and testing. For many SMEs that means setting up a platform rather than writing code. Either way, test with real examples from your business, not tidy demo data.
Deliverable: a working, tested solution signed off by the people who will use it.
The tempting shortcut: building every feature anyone asked for. Launch with what the objectives need; add the rest once people are using it.
Deliver and Drive: implementation and adoption
Go-live is where many projects declare victory. In our roadmap it is the midpoint.
Deliver: implement and deploy the solution
Deliver covers data migration, go-live and training. Plan the cutover date, decide what happens to old systems and make sure every user can do their daily tasks in the new one before it becomes the only option.
Deliverable: a live system with clean data and trained users, plus a named person for support questions.
The tempting shortcut: one long demo session for everyone. People learn by doing their own tasks, ideally with someone beside them for the first few days.
Drive: successful adoption and integration
Drive is the stage most projects skip, and it is often the one that decides success. It means watching whether people actually use the new way of working, removing friction quickly and stopping the old workarounds.
Questions to ask:
- Are people logging in and using the system for the tasks it was meant for?
- Are managers still asking for the old spreadsheet or report?
- What do users find slow or confusing, and can we fix it this week?
Deliverable: adoption measures tracked for at least the first few months, with a list of fixes made.
The tempting shortcut: moving the team on to the next project the week after go-live. Without follow-through, old habits return within weeks.
Document and Diversify: learn, then expand
The final pair turns a single project into a capability the business keeps.
Document: outcomes and feedback
Document compares results with the objectives set in Define, gathers feedback from users and records how things now work. Short guides and process notes mean new staff can learn the system without relying on the one person who set it up.
Deliverable: a results summary against each objective, user feedback, and up-to-date process guides.
The tempting shortcut: writing nothing down because "everyone knows how it works". Everyone knows until someone leaves.
Diversify: expand and scale
Diversify asks what comes next. With one process working well, you can extend it to another team, add automation, connect another system or take the model to a new location. This is where the roadmap loops back to Discover for the next project.
Deliverable: a prioritised list of next steps, each with its own rough business case.
The tempting shortcut: expanding before the first change has stuck. Prove it works in one place, then grow it.
Using the roadmap to check a project in flight
You do not have to start from scratch to use the 8 D's. If you are halfway through a project that feels off, work through these questions and note where the answer is "no" or "not sure".
| Stage | Check |
|---|---|
| Discover | Did we talk to the people who do the work, not just managers? |
| Define | Can we state our objectives as measurable outcomes, and is scope written down? |
| Design | Did we simplify the process before choosing or configuring tools? |
| Develop | Has the solution been tested with real data by real users? |
| Deliver | Is there a clear cutover date and a plan for the old system? |
| Drive | Are we measuring adoption, and does someone own fixing friction? |
| Document | Will we compare results with the original objectives? |
| Diversify | Do we know what we would do next if this works? |
The earliest "no" is usually where the trouble started. A project struggling with adoption often traces back to a Discover stage that never involved frontline staff, or a Define stage with no agreed measure of success. Fix the root, not just the symptom.
For a broader view of how transformation fits a business of five to 200 people, including budgets and what to do yourself, see our step-by-step guide to digital transformation for small business.
Frequently asked questions
How long does a digital transformation roadmap take?
It depends on scope. A single-process project, such as moving sales into a CRM, might run from Discover to Drive in a few months. A business-wide change is better treated as a series of smaller loops through the roadmap, each delivering results before the next begins.
Can we skip stages if the project is small?
You can shorten stages, but skipping them usually costs more later. On a small project, Discover might be two conversations and Document might be a one-page summary. The thinking still needs to happen.
Who should own the roadmap in a small business?
One named person with the authority to make decisions, usually the owner or a senior manager. They do not need to be technical. They need to keep the project tied to its objectives and make sure Drive gets the same attention as Develop.
Bringing it together
The 8 D's are less about the labels and more about the discipline: understand before you build, launch with adoption in mind and learn before you expand. Use the stages to plan your next project, or to find out why a current one has stalled.
The roadmap is also how we deliver our own work. If you would like help running it in your business, our services page shows how we take projects from Discover through to Diversify, and stay with you after go-live.
