What great PMs do: traits, AI strategy, and Slack's product process

Executive overview

Most product managers focus on shipping features, but the real job is facilitating decisions, amplifying teams, and driving impact. Noah Weiss, CPO at Slack, distills 15 years across Google, Foursquare, and Slack into a clear model for PM excellence and product development at scale.

Slack's edge comes from treating product as a creative discipline — with principles, rituals, and structured learning replacing intuition and heroics.

The best PMs don't make decisions — they make it easy for teams to make high-quality decisions fast.

The 10 traits of great product managers

1. Live in the future and work backwards — carve out time for a 6–24 month horizon, not just the next sprint
2. Amplify the team — facilitate ideas, create energy, be a multiplier not a dictator
3. Execute impeccably — create the aura of "I've got this"; nothing drops
4. Focus on impact — to customers first, then the business; impact solves all PM problems
5. Facilitate the pace and quality of decision-making — not playing tiebreaker, but keeping the org unblocked
6. Optimise for the pace of learning — willing to sacrifice short-term impact for new levers
7. Write well — the only scalable influence as scope grows
8. Be data-fluent — quantitative, survey, and customer research all count; not just statistics
9. Have product taste — develop intuition for what people will love before you can test it
10. Know your North Star — understand which metrics actually predict long-term success

Working with product-minded founders

• Align on principles first — shared language for what great product looks like, so reviews don't feel like Goldilocks
• The founder owns the vision; teams own creative execution within that vision
• Involve the founder on a U-curve: heavy at the start (strategic buy-in, goals, anti-goals), light in the middle, heavy again at the end (taste-test before launch)
• At the final stage, do a live bug bash together — engineers, design, product, founder in one room — rather than a confrontational sign-off
• Refinement in code beats refinement in static mocks every time

Complaint storms and customer love sprints

• Complaint storms: team reviews a competitor's product end-to-end, cataloguing every confusion and friction point — then turns that critical eye on their own product
• Starting with someone else's software lowers defences and calibrates quality benchmarks
• Similar to Stripe's "friction logging" but with the warm-up step of an adjacent product first
• Customer love sprints: two-week hackathon-style sprints to ship a backlog of low-effort, high-impact polish items — at least quarterly for user-facing teams
• Roadmap is a portfolio: new capabilities vs. incremental improvement, risky bets vs. known bets, impact vs. learning

Rebuilding Slack's self-service growth (2019)

• Self-service plateaued after the enterprise push; the next-generation customer had different needs
• Threw out the existing roadmap; spent six months purely optimising for learning, not impact
• Key insight: comprehension and desirability — new users didn't understand what Slack was for or why it was worth the change cost
• Introduced a trial strategy for the paid product (previously only free or paid, no tasting)
• Defined a new North Star metric: successful teams — 5 people using Slack most of the workweek; this cohort upgraded at 4× the rate within 6 months
• Rallied all product teams around that early-funnel metric, not just the self-service team
• Result: doubled the rate of new paid customer growth over the following years

AI strategy at Slack and lessons from 15 years

• Google Knowledge Graph work (2008) established the core principle: the UI's promise must match the quality of the underlying data — a principle LLMs still violate through confident hallucination
• Build virtuous cycles where training data is a natural byproduct of product usage (e.g. Netflix ratings)
• AI team structure: central ML/search infrastructure shared across several small, parallel prototype teams — not one monolithic AI team
• Long-term: AI capabilities become part of every product team's roadmap, like mobile is today
• North Star vision: Slack as a personal chief of staff who summarises everything you care about — not achievable yet, but worth heading toward

How Slack enables zero-to-one bets

• Cultural principle: take bigger, bolder bets — avoid crawling up the hill without seeing the mountain range behind it
• Spin up new, dedicated teams before an area matures (huddles and clips in early pandemic; AI now)
• Give incubation teams a "jail-free card" from normal quarterly planning — measure by pace of learning, not output
• Path: prototype → pilot → launch; don't ship until it blows people away

Slack's product development principles

• Be a great host — relentlessly save users' steps; foresight over features
• Don't make me think — design for people from many backgrounds; don't reinvent patterns
• More clicks can be fine — clarity and trust matter more than minimising taps in non-transactional software

Scaling product development

• Pilot program: thousands of pre-signed customers across industries, sizes, and geographies; roll out net new features to whole teams (required for multiplayer products like huddles)
• Feedback via Slack Connect threads, surveys, and usage data before broad launch
• Usability sessions with live threads: PMs, engineers, designers react in real time in a Slack thread — the thread becomes the research report
• Customer experience (CX) team pipeline: front-line support insights flow directly to product teams

Career advice by seniority

Early-career focus:

• Impeccable execution — creates the "I've got this" aura that earns more responsibility
• Build a nose for impact — demonstrate momentum and credibility
• Data and research fluency — bring insights to the team

Senior PM / director focus:

• Quality of decision-making at scale — unblock teams of teams, not just one team
• Living in the future — own the longer-term strategy that realises the founder's vision
• Writing — highest-leverage use of time to influence product direction across a large org

Book recommendations

• The Innovator's Dilemma and The Innovator's Solution — Clayton Christensen; best books on product strategy
• Radical Candor — Kim Scott; essential for leadership and influence
• Leadership in Turbulent Times — Doris Kearns Goodwin; leadership under crisis, drawn from presidential history
• Creative Selection — Ken Kocienda; iterative creative work at Apple; best book on product taste
• On Writing — Stephen King; high-volume, high-quality production writing