Purpose
The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Architecture Canvas
Architecture Inception Canvas
Structures the start of a new system around business goals, functions, constraints, and architecture hypotheses.
A compact inception workshop for a new system: business case, functions, context, quality goals, constraints, hypotheses and risks.
Which goals, constraints and testable architecture hypotheses shape the new system?
- Participants
- 3-8
- Time
- 60–120 minutes with prepared participants; missing requirements or technical research are separate.
Which goals, constraints and testable architecture hypotheses shape the new system?
System
Name system and business case
Complete system, team, date and iteration; describe business case and functional overview for a new system.
Goals
Capture context and quality goals
Draw the system as a black box with communication partners; record the top quality goals from stakeholder view.
Constraints
Record constraints
Separate binding requirements from preferences; add source, owner and effect.
Hypotheses
Record hypotheses and risks
List consequential architecture hypotheses with reasons, technical risks and a way to investigate them.
Update the work record when new evidence, changed constraints or the planned review changes an assumption.
A good fit when
For greenfield work at project inception, not detailed design or a general replacement for communication about existing systems.
Ideal for
- Inception Workshops
- Early Product Discovery
- Stakeholder Alignment
Not good for
- Mature systems with good documentation
- Detailed implementation work
Outputs
Context for a greenfield inception
The canvas contains system, team, date, and iteration, as well as the business case and functional overview for a new system.
Context diagram and quality goals
The diagram shows the system as a black box with communication partners and records the top quality goals from the stakeholder view.
Traceable constraints
The artifact separates binding requirements from preferences and includes source, owner, and effect.
Hypotheses and technical challenges
The artifact lists consequential architecture hypotheses with reasons, technical risks, and an investigation approach.
Architecture Inception Canvas fields from the published template
Fictional example
Source-defined fields only; use the linked version. The example is fictional and the working canvas begins empty.
Business Case
Describe the business or economic driver.
A rental booking service is proposed; the economic driver still needs confirmation.
Functional Overview
List the most important functions at high level.
Check availability, request a reservation and receive confirmation.
Business Context
Show the system as a black box and its communication partners.
Customers and payment service are neighboring partners.
Organisational Constraints
Record organizational limits on design choices.
Must connect to the existing booking operation; owner to confirm.
Quality Goals
Name three top quality goals from key stakeholder view.
Clear status during concurrent reservations; metric still open.
Technical Constraints
Record technical limits on design choices.
Existing booking interface needs verification.
Architectural Hypotheses
Record consequential architecture hypotheses and reasons.
A spike tests whether availability can be synchronized reliably.
Technical Challenges & Risks
List known technical challenges and risks.
Timeout may leave reservation status unclear.
First step
Use the published Architecture Inception Canvas and record system, team, workshop date and iteration.
Deep dive
How it works
First, goal, context, stakeholders, risks, and constraints are collected. Then the team condenses key options, open questions, and assumptions into a shared working state. This creates a usable starting point for architecture conversations and further detail work.
In detail
The canvas helps because it focuses an early architecture conversation on goals, framing, risks, and key decisions before details diverge. Good use connects product context and technical consequence instead of just producing a nice overview. Its strength shows when dependencies, quality demands, and open bets get a shared place early, making starting decisions more deliberate.
Facilitation
Start with the occasion, target picture, and the initiative's most important uncertainties so the canvas provides genuine initial orientation. The picture gets clearer as soon as an open assumption touches several technology decisions. Finish by noting a few prioritized architecture questions and a clear path for the first validations.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Sources
Architecture Inception Canvas (official PDF)canvas.arc42.orgThe official arc42 template specifies these named fields and distinguishes AIC from its communication canvas.Canvas overview | arc42canvas.arc42.orgThe official arc42 template specifies these named fields and distinguishes AIC from its communication canvas.
Artifact templates
Architecture Inception Canvas: WorksheetPlan a session or initiative to match the actual scope of work.canvas
Architecture Inception Canvas: WorksheetPlan a session or initiative to match the actual scope of work.
canvasarchitecture-inception-canvas-working-template.md
Plan a session or initiative to match the actual scope of work.
Architecture Inception Canvas: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Prepare the full method Time: 60–120 minutes with prepared participants; missing requirements or technical research are separate.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Official canvas, business goals, communication partners, known constraints and key stakeholders.
- Roles: Product/business · software architecture · engineering · stakeholders responsible for quality.
- Advance information: Choose materials, data access and participants to fit the research or decision question.
- Overall time needed: 60–120 minutes with prepared participants; missing requirements or technical research are separate.
- Setup: Open the method-specific structure. Fictional examples are for orientation only; keep the blank worksheet separate from actual findings.
Prepare for the work steps
System: Name system and business case
- Use the published Architecture Inception Canvas and record system, team, workshop date and iteration.
- Official canvas, business goals, communication partners, known constraints and key stakeholders.
Goals: Capture context and quality goals
- Context for a greenfield inception
- Official canvas, business goals, communication partners, known constraints and key stakeholders.
Constraints: Record constraints
- Context diagram and quality goals
- Official canvas, business goals, communication partners, known constraints and key stakeholders.
Hypotheses: Record hypotheses and risks
- Traceable constraints
- Official canvas, business goals, communication partners, known constraints and key stakeholders.
Architecture Inception Canvas fields from the published template
Business Case
Describe the business or economic driver.
...
Functional Overview
List the most important functions at high level.
...
Business Context
Show the system as a black box and its communication partners.
...
Organisational Constraints
Record organizational limits on design choices.
...
Quality Goals
Name three top quality goals from key stakeholder view.
...
Technical Constraints
Record technical limits on design choices.
...
Architectural Hypotheses
Record consequential architecture hypotheses and reasons.
...
Technical Challenges & Risks
List known technical challenges and risks.
...
Architecture Inception Canvas (official PDF)
System: Name system and business case
Expected artifact: Context for a greenfield inception
Context for a greenfield inception
Entry:
...
- Is purpose separate from technology?
Goals: Capture context and quality goals
Expected artifact: Context diagram and quality goals
Context diagram and quality goals
Entry:
...
- Are partners and quality expectations concrete?
Constraints: Record constraints
Expected artifact: Traceable constraints
Traceable constraints
Entry:
...
- Is every constraint binding and verifiable?
Hypotheses: Record hypotheses and risks
Expected artifact: Hypotheses and technical challenges
Hypotheses and technical challenges
Entry:
...
- Is a concrete check planned?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/architecture-inception-canvas/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Architecture
Software Architecture Canvas
Instead of Architecture Inception Canvas, when you want to frame an architecture on a compact, shared overview sheet.
Architecture
Risk Storming
Moves architecture context, options, and consequences toward a concrete result through "place the architecture diagram or plan in the center", "set risk categories such as technical, organizational, and external", and "assign an owner and next steps for each top risk".
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Examines how architecture decisions support important quality goals and makes risks and trade-offs visible.
Architecture
Request for Comments
Uses a structured proposal and review process to make non-trivial technical or product changes discussable and decidable.
Architecture
SAAM (Software Architecture Analysis Method)
Uses concrete tasks to show how well an architecture supports use and change.
Architecture
Architecture Communication Canvas
Prepares stakeholders, core messages, and artifacts so architecture communication connects deliberately.
Constraints and origin
LowWorkshop1-2 h
Profile
- Method form
- Canvas
- Participants
- 3-8
- Time
- 1-2 h
- Maturity
- Established
- Origin
- arc42 Community
Next up: Architecture Decision Record