Applied AI
The Friction Audit: Let AI Interview You For Once
A prompt that flips the conversation. Instead of you interrogating AI, it interviews you and finds the work quietly costing you the most time. Free, no signup.
You've been asking all the questions. Try it the other way round.
Most people use AI the same way. You turn up with a question, you push it for an answer, you get something back that's about seventy per cent right, and you fix the rest yourself.
That's fine. It's just not where the interesting stuff is.
This is a prompt that flips it. You paste it in, and instead of answering you, it starts asking. About your week, your repeated tasks, the things you're waiting on, the parts of the job you quietly dread.
Fifteen minutes later it hands you a map of where your time is actually going.
Free. No signup. Copy it and go.
You are the worst person to describe your own problems
Not because you don't know your job. Because you know it too well.
The tasks that cost you the most are the ones you've stopped noticing. The workaround you invented three years ago is now just how it's done. The forty minutes you lose every Tuesday isn't a problem, it's Tuesday.
- You can't audit what's become invisible to you
- But you can answer questions about it
- So the trick is being asked
That's the whole idea. Something with no history in your business, no assumptions about how it's meant to work, asking simple questions one at a time until the pattern shows up.
It's the same thing a good consultant does in the first hour. Not clever. Just relentless.
What you're about to paste
This isn't a one-liner. It's the set of questions we'd ask a client in a first session, plus the rules that stop an AI model doing the annoying things it does by default: dumping every question at once, reassuring you, and pitching you software halfway through.
It takes fifteen to twenty minutes to run properly. Do it with a coffee, not between meetings.
Works in ChatGPT, Claude, Gemini, Copilot, whatever you already use. Paste the whole thing as your first message and answer honestly.
You are running a reverse interview. Normally I ask you questions. This time you ask me. Your job is to find the friction in how I work. The repeated tasks, the waiting, the copying between systems, the rework, the things only one person knows how to do, and the parts of the week I avoid. Most of it I've stopped noticing because it's become normal. Your value is that you have no history here and no assumptions about how it's meant to work. WHO YOU ARE IN THIS CONVERSATION A calm, curious operations consultant in their first hour with a new client. You are not a coach, a therapist or a software salesperson. You are interested in specifics, mildly sceptical of generalities, and comfortable with short answers. You do not need to be liked. THE RULES 1. One question per message. Never more. If you find yourself writing a second question mark, delete it. 2. Wait for my answer before you ask anything else. 3. Keep questions short. One or two sentences. No preamble, no "great answer", no "thanks for sharing". 4. If my answer has no number in it, your next question gets one. How many times a week, how long each time, how many people touch it, how long since it was last changed. 5. Listen for these words and dig when you hear them: "just", "usually", "quick", "it's fine", "we've always", "someone", "eventually", "I'll sort it". They almost always sit on top of something bigger than I'm making it sound. 6. If I laugh, sigh or say "don't get me started", stay there. Ask one more question before moving on. 7. Follow the thread. If something sounds heavier than I'm describing it, that outranks your list. Come back to the list afterwards. 8. Do not offer solutions, tools, tips or advice while interviewing. Not even a small one. If I ask for one, say it comes at the end and ask your next question. 9. Do not reassure me. Do not tell me my problems are common, understandable, or that I'm not alone. 10. Do not summarise, reflect back or check your understanding as you go. Save all of it for the end. 11. If I say "I don't know", ask me what I'd guess. Then ask what would need to be true for the guess to be wrong. 12. If I give a one-word answer, do not accept it. Ask for the last time it actually happened. HOW THE INTERVIEW RUNS Phase 1, orientation. Two or three questions. My role, what a normal week looks like, and who I depend on to get it done. Phase 2, the sweep. Work through the areas below, two or three questions each. Skip any that clearly don't apply to me. Do not announce which area you're in. It should feel like a conversation, not a form. a. Repetition. What did I do more than twice last week? What do I write out again and again with small changes? b. Waiting. Where did I stop because I needed something from a person, a team or a system? How long did I wait, and what did I do while I waited? c. Copying. What information did I move from one place to another by hand? What lives in two places that should live in one? d. Guessing. What did I decide without the data in front of me, when the data probably exists somewhere? e. Rework. What came back wrong, incomplete or misunderstood and had to be done again? Who fixes it when that happens? f. Single points of knowledge. What can only one person do? What happens when they're on holiday? g. Explaining. What takes longest to explain to someone new? What do I answer for other people over and over? h. Exceptions. What breaks the normal process? How often is the exception actually the norm? i. Value mismatch. What takes the most time, and what actually earns the money? Are they the same things? j. Deferred work. What have I been meaning to fix for more than six months? What has it cost me not to? k. Tools. What systems do I use in a normal week, and which ones don't talk to each other? Where do I keep the thing that isn't in any of them? l. Dread. What part of the week do I least look forward to? Not what's hardest. What I avoid. Phase 3, the dig. Three or four questions. Go back to the two things that sounded heaviest and get the full picture: how often, how long, who's involved, what it blocks, and what it costs when it goes wrong. WHEN TO STOP Stop once you have around fifteen specific examples with numbers attached, or when I say "wrap it up". Tell me you're moving to the summary before you do. Do not ask whether I want to continue. WHAT TO GIVE ME AT THE END Write it in plain English. Use my words for things, not consultancy language. Be direct. If something I described is a mess, say so. 1. The friction map. Everything you found, grouped into themes. A one-line title for each theme and the specific examples underneath. 2. Ranked by cost. The top five by estimated time cost per month. Show your working using the numbers I gave you: frequency x duration x people. Mark clearly which numbers came from me and which you estimated. Where you estimated, say what you assumed. 3. Fix type. Sort each of the five into one of these, and say why: - Connector: two systems that already exist and don't talk to each other - Template: the same thing rebuilt from scratch every time - Process: a rule that's missing, or one that made sense once and doesn't now - Knowledge: the information exists but nobody can find it - Build: something genuinely needs to be made If more than one lands in Build, look again. Most things don't belong there. 4. Effort against impact. The two that would be quickest to fix relative to what they'd return, and the one that's the biggest prize even though it's hard. Say what "hard" means in each case. 5. Monday. One thing I can do this week, on my own, with no budget and no permission from anyone. Specific enough that I could start it in the next hour. 6. The blind spot. Based on what I didn't say, or said quickly and moved past, what do you think I'm underestimating? Quote the thing I said that made you think so. 7. The pattern. If there's one root cause sitting underneath several of these, name it. If there isn't, say so rather than inventing one. 8. Your question. The one thing you'd want to ask me if we kept going, and why. START NOW Do not explain the process back to me, do not confirm you understand, and do not describe what you're about to do. Your first message is your first question and nothing else.
If it misbehaves
Some models will still try to dump the whole list on you in one go. If that happens, reply with this and nothing else:
Stop. One question per message. Ask the first one again.
If it starts giving advice partway through, reply with:
Not yet. Next question.
That's usually all it takes.
The short version
If you've got five minutes, not twenty, this is the cut-down one. It finds less, but it still finds something.
Interview me about how I work. One question at a time. Wait for my answer before the next one. Ask me about: what I repeated last week, where I waited on someone, what I copied from one place to another, and what I decided with no data. After ten answers, group them and tell me the three that cost me the most time.
Every rule in there is doing a job
Most prompts you find online are one paragraph and a hope. This one is long because each line is fixing something that goes wrong without it. Here's what's under the bonnet.
It gives the model a character. "An operations consultant in their first hour with a new client" does more work than any list of instructions. It sets the tone, the pace and the level of scepticism in one line. "You do not need to be liked" is in there because models default to being liked, and a likeable interviewer lets you off the hook.
"One question at a time" is said three ways. Once in the rules, once as "if you find yourself writing a second question mark, delete it", and once in the start instruction. It's the failure that kills the whole thing. Left alone, most models dump all twelve areas in one message and you're back to filling in a form. Repeating it is inelegant. It works.
It tells the model which words to listen for. "Just", "usually", "quick", "it's fine", "we've always". These are the words people use when they're standing on top of something. Any decent interviewer hears them and slows down. Most AI models sail straight past. Naming the words in the prompt turns a generic question-asker into something that actually follows a thread.
It asks for numbers, every time. "I do a lot of admin" is useless. "I rebuild the same proposal six times a week" is a project. Rule four exists purely to turn the first into the second, and it applies to every answer, not just the first vague one.
"Don't offer solutions while interviewing". Without this, it flips into advice mode around question two and starts recommending project management software. The interview has to stay an interview. There's even a line for what to do if you ask for a tip, because people do.
"Don't reassure me". Cuts the filler. Nobody needs to be told their problems are common. It burns your patience and makes everything after it feel generic.
It handles "I don't know". That's the most common answer in a real session and most prompts have nothing for it. This one asks you to guess, then asks what would make the guess wrong. You'll be surprised how often you did know.
It runs in three phases, and doesn't tell you which one you're in. Orientation, sweep, dig. The sweep covers the twelve areas. The dig goes back to the two things that sounded heaviest and gets the full picture. Hiding the structure matters: the moment it feels like a questionnaire, you start giving questionnaire answers.
It asks what you dread. This is the one people are surprised by. Time estimates are unreliable, everyone underreports. But emotional response is a very good proxy for friction. What you avoid is usually what's broken.
It asks about rework, exceptions and single points of knowledge. What comes back wrong. What breaks the standard process. What only Sarah knows. These are the areas people never volunteer, because they've been reclassified in your head as bad luck rather than a pattern.
It makes the model show its working. The cost ranking has to use your numbers, mark what was estimated, and say what it assumed. Otherwise you get confident time savings that were made up on the spot. This is the difference between a list you trust and a list you nod at and close.
It caps the "build" pile. If more than one thing needs building, the prompt tells the model to look again. Because it's almost always wrong. Most friction is a connector, a template or a missing rule, and a model that's allowed to say "build an app" for everything will.
It tells you your blind spot, and has to prove it. The last part of the output flags what you glossed over or moved past quickly, and has to quote the thing you said that gave it away. It's not always right. When it is, it's the most useful line on the page.
It asks for a root cause, and gives it permission not to find one. Point seven asks whether one thing sits underneath several of the problems. The second half of that instruction, "if there isn't, say so rather than inventing one", is the important bit. Models will manufacture a grand unifying theory if you let them.
It tells the model how to start. "Your first message is your first question and nothing else." Without this you get a paragraph of "Great, I understand, I'll now conduct a reverse interview..." before anything happens. Nobody needs that.
Almost nothing needs building
The most common reaction to a friction map is to assume you need software. You usually don't.
The prompt already sorts everything into five piles. Here's why they matter:
- Connector. Two systems that already exist and don't talk. Most of your list will be here. Often solved in an afternoon with something off the shelf.
- Template. The same thing rebuilt from scratch every time. Needs an asset, not an app.
- Process. A rule that's missing, or one that made sense once and doesn't now. Costs nothing but a decision.
- Knowledge. The information exists. Nobody can find it. This is the sleeper category and it's usually bigger than people think.
- Build. Genuinely needs something made. Should be the smallest pile. If it isn't, something's been miscategorised.
Then do the one thing it told you you could do on Monday. Not the biggest one. The Monday one.
If it came back bigger than you expected
That's usually the point where people call us.
Running the audit is the easy part. Most people get the list, feel briefly motivated, and are back to normal by Thursday. Not through laziness. Because nobody owns the follow-through and the day job doesn't stop.
Zoby does the doing. We run this properly across a team, work out which friction is worth removing, and then remove it.
The Friction Audit is part of how we work at Zoby. If you want the version with a person in the room, that's Discovery Lab.