A chief of staff in your pocket
Of the three scenarios in this workshop, this is the one every leader in the room can start this quarter. A personal agent that lives in WhatsApp, reads what you let it read, and handles the connective tissue of a senior job: triage, preparation, capture and follow-through. It is also the lowest-risk way for a leader to learn, personally, what agents can and cannot do before any organisation-wide decision has to be made.
A day with it
The value is not one dramatic capability. It is the steady removal of small coordination work, hour after hour, in the channel you already live in.
- Morning triage: before you open your inbox, the agent has sorted it into three piles: needs-you, drafted-for-you, and noise. You read the first pile, review and release the second, and never see the third.
- Meeting preparation: for each meeting on today's calendar, a one-page prep: who is in the room, what was agreed last time, what is still open, and what you said you would bring.
- Capture on the move: a voice note recorded in the car becomes a structured brief by the time you park: context, decision needed, options, next steps, ready to forward or file.
- Follow-through: the agent keeps a ledger of promises made, yours and other people's, and nags. "You told the finance lead you would respond by Thursday" is a message you get on Wednesday.
What it needs, and what that means
To do the job described above, the agent needs real access: your email, your calendar, your files, and a messaging channel such as WhatsApp to reach you. That access is precisely why the setup must be deliberate. A chief of staff is useful because it sees everything; that is also the risk to manage.
| What it needs | Why it needs it | What that obliges you to decide |
|---|---|---|
| Email access | Triage, drafting, promise tracking | Read-only first; sending rights are a separate, later grant |
| Calendar access | Meeting preps, scheduling awareness | Whose calendars it may see beyond your own |
| File access | Context for briefs and preparation | Which folders are in scope, which are excluded |
| Messaging channel | The interface you actually use | Which conversations, if any, it may read versus only write to you |
Behind those grants sit three setup decisions that should never be defaults. Use your own API key or a governed company instance, not a free consumer account, so usage is attributable and terms are known. Know what data leaves the device, and to which model provider it goes, before the first message is processed. And decide where the agent runs: your own instance, or one your organisation governs.
Starting safely as an individual
The staircase for an individual leader is short and conservative. Each step earns the next.
- Start read-only. Triage, preps and briefs need no sending rights at all. Weeks of value are available before the agent can act on anything.
- Add sending rights only with per-message approval. The agent drafts; you release. Autonomy over outbound messages is a later decision, if it is ever taken.
- Keep client-confidential material out until your organisation has a policy that covers it. Your own diary and drafts are yours to risk; a client's data is not.
- Prefer a governed setup over a laptop experiment. A personal instance running unmanaged on a laptop is how shadow IT starts. A governed instance gives you the same learning with an audit trail.
Why leaders should go first, personally
The organisational decisions ahead, which workflows to automate, what autonomy to grant, what governance to require, will be made by people in this room. A leader who has lived with an agent for a quarter makes those calls from experience: they know where it saved an hour, where it confidently got something wrong, and what supervision actually feels like. A leader who has not is deciding from vendor slides. The personal chief of staff is not just a productivity tool; it is the cheapest management education on agents available, and it is available now.
Related
BASIC · Agentic AI Workshop · aiagent.research.my