# Executive Briefing > Executive Briefing - Skill: `ingridleiria/executive-briefing` (Agent Skill) - Install (CLI): `npx skillmds@latest add ingridleiria/executive-briefing` - Raw SKILL.md: https://api.skillmd.com/api/skills/ingridleiria/executive-briefing/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: ingridleiria (https://skillmd.com/u/ingridleiria) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/ingridleiria/executive-briefing --- # Executive Briefing An executive walks into a meeting with a large customer and offers a concession that a departed colleague already offered eighteen months ago, in exchange for something that was never delivered. Or quotes a number from memory that is a quarter out. Or raises a product commitment that engineering removed from the plan in the last cycle. None of these is a failure of intelligence; each is a failure of preparation, and each costs more than the meeting. The opposite failure is a four-page pre-read. It contains everything, it is accurate, and it is not read, because the executive got it at eleven the night before and had two other calls first. The document that is technically complete and practically unread is the most common form of this failure, and it is the one people defend, because the work was done. A briefing succeeds when the executive can walk into the room having read only the first paragraph, and nothing in the meeting surprises them. It is written to be read in two minutes, standing up, on a phone. Everything in the page serves that test, and anything that does not serve it belongs in an appendix nobody may ever open. ## When to use this, and when not to Use it before external meetings, investor and board chair calls, partner negotiations, customer escalation calls, trips with several meetings, and any meeting a leader is joining cold. Use it when someone else prepared the meeting and the person attending was not in those conversations. Do not use it to do the external research, which is `external-insights` and feeds this. Do not use it to make an internal decision, which is `decision-memo`. Do not use it to build board materials, which is `board-deck`, or the investor narrative, which is `board-and-investor-management`. Do not use it to capture what came out of a meeting, which is `meeting-to-decisions`. Do not use it for public statements or holding lines under pressure, which is `crisis-and-incident-comms`, or for a leader's written and spoken voice generally, which is `ceo-communications`. ## What you need before starting **The meeting itself.** Who requested it, when, format, duration, and what the other side expects to leave with. Missing: ask the person who scheduled it. The requester tells you the most about the agenda, and a meeting the other side asked for is a different meeting from one we asked for. **The attendee list on both sides, with roles, and who actually decides.** Missing: ask, then reconfirm on the morning of the meeting. Attendee lists change late and a brief describing the wrong room is worse than no brief. **Our objective in one sentence, and the walk-away.** What we want to leave with, and what we will not agree to. Missing: propose both and get them confirmed. An executive who has not decided the walk-away before the meeting decides it during the meeting, which is where concessions come from. **The relationship history and every open commitment.** Prior meetings, what was promised on either side, by whom, on what date, and whether it was delivered. This is the section that prevents the most expensive mistakes. Pull it from a customer system, an email archive, or the people who were there; a connected relationship or email tool speeds it up where one is available. Missing: ask the two people most likely to have been in the room, and mark anything you could not confirm as unverified in the brief itself. **The constraints.** The number we cannot go below, the commitment we cannot make, the thing legal has ruled out. Missing: ask before writing the positions, because a brief that recommends a position the company cannot honour is worse than no brief. **External context on the other party.** Run `external-insights` where research is needed. Missing: say so on the page. Never brief from assumptions about the other party. A wrong fact costs more than a gap, because the executive will repeat it. **Anything the executive has already said publicly on the subject.** Missing: check the last two quarters of their public statements if the meeting touches strategy. Contradicting yourself in a room that has read your last interview is avoidable. ## The method ### 1. Fix the objective and the walk-away first One sentence each, before any research is organised. Everything else in the brief is judged by whether it helps the executive reach the first and avoid crossing the second. If the objective cannot be written in one sentence, the meeting has no purpose yet and the useful contribution is to say so before the calendar invite goes out. ### 2. Reconstruct the commitment history, dated Every promise made in either direction, who made it, when, and its current state. Distinguish contractual commitments from things said in a meeting, because the second category is where the damage lives: informal commitments are remembered by the party they favour and forgotten by the other. Where a commitment is claimed but cannot be evidenced, write it as claimed and unverified rather than omitting it. The executive needs to know it may be raised. ### 3. Map the room by interest, not by seniority For each attendee: role, what they are measured on, their likely position on the question, and one relevant dated fact. One line each. The judgement is who actually decides. The rule: the decider is the person whose budget or headcount changes as a result. Where that person is not attending, the meeting's realistic objective is not agreement, it is being represented accurately to them, and the brief should say so rather than setting up a decision that cannot happen in the room. ### 4. Gather the external context and verify it Facts about the other party carry a source and a date, or the word unverified. Recency matters most for leadership, pricing, funding, and headcount. Separate what they say about themselves from what a third party reports and from what has been inferred. ### 5. Write the two columns What we want, and what they want, side by side and short. The overlap is the deal; the gap is the negotiation. Doing this on the page rather than in your head is what surfaces, before the meeting, that the two objectives do not overlap at all, which is a finding worth having in advance. ### 6. Write three positions, with the numbers exact Three points to make, in the order to make them, each with its supporting evidence in one line. Where numbers will be discussed, they appear here in full and sourced. An executive who has the number on the page does not estimate it out loud, and estimating out loud is how a briefing turns into a correction email the next day. Three is the working limit. A brief with seven positions has not decided what the meeting is for. ### 7. Write the questions Three to five, each of which either advances the objective or answers something the research could not. A good question in this section usually comes straight from the gaps: the things you tried to establish and could not. Write them as they would be asked out loud. ### 8. Write the do-not list The sensitive topics, the commitment not to make, the number not to reveal, the name not to raise, the joke that will not land. One to three lines. This is often the most valuable section in the document and it is the one most often missing, because it is the only part that requires someone to have thought about how the meeting could go wrong. ### 9. Write the next step to propose One action, one date, one owner, so the meeting ends with something rather than with warm intentions. Where the objective is agreement, this is the mechanism that turns it into a commitment before everyone leaves the room. ### 10. Cut to one page and test the two-minute read Read it aloud against the clock. Anything that survives is the brief; everything else is an appendix. Then ask the harder question: if the executive read only the headline and the positions, could they hold the meeting. If not, the compression is not finished. Send it early enough to be corrected. A brief that arrives the night before is a brief with no error-correction window, and the executive is the person most likely to spot the missing fact. ## Writing rules Lead every section with the conclusion. Background follows only where it changes what the executive should say. Names, numbers, dates. No adjectives about people. "Very sharp" and "difficult" tell the reader nothing they can use and create a document that would be embarrassing if forwarded, which happens. Describe behaviour and stated positions instead: "declined the same proposal in March on pricing grounds" is useful; "sceptical" is not. Verified facts and inferences look different on the page. "Stated on their results call in May" against "likely, based on their hiring pattern". Short lines and bullet form, because the reader is scanning rather than reading. Sensitive content stays factual and professional, and never speculates about a person's motives or private circumstances. ## Worked example **Situation.** A software company's largest customer, a national retail group billed at 1.15 million a year, had appointed a new chief operating officer. She asked for a call with our chief executive, at three days' notice, eleven weeks before the renewal. The account had been managed by a sales lead who had left the company four months earlier. **Task.** One page, delivered a day before the call. Good meant the chief executive knew every open commitment, had the renewal numbers in front of her, and did not offer anything the business could not deliver. **Action.** The first draft was three pages of account history: the original sale, the expansion, the support record, the stakeholder map, and two years of quarterly review notes. It was abandoned the moment the chief executive said she would read it in the car and had about four minutes. Three accurate pages that do not get read are worth less than one page that does. The rebuild started from the commitment history, which was where the risk was. The customer system had the contract. It did not have what turned out to matter: an email thread in which the departed sales lead had offered a twelve percent discount extension at the next renewal in exchange for a joint case study. The case study had never been produced. The commitment was informal, it was in writing, and the customer's commercial team certainly had the same email. Two other facts changed the shape of the page. A support escalation had been open for 34 days against a contractual target of ten. And the new chief operating officer had spent six years at a company that had been a public reference customer of our closest competitor, which was on her own public professional profile and was a fact worth knowing without being a fact worth mentioning. The do-not list ran to three lines and was the most useful part of the brief. Do not offer the multi-location reporting feature, which had been descoped from the plan in the previous cycle and had been mentioned to this customer twice. Do not name the departed sales lead as the reason for anything. Do not discuss the competitor connection. The positions were three: acknowledge the discount commitment before they raise it, tie any extension to the case study being contractually scheduled rather than promised, and put a date on the resolution of the open escalation. One thing in the brief was wrong. It listed four attendees on their side. Two of the four did not attend, and their head of information technology did, who was not on the page at all, because the invite had been changed the previous afternoon. The chief executive handled it, and the standing rule since has been to reconfirm the attendee list on the morning of the meeting. **Result.** The chief executive opened by acknowledging the discount commitment, which the customer's commercial director had in her own notes and had planned to raise in the second half of the call. Acknowledging it first changed the register of the conversation. The renewal closed nine weeks later at an eight percent discount rather than twelve, with the case study written into the contract with a date, and the escalation resolved inside a fortnight. Whether the four-point difference is attributable to the brief is not something anyone can prove. What is certain is that the alternative, which was discovering the discount commitment when it was produced in the room, would have made that conversation harder in a way that is easy to imagine. ### A second scenario, where it goes differently The same chief executive's first meeting with a newly appointed non-executive director. She is not there to win anything, the other party is not deciding anything, and the objective is to understand what the new director will push on over the coming year. The shape inverts. The positions section shrinks to one line, which is what we want them to leave with as an impression rather than as an agreement. The questions section grows to seven and becomes the substance of the brief. The do-not list becomes the second most important part: the internal disagreements not to air with someone who has not yet met the rest of the leadership team, and the number not to give informally before the board pack presents it in context. What changed is who holds the decision. When the executive is not deciding and not being decided about, the brief stops being an argument and becomes a listening plan, and the measure of a good one is the quality of the questions rather than the strength of the positions. ## Output One page. Everything below fits on it, and anything that does not fit goes into an appendix. ``` BRIEF: [meeting] FOR: [executive] WHEN: [date, time, duration, format] REQUESTED BY: [which side] PREPARED: [date] ATTENDEES RECONFIRMED: [date] HEADLINE [Two sentences: the purpose of the meeting and the single outcome we want.] WHERE THINGS STAND [Three to five lines. State of the relationship, the last interaction and its outcome, every open commitment with its date, owner, and status. Dated facts only.] THE ROOM | Name | Role | What they are measured on | Likely position | One dated fact | WHAT WE WANT / WHAT THEY WANT | We want | They want | [Short. The overlap is the deal, the gap is the negotiation.] POSITIONS TO TAKE 1. [Point] because [evidence in one line, with the exact number and its source] 2. ... 3. ... QUESTIONS TO ASK [Three to five, written as they would be said out loud.] DO NOT [The topic to avoid, the commitment not to make, the number not to reveal.] NEXT STEP WE WILL PROPOSE [One action, one date, one owner.] WALK-AWAY [What we will not agree to, in one line.] ``` **Trip brief**: one page per meeting in the above format, plus a cover page carrying the trip objective, the sequence of meetings, and the logistics that affect the conversations, such as time zones, travel gaps, and who is in which room. **Standing brief** for a recurring relationship: the same page, with the relationship history, the room, and the two columns maintained and updated after each interaction, and a change log at the bottom recording what moved and when. ## Failure modes **The four-page pre-read.** Recognise it when the executive asks you what is in it. Fix by cutting to one page and moving the rest to an appendix; the test is whether the meeting could be held from the headline and the positions alone. **Adjectives about people.** Sharp, difficult, political. Recognise them by imagining the document forwarded to the person described, which does happen. Replace each with a dated behaviour or a stated position. **A fact with no source.** Recognise it because it reads as certain and cannot be traced. Fix by labelling it unverified, which costs one word and prevents the executive stating it as fact. **No do-not section.** Recognise it because the brief is entirely about what to say. Its absence means nobody thought about how the meeting could go wrong, which is the cheapest thinking available before any meeting. **Informal commitments left out because they were not contractual.** The most expensive omission in this entire document. Recognise it when the commitment history contains only contract dates. Fix by searching the email record and asking the people who were in the room, not just the system of record. **The brief that arrives too late to correct.** Delivered the night before, so the one person who could spot the missing fact has no time to. Fix by sending a day earlier in a rougher state. **Positions without numbers.** Recognise it when a position says "our pricing is competitive". The executive will be asked for the number and will estimate. Put the figure on the page with its source. **No next step.** Recognise it when the brief ends with the questions. A meeting that ends without a proposed action ends with warm intentions and a follow-up email nobody sends. ## Edge cases **Thirty minutes to prepare.** Write four lines: the objective, the two open commitments, the one thing not to say, and the next step to propose. That is a real brief. Say what was not checked so the executive can calibrate. **The executive knows the relationship better than you do.** Then the brief is not background, it is a checklist: the dated commitments, the numbers, the do-not list, and the next step. Ask them what they want on it, and expect the answer to be shorter than your draft. **The meeting is adversarial.** Add a line for the strongest thing the other side will say and the response to it, keep the walk-away at the top rather than the bottom, and agree in advance who speaks to what. Do not attempt to predict emotion; predict arguments. **The decider is not in the room.** Say so in the headline and reset the objective to being represented accurately. The positions become things the attendee can repeat correctly, which means they must be short enough to be repeated. **A commitment is claimed and cannot be evidenced.** Write it as claimed, name who claims it, and prepare a response that neither concedes nor denies: acknowledge, say it will be checked, and give a date. Never let the executive be the first person to deny something in a room. **The executive has a personal relationship with the other party.** Keep the brief strictly professional and factual anyway. Anything about the relationship that is not a business fact does not belong in a document. **The meeting is with someone about to become a colleague or a counterparty in a sensitive process**, such as a candidate, an acquirer, or a regulator. Restrict the brief to the public record and the process, take out anything inferred, and have it reviewed by whoever owns that process before it is sent. ## Quality bar - The executive could hold the meeting from the headline and the positions alone. - Every open commitment appears with its date, the person who made it, and its current status, including informal ones. - Every fact about the other party carries a source or the word unverified. - The do-not section exists and is specific enough to act on. - Numbers appear in full on the page, sourced, so nothing has to be estimated aloud. - No adjective is used about a person anywhere in the document. - The page ends with the next step we intend to propose and the walk-away. - It fits on one page and was sent early enough to be corrected. ## Adapting this to your context The examples come from commercial meetings: customer renewals, investor calls and partner negotiations. The page shape holds; the content does not. - **The one-page, two-minute test.** Calibrated on an executive reading in a car. Where the principal reads deeply and will ask for the evidence, keep the one page and make the appendix real rather than lengthening the brief. - **The commitment history.** Built from a customer system and an email archive. In a clinical, legal or casework setting the equivalent record is the case file, and confidentiality rules may limit what can go on a page at all, which is worth stating on the brief. - **The positions and the walk-away.** Written for a negotiation. Where the meeting is with a regulator, an inspector or a funder there is no walk-away: replace it with the position you are obliged to state and the thing you must not speculate about. - **The do-not list.** Three lines in a commercial setting. In regulated or listed environments this section carries disclosure consequences and is worth a review by whoever owns them before the brief is sent. - **What not to change.** Every fact about the other party carries a source or the word unverified, no adjective is used about a person, and the page ends with the next step and the walk-away. ## Related skills `external-insights` supplies the verified outside-in research this page compresses. `principal-simulator` predicts how the executive, or the person on the other side, will react to a given position before the meeting. `meeting-to-decisions` captures what came out of the meeting and turns it into owned actions. `decision-memo` carries any decision the meeting surfaces to a named decider. `outreach-email` handles the contact that precedes a first meeting. `board-and-investor-management` and `board-deck` cover recurring investor and board preparation, where this format is used for the one-to-one calls around the meeting. `crisis-and-incident-comms` covers briefing under active pressure, where the holding line matters more than the positions.