
design, evaluate and defend a solution that reduces a human impact on an ecosystem, using criteria, constraints, test evidence and a weighted decision matrix.
Phase 5: Prove It
Do Now. You have five minutes in front of the council. Write the one trade-off you most want them to understand.
Which opening best fits the council?
The challenge. Using the ecosystem your team chose (a kelp-forest coast, a river estuary or a fire-adapted forest), present a design that reduces a human impact on its biodiversity, and defend it to the council: scientists, agency staff and community members.
The design cycle in your brief.
Using ecological reasoning. Tie your design to what you learned about stability (HS-LS2-6): will your solution help the ecosystem return to a stable state, or does it only treat a symptom? For a regime shift like an urchin barren, a solution may need to push the system back past a threshold before it can hold itself there.
Worked example: one paragraph of a strong brief. “We prioritized long-term kelp cover over speed. Our simulation shows 50% removal for four years, then 10% a year, keeps urchins below the 2 per m² threshold, so kelp can hold itself in place. The trade-off is a permanent maintenance cost of about 1 budget unit per hectare a year. The model has no larvae from other reefs, so we recommend monitoring urchin density every spring.”
Presentation. Pitch in five minutes, live or recorded, and answer one question about your trade-offs.
Check your brief with your team before the pitch.
After the pitches, reflect.
What did the council ask, and how well did your evidence answer it? What would you add to the brief?
Compare your design with one from a different ecosystem. Which ecological idea (keystone species, tolerance range or threshold) did each design depend on?
Write a design brief of 1,000–1,400 words that defines a human-impact problem in a kelp-forest coast, a river estuary or a fire-adapted forest; states prioritized, quantified criteria and constraints, including social and cultural ones; breaks the problem into sub-problems; compares at least three solutions in a weighted decision matrix; presents test evidence from a prototype, simulation or public dataset, with its limitations; and explains your version 2 refinement. Teams of two may submit one brief with a statement of who did what. Hand-drawn diagrams are fully acceptable. Then pitch for five minutes, live or recorded.
| Criterion | What proficient looks like |
|---|---|
| Problem definition (HS-ETS1-1, HS-LS2-7) | Criteria and constraints are specific, quantified where possible, prioritized, and include societal needs; the human impact is backed by evidence. |
| Decomposition (HS-ETS1-2) | Breaks the problem into manageable sub-problems and targets one clearly. |
| Evaluation of trade-offs (HS-ETS1-3, HS-LS2-7) | The matrix is correct; cost, safety, reliability and social and cultural effects are discussed honestly. |
| Simulation and testing (HS-LS4-6) | The simulation or test represents the human activity and the biodiversity factor, uses realistic inputs, states its limitations, and was revised after the stress test. |
| Ecological reasoning (HS-LS2-6, HS-LS2-7) | Explains how the solution reduces the impact on biodiversity and whether it helps the ecosystem regain stability. |
| Evidence and communication | Claims tied to data and sources; the pitch answers a question accurately. |
You defended a real design to a real-world panel. Next: the unit checkpoint.
Exit ticket: which Wonder Board question can you now answer best? Write the question and your answer.
How confident are you that you can design and defend a solution that reduces a human impact on an ecosystem?
Timing: the task spans about four periods (planning, peer review, drafting, pitches); this lesson is pitch day.
Setup: invite staff, family or local professionals to role-play the council, in person or by video. Visitors can score the communication row.
Listen for: trade-offs hidden behind a matrix total; simulations presented as proof; community effects mentioned only in passing.
Support / stretch: give a section-by-section outline. Stretch: add a sensitivity check showing how the matrix winner changes if the community weight doubles.