Improving Your Tool UX Design by Removing the Faults of "Sensible Defaults"
summary
Asserts that rigid “sensible defaults” break complex tool workflows and recommends making defaults editable defaults so users can drag toolbars, save layouts and remap hotkeys in Unity, Maya, Blender and Unreal; cites the WWII cockpit fix and the real-world fragility of a shared Maya shelf maintained by a departed tech artist. Gives concrete wins: small per-user time savings (e.g. 2.4 minutes/day) scale across teams to months or a year of saved work and reduce onboarding and burnout.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:13Sensible defaults fail in tool UX
- 5:04Myth of the average user
- 9:39Adjust tools like workspace
- 14:11Editable over sensible defaults
- 20:32Workflows matter more than tools
- 24:45Adjustable tool design solutions
- 31:26Complex vs basic UX in game tools
- 33:31Accessibility and cost concerns
- 37:44Removing faults from defaults
- 40:15Q&A: Adjustability for gamers
- 42:22Q&A: Creativity in workflows
related talks
59m5 ways the UX of your toolset improves the quality of your games
33mBeyond Buttons: Crafting Satisfying & Easily Marketable Products
36m"UX for Developers, Seriously!"
24mYou're Doing UX Unconsciously, Now Let's Make it Conscious and Intentional
01h 02mBuilding Better Systems: Boosting Accessibility for the Default Mode Network
36mUX designers /developers collaboration anti patterns
42mIndispensable Principles for Designing Complex User Interfaces
29mThe Importance of Design: maybe the users aren't wrong?