Chris ッ

Wait…what’s up with the 4 image limit on here? That seems absolutely archaic 🤡

The idea is that eventually everyone develops an eye and a goal of ensuring the quality bar is always met or exceeded.

Hope that helps – let me know if you have any other questions. Sorry this was so long 😌

5% of the roadmap for quality improvements might be a good starting point to see if that’s feasible and can be committed to by a single team as a pilot. If it works out and is successful, you can graduate that to more teams for future quarters.

Last (and hardest) step is getting support for the initiative in the org. Great managers help but you’ll still need buy-in from product and eng and any of the teams to pick up work alongside other important projects.

All of that should give you alignment on what meets the quality bar and help you break these out into a prioritized backlog.

1) Meets quality expectations, minimal rough edges
2) Not meeting most quality expectations, lots of rough edges
3) Meets no quality expectations, detrimental to the experience)

(Feel free to come up with your own system)

Next is documentation (screenshots or recordings) to highlight issues & annotate why it doesn’t meet the quality bar. I categorize into 3 buckets focused on elements within major journeys.

Then, it’s a good time to get into a habit of providing extremely detailed and pointed feedback on designs that are in flight (if you’re not already doing this). It’s extra work but necessary to sharpen your eye and help people develop their own so quality issues never happen in the first place.

Why is quality so rare? - Linear Now

There’s a non-zero chance that you’re the only one who recognizes this.

You also need to be able to define what ‘quality’ means with your team. There are so many resources and opinions on this.

Some of the Linear posts recently are particularly inspiring.
linear.app/now/why-is-q...

First step is recognizing you have a ‘Quality’ issue in the first place. If you use your product on any regular cadence and notice poorly implemented designs, disjointed experiences that lack cohesion or consistency, poor interactions, confusing content, etc… then it might be time to make a case.

For sure! Can share some details tomorrow when I get some time.

Have officially started the 'Design quality' initiative in my org at work.

Feels really good to finally put some definitions and practices in place that fly directly in the face of the garbage being churned out from 'vibe coding' and 'move fast break stuff' BS

Spent the last few years learning how to ski.

I think I’m going to switch things up this winter and focus on snowboarding. And trying not to break any bones 🩻

AI ‘Workslop’ Is Killing Productivity and Making Workers Miserable AI slop is taking over workplaces. Workers said that they thought of their colleagues who filed low-quality AI work as "less creative, capable, and reliable than they did before receiving the output."

www.404media.co/ai-workslop-...

Some PMs have never been gamers and it shows

You know you made the right Airbnb decision when they've got Hitchens on the bookshelf.

That's not what design is or does and it's actually hilariously and sadly ironic that the same people who historically complained that they weren't included at the start are now committing the same "sins".

Internal resistance to this growing momentum feels impossible. It seems like we (design) are inching ever closer to being brought in at the end to "do design" or "make it look good".

Everyone is so consumed with creating as fast as possible because any output is being more highly-valued than positive outcomes. With AI enabling more roles to jump in and contribute it's becoming increasingly more difficult to control quality because "That's so cool! Let's ship it!"

hiya. figma is a fucking terrible source of truth. if you're building one of the 142,000 AI-powered design system tools out there right now, binding your 'truth' to a proprietary file format in a proprietary platform from an org that’s showing some shaky signs is just extremely Not The Way™.

From now on I'm making a point to use the correct language to describe technology that is currently described as "AI."

An LLM isn't AI
Image generators aren't AI
Machine learning isn't AI
Algorithms aren't AI

AI is a marketing term that obscures meaningful critique of real technologies.

Not really an overstatement to say that the test of a free society is whether or not comedians can make fun of the country's leader on TV without repurcussions.

Had a lovely Labor Day weekend over in Eastern Oregon. The Wallowas are great — wish they were closer.

It's so hilariously unnecessary and the use-cases on the website are some of the most uninspiring examples.

Stumbled across this gem yesterday (and all linked gems within) a-website-is-a-room.net

Editorial: Bend should explore boosting neighborhood shops The city changed its code to allow more. Nothing much has happened. It is time to take another look at the code.

What if we re-legalized neighborhood businesses in Bend? People love a lot of the existing ones like Bruno's

bendbulletin.com/2025/08/20/e...

5 for 5 today on people who clearly lied during the screener questionnaire on User Interviews. Seems like these people are gaming the system for the paid incentives. Cool cool cool.

There has to be a better way to vet people...

Most people will never know the pain of sitting through a usability test interview with a participant who clearly lied during the recruiting process and hasn't actually used the product.

Amongst a sea of todo apps, nothing comes close to the tactile feel and satisfaction of checking things off with pen and paper.

In Baker City, OR for the last night of my moto trip. Staying at a hotel with an attached restaurant. They serve American and Indian food, are blaring country music periodically interrupted by Spotify commercials, and cricket is on the big screen in the bar. Truly a unique dining experience.