Integrations & Teams
The Integrations page was a list of what might connect someday, and the Teams page had no teams. Neither page matched its name.
After eleven rounds of ideas, Integrations shipped in the product as a catalog grouped by what you want to do, with connected tools showing live numbers. Teams moved to its own cycle.
Documents
With file names, on their own page →Start here
Documents
Pages
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
The product's Integrations page is now a catalog in five groups, where connected tools show live numbers and the rest offer one add button.
Integrations, grouped by job · came from Mark Parsonopen →
- 2
Both catalogs now use the same five headings: sources, security and observability, notifications, fixing things, and evidence.
Five groups, in plain jobs
- The ideas moved from an honest directory, through job-first and setup-first versions, to compact capability cards. Early → final
- An integration card and a logo part joined the shared library, with twenty third-party logos. In words
- The Teams page got research and four concepts, then moved to c67 to be refined and shipped. New in this cycle
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.
The product's Integrations page is now a catalog in five groups, where connected tools show live numbers and the rest offer one add button.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Both catalogs now use the same five headings: sources, security and observability, notifications, fixing things, and evidence.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked for creativity, framed by jobs to be done
Commissioned the pass on both pages, asked for comparable screens from other products and for the most important jobs first, as input to the design team's own work.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 12
The full record 0 decisions · 10 key-change entries · 974 words · 11 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 c61 →