Q01
Question — Which spreadsheet has created the most confusion when its owner was absent, unavailable, or changing roles?
Uncovers — Key-person dependency, hidden system of record, operational fragility.
Why it stays clean — It asks about an existing spreadsheet and dependency, not spreadsheet preferences.
Follow-up probes —
- Who owns it?
- What decisions rely on it?
- Who else understands the formulas, tabs, and update rhythm?
Polite-answer trap — Useless/evasive: “We have lots of spreadsheets.” Redirect: “Which one has caused confusion when people could not find, update, or understand it?”
Q02
Question — Which WhatsApp groups are operationally important on a live project, and what decisions or records pass through them?
Uncovers — Informal communication channels, evidence leakage, real coordination behavior.
Why it stays clean — It asks about actual groups and content categories rather than messaging opinions.
Follow-up probes —
- Who is in the most important group?
- What happened there yesterday or last week?
- What gets copied out of WhatsApp into a formal record?
Polite-answer trap — Useless/evasive: “WhatsApp is just for quick messages.” Redirect: “What was the last work decision or site update that first appeared in WhatsApp?”
Q03
Question — Which paper forms, notebooks, printed drawings, sign-in sheets, or handwritten logs are still used on site?
Uncovers — Paper persistence, site reality, audit trail gaps, digitization limits.
Why it stays clean — It asks for observed on-site artifacts, not digital aspirations.
Follow-up probes —
- Who fills them in?
- Where do they go afterwards?
- When are they scanned, typed up, filed, or forgotten?
Polite-answer trap — Useless/evasive: “We are mostly digital now.” Redirect: “What paper was physically present on the last site visit or in the last site office?”
Q04
Question — Which whiteboard, wall chart, lookahead board, or informal tracker matters more than the official system on some days?
Uncovers — Local control, official-system mismatch, planning behavior, operational cadence.
Why it stays clean — It asks for a real artifact and comparison with official tools.
Follow-up probes —
- Who updates it?
- Who stands around it?
- What does it show that the official system does not?
Polite-answer trap — Useless/evasive: “The official system has the information.” Redirect: “What is written on the board that people check before opening the system?”
Q05
Question — Which critical process depends on one person remembering who said what, what was agreed, or what needs chasing?
Uncovers — Tacit knowledge, single-person bottleneck, undocumented commitments.
Why it stays clean — It asks for a named dependency in current work.
Follow-up probes —
- Who is that person?
- What happens when they are on holiday?
- What is the last thing only they knew?
Polite-answer trap — Useless/evasive: “People communicate well.” Redirect: “Who gets called when nobody else knows the status?”
Q06
Question — Where does the team repeatedly copy the same information between email, Excel, PDFs, drawings, cost systems, programmes, or project portals?
Uncovers — Manual rekeying, admin burden, data fragmentation, error risk.
Why it stays clean — It asks for an existing repeated action rather than automation interest.
Follow-up probes —
- Who does the copying?
- How often?
- What mistake happened last time the copied data was wrong or late?
Polite-answer trap — Useless/evasive: “There is some duplication.” Redirect: “Which exact field or file is copied most often, and between which two places?”
Q07
Question — What was the last delay, dispute, rework item, missed claim, or client issue where the needed evidence was in a message, spreadsheet, paper note, or someone’s head?
Uncovers — Pain intensity, evidentiary gaps, commercial consequences, workflow risk.
Why it stays clean — It asks for a concrete incident rather than declaring the workaround painful.
Follow-up probes —
- What evidence was missing or hard to find?
- Who spent time reconstructing it?
- What happened financially or operationally afterwards?
Polite-answer trap — Useless/evasive: “That happens occasionally.” Redirect: “Which incident from the last few months is easiest to remember?”
Q08
Question — Which unofficial spreadsheet or tracker gets updated before the official system because people trust it more?
Uncovers — Trust gap, unofficial source of truth, speed-versus-control tradeoff.
Why it stays clean — It asks what people do first, revealing real trust.
Follow-up probes —
- Who created it?
- Why do people trust it?
- What happens when it disagrees with the official system?
Polite-answer trap — Useless/evasive: “The official system is the source of truth.” Redirect: “When the two disagree, which one do people act on first?”
Q09
Question — Which email inbox, shared drive folder, or PDF pack has become a de facto database?
Uncovers — Document overload, data retrieval cost, informal records, audit complexity.
Why it stays clean — It asks about actual storage habits rather than desired information architecture.
Follow-up probes —
- Who knows how to search it?
- What naming convention is used or ignored?
- What was the last item that took too long to find?
Polite-answer trap — Useless/evasive: “We have a structured filing system.” Redirect: “Where do people search first when they need an old answer quickly?”
Q10
Question — Which recurring meeting relies on someone manually pulling together information from several messy sources beforehand?
Uncovers — Reporting burden, data latency, hidden admin labor, meeting-critical workflows.
Why it stays clean — It asks for a current meeting and preparation process.
Follow-up probes —
- Who prepares it?
- How long does preparation take?
- Which source is usually missing, late, or disputed?
Polite-answer trap — Useless/evasive: “Reports are produced as needed.” Redirect: “What was the last meeting pack that took someone a painful amount of time to compile?”