Make Your Expertise Easier to Understand

Mike Giannulis shows experts, coaches, and consultants how to find their first book idea in a question they already answer, then capture it in a three-minute recording. One question, one reader, one concrete step.

Show Notes

Turning your expertise into a published book starts with a question you already know how to answer. Mike Giannulis, founder of Dictate, opens this first episode of Talk Your Book Into Existence by drawing a distinction that changes how you think about writing a book: expertise is what you know, and authority is what other people know about you. Those two things are not the same, and a book is one practical way to close that gap. This episode is not a pitch for overnight transformation. It is a concrete starting point. You will learn why the explanations you give every day in client calls, coaching sessions, and workshops are raw material for a book, and why those explanations feel ordinary to you but genuinely useful to someone on the outside. You will walk through a three-part exercise: write down one recurring question your audience asks, record a three-minute spoken answer, and listen back to check that your answer contains a clear problem, a useful explanation, and a specific next step. If all three are there, you have the beginning of a book. Not a chapter plan, not a query letter. A proof of concept you can build on tomorrow. A quick note before we begin: this episode is narrated by an AI-generated voice. the book Talk Your Book Into Existence: https://startdictate.com/talk-your-book

What is Talk Your Book Into Existence?

You already explain your best ideas to clients, colleagues, and audiences. Join Mike Giannulis, founder of Dictate, for practical 10- to 15-minute episodes on turning that spoken expertise into a published book through conversations with an AI interviewer. Each episode gives experts, coaches, and business owners one clear step to capture their ideas, shape their message, and move their book forward.

Episodes of this show are narrated by an AI-generated voice.

Your first useful book idea may be hiding in a question you already answer. Today, choose that question, picture one reader, and turn your answer into material you can build on.

Welcome to Talk Your Book Into Existence with Mike Giannulis, founder of Dictate. Learn how to turn the ideas you already share out loud into a published book, one conversation at a time. Today, you will leave with one practical step you can use on your own book.

A quick note before we begin: this episode is narrated by an AI-generated voice.

Why Expertise Alone Doesn't Speak for Itself.

Let's start with a distinction from Talk Your Book Into Existence that helps explain why communicating your expertise matters.

Expertise is what you know. Authority is what other people know about you.

Those two things are not the same. You can be genuinely excellent at your craft and still be invisible to the people who need you most. One useful place to look is how clearly you communicate what you know. Your knowledge is organized inside your head in a way that makes complete sense to you, and it may be absolutely opaque to someone on the outside looking in.

A book changes that. Not by magic, and not automatically, but in a specific and practical way. When you take what you know and put it in a form that someone else can follow, you're doing something your credentials alone can't do. You're making your thinking accessible. You're removing the barrier between your expertise and the person who needs it.

Now, I want to be careful here, because there's a version of this conversation that turns into a sales pitch for the idea that publishing a book will transform your career overnight. That's not what I'm saying. What I'm saying is narrower and, I think, more useful.

A book is a credentialing device. That is how I describe one of its roles in the book: a reader can use it as an early signal of what you know. It isn't a license or proof that every claim is correct. Imagine a prospective reader looking at a cover and table of contents. Those details can help them decide whether the book addresses a problem they have, even before they read a chapter or speak to the author. The book changes how you're perceived before the conversation even begins.

But notice what that doesn't say. It doesn't say the book guarantees higher fees, or a flood of speaking invitations, or a pipeline full of inbound clients. Those outcomes are possible. Whether they happen depends on your market, how you position the book, and what you do after it exists. The book opens a door. You still have to walk through it.

So the more honest framing, and the one I think actually serves you better, is this: a book gives your thinking a visible, organized form that a reader can return to. It externalizes knowledge that's currently locked inside your head. And once that knowledge is out there, in a form other people can read and reference, you've created something that can work on your behalf in ways that your spoken reputation alone cannot.

That's the gap this show is built around. Not the gap between where you are and some idealized version of your career. The gap between what you know and how clearly it comes across to the people you're trying to help.

If that gap sounds familiar, consider where your useful explanations currently live. Not because you're bad at explaining things. You explain your ideas every single day to clients, to audiences, to colleagues. The problem is that it's scattered. It's contextual. It may never reach anyone beyond the people in that conversation.

A book captures it. It makes it repeatable. It makes it findable by someone you've never met, on a day when you're not in the room.

The useful question is whether you can organize an explanation that helps a particular reader make progress. That is a manageable starting point for a book.

And the first question that argument raises is: where do you actually start? Not with an outline. Not with a chapter structure. With a question.

If you want to work through this process in more detail, my book, Talk Your Book Into Existence, is at startdictate.com/talk-your-book. The link is also in the episode notes.

The Question You Already Answer Every Day.

Here's a practical exercise you can try by paying attention to your own conversations.

Think about the last ten client calls, consultations, or coaching sessions you had. Did the same question come up more than once? If it did, write down how people asked it. Maybe it was phrased differently each time, but underneath the different phrasings, the problem was the same.

A recurring question can be a useful seed for your book. If nothing repeats yet, choose one question you can answer clearly and test whether it matters to your intended reader.

Let me make this concrete with a hypothetical example. Say you're a leadership coach. And let's say you've noticed that a version of the same question keeps coming up in your sessions: my team doesn't follow through on decisions. Every time we make a commitment in a meeting, it dissolves by Thursday. What am I doing wrong?

Now watch what happens when you actually try to answer that out loud. You don't just say, "That's a common problem." You probably say something like: the issue usually isn't the decision, it's what happens immediately after the decision. In this hypothetical team, the meeting ends without a clear owner, deadline, or shared record of what was agreed. So by Thursday, everyone has a slightly different memory of what they committed to.

That's an explanation. That's a problem, a cause, and a direction. You can look for that same shape in an explanation from your own area of expertise.

Now if I pushed you further, you'd give a next step. Something like: the simplest fix is to spend the last five minutes of every decision meeting writing down three things, who owns this, what the specific deliverable is, and what date it's due. Post that to a shared channel before the meeting ends.

For an example, you could describe what that hypothetical team writes down: Alex owns a one-page proposal, it is due Friday, and the group agrees where to find it. Keep an invented example clearly labeled. Use a real client's story only when you have permission and can verify the details.

That's a book. Not yet in the sense of chapters and a cover. But in the sense of raw material. You have a problem your audience actually has, an explanation that teaches them something they didn't know, a concrete next step, and a story that makes it real.

You may have useful explanations in notes, workshops, or one-to-one conversations that feel too ordinary to become book material. They feel ordinary to you because you've thought about the problem so many times that the answer is obvious. But obvious to you is not obvious to your reader.

Here is the thing: your expertise feels like common sense from the inside. From the outside, it's genuinely useful knowledge that other people can't easily access.

That connects to the book's role as a trust signal. Giving a reader a specific explanation lets them examine your thinking for themselves. You can begin building that explanation before you have a chapter outline. Start with the question, identify the person asking it, and decide what they should understand by the end of your answer.

So the practical move here is not to brainstorm a book topic in the abstract. It's to recall a real conversation, a recurring one, and notice what you already say when that question comes up. Notice the explanation. Notice the step you recommend. Notice the example you reach for.

That's your starting material. Not a blank page. A conversation you've already had.

And once you've identified that conversation, one way to capture it is to say it out loud. Not to write it. Not to outline it. Just to explain it, the way you would explain it to a client, and record that explanation.

Three minutes. One question. One answer with a clear next step. That gives you a small piece of material you can review and develop. You don't need to pretend it is already a finished chapter.

Of course, the author is responsible for reviewing and verifying whatever gets captured, shaped, and drafted. That's true whether you're working with an AI tool or a traditional editor. The raw material comes from you. The review comes from you. What changes is the efficiency of what happens in between.

Turn One Recurring Question Into a Clear Starting Point.

So now you have a framework for what a book is and where it comes from. Let me make the application as concrete as possible, because the point of this episode isn't to leave you inspired. It's to leave you with something you can actually do before you listen to the next one.

The exercise is simple, and it has three parts.

First, write down a question your audience, clients, or colleagues repeatedly ask you. One question. You probably thought of two or three already while I was talking. Pick the one that shows up most often, or the one where you feel the most clarity about your answer. Write it down, literally, on paper or in a note.

Second, answer it out loud. Set a timer for three minutes. Record yourself on your phone. Don't write anything, don't outline anything. Just answer the question the way you would answer it in a client session. Name the problem. Explain what most people get wrong about it. Give a specific next step.

Third, listen back and notice whether your answer contains three things: a clear statement of the problem, an explanation that teaches something, and a concrete action the listener could take. If all three are there, you have raw material. If one is missing, record it again and add what's missing.

That's the starting point of a book. Not an outline, not a chapter plan, not a query letter. A three-minute spoken answer to a question you already know how to answer.

Now I want to address something that might be running in the background for you. You might be thinking: but that's such a small thing. How does a three-minute recording turn into an actual book?

The answer is that it doesn't, by itself. One recording isn't a book. But it's a proof of concept. It demonstrates that you have something to say, that you can say it clearly, and that your answer has the shape of useful instruction. If you are unsure whether you have enough material, this exercise gives you something concrete to evaluate. You may discover a useful explanation, a missing example, or a question you need to research before going further.

Use a reader's needs as your editing standard. In the leadership example, 'communicate more effectively' is vague. 'Before the meeting ends, record an owner, a deliverable, and a deadline' gives the reader something to try. Then ask where that advice might need adjustment. A decision that depends on another department may need a named person to resolve that dependency. Adding that limit makes the explanation more useful, without promising the method solves every kind of team problem.

The purpose of this episode was to give that communication a clear starting point. You now have one. A question, a recorded answer, a check for whether the answer contains a problem, an explanation, and a next step.

Before you save the recording as book material, add a short note: who is this for, what question does it answer, and what needs checking? Separate a personal opinion from a factual claim. If you mention a statistic, quotation, or client result, flag it for verification. An AI interviewer can help you explore and organize your answer, but you remain responsible for what the reader eventually receives.

In the next episode, we're going to look at the practical obstacles that keep a book unfinished, even after someone has started. Because beginning is one thing. Sustaining the momentum is a different problem, and it has specific, solvable causes. I'll name them directly and tell you what to do about each one.

For now, do the exercise. Write the question. Record the answer. Listen back. That's one concrete step, and it's the right one.

Your takeaway is one question, one reader, and one recorded answer. Keep the recording, label what needs checking, and choose the next detail your reader would need. That gives your book a concrete starting point you can return to tomorrow.

Take the next small step on your book today. For more guidance, find Talk Your Book Into Existence at startdictate.com/talk-your-book.

Visit startdictate dot com slash talk your book.

Next time on Talk Your Book Into Existence: Find the Obstacle Keeping Your Book Unfinished. An unfinished book can have several causes. Identify whether your next step is making time, narrowing the topic, talking through an idea, accepting a rough draft, or setting a review deadline. Follow the show so the next episode is ready when you are.

Thanks for listening to Talk Your Book Into Existence. Follow the show for your next practical step, and share this episode with someone who has a book in them. Your next conversation could be the start of a chapter.