Tools and Processes

Marty Cagan responds to readers who argued that any tool or process can be used well or badly, so blaming the process is misplaced, and that culture matters more than process. He agrees culture is central but argues tools and processes are never neutral: each one is designed to make some behaviors easier and others harder. Using examples like OKR software, roadmap tools that tally stakeholder requests, and Agile release cadence, he shows how these choices either reinforce or undermine values such as empowerment, transparency, and quality. The practical takeaway is that teams should look past vendor marketing and examine what a tool actually encourages or discourages.

01Key takeaways

• Treat every tool or process as a set of built-in incentives that favor some behaviors and hinder others.
• Ignore vendor marketing claims and examine what the tool actually makes easy and difficult in daily use.
• Check whether a tool's assumptions about empowerment, transparency, and results match your team's values.
• Be wary of roadmap tools that turn prioritization into tallying stakeholder requests, since this often yields weaker products.
• Recognize that process changes like release cadence affect the whole team and should be deliberately aligned with culture.
• Evaluate processes for the cultural signals they send, not just their mechanics.

02Key sections

Responding to the PMO debate

Cagan follows up on his earlier critique of SAFe and explains that this piece addresses two challenges readers raised: that tools are neutral, and that culture matters more than process.

Tools are never neutral

Every tool or method helps its intended user do certain things more easily while making other things harder, so choosing one is a value-laden decision.

OKR and roadmap tool examples

OKR software makes objectives transparent by design, while some roadmap tools push teams toward tallying requests and data-driven prioritization that Cagan believes produces poor products.

Process choices shape culture

Changes like moving from quarterly to biweekly releases affect planning, quality, and team autonomy, so they either support or work against cultural values.

Evaluating what a tool encourages

Teams should judge tools by the behaviors they actively promote or discourage rather than by vendor marketing, and check that those behaviors match their goals.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.