Business understanding interview

What outcomes matter to this person and to the business? How do they know whether work went well? What creates revenue, cost, delay, risk, customer value, or operational pain? Do not assume the stated metric is the real objective. Ask why it matters and what happens when it moves.

Follow a real case end to end. Identify: what triggers the work; who touches it; what information arrives with it; what systems are used; what decisions are made; what gets handed off; what waits; what can go wrong; and what marks the work complete. When the employee says "then we do X," ask what actually happens next rather than immediately abstracting it into a workflow box.

Pay special attention to moments where an experienced employee says things like: "it depends"; "you just kind of know"; "normally"; "unless"; "I always check"; "I would never"; "if this happens, then..."; or "the new people usually get this wrong." These are candidate decision rules, exceptions, and training material. Ask for the reason and for a concrete example.

For every important judgment, ask what information the employee looks at and where it comes from. Prefer inspectable artifacts over recollection when possible. Examples include: CRM records; email threads; spreadsheets; estimates; contracts; calendars; accounting records; price books; photos; tickets; call recordings; documents; dashboards; and external data sources. "Show me the last one" is often the most useful follow-up in the interview.

Do not treat an awkward process as accidental until you know why it exists. A manual step may encode a legal requirement, trust boundary, customer expectation, exception-handling mechanism, or hard-won operational lesson. Ask why before proposing automation.

Look for problems with meaningful consequence rather than generic annoyance: lost revenue; slow response; margin leakage; rework; errors; missed follow-up; customer uncertainty; poor handoffs; duplicated data entry; dependence on one experienced person; inability to answer a recurring question; or work that cannot scale with demand. Ask how often it happens and what it costs in time, money, risk, or customer experience.

Ask what a new employee takes longest to learn, what mistakes they make, which decisions require supervision, and how experienced people explain the work today. This is not merely onboarding research. It helps locate tacit knowledge that may belong in the business understanding system and later power the handoff layer.