Leadership beyond the prompt
Agree on the outcome.
Then delegate.
A Chief Operating Agent needs a clear definition of success. The CEO still owns the choices behind it.
When dot and I worked through the objectives for a diversified frontier firm, the conversation moved from broad ambitions to what would actually count as progress. We kept refining the language, the evidence and what could realistically fit.
I’m the CEO. dot is the Chief Operating Agent I’m working with as we design the firm. I still own the priorities and tradeoffs. Let’s be real: a polished plan leaves somebody responsible for the result.
What the firm needs to prove
These are the broad objective themes we can share. The actual key results and monthly commitments remain private.
Business viability
Prove the firm can earn income.
Reliable delegation
Build an agent team that reliably finishes delegated work.
Customer value
Prove a repeatable customer offer for a business line.
Beyond the Chat Box
The handoff starts in the planning conversation.
An unclear outcome becomes everybody’s interpretation of the job.
In our discussion, the useful back-and-forth was about what the words would require us to demonstrate. A broad ambition needed evidence. A promising draft needed a reality check before it could become a commitment.
That is a leadership job. The agent can help expose an assumption or make a proposal easier to question. I have to decide whether the result matters, whether the commitment fits and what evidence I will accept.
Clearer instructions help the next handoff, too. The person or agent receiving the work should be able to understand the outcome without reconstructing the whole conversation.
Give each kind of statement its job.
We used the OKR framework described in John Doerr’s Measure What Matters as a reference. Objectives and Key Results give direction and progress different jobs.
Objective
The meaningful change we want to achieve. It explains why the work deserves attention.
Key result
A measurable, verifiable result within a defined review period. It should be challenging and realistic.
Monthly commitment
The work we choose to carry out in support of the result, with an owner and capacity to do it.
The monthly commitments are our way of organizing execution. Finishing an activity does not by itself establish that the key result was achieved.
Make the handoff answerable.
For a delegated assignment, I want the brief to make responsibility visible. These are generic questions for the working agreement, not our private key results.
- Outcome
- What must be true when the work is finished?
- Owner
- Who is responsible for finishing it, and who receives the result?
- Authority
- What may the agent do, and which decision needs to come back?
- Evidence
- What can the recipient inspect before accepting the work?
- Blocker
- If it cannot finish, what is missing and who can resolve it?
Monthly review should change the next decision.
Compare the evidence.
Return to the agreed key results. Check what was measured, what was delivered and what the recipient accepted. Keep unfinished work visible.
Decide what follows.
Continue work that is producing the intended result. Revise assumptions, resolve blockers or reduce the next commitments when the evidence calls for it.
Keep the original success criteria visible when reviewing progress. A missed result can teach us something without being relabeled as a success.
Use the next assignment
as the test.
Write the outcome, name the recipient and describe acceptable evidence before opening another tool. We are still designing and testing this firm; dependable agent operations and a working business have to be demonstrated.
The question
At the next review, what would you need to see before calling the delegated work done?
Ciao, Jason
Framework reference: What Matters: Objectives and Key Results. This edition applies the published framework to our own planning conversation. It does not imply personal advice or endorsement from John Doerr.