When the agent executes, our judgment matters more
In a conversation with coworkers, I asked how we felt about AI agents now that they could handle so many tasks. One teammate admitted feeling useless. That remark made me pause.
I understand where that feeling comes from. When part of what used to take sustained effort starts getting done much faster, it is natural to wonder where our contribution goes. My answer was to share how I was experiencing that shift myself.
For me, the work starts by understanding a need, imagining a solution, and deciding what has to happen for it to be genuinely useful. The agent helps me materialize it; judgment and accountability remain part of my work.
Designing before asking it to build
This way of organizing grew out of my day job at an international organization. I wanted to run multiple projects simultaneously without relying on remembering every conversation or re-explaining everything from scratch.
In my practice, roughly half of the initial effort goes into talking things through, exploring, and clarifying. That is a personal orientation, not a rigid ratio every project must follow.
I think alongside the agent, cross-check sources, and try to close open questions that affect the solution. If understanding data, inspecting a table, or verifying how something behaves is needed, that exploration is part of the design. Some questions can only be answered by testing; what matters is recognizing them and knowing what each test is meant to clarify.
Context needs a place to continue
A good conversation helps a lot, yet I do not want a project's memory trapped inside a chat window. That is why I organize work into four spaces, each with a clear responsibility:
- 00-specs/ Context, sources, needs, decisions, and acceptance criteria.
- 01-development/ Work that materializes the solution.
- 02-exploration/ Experiments, analysis, and trials.
- 03-results/ Deliverables prepared for review or use.
In specs, I gather the context needed to think clearly: requests, emails, documents, and meeting notes converted to Markdown, alongside specifications. Every source keeps its origin and date, and anything that could not be converted reliably is flagged for review.
I separate what we received from what we interpreted, proposals from confirmed decisions, and experiments from verified results. An index helps locate the relevant document. The active specification should state what we are trying to solve, under what constraints, and how we will recognize that it works.
Recording an attempt that did not work can also be valuable, as long as it states what was tried and what we learned—preventing us from repeating mistakes out of forgetfulness or treating a discarded idea as an active instruction.
People are part of the context too
When a solution involves many people, understanding the deliverable is not enough. It also matters who needs what, who decides, and what agreements exist across teams.
I find it helpful to keep concise notes on collaborators with relevant professional information: role, responsibilities, expressed needs, agreements, and confirmed working preferences. Those notes require sources and updates; they are not personality profiles.
For example, if I say "Ana asked to review this" and Ana is the marketing analyst on that project, the agent can check her note and recall what she needs and what was agreed. Ana is a hypothetical example here. If a name is ambiguous or information is missing, the agent should ask.
On larger teams, the agent can help connect needs, spot tensions, and prepare sharper questions. Agreements are still confirmed with people. A new request does not automatically become an approved decision.
One task, one conversation. One project, one shared memory.
I keep conversations scoped coherently: one to understand a need, another to build a piece, another to review a result. Each conversation receives the relevant context and writes back its decisions, findings, and open questions to the project.
I neither open a separate chat for every tiny action nor try to force everything into one endless thread. Before switching tasks, I leave what is needed so the next conversation can pick up the thread cleanly.
A large context window does not guarantee accurate understanding. Selecting, structuring, and maintaining information remains human work. My goal is for continuity to rest on readable documents and shared criteria.
A guide to try this way of starting
I am sharing a generalized version of my kickoff guide. It works as a prompt or a reusable instruction: it preserves the initial interview, waits for confirmation, and prepares the four folders. You can copy, download, and adapt it to your setup.
It is designed for starting a conversation with your agent. If it has authorized access to your files, it can create the structure; otherwise it should offer a simple alternative. The guide contains no internal procedures or confidential information from my workplace.
Read the full guide
From work to personal life
That order started in my professional projects and later carried over into my personal life. I wanted to bring to my own ideas, memories, and information the same care I was putting into external work.
You can see it in my personal logbook, where I share a simple structure to start organizing your own information.
What excites me to share is that possibility: devoting our judgment to understanding and designing, while leaning on agents to explore and build with greater continuity. If this way of working resonates with what your team is navigating, let's talk.