Answer who, why, and what next in order, then check each answer before you send.

The Who, Why, and What Next of an intro email is a checklist, not a slogan. Every introduction that works answers three questions in order: who are these two people, why should they talk, and what should happen after they read. When one answer is missing, the reader has to supply it, and most readers will not. Use the three questions as a gate before you send anything. Read the draft and point to the sentence that answers each question. If you cannot find it, the message is not ready, no matter how polished the prose is. That gate is faster than rewriting, and it catches the missing part before it hides under better wording.
Order matters because each answer depends on the one before. You cannot write a credible why until you know who each person is and what they are responsible for. You cannot write a useful what next until the why names a specific topic. Draft in that order and review in that order. When a draft feels vague, the weakness is usually earlier than the sentence you dislike: a fuzzy who produces a generic why, which produces a vague action. Fix the earliest weak answer first. Rewriting the closing will not repair an overlap that was never specific enough to support it.
Assign the three questions to different moments in your workflow. The who belongs to preparation, before you write. The why belongs to drafting, where you choose the overlap. The what next belongs to review, where you check that one action is obvious. Keeping these moments separate prevents the common habit of polishing the closing line while the reason for the message is still unclear. Write the three answers in a short note first, then speak the email from that note. When the note is complete, drafting becomes a translation task rather than a discovery task, and you can hear a missing answer before you speak.
Define what a complete intro looks like as a deliverable. It has two named people, one line each, one verifiable overlap, and one action with an owner. It fits in roughly one hundred to one hundred and fifty words. It can be read once and answered in one line. It names no more than one topic and asks for no more than one thing. Write that definition down and use it to review your own drafts and those of colleagues. A shared definition turns the three questions into a standard. Add the definition to any team note about introductions so reviewers apply the same bar.
The who line should give the reader enough to place each person without turning into a biography. Use role, current focus, and one relevant detail. For example: Mina leads support for the self-serve segment and is rebuilding its onboarding. That sentence says what she runs, what she is working on, and why the work matters. It does not list her previous employers or her education. Aim for one sentence per person. If you need two, the second is usually the why, so move it to the next section. One sentence per person keeps the reader moving and leaves the reasoning to the section that needs it.
Write each who line from the person's own perspective. A line that the subject would accept is safer than a line that flatters them. Avoid adjectives such as brilliant, world-class, or seasoned, because they invite skepticism and say nothing checkable. Prefer verbs and nouns that describe work: runs, builds, owns, reviews, decides. If the person is senior, describe scope rather than praise. If the person is new to their role, describe the mandate rather than their history. These choices keep the introduction credible to both readers. Read the line as if you were the subject, and remove anything you would not want forwarded.
Check names, spelling, and pronouns before anything else. A misspelled name is the error most likely to be remembered, and a wrong pronoun is the error most likely to cause offense. Say each name aloud once, then read the written version and compare. When two people share a first name, use a short descriptor after each mention. When a name has an unusual spelling, confirm it with the person rather than guessing. These checks take a minute and are the cheapest quality improvement available for any introduction. Keep the confirmed spelling in your notes so the next message starts from the correct form.
Decide what to leave out of the who lines, and write the exclusion rules down. Leave out reporting lines unless they explain the overlap. Leave out tenure and education. Leave out titles that only make sense internally. Leave out anything the person has not agreed to share, such as a job search or an unannounced project. The who line exists to help the other reader decide whether a conversation is worth having, not to summarize a career. A short, accurate line does that better than a full profile. Write the rules once and reuse them, because each exception you add makes the who line longer.
The why is the sentence readers judge most harshly, because it is the one they cannot verify from the message alone. A good why names a specific overlap: a shared problem, a complementary skill, a decision one person is making and the other has already faced, or a customer segment both serve. State it in two sentences at most. Avoid vague bridges such as you should know each other or there may be synergies. If the overlap needs three sentences to explain, it is probably two overlaps, and the message needs only the stronger one. Choose the overlap that produces a specific first topic, not the one that sounds most impressive.
Test the why with a simple challenge: could either reader disagree with it? A claim that no one could dispute, such as you both care about quality, is not a reason. A claim that one reader could check, such as you are both reducing manual review in the same part of the workflow, is a reason. Write the why so that it names the topic, the stakes, and the connection. Then remove any adjective doing work that a fact should do. Specificity is what makes the sentence survive the reader's first skeptical pass. Read it once as a skeptic and once as a friend, and keep the version both can accept.
Match the why to the current moment. A reason that was true six months ago may be stale. Before you write, check the one fact the why depends on: is the role still open, is the launch still scheduled, is the decision still pending. If you cannot confirm it, either refresh the fact or choose a different overlap. Write the date beside the fact in your notes. This small discipline prevents the embarrassing follow-up where the reader replies that the project ended last quarter. When the fact has changed, update the note and pick the overlap that still holds today.
Write the why as a sentence both people could repeat. If one reader could not explain to a colleague why the introduction was made, the overlap is too abstract. Practice by saying the why aloud in one breath, then asking a colleague to paraphrase it. If their paraphrase loses the specific topic, rewrite the sentence until it survives. Keep the final wording in your notes for similar introductions. A reusable why shape is more valuable than a clever phrase, because it transfers to the next pair of people. Write the shape as a fill-in sentence with two blanks, one for the topic and one for the stake.
The what next should be impossible to miss. Put it in its own short paragraph or its own sentence at the end, and make it the only request in the message. Name the action, the owner, and the timeframe. For example: Mina will send two times that work this week; Sam, reply with the one you prefer. That sentence tells each person what to do and who moves first. If the action needs a decision from someone senior, say so explicitly rather than leaving the reader to infer it. Put the sentence on its own line so a reader scanning on a phone cannot miss it.
Offer one action, not a menu. A menu of options feels polite and produces paralysis. If you genuinely need a fallback, make it lighter than the primary action and put both in one sentence: reply with a time, or tell me if a short note is easier. Do not add a third option. Also decide what happens if no one replies. A quiet intro is not a failure if the two people simply did not need to talk; note the outcome and close the thread rather than sending a reminder that adds pressure. Record the quiet outcome in your notes and move on rather than treating silence as a rejection.
Draft the closing action in the same sitting as the rest of the message, because the action depends on the why. With Voiskey, you press a shortcut, speak the who, the why, and the what next in order, and polished text appears at the insertion point in your message window. It removes filler words, stutters, false starts, and self-corrections, so the closing stays short even when you are thinking out loud. It also adapts punctuation, formatting, tone, and phrasing to what you are doing. Download Voiskey for Mac and Windows and dictate the three parts in one pass. Keep the three answers in the same order every time so the review becomes mechanical.
Review the what next against three checks. First, is there exactly one action? Second, is the owner named? Third, can the reader complete it in under a minute? If any answer is no, rewrite the closing before you send. Then read the closing alone, without the rest of the message, and ask whether it still makes sense. A closing that depends on the reader remembering an earlier paragraph will be missed. The final sentence should work as a standalone instruction, which is what makes it survive a quick phone read. If it needs the earlier paragraph to make sense, move the missing detail into the closing.
Audit your introductions with the three questions once a month. Take ten recent messages and mark whether each has a clear who, why, and what next. Count the missing answers by type. A cluster of missing whys usually means the overlap was assumed rather than checked. A cluster of vague what nexts usually means the writer was avoiding a specific ask. The counts tell you which part of the workflow needs attention, and they are more useful than a general impression that the messages could be better. Write the counts beside the sample date so the next audit compares like with like.
Use the audit to fix the template rather than individual messages. If the why is often missing, add a required line to your note that names the overlap before you draft. If the what next is vague, add a required line for action and owner. If the who is too long, add a word limit per person. Change one requirement at a time and review the next ten messages against it. This is the difference between an audit that improves the process and one that only produces a list of regrets. Keep the previous requirement next to the new one so you can see which change helped.
Bring the audit into your spoken workflow so the standard is easy to apply. Voiskey composes in the field where you already type, so you can speak the three answers directly into the draft and see the result before sending. Because it learns names, jargon, acronyms, and spelling preferences, the who lines stay consistent across messages. Keep a short note with the three required answers and read it before you speak. Download Voiskey for Mac and Windows and run the audit on messages you draft in the app. Read the note aloud once before you start, then speak the three answers without looking back.
Close the loop by writing one example of a complete intro and one of a message that failed the audit. Label the failure by the missing question, not by the person who wrote it. Share both examples with anyone who sends introductions on your behalf, and ask them to mark the three answers in each. When they can do that reliably, the standard has transferred. Review the examples each quarter, replace them when the work changes, and keep the audit on the calendar so the standard does not fade. Put the examples in the same note as the template so a new writer finds both together.
Voiskey is an AI voice typing app that works at the system level. Press a shortcut, speak the three parts in order, and polished text appears at the insertion point in your message window. It removes filler words, stutters, false starts, and self-corrections, and it adapts punctuation, formatting, tone, and phrasing, so the three answers arrive as a short written message you can review and send.
Role, current focus, and one relevant detail, in one sentence per person. Voiskey learns names, jargon, acronyms, and spelling preferences, so recurring names and team terms stay consistent as you dictate. Say each name clearly, check the spelling at the insertion point, and move anything that explains the connection into the why section instead.
Speak one action, one owner, and one timeframe in a single sentence, and place it at the end. Voiskey removes filler words and self-corrections, so the closing stays direct when you think out loud. Review it alone at the insertion point: if it still makes sense without the earlier paragraphs, it will survive a quick phone read before you send.
Voiskey supports more than one hundred languages and translation. You can speak the who, why, and what next in the reader's language, and polished text appears at the insertion point. It adapts punctuation, formatting, tone, and phrasing to what you are doing, which keeps each of the three answers clear across languages without a separate drafting step.

Download Voiskey for Mac and Windows and dictate the who, why, and what next in one pass.
Use it across macOS, Windows, iOS, and Android