Q01
Question — Tell me about a useful tool, process, or service that still failed to get adopted widely. What stopped it despite being useful?
Uncovers — Adoption ceiling, non-obvious blockers, workforce resistance, org limits.
Why it stays clean — It asks for a past failure where usefulness was not enough.
Follow-up probes —
- Who benefited from it?
- Who did not change behavior?
- Was the cap budget, trust, training, IT, client rules, data, or timing?
Polite-answer trap — Useless/evasive: “Good tools still need rollout.” Redirect: “Which useful tool had the clearest gap between value and adoption?”
Q02
Question — Which data, documents, drawings, photos, messages, cost information, or client materials are hardest to put into third-party systems?
Uncovers — Data sensitivity, confidentiality limits, integration barriers, buyer risk.
Why it stays clean — It asks about existing data restrictions rather than abstract security concerns.
Follow-up probes —
- Who decides what cannot be shared?
- What was the last case where sharing was blocked or restricted?
- Was the concern client, commercial, personal, legal, or contractual?
Polite-answer trap — Useless/evasive: “We are careful with sensitive data.” Redirect: “Which specific data type caused the last restriction?”
Q03
Question — What was the last tool or process change that site teams resisted, and what form did the resistance take?
Uncovers — Workforce adoption barrier, cultural limit, training burden, enforcement reality.
Why it stays clean — It asks for observable resistance rather than stereotypes about site teams.
Follow-up probes —
- Was resistance open refusal, slow use, bad data entry, complaints, or workaround creation?
- Who handled it?
- Did the resistance fade or persist?
Polite-answer trap — Useless/evasive: “People can be resistant to change.” Redirect: “What did people actually do or not do on the last resisted rollout?”
Q04
Question — Which client, contract, framework, JV partner, main contractor, subcontractor, or insurer has prevented a process or tool from being used as intended?
Uncovers — External adoption constraints, contractual friction, ecosystem dependency.
Why it stays clean — It asks for a real outside constraint.
Follow-up probes —
- What requirement conflicted?
- Who raised it?
- Did the firm adapt, duplicate work, or abandon the tool?
Polite-answer trap — Useless/evasive: “External parties affect what we can do.” Redirect: “Which outside party last forced a change to your preferred process?”
Q05
Question — Which purchase or rollout failed because the team did not have time to implement, configure, train, migrate, or maintain it?
Uncovers — Bandwidth ceiling, implementation capacity, hidden cost, adoption realism.
Why it stays clean — It asks for a past implementation bottleneck.
Follow-up probes —
- Who was supposed to own implementation?
- What task was not done?
- Was the issue temporary workload or permanent lack of ownership?
Polite-answer trap — Useless/evasive: “Time is always a constraint.” Redirect: “Which rollout lost momentum because nobody had enough time to finish the implementation work?”
Q06
Question — Which tool has been limited by site connectivity, device availability, data quality, permissions, or field conditions?
Uncovers — Operational environment limits, reliability constraints, field practicality.
Why it stays clean — It asks for the physical and operational constraints that have already appeared.
Follow-up probes —
- Which site showed the problem?
- How did users work around it?
- Did the vendor or internal team fix it?
Polite-answer trap — Useless/evasive: “Sites can be challenging environments.” Redirect: “Which site or project made the limitation visible most recently?”
Q07
Question — What was the last time finance or leadership said no to something even though users liked it?
Uncovers — Budget cap, leadership skepticism, value proof threshold, economic limit.
Why it stays clean — It asks for an actual no after user support.
Follow-up probes —
- Who liked it?
- Who said no?
- What reason was given: cost, timing, risk, duplication, evidence, or priorities?
Polite-answer trap — Useless/evasive: “Budget always matters.” Redirect: “Which liked tool or service still failed to get funded?”
Q08
Question — Which process or tool creates fear of monitoring, blame, surveillance, or exposing weak performance?
Uncovers — Political resistance, trust barrier, data visibility risk, workforce psychology.
Why it stays clean — It asks about observed fear around current or past systems.
Follow-up probes —
- Who expressed the concern?
- Was it said openly or shown through behavior?
- Did leadership adjust messaging or controls?
Polite-answer trap — Useless/evasive: “People sometimes worry about being monitored.” Redirect: “Which rollout produced that concern most clearly?”
Q09
Question — Which existing system has been discussed as too embedded to replace in the short term?
Uncovers — Switching cost, incumbent lock-in, process dependency, migration barrier.
Why it stays clean — It asks about current embeddedness rather than incumbent satisfaction.
Follow-up probes —
- What data, integrations, reports, or habits create the lock-in?
- Who suffered during the last upgrade, migration, outage, or replacement discussion?
- Has replacement ever been discussed?
Polite-answer trap — Useless/evasive: “Some systems are business-critical.” Redirect: “Which one caused the most disruption during a past upgrade, outage, migration, or replacement discussion?”
Q10
Question — Which type of improvement gets praised in meetings but repeatedly fails to receive budget, staff time, or rollout attention?
Uncovers — Talk-versus-action gap, natural cap, strategic noise, priority reality.
Why it stays clean — It asks for repeated observed non-action, not opinions about importance.
Follow-up probes —
- Who praises it?
- What resource is never allocated?
- When was the last time it was deferred?
Polite-answer trap — Useless/evasive: “There are always competing priorities.” Redirect: “Which praised initiative has been deferred most often?”