Build a Technology Strategy
Strategy · 2–3 weeks · Advanced
The job
Map your value chain and technology landscape to make better build-vs-buy and investment decisions.
What the sponsor gets
Each canvas and map from this playbook — PESTLE Canvas, SWOT Analysis, Cynefin Framework, Prioritisation Matrix, OKR Canvas, Journey map — exports as a PDF, or as PowerPoint on Pro, straight from the session, and the whole run exports as one PowerPoint for the sponsor. Nothing is redrawn.
The method
Audit the current technology landscape
Catalogue existing systems, integrations, technical debt, and team capabilities. Interview engineering leads, product owners, and the CFO to understand where technology enables the business and where it constrains it.
Tip: Ask "what do you work around every day?" — the workarounds reveal the real pain points, not the system inventory.
Scan external technology forces
Create a PESTLE canvas focused on technology trends, regulatory requirements (data privacy, AI governance), competitive moves, and talent market shifts that should inform the strategy.
Tip: Separate hype from relevance — not every technology trend matters to your organisation. Focus on what affects your specific value chain.
Assess technology strengths and gaps
Create a SWOT canvas for your technology function. Be honest about legacy debt, skills gaps, and vendor lock-in alongside genuine strengths.
Tip: Your biggest weakness is usually not the technology itself — it is the organisation's ability to absorb change at the pace the strategy demands.
Classify investment decisions by complexity
Use Cynefin to categorise each technology initiative. Infrastructure upgrades are typically complicated (expert domain), whereas AI adoption and platform shifts are complex (experiment and learn).
Tip: Resist the urge to treat everything as complicated and hand it to consultants — complex initiatives need experimentation, not blueprints.
Prioritise the technology portfolio
Plot all candidate initiatives on an impact-vs-effort matrix. Include both new investments and debt reduction. Force the leadership team to make trade-offs rather than funding everything insufficiently.
Tip: Technical debt reduction rarely looks exciting on the matrix but failing to invest in it makes every future initiative slower and more expensive.
Plan the people side of technology change
Create a Change Management journey for how staff will experience the technology shifts. New systems fail when adoption planning is an afterthought.
Tip: Budget at least 20% of any technology programme for training, change management, and adoption support — or accept that the system will be underused.
Set 12-month technology objectives
Translate the prioritised portfolio into OKRs covering delivery milestones, adoption targets, and capability development. Each objective needs a single accountable leader.
Tip: Include at least one OKR about reducing technical debt — if it is not an explicit objective, it will always lose to feature work.
The canvases and maps
- PESTLE Canvas
- Six fixed boxes — political, economic, social, technological, legal and environmental — so the room scans the whole outside world, not just the two forces it already worries about.
- SWOT Analysis
- Four quadrants split inside from outside and helpful from harmful, so strengths cannot hide threats and every point has to land somewhere.
- Cynefin Framework
- Complex, complicated, chaotic and clear, with disorder beneath for anything not yet sorted, so the team agrees what kind of problem it has before it chooses how to tackle it.
- Prioritisation Matrix
- Impact against effort in four quadrants — quick wins, major projects, fill-ins and avoid — so the team trades off instead of calling everything a priority.
- OKR Canvas
- One objective, three key results and the initiatives beneath them, so ambition and measurement sit on the same page and no initiative floats free of a result.
- Journey map
- Stages run across and lanes run beneath them, so the experience reads in the order people live it and each low point lines up with what causes it.
What it doesn't do
It doesn't run the room for you or decide for the client. The steps, canvases and duration are a starting point you adapt; the judgement stays yours.