Micro Problems
Next: Review the waiting candidate problems and the two advisor-driven standing changes, then decide on the product-input plan.
market-analyst was built to size up a market, but it now mostly feeds design, and briefs were written by hand because calls weren't sorted by the user's problem.
Fifteen user problems now sit in a registry, each with the question it asks of the product. Calls tag them, the site leads with them, and design cycles cite them.
Documents
With file names, on their own page →Start here
Documents
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
Fifteen problems each pair a user's pain with the question they'd ask the product, and the people who feel it.
A registry of user problems · came from Samuel Curry and Mark Parsonopen →
- 2
The October product sessions were read, and their decisions became a design cycle and were written into four others.
Product sessions feed design directly · came from Mark Peterson, Rob Genova and others
- The dashboard opens on the problem space; the sales numbers moved one row down, and nothing was removed. In words
- Reading a call now tags the known problems and proposes new ones for a person to promote. In words
- Two problems became recurring on an outside voice that is also helping design the product, and both are flagged for review. 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.
“I've been fighting for better AI governance and not technical, administrative controls, and how do we AI for everyone, how do I put a life cycle in place for that without squashing innovation.”
market-analyst /calls/d232f12c… (local)market-analyst-c12-D2 Use case (supply-side hypothesis) → micro problem (demand-side user question), many-to-many; the registry holds the problem, never the solution. — Mark Parson
market-analyst-c12-D3 Two forms per problem: a pain statement (canonical) and a product-facing question, required to promote. — Mark Parson
Fifteen problems each pair a user's pain with the question they'd ask the product, and the people who feel it.
“We off boarded our interns... 5 laptops that went out. They came back... they'll be offline for a while... they wouldn't get an update.”
market-analyst /calls/5c8785e2… (local)market-analyst-c12-D6 In decision briefs, later statements win over workshopping. — Mark Parson
The October product sessions were read, and their decisions became a design cycle and were written into four others.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Brought the intern laptops that went offline, and the rulings design built on
Cited: his Oct 21 story of offboarded intern laptops missing updates moved fleet-scale compliance to recurring. The record also names his product sessions (Oct 12–23) as the source of the decisions written into design c114, c116, c118 and c121.
“We off boarded our interns... 5 laptops that went out. They came back... they'll be offline for a while... they wouldn't get an update.” first-hand
His relief at self-hosting made transcript governance a recurring problem
Cited: the record says the extractor tagged Phil Chen's relief at the self-hosted control plane (Tiled demo, Aug 25) to session-transcript governance, making it recurring alongside Moto, and flags it for Mark's review.
“That solves a huge problem... that could be a killer right there.” first-hand
His governance-gap line anchors the agent-identity problem
Cited by name: the record re-pinned "Sam Curry's governance-gap line" to agent-identity scoped access by hand. Matched: the observation is d232f12c#1 by its curated reference.
Opened the product sessions to the team so they could be read
Cited: his Mon/Wed/Fri "Qpoint Product" series was hidden from the API as private; Rob set it to Organization, which let Oct 12, 14 and 19 through.
Redefined the tool as a design tool first
Cited: his 2026-09-21 prompt reframed market-analyst as the source of truth for the problem space; he confirmed the four unlocking decisions, reviewed the fifteen drafted problems, and set the rule that later statements win over workshopping.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 4 decisions · 11 key-change entries · 2,765 words · 0 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 c12 →