Articles / Interviews Lie. Watching Tells the Truth
1 month ago 2 min read
Operations & Process

Interviews Lie. Watching Tells the Truth

If you only interview people about a workflow, you will capture the polite version. If you watch the work, you capture the real version.

Back to articles

Key takeaways

What you’ll walk away with

Capture the real steps, not the story

Save the real artifacts

Find the handoffs and the exceptions

You ask someone, "How does onboarding work?" They tell you a clean story. It sounds great.

Then you watch the work for ten minutes and you see the real truth. A form is missing. Someone hunts for an email. A spreadsheet has the real status. A Slack message becomes the handoff.

That gap is why automation projects feel cursed.

Why interviews mislead

People are not lying on purpose. They are describing what they think should happen.

They skip the annoying parts because it feels normal to them. They forget the detours because they do them on autopilot. So your process doc looks clean, but your build breaks the first day.

A real example

A team says, "When a client pays, we onboard them." Sounds simple.

But when you watch, you see a different chain. Payment hits. Someone checks the bank. Someone copies the address from an email. Someone creates a folder. Someone asks in Slack, "Did we get the intake form?" Then the kickoff call gets booked.

If you automate the story, you miss the real inputs and the real handoffs.

What to watch instead

You do not need to shadow people for days. You just need one real run.

Pick one workflow and watch it happen once. While you watch, capture three things.

  1. Trigger: what starts the work in real life? A form, an email, a payment, a call, a Slack message.

  2. Artifacts: what do people touch to make it happen? Save the real stuff: the email, the form, the spreadsheet, the template. These are the system.

  3. Breaks: where does it slow down or get weird? Where does someone ask a question? Where does it get handed off?

The simple fix

When you document a workflow, write two columns:

  • what people say happens
  • what actually happens

Then fix the biggest mismatch first. It is usually a missing input, a handoff with no owner, or an exception that happens every week.

Why this matters

If you build on the fantasy version of a workflow, you get fragile automation and constant rework. If you build on the real version, simple automations start working the first week.

If you want help with this, book a discovery call.

If I watched one workflow in your business for 15 minutes, which one would you pick?

Next step

Want more simple ops notes like this?

Join the SwiftRoot newsletter. Short, practical notes on getting clear before you automate.

No spam. Unsubscribe anytime.

Or

Book a quick discovery call

If you want help picking the right place to start, we can get you clear fast.

Back to articles
by Alek Mlynek
Operations & Process