Interviewing a Local Owner for Your Cafe Blog Step by Step

Jacob Mishalanie

Oct 7

11 min read

You want to sit down with a neighbor, a roaster you buy from, or another owner down the block and turn that conversation into something worth reading. Short answer: a good interview post comes from a short, prepared conversation that you record, edit lightly, and let the person you talked to actually approve before it goes anywhere near the internet. None of that requires a journalism degree. It requires a little preparation and a lot of respect for the person giving you their time.

This walks through the whole thing, start to finish. The questions worth preparing, eight to ten of them, most of them open ended. The shape the finished post should take, so a reader gets the point fast instead of scrolling through a raw transcript. And the permissions piece, the part people skip and then regret, covering consent, review and the right for your subject to pull a quote they are not comfortable seeing in print. By the end you should have one interview requested, prepared and on the calendar.

The Questions

Prepare eight to ten questions before you ever reach out, not because you will ask every single one in order, but because having them written down keeps a conversation from stalling into small talk. Aim for five of them to be genuinely open ended, the kind that cannot be answered with a single word: how did you end up doing this, what changed about the work over the years, what do you wish people understood about it, what is a mistake you learned something real from. Closed questions have their place for filling in facts, when did you open, how many people work here, but a whole interview built from them reads flat.

Order matters more than people expect. Start with something easy and factual, a warm up that lets the person settle into talking before you ask anything that requires real reflection. Save the more personal or harder question, the one about a mistake, a hard year, a doubt they had, for the middle of the conversation once there is some trust built, not the opening question, which can feel like an ambush before anyone has warmed up.

Leave real room for follow up questions that are not on your list at all. The best line in an interview post is almost never the answer to a question you planned. It is the thing that comes out when you ask, wait, tell me more about that, in response to something the person just said in passing. Treat your written list as a floor to stand on, not a script to read from top to bottom without deviating.

The Structure

A raw transcript is not a blog post, and one of the most common mistakes a first time interviewer makes is publishing something that reads like one anyway. The reader's actual question, why should I care about this conversation, needs an answer near the top, not buried three screens down after a long introduction about how you met the person. Open with a short, direct answer: who this person is, why they are worth hearing from, and the one thing from the conversation most worth knowing, stated plainly in the first few lines.

After that short answer, a brief fact box works well, the person's name, their role, how long they have done the work, maybe one detail that grounds them as a real, specific person rather than a generic voice. Then the body of the post: three to five real quotes, each one given enough surrounding context that a reader who was not in the room understands what question prompted it and why it matters, rather than a quote dropped in with no framing at all.

Close with a next step, something concrete a reader can actually do: visit the place, try something the person mentioned, follow their work somewhere else. An interview post without a next step tends to just end, leaving the reader with a nice read and nothing to do with it. A next step turns a good conversation into something that moves a reader from reading to doing.

One structural habit worth building early: write the short answer at the top last, after you have already picked your three to five quotes. It is much easier to summarize a conversation accurately once you already know which parts of it made the final cut, rather than writing a summary first and discovering later that your best quotes do not support what you promised at the top.

The Permissions

Ask for written consent before you publish anything, ideally before you even record, a simple sentence confirming the person understands the conversation may be published, lightly edited for length and clarity, and that they will get to review it before it goes live. This is not about legal protection so much as it is about basic respect for someone who gave you their time and their words. People talk differently, more openly and more honestly, when they trust that what they say will not get twisted or published without a chance to see it first.

Send a full review pass before publishing, not just a courtesy heads up after the fact. Let the person read the actual post, check that their name, title and any factual details are spelled correctly, and confirm every quote attributed to them is something they are genuinely comfortable seeing in print exactly as written. Build in the right to withdraw a quote. If someone reads back what they said in the moment and winces, honor that and cut it, even if it was the best line in the conversation. A slightly less colorful post that a subject is fully comfortable with beats a punchier one that damages the trust you are trying to build with actual local people.

A simple request email covers most of this in a few lines: introduce yourself and the blog, explain roughly what you would like to talk about and why you thought of them specifically, offer a rough time commitment so they can plan for it honestly, fifteen to twenty minutes is a reasonable target for a first interview, and mention plainly that they will see the post before it publishes. That last line alone tends to make people say yes more readily, since it removes the fear of being misquoted or surprised.

Turning a Long Conversation Into a Short Post

A phone voice memo app paired with a basic transcript tool is enough equipment for a first interview. There is no need to buy specialized gear or learn new software before you have even had a single conversation. Record with the person's knowledge, obviously, transcribe it afterward, and expect the transcript to need real editing, since spoken language is full of false starts, repeated words and half finished thoughts that read as messy on the page even when they sounded completely natural out loud.

Light editing for length and clarity means trimming the false starts, joining a broken thought into one clean sentence, and cutting anything repetitive, without changing what the person meant or putting words in their mouth that were not there. If you find yourself needing to add a whole idea that was not said, to make a quote punchier or clearer, that is the line where editing turns into rewriting, and it is worth stopping right there and either leaving the quote as it naturally was or asking the person to expand on it in a quick follow up instead.

A useful test before publishing any quote: read it back exactly as written and ask honestly whether it still sounds like the person, in their own words and rhythm, or whether it now sounds like you, tidied into your own writing voice. A quote that has drifted too far from how someone talks is a sign the edit went too far, even if every individual word technically came from the original conversation.

It also helps to keep the raw transcript on hand even after the post is finished, filed away somewhere you can find it again. If a question ever comes up later about exactly what was said, having the original recording and transcript to point back to is far more useful than trying to remember the conversation from memory months afterward, and it is a small habit that costs nothing to build in from the start.

Choosing Who to Ask First

Your first interview does not need to be the biggest name in town. It is easier to start with someone you already have some relationship with, a roaster you buy beans from, a neighbor who runs the shop two doors down, someone you already see at the farmers market, because a first interview with a total stranger asks you to build trust and conduct your first ever interview at the same time, which is a lot to ask of yourself. Practicing the format with someone who already knows you, even a little, lets you focus on the actual craft of the conversation.

Once you have done one or two of these, reaching further, a farmer who supplies a roaster you feature, an owner in a neighboring town whose shop you admire, gets easier, both because you have a finished example to point to when you make the request and because you will have a better feel for your own rhythm as an interviewer. There is no need to rush toward the most impressive possible subject before you have a comfortable process worked out on someone lower stakes first.

It is also worth thinking honestly about why you are asking a specific person, beyond simply that they said yes. A genuine reason, their coffee changed how you think about sourcing, their shop solved a problem yours also faces, a hard year they got through that other owners are quietly dealing with too, gives the conversation a real spine to build around, rather than a generic set of questions asked of whoever happened to be available that week.

What This Post Is Not

This is not legal advice about defamation or what you can and cannot publish about someone, and any uncertain situation, a subject asking you to remove something after the fact, a disagreement about what was said, deserves a real conversation with the person involved rather than a rule from a blog post. It also is not a promise that an interview post will bring in search traffic or rank for anything specific. That is not why this kind of post is worth doing, and treating it as a traffic tactic rather than a genuine conversation tends to produce a worse, more transactional interview anyway.

The real reason to do this has very little to do with search at all. In the Southeast audit of 201 shops across 53 cities, most cafe blogs, 83 percent, sat empty with zero posts, and the ones that did publish rarely took the time to talk to another real local person and put that conversation into words. A short, honest, well permissioned interview with a neighbor or a fellow owner is a different kind of post than a generic listicle, because it is built entirely from a real conversation that could not have happened anywhere else. That is worth doing for its own sake, whether or not it ever shows up in a search result.

Frequently Asked Questions

How many questions should I prepare for a cafe blog interview?

Eight to ten written questions is a reasonable target, with about five of them open ended rather than answerable in a single word. You will not necessarily ask every question in the order you wrote it, but having the list keeps the conversation from stalling and gives you something to return to if it drifts.

Should I record the interview?

Yes, with the person's knowledge. A phone voice memo app paired with a basic transcript tool is enough for a first interview. Recording lets you stay present in the conversation instead of scribbling notes, and it gives you an accurate source to work from when you write the post afterward. Keep the raw file and transcript filed away after publishing.

Do I need written consent before publishing an interview?

Yes. A simple written confirmation that the person understands the conversation may be published, lightly edited, and that they will review it before it goes live is worth getting before you record, not after. It protects the trust of the conversation as much as it protects you. One sentence in the request email is usually enough.

What should the structure of an interview post look like?

Open with a short, direct answer to why this conversation matters, follow with a brief fact box about the person, include three to five quotes with enough context that a reader understands what prompted each one, and close with a concrete next step the reader can take. Write that opening answer last, once the quotes are chosen.

How do I edit a messy transcript without changing what someone said?

Trim false starts, join broken thoughts into clean sentences, and cut genuine repetition, without adding an idea that was not said. A useful test is reading a quote back and asking honestly whether it still sounds like the person or whether it now sounds like your own writing voice. If a quote needs a whole new idea to work, ask a quick follow up instead.

What if the person I interviewed wants a quote removed?

Honor that request, even if it was the strongest line in the conversation. Building in the right to withdraw a quote during the review pass is part of the basic respect this whole process is built on, and a post the subject fully trusts is worth more than one slightly punchier line. Mention that right in your first request email.

How long should the interview itself take?

Fifteen to twenty minutes is a reasonable target for a first interview, and it is worth stating that rough time commitment plainly in your initial request so the person can plan for it honestly rather than guessing how much of their day you are asking for. Eight to ten prepared questions fit comfortably inside that window.

Should I send the whole post for review or just a summary?

Send the actual finished post, not just a courtesy summary. Let the person read exactly how they are quoted, check spelling and titles, and confirm they are comfortable with every line attributed to them before it publishes anywhere. Give them a few days to read it, and treat any quote they want pulled as cut, no argument needed. That full review pass is the promise that got them to say yes.

Will an interview post help my cafe blog rank in search?

This post makes no promise of ranking benefit, and that is not the actual reason to do this. In the Southeast audit of 201 shops across 53 cities, 83 percent of blogs sat empty with zero posts, and a real conversation with a real local person is a different kind of post worth doing for its own sake.

Can I name the real person and cafe I interviewed?

This post itself avoids naming real people or businesses as examples, but that guidance is about how this piece is written, not a rule against your own interview post naming your actual subject with their full, informed consent, which is normal and expected for a real interview once permissions are in place. Confirm the spelling of both names during the review pass.

Work with Hillcane

You want to talk to a neighbor or a fellow owner and turn it into a real post, but you have never done an interview before. Here is the whole process, start to finish.

If you want help planning a content calendar that includes real conversations like this one, reach Hillcane at hillcane.co/contact or call (256) 384-2449.