Give Memory a Job Before You Store Anything
Define an agent memory by the future job it must support, not by what was easy to capture.
The memory design move: start with the job, not the storage layer. Jobs to Be Done asks what progress a person is trying to make. For agent memory, use the same lens: what future job should this remembered fact help the agent perform? That job might be personalization, continuity, decision recall, exception handling, or risk detection. If you cannot name the job, the memory probably belongs in a transcript, not in durable memory. Job before detail The same detail can be useful or useless depending on the job. "Prefers short updates" matters if the agent drafts stakeholder notes. It does…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in