(The posts I like) Series : 0126 .

🌳 Decision Trees For UI Components (https://lnkd.in/eiuWb3bq), a fantastic set of design decision trees for notifications, errors and alerts, loading patterns, calls to action, truncation and overflow from the Workday design system — with guidelines, examples and use cases, do’s and don’ts. Notifications Decision Treehttps://lnkd.in/e6pwi6P3Errors and Alerts Decision Treehttps://lnkd.in/eiuWb3bqLoading UX Decision Treehttps://lnkd.in/eq2gZjnHCalls to Action Decision Treehttps://lnkd.in/eBc2k3KqTruncation and Overflow Decision Treehttps://lnkd.in/eD5MCpeRWhat I absolutely love about this approach is not only that it beautifully visualizes design decisions, but that it also serves as a documentation. It establishes shared standards across teams and includes examples to follow, with incredible value for new hires.Of course exceptions happen. But once you have codified the ways of working for design teams as a decision tree, and make it front and center of design work, it resolves never-ending discussions about UI decisions for good.Whenever a debate comes up, document your decisions into a decision tree. Turn them into posters. Place them in kitchen areas. Developer’s and QA workspaces. Put them in design critique rooms. Make them visible where design work happens, and where code is being written.A huge, HUGE kudos to the wonderful Workday team for putting together these decision trees (and writing impeccable alternative text for them!) 👏🏼👏🏽👏🏾. It’s worth mentioning that every project will need its own custom trees, so please them as an idea to build upon and customize away for your needs.Further resources:Onboarding UX Decision Tree, by NewsKithttps://lnkd.in/e8TmMDFfForm Controls Decision Tree, by Runi Goswami‍https://lnkd.in/e4NM5sgkHappy decision planting, everyone! 🎉🥳