Key Takeaways

  • Linear uses a weekly ritual called Quality Wednesday where every employee finds and repairs at least one defect in the live product.
  • The goal is not ticket throughput: Saarinen designed the ritual to train the entire team to see subtle craft defects like broken hover states and rough animations.
  • Fixes are intentionally small, often taking five minutes rather than turning into multi-week engineering projects.
  • The team presents their findings in a shared weekly review so new hires absorb the company's definition of craft from peers.
  • This practice forms the core of the Linear's Quality Wednesday Ritual.

The Linear's Quality Wednesday Ritual

Step 1: Inspect the Product Weekly

Every week, task team members to spend dedicated time exploring the live product to spot subtle defects, such as janky animations, copy errors, or broken hover states.

Step 2: Ship a Fast Fix

Have each participant fix at least one identified defect directly (often a 5-minute task rather than a major refactor).

Step 3: Shared Review Meeting

Gather the team in a weekly meeting where everyone presents their findings and fixes, training the broader organization's eye for quality and aligning design standards.

When This Works (and When It Doesn't)

Saarinen created this ritual to solve a common scaling failure: new hires arrive with different definitions of quality. As Saarinen explained, “We notice that not everyone has the same standard or understanding what quality means.” Instead of creating a design approval gate that slows down shipping, Saarinen turned quality into a recurring habit.

This works because taste is a muscle built through repetition. As Saarinen noted, “The bigger impact with this is not really that we do these fixes. The bigger impact is that everyone trains themselves to look for this, they train their eye to notice the small mistakes.” When team members share their findings aloud, engineers and designers see what their peers pay attention to. “Because we do this in a meeting, everyone shares their findings and their fixes. Everyone can learn from that and see how other people are finding these problems.”

This method breaks down when teams use it as an excuse to avoid hard architectural fixes. A product with twenty fixed hover states still fails if the core database schema is broken or the onboarding flow confuses users. It also fails if leadership treats it as a shaming exercise rather than a collective learning session.

What to Do With This

Set a 45-minute calendar block this Wednesday for your engineering and design team. Give everyone 20 minutes to click through your live onboarding flow, find one broken UI detail (like an unaligned icon or awkward copy string), and fix the code directly. Use the remaining 25 minutes for a quick screen-share session where each person shows the before-and-after of what they shipped.