Tech Solution Canvas
Align product, architecture, and delivery constraints in one canvas.
The tech solution canvas aligns product goals, architecture, integrations, constraints, and delivery risks on one page for technical strategy.
Engineering builds without strategic context; product promises without feasibility. The canvas bridges teams.
Before major build phases, platform shifts, or enterprise deals with compliance needs.
- State product outcomes from strategy.
- Map components and data flows.
- List integrations and non-functionals.
- Mark build/buy/partner decisions.
- Link risks and ADRs.
- Tied to customer outcomes.
- Non-functionals explicit (security, scale).
- ADRs for key forks.
- Diagram-only — no decisions.
- Missing compliance constraints.
- Disconnected from roadmap priorities.
Northvale Systems tech canvas: API gateway to ERP, document store with retention policy, OCR microservice, SSO for internal buyers — ADR for build vs buy on OCR.
Acme Analytics canvas tied board-export goal to read-only warehouse, Stripe/NetSuite connectors, SOC2 controls — deferred ML forecast to Q4.
Harbor Consulting lightweight client portal for SOP videos — buy Vimeo OTT vs build — chose buy to protect consultant time.
Clearwater Initiative tech: offline-first mobile web, SMS aggregator, simple Postgres backend — minimise stack for field connectivity.
/tech tech-solution-canvas, IDs TS-01. Pairs ADR documents and Wardley maps.
Related techniques
Sources & further reading
- Richardson, C. (2018). Microservices Patterns. Manning.