
Lessons from Des Traynor
Des Traynor co-founded Intercom and changed how software companies talk to their customers. He popularized the Jobs-to-be-Done framework for product teams and spent years explaining why building great software means repeatedly saying no to new features. This profile collects his operating rules for product strategy, scaling a business, and adapting to AI.
Part 1: Product Strategy & Vision
- On strategy: "Strategy isn’t what you say you’re going to do. It’s what you say no to." — Source: [Intercom Blog]
- On core focus: "It is much easier to build a product that solves one problem perfectly than a product that solves ten problems poorly." — Source: [Intercom on Product Management]
- On product boundaries: "If you’ve never said no because of your product vision, then you don’t have a product vision." — Source: [Business of Software]
- On filtering ideas: "Ask yourself if this feature will matter in five years, or if it is merely a temporary fix for a temporary problem." — Source: [Intercom Blog]
- On mass appeal: "When you try to build a product for everyone, you end up building a product for no one." — Source: [Inside Intercom Podcast]
- On scope restraint: "Avoid the trap of the product monster. This is the bloated tool that tries to do everything and loses its core identity." — Source: [Intercom on Product Management]
- On delivering value: "Building a great product isn’t about creating tons of tactically useful features which are tangentially related. It’s about delivering a cohesive product with well-defined parameters." — Source: [Intercom Blog]
- On early traction: "Version one is easy because it is precisely what the founders want to build. The hard part is maintaining quality when external forces arrive." — Source: [Business of Software]
- On defining the negative: "Our product strategy here at Intercom very clearly states what we are not doing. There is no ambiguity." — Source: [Intercom Blog]
- On aligning features: "Is this a forward step along the path we have chosen, or are we simply reacting to a noisy customer?" — Source: [SaaStr Annual]
Part 2: The Art of Saying No & Feature Bloat
- On execution versus vision: "A strategy is only as good as your willingness to defend it against good ideas that do not fit." — Source: [Intercom on Product Management]
- On feature blackmail: "As you gain traction, feature blackmail from customers and sales teams will test your resolve to say no." — Source: [First Round Review]
- On saying the word: "If you’re building a product, you have to be great at saying no. Not maybe or later. The only word is no." — Source: [Business of Software]
- On short-term fixes: "Be careful not to swap a long-term ow for a short-term wow." — Source: [Intercom Blog]
- On hidden costs: "Small feature additions create exponential permutations and maintenance costs that eventually slow down your entire engineering team." — Source: [Intercom on Product Management]
- On the right scope: "Avoid scopes that are too big to adopt or too small to matter. Look for the 'Scopi-locks' sweet spot." — Source: [Intercom Blog]
- On sales requests: "Sales wants features to close today's deal, but product needs to build features that open up tomorrow's market." — Source: [Inside Intercom Podcast]
- On consultingware: "Do not build consultingware for a single loud user at the expense of the rest of your customer base." — Source: [Business of Software]
- On declining gracefully: "You can say no without being a jerk. Explain the vision and why the request does not align with the current path." — Source: [Intercom on Starting Up]
- On the illusion of quick wins: "There is no such thing as a quick win in software. Every line of code must be maintained forever." — Source: [Intercom on Product Management]
Part 3: Jobs-to-be-Done Theory
- On context over personas: "Traditional user stories focus too much on the person. Job stories focus on the context and the triggering event." — Source: [Intercom on Jobs-to-be-Done]
- On the Job Story format: "Frame the problem clearly. When a situation happens, I want a specific motivation, so I can achieve an expected outcome." — Source: [Intercom on Jobs-to-be-Done]
- On hiring and firing: "Customers do not merely buy products. They hire them to do a specific job. If you fail, they will fire you." — Source: [Inside Intercom Podcast]
- On unexpected competitors: "Your real competitor is rarely the company that looks like you. If your job is quick updates, your competitor is a hallway chat." — Source: [Intercom Blog]
- On predicting behavior: "The situation or context someone is in is a much better predictor of behavior than their job title or demographic." — Source: [Jobs-to-be-Done Radio]
- On building demand: "It’s easier to make things people want than it is to make people want things." — Source: [Intercom Blog]
- On switching moments: "Growth comes from understanding the exact moment a customer decides to leave their current solution and hire yours." — Source: [Intercom on Jobs-to-be-Done]
- On outcomes over features: "People do not want a faster chat widget. They want a resolved customer issue." — Source: [Inside Intercom Podcast]
- On observing struggles: "Instead of inventing a new need, find a job that people are already trying to do but struggling with." — Source: [Intercom Blog]
- On feature adoption: "If a new feature does not map to a job your customers are already trying to accomplish, it will go unused." — Source: [Intercom on Product Management]
Part 4: Customer Support & Communication
- On support as product: "Great customer support is never an operational cost. It is a core feature of your product." — Source: [Intercom on Customer Support]
- On conversational support: "Customers do not want ticket numbers. They want a conversation with a human who can actually help them." — Source: [Intercom Blog]
- On feedback loops: "The customer support team is your best source of product feedback. Do not isolate them from the product team." — Source: [Inside Intercom Podcast]
- On self-serve support: "Automate the common, simple questions so your humans have the time and energy to solve the complex ones." — Source: [Intercom on Customer Support]
- On empathy in service: "A good support interaction acknowledges the user's frustration before trying to force a technical fix." — Source: [Intercom Blog]
- On company voice: "Talk to your customers like you would talk to a colleague. Drop the corporate jargon." — Source: [Intercom on Starting Up]
- On proactive communication: "Do not wait for users to hit a wall. Reach out when you see them struggling with a specific workflow." — Source: [Intercom Blog]
- On apologizing well: "When the product fails, apologize sincerely and directly. Do not hide behind vague system issues." — Source: [Inside Intercom Podcast]
- On meaningful metrics: "Measure resolution time and customer satisfaction, not simply how many tickets an agent closed per hour." — Source: [Intercom on Customer Support]
Part 5: Scaling Startups & Go-to-Market
- On unscalable early days: "In the early days, you have to manually recruit users and hand-hold them to success. Scale comes later." — Source: [Y Combinator Startup School]
- On pricing strategy: "Your pricing shouldn't reflect only the cost to build the product. It should align with the value the customer receives." — Source: [Intercom on Starting Up]
- On your first users: "Your first 100 customers are investors in your product. Treat their feedback as your most valuable asset." — Source: [Inside Intercom Podcast]
- On product-led marketing: "The product should be its own best marketing tool. If it’s hard to explain, it will be hard to sell." — Source: [Intercom Blog]
- On moving upmarket: "As you move upmarket, the buyer changes from the end-user to the manager. Your messaging must adapt accordingly." — Source: [Lenny's Podcast]
- On understanding churn: "High churn is a symptom of a product that either doesn't do the job or was sold to the wrong person." — Source: [Intercom on Starting Up]
- On startup advantages: "Your advantage as a startup is speed and focus. Do not try to beat incumbents at their own game." — Source: [SaaStr Annual]
- On content marketing: "Write content that teaches people how to do their job better, rather than content that demands they buy your tool." — Source: [Intercom Blog]
- On launch expectations: "Your goal isn’t to win Product of the Day. It’s to start 100 meaningful conversations with potential users." — Source: [Lenny's Podcast]
Part 6: Design & User Experience
- On empty states: "Design the empty states first. That is what every single new user will see, and it dictates whether they stick around." — Source: [Intercom on Product Management]
- On managing complexity: "You cannot eliminate complexity. You can only move it around. The goal is to move it away from the user." — Source: [Inside Intercom Podcast]
- On interface speed: "A UI that responds immediately builds trust. Latency destroys the feeling of reliability." — Source: [Intercom Blog]
- On the power of copy: "Copy is interface. Good writing will solve more UX problems than a redesigned button." — Source: [Intercom on Product Management]
- On user workflows: "Do not simply design screens. Design the complete flow from user intent to completion." — Source: [Intercom Blog]
- On true onboarding: "Onboarding should not merely show people where the buttons are. It should show them how to succeed with your product." — Source: [Intercom on Onboarding]
- On the activation moment: "Identify the exact action that makes a user realize the value of your product, and design the first experience around getting them there." — Source: [Inside Intercom Podcast]
- On predictable design: "Internal consistency makes a product predictable, and predictability makes it easy to learn." — Source: [Intercom Blog]
- On sensible defaults: "Most users will never change the default settings. Make sure your defaults represent the best possible experience." — Source: [Intercom on Product Management]
Part 7: AI's Impact on Software
- On AI as a paradigm: "AI isn’t a feature. It’s a foundation shift that requires rethinking the entire tech stack and user experience." — Source: [Lenny's Podcast]
- On avoiding thin wrappers: "You’re never going to make money filling in the gaps in a platform. Do not build a thin wrapper on top of an LLM." — Source: [Lenny's Podcast]
- On the kill zone: "Customer service is very much in the kill zone of AI. Either you correct your business with AI, or the market will correct you." — Source: [Web Summit Talk]
- On resolution over deflection: "The goal of AI in support has shifted from deflection to actual resolution. If AI can answer the question, it should." — Source: [Intercom Blog]
- On new economics: "When AI happened, it was the first time software engineers had to deal with the fact that code didn’t execute for free anymore." — Source: [Inside Intercom Podcast]
- On cannibalizing yourself: "Sometimes you have to build a product that is hostile to your core business model if it is what the future demands." — Source: [First Round Review]
- On future team composition: "The future of support will be humans plus AI, with AI handling the predictable volume and humans handling the high-empathy edge cases." — Source: [Intercom Blog]
- On AI augmentation frameworks: "AI will either augment humans, do some of their specific tasks, or take over the entire workflow." — Source: [Lenny's Podcast]
- On durable advantages: "As AI commoditizes software creation, brand and community are still going to be your residual, long-term moats." — Source: [Inside Intercom Podcast]
Part 8: Leadership & Operating Structure
- On making hard choices: "If you’re going to eat dirt, don’t nibble. Make hard decisions quickly and decisively rather than dragging them out." — Source: [Lenny's Podcast]
- On operational priorities: "Take care of the People, the Products, and the Profits, strictly in that order." — Source: [Inside Intercom Podcast]
- On founder connections: "Founders must stay deeply connected to the product and the customers, even as the company scales." — Source: [Intercom on Starting Up]
- On organizational debt: "Similar to technical debt, fast growth creates organizational debt that eventually requires a painful refactoring of teams." — Source: [First Round Review]
- On scaling teams: "The person who helped you get from zero to one is not always the right person to take you from one to ten." — Source: [Intercom Blog]
- On leadership alignment: "If the leadership team isn't completely aligned on the why, the rest of the company will execute in chaotic, opposing directions." — Source: [Inside Intercom Podcast]
- On sustaining velocity: "Speed is a feature of small teams. To keep it as you grow, you have to deliberately design for autonomy." — Source: [Intercom on Starting Up]
- On strategic pivots: "Step one is a big, brave decision. Step two is being willing to make every self-harming decision necessary to complete the transition." — Source: [Web Summit Talk]
- On updating mental models: "The best operators are constantly updating their mental models based on what the market is telling them today, not what worked yesterday." — Source: [Inside Intercom Podcast]