Call My Name
Next: The team's first pass on the names, then the shared session; then the rename and the records updated in one change.
Two new things need names, and a name decides what customers think they are.
A brief with the candidates placed by the model each attaches to, the agent's proposal, and a one-hour agenda for deciding as a team.
Documents
With file names, on their own page →Start here
Documents
Pages
- /cycles/design/sketches/c0-naming-map (local dev)
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
Every candidate name sits next to the idea it attaches to in a customer's head.
The naming map · came from The Qpoint teamopen →
- One document to read before the session, with the agent's pick argued and the alternatives kept. 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.
c0-D2 The names are decided out in the open in a shared team session, after a first pass; the brief places the suggestions by the mental model each attaches to. — The Qpoint team
Every candidate name sits next to the idea it attaches to in a customer's head.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked for the names before the code
Started the app's repo with a naming cycle; framed it by the customer's cognitive map and the job they undertake; named the two verbs the test rests on: the control plane is something you connect to, qcontrol is the thing you deploy.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 1
The full record 2 decisions · 2 key-change entries · 520 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 c0 →