Handled one at a time, each of these is a minor convenience: a faster inbox, a tidier calendar. Handled as a set, with the same judgement applied to all of them, they start to add up to something a leader would recognise from a very different kind of hire.
Where the friction is
The day starts with an inbox that has to be triaged before anything else can happen, whatever else is on. A meeting produces a decision that nobody writes down, so the same discussion happens again in three weeks, with slightly different people in the room. Calendar time gets given away by default, because declining takes longer than accepting and there is never a good moment to do the harder thing. A follow-up gets promised out loud and never sent, because the moment passed and something else arrived first. None of this is a crisis. It is just where the hours go.
Where this usually goes wrong
The quiet failure in this category is scope creep after a good week. A workflow that drafts routine replies well earns trust with less routine ones, until something sensitive goes out sounding like a person who was not paying attention. The protection is a line drawn up front, in writing: the threads that never touch drafting at all. With that line held, one near miss never poisons trust in the routine drafts the workflow keeps getting right.
What gets built
Email triage and drafting
The work it replaces. A leader opens the inbox and reads everything in arrival order, regardless of what needs attention first. Replies get drafted from scratch even when the same three answers cover most of what arrives.
What gets built. Incoming email is classified by type and urgency as it lands. Routine requests get a drafted reply waiting for approval; anything time-sensitive is flagged to the top. The workflow learns the leader's usual answers to recurring questions and drafts in that voice (a typical stack: the existing email platform, a workflow tool, a language model for classification and drafting).
The governance built in. Nothing sends without approval. Sensitive threads, anything involving a complaint, a legal matter or a personnel issue, is excluded from drafting entirely and flagged for direct handling.
What gets measured. Time to inbox zero against baseline, the share of drafts sent with no edits, and how many items still need the leader's own words.
Meeting-summary-to-actions
The work it replaces. A meeting ends, notes exist somewhere, and the actions inside them either get typed up hours later from memory or never get typed up at all.
What gets built. The meeting is recorded or transcribed, and the workflow extracts decisions, owners and dates directly from what was said, then creates the tasks in whatever system the team already tracks work in. A summary goes to attendees within minutes of the meeting ending.
The governance built in. A person reviews the extracted actions before they are assigned; the workflow proposes, it does not assign unsupervised. Recordings and transcripts are stored under the same access rules as the meeting itself.
What gets measured. Time between meeting end and actions logged, the share of actions that needed correction, and whether the same decision is still being re-litigated in a later meeting.
Add enough of these, governed the same way, and they stop behaving like separate tools. A system that filters what reaches you, drafts what can be drafted, remembers what was promised and flags what still needs a decision is doing the job a chief of staff does, at whatever scale a business can justify one. The workflows above are how that gets built: one at a time, each one governed on its own, never running ahead of the judgement that controls it.
Re: proposal timing
Invoice query, Hendersons
Complaint: delivery delay
Excluded from drafting entirely
Confirm Q3 pricing with Sam
Send revised scope to Alex
Wednesday, 7:42am