👂
01 / LISTENAsk before you build
“What is hardest about using this?” can reveal a need that the design brief missed. Practice: ask a user one open question, then listen without interrupting.
01 / The overlooked advantage
Small behaviours. Serious consequences.
A technically impressive design can still fail when people misunderstand it, cannot afford it, cannot use it or do not trust it. These six habits deserve as much attention as the prototype.
🧭
02 / JUDGEMENTSay what you don't know
A confident guess is not a verified safety result. Practice: separate facts, assumptions and unknowns when presenting.
🗣️
03 / COMMUNICATEMake it understandable
Explain your design to a non-engineer in 30 seconds. If they cannot see the benefit, simplify the explanation—not the truth.
🤝
04 / TEAMWORKInvite the quiet voice
“We haven't heard your view yet.” One sentence can reveal a safety concern or better alternative the group overlooked.
⚖️
05 / ETHICSNotice who gets left out
A cheaper app-only system might exclude people without smartphones. Ask who benefits, who bears the risk and who has a choice.
🔁
06 / ADAPTABILITYRespond without defensiveness
When testing disproves your idea, changing course is evidence of learning—not weakness. Explain what changed and why.
02 / Engineering in the real world
Four moments when the “small thing” becomes the big thing
The warning nobody raised
A junior colleague notices an unusual test result before launch. Will your team reward the question—or dismiss it to meet the deadline?
The door that works for some
A smart entrance performs perfectly in testing, but a wheelchair user cannot reach the controls. Did the team test with the right people?
The perfect product nobody buys
Your design improves performance, but maintenance costs make it unaffordable. Can you defend total lifetime value, not just technical performance?
The model says “safe”
An AI tool recommends a design change. Who checks the assumptions, failure modes and evidence before anyone signs off?
Cheap today, costly tomorrow
A low-cost component is hard to repair and replace. What happens to energy, waste and costs over ten years?
Five minutes with a recruiter
Instead of listing software packages, explain a problem, your contribution, a trade-off and what you learned.
These are illustrative teaching scenarios, not reports of specific incidents.
03 / Interactive decision lab
The £100m Engineering Trade-Off
Your team is designing a resilient urban transport system. Allocate exactly £100 million. There is no universal best split: explain your assumptions, identify who benefits and defend what you chose not to fund.
£100m allocated. Now explain the trade-offs.
Teaching simulation only. These allocations are not real project cost estimates, and spending levels do not predict engineering performance.
Question 1
Who could be disadvantaged by your decision, even if the overall project succeeds?
Question 2
What evidence would change your allocation? Name a test, stakeholder or data source.
Question 3
What is the worst credible failure—and who would be accountable?
04 / Your one-hour mission
From discussion to a decision worth presenting
Your goal is not the most complicated design. Your goal is a decision your team can explain, question and improve.
05′
Choose the problem
Identify a real user and a meaningful engineering need.
10′
Challenge assumptions
Ask who is affected, what is unknown and what might fail.
15′
Make the trade-off
Allocate resources and justify the opportunity costs.
20′
Build your poster
One clear visual: problem → evidence → solution → trade-off → impact.
10′
Pitch & question
Short group pitches and questions; adjust timing to group count.
05 / Three questions · Four choices each
Would you notice what matters?
Choose what you would actually do—not what sounds impressive. Discuss why the other options are tempting. Feedback appears after you choose; submit all three for your score.
06 / The five-minute opportunity
Can you make someone care in 60 seconds?
A recruiter, client or investor may not need every calculation in the first minute. They need to understand the problem, your reasoning and why the solution matters.
15 SECONDS
The human problem
“We noticed that [specific group] struggles with [specific problem]…”
20 SECONDS
Your engineering idea
“Our solution works by… We chose it over… because…”
15 SECONDS
Evidence & trade-off
“Our strongest evidence is… The main uncertainty or risk is…”
10 SECONDS
Why it matters—and what happens next
“This could improve [human outcome]. Our next step is to test [critical assumption] with [real users or evidence].”
“Your technical knowledge may open the door. Your judgement, curiosity and communication help you walk through it.”
Before you leave: What is one small professional habit you will practise in your next group project?