CSUX Blueprint Builder
Drop your research and notes. Get back a journey map that makes the argument for you, grounded in evidence and built for leadership decisions.
Readiness
Two things I need to know before we start.
1 of 2
Who needs to see this?
Name the person or role who'll act on what this reveals.
2 of 2
What do you need this to do?
Journey maps are best at one specific thing. Make sure this is the right tool.
Both answered. I'll use your answers to calibrate what I ask for next.
A name, a program, and an owner. Takes 15 seconds.
All fields are required to continue.
Step 1 — Load your sources in Quick Coach
Open Blueprint Kit Coach, attach your research files or focus your Space, and ask: “Summarize my research for a [your program] journey map. Give me one structured document I can paste into the builder.” Then paste what it gives you into the box below.
Open Blueprint Kit Coach ↗Or upload clean text files directly
Drop files anywhere, or browse
Text, Markdown, CSV, JSON · up to 5MB each
Your sources
Nothing yet. Drop a file to start.
Sources live with this map only — each new map starts fresh.
Reading your files...
These become the evidence woven through your blueprint. Tap any row to review what I pulled.
Shape
I read your sources and shaped a blueprint that fits your evidence. Review it, then build — or adjust anything first.
A standard, five-section map, centered on your strongest moment and written for one decision-maker.
Standard map — five sections (Problem, Scale, Journey, Evidence, Takeaway)
You have strong data for the core journey. Your evidence is sharp enough to stand on its own.
The routing decision point
4 of your data points cluster here. This is where the experience breaks most visibly.
Your decision-maker
After reading, they should be able to decide whether to invest in the redesign.
The shape of your map
Worth weighing before you build
Shaping your map...
Downloads a .zip with your blueprint (HTML + CSS + JS) and an /evidence/ folder with your source files. Open index.html in any browser to present.
What changed between versions. Each version represents a design or architecture milestone, not a calendar release.