Your guide to bringing the Product Operating Model to life
What problem are we trying to solve? Many companies today are attempting to shift toward what Marty Cagan has labeled the Product Operating Model (POM). In his excellent book Transformed, co-authored with Chris Jones, Cagan synthesizes patterns observed in high-performing digital product companies.
A key challenge product leaders face is figuring out how to operationalize the product operating model in their unique context. There is broad consensus that this is not a tools or process problem—so when we say "operationalize," we are not referring to process gates or software implementations. Instead, we're talking about the central design challenge: defining the rituals, artifacts, frameworks (explicit and implicit), guidelines, language, and behaviors that support the transition to the product operating model.
At Dotwork, we refer to this collection of elements as a Product Operating System—the unique set of design decisions that bring the POM to life within a given context.
The Dotwork POM Starter Pack is intended to provide companies with something they can start using right away—or use as inspiration for tailoring their own version. Product operating systems are deeply contextual. There is essentially a 0% chance you'll want to adopt this as-is. But if you're looking for a scaffold to get things moving—with an expiration date and an agreement to revisit and adapt it—we've got your back.
Who are we trying to help? You're a product leader or product operations leader who has been tasked with "moving to the product operating model." You're aware of the many hurdles—skills gaps, organizational inertia, politics, environmental constraints. You want to design an operating system that fosters the right behaviors and interactions, and nudges your team in the right direction.