Why No One Can Agree on the "New" Button?

https://www.ssw.com.au/rules/the-value-of-consistency

Contact us: https://bit.ly/4fAFrVx

Why can’t developers agree on UI design? Whether it’s the “New” button in Outlook, the “Post” button in LinkedIn, or the “+” button in Discord—consistency is the key to a great user experience. In this video, Adam Cogan breaks down why UI/UX consistency is broken across the industry and why we need to do better. Which app do you think has the most confusing UI? Let us know in the comments

00:00 | Introduction: Why developers follow SSW Rules
00:13 | The UI Consistency Problem
00:19 | Where is the “New” Button? (Toast Message examples)
00:27 | The “New” Button Rule
00:35 | Real-world check: Outlook, LinkedIn, and Discord
01:45 | The state of our industry
01:52 | How you can help: SSW Rules on GitHub
02:14 | Conclusion

About SSW: https://linktr.ee/SSWTV
Links:
LinkedIn: https://linkedin.com/company/ssw
Twitter: https://twitter.com/ssw_tv
Facebook: https://facebook.com/SSW.page
Instagram: https://instagram.com/ssw_tv
Tiktok: https://www.tiktok.com/@ssw_tv

Get in touch: Adam Cogan – SSW Chief Architect + Microsoft Regional Director About: https://www.ssw.com.au/people/adam-cogan/
LinkedIn: https://www.linkedin.com/in/adamcogan/

#sswrules #uiux #softwaredevelopment #consistency #uxdesign #softwareengineering #coding

V5 – Lydia

About the speakers

Adam Cogan blogs at adamcogan.com and interviews for SSW TV frequently. He is the Chief Architect at SSW.

Treat Your Code Like Uranium | Adam Cogan

Adam Cogan shares a striking story comparing two World War II factories—one ordinary, one handling uranium—and the surprising lesson that the uranium workers lived longer because they followed disciplined, risk-aware practices. He connects that idea to software teams: the best outcomes come from careful habits like automated tests, telemetry, pull requests, retrospectives, shared rules, and good tools. The message is simple: treat software delivery with the same respect as dangerous work, and you’ll reduce stress, avoid chaos, and get better results.

3 Tips for Better Video Recordings | Adam Cogan

Great coaching can dramatically improve how you present, communicate, and learn. In this video, Adam Cogan shares 3 practical coaching tips that SSW uses every day—from onboarding and role plays to improving video delivery. He explains why having a coach matters, why immediate interruption beats delayed feedback, and how repeating corrections helps lock in better habits.

TinaCMS + Fumadocs: Bring Visual Editing to Your Docs | Hark Singh

Discover how to connect Playwright with AI agents and unlock powerful workflows.

Stop Using 👍 Wrong in Teams | Adam Cogan

A quick communication tip from Adam Cogan: don’t use 👍 as a catch-all response when someone assigns you a task in Teams, Slack, or Google Chat. In the example Adam gives, if a task will take about five minutes, a thumbs up is too ambiguous because it does not clearly say whether you’ve read it, agree with it, are doing it now, or will do it later. Instead, use 👍 for agreement, 👀 to show you’ve seen the task and are actively working on it, and then replace 👀 with ✅ once the task is done. It is a small change, but it removes ambiguity and cuts down unnecessary follow-up messages.

How to record a done video in SSW | Sylvia Huang | SSW Rules

Sylvia Huang from SSW shares her SSW Cultural Exchange experience from Hangzhou, China to Australia

4 Essential Sales Tips for Engineers | Adam Cogan

Not a salesman? No problem. Adam Cogan shares 4 practical tips to help engineers navigate sales meetings with confidence. Learn how to stop “selling” and start solving, how to talk numbers without the awkwardness, and why being transparent about your process wins more clients.

Do you explain why you’ve deleted or updated an appointment? | Adam Cogan | SSW Rules

Ever wonder why a meeting was moved or cancelled? Adam Cogan explains the “Secret Ingredient” to professional scheduling: always include a version history and reason for change at the top of your appointments. Improve clarity, keep a record of changes, and hold participants accountable with this simple SSW Rule.

Chat first before changing others’ code | Adam Cogan

Changing someone else’s code? Don’t just dive in! Adam explains why it’s important to check the source history and talk to the original developer before making changes. A quick chat can save headaches and keep everyone on the same page. Perfect advice for devs working in teams!