Most companies do not lack technology ideas. They lack a short, shared answer to the question "what are we doing with our systems this quarter?" Without it, requests pile up, every tool looks equally urgent, and the loudest complaint wins.
This article is for technology leads and managing directors of small and mid-sized companies. It describes a plan that fits on one page and can be agreed in a single meeting. It is about planning a whole quarter across your tools. If you are deciding how to modernise one specific system, see modernising a legacy system in pieces instead.
Why one page
A long roadmap gets out of date within weeks and nobody reads it twice. A single page forces choices. If something does not fit, it either waits or something else leaves. That is the point: the page makes the trade-offs visible before the quarter starts, not halfway through.
Keep the page for the next three months only. Longer horizons belong in a separate, looser list of directions.
The three columns
List every tool or system the business relies on, then place each one in exactly one column.
Keep
The tool does its job, people understand it and the cost of its problems is small. "Keep" does not mean "ignore". It means no project this quarter, apart from routine updates and backups. Write one line on why it stays, such as "stable, two users know how to fix it".
Replace
The tool causes regular, visible cost: lost time, errors, risk or a block on something the business wants to do. Replacement means a real project with an owner, a finish line inside the quarter and a plan for moving the data. If it cannot be finished or at least safely started in three months, split it into a first step, as described in the article on budgeting time for technical debt.
Leave alone
The tool is old or untidy, but touching it now would cost more than it saves. Typical reasons are that it is about to be retired, that only one person understands it and a change would be risky, or that it supports a process that is itself changing. Writing "leave alone" with a reason is a decision, not neglect. Add a date when you will look at it again.
Criteria for placing a tool
Use the same four questions for every line. Answer each in a word or short phrase.
- Business effect: what breaks or slows down if this tool fails or stays as it is?
- Risk: is there a security, legal or continuity concern, such as no support or a single person who knows it?
- Effort: roughly how many person-weeks would a change take, including moving data and training?
- Timing: is there a reason to act now, such as a contract ending or a planned change in the process?
A tool with high business effect, real risk and moderate effort is a candidate for "replace". A tool with low effect and high effort is nearly always "keep" or "leave alone". Do not add more criteria. The more you add, the more the discussion turns into scoring instead of deciding.
Keep the replace column short
The most common mistake is a replace column with eight items and a team of three. Count the capacity honestly: how many people, how many weeks, and how much of that time is already taken by normal support? Then fit no more than one or two replacements, plus the first step of a larger one. Everything else moves to the next quarter's candidates.
A useful rule is to leave a margin of about a third of the capacity free. Urgent problems will appear, and a plan with no room for them breaks in the first month.
How to defend the plan in front of leadership
Leaders rarely want to discuss the tools themselves. They want to know what the plan means for the business and what it asks of them. Prepare three short statements:
- What improves: for each replacement, one sentence on the effect, for example "invoices will no longer be re-typed by hand".
- What we are deliberately not doing: read out the "leave alone" column and the reasons. This builds trust, because it shows that the list was chosen, not just collected.
- What we need from you: a decision, a budget line or a person's time, stated once and clearly.
Avoid names of products and technical terms unless someone asks. If a question goes too deep, offer to answer it in writing afterwards. A calm "this is what we chose and why" is more convincing than a detailed defence of every line.
A short example
Imagine a distribution company with nine tools. The team places five in "keep", for example email and the accounting package. Three go to "leave alone", among them an old reporting spreadsheet that will disappear when a process changes in the spring. One goes to "replace": the order form that staff copy by hand into the stock system. The plan states the effect (less retyping, fewer wrong orders), the owner, the capacity needed and a review date for the spreadsheet. Leadership approves it in a twenty-minute meeting. The example is illustrative and does not describe a real client.
What to do this week
Write down all the tools your team supports on one sheet and put each in a column. Answer the four questions in a word or two. Then cross out replacements until the remaining work fits two thirds of your real capacity. Share the page with one colleague from the business side before you take it to leadership, and ask only whether each decision makes sense to them. For a related habit on the documentation side, see two-page documentation for an internal tool.
Sources
- Our related articles linked above.
- The approach described is a general working practice, not a standard; adapt it to your organisation. The example is illustrative and does not describe a real client. No figures or client results are claimed in this article.