First build · Advanced beginner · Lesson 30 of 99 · about 5 hours
Iterating on evidence rather than taste
After this you can turn test findings into prioritised changes and show a clear before/after with a stated reason.
Why it matters
Take your session notes, rate each problem by severity (how many hit it, how badly it blocked them, how easy to fix), then change the design for the top three only. Document each change as: what we observed, what we inferred, what we changed, what we expect to improve. This before/after with reasoning is the single most persuasive artifact in a junior portfolio, because it is the hardest thing to fake. Trap: fixing everything, which hides your prioritisation judgement, the thing being assessed.
How to use this resource
Reference the sections on analysing findings and severity rating. Do not read it end to end at this point; you need one specific part.