Why Developers Lose Touch With Users

Most software teams rely on customer support, chatbots, or contact forms as the only communication channel between the people who build a product and the people who use it. As a company grows, the gap widens: developers get requirements, ship projects, and fix bugs that surface after launch, but rarely hear directly from the end users whose workflows depend on their code.

The result is twofold. Developers become disconnected from the products they build and the people they build them for, and that distance breeds a lack of empathy that can quietly degrade product quality over time. When engineers only see support tickets secondhand—filtered through advisors who may not capture the full context of a customer's frustration or workaround—they miss the nuance that comes from direct interaction.

The Case for Closing the Distance

Creating a direct line between developers and customers yields measurable benefits that go beyond surface-level satisfaction. Four stand out at Shopify:

  • Perspective on real product usage — Developers often deliver against a requirements list, but customers may interact with the product in unexpected ways. Hearing customers describe their problems firsthand builds context that a support ticket cannot convey.
  • Workarounds as product insights — End users routinely find creative paths to the functionality they need, such as using one product feature to compensate for a missing one. These workarounds are a goldmine for deciding what to build next, whether that means bug fixes, improved versions, or entirely new products.
  • Broader domain knowledge — Customers ask questions across the full product surface, not just the slice an engineer works on. Listening to those questions pushes developers to explore unfamiliar areas and cultivates T-shaped skills—deep expertise in one domain with working knowledge across others.
  • Interpersonal growth — Support interactions require patience, active listening, and honest expectation-setting. When a frustrated customer wants an immediate fix that won't come quickly, the right response is not a false promise but a candid explanation that puts them at ease.

Shopify's Approach: Bridge the Gap

To operationalize this philosophy, Shopify launched the Bridge the Gap program in 2014. Its mission is straightforward: give every employee, regardless of discipline, the opportunity to connect with merchants in a human way through the Support organization. The program runs through three channels.

Workshops

These sessions focus on specific areas or topics within the platform, diving deep into how merchants experience that part of the product. Attendees are free to ask questions throughout, gaining context and clarity that would be hard to acquire from documentation or code reviews alone.

Internal Podcast

For asynchronous learning, the podcast features recorded clips from actual support calls followed by a discussion between the Support Advisor who handled the call and a host. It lets employees absorb merchant stories at their own pace without needing to block out a live session.

Shadowing Sessions

Employees can shadow a Support Advisor for an hour while they handle real-time questions from merchants via chat, phone, or email. Sessions may be broad or scoped to a specific segment such as marketplaces, partners, or Plus merchants. Participation is voluntary but strongly encouraged within the company.

Shopify's mission is to make commerce better for everyone, and keeping the end user in mind is central to that goal across every team. Bridge the Gap is the mechanism that turns that mission from an abstract principle into a regular, concrete practice for the people who ship the code.