Loading…
Browse by type
Explainer reads
Explainer posts on Yomu, summarised newest first.
- 1,372 posts
- 20 companies
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.
Explainer posts
Your Privacy Ecosystem Is Crucial In The Age Of GDPR - Inside
GDPR is a major regulatory change affecting all companies with EU customers globally, standardizing data handling and requiring legal justification for processing and user data rights. A privacy ecosystem includes all vendors and integrations sharing customer data, and the weakest link determines overall security, as a breach anywhere damages trust. Companies must invest in security programs with penetration testing, continuous monitoring, vulnerability disclosure, staff training, and a healthy paranoia about risks to protect against external attacks and data breaches. They should track and reduce unnecessary data access, choose vendors with contractual assurances and mature security, audit third-party providers regularly, and establish developer guidelines for integrations. Active communication and transparency about data storage, retention, and deletion are crucial for customer trust, and properly trained sales and support teams can turn GDPR compliance into a marketing differentiator.
Behind the design work of Building Intercom - The Intercom Blog
For the ‘Building Intercom’ event page, the design team aimed for an ‘unapologetically nerdy’ aesthetic to appeal to engineers without resorting to tired clichés. The author discovered the Hershey fonts, originally created in the 1960s by physicist A.V. Hershey, and revived them into functional font files using FontSelf and then Glyphs for weight variations. A small Python script automated placing outlines into a .glyphs file, and Paper.js enabled interactive vector animations. Testing revealed issues such as event details being overlooked, Paperscript’s JavaScript evaluators forbidden by Intercom’s security team, and poor mobile browser support for Paper.js. The project reinforced the value of taking meaningful risks in design and development, reminding the author that overcoming fear of consequences is part of the work.
Why you should have skin in the engineering game - The Intercom Blog
The post compares the high-stakes feedback of professional cycling to engineering, noting that engineers in growing companies often become disconnected from customers through support teams and product managers. The author, a former cyclist, advocates for engineers to maintain ‘skin in the game’ by personally connecting with customers. Intercom enforces regular customer days for all employees to give first-hand exposure, uses GitHub integration to easily dig into real customer conversations, and encourages direct outreach for complex issues. Working through a subtle bug caused by a feature update, the author iterated directly with a customer for a week, restoring their broken workflow. This personal investment in outcomes motivates engineers and ensures their work has real impact, while the post encourages others to seek similar practices.
Understanding the customer success pyramid - The Intercom Blog
The post introduces the Customer Success Pyramid, a framework modeled on Maslow’s hierarchy of needs, to help businesses understand and meet customer needs. At the base is providing precise and accurate support, which builds trust and must be maintained as the product and team grow. Above that is promptness, meaning being fast when it matters, such as using real-time chat during a customer’s early days. The middle levels focus on being personal to build rapport and personalized by using customer data to tailor interactions without being intrusive. Higher levels include preemptive support, where businesses identify problematic patterns and intervene before the customer notices, and prescience, where AI and machine learning automate this proactive guidance; the post notes that operating higher on the pyramid increases the likelihood of successful outcomes.
Embracing a human tone in customer support - The Intercom Blog
The post argues that making customer support conversations more human, by acknowledging emotions and personal context, is key to delivering next-level service, especially on chat platforms like Intercom. It advises support reps to recognize ‘signs of life’ such as crying emojis or a simple ‘how are you?’, and to respond truthfully rather than with a robotic script. When agents inevitably make mistakes, such as sending the wrong link, they should own the error transparently and use humor or emoji to diffuse tension. Emoji and GIFs are encouraged in light moments, but the human tone should not be forced; it works best when natural and when reps look beyond conversations to gather candid product feedback. Over the long term, personal interactions make support faster by building familiarity with customers, allowing reps to recall context at a glance.
Using Intercom to design Intercom - The Intercom Blog
A designer at Intercom explains how the team uses their own product to gather data-driven insights for design decisions, replacing intuition with evidence from real customer interactions. Support team members tag feature requests and confusing conversations, which the research team organizes by topic for easy access. In one example, the designer analyzed 120 conversations about multi-person messaging and found only 33% actually wanted that feature, while others needed handoff or transfer capabilities. In another, an automated message targeting users who sent one-to-one messages via the fully featured editor revealed within hours that the ability to duplicate messages was the missing feature. This approach ensures design solutions are based on real customer needs rather than surface-level requests.
Your product is already obsolete - The Intercom Blog
Technology products inevitably become obsolete as industries shift, and failing to adapt can kill a business faster than most founders expect. Success breeds complacency, which breeds failure, making paranoia a necessary survival trait for everyone in tech. Historical examples like satnav manufacturers gutted by the iPhone and telcos disrupted by WhatsApp show that customers will abandon an incumbent for a simpler, faster way to achieve their goals. To avoid this fate, Intercom advocates thinking of a product as a flexible system rather than a set of screens or user flows, allowing it to integrate across new mediums. This systems approach enables the product to remain relevant through multiple technology cycles by focusing on helping customers make progress in their lives.
The golden mean of design and engineering - The Intercom Blog
The post draws on Aristotle’s golden mean to argue that great products require a balance between design and engineering, not compromise. Engineers naturally focus on functionality and performance, wanting to ship features and increase speed often without customer requests, while designers aim for optimal user flows and catch subtle interaction details. The OAuth implementation exemplifies this, with engineers building the technical side and designers crafting user flows, each pursuing their own self-interest through daily stand-ups and whiteboard sessions rather than compromising. This self-interest, guided by Adam Smith’s invisible hand, yields superior products than continual compromise, which leads to mediocrity. The post recommends embedding designers in product teams via a hub-and-spoke model, and leaders trusting their teams to find equilibrium rather than imposing rules.
Empathy: the key to better support content - The Intercom Blog
As businesses scale, they risk losing touch with customer problems, which becomes apparent in support content. The post argues that empathy—both cognitive and emotional—is essential for creating effective help content. Cognitive empathy involves understanding customer perspectives by surrounding oneself with customer information, as Harley Davidson does with bike trip photos, and by staying informed about product evolution through conversations with design, support, and engineering teams. Emotional empathy requires experiencing the frustrations customers face, such as imagining a world without the product’s key features or actively finding and reporting bugs to understand user pain, as encouraged by Intercom’s “if you find something broken, you now own fixing it” poster. By combining both types of empathy, support writers can produce content that resonates with users and addresses their real needs, as shown in Intercom’s Smart Campaigns and User Map documentation.
Multi-Tenant SaaS Apps with Auth0 Organizations — Part One
Auth0 Organizations provide an isolated workspace per tenant with dedicated members, identity provider connections, metadata, and role-based access control, addressing enterprise requirements like Acme Corp’s SSO ultimatum. Login flows differentiate between B2C users (no organization parameter) and B2B users (organization parameter scopes connections, branding, and token claims including org_id). Home Realm Discovery automatically matches users to their enterprise IdP by email domain when an organization is set, requiring the Identifier First authentication profile and eliminating password prompts. Authorization is per-organization via org_id claims in access tokens, with organization-level roles and permissions resolved through RBAC. The post also covers invitation tickets, tenant context switching where users obtain new tokens with a different org_id, recommends one Auth0 Organization per app tenant, describes Auth0 Actions for custom metadata, and introduces this as part one of a five-part series on B2B identity.
Production-grade LLMs and agents: a field guide
Production-grade LLM agents require deterministic machinery around the probabilistic model, not a larger model. A maturity model defines six levels: determinism, evaluation, confidence, safety and governance, operability, and production-grade build, each assuming the one below. Teams should fix their weakest level in order, starting with determinism before evals, and contain the model to a single node in a fixed graph where it proposes actions a separate component applies after approval. A self-assessment checklist with items like evals as a CI gate and layered guardrails helps teams identify their current level, with fewer than half ticked indicating they are earlier than the demo suggests. The post links to a series of 25 deep-dive articles covering each rung of the maturity model.
Part 5: Operating an LLM system: observability, cost, routing, and the platform underneath
Level 5 covers operability for LLM systems: daily running, cost control, provider outage survival, and fast shutdown on misbehavior. A single gateway funnels all model traffic, measuring cost, routing requests, enabling failover, and hosting an instantaneous kill switch; a shared decision_id threads metrics, logs, traces, and the audit ledger. Observability supplements RED metrics with a decision layer capturing auto vs. human splits, guardrail blocks, judge disagreements, token spend per tenant and capability, and shadow-eval pass ratios via tiered structured logs. Cost controls attribute spending at the gateway per tenant and capability, with hard budget ceilings; optimization follows order: skip model, batch, cache, right-size, trim—each step profiled against quality. The platform spine includes stateless agent services, the gateway, an audit datastore, cache, secrets store, and object storage—scoped with least-privilege IAM and encryption, avoiding queues or vector stores until warranted.
Ways to think about customer onboarding - The Intercom Blog
Customer onboarding is critical, yet most apps lose half their new users by the second day because it fails to deliver real value. Instead of focusing on feature adoption like creating a to-do list, onboarding should help users achieve their ultimate goal, such as delivering a project on time, turning them into superheroes. The Jobs-to-be-Done framework reveals the motivations driving sign-ups, enabling segmentation and tailored onboarding flows for groups with similar needs. The four forces model adds context by showing push and pull factors when users switch, maximizing forces for change like long email trails and minimizing resistance like switching anxiety. Finally, behavior-based messaging should be scheduled by time with a priority list rather than predefined sequences, avoiding the complexity of N-dimensional decision trees, as implemented in Intercom’s Smart Campaigns.
Content as a growth engine for your business - The Intercom Blog
Content marketing advice often focuses on promotion rather than the substance of the content itself, leaving businesses without a clear strategy. Drawing on his experience leading Intercom’s content team and two decades as a journalist, John Collins argues for evergreen content that addresses timeless themes like filing a good bug report rather than news events. Evergreen content decays slowly and provides a compound return, with analysis showing it grows traffic three times faster than news-focused blogs over a year. He applies a journalist’s 5W and 1H framework—who, what, where, when, why, how—to plan content strategy, emphasizing that specialists should write, topics should help customers solve problems, and content must be relevant to the business. Collins concludes with four key takeaways: stay committed for the long term, make content relevant, impose a high editorial bar, and embrace unexpected benefits like easier hiring.
Build your customer relationships around consistency and trust - The Intercom Blog
The Industrial Revolution scaled business reach but separated owners from customers, forcing service through mail or phone, a pattern that the internet initially continued. Now, consumerization of technology provides tools for human interaction at scale, enabling businesses to return to building personal relationships online. Amazon exemplifies this by minimizing customers’ total cost beyond price—time, mental energy, and uncertainty—through frictionless purchasing, easy returns, and proactive resolution of issues. To build trust, businesses must help customers succeed, invest in relationships by being generous and never transactional, and be available on customers’ preferred messaging apps like Messenger or WhatsApp without requiring repeated context. Consistent behavior over time builds brand reputation, and businesses should engage on review sites and social media to shape their message and earn trust, as perception eventually matches reality.
Inside Intercom New York startup panel - The Intercom Blog
At an Intercom World Tour panel in New York, founders from Augment, an AR platform; Greenhouse, recruiting software; and Hello Alfred, on-demand home services, shared lessons on building emerging technologies. Mike Boufford of Greenhouse described fixing bugs by chatting with customers and deploying fixes within minutes, demonstrating how product and support intertwine. Christian Bjelland of Hello Alfred explained that their service must advocate for customers when real-world problems like lost laundry occur, requiring quick reactions. On growth, Boufford advised proving product-market fit before raising money, while Bjelland stressed dense, sustainable growth in specific zip codes to maintain quality. Lindsay Boyajian of Augment noted that no AR platform existed before, so constant user feedback and rapid iteration are critical to building a useful product.
Design in the age of entanglement - The Intercom Blog
The post argues that product design has entered a fourth era, the age of entanglement, following three earlier phases: augmentation, the PC era, and the web era. The author claims that three overlapping technology trends that made innovation predictable are ending, creating uncertainty. Designers now face a complex web of interconnected ideas, technologies, and systems that no single person can fully grasp. The post advises designers to think in systems, build one thing at a time from the center outward, and observe and iterate based on real-world reactions. It suggests that this uncertainty may be a return to a more natural state, where technology takes its rightfully uncertain place in the world.
Inside Intercom London startup panel - The Intercom Blog
At the first Inside Intercom World Tour stop in London, startup founders Bridget Harris, Will Swannell, and James Blackwell shared insights on building great products. On pricing, James advised setting it at the high end you think you can get away with, while Bridget regretted offering a free product that forced later price increases; Will argued simplicity is key, with the cost answer in two words. For hiring, Bridget uses a process of elimination to avoid bad hires and recommends remote options; Will noted HR’s importance is often underestimated. On funding, Will said crowdfunding builds a community of buyers, while Bridget warned VC funding changes priorities. The panel also stressed measuring customer acquisition through each interaction to profit, treating every interaction as a sales opportunity, and ensuring the product solves a real problem; James added that great products create moments of delight when things just work.
How users understand new products - The Intercom Blog
Users form different mental models of the same product based on their experiences and assumptions, as illustrated by the “draw toast” exercise where people depict the process in diverse ways. When a product’s system model—how it actually works—aligns with a user’s mental model, the interface feels intuitive; a mismatch causes confusion. To discover these mental models, product teams should talk to users, ask them to draw how they believe the product works, and listen to the nouns and verbs they use. Designers can bridge gaps by employing standard interface patterns (e.g., buttons that behave like buttons), using customers’ own language, and leveraging metaphors like Apple Wallet’s ticket-like appearance or Nest’s dial-based thermostat interface. When a product cannot mirror existing mental models, teams can educate users through tutorials and walkthroughs, similar to video game onboarding, helping customers learn new concepts and quickly grasp the product’s value.
Content strategy: How words build a product - The Intercom Blog
Words in a product evolve like the Ship of Theseus, with each change affecting identity; the term “page” long constrained web design, showing how working titles gain unintended baggage. Intercom’s content strategy transforms this organic dialect into an intentional one, addressing team silos and UI inconsistencies. They categorized every visible word—objects, views, people, actions—into a taxonomy and glossary that gave consistency and control over how each part is described and how parts relate. They interviewed all teams to map natural vocabularies, discovering job-related differences and treating them as assets. Finally, they derived three UI writing principles: speak naturally, speak directly to the user but never for the user, and guide users through complex ideas, recommending that content strategy start after discovering the organic voice already present.
Top topics
- Architecture834
- Performance816
- LLMs660
- Machine Learning622
- Open Source563
- AI Agents553
- AI470
- Developer Experience448
Weekly digest
The best engineering reads, once a week.