Week 11: Fix It Without Breaking It

Redesigning a hostile system without pretending its original goals didn't exist

17 May 2027

Redesigning something is easy if you’re allowed to ignore why it existed in the first place. This week is harder than that: fix the system without destroying whatever legitimate goal it was actually serving. That means naming what the user needs, what the organisation needs, what constraints were real, and what specifically caused the original problem — before you’re allowed to claim your version is better.

Outline#

• what the user needs, what the organisation needs, what constraints exist, what actually caused the problem
• diagnosing the cause before proposing a fix, and prioritising the problems that actually matter
• Redemption Studio, this week’s session
• what the Redemption Project still needs before next week
• the semester’s full arc, in one line: observe, understand, manipulate, create, test, question, redesign