1 min lesson
Communicating to a fast, technical org
Show why this lesson detail matters: "The cursorAngle is explicit: a small, talent-dense team moving extremely fast."
Step 1 of 4
At Cursor the readout competes with shipping. If your insight can't be absorbed in the time it takes to read a Slack thread, it loses to the next PR.
The cursorAngle is explicit: a small, talent-dense team moving extremely fast. Nobody is sitting through your forty-slide deck. The format itself is part of the craft and the default of a beautiful longform report is often the wrong call here.
Learn more
Full explanation
Slack TL;DR - the most-used research artifact at a fast org
RESEARCH: Why senior devs stall on Agent (n=9 interviews + tab-adoption logs) Bottom line: discoverability, not capability, is gating Agent adoption. 7 of 9 never found the Agent panel unprompted; all 7 expected a keyboard entry. Recommend: surface Agent on the keyboard path devs already use (Cmd-K), test in a flag. Confidence: high - interviews + logs agree. Full writeup + clips in thread ↓
Match the artifact to the decision at stake, not to how much work you did. A throwaway usability read on a button does not earn a deck; a quarter-shaping strategy study might.
Fast read, one decision.
Use for: quick evaluative reads, hypothesis checks.
Five lines, bottom-line-first, link to depth.
A few insights, a clear ask.
Use for: a feature decision a small group owns.
Skimmable, decision-shaped, clips embedded.
Strategy or contested calls.
Use for: roadmap tradeoffs needing buy-in.
Run it as a working session, not a lecture.