I’d rather play with the plan than read it
I think more clearly with an agent when I can change something and see what happens.
Planning with an agent through a chat interface usually ends in a document: phases, file lists, open questions, and a request for a yes. I skim it and say yes. What each of us meant only shows up later, in the diff.
Now I ask for a few versions of the idea I can try. A prototype I can click through, a behavior I can change. Rough is fine. It only has to be real enough to react to.
Trying them changes how I decide. I notice something I hadn’t thought to ask about, combine parts of two versions, or want to try something else entirely. Often that is how I find out what I wanted in the first place.
Bret Victor’s Media for Thinking the Unthinkable gets at this: seeing a system respond as we change it helps us reason about it. We can inspect what happens instead of keeping the whole thing running in our heads.
Or take a plan for a busy day. Give the writing another half-hour and something else no longer fits, even though there is free time left. Move the print pickup and watch the afternoon open up. Adjusting these sliders could be my reply to the agent, with the consequences visible before I settle on the values.
| Time | Plan |
|---|---|
| 09:00–09:30 | Inbox |
| 09:30–10:30 | Write note |
| 10:30–11:00 | Team call |
| 11:00–12:30 | Edit photos |
| 12:30–13:15 | Lunch |
| 13:15–13:45 | Admin |
| 13:45–14:00 | Free |
| 14:00–14:30 | Travel out |
| 14:30–15:00 | Print pickup |
| 15:00–15:30 | Travel back |
| 15:30–17:00 | Bind maquette |
| 17:00–18:00 | Free |
All five work tasks fit, with 75 minutes free. Giving the writing 90 minutes leaves no uninterrupted slot for binding the maquette. Moving the pickup to 13:45 makes everything fit again.
In a purely textual chat, every small experiment is another message, wait, and explanation to interpret. I’d like the agent to give me something I can think with, where changing my mind is as easy as moving a control and seeing what happens.