The PRD Was Already Dead. Slack Proved It in Public.

I have been saying the PRD collapsed into three artifacts: a one-page brief, a working prototype, and a colocated eval. Slack is now running the org-chart version of that argument.

The short version

The PRD was already dead, and Slack proved it in public. Instead of quarterly roadmap commitments, Slack is reportedly running small cross-functional squads, sometimes one designer and one engineer, that prototype continuously and let evidence decide direction rather than a plan decide it in advance. This is not a scrappy startup habit; it is a company with the resources to run traditional planning choosing not to. At scale the fixed roadmap is the thing that breaks, because commitments made months out are made on stale information, and AI makes information decay faster than a quarterly cycle can track. What replaces the roadmap is not chaos but a different discipline: a shared brief and a shared definition of a good outcome, with the destination allowed to change as the prototype teaches you what you are actually building.

Instead of quarterly roadmap commitments, Slack is reportedly running small cross-functional squads, sometimes a single designer and a single engineer, that prototype continuously and let evidence decide direction rather than a plan decide it in advance. This is not a scrappy startup habit. This is a company with the resources to run a traditional planning process choosing not to.

The reason this matters is that most product leaders still treat prototype-first as something only small, informal teams can afford. Big companies need process, the thinking goes, because they need predictability and cross-team coordination. Slack's structure argues the opposite: at scale, the fixed roadmap is the thing that breaks, because commitments made months in advance are commitments made on stale information, and AI has made information go stale faster than a quarterly cycle can track. This is continuous discovery applied to the org chart, not just the research calendar.

What replaces the roadmap is not chaos, it is a different kind of discipline. Tiny squads still need a brief. They still need a shared definition of what a good outcome looks like. What they drop is the fiction that you can specify the destination accurately before you start moving. The brief tells you why you are building, the prototype tells you what you are actually building, and the two are allowed to diverge. That is exactly the split I described when the PRD collapsed into a brief, a prototype, and an eval, and the reason the prototype is now the spec.

If you are still running your org on a roadmap deck that gets presented once a quarter and defended in every meeting after, the uncomfortable question is not whether AI changes your job. It is whether the artifact you have built your entire planning process around was ever the right artifact, and whether you kept it because it worked or because it was legible to people above you.