QControl Brochure Site
To close: Write the Outcome, noting which lens (if any) Mark preferred. · Add wf5 and the mockup to the status list and fix the lens names. · Move it from CYCLES.md to HISTORY.md.
last activity May 11
QControl had strong proof, a real agent incident and a clear architecture, but no product page for security leaders, and the best way to tell its story was unknown.
Five one-page brochure wireframes tell the same product five ways: the nine-second incident, the blind spot, the architecture, the cost of trust, and a competitor's layout. A mockup followed.
Documents
With file names, on their own page →Start here
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
Five rough one-page brochures, each built around a different way into the same product.
Five ways to tell one story · came from Mark Parsonopen →
- A higher-fidelity mockup of the whole product site followed the five rough pages. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Five rough one-page brochures, each built around a different way into the same product.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Built the five lenses
The record names no one; the wireframes and the mockup were committed by Mark Parson (git), so the credit is matched from authorship.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 1
The full record 0 decisions · 0 key-change entries · 298 words · 1 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c14 →