Amazon Doc vs. Microsoft Spec Review
As a PM, I’m noticing Microsoft spec reviews are wildly different than Amazon doc reviews. (Was previously an L6 PM at amazon, now an L65 PM at MS.) By amazon doc reviews, I’m specifically thinking about 1 or 6 pager strategy docs that PMs write. Amazon PM Doc reviews are focused on: - finding the right metrics, KPIs, data to set goals - leadership as an audience (smaller doc reviews might take place with ICs as doc is drafted) - business strategy -priorities determined using a prioritization model (like RICE) MS PM spec reviews are focused on: - finding the right UX (sometimes tactical UI conversations) based on IC opinions on the call (rarely making data-driven decisions) - L65 and below as an audience - tactical implementation (v.s. business strategy) - priorities determined by who is the loudest or con census on call Curious to know from other PMs who’ve been at MS and amazon if this was their experience too
I think you nailed it. From my experience, the Msft spec is an engineering focused doc for the team. More about what. A touch on why. Trying to leave the hope to the devs. The UI focus may be the specifics of your team and could be if you don’t have access to designers.