You've written the book. The chapters are done. The acknowledgments are drafted. Now you're staring at a blank page that sits before Chapter One, and someone — maybe your editor, maybe a writing blog — told you that you need a preface.
So you sit down to write it. And you freeze.
Because what even is a preface? Is it an introduction? Also, a prologue? A place to thank your cat? And most authors get this wrong. I've seen prefaces that should've been introductions, introductions that were really chapter ones in disguise, and prefaces that read like diary entries the author forgot to delete.
Let's clear this up once and for all.
What Is a Preface
A preface is a short section written by the author that explains why the book exists and how it came to be. Worth adding: that's it. It's not part of the book's argument or narrative. Now, it's meta. It sits outside the work proper — usually before the introduction, before the table of contents, sometimes even before the foreword (if there is one).
Think of it as the author stepping onto the stage before the play starts. House lights still up. "Hey, here's why I wrote this, and here's what you should know before you dive in.
Preface vs. Introduction vs. Foreword vs. Prologue
This is where everyone gets tangled. Here's the cheat sheet:
- Preface: Written by the author. About the book's origin, purpose, scope, or methodology. Optional.
- Introduction: Written by the author. Part of the book's actual content. Sets up the argument, defines terms, maps the road ahead. Expected in nonfiction.
- Foreword: Written by someone else* — usually an expert or known name. Lends credibility. Signed with their name, not yours.
- Prologue: Narrative device. Part of the story. Fiction only. Sets up events before Chapter One.
If you're writing a memoir, you might not need any of these. Plus, if you're writing a technical guide, you probably need an introduction but can skip the preface. In real terms, if you're writing a revised edition of a classic text? Preface is standard — you're explaining what changed and why.
Why It Matters
Readers skip prefaces. On the flip side, a good preface tells them: this author knows their scope. Let's be honest. This author has humility. Most people flip past them. But the ones who don't* skip — reviewers, librarians, professors, serious readers — they're looking for signals. This book has a reason to exist.
A bad preface signals the opposite: ego, confusion, or filler.
I once reviewed a business book where the preface ran twelve pages. Twelve. It name-dropped the author's mentors, summarized every chapter in detail, and included a paragraph about the author's morning routine. By page three, I didn't trust the book. If the author can't distinguish between "why I wrote this" and "what this book says," how sharp is the thinking inside?
The preface also serves a practical function. It's where you:
- Define the audience (and who isn't* the audience)
- Explain your methodology or sources
- Note limitations or biases
- Contextualize a revised edition
- Disclose conflicts of interest
Skip it, and you risk looking sloppy. Overdo it, and you look self-indulgent.
How to Write a Preface That Earns Its Page
There's no single template. But every strong preface hits a few core beats. Here's how to build yours.
1. Start with the spark
What moment made this book necessary? Still, " That's background. Not "I've always been interested in X.The spark is specific: a conversation, a failure, a gap you noticed, a question no one answered.
Example*: "In 2018, a junior designer on my team asked me why we still used waterfall planning for digital products. I didn't have a good answer. That question became this book.
That's a preface opener. It's personal, concrete, and immediately tells the reader what problem the book solves.
2. State the book's promise in one sentence
Not a summary. A promise. What will the reader walk away with?
"This book teaches product teams how to run lightweight discovery cycles that fit inside two-week sprints."
Done. Now the reader knows the contract. If they don't want that, they can put the book down — and that's a win for both of you.
3. Explain your authority — briefly
Why you? Not your resume. Your lens*.
"I've spent fifteen years leading design teams at Series A startups. I've shipped products that flopped and products that scaled. This book comes from the scars, not the wins.
That's credible without being arrogant. It also signals perspective: this isn't academic theory. It's field-tested.
4. Define the scope and boundaries
What's not in the book? This is the move most authors skip — and it's the one that builds the most trust.
"This book doesn't cover enterprise sales cycles or hardware prototyping. It focuses on software product discovery in teams of three to twenty people."
Readers appreciate honesty. Practically speaking, it prevents the "but you didn't cover X! But reviewers really* appreciate it. " complaint before it starts.
5. Address the edition (if relevant)
Second edition? Third? That's why new foreword? Consider this: updated data? Say so — and say why.
"The 2024 edition adds a chapter on AI-assisted discovery, rewrites the metrics section based on new benchmark data, and removes the now-obsolete chapter on paper prototyping."
That's useful. "This edition has been fully revised and updated" is not.
6. Thank people — but keep it tight
A preface isn't the acknowledgments page. "Thanks to my editor, my partner, and the teams who let me test these ideas on their projects.Think about it: one short paragraph. " Done. Maybe two sentences. Save the long list for the back.
7. End with an invitation
The last line should nudge the reader forward. Not "I hope you enjoy this book." That's passive.
Want to learn more? We recommend are wax melts bad for you and journal of applied materials and interfaces for further reading.
"Turn the page. Let's build something that works."
Or: "Chapter One starts with the mistake almost every team makes in week one."
Give them momentum.
Common Mistakes (And How to Avoid Them)
Mistake 1: Writing an introduction and calling it a preface
If your "preface" defines key terms, outlines the book's structure chapter by chapter, or presents the core framework — that's an introduction. Move it. Label it correctly. The preface stays meta.
Mistake 2:
Mistake 2: Turning the preface into a “how‑to” manual
What it looks like – A paragraph that walks the reader through the author’s research process, interview scripts, or data‑collection tools.
Why it fails – The preface is a contract, not a tutorial. Readers who want the methodology can find it in an appendix or a separate workbook.
How to fix it – Keep the focus on why the book exists. If a process detail is essential to the promise, weave it into the relevant chapter instead.
Mistake 3: Ignoring the reader’s time
What it looks like – A lofty introduction that spends five paragraphs defining “discovery” before landing on the promise.
Why it fails – Readers scan prefaces in seconds. Every extra word is a cost they’ll subtract from the value they expect.
How to fix it – Write in reverse: start with the promise, then prune everything that doesn’t directly support it. Aim for under 150 words total.
Mistake 4: Making the promise vague
What it looks like – “This book will help you improve your product process.”
Why it fails – Vague promises give readers no concrete expectation, leading to mismatched hopes and disappointing reviews.
How to fix it – Quantify the outcome. Example: “This book teaches product teams how to run lightweight discovery cycles that fit inside two‑week sprints and reduce rework by at least 30%.”
Mistake 5: Forgetting to close the loop
What it looks like – A preface that ends with a generic “Thank you” but never reinforces the contract.
Why it fails – The reader is left without a clear call‑to‑action or reminder of what they’ll gain.
How to fix it – End with a forward‑looking line that ties back to the promise. “Turn the page and start building discovery cycles that actually move the needle.”
Mistake 6: Over‑credentialing
What it looks like – A preface that reads like a LinkedIn profile: “15+ years of UX leadership, MVP launches at Fortune 500s, published speaker at XYZ conferences…”
Why it fails – Credentials become noise unless they directly illustrate the lens you bring to the promise.
How to fix it – Use a single, vivid anecdote that shows perspective. “I learned the hard way that a polished prototype can mask a flawed problem statement; that lesson fuels every framework in this book.”
Mistake 7: Skipping the scope disclaimer
What it looks like – No mention of what the book doesn’t* cover, assuming readers will infer boundaries from the chapters.
Why it fails – Readers waste time (and money) expecting guidance on topics that aren’t there, and they blame the author.
How to fix it – Add a brief, honest line. “This book focuses on software product discovery for teams of three to twenty people; it does not address enterprise sales cycles or hardware prototyping.”
Putting It All Together
A strong preface is the silent handshake that turns a book into a partnership. Use the seven steps above to write one that respects both you and your reader:
- Open with a concrete problem the reader faces.
- State a single, actionable promise that tells the reader exactly what they’ll walk away with.
- Explain your authority through a lens, not a résumé.
- Define scope and boundaries up front.
- Address any edition‑specific updates and why they matter.
- Thank key contributors in a tight paragraph.
- End with an invitation that propels the reader into the first chapter.
Avoid the common mistakes—over‑loading with process, wasting time, vague promises, missing the loop, over‑credentialing, and neglecting scope—so the preface feels like a
Final Thoughts
A preface isn’t a marketing brochure or a résumé; it’s the first handshake between you and the reader. When you follow the seven‑step recipe it becomes a clear, honest invitation that sets the stage for the learning journey inside the pages.
- Problem‑first, promise‑second keeps the narrative focused on the reader’s pain point.
- A lens, not a list of accolades turns authority into a relatable story.
- Scope, scope, scope prevents mis‑aligned expectations and saves everyone time.
- Closing the loop gives the reader a tangible next step and a sense of purpose.
By treating the preface as a living contract, you let the reader know exactly what they’ll gain, why you’re the right guide, and how the book will fit into their workflow. The result is a preface that feels like a partnership rather than a preamble, and a book that delivers on its promise from the very first page.
Now that you have the blueprint, it’s time to write that handshake. Open the first chapter with confidence, knowing the preface has already built the bridge you’ll cross together.
