work assistant · roadmap
What it can already do, what's being built, and what's coming. Honest status, no dates, because the priorities shift with what you actually need.
Clear the backlog one thread at a time, flag what's genuinely exploding today, and file the no-action dross. The core of it.
A mention or assignment is treated as a real action to close on the row, not an email to bury. (This started as a bug one of you would have hit.)
Ask what your assistant has been doing and get a clean summary: what the inbox passes did, drafts waiting, actions still open.
One home for the pack, updates, and a key-protected way for your assistant to report problems straight to Andre.
Go past "don't bury them". Your mentions and assignments become a to-do list your assistant keeps on top of and chases, so nothing on a row goes quietly stale.
The pattern that saves the most time. An email comes in that needs a meeting: it spots it, checks the calendar, finds a slot that works for everyone, and all you do is say yes or no. Same idea for the jobs that come round every project, each one taught once then driven with a nod.
Before any meeting, a rock-solid one-pager: every open thread with that person from your mail and the trackers, what you owe, what they owe. The version on the examples page works today; this makes it solid enough to walk in cold on.
A shared team space where your assistants hand work between each other. Big one, no rush, only when the basics are bedded in.