it's very common/easy/exciting to start the process of adding new content or functionality to a UI by designing a new interaction/or style. most designers start this way but every new interaction model and/or visual style adds cognitive load...
... "why/how is this different? how do I use it? etc" instead it's best to start with existing interaction models and treat new ones as a last resort. here's a simple way to enforce that yourself:
1. list out the interaction models in your product
2. explain what each one is there for; justify its existence in words
3. when asked to add something new, go through this list and see what is most appropriate
4. if none fit, try cramming into to the closest one
...
2. explain what each one is there for; justify its existence in words
3. when asked to add something new, go through this list and see what is most appropriate
4. if none fit, try cramming into to the closest one
...
... 5. if it totally doesn't work, consider adding a new interaction model to the list but define it clearly/tightly
not as much fun as designing something new, I know.
but making things easy to use is hard. especially as they grow.
not as much fun as designing something new, I know.
but making things easy to use is hard. especially as they grow.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
