The executive assistant leaders call when the infrastructure beneath them needs to match the size of their ambition.
To build the operational infrastructure that governs each layer of an executive’s ecosystem.
Email me directly or use the scheduling link. I respond same day.
melissahilaryjohnson@gmail.comTap any case study or sample to add it to your request.
Your details, the role, and one line on what you are assessing.
Once it is signed and returned, the work reaches you within 48 hours.
Registro de cada decisión interfuncional tomada durante el tercer trimestre en la organización LATAM. Quién propuso, quién disintió, qué se decidió, y cuál fue el resultado 90 días después. La atribución es el punto central. Un instrumento de rendición de cuentas que deja claro quién tomó qué decisión y con qué información.
Documento de alineación previo al lanzamiento que obligó a Producto, Legal, Finanzas y Ventas a comprometerse con una posición única antes de salir al mercado. Incluye el registro de qué área retrasó el lanzamiento y por qué. La claridad forzada como herramienta de ejecución.
Documento interno breve que define cuándo y cómo escalar algo a la oficina del CEO. No es un sistema de filtrado. Es lo contrario. Les dijo a los VPs: "tráeme estas cinco cosas temprano y te facilito el trabajo." Las solicitudes entrantes aumentaron, no disminuyeron. La accesibilidad como ventaja operativa.
Portafolio de fin de año con los problemas interfuncionales que otros líderes me trajeron y sus resoluciones, organizados por área: Producto, Ingeniería, Finanzas y Comercial. El volumen es la evidencia. No es un resumen de logros. Es un registro de trabajo.
Un tablero semanal de una sola página que combina economía del producto, pipeline comercial y salud operativa en una sola vista, la que el CEO realmente abría. Incluye el registro de acciones: qué decisiones se activaron a partir de qué señales. La visibilidad integrada que genera acción es lo que la mayoría de los candidatos finge con una captura de pantalla de Looker.
Three phases, Listen, Trust, Own, each with milestones, deliverables, and a built-in check-in structure. 12 to 15 pages. The document I hand an executive on Day 1 so Day 90 isn't a surprise.
End-to-end executive travel itinerary across multiple countries. Flights, ground transport, hotels, visa requirements, local contacts, and emergency protocols. Everything in one doc.
The handoff document I built when transitioning out of a principal relationship. Every system, preference, relationship context, and open loop documented so the next person doesn't lose 90 days figuring out how the office runs.
One page. Signal over noise. Business health, decisions needed this week, and what I'm watching. Written so the CEO can read it in under 10 minutes and act on it immediately.
The living doc that tracks every relationship that matters to the executive: board members, investors, key partners, and talent, with last contact, context, and what's needed next.
The complete pre-board checklist. Materials coordination, pre-reads, attendee logistics, exec prep sessions, and post-meeting action log. Nothing left to chance.
The complete preferences doc. Communication style, meeting structure, travel requirements, working hours, dietary needs, and non-negotiables. Built so any operator can support this principal without asking twice.
End-to-end production document for a company all-hands. Run of show, speaker prep, slide coordination, Q&A logistics, and post-event follow-up. The doc that makes 500 people look seamless.
Full pre-event project plan with sprint structure, team assignments, and deliverable timelines, plus a post mortem capturing outcomes, blockers, and what gets built into the next cycle.
Ghost-written board narrative built from the CEO's raw thinking. Shows the before, meaning fragmented notes and half-formed logic, then the after: a structured story with a clear arc and a single recommendation.
Pre-read written ahead of an executive offsite. Not just the agenda, but the real agenda. Every session has the stated goal and the unstated tension. Dissenting views are named, not smoothed over.
The personal framework I run every week. The signals, the ratios, the conversations, and the silences I track across the org to know what's about to become a problem before it does.
A list of introductions I engineered that closed: deals, hires, partnerships. Each one shows the context, why I connected those two people, how I framed it on both sides, and what happened after.
The calendar and communication protocol I run for executives with active relationships in the Gulf. Covers scheduling norms, decision-making pace shifts, the Hajj travel window, and how to maintain relationship momentum.
A cohort analysis that surfaced retention dynamics no one on the team had connected. Shows the methodology, the initial hypothesis, what the data actually said, and what changed as a result.
A KPI tree that connects daily operational metrics to the financial outcomes the board actually cares about. Built so leadership can trace a number from the board deck back to the team that owns it.
The one-pager I send before a first meeting with a regional fund, government-linked entity, or distribution partner. One page. What we are, why now, what we're asking for, and what they get.
Written for a scenario where Product and GTM disagreed on prioritization. Lays out each position fairly, names the actual disagreement, and closes with a clear recommendation and a next step. The memo that gets the decision made without a meeting.
A weekly briefing format built for a family office principal, covering portfolio updates, relationship activity, board obligations, and personal priorities. Read-in-10 format.
The full scope of the Chief of Staff function for a family office. It defines the operating rhythm, communication architecture, stakeholder map, and decision escalation framework.
The full meeting infrastructure for a family office with active board and investor relationships. Pre-meeting prep package, agenda architecture, materials coordination, and post-meeting action log.
Coordinating a principal moving between primary residence, secondary home, and travel property. Staff handoffs, inventory tracking, vendor access management, and the 48-hour arrival prep protocol that means nothing is wrong when they land.
Working doc covering digital hygiene, physical security for travel, what the EA controls vs. what goes to the security team, and the communication blackout protocol for sensitive trips.
Concierge medicine providers, specialist relationships by city, medication management for international travel, and the protocol for a medical situation abroad. The EA who has this doc ready has already thought through something most principals haven't.
How the household runs when the principal is there, when they're not, and during a transition. Roles, access levels, communication norms, and the escalation path that doesn't require waking the principal at 2am.
The behind-the-scenes document for a private dinner at a principal's home. Catering coordination, security sweep, seating by relationship dynamics, pre-brief on each guest, and the post-event debrief.
Live Notion workspace, AI workflow demos, calendar preset in action, relationship pulse system. Not a slide deck.
Tap any case study or sample to add it to your request.
Your details, the role, and one line on what you are assessing.
Once it is signed and returned, the work reaches you within 48 hours.
Install a complete operating system so the executive only receives judgment-level work, and so their time, cognitive modes, and energy are allocated against explicit targets rather than inherited obligations.
Run intake to establish where the executive’s time is supposed to go by category and by mode. Without targets, a calendar audit is only an opinion.
Most assistants inherit recurring obligations and protect them. What they never do is run a diagnostic against the executive’s targets and ask whether a recurring commitment moves the week toward or away from where that time is supposed to go.
Before I audit the calendar, I run one formula.
Intake gives us the target to measure against. Without it there is no baseline, so you are looking at a list of meetings with nothing to compare them to, and that is an opinion rather than a measurement.
If intake sets external commitments at thirty percent and the schedule shows recurring commitments already consuming thirty-five percent of that allocation, that is the first gap I surface before touching a single meeting. It is the difference between where the time is supposed to go and where existing obligations are already sending it.
A gap of one to two percent is monitored. A gap of five percent or more is acted on immediately.
Intake is not a preference survey. It is a weighted allocation model, so each question is built to produce a number rather than an opinion. Six question types do the work. Select one to see the form it takes and what it feeds.
Sets the starting mode profile. A Chief Strategy Officer opens at thirty percent Visionary. A Chief Operating Officer opens at thirty percent Operator. Every later answer moves the number off that anchor rather than off zero.
Becomes the divisor in the audit formula. Fifty hours means one hour a week is two percent of the allocation, so a two-hour standing meeting is already four percent of the executive’s year.
Produces the stated target. The constraint is the point, because an unconstrained question returns a list of everything the executive values rather than a ranking of what they will actually protect.
Corrects stated preference with revealed preference. Whatever the executive sacrifices first under pressure is the category their stated target is overweighting, so the model discounts it.
Weights the model toward observed behaviour. Repeatedly rescheduling a category is data, and it either means the target is wrong or the block is placed in the wrong part of the week.
Splits the target into current and trajectory. The audit then measures the calendar against where the executive is going rather than only against where they are.
The role anchor sets the opening profile. Capacity sets the denominator. The constrained allocation gives the stated target. Scenario and history answers discount any category the executive sacrifices under pressure. The horizon answer adds the trajectory weight. The model then normalizes the result to one hundred percent, and that is the target the calendar is measured against.
As the executive answers the quiz, the percentages shift from base to actual. The baseline tells us where the role needs them to be, and the quiz reveals where they actually are. The gap between those two is the data collected in stage one, and it becomes the input that drives every stage that follows.
If a principal says strategy should be fifteen percent and recovery should be eight percent, those are not arbitrary preferences. They become the target we calibrate toward and the metric we measure against in real time.
| Category | Hrs | Actual | Target | Gap |
|---|---|---|---|---|
| External | 7 | 14% | 30% | -16% |
| Team Meetings | 18 | 36% | 20% | +16% |
| Direct Reports | 11 | 22% | 14% | +8% |
| Stakeholders | 9 | 18% | 12% | +6% |
| Customers | 3 | 6% | 10% | -4% |
| Strategy | 6 | 12% | 6% | +6% |
| Friends / Family | 1.5 | 3% | 5% | -2% |
| Recovery | 0 | 0% | 3% | -3% |
Once the five percent threshold is crossed on at least one life category, I schedule a twenty minute session with the executive. The purpose is not to work out what to do, because the thinking is already done. It exists to give my leader visibility into what I found, surface any context I am missing, and leave with a confirmed action list. The audit summary is the first of the two documents that go into that session.
Tag work by the cognitive state the role requires rather than by individual commitments in their life. A board presentation and a performance review are not the same mode, and treating them as interchangeable is how whiplash enters the week.
Tap any bubble to learn what each of these cognitive states actually costs when it shows up in the wrong room.
Order the workload so modes compound instead of deplete. Visionary before Connector. Mentor before late-day Executor. Recovery as a deliberate transition rather than leftover whitespace. Wrong stacks transfer fatigue into the next room, and right stacks make each room sharper than the last.
Color stops being decoration and becomes the read-out for the mode system. Most executive calendars are colored by what a meeting is called, so fifteen categories look sorted while telling you nothing about what the week actually costs. Color is assigned by mode instead, which means a week can be diagnosed before a single title is read.
Every calendar I see before I touch it looks the same. Random dark colors, no pattern, grouped by whoever asked first. Interviews, customer visits, press, and investor meetings all get their own color, yet they are one thing: the executive stepping outside the organization and representing it outward. I collapsed the labels into the categories that govern allocation, so the color finally reports on energy rather than on nomenclature.
A calm-looking calendar is a well-sequenced calendar. When the color moves smoothly from warm to cool to neutral, the executive is traveling through the day without cognitive whiplash. When the color jumps, the day is asking them to become a different person every forty-five minutes, and that cost never appears on any agenda.
Eight modes, eight colors, one rule for each. This is the key the whole calendar is drawn against.
Staffing design, meaning the minimum model that can run the system without heroics.
Ask where the executive is still compensating. Every signal on the left is the executive absorbing a cost, and every gap on the right is the layer that should have absorbed it instead.
If the executive had to personally handle a problem that should have been stopped earlier, a broken handoff, a late package, a household issue, a conflicting meeting, a commitment that slipped, then the failure started upstream.
When material gaps surface, run a short decision session. The analysis is already done, so the meeting exists to confirm context, lock actions, and authorize eliminations, compressions, and additions.
The Action Plan is what I bring to the table live. It lists every meeting that crossed the five percent threshold with a proposed action, whether that is compress, convert, or eliminate, and the reasoning behind each. View the sample→
When the meeting is necessary but running longer than the value it delivers, sixty minutes drops to thirty.
When a recurring hold exists for updates or information sharing that does not require live presence, it is replaced with Loom, Slack, email, or a document.
A meeting that no longer has a clear owner, outcome, or decision attached to it, and that nobody would notice if it disappeared.
Here are the categories that make up the Office of the Executive.
Here is a bit of what each one should have. Two are open as a sample. The rest are shared during an active conversation or under NDA.
Trackers, automations, the AI drafting layer, the knowledge base, and the guardrails around them.
Briefing standards, appearance logistics, and message-adjacent operational control.
A system for a pillar is only built where the executive is already paying a tax. That compensation is the signal you use to design a workflow. Look for:
A system for a pillar is incomplete until it meets all five.
Missing any one means the executive will eventually compensate again.
The dashboard holds one shared brain for the office, so everyone works from one source of thought rather than five interpretations of it.
It can live in any system. Some of my favorites are:
Executive focus shifts entirely to high-impact judgment, relationship-building, and critical decision-making.
Commitments are tracked automatically, materials arrive fully vetted, and cross-functional coverage remains seamless, even when key players are offline.
People who work with or under your executive will understand exactly how to engage, what belongs on an agenda, and how decisions reach closure.
The infrastructure around them should carry one hundred percent of the operational load, freeing executive bandwidth for the work that matters most, which should be purely strategic.
Every meeting below was pulled from the recurring audit in part one. Each carries a category gap of five percent or more. Nothing on this list moves without confirmation, and anything touching an external relationship or a direct report comes to Mike before I act.
Mike’s highest stated priority is consuming only 14 percent of the week. Every category below is over-anchored while External is being crowded out. Protected recurring External blocks need to be added before anything else is placed.
Running 1.5 hours a week on a standup format. President-level attendance at all three sessions is likely not required.
Largest single recurring hold. Likely compressible to 60 minutes with a tighter agenda, or convertible to async updates.
Dashboard-driven meetings rarely require the president live. Convert to a shared doc with async commentary unless a decision is teed up.
Weekly prep for a quarterly event. In non-offsite months this slot has no output. Convert to async doc prep.
QA reviews at president level suggest no defined quality owner below. Bring to Mike before any change, this needs context.
A two-hour weekly group sync on top of individual one to ones is likely redundant. Compress to 60 minutes or move to biweekly.
Runs alongside DR Group Sync and individual one to ones, creating overlapping forums. Clarify the distinct purpose or consolidate.
Weekly finance one to one may be over-cadenced. Biweekly may serve the same function and free 30 minutes a week back to External.
Weekly at president level may be over-cadenced. Confirm whether monthly with async updates would suffice.
Runs alongside a separate Investor Call under External. Likely duplicate, bring to Mike to confirm before touching.
Without a dedicated government affairs function, this may be over-indexed. Needs context, do not change without confirmation.
High cadence unless a deal is active. Move to biweekly and convert between sessions to async pipeline doc updates.
Suggests ownership may not be fully delegated. Confirm whether this should be owned by the Head of Growth with Mike attending monthly.
Monthly hold for a quarterly event. In non-offsite months there is no output. Convert to a doc activated three weeks before each offsite.
Zero protected recovery time across a 50 hour week. Add a standing 30 minute buffer, either end of day Friday or post All Hands.
The Action Plan is what I bring to the table live. It lists every meeting that crossed the five percent threshold with a proposed action, whether that is compress, convert, or eliminate, and the reasoning behind each.
When the meeting is necessary but running longer than the value it delivers, sixty minutes drops to thirty.
When a recurring hold exists for updates or information sharing that does not require live presence, it is replaced with Loom, Slack, email, or a document.
A meeting that no longer has a clear owner, outcome, or decision attached to it, and that nobody would notice if it disappeared.
Programs, cards, and club memberships sit in the executive’s name. When an account exists, I never book through a public channel.
Authorized user status, the service desk on file, and preferences loaded, so a request lands as the principal rather than as a stranger.
A named contact at each desk who already knows the standard. That is why a hard ask at 9pm on a Friday gets answered.
Six rules that hold before any tool is opened. They are not preferences. They are the conditions under which an executive can move fast without ever exposing what should stay closed.
Enterprise agreements are configured for zero retention wherever the vendor supports it, so prompts and outputs are not stored or used for training.
Confidential, restricted, and P4-classified material never enters a non-enterprise model. If the tier is not covered by an enterprise agreement, the data does not go in.
Credentials, keys, and tokens stay in local secure storage. They are never pasted into a chat window, a shared document, or an automation payload.
When material cannot leave the machine, transcription and analysis run locally through Whisper and Ollama rather than a hosted service.
Every automation gets the narrowest scope that will do the job, with access reviewed and revoked when a workflow is retired.
Automations log what moved and when, so any pipeline touching executive data can be traced end to end.
I've called the Claude API directly, written production-grade prompts, built agentic workflows, and shipped functional tools. I don't use AI, I build with it. When a CEO wants to know what's real, I can show them something working, not a screenshot.