This creator has fascinating insights into design and UX. This team’s synthesis is more insightful and professional than anything else I have been able to casually consume.
This particular video argues against the notion of a “happy path.” In reality, “edge cases” are just as valid _states_ as the “happy path.”
At work, I am rewriting a Salesforce Implementation that failed largely due to poor UX. The first solution was built by contractors who later ditched. They built the “happy path.” After they left, I had to support the software. When we launched, I had conversations with users EVERY DAY where I had to say, “sorry, we didn’t plan for that edge case.” It turns out that edge cases aren’t really “edge” at all. It was just a poorly designed system.
Watching this video made me redouble my efforts to plan for every state. I want to be able to respond to support questions with, “we designed for that.”
What do you think? How can we balance good design with time and money requirements? Any thoughts about the video’s suggestions at the end?
stephenlf•2h ago
This particular video argues against the notion of a “happy path.” In reality, “edge cases” are just as valid _states_ as the “happy path.”
At work, I am rewriting a Salesforce Implementation that failed largely due to poor UX. The first solution was built by contractors who later ditched. They built the “happy path.” After they left, I had to support the software. When we launched, I had conversations with users EVERY DAY where I had to say, “sorry, we didn’t plan for that edge case.” It turns out that edge cases aren’t really “edge” at all. It was just a poorly designed system.
Watching this video made me redouble my efforts to plan for every state. I want to be able to respond to support questions with, “we designed for that.”
What do you think? How can we balance good design with time and money requirements? Any thoughts about the video’s suggestions at the end?