Ux patterns For 2026 (Google Doc + Videos) (https://lnkd.in/ehCWtHgF), a free 3h 30mins-online workshop recording on design patterns to address frustrating UX — with all video recordings, slides and examples in one single place. Share with your friends and colleagues — no strings attached! From early 2025, still up-to-date today.
Google Doc (slides, videos, links): https://lnkd.in/ehCWtHgF
All slides (PDF): https://lnkd.in/dH7ysYHw
🎁 Free recording: Designing For Complex UIs in 2026: https://lnkd.in/dTrurd44
Key takeaways:
1. The fold exists, but often it doesn’t really matter that much.
2. Page length is typically not the problem — lack of rhythm is.
3. Around 80% of your page’s visitors will actually never read it.
4. F-shape scanning is a poor, inefficient fallback behavior.
5. Layer-cake scanning pattern is much more effective.
6. Shift user’s attention from looking → scanning → reading.
7. People are never “edge cases” and “average” users don’t exist.
8. Users often start scrolling immediately, before page fully loads.
9. Scanning is easier if we arrange details along a single axis.
10. Users skip decorative images, study informational ones.
11. Users study first images to decide whether to ignore the rest.
12. Design UI states: blank, loading, partial, error and idle states.
UX guidelines:
1. Use banana testing and content heatmapping to test content.
2. We map brand voice and tone against impact and purpose.
3. Poor error messages are generic, unclear, technical, excessive.
4. Good error messages say what happened, why and how to fix it.
5. Consider displaying error messages above text input, not below it.
6. If you can, avoid displaying error messages in toast messages.
7. Replace tooltips by showing key details or using an accordion.
8. Allow users to override aggressive validators (for names, address).
9. FAQs can often be unnecessary → front-load key details.
10. Badges are static → relay status/updates (new, pending, -7% ↘).
11. Tags are static (keywords) or interactive (filters, selection, actions).
12. Always prefer adjectives or nouns for non-interactive tags.
13. Static labels should never look like buttons or interactive elements.
14. AI interfaces require good input UX, output UX, refinement UX.
15. Allow users to refine AI input/output by interacting directly on it.
16. Replace chatbots → sparkle AI capabilities across user journeys.
17. Layer user journeys against each other to identify hubs/hotspots.
18. Best AI experience doesn’t have sparkles → it just does its job.
Recorded by yours truly with the wonderful UX community. And a huge THANK YOU to everybody sharing their work and their findings and insights for all of us to use. 🙏🏼 🙏🏾 🙏🏾
graphical user interface, application, Teams