Many customer experience teams act as message relays. They collect a bug report, forward to engineering, and wait. Linear's CX team does the opposite: they investigate deeply before escalation, enabling engineers to fix bugs within strict SLAs based on severity.

Linear's CX team's upfront investigation work to gather logs, document reproduction steps, and provide complete context is what makes their zero-bug policy possible. Alexandra Lapinsky Wilson, who leads customer experience at Linear, explains that when CX teams do thorough troubleshooting before escalation, engineers can act immediately without back-and-forth. The work required to fix a bug is identical whether you do it now or later, but immediate fixes spare users pain while building trust - and it's the CX team's preparation that enables speed.

Redefine What Counts as a Bug to Validate User Perception

Linear's CX team uses a radically user-centric definition that eliminates adversarial "that's expected behavior" responses. Wilson explains: "Anything that a user feels is a bug is warranted to be filed as a bug. So if something feels incorrect, not behaving as expected, then it's a bug."

This definition empowers the CX team to validate user perception from the first interaction. Instead of dismissing concerns with technical explanations, Linear's CX team investigates every report where something doesn't feel right. Lapinsky Wilson notes she's worked in environments where sharing user concerns resulted in dismissive responses from engineering. At Linear, the CX team is actively encouraged to advocate for experiences that don't feel right.

This approach transforms the CX team's role from complaint management to user advocacy. Users feel genuinely heard because their perspective is validated. Frustration is minimized because issues get fixed before others encounter them. And trust increases as users see the CX team's commitment translating into actual product improvements - often within hours of reporting.

Do the Investigation Work That Engineers Need

The zero-bug policy succeeds because Linear's CX team does substantial investigative work before bugs reach engineers. Wilson describes the team bringing "a lot of empathy and also a lot of detail and diligent troubleshooting" to reduce confusion about core issues.

When reports come in, the CX team gathers logs, documents exact reproduction steps, and investigates the complete user experience: what they were trying to achieve, what steps they took, what went wrong. They use internal tools to examine feature availability for specific users. All of this happens before an engineer even looks at the issue.

This diligent preparation is what enables Linear's aggressive SLAs: high-priority bugs fixed within 48 hours, low-priority within 7 days. Engineers can act immediately because the CX team has already eliminated confusion and provided everything necessary. As Lapinsky Wilson explains, this reduces "the back and forth that can sometimes happen based on confusion or a lack of clarity upfront as to what the core issue really is."

The workflow demonstrates how CX owns the entire loop: user reports issue, CX investigates thoroughly, CX files bug in Linear with appropriate SLA, engineer fixes within timeframe, conversation automatically reopens, CX notifies user. This often happens within one to two hours of the initial report, creating a responsive feedback loop where users see their CX interaction directly driving product improvement.

Claim Agency Your CX Team Already Has

When asked how CX leaders can advocate for product quality in less supportive organizations, Lapinsky Wilson emphasizes that much of what Linear does is "within the agency of the CX team" and doesn't require organizational permission.

First, create dedicated forums for dialogue. Linear's CX team holds monthly meetings with product teams to discuss feature requests, bugs, and process improvements. Come with a strong agenda, track items for follow-up, and create space for open conversation about what will or won't be fixed and why. These conversations help the CX team feel empowered when talking to users, even when not everything can be addressed.

Second, staff your CX team on product projects. At Linear, every medium and high-priority product project includes a CX team member from kickoff through launch. Their responsibility is representing users throughout the product development cycle: early discovery, deciding on alpha or beta releases, determining which users to include in testing, planning communications, and creating enablement materials. Lapinsky Wilson notes this practice was in place long before she joined, demonstrating respect for the CX perspective.

Third, prepare thorough bug reports that enable rapid engineering response - this is entirely within CX control. Fourth, celebrate user-focused behavior. When users share positive feedback about fast fixes, make sure the responsible engineers are recognized. This builds the cross-functional relationships that make zero-bug policies sustainable.

Optimize for Quality, Let Speed Follow

Linear's CX team is known for fast response times, but Lapinsky Wilson's perspective on metrics reveals that quality comes first. While the team tracks time to first response and time to resolution, the focus remains on whether those interactions are genuinely high-quality.

Lapinsky Wilson tells her team: "I'd rather you spend more time on fewer tickets if the quality is really high." Quality is "one of those things where you really know it when you see it" - users feel heard, they get thoughtful responses, the product's intentionality translates into the support experience.

The CX team asks: was it a thoughtful, high-quality first response, not just a fast one? Was it a good resolution, not just a closed ticket? The team operationalizes repetitive questions efficiently, enabling skilled team members to provide high-quality support rather than just checking boxes quickly.

Lapinsky Wilson describes the approach as "a very beautiful blend of qualitative and quantitative." Everything the CX team does - documentation, user feedback, working cross-functionally, meeting users across channels like Slack, Twitter, or Reddit - holistically combines to create exceptional customer experience.