IntercomProblem & solution
The key to having impact as an engineer? Empathy - The Intercom Blog
Summary
Product engineer Serena Fritsch argues that empathy for users is the key to having maximum impact as an engineer. She illustrates this with Intercom’s Snooze feature, which was built to unblock other work but created a ‘black hole’ of indefinitely snoozed conversations. The team had built the feature in isolation, focused on technical delivery rather than understanding how support agents and customers interact. After shadowing the Customer Success team, gathering feedback, and conducting a cross-functional post-mortem, they added a scheduled job that forces snoozed conversations to reopen. Fritsch concludes that solving the right problem matters more than technical elegance, and engineers must be mindful of the new contexts their products create for people.
Context
Intercom’s Inbox had only two conversation states (open or closed). Support agents closed conversations when customers didn’t respond, which distorted resolution reports. A third state, Snooze, was added to unblock other features, but agents used it to indefinitely postpone conversations, creating a ‘black hole’ backlog.
Approach / What changed
The engineer shadowed Customer Success team members, gathered customer feedback, and conducted a cross-functional post-mortem with designers, analysts, researchers, and PMs. The team then added a scheduled job that forces snoozed conversations to reopen by placing them on an SQS queue for state change.
Takeaways
Building a technically correct feature in isolation can create new problems if the team lacks context about how users actually interact with the product.
Shadowing customer-facing teams and gathering direct feedback helps engineers challenge their preconceived ideas and learn what is actually true about user behavior.
Cross-functional post-mortems with designers, analysts, researchers, and PMs can uncover why a solution failed and inform a better iteration that solves the right problem.
FAQ
Why did the first Snooze feature fail?
The first version of Snooze never reopened a conversation unless someone replied, so agents could snooze indefinitely, creating a large backlog that analysts called the 'black hole of Snooze.'
What caused the team to build the wrong solution?
The team built Snooze in isolation with the wrong motivation: they were focused on unblocking other Intercom features rather than understanding how support agents and customers actually interact. They lacked context around that interaction.
How did the engineer build empathy for users?
The engineer shadowed the Customer Success team to observe real usage, gathered all available customer feedback, and held a cross-functional post-mortem with designers, analysts, researchers, and PMs to discuss solutions for the next iteration.
Source and freshness
- Source
- intercom.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.