Keep the person in view when the conversation changes
A short project foundation helps a small task retain its purpose.
Getting startedAbout 2 min read
A small task can lose the larger purpose
A new coding conversation may begin with a button that needs fixing. The task describes the broken action precisely, but says little about the person using it. A technically reasonable repair can then bring unfamiliar labels or unnecessary choices into the screen.
In My Next Step, someone may be confident about their life experience while feeling uncertain with technology. A control that asks them to manage parsing or configuration can move the difficulty from the software onto them.
Keep a small foundation close to the work
J_OS now makes the product’s purpose, intended users, their needs and important decisions explicit. A fresh conversation can begin with that foundation alongside the current task, rather than having to infer the audience from the source code.
The note should be concrete enough to affect a decision. “Make it easy to use” says less than “the person should be able to attach a document without understanding file processing”. Keep it current when your understanding changes.
Look for the decision it changes
After a change, ask the agent to explain one design choice in relation to the intended person. Then try the experience yourself. Reading a foundation is a starting point; it does not establish that the result fits.
The point is to keep someone visible while attention moves through smaller tasks. A short note is useful only if it helps that happen.