Black Swan Bistro - Part 8
Prioritise and Improve
Turn your Part 7 audit record into a small, justified improvement pass with before-and-after testing.
Not Every Finding Becomes Today's Work
A useful audit often creates more findings than you can responsibly fix at once. That is normal. Professional improvement is not about touching everything; it is about choosing the next valuable change and proving it helped.
In this lesson, your audit record becomes an improvement plan. You will choose a few findings, make focused changes, retest, and write down what changed.
- Which audit finding would make the biggest difference to a visitor?
- Which finding is easy to fix but not very important?
- What could break if you change too much at once?
This lesson depends on the Part 7 audit record. Keep the record open while you work.
Learning Objectives
By the end of this lesson, you'll be able to:
- Prioritise audit findings by impact, effort, confidence, and risk
- Choose a small improvement set that can be tested properly
- Make focused code changes without redesigning the whole site
- Record before-and-after evidence in an improvement log
- Use Git commit messages to explain purposeful improvements
- Identify Identify remaining risk and future work honestly
Why This Matters:
Prioritisation turns a list of findings into maintainable work. The aim is not to do everything; it is to improve the Bistro in a way that is useful, testable, and easy to explain.
Before You Start:
You should be familiar with:
- Black Swan Bistro Part 7: Audit the Live Website Review here
- Refactoring for Reuse Review here
- Monthly Website Health Check Review here
Prioritise the Audit Findings
Start with the audit record, not your memory. For each candidate finding, ask four questions:
Impact
How much does this affect visitors, trust, accessibility, search, or maintainability?
Effort
Can this be fixed and retested in this improvement pass?
Confidence
Is the evidence strong enough, or does the finding need another test first?
Risk
What might break if you change this, and how will you check?
Scores can help, but they do not replace judgement. If two findings have similar scores, choose the one that has clearer evidence and a cleaner test path.
Choose the Improvement Set
| Decision | Meaning | Bistro example |
|---|---|---|
| Do first | High user impact, clear evidence, manageable change, low regression risk. | A mobile navigation link is hard to reach, or an image fails to load on the live menu page. |
| Plan carefully | Important, but needs design judgement, client approval, or wider retesting. | Reworking the menu page hierarchy or replacing several large images at once. |
| Quick polish | Low risk and easy to fix, but not more important than user-blocking issues. | A small spacing inconsistency or a clearer footer link label. |
| Monitor or defer | Not enough evidence, low impact, or outside the current project scope. | A cosmetic preference that would trigger a broad redesign. |
Scope guard: for this lesson, choose two or three improvements. At least one should improve a real visitor outcome. At least one should include a clear retest.
Student Resource: Improvement Log
Black Swan Bistro improvement log
Use this Markdown worksheet to prioritise findings, record before evidence, track changed files, note tests, and capture the after result.
Each log entry should answer
- What finding from the audit record is being handled?
- Why is it worth doing now?
- What is the smallest sensible change?
- What files changed?
- How was the before state captured?
- How was the after state tested?
- What remains unresolved?
Make Focused Changes
Work in a small loop: choose one finding, make the change, test the affected behaviour, update the log, then decide whether to continue. This keeps the Bistro maintainable and protects your ability to explain the work.
A tidy improvement might be an image dimension fix, clearer link text, a mobile spacing adjustment, a corrected metadata description, a missing alt text decision, or a small refactor that removes duplicated restaurant details. A broad restyle is usually too much for this pass.
Before and After Evidence
Evidence is how you know the improvement worked. The exact evidence depends on the finding:
| Finding type | Before evidence | After evidence |
|---|---|---|
| Mobile layout | Viewport width and screenshot showing the issue. | Same viewport width and screenshot after the fix. |
| Keyboard or accessibility | Tab order note, focus screenshot, inspector note, or screen reader observation. | Repeated keyboard path or accessibility check with the result recorded. |
| Performance | Network file size, image dimensions, or measured issue. | Reduced file size, correct dimensions, or repeated measurement. |
| Content or SEO | Current title, heading, page copy, link, or metadata. | Updated rendered page and source or metadata check where relevant. |
Do not invent performance gains. If you did not run Lighthouse or a production network test, say exactly what you did test.
Check Your Improvement Plan
Before editing, make sure the plan is small enough to test.
- Why should Part 8 start from the Part 7 audit record instead of a fresh list of ideas?
- What is the risk of fixing five unrelated findings in one change?
- What should an improvement log prove?
Check Your Answers
- The audit record keeps the work evidence-based. It helps you choose improvements that solve observed problems rather than preferences invented after the fact.
- It becomes harder to test, review, explain, or undo the work. A regression may be difficult to trace back to one cause.
- It should show what was changed, why it was changed, what evidence existed before, how the change was tested, what evidence exists after, and what remains unresolved.
How confident are you with this concept?
Still confused | Getting there | Got it | Could explain it to a friend
Guided Practice: Plan and Complete One Improvement
Use the improvement log to move from evidence to a focused change.
Select three findings from Part 7
Choose one finding that affects visitors, one finding that affects site quality or maintainability, and one smaller polish item. Copy their evidence into the improvement log.
Need a hint?
Score impact, effort, confidence, and risk
For each finding, score impact, effort, confidence in the evidence, and regression risk. Use the score to decide what to do now, not to pretend the decision is mathematical.
Need a hint?
Make one improvement at a time
Change the smallest amount of code that solves the selected finding. Retest the affected page before moving to the next item.
Need a hint?
Record before and after evidence
Add the before evidence, changed files, test steps, after evidence, and remaining risk to the improvement log. The log should explain the decision to someone who did not watch you code.
Need a hint?
You're on track if you can:
- Each selected improvement links back to a Part 7 finding
- The chosen work is small enough to test properly
- Changed files are recorded
- Before-and-after evidence uses comparable conditions
- Remaining risks or deferred findings are written down
Independent Challenge: Complete the Improvement Pass
Now try this on your own without hints!
Your task
Complete a focused improvement pass for the live Black Swan Bistro site. Use your audit record, choose two or three improvements, make the changes, retest, and finish the improvement log.
Requirements:
- Prioritise at least three audit findings before editing
- Complete two or three focused improvements
- Record before evidence and after evidence for each completed improvement
- Run the relevant local checks for the changed files
- Write a short summary of what remains deferred and why
Stretch Goals (Optional):
- Create one Git commit per improvement type with clear messages
- Ask another learner to review the improvement log before deployment
- Retest the deployed site after publishing the improvements
Success Criteria:
| Criteria | You've succeeded if... |
|---|---|
| Prioritisation | The chosen improvements are justified by audit evidence and visitor impact. |
| Implementation | Changes are focused, readable, and do not introduce unrelated redesign work. |
| Verification | Before-and-after evidence shows what was tested and what changed. |
Recap
You have moved from audit evidence to deliberate improvement. The important habit is the loop: choose with evidence, change with scope, test with comparable conditions, and record what remains.
Lesson Complete: Improve With Evidence
Key Takeaways:
- Prioritisation connects audit evidence to responsible action.
- Impact, effort, confidence, and regression risk are better guides than personal preference.
- Small focused changes are easier to test, review, and explain.
- Before-and-after evidence is part of the work, not an optional extra.
- A good improvement log helps future you understand the decision.
Learning Objectives Review:
Look back at what you set out to learn. Can you now:
- Prioritise audit findings by impact, effort, confidence, and risk Check!
- Choose a small improvement set that can be tested properly Got it!
- Make focused code changes without redesigning the whole site Can explain it!
- Record before-and-after evidence in an improvement log Could teach this!
- Use Git commit messages to explain purposeful improvements Check!
- Identify remaining risk and future work honestly Got it!
If you can confidently answer "yes" to most of these, you're ready to move on!
Think & Reflect:
Impact
- Which improvement had the clearest visitor benefit?
- Which finding did you defer, and was that the responsible choice?
Testing
- Was your after evidence directly comparable to your before evidence?
- What would you test again after deployment?
Looking Ahead:
Continue to Part 9, where the Bistro receives a realistic client change request. You will update the live project without drifting into unnecessary redesign.