Week 11 Session: Redemption Studio
Returning to your original bad system to fix it, without destroying whatever legitimate goal it was actually serving
17 May 2027
Before the session#
Bring your redesign in progress, plus a plain answer to what caused the original problem — not just what was wrong with it.
In the session#
Redemption Studio: you present your final-project system in five steps — Original → Problem → Cause → Constraints → Proposed Redesign — and your peers challenge the redesign by naming any stakeholder or requirement it looks like you’ve ignored. The constraint that makes this hard is the same one from week 5, run in reverse: make it better without destroying the original system’s legitimate goals.
Afterwards#
This is the payoff of the whole semester’s arc — observation, psychology, manipulation, creation, testing, ethics, redesign — landing in one project. The Redemption Project is presented next week.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- your redesign names what the user needs, what the organisation needs, and the constraint that produced the original problem
- you present before, why it was bad, what caused it, the redesign, and what changed, in that order
- a peer's critique of your redesign is recorded, not just delivered
Teaching team
- Idris Fenn — tutor