Blind Matrix
scroll
Blind Matrix
Product Designer • Strategy, Logic Mapping & Prototyping Discovery Phase & Feasibility Study • 6 Weeks
Translating complex manufacturing rules into a fail-safe digital configurator for SMEs
Sometimes success isn't shipping features, it's preventing the client from building the wrong thing. My prototypes and logic maps validated that technical requirements exceeded resources, saving the client from a stalled development cycle.
Drowning in Dependencies.
Small manufacturers relied on manual Excel calculations to configure orders. However, the logic was hidden in "tribal knowledge": Motor power depends on blind size; fabric width dictates rolling constraints; striped patterns cannot be rotated. Building a tool without mapping this would lead to impossible orders.
Strategic Clarity & Risk Mitigation
Feasibility: Validated that technical requirements exceeded client resources, preventing a stalled development cycle. Asset Creation: Delivered the client's first-ever documented blueprint of their business logic. Key Takeaway: "Sometimes success isn't shipping features; it's preventing the client from building the wrong thing."
The "Fail-Safe" Ordering Flow.
My workshops revealed that "Control Type" (Manual vs. Electric) dictates all physical dimensions. I restructured the user flow to ask for Control Type first. This immediately filters out invalid dimensions downstream, preventing the user from configuring a product that physically cannot be built.
Visualizing Invisible Logic
The client needed to update rules (e.g., "If Surface Mount -> Hide Accessories") but lacked IT staff. Instead of asking them to write code or complex Excel formulas, I prototyped a Visual Logic Tree. This allowed non-technical staff to build "If/Then" dependencies using a simple select component.
Solving the Data Entry Barrier
Migrating 1,000+ fabric SKUs manually would take weeks, making the tool unusable for small teams. I designed a Bulk Import Strategy that maps client CSV files to system parameters and auto-matches them with product images, reducing onboarding time from weeks to minutes.
This project reinforced that design is often about 'uncovering the unknown.' By visualizing complex dependencies early, we identified the true scope of the product before a single line of code was written. Sometimes, a successful design phase is one that clarifies that the business is not yet ready to build.
