[product1087]

> Product teams painstakingly craft their product specs to ensure they're building the right thing. Unfortunately, the pace of modern product development is so fast that the minute a product spec is written, it’s no longer relevant.

I think the missing insight is that while the final outcome is no longer relevant, the process of reaching the outcome is critical! When I am trying to understand a feature, I find myself spending most my time in the version history of Google Docs (something that team has treated as a secondary feature) – learning how the feature team's collective understanding has evolved. I think Decisions in Fable is a step closer, but not far enough.

One thing I would love to see is product spec editing / collaboration focused around version history. The real "work" of building product specs is building shared context between PM, Eng, UX through evolution of the requirements. However unlike devs who can see the diff of a code file, PM rarely "show their work" – and it makes it hard for everyone to see how the final requirements were reached. I still haven't seen any PM tool with this paradigm in mind.

[addorai]

This is a great point. It's particularly useful to have that context into how the thinking evolved when you're looking back at a feature built months or years ago, to help you avoid doing something that was skipped in good reason OR make the same mistakes again.

We agree our decision feed is just step one to get there, we're also exploring other ways to show the evolution of work.