How I Decide a RAXXO Tool Needs a Redesign, Not a Patch

Before touching a shipped RAXXO tool's core screens, three signals are assessed in order to determine whether a redesign or a patch is needed. A patch resolves one issue reported by a user, while a redesign addresses a recurring problem from multiple users. The kill switch allows for the redesign process without causing disruptions to the user experience. While patches focus on fixing specific issues, redesigns question if the entire screen is asking the right questions from the user's perspective.

Designers should focus on the screens surrounding the problematic elements during a redesign and avoid working on export formats or saved URLs. The distinction between patches and redesigns is crucial because patches only fix the symptoms, while redesigns address the root cause. When faced with a screen that is structurally unclear, rebuilding it from scratch is the only solution.

If there is a feature that users don't use but solves a real problem, it is an indication that a redesign is necessary instead of a patch. The final checklist helps designers decide whether to proceed with the redesign by considering four key questions: whether it is a single screen or a flow, the potential loss if the redesign fails, whether it can be rolled out using a kill switch, and whether the redesign changes what the tool promises or just how it delivers on those promises.

By running through these questions before starting a redesign, designers can avoid creating a tool that is visually appealing but less useful. Writing down the answers to these questions provides a commitment to the scope of the redesign and helps prevent the redesign from expanding beyond its intended boundaries. The pattern of redesigning screens based on user feedback and usage data has proven effective in improving the overall user experience.