M25BuildTechnology· Module 1
Technology Strategy
Systems were bought one at a time to solve urgent problems. Together they don't fit the business.
- Grow
- Scale
- Fix
- Technology
- Strategy
- ~5 min · Map
The business problem
Many businesses accumulate software reactively: an accounting package here, a POS there, spreadsheets and WhatsApp in between. Data is re-typed, reports disagree and each new system adds cost without improving control.
Why it matters
Technology should follow the operating model. A simple strategy — what each system is for, which is the source of truth, and in what order to invest — prevents expensive mistakes.
What you will learn
- Map current systems against business functions
- Decide the system of record for each type of data
- Choose between buy, integrate and build
- Sequence technology investment by business priority
Core questions
- What system supports each function, and where do spreadsheets fill the gaps?
- Which system holds the truth for customers, products, stock and money?
- Where is data re-typed between systems?
- What should we fix before buying anything new?
Work through the module
CaseWhat is happening?
Distributor, 55 people · Illustrative teaching case
A distributor uses separate systems for accounting, stock, sales orders and delivery, plus a dozen spreadsheets. A new CRM is proposed. Mapping the systems shows the real issue is three different product lists. The business decides to fix product data and connect stock with orders before adding any new system.
DecisionWhat does the leader need to decide?
Buy the new system that has been proposed, or map and fix the existing landscape first?
FrameworkHow should they think about the problem?
Buy → integrate → build
Buy standard software for standard processes. Integrate it so data flows once. Build only where the process is distinctive and creates advantage. Fix process and data before any of the three.
ToolWhat can they use?
Systems mapMap
- List every system and spreadsheet in use
- Map each to the functions it supports
- Mark the system of record for key data
- Mark every manual re-entry between systems
ApplicationHow does it apply to their business?
Apply it to your own business:
- Draw your systems map
- Count the manual re-entries
- Rank the gaps by cost and risk
ImplementationWhat changes?
What should change in the business:
- Name a system of record for each data type
- Build a 12–18 month roadmap: fix, integrate, then buy
- Assign a business owner, not only IT, for each system
ReviewDid it work?
How to tell whether the change worked:
- Have manual re-entries reduced?
- Do reports from different systems now agree?
- Is each investment linked to a business outcome?
After this module you should be able to decide
Buy the new system that has been proposed, or map and fix the existing landscape first?
And leave with: A systems map and a sequenced technology roadmap.
Sequence · Technology
Related modules
Part of these learning paths