When every digital idea looks urgent, the useful question is not "what should we do?" but "what are we not doing this year?". A good roadmap scores each idea on value, effort and risk, puts them in an order that respects what depends on what, funds the top few with room for surprises, and writes the rest on a stop list. For a business with a few busy managers, that usually means one large project and one or two small ones at a time.
The worked example below follows a 30-person service business with seven ideas on the table and a $60,000 budget for the year. The figures are illustrative assumptions in Canadian dollars.
Step 1: collect every idea in one list
Put every idea in one place before judging any of them. Ideas live in owners' heads, staff complaints, vendor pitches and half-finished projects, and leaving any out means it will reappear later.
For each idea, write one line on the problem it solves, who asked for it and what "done" would look like. If nobody can say what problem it solves, it goes straight to the stop list.
Our example business has seven ideas:
- Move quoting from spreadsheets into the CRM.
- Connect the CRM to the accounting system.
- Rebuild the company website.
- Build an owner's weekly KPI dashboard.
- Add an AI chatbot to the website.
- Introduce an inventory app for parts and materials.
- Set up a password manager and an access register for all business accounts.
Step 2: score value, effort and risk
Score each idea from 1 to 5 on three questions, then combine them. We use value × 2 − effort − risk, because value should count most while still penalising projects that are hard or likely to go wrong.
- Value: how much time, money or risk it removes, or revenue it supports. 5 is large and measurable.
- Effort: money and staff time required. 5 is large.
- Risk: chance it fails, disrupts operations or depends on unknowns. 5 is high.
| Idea | Value | Effort | Risk | Score (V×2 − E − R) |
|---|---|---|---|---|
| 1. Quoting in the CRM | 5 | 3 | 2 | 5 |
| 4. Owner's KPI dashboard | 4 | 2 | 1 | 5 |
| 2. CRM–accounting connection | 4 | 2 | 2 | 4 |
| 7. Password manager and access register | 3 | 1 | 1 | 4 |
| 6. Inventory app | 4 | 4 | 3 | 1 |
| 3. Website rebuild | 3 | 4 | 3 | −1 |
| 5. AI chatbot | 2 | 2 | 4 | −2 |
Check one row: quoting scores 5 × 2 = 10, minus 3 for effort, minus 2 for risk, which gives 5. The scores are rough on purpose. If two people score an idea two or more points apart, the discussion that follows is usually worth more than the number.
Step 3: respect dependencies
A high score does not mean "start first". Some projects only work once others are finished, so sequence by dependency before you sequence by score.
In our example, the KPI dashboard scores well but depends on clean quoting data in the CRM and on the CRM–accounting connection, because revenue and margin figures come from both. Starting it first would mean building reports on data you are about to change.
The access register has no dependencies and protects everything else, so it goes early even though its score is middling. It is also the cheapest item on the list.
Dependencies for the example:
- Dashboard (4) needs quoting (1) and the connection (2).
- Connection (2) works best after quoting (1) is in place.
- Inventory app (6) needs a decision on how parts appear on quotes, so it follows quoting (1).
Step 4: lay out a 12-month roadmap by quarter
Put the sequenced projects into quarters, with one major project at a time. Leave white space; work always takes longer than the plan.
| Quarter | Main project | Small project | Decision point |
|---|---|---|---|
| Q1 | Quoting moved into the CRM | Password manager and access register | Is quoting live and used by everyone? |
| Q2 | CRM–accounting connection | Data cleanup of customer records | Do invoice totals match between systems? |
| Q3 | Owner's KPI dashboard | Written KPI definitions | Does the owner use it weekly? |
| Q4 | Inventory app: requirements and shortlist only | Roadmap review for next year | Buy, defer or drop? |
Notice that Q4 is a decision, not a purchase. Deciding whether to buy inventory software is a smaller commitment than buying it, and by then you will know far more. For the dashboard, our owner KPI dashboard guide covers the definitions step.
Step 5: sequence the budget, with contingency
Fund the plan quarter by quarter and hold back a contingency of at least 15%. Money spent early on the wrong thing is the hardest to recover.
| Item | Budget |
|---|---|
| Quoting in the CRM (setup and training) | $18,000 |
| Password manager and access register | $2,000 |
| CRM–accounting connection | $9,000 |
| KPI dashboard | $8,000 |
| Inventory app requirements and shortlist | $5,000 |
| Contingency (15% of $60,000) | $9,000 |
| Held for Q4 decision | $9,000 |
| Total | $60,000 |
The allocated projects add up to $42,000. With $9,000 contingency, that is $51,000, and $9,000 is held until the Q4 review. If the inventory app is approved, that reserve becomes its first instalment; if not, it rolls into next year.
Step 6: write the stop list
The stop list is the most important part of the roadmap, and the one owners most often skip. Write down what you are not doing, why, and when you will reconsider.
- Website rebuild: deferred to next year's review. The current site works; a rebuild competes for the same people who are moving quoting. Revisit once the dashboard shows which services bring the most margin.
- AI chatbot: stopped. Low value at current enquiry volumes and a real risk of wrong answers reaching customers. Revisit if enquiries double. If you want to test AI, the automation payback guide shows how to pick a safer first task.
When a vendor calls about the item on the stop list, the answer is already written down.
Common mistakes in digital roadmaps
The same few problems appear again and again.
- Starting with the most visible project. A new website feels like progress, but it rarely fixes the problems staff complain about daily.
- Running too much at once. Three overlapping projects share the same five people and all slip.
- Skipping the decision points. Each quarter should end with a yes, no or adjust.
- No owner per project. Every project needs one named person inside the business who is accountable.
A quarterly review agenda
A 60-minute review each quarter keeps the roadmap alive. Use the same agenda every time.
- What finished, and did it deliver the value we scored? (15 minutes)
- What slipped, and what was the real cause? (10 minutes)
- New ideas since last quarter, scored on the same three questions. (15 minutes)
- Next quarter's main and small project, with named owners. (15 minutes)
- Anything to add to, or take off, the stop list. (5 minutes)
Where we come in
Our digital strategy and roadmap engagement runs this process with your leadership team and delivers a costed, sequenced plan with the stop list included. If a project on the roadmap involves new software, software selection is the next step. To talk it through, call or text (604) 632-4959, or see how we work.
Frequently asked questions
How many digital projects should a small business run at once?
For most businesses under about 50 people, one major project and one or two small ones at a time. The limit is usually the attention of the few people who know how the business works, not the budget.
What scoring method do you use?
A simple one: value counts double, then subtract effort and risk, each scored 1 to 5. It is deliberately rough. Its job is to start an honest conversation, not to produce a precise number.
Why write a stop list?
Because ideas that are not explicitly stopped tend to come back every month and pull attention. A stop list records what you decided not to do, why, and when you will look at it again.
How often should the roadmap be reviewed?
Quarterly. Review what finished, what slipped and why, re-score anything new, and adjust the next quarter. Changing the plan every week means there isn't one.