Element L: Presentation of Designer's Recommendations

1 min read

Week 12: Presentation of Designer’s Recommendations

PLTW Element L — Presentation of Designer’s Recommendations.

Areas Needing Further Development & Testing

Based on your Element I test data (Week 9) and Element K reflection (Week 11), list the specific areas of your prototype that are unfinished, unreliable, or untested — be concrete about what and why.

Synthesize Expert Recommendations from Element J

Pull the external evaluation findings from Week 10 (Element J) and turn them into specific, actionable recommendations — not just a restatement of the feedback.

Draft Recommendations for the Next Iteration

Write your Designer’s Recommendations: what should change in the Sprint 4 redesign, and why.

Recommendations should be specific and evidence-backed (e.g. “switch to server-side validation — 40% of external evaluators triggered the client-side bug”) — not vague (“make it better”).
This document is what your team walks into N@tM (Element M, this same week) able to defend, and what Sprint 4 (Element A, Iteration 2) starts from.

Core Deliverables

Areas-needing-development list, tied to Element I/K evidence.
Synthesized recommendations from Element J external evaluation.
Written Designer’s Recommendations for the Sprint 4 redesign.