ockhams-equivalent-designs

What problem does it solve?

It solves the problem of defending complexity in design decisions by helping you determine whether two alternatives are functionally equivalent for users, rather than being “equivalent” only on the happy path.

Core Features & Use Cases

• Defines functional equivalence for UX outcomes: checks whether designs match the user goal, outcome quality, user cost, edge-case handling, and downstream system state.
• Surfaces hidden differences: identifies cases where designs look similar but differ in performance, error recovery, discoverability, accessibility, internationalization, and future flexibility.
• Guides a disciplined tradeoff decision: helps you list concrete differences, quantify impact when possible, and decide to apply the “razor” only when equivalence is genuine.
• Use Case: Compare two UI flows for editing a profile—one guided wizard vs. one full-page form—and decide whether the outcomes are equivalent for the users and context, or whether the wizard genuinely improves critical edge cases.

Quick Start

Ask the agent to evaluate whether “Option A and Option B” are functionally equivalent for a specific user goal and time horizon, then recommend the simpler option only if equivalence holds across edge cases, accessibility, and downstream effects.