Worked Examples
Catalyst Canvas: End-to-End Sample Workflow
Complete an all-feature retrofit demonstration in Catalyst Canvas.
Catalyst Canvas · How-to Guide
Problem framing, stakeholders, personas, journeys, evidence, assumptions, research, concepts, prototypes, tests, learning, review, and handoffs.
Purpose
This end-to-end workflow demonstrates every documented Catalyst Canvas capability through one fictional resilient-community-retrofit case. The objective is not to prove a real-world conclusion; it is to verify the complete product workflow with controlled data.
Prerequisites
- The current product release
- A new synthetic workspace
- The all-feature CSV and JSON
- No production or private information
- Time to review every checkpoint
Sample data
This article uses a fictional Resilient Community Retrofit Program. The files contain one demonstration row for every documented feature, so each capability can be tested without private or production data.
Download CSV feature examples · Download JSON workspace example
Preview
| # | Feature | Sample action | Expected result | Classification |
|---|---|---|---|---|
| 1 | Project Workspace | create CANVAS-RETROFIT-001 with owner and status | a persistent project | synthetic-demo |
| 2 | Challenge Frame | describe energy, comfort, users, desired change, and boundaries | a concise challenge statement | synthetic-demo |
| 3 | Stakeholder Map | map visitors, staff, facilities, funders, and contractors | a stakeholder network | synthetic-demo |
| 4 | Personas | create an evidence-bounded facilities-manager persona | a persona separating evidence from inference | synthetic-demo |
| 5 | Journey Map | map room booking, comfort complaints, and facilities response | a stage-based journey | synthetic-demo |
The downloadable files include all 18 feature rows.
Procedure
Scenario
A community center is assessing energy, comfort, financing, implementation, evidence, and monitoring needs. Use only the supplied fictional records.
- 1. Project Workspace: create CANVAS-RETROFIT-001 with owner and status. Confirm a persistent project.
- 2. Challenge Frame: describe energy, comfort, users, desired change, and boundaries. Confirm a concise challenge statement.
- 3. Stakeholder Map: map visitors, staff, facilities, funders, and contractors. Confirm a stakeholder network.
- 4. Personas: create an evidence-bounded facilities-manager persona. Confirm a persona separating evidence from inference.
- 5. Journey Map: map room booking, comfort complaints, and facilities response. Confirm a stage-based journey.
- 6. Point of View: synthesize user, need, and insight. Confirm a reviewable POV statement.
- 7. How Might We: ask how to reduce energy without hiding comfort tradeoffs. Confirm bounded design questions.
- 8. Evidence Ledger: add utility bills, observations, and interviews. Confirm source-linked evidence records.
- 9. Assumption Ledger: record that staff will use a dashboard weekly. Confirm an assumption with risk and test.
- 10. Research Plan: plan interviews, meter review, ethics, and outputs. Confirm a governed plan.
- 11. Idea Generation: generate sensor, scheduling, controls, and training concepts. Confirm an idea set linked to needs.
- 12. Concept Selection: score concepts on feasibility, impact, equity, and evidence. Confirm a transparent selection rationale.
- 13. Prototype Plan: define a comfort-and-energy dashboard prototype. Confirm a bounded prototype specification.
- 14. Test Plan: test whether staff can identify an overheating zone. Confirm a task script and success measures.
- 15. Learning Log: record that users misread a comfort score. Confirm a chronological learning entry.
- 16. Review Workflow: request research and accessibility review. Confirm a human review trail.
- 17. Comparison: compare two dashboard concepts using aligned criteria. Confirm a side-by-side evidence view.
- 18. Export and Handoffs: send the chosen concept to Decision Studio. Confirm a portable bundle and receipt.
Save and review
- Save the final workspace under the sample workspace ID.
- Close and reopen it in a clean session.
- Compare every feature result with the sample expected_result field.
- Document unresolved differences and do not hide warnings.
- Export one complete artifact bundle.
- Send one supported handoff to an integration and verify its receipt.
Supported integrations
- Decision Studio
- Knowledge Library
- Catalyst Data
- Research Lab
- Product Support Platform
- Platform Core
Expected output
- a persistent project
- a concise challenge statement
- a stakeholder network
- a persona separating evidence from inference
- a stage-based journey
- a reviewable POV statement
- bounded design questions
- source-linked evidence records
- an assumption with risk and test
- a governed plan
- an idea set linked to needs
- a transparent selection rationale
- a bounded prototype specification
- a task script and success measures
- a chronological learning entry
- a human review trail
- a side-by-side evidence view
- a portable bundle and receipt
- A complete saved workspace
- A portable export
- A validated cross-product handoff receipt
Verification
- Every CSV feature row has a corresponding saved result.
- The JSON workspace ID and product version are preserved.
- The export can be inspected without temporary browser state.
- The receiving product identifies source, destination, schema, artifact, and review state.
- A human reviewer can reproduce or audit the demonstration.
Responsible use
Avoid fabricated personas, extractive research, sensitive-data collection without safeguards, and claims unsupported by evidence.
Replace synthetic data only with information you are authorized to use, after reassessing licensing, privacy, uncertainty, and review obligations.