Skip to content
Accelerate ship velocity & quality by streamlining your end-to-end product design & development process.Increase stakeholder alignment through tighter feedback loops and visibility by deepening cross functional collaboration and engagement, thus better product-market-fit and value to users.Consolidate your product tech stack: you shouldn’t be using a different tool for OKRs & planning, requirement/technical documentation, decisions, wiki, meetings, product team hubs, initiative / roadmaps, and launch checklists. Product teams commonly replace Airtable, Notion, and Confluence, opportunistically reduce licenses with project mgmt. tools like Asana and Smartsheet, and deeply with the rest of their stack, namely ticketing ( 
Loom or some sort of visual.
ProductOS
- Pages
Share
Explore
ProductOS homepage
A Product Design & Development Operating System, or ProductOS for short, is how companies learn from the market and ship delightful products that create value for their customers. While the PDE org (Product, Design, Engineering) chiefly owns this operation, the best product-led companies like ,
, and
deeply integrate key cross-functional stakeholders and business systems like sales and marketing in the process. What you can expect from rolling out a ProductOS:
) , design ( ), chat ( ), code ( ), and customers ( ). FAQs
Q: How do we define Tiers 1-4, and what is the process for assigning tiers?
A: At a high level, new products are assigned a tier ranging from 1 (highest GTM impact) to 4 (lowest GTM impact). Detailed tier definitions are captured in the tab here. Tiers for all bets should be determined and documented in the PD Bets Tracker at the start of a quarter, as part of the quarterly check-in process. See more:
Q: What is the difference between a release and a launch?
A: A release is confined to a specific product functionality that is being released to market, whereas a launch is an external-facing marketing moment (owned by PMM) that is integrated with ongoing campaigns and can either capture a single high-impact release, or bundle together multiple lower-tier releases.
-Each Tier 1 release always has a launch associated.
-Tier 2+ releases may or may not be captured within a launch.
Q: What if a deliverable doesn't apply to my release?
A: The templates are intended to be guidelines, not strict rules! Please delete any deliverables and/or exit criteria that do not apply to your release, in particular for Tier 2-4 releases.
Q: Should my release be blocked if I have not met an exit criterion?
A: For Tier 1 releases, exit criteria in the EXIT CRITERIA / RITUALS (Tier 1-2) are blockers. Our priority is to always move fast but to do so in alignment with GTM to maximize impact. For Tier 2+ releases, Exit Criteria & Rituals are recommended but should not block a release.
Q: Does "new product" always mean a brand new product (ex: CDP), or can it be a feature release?
A: "New product" refers to all new functionalities that we are bringing to market. This can constitute a brand new product (ex: CDP), or more incremental improvements & feature releases. Different sizes of releases are captured via the tier definitions.
Note that this template represents a guideline for how to introduce new products. Each release is unique and may have specific requirements not captured by this template. We recommend that users apply a layer of judgement on top of the template to guide an end-to-end release strategy.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.