Sean Dexter

@brian_lovin maybe consider audio for alt solution to your stated chat usecases(my recent tweet link)? & learn from Meta's Workchat: Don't let post-focus = self-promo noise, response pressure > being left on read. channels are easier to navigate to specifics - feeds you can ONLY search/save

Chatting with your team is good. Using chat to make big decisions, share project updates, give design feedback, or have topic-based conversations is bad. Chat: • Harder to search • Not async friendly • Noisy and hard to keep up with • Creates pressure to respond quickly We spend a lot of time thinking about how to help teams improve their communication hygiene by default. One of the more effective tools we've found is changing how chat looks and feels — bubbles instead of block-based text formatting. Our bubble UI makes chat feel perfect for quick questions, ephemeral culture-building, or real-time collab. The size of the chat input is itself a subtle cue that you should share small ideas; big ideas go in posts or docs. Campsite chat is still powerful — share any file, react, reply, and edit messages (with a handy keyboard shortcut). And it's really easy to convert a message into a new post to gently guide conversations to the right format! We're hearing from teams that switch to Campsite that they're graduating from chat to posts as their primary communication method. This is helping them become more async-friendly, more organized, and reduces the noise/distraction for everyone else.

I've got thoughts on the Slack "huddles" feature: link.medium.com/qbi53CG36Jb

“I don’t do 1-on-1s, and almost everything I say, I say to everybody all the time.” This reminds of the idea of designing in the open. For example, I’ve seen before where you design in a silo. You then share your work to your immediate stakeholders. Then these stakeholders take it to their stakeholders for approval. That’s a whole load of effort and risks your message being watered down by the time it gets to the decision maker. Alternatively work in the open and flatten the hierarchy.

Good riddance. Thanks Jensen. 1:1s are highly overrated:

@hey_madni scrum masters panicking rn

12. Meeting AI

Less than 3 hours since OpenAI announced GPT-4o, and the hype is unreal. Here are 16 wild examples you don't want to miss: 1. Interview preparation

4pm, Saturday, 24 June, Moscow While access to Red Square is blocked off, it’s calm around the Kremlin. Plenty of tourists still walking around, and business as usual, amid reports that Wagner forces are en route to Moscow

@AdhamDannaway Yes! Consistency is only valuable insofar as it leads to better solutions. The internal logic of designers is rarely evident to users - they mostly take every component on its own terms anyways. Better to optimize for "best" over "most consistent" when the two conflict

As expected, it seems like most prefer B. I’ll admit that it looks and feels better. Perhaps we’re just used to seeing it on our iPhones? 📱 The issue is that B diverges from the colour system. Elevated surfaces should have slightly lighter shades of the main background grey in dark mode. The white handle in option B is also much higher contrast in dark mode compared to light mode, which is inconsistent. Are we saying that we should break the rules and introduce system inconsistency if it looks better? 🤔

A or B? 🤔 Given the following slider component in light mode, what colour should the handle be in dark mode? PS This slider component is part of a design system I'm working on to go with my book @PracticalUi 📘 #design #designsystem #ux #uxui #uxdesign

it’s a shame how narrowly some design managers evaluate prospective hires. noticing a trend where designers only work in the same style role regardless of the company. there are some of us who can be trusted to tackle anything - growth, core, design systems, ads/partnerships, b2b, etc.

My experience has repeatedly proven this Paul Graham quote to be true. Three implications: 1. Writing cultures tend to learn faster than those that use slides, dashboards, or other mediums. 2. They learn faster because they present denser information to readers, but even more importantly because they help writers think more clearly. 3. As you become more senior, it is very dangerous to only review work from other people. You must keep writing yourself.

@johncutlefish I always try for #3. Sometimes with "UX needed"/UX ready" tags to indicate what I need to work on and what's ready for engineering.

“So they’re just giving the engineers files without naming their layers. It doesn’t really impact the build but it’s something I would never do because I think the engineers might get confused and not know the image is an image or the button is a button”

If you use WCAG 2.x for light mode, and then APCA for dark mode, then you have met legal requirements. WCAG 2.x only requires ONE mode to meet 1.4.3. Regardless, APCA so completely stomps on WCAG 2 for dark mode, that should never have been a concern. #a11y #color #colours

@AdhamDannaway Left is better. Better accessibility since it's more likely to pass the straw test. Eventually you will have larger or Fullscreen modals and right aligning ctas means some will not notice them on larger screens. Left is more in line with f pattern scanning.

Which type of designer are you? 🤔 Vote for left or right aligned buttons in dialog boxes and explain why. #design #uidesign #uxdesign #uxui #productdesign #ux

Alan Moore giving the best writing advice I have ever heard

@peterme There are plugins to suggest min touch targets. Human judgement is better for handling anything more complex IMO. Fitts law isn't really straightforward in application. A more granular tool might easily mislead some designers more than help them.

Why don't any of the supposed "digital design" tools have any guidance/assessment for known cognitive/ability matters like Fitts' Law (which is straightforward)? (en.wikipedia.org/wiki/Fitts%27s…) I'm tired of mis-tapping/clicking because UI designers don't understand the basics.

ANNOUNCING BRIDGE PCA 100% backwards compatible with WCAG_2 contrast, but using APCA technology. Lc 60 exceeds WCAG 3:1 Lc 75 exceeds WCAG 4.5:1 Lc 90 exceeds WCAG 7:1 Polarity aware, modified for backwards compatibility (at a loss of flexibility) install: npm i bridge-pca

WCAG 3 will use a new color contrast method called APCA (Advanced Perceptual Contrast Algorithm). It's a big improvement over the current system but there are a lot of changes to get your head around. 🧵

Figma continues to skyrocket — 63% reported it was their primary UI tool buff.ly/3lO5WwL — by @seandexter0

Wrote about Figma taking over the world: seandexter1.medium.com/figma-continue…

@johncutlefish Hubspot was mostly sales driven initially.