Slack is a loved product, and that’s not an accident

In 2013, Stewart Butterfield wrote what amounted to a promise:

“You’re buying a commitment to the craft of making high quality software: polished, responsive, attractive, simple, powerful, and, above all, useful. You’re buying attention to detail that saves you time and makes your life just a little less demanding. We are genuinely trying to sell you a simpler, more pleasant and more productive working life.”

That wasn’t marketing copy. It was a declaration of values, one that bet Slack’s entire identity on something most enterprise software companies dismiss as a luxury: caring about how the product feels.

It worked. Slack is probably the only enterprise product people describe with actual feelings of love. Not satisfaction, not productivity gains, but love. People organically rave about it. They recommend it to friends. 

That doesn’t happen because of feature completeness or competitive pricing. It happens because, at its best, Slack communicates something rare: somebody gave a damn about me.

That feeling is craft. And if we break down Slack’s mission to make people’s working lives simpler, more pleasant, and more productive, we can translate each of these attributes to ones we can make more tangible in our day-to-day product development process:

• Productive = Utility
• Simple = Usability
• Pleasant = Feel

All three, held together with care. That’s the formula. It always has been.

Why craft is hard to align on

If everyone agrees that quality matters, why is it difficult to deliver consistently? Largely because craft has properties that make organizational alignment genuinely hard:

• Craft is subjective, until it isn’t. Disagreement surfaces the moment you have to define it. Is this interaction good enough? Is this component polished? Without shared standards, these discussions become battles of personal taste rather than principled decisions. You can’t argue craft in a document. You can only experience it.
• It seems like craft competes with velocity. Engineering and Product are often rewarded for shipping, not refining. Craft requires slowing down at key moments, which feels costly when measured against sprint commitments. The incentive systems work against craft, but  this is a false trade-off: craft debt compounds just like technical debt, and eventually you pay for it in churn, reputation, and the slow erosion of what made your product special.
• We speak different craft languages. Designers talk about visual hierarchy, micro-interactions, and emotional resonance. Engineers talk about performance, reliability, and clean architecture. Product Managers talk about user value and adoption curves. All of these are craft, but without a shared language, we each optimize for our own definitions and miss the whole in the process..
• “Good enough” is a moving target. Customer expectations rise with every great product they encounter. What felt polished two years ago feels dated today. Craft isn’t a milestone you hit. It’s a discipline you maintain.
• Craft is hard to measure. You can’t put craft in a dashboard. That makes it nearly impossible to prioritize, fund, and defend, especially when it matters most.

Why craft matters more right now

The distance from nothing to adequate has collapsed. The distance from adequate to loveable has not.

AI has changed the creative landscape in a fundamental way. It has collapsed the distance between description and interaction. An interface appears immediately, behavior responds instantly, and possibility takes shape before the product even exists. Almost everyone can now be a builder, manifesting ideas faster than ever before. That is genuinely new.

What is not new is the gap between something that looks finished and something that is.

When the cost of producing “good enough” approaches zero, only the quality gap matters. And that gap, the one between functional and beloved, is exactly where Slack has always competed.

This creates specific dangers:

• The false sense of done. When you lack expertise in a domain, AI output seems perfectly fine. A generated interface looks like a finished product. Generated code looks like it’s ready to ship. The visual completeness masks absent craft, missing structure, and unhandled edge cases. “Looks finished” is not “is finished.”
• The IKEA effect at scale. When everyone can build, everyone overvalues what they’ve built. AI feeds our ego: we prompted it, we shaped it, it’s ours. The endowment effect kicks in: we overvalue what we own. We keep investing because we already started, not because it’s good. . AI output is a starting point, not a destination.
• The erosion of invisible work. Quality used to require thinking before building. Now stakeholders can see something interactive immediately. The question shifts from “Did we think this through?” to “Does it look like it works?” Visible behavior replaces invisible structure as evidence of progress.
• Mundane becomes the baseline. If anyone can generate a competent-looking product interface , competence is no longer a differentiator. The only way to stand out is to be great. As the floor rises, craft becomes the only competitive advantage.

This is not an argument against AI. AI can expedite every process we have. But AI does not feel. It can’t know what it’s like to be frustrated by a slow transition, delighted by a thoughtful empty state, or reassured by a well-timed confirmation. Humans don’t just evaluate products practically. They evaluate them emotionally. That judgment is something only we can exercise, because we feel it.

We are humans, designing for humans. That’s the job AI can’t replace, only support.

What we mean by craft

Quality is the output. Craft is the mindset that produces it.

Craft is the care, skill, and judgment applied consistently to make something great. It’s not perfectionism; it’s the refusal to accept “good enough” when “great” is achievable. It’s not slowness; it’s knowing when to slow down and where speed serves the user.

As Karri Saarinen puts it:

“Craft is the mindset that creates quality. But it’s not enough. You need to have the right skills and ideas. You need individuals who take their profession and craft seriously, then build teams that work this way together, and have a company that creates the conditions for it. Not only incentivizing with deadlines and metrics, but also caring if the experience is good enough.”

This describes a system, not an individual heroic effort. Craft scales when three things align:

1. Individuals take their profession seriously and hold themselves to a high bar.
2. Teams create the collaborative conditions for quality: a shared language, mutual respect for each other’s craft standards, and collective pride.
3. A company that protects space for craft through incentives, culture, and a leadership team that doesn’t just demand craft, but also demonstrates it

Great products require consistent, daily effort keeping the quality.

A shared framework: Utility, Usability, and Feel

If craft is the mindset, we need a shared lens for evaluating the output across different dimensions. Here’s a framework simple enough for Product, Engineering, and Design to use together in any review, planning session, or critique.

Utility: Are we solving the core job cleanly?

Utility is crossing the threshold where value actually explodes for the user. It’s the “painkiller, not vitamin” test. Core questions:

• Does this solve a real, frequent, painful problem?
• Is it worth the cost (in complexity, cognitive load, attention) to the user?
• Are we adding unnecessary complexity, or solving the job cleanly?
• Does it create social capital by making the user better at working with others?

The failure mode: over-engineering a solution, solving the wrong problem, or adding features that dilute core value.

Usability: Is it intuitive, fast, and frictionless?

Usability means zero friction to understand and use. Most product quality conversations touch on this, but we often neglect the full scope:

• Comprehensibility: Can someone understand what to do without explanation?
• Reliability: Does it work every time, in every state?
• Performance: Does it feel instant?
• Accessibility: Can everyone use it, regardless of ability?
• Predictability: Does the system behave consistently?
• End-to-end flows: Does the full journey work, including edge cases?

The failure mode: something that works in a demo but breaks in real life. Confusing, slow, or brittle experiences.

Feel: Does it feel good? Does it feel like Slack?

Feel is the hardest to define, so it’s often deprioritized.  It’s the emotional response: the judgment that happens before you can articulate it. Users often can’t explain what’s wrong with a poorly crafted product. They just know something feels off.

• Cohesion: Does this feel consistent with Slack’s patterns and conventions?
• Voice and tone: Does the language feel human, warm, playful, and confident?
• Attention to detail: Are transitions smooth? Are states handled gracefully? Do the small things feel considered?
• Emotional resonance: Does this feel especially thoughtful or refined?

The failure mode: a generic, soulless, or inconsistent experience. A product that works but that nobody would describe with affection.

• Useful + Usable = Mundane / table stakes
• Usable + Delightful (but not useful) = Gimmicky / Unnecessary / Distracting
• Useful + Delightful (but not usable) = Obscure (Dark UX patterns fit here)

The gut-check

Across all three dimensions, one question unifies them: Are we proud to ship this?

If the answer requires qualifiers (“Well, given the timeline…” or “It’s fine for v1…”), we have craft debt. Sometimes that’s a conscious trade-off. But it should be conscious, visible, and tracked, never the default.

Everyone owns this

Craft is not a Design initiative. It’s a product quality standard owned by every discipline. AI may blur the boundaries between roles, but each role still has a distinct part to play.

• Engineers own the final artifact. Performance, reliability, animation smoothness, state handling, edge case all  live in code. No Figma file ships to users. The product is the implementation. Engineers with craft sensibility are the difference between a product that works and one that feels alive.
• Product Managers own the utility judgment: what to build, what not to build, and how to scope it so there’s room for quality. The decision to ship something half-polished is a PM decision as much as a design one. Curation, the discipline of saying no, is a craft act.
• Designers own the coherence: patterns, consistency, emotional arc, and the holistic experience across features and surfaces. Design sets the target for how it should feel, and advocates relentlessly when the target is compromised.
• Leaders own the conditions. Time, incentives, feedback culture, and the visible prioritization of quality. If leadership only celebrates speed, that’s what the organization optimizes for. Craft requires leaders who notice the details and create the space for teams to care.

The bar

Craft isn’t perfectionism. Perfectionism is self-indulgent: it optimizes for the maker’s satisfaction. Craft is empathetic: it optimizes for the person on the other side. We’re not doing art. We’re designing for others. Every decision should be grounded in: does this make someone’s working life simpler, more pleasant, more productive?

AI will make building faster. Competition will get more competent. The floor will rise. What won’t change is what makes people love a product: the feeling that every detail was considered, that someone cared about their experience, that the product respects their time and attention.

The question we hold ourselves to isn’t “Is this done?” It’s: Would I recommend this to someone I care about?

That’s the bar. And it’s a bar we hold together, across Product, Engineering, and Design, every day, in every decision, in every detail.