“What are the adoption barriers?”
A category with nowhere obvious to begin.Summer 2026 · Tony Yu
Asking the
Wrong
Question Well
I walked into a transportation-engineering office with no technical vocabulary—so I was always going to ask the wrong questions. This is the summer I learned to ask them well: grounded in the real work, aimed at a real decision.
Podcast · Listen now · 07:57
The one move that changed everything
Stop asking about topics. Start asking about episodes.
A topic is a subject. An episode is something that actually happened. People can struggle to answer the first; they can tell you the second.
“Walk me through the last time the schedule slipped. What did you shorten?”
A memory with a sequence, a choice, and a consequence.Try the moveTurn another topic into something a person can remember
Start with a topicTrust
Ask about the last time“Tell me about the last time you doubted a result. What happened next?”
Use the pattern: Tell me about the last time ___. Then ask what happened next.
The learning challenge
I wanted to learn how to ask useful questions.
I entered a transportation engineering environment without the vocabulary to read a radargram or explain a semi-rigid base. I could make a question sound polished and still get an abstract answer.
So I set a simpler goal: understand the work before I open my mouth, figure out what decision the conversation is actually feeding, and ask about things that really happened—not definitions.
Field-ready, in plain English
Questions tied to real work and a real decision, not textbook definitions.
AudienceStudents and early-career professionals learning to contribute inside a technical team before they speak its language fluently.
Four strategies
How I managed the learning
Each strategy created evidence I could revisit, test, and improve across the semester.
Keep a question log
Record unfamiliar terms, my first interpretation, the question I asked, and what changed after the answer.
Follow the work
Observe the sequence of real tasks before asking people to explain their opinions or preferences.
Test questions aloud
Use mock walkthroughs and field conversations to hear when a question feels natural, vague, or scripted.
Learn through people
Ask for feedback from technical and organizational mentors, then revise the method while the experience is fresh.
Weeks 2–13 · Learning tracker
Twelve weeks of getting more specific
Reconstructed from my notes and project revisions, this tracker shows the work, the evidence it produced, and the idea I carried into the next week.
12weeks documented
5method iterations
4learning strategies
1portable method
- Week02
Name the challenge
I recorded the first conversations I could not fully follow. Instead of hiding unfamiliar terms such as radargram and semi-rigid base, I made them the start of the work.
- Evidence
- Question log · working vocabulary
- Learning
- Curiosity only helps when I admit what I do not know.
- Week03
Build a baseline
I compared questions that sounded intelligent with the answers they actually produced. The gap was uncomfortable and useful.
- Evidence
- Baseline question sample
- Learning
- Abstract wording invited abstract answers.
- Week04
Observe before asking
I began mapping a field task as a sequence: arrival, setup, survey, interpretation, and handoff.
- Evidence
- Process walkthrough notes
- Learning
- A question becomes useful when it has a moment in the work.
- Week05
Draft the question bank
I built a one-page Field-Readiness Question Bank with roughly fourteen prompts for a technical conversation.
- Evidence
- Version 1 · one-page bank
- Learning
- Coverage improved, but the page still felt like a form.
- Week06
Test it aloud
Mock walkthroughs exposed stiff wording, duplication, and questions that arrived before enough context existed.
- Evidence
- Marked-up conversation script
- Learning
- A good question can fail when it arrives in the wrong order.
- Week07
Move from topic to episode
I rewrote general opinion prompts as recent-event prompts: the last delay, the last workaround, the last difficult handoff.
- Evidence
- Before-and-after rewrites
- Learning
- Specific memory was more revealing than general belief.
- Week08
Organize the conversation
I grouped prompts into four stages: context, work, decision, and consequence. The conversation became easier to follow.
- Evidence
- Version 3 · four-stage guide
- Learning
- Sequence lowered the burden on both people.
- Week09
The side-by-side moment
Luke placed two radar images beside each other. Rather than label the field result as irregular, I began asking which feature separated it from the clean laboratory image.
- Evidence
- Turning-point reflection
- Learning
- Technical data gains meaning through context.
- Week10
Add the HOD lens
I mapped role pressure, coordination, psychological safety, and the stakeholders who would feel the result but were absent from the room.
- Evidence
- Stakeholder map · principle notes
- Learning
- Some of the most important people are not in the conversation.
- Week11
Build a portable method
The guide became a Field Conversation Design Method. Step 0 was simple: name who will not be in the room.
- Evidence
- Version 4 · method and flow
- Learning
- A method must work beyond one interviewer.
- Week12
Test transfer
I watched a colleague read the question bank like a form, then rebuilt it with Dr. Li's feedback and tested whether the method could travel.
- Evidence
- Transfer test · mentor feedback
- Learning
- Portability exposed assumptions I could no longer see.
- Week13
Synthesize and continue
I finalized the bilingual guide, the website narrative, and a podcast plan that keeps the people behind the learning at the center.
- Evidence
- Version 5 · final reflection
- Learning
- The assignment ends; the practice does not.
The turning point
Two images. One question I could no longer ask abstractly.
Luke, a member of the laboratory's technical staff, pulled up two radar images: one clean laboratory result and one from a road in service.
I called the field image “irregular.” Luke's correction was simple: description was not yet a question. Asking which feature separated the two gave him something concrete to answer—and made me wonder whether the “noise” was the road telling us something.
The point was not to sound technical. It was to help a real decision move.
Before & after
A question can sound good and still be hard to answer.
01
Before · abstract
“What are the adoption barriers?”
After · field-ready
“Walk me through the last time the schedule slipped. What did you shorten?”
From category to lived episode
02
Before · abstract
“Would you trust this result?”
After · field-ready
“Suppose the report says the base is sound and six months later it is not. What happens next, practically?”
From opinion to consequence
03
Before · abstract
“What would make it hard to use?”
After · field-ready
“Where did you have to stop and wait? What part did you not survey, and why?”
From speculation to work sequence
The outcome
The Field Conversation Design Method
A one-page, bilingual guide anyone could pick up to plan a field interview.
It helps an interviewer move from a broad topic to a concrete episode without making the conversation feel like a test.
Step 0Name who will not be in the room.
Before anything else, ask who is affected by the decision but will not be at the table. It might be the crew or the future maintenance team. Make the questions speak for them.
Cognitive load
Ask one concrete thing at a time.
Curse of knowledge
Make room for explanation without pretending fluency.
Question order
Establish context before asking for judgment.
Psychological safety
Remove the feeling that there is a correct answer.
Episodic recall
Ask about the last time, not what usually happens.
Portability
Design a guide another person can use.
Field notes · Episode 01
Asking the
Wrong Question WellPodcast · 07:57
The conversation behind the method
I chose a podcast because my learning happened through people. In this episode, Luke and Dr. Li revisit the moments that turned a question bank into a method.
Guest 01Luke
Member of technical staff at the lab
Guest 02Dr. Li
Senior researcher specializing in GPR
Episode 01 · Listen nowAsking the Wrong Question Well
07:57Episode route
00:00–01:42The wrong question
A cold open with Luke, followed by the challenge: learning to ask useful questions without technical fluency.
01:42–02:44The two images
Luke explains why “irregular” only describes the field image—and which question makes it answerable.
02:44–03:31Who answers if it fails?
Dr. Li reframes adoption as a question of accountability, not confidence in the algorithm.
03:31–05:15The most useful eleven minutes
A question bank fails as a conversation, then becomes a portable method.
05:15–07:57What changed
Tony, Luke, and Dr. Li reflect on honest learning, better questions, and what comes next.
Reflection
I stopped treating expertise as a performance.
I learned that I could contribute before I was technically fluent. I had to respect the work enough to be concrete and honest about what I did not know.
I now prepare by finding the decision and asking who is missing from the room. That reduced the urge to improvise a “smart” question.
A novice does not need perfect vocabulary to ask a valuable question. Start with a real episode, make the consequence visible, and give the other person room to think.
I will keep the question log and test the method in new technical settings, especially where engineering work needs to make sense to people outside the lab.
“My learning happened through people.”— Tony Yu
The practice I am taking forward