An admin assistant posted this week about her job supporting a regional president. Eight years in. The actual role is fine. The problem is the other hundred people in the building, who come to her for every little thing: where the supply room is, how to clear a printer jam, who's at the door. She and one colleague have written the idiot-proof emails. Nobody reads them. The more they systematize, the more people seem to route around it and just tap her on the shoulder.
She has become the system. The single human lookup table for a hundred people who never learned to look anything up. That is an architecture problem, and architecture problems have architecture fixes.
Here's the reframe this issue runs on: every recurring interruption is a question that should have been answered by something other than you. Build the thing that answers it, and the interruption stops arriving at your desk. AI has turned building that thing into a job of minutes.
Subscribe to The Dispatch and the rest of this issue unlocks right here, along with the full archive. One email every Tuesday, about 8 minutes, built for admin professionals. No spam, unsubscribe anytime.
Already subscribed on this device? This unlocks automatically.
One honest note up front, same as always: a system will not fix a boss who won't back you up, and it will not make rude people polite. What a system does change is the conversation. "I'm drowning" is a feeling, and feelings get waved off. "Here are the 12 questions I answered 40 times last month, and here's the self-serve page I built so I don't have to" is a case. You stay the editor and the operator. AI builds the scaffolding fast.
You keep getting interrupted because the answer lives in your head, so your head is the only place to get it. Move the answer somewhere else and the interruption has somewhere else to go.
You don't need new software. Open the surface you already have: a OneNote or Copilot Notebook page, a pinned shared doc, a Teams or SharePoint wiki page. Title it something people will actually click, like "Office Quick Answers" or "Read This First." That single page is where every repeat question goes to get answered forever.
Skip writing it from scratch. You already have the raw material, buried in your sent folder and your chats, in the form of the same reply you've typed forty times. This issue is about mining that, letting AI shape it into a page, and pointing people at the page instead of at you.
Start it today with your five most-asked questions. It grows itself from there.
You can't fix interruptions you can't see. Spend one week jotting every "quick question" on a sticky, OR let AI mine the pattern out of what you've already written:
Here are the last 30 short replies I sent to coworkers who asked me quick questions: [paste a batch of your short sent emails / chat replies]. Group them into recurring question types. For each type, tell me: (1) the question in plain words, (2) how many times it seems to come up, and (3) whether it could be answered by a written instruction instead of by me. Rank them by how often they recur. Do not invent questions I didn't include.
You're looking for the vital few: the handful of questions that generate most of the taps on your shoulder.
Once you know the repeat offenders, put the answers in plain, findable language:
Turn these recurring workplace questions into a short, scannable "Quick Answers" page for coworkers to self-serve. For each: a clear question as a heading, then a 1-3 sentence answer in plain, friendly language. Keep it skimmable, no jargon, easy for someone in a hurry. Here are the questions and the answers as I currently give them: [paste your Q&A]. Keep every fact exactly as I've written it. Do not add steps or details I didn't provide.
Now the printer-jam answer, the conference-room-booking steps, and the where-is-everything map live on a page with a URL, not in your memory.
The page only saves you if you stop hand-writing the redirect. Pointing people to it should take one click:
Write me 4 short, warm, non-passive-aggressive replies I can reuse when a coworker asks me something that's already answered on our Quick Answers page. They should point the person to the page and still sound helpful, not annoyed. Vary them from a one-liner to a slightly warmer version for someone senior. End each with the placeholder [LINK].
Save these as text shortcuts or quick replies. "Great q! It's all on the Quick Answers page here: [LINK] 🙂" costs you three seconds instead of three minutes.
Some asks are legitimate work: event help, bookings, materials. Those should arrive as a list you triage, not an ambush mid-task:
Help me design a simple intake for work requests so people stop interrupting me in person and instead submit through one channel. Suggest: (1) the 4-6 fields the form should ask for so I get what I need up front, (2) a one-line "how to request my help" blurb I can pin in Teams/email, and (3) a short, kind message I can send when someone shoulder-taps me instead, redirecting them to the form without sounding cold.
A Microsoft Form, a shared list, even a dedicated email label. The point is that requests land somewhere you check on your schedule, with the context already filled in, instead of interrupting the deep work only you can do.
All four moves do the same thing. They shift the low-value lookups off your shoulder and onto a page, so the high-value work gets your attention back: the judgment, the coordination, the things an executive actually pays for. You stay just as available to the people who genuinely need you. That's the whole game. Stop being the lookup table, start being the operator.
Everything above, already built. A fill-in Quick Answers page template with a 12-question starter checklist, the four deflection replies as swipe copy, the six-field request intake with a pin blurb, all four prompts, and a one-week rollout plan. About 90 minutes of work, laid out day by day.
Download the kit →1. You are not the only human help desk this week. In one r/ExecutiveAssistants thread, an admin described spending an entire day folding 250 letters while a hundred coworkers pinged her for things they could Google. The comments were a wall of "same." Read interruptions like that as a design failure of the office, then design around them.
2. A "vent session" thread became a systems checklist. A "Worst Day as an EA" thread pulled dozens of stories, and buried in the pile was the same root cause over and over: no self-serve layer, no triage, no written process, so every gap becomes a tap on the EA's shoulder. Read your own bad days that way. Each recurring fire is a page you haven't built yet.
3. The tools quietly got good at this. Copilot Notebooks rolled out to licensed Microsoft 365 Copilot users this month, and since July you've been able to @mention the Word and Excel agents directly inside Copilot chat. Turning a messy pile of "here's how we do things" notes into a clean self-serve page is now a five-minute prompt. More free templates and guides that pair with these prompts: browse the library.
Paste a batch of your last quick-reply emails into your AI tool and let it show you which questions you've quietly become the database for. Most people are startled by how few questions cause most of the interruptions, which is exactly why a one-page fix works.
Then hit reply and tell me the single question you answer the most. I'm collecting the greatest hits. I read every reply.
Master your tools. Own your work.
— Kristy
Digital Zena subsidiary of Fusion AI Consulting LLC
This is exactly what the founding cohort is built for: six weeks, live, small, for admin pros going from digitally functional to digitally fluent. The kind of fluency that turns a recurring manual grind into a system that runs without you. You'll build a working automation you keep, deployed in your real job. Founding seats are limited and priced for the people who get in early.
Join the waitlist →