A field guide for experts who talk better than they type
The 6 Explainer Types: why the way you talk is the content style you've been looking for.
Chapter 1
You already know you should be publishing. Every solo expert does. You've heard the sermon about consistency, you follow three people who post daily, and you have a drafts folder that proves you tried. This book is not going to tell you to post more. That advice has never once worked on you, because motivation was never your problem.
Information was. Specifically: nobody ever told you what kind of creator you already are.
Here's the moment this book is built on. Someone at dinner asks what you actually do. Not the job title, the real thing. And for about two minutes, you light up. You're clear, you're specific, you're interesting, and you're not trying. Whatever you did in those two minutes, that's your native style. Some people answered with a story about a client. Some drew a map on a napkin: "there are really three kinds of problem here." Some reached for an analogy, some picked a fight with the conventional wisdom, some grabbed a phone to show something, and some turned it around and started asking the other person questions.
Six different moves. All of them worked, because they were each performed by someone running their home-base style, unedited.
Now compare that to what happens when you sit down to "make content." You open a blank page and try to write the way successful posters write. If their style happens to match yours, fine. Usually it doesn't. The dominant advice in the creator economy assumes a writer: daily essays, tight hooks, punchy lines. Some experts are writers. Most are talkers, and a talker writing against their own grain produces exactly what you'd expect: stiff posts, slow drafts, and a quiet certainty that content just isn't for them.
The claim of this book is simple. The way you explain things out loud is an observable, fairly durable behavior — researchers who study communicator style have been measuring differences like these for decades (Norton, 1983). It shows up every time someone asks you a real question. And each version of it maps onto specific content formats where it wins, and other formats where it loses no matter how hard you grind.
So the plan is not "become a content person." The plan is: identify the two minutes you already do well, learn which formats are built out of exactly that behavior, and stop paying full price to produce the formats that fight you. The next chapter shows where the six types come from and why this isn't astrology. Chapters 3 through 8 give each type the full treatment: how to spot it, what the research says about why it works, your format map, your failure mode, and how to get it out of your head by talking. Chapter 9 covers blends, because you're one. Chapter 10 gives you a one-week test to prove all of this against your own numbers.
Chapter 2
A typology earns trust by showing its work, so here is ours.
The oldest bones are rhetorical. Teachers of writing have sorted communication into kinds for two centuries: Samuel Newman's 1827 rhetoric textbook listed five, Alexander Bain's 1866 revision settled the canon that American schools taught for decades — narration, description, exposition, argument. Composition scholars eventually stopped teaching writing "by mode" (the definitive history is literally titled "The Rise and Fall of the Modes of Discourse"; Connors, 1981), and we're not reviving the pedagogy. But as a way of sorting what a stretch of explanation is doing, the categories have proven stubbornly durable. They survive today in the three text types of the Common Core: narrative, informative, argument. The Campfire, the Mapmaker, and the Sparring Partner are those three, observed at a dinner table instead of in an essay.
The other three types come from watching how people teach. The Translator's move runs on what cognitive scientist Dedre Gentner calls structure-mapping (Gentner, 1983): a good analogy carries a system of relationships from something you know to something you don't, which is why "the atom is like a solar system" teaches more than a list of facts. To be precise about what's science here: structure-mapping describes how analogy works in everyone. Calling someone a Translator describes a habit of reaching for it first. The mechanism is Gentner's; the label is ours. The same honesty applies to the Demonstrator (the worked-example research behind it is about how novices learn, not about personality) and the Diagnostician (Socratic questioning is a technique anyone can use; some people just default to it).
Our type vocabulary also borrows from Anthony Grasha, who spent a career categorizing teaching styles (Teaching with Style, 1996). Two of his five styles echo here: his Personal Model teacher, who instructs by doing the thing in front of you, is a close cousin of the Demonstrator, and his Facilitator, who guides by questions, loosely resembles the Diagnostician. Grasha insisted on a point we're adopting as a design principle: nobody is one style. His research found every teacher blends all five and shifts the mix with the audience and the material.
That's why your quiz result is a stack, not a box. You'll get a primary type and a secondary, and the right way to read them is as your most comfortable starting register, not a fixed identity. The axes are continua. Skilled explainers flex across all six moves; what differs is where each of us starts when nobody is managing us. If a description in the coming chapters feels 80% right, that remaining 20% is probably your secondary showing through, and Chapter 9 is about exactly that.
One more piece of the work shown: how the quiz avoids measuring who you wish you were. Direct trait questions are easy to answer aspirationally. In studies where people are asked to fake good, self-ratings shift by half a standard deviation or more, while questions tied to concrete situations move about a third as much, and questions about specific, checkable moments move least (Viswesvaran & Ones, 1999; Nguyen et al., 2005; Becker & Colquitt, 1992). So the quiz never asks what you're like. It asks what your first sentence sounded like last time, what the person across the table did, and what people literally say when they thank you. Harder to fake is not impossible to fake, and the result is a lens, not a diagnosis. But the lens is ground from behavior, which is the best material available.
Chapter 3
🔥The CampfireStory-first. "So I had this client last spring…"
Someone asks you a question and you answer with a moment. Not a principle, not a list: a scene, with a person in it, moving through time. You don't say networking referrals beat cold outreach; you say "so in March this founder emails me out of nowhere," and two minutes later everyone at the table knows exactly why referrals win, without you ever stating it. When a client asks what they should do, your instinct is to tell them about another client who faced the same wall. The lesson arrives wearing a story, or it doesn't arrive at all.
The research on stories is more interesting than the folk wisdom, and Campfires should know the real version. It is not true that stories beat statistics at persuading people; the earliest meta-analysis on the question found statistical evidence slightly ahead (Allen & Preiss, 1997), and later work sharpened the split: numbers do more to change what people believe, stories do more to change what people do (Zebregs et al., 2015). Against ordinary non-narrative messages, stories reliably win on attitudes and intentions, with early evidence they move behavior too, and the effects hold up over time (Braddock & Dillard, 2016; Oschatz & Marker, 2020). Messages that combine a story with the numbers beat either alone (Allen et al., 2000).
There's a second finding that matters even more for a solo expert, because your content sells you. In five experiments, listeners rated speakers who argued with stories as warmer, and speakers who argued with numbers as more competent: modest but consistent effects, from a single lab and not yet independently replicated, that even changed whom listeners picked as a partner for cooperative work (Clark, Green & Simons, 2019). Warmth is the currency of trust-based services. People hire coaches and consultants they feel they know. Your style plays to exactly that feeling.
Lead formats, where your style is the whole advantage:
Workable, fine with adaptation: frameworks presented through the story that produced them; myth-busting told as "I believed this too, until."
Fights you, so produce sparingly and never judge yourself by it: bullet listicles, tactical checklists, anything that asks you to strip the person out of the point.
You bury the lede. You're four minutes into the setup before anyone knows why they're listening, which is charming at dinner and fatal in a feed. The counter-move is stolen from screenwriters: give away the ending first. "This client fired her biggest customer and revenue went up. Here's the whole story." The hook is the destination; the story is the ride. Your second failure mode is compression: when someone forces you to bullet-point your insight, it dies. Don't compress the story. Pick a smaller story.
Campfires marry Mapmakers: your story plus their structure is the case study that actually teaches. With a Sparring Partner secondary you become the parable-with-a-villain, the most shareable story shape there is. The type most likely to misread you is the Mapmaker, who hears your setup and wants the point faster; when you write for Mapmakers, front-load the takeaway and let the story earn the scroll.
Chapter 4
🧭The MapmakerFramework-first. "There are really three kinds of…"
Someone asks a messy question and within thirty seconds you're sorting it. "There are really three kinds of churn." You can't help it: territory arrives and your head draws a map. At dinner you're the one who takes a rambling complaint about someone's job and hands it back as two options and a deciding question, and they look at you like you turned the lights on. When a client asks what to do, you don't reach for a story or a hot take; you reach for the whiteboard. First you name the stages, then you show them which stage they're standing in. People leave conversations with you feeling like the problem suddenly has drawers.
The categories you build by instinct have a long paper trail. Versions of them appear in Samuel Newman's 1827 rhetoric textbook and were codified by Alexander Bain in 1866 as the classic modes of discourse. Exposition, the mode you live in, breaks down further into classification, process, and comparison, which map neatly onto "the three kinds of," "the four stages of," and "X versus Y." Two caveats belong here. Composition scholars stopped teaching writing by mode decades ago (Connors, 1981), so the lineage shows these are durable ways of sorting what an explanation is doing rather than an endorsed method. And classification is machinery every explainer uses; what the label describes is your habit of reaching for it first.
The finding that should interest you most is about perception. In five experiments, speakers who argued with numbers were rated more competent, while speakers who argued with stories were rated warmer; the effects were modest but consistent, and they changed whom listeners picked for which kind of work (Clark, Green & Simons, 2019). Structured, statistical evidence also does more than narrative to change what people actually believe (Zebregs et al., 2015). Competence is your default output. It's why prospects trust you with the hard problem, and why your content can sometimes read like it was written by the hard problem.
Lead formats, the ones that reward structure:
Workable, fine with adaptation: case studies structured as one client moving through your stages; comparison posts; myth-busting framed as "the map most people use is missing a region."
Fights you; make these rarely and grade yourself elsewhere: raw personal-arc storytime, vibes-first hot takes, anything that asks you to publish a feeling before you've sorted it.
You over-structure. Sometimes there aren't three kinds; there are two and a weird one, and you quietly shave the weird one until it fits the drawer. Before you publish a map, run one real client through it out loud. If you catch yourself trimming their situation to fit a stage, the map is wrong, and the trimming is usually where your next framework lives. Structure also has a second price: temperature. A map with nobody standing on it reads cold, and the research above says structure buys you competence, not warmth. So re-attach a human before you post: one sentence of a real mess, then the drawers that sorted it.
Mapmakers marry Campfires: their story walking through your stages is the case study clients actually finish, and it fixes your temperature problem for free. Add a Translator secondary and your framework grows a handle people can carry; a named map with one good analogy per stage is what gets repeated in rooms you're not in. The type most likely to misread you is the Campfire, who hears drawers where a person used to be; when you write for Campfires, open with the mess and make them want the map.
Chapter 5
🔁The TranslatorAnalogy-first. "It's basically like…"
Your first sentence starts with "okay, so you know how…" You explain by borrowing. Whatever the listener already understands, mortgages, sourdough, traffic on the 405, becomes the vehicle, and your real point rides in on it. When a client asks why their launch flopped, you don't reach for funnel metrics; you say "you threw a party and forgot to put the address on the invitation," and they get it instantly. People quote you back to yourself weeks later, sometimes word for word. That's the tell. Your ideas travel because you pack them in containers that already fit through the listener's door.
When you reach for an analogy, the machinery underneath is what cognitive scientist Dedre Gentner calls structure-mapping (Gentner, 1983): a good analogy carries a whole system of relationships over from something familiar to something new, which is why "the atom is like a solar system" teaches more than any list of facts about electrons. This is one of the most solidly confirmed accounts in cognitive science, tested and upheld for forty years.
One honesty note, because this book promised you no astrology. Structure-mapping describes how analogy works in everyone; the Translator label is our name for the habit of reaching for it first. What the research does show is that people differ in how readily they generate analogies unprompted, and that this fluency grows with deep expertise in a domain (Goldwater et al., 2021). Your comparisons get better as you go deeper, which is convenient, since depth is the thing you sell.
The classroom research adds a warning worth keeping. Every analogy breaks somewhere, and breakdowns nobody flags will breed real misconceptions in the listener's head. Glynn's Teaching-With-Analogies model makes "show where the analogy fails" an explicit, non-optional step (Glynn, 1991). Hold that thought; it returns in your failure mode.
Lead formats, the ones your reflex was built for:
Workable, fine with adaptation: framework content where you supply the handles for someone else's structure; teaching pieces that open on the comparison and then earn it with detail.
Fights you, produce sparingly and never judge yourself by it: step-by-step documentation, spec-level tactical checklists, anything that punishes approximation and pays only for literal precision.
You ride the analogy past its breaking point. The comparison that illuminated the first eighty percent starts quietly lying about the last twenty, and because it sounds so clean, nobody checks, including you. Precision is your tax, and someone eventually audits.
The counter-move comes straight from Glynn: break your own analogy in public. "Habits compound like interest, except there's no bank statement, so you can't see the balance until it's large." Naming the breaking point does two jobs at once. It converts a liability into a credibility signal, and it hands you a second piece of content for free. A useful test before you publish any comparison: does it predict something about the target, or just decorate it? If it only decorates, file it as a caption and keep looking for the explanation.
Translators marry Mapmakers. Their structure plus your handles is the named framework people can actually repeat: the map gets built by them and remembered because you labeled the drawers. With a Campfire secondary, your metaphor gains a protagonist, and the story makes the comparison stick twice as hard. Sparring Partners will misread you fastest: they hear an analogy and start prosecuting its edge cases in the comments. When you write for Sparring Partners, flag the breaking point before they find it; disarming the objection is cheaper than winning the thread.
Chapter 6
🥊The Sparring PartnerChallenge-first. "OK but everyone gets this wrong—"
Someone at the table repeats a piece of common wisdom and you feel it physically. Your first word is "OK." Your second word is "but." You don't explain by laying out what's true; you explain by staging a fight between what everyone believes and what actually works, and you make the listener the referee. When a client asks what they should do, you start with what they should stop doing, because half your value is the first twenty minutes, where you dismantle the advice they walked in with. People leave conversations with you slightly winded and noticeably sharper. They think harder around you than they do alone.
The research that comes closest to what you do is minority influence. When one consistent voice dissents from a group, it can shift what the group sees and believes, even on judgments as basic as the color of a slide (Moscovici, Lage & Naffrechoux, 1969). The finding that matters more for you came later: exposure to a dissenting minority makes people think divergently. They consider more alternatives, search harder, and produce more original solutions, and the effect shows up even when the dissenter turns out to be wrong (Nemeth, 1986). Majority pressure buys compliance; dissent buys thought. That is the mechanism under every good myth-busting post you'll ever write. The listener doesn't just adopt your position, they start actually processing the question.
Two flags before you run with this. First, this is research about dissenting positions in groups, not about a kind of person; the label describes your habit of taking that position first. Second, the marketing lore that contrarian content "out-engages" by some tidy percentage is practitioner-grade and we treat it that way. What the peer-reviewed work does insist on is consistency: Moscovici found that erratic dissent gets dismissed while consistent dissent converts. Scattered hot takes read as noise. A position, prosecuted patiently, reads as a point of view.
Lead formats, where the fight is the feature:
Workable with adaptation: case studies told as bad-advice autopsies; frameworks framed as "the standard playbook versus what works."
Fights you, and not worth grading yourself on: neutral how-to guides, curation roundups, inspirational quote content. Anything with nothing to push against.
You need a foil. With nothing to argue against you stall, which is why the blank page is your worst enemy: it refuses to fight back. So keep a foil file. Every bad take you scroll past, every piece of advice a client repeats to you wide-eyed, goes in the file, and content day starts there instead of at zero. The other bill comes due at full volume: you exhaust a room that just wanted an answer, and readers who came for help leave feeling scolded. So budget the rebuild: for every hundred words of teardown, a hundred words of "do this instead." The demolition earns attention. The replacement earns the client.
Sparring Partners need Mapmakers, because your teardown plus their map is the rare post that destroys bad advice and replaces it in the same scroll. With a Campfire secondary, your takedowns grow a protagonist: the story where everyone gave her the standard advice and she ignored it, which readers share because it lets them pick a side. The type most likely to misread you is the Diagnostician: you interrogate the claim, they interrogate the person, and to their ear your friction sounds like not listening. When you write for Diagnosticians, and for tired readers generally, name the belief you're attacking before you attack, so nobody at the table wonders if the belief is them.
Chapter 7
🛠️The DemonstratorShow-first. "Here, it's easier if I just show you."
Your hand is already moving before the question ends. Toward a napkin, your phone, their laptop. "Here, it's easier if I just show you." You explain through your hands, narrating while you work, and the doing carries the point. When a client asks a question on a call, you're sharing your screen before you finish your first sentence, walking them through a real one instead of describing a hypothetical one. Your answer isn't a principle you state; it's a thing you perform, live, on actual material. Watch yourself at dinner: everyone else is talking, and you're the one who just cleared the plates aside to lay something out.
The closest research anchor for your type is the worked-example effect. In the founding study, algebra students who studied fully worked solutions instead of grinding through equivalent practice problems solved new problems in roughly half the time with a fraction of the errors (Sweller & Cooper, 1985). The finding has held up unusually well since: a meta-analysis of 55 studies found a solid medium effect on performance (Barbieri et al., 2023). Walking someone through a complete, real case is one of the most reliably measured teaching moves there is.
The same literature sets two limits, and Demonstrators should know both. First, the advantage fades and can reverse as your audience gets more expert (Kalyuga et al., 2003). Beginners need the full walkthrough; seasoned practitioners can learn more from wrestling with the problem themselves, and a step-by-step demo slows them down. Know which room you're in. Second, the benefit transfers poorly beyond problems that resemble the demo, unless the examples vary (Paas & van Merriënboer, 1994). One demo teaches your process on one case. Three different cases teach the process.
One more boundary. This research shows that demonstration teaches procedures to novices; it does not prove show-first is the best way to explain every kind of idea. The type name itself borrows vocabulary from Anthony Grasha's teaching-styles framework, where the Demonstrator echoes his Personal Model, the teacher who says "watch me do it, then try it my way" (Grasha, 1994). Grasha insisted nobody is one style: the mix shifts with the audience and the material.
Lead formats, where showing beats saying:
Workable with adaptation: case studies organized around the artifact, screenshot carousels with step captions, webinars built on one live build.
Fights you, so ration them: pure-text essays, abstract opinion threads, any channel where there is nothing to point at. Text flattens you; that's a fact about the channel, and it says nothing about your talent.
You skip the why. To you, the demo self-evidently contains it, so you narrate the what and let the reasoning stay silent. Beginners copy your steps without the judgment underneath and stall the first time their case differs from yours, which the transfer research predicted. Fix it by saying the fork out loud: at each meaningful step, name the thing you almost did instead and why you didn't. "I'm compressing this image now, not at the end, because..." costs you five seconds and turns a recording into teaching. Your second cost is channel mismatch. When a format gives you nothing to show, you go quiet and conclude you have nothing to say. You do; it just needs a screen.
Demonstrators marry Mapmakers: your walkthrough plus their structure is the definitive guide people bookmark. With a Campfire secondary you become the build-in-public storyteller, where the demo has an arc and a stumble in the middle. Your nearest neighbor is the Campfire, and the difference is tense: they tell the story about the doing, you do it live. A Mapmaker watching your flawless demo will ask where the framework is; that's the misread to plan for. When you're writing for Mapmakers, state the rule you're following once per section, then get back to your hands.
Chapter 8
🩺The DiagnosticianQuestion-first. Answers your question with two better ones.
A friend asks, over dinner, whether she should quit her job. You say: "What would have to be true for you to stay?" Twenty minutes later she has her answer, she's grateful, and you said maybe forty words. That's the tell. You physically cannot prescribe before you've palpated. When a client opens with "what should I do," your first move is intake: what have you tried, what happened, what does good look like to you? The advice you eventually give lands harder than anyone else's, because by the time it arrives it's made of their own material. People leave conversations with you feeling seen, because the explanation was built live, out of their answers, in front of them.
Your anchor literature is the research on Socratic questioning, read with its caveats attached. In cognitive therapy, sessions where the therapist leaned harder on Socratic questions were followed by slightly larger improvements in the client's symptoms (Braun & Strunk, 2015), and a follow-up traced why: the clients had revised their own thinking rather than accepting someone else's (Vittorio et al., 2022). That is your whole method in one finding. People change their minds when the new idea is assembled from their own answers. The counterweight matters too: reviewers caution that no study has yet shown that asking beats simply telling (Clark & Egan, 2015), so hold the superiority claim loosely. Tutoring research adds a twist: it isn't the number of questions a tutor asks that predicts learning, but whether the learner gets pushed to generate their own explanations (Graesser & Person, 1994; Chi et al., 2001). Quality over volume. Two good questions beat nine reflexive ones.
About the label: the question-first posture loosely echoes the Facilitator style in Anthony Grasha's teaching-styles framework (Grasha, 1994), but Grasha himself found that every teacher blends all the styles and shifts the mix with the room. Elicitation is the mechanism; Diagnostician is our name for defaulting to it.
Lead formats, your intake productized:
Workable with adaptation: case teardowns framed as "here's what I'd ask first"; podcast guesting, if you warn the host you'll interview them back.
Fights you, so don't measure yourself here: hot-take threads, manifesto posts, anything that demands a thesis in line one with nobody in the room to examine.
You withhold. Someone asks a direct question and gets two better ones back, which is generous in a session and maddening in a comment section. Part of your audience wanted the answer, and to them your questions read as evasion, or worse, as a meter running. The deeper cost is that you chronically under-publish your actual point of view. Eliciting is your reflex; declaring feels like malpractice without an exam first. But content is a room where the patient isn't present, and a feed full of questions with no verdicts builds a reputation for wisdom without a position. The counter-move is a ration: for every piece built on questions, force one verdict piece that begins "In most cases, I tell people to." Your defaults exist. You apply them every week. Publishing them costs you nothing but discomfort, and they're the content that lets a stranger decide to hire you.
Diagnosticians build with Mapmakers: your questions plus their drawers is the self-assessment, the decision tree, the "which kind are you" piece that gets forwarded to one specific person. With a Translator secondary you're the advice columnist whose questions arrive carrying an analogy, so readers see their own situation before you've said a word about it. Sparring Partners misread you most: you both open interrogatively, but they're challenging the claim while you're examining the person, and they'll take your intake questions as an invitation to fight. The reader most likely to misread you is anyone in a hurry. When you write for them, put your default answer in the first line and let the questions earn their keep underneath it.
Chapter 9
If your quiz result felt 80% right, this chapter is the other 20%.
Nobody runs one style. Grasha found the same thing about teachers: everyone carries all the styles and shifts the mix with the room. What the quiz measured is your order of operations, the move you make first when nobody is prompting you. Your result came as a stack for that reason: a primary type and a secondary. The primary is your home base. The secondary is the flavor, and it's usually what separates you from everyone else who shares your primary.
The pairings matter because they unlock formats neither type owns alone.
Campfire × Mapmaker tells the story, then names the pattern. This is the case-study-that-teaches, the most trusted format in consulting content. Campfire × Sparring Partner is the parable with a villain: "everyone told her to do X; here's what happened when she didn't." Enormously shareable, because it lets the reader take a side. Mapmaker × Translator produces the named framework people can actually repeat, because every category comes with an analogy handle. This is the combination that ends up as keynote titles. Mapmaker × Sparring Partner writes the takedown-with-a-better-map: "stop using the funnel; here are the three loops that replaced it." Translator × Campfire wraps one extended metaphor around one true story, the signature move of the best explainer newsletters. Sparring Partner × Diagnostician argues by cross-examination, the debate podcast guest who wins with questions. Demonstrator × Mapmaker turns a live build into a numbered system: watch me do it, then here's the checklist you keep. Demonstrator × Campfire is build-in-public with an arc, progress updates people follow like a series. Diagnostician × Translator coins the analogy that makes a client feel seen: "your pipeline isn't broken, it's a garden hose with six kinks." Diagnostician × Campfire turns anonymized client questions into story-shaped advice columns.
Two practical rules for working your stack. Lead with your primary when the format decision is yours; the lead formats in your primary's chapter are still the ones to build your cadence on. Borrow your secondary when a format demands it: a Campfire with a Mapmaker secondary can survive making framework carousels by telling the one-sentence story of where each framework came from. And if a chapter's failure mode paragraph stung twice, once for your primary and once for your secondary, that's normal. The costs stack too.
A note on sharing your result, since the stack line is built for it: the useful comparison isn't "which type is best." It's who covers your blind side. The colleague whose stack mirrors yours in reverse is the one who should be reviewing your drafts, and you theirs.
Chapter 10
A typology you never test is a horoscope with citations. So test it.
The protocol is one week, four pieces of content, and one comparison you run on yourself. Publish three pieces in your lead formats, the ones your type's chapter listed first. Publish one piece in a format from your "fights you" list. Same effort budget for each. Then compare two numbers you don't need an analytics degree to read.
Felt effort. How long did each piece take, and how much of that time was dread? Be honest about the difference between "this took 40 minutes because I was shaping it" and "this took 40 minutes because I rewrote the first line nine times." Lead-format work tends to produce the first kind of slow; fighting-format work produces the second.
Response quality. Not just reach. Look at who responded and what they said. Lead-format content typically pulls replies that sound like your actual clients ("this is exactly the situation we're in"), because it carries the version of you that clients buy. Fighting-format content, when it works at all, tends to pull empty engagement.
Three rules to keep the test fair. Don't pick your easiest topic for the lead formats and your hardest for the fighting one; use topics of similar weight. Don't judge anything by its first hour; give each piece its full platform lifespan. And produce all four the same way: out loud first. Talk each piece into a draft before you type a word of it, because the entire premise of your result is that your explaining voice is the asset. If you talk the drafts through an interview (this is what Xtraktr is for, and by now you know which steering mode is yours), the lead-format pieces should come out close to done. That's the tell you're looking for.
What you'll probably find is what this book predicts: the formats built from your natural explaining move cost less to make and land better with the people you want. The research in each chapter supplies the mechanism; this week supplies the evidence about you. If the week proves otherwise, trust the week. The quiz measured a home base, not a ceiling, and some people have spent enough years in an adopted style that it has become the real one. Either way you'll finish the week knowing your answer, which is more than the sermon about consistency ever gave you.
One last thing. You now know your type, your formats, and your extraction method. The bottleneck left is the one this book started with: the gap between how good you are out loud and what ends up published. That gap is a tooling problem now, and tooling problems are solvable this afternoon.
Appendix
Every research claim in this book is bounded by what these sources actually found, caveats included. Where a type label goes beyond the research (and it does; the science describes mechanisms, the labels describe habits), the chapter says so in the text.
Find your type
Eight questions about what you already do at the dinner table.
Take the 60-second quizThen get it out of your head: Xtraktr interviews you out loud and turns your answers into your type's formats, on your iPhone.