02 · How I work · The Design-Research Framework
How the work moves.
Teams skip research because it looks slow, then decide on guesswork. I wrote this down in 2011 so the research never stops. Now agents keep it running.
01 · The problem space
Where the tension lives.
Every project starts where three things pull against each other: what people want and need, the business’s rules and objectives, and what the technology can do. Economics and governance frame all three. Strategy sits where they overlap.
02 · The active space
Three loops, each folding into the next.
Direct and Define belong to product. Discover and Design belong to content and design. Develop and Deploy belong to engineering. Each loop starts with a person on the left and comes back to the same handle when it’s done, so a person decides before anything moves on. Where two loops overlap, the teams work in the same space at the same time.
03 · The well-informed space · WĪS
Every cycle adds to it.
Problem articulations, multi-sensory artifacts, observations, scenarios and user journeys, KPI reporting against ROI, recommendations and proposals. It feeds inspiration back into the loops, and today it doubles as memory an agent can browse and keep current.
It was never a line
Perform in the storm.
Process diagrams put this on a straight line. It never is, and it’s a disservice to practitioners to say it should be easy. Drawn on its own, the forward path is a jagged wave. The aim isn’t to calm the chaos; it’s to build the fortitude to do good work inside it.
Six touchpoints
Where a person decides, and where teams work together.
For each one: what crosses, who’s responsible, the skills, deliverables, workshops and methods, and what agents do. Written one at a time, here.
At every crossover · working with AI
A person makes the call.
Anthropic’s 4Ds, delegation, description, discernment and diligence, sit at each handle. Agents run the loops. The well-informed space is their memory.
For your team
Research that keeps running alongside delivery. Agents do the legwork, and your people make the calls.
Methods, coming one at a time
What grows from here.
- Setting the strapsThe bounds of the system: context, rules, tools, memory and checks. Context engineering lives here.Coming
- The leashHow much autonomy an agent gets: short leash, loose leash, off leash, and how you call it back.Coming
- The six Ds, one loop at a timeDirect and Define, Discover and Design, Develop and Deploy, each with its deliverables.Coming
- The well-informed spaceWhat every cycle leaves behind, kept current so people and agents can build on it.Coming
- At the crossoverDelegation, description, discernment and diligence: where a person makes the call.Coming
Want to see how this would run on your team?