
give and use peer critique, test version 1 against the criteria under harder conditions, and build a version 2 that still meets them.
Phase 4: Build
Do Now. A late-afternoon rain shower, a tired driver: what two numbers in our model get worse, and in which direction?
On wet pavement the tires can supply less friction force. By Fnet = ma, what happens to the car's maximum deceleration?
Gallery critique. Post your spreadsheet results, matrix and version 1 on chart paper. Visitors leave three sticky notes: I like… (a strength backed by evidence), I wonder… (a question about an assumption), What if… (a change to test). Answer at least two notes in writing.
The stress test. Engineers test designs against harder conditions than average. Our stress case: a slower driver (tr = 2.0 s) on wet pavement (a = 4.0 m/s2), both illustrative values. Worse friction means a smaller net force, so by a = Fnet/m the car decelerates less.
| Design | Speed | Sight distance | Stopping distance (stress case) | Result |
|---|---|---|---|---|
| A. 25 mph | 11.18 m/s | 30 m | 22.4 + 15.6 = 38.0 m | Fails by 8.0 m |
| B. Remove parking, 30 mph | 13.41 m/s | 45 m | 26.8 + 22.5 = 49.3 m | Fails by 4.3 m |
| Version 2: A + B together | 11.18 m/s | 45 m | 38.0 m | Passes, 7.0 m spare |
Worked example 1: iterating. Diego’s team chose B as version 1. The stress test showed B fails on a wet day with a slow driver. Combining B with a 25 mph school-hours limit passes with 7.0 m to spare. Their version 2 costs a little more and slows traffic slightly during school hours, a trade-off they state openly.
Worked example 2: answering a critique. Sticky note: “I wonder if 2.0 s is too harsh.” Reply: “Highway designers assume a longer reaction time than a ruler drop because real drivers are surprised. Our stress case protects the children if the driver is not alert, which is the client’s top need.”
Back to the stakeholders. Version 2 serves families (larger margin), keeps most parking for residents, and slows drivers only during school hours. Name who gains and who gives something up.
Run the stress test in your spreadsheet, then answer.
Write version 2.
Describe your version 2: what changed, the stress-test result and the spare distance. Then explain the trade-off for two stakeholders and why the safety need of children outweighs it.
Vision Zero is a road-safety approach that began in Sweden, where the national parliament adopted it as policy in 1997. Its starting idea is that people will always make mistakes, so streets, speeds and vehicles should be designed so that a mistake does not cost a life or a serious injury.
In practice, Vision Zero planners match speed limits to what the human body can survive in a collision, which means lower speeds where people on foot share space with cars. They also redesign crossings so drivers see pedestrians sooner and slow down naturally. Many cities on several continents have since adopted Vision Zero plans and use crash data to decide where to act first.
Think about it: How is Vision Zero’s idea, “design for the mistake,” like our stress test? What data would you want before claiming that a Vision Zero change made a crossing safer?
Version 2 is ready. Next phase: write the design report and defend it to the client.
Exit ticket: explain, using Fnet = ma, why wet pavement made your version 1 fail, and how version 2 fixed it.
Materials: chart paper, three colors of sticky notes, devices with the team spreadsheets.
Setup: 15 min gallery walk, 15 min stress test, 10 min case study, the rest for version 2. All stress-case values are illustrative.
Listen for: vague critique (“nice job”); teams that keep version 1 without data; ignoring who pays for a trade-off.
Support / stretch: give a critique card with examples of specific notes. Stretch: find the lowest deceleration at which version 2 still passes.