3 ms·
I still am holding out hope for progressive complexity to be adopted by the UI & product worlds across the verticals, but anything meaningful here needs to be s
by vlovich123 6y ago
I still am holding out hope for progressive complexity to be adopted by the UI & product worlds across the verticals, but anything meaningful here needs to be something engineering can solve across problem domains. I don't know if that's actually possible. The ideal system could support more power user use cases without increased technical maintenance burden/UI complexity & designer burden on a per-feature basis/& product clarity. That seems like a tall order.
To me I think it depends what your power user cohort looks like. Are your power users also where you make your money? Are they an important cohort to learn from to innovate to stay ahead of competition? Are they organic advocates for the product spreading the word & building brand value for you?
Which case kind of determines how I would adjust business strategy. If they're revenue drivers, then tailor the UI to them from the get-go. If new users are important to continue growing the power user revenue base, make the new -> expert conversion easy (separate sign-up flow, ways to identify how to get them access to the power tools they need without overwhelming them, etc). This doesn't even have to be UI changes. Could be training materials, courses, hands-on experiments, sandboxes etc to ramp up beginners to where they want to spend revenue.
If they're providing market research to maintain your edge, then maybe some amount of progressive discovery instead (e.g. an advanced drop-down for a given screen to tune the knobs, API to automate, or whatever is relevant for your business). Maybe some good task-oriented documents to help new users ramp up to be power users.
If they're advocates then do what you can to make them happy or excited. Some times holding off on a popular feature can build some excitement about the launch to increase the reach of the announcement to attract more customers. Avoid massive redesigns that break them or build a gradual transition plan (don't pull a Digg). Feature requests are important to listen to but don't necessarily need to be addressed to keep good will (like what Yelp did/does with incentives for power Yelp reviewers). For technical things, giving them a bit of outsized attention to solving bugs that are friction-causing might be warranted to maintain the good will.
- forgotmypw17 6y agoThank you for writing, progressive complexity is a great term. For my project, a web-based forum, I categorize UI controls as beginner or advanced, and hide the letter behind a setting. New users see only the essentials, intermediate users see both extra controls and hints, and expert mode takes the hints away. I've had overwhelming success with this technique in user studies, both with beginners doing register-comment-vote, and advanced users tasked with "vote against my vote on this item". The best part is how easy it is to layer the UI like this with HTML and DOM. My concept works in 10-year-old browsers and I believe I can extend suport even further!