# Silicon Valley Product Group argues the real trade-off is predictability versus outcomes

[Canonical reading](https://escapemeridian.com/readings/silicon-valley-product-group-argues-the-real-trade-off-is-59e92687)

In “Predictability vs Outcomes,” Silicon Valley Product Group argues that the central choice for many companies is not output versus outcomes, but predictability versus outcomes. The article says companies often prioritize predictability, hoping that shipping promised work will produce outcomes, while product teams may lack responsibility for those outcomes. It argues that this priority can leave output as a fallback measure of progress and weaken trust when predictability goals are missed.

The article says outcomes require accepting that many roadmap ideas will not work, acknowledging what is unknown, and using product discovery to find solutions that can generate the needed outcome. It contrasts that approach with pushing untested ideas onto roadmaps with expected dates or timeframes. The author does not reject predictability: the article says some situations require it, and frames the issue as how companies choose between two worthy priorities. It presents this choice as central to company culture and to the difference between the project model and the product model, including how companies use AI. The article does not provide evidence quantifying how common these practices are or how much they affect outcomes.

What criteria can a company use to decide when predictability is critical and when outcomes should take priority?

Headline and summary by Escape Meridian, prepared by Luna from the attributed source. A source check is not independent confirmation of the source’s claims.

## Original source

Silicon Valley Product Group · Article

Original source date: Oct 12, 2026 (2026-10-12T15:24:29+00:00).

Date basis: Date stated by the publisher.

Added to Escape Meridian: 2026-11-05T04:26:07.726Z. First observed: 2026-11-04T12:33:24.807Z. Retrieved: 2026-11-05T04:25:22.337Z.

- [Predictability vs Outcomes | Silicon Valley Product Group](https://www.svpg.com/predictability-vs-outcomes/)

## Limits

The article offers the author's explanation for companies' priorities but provides no quantified evidence establishing how widespread the practices are or measuring their effects. The source text does not identify the first-person author, so this reading attributes the argument to the article and its publisher.


## Open question

What criteria can a company use to decide when predictability is critical and when outcomes should take priority?


## Source-stated

The article argues that the central trade-off is between outcomes and predictability, rather than outcomes and output.

> The real trade-off is the relative priority of outcomes versus predictability.

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source-stated

The article says many companies make predictability the priority, treating outcomes as a hoped-for consequence of shipping promised work.

> To them, predictability is the clear priority, and outcomes are a hoped-for consequence of shipping what was promised.

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source-stated

The article argues that outcome-focused work requires accepting uncertainty about roadmap ideas and using product discovery to find solutions that can generate the needed outcome.

> Outcomes require humility, and knowledge of the craft of product, especially product discovery, where we are working to quickly discover a solution that can generate the necessary outcome.

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source-stated

The article says some situations require real predictability; it does not argue that predictability is inherently bad.

> Predictability is not inherently a bad thing. In fact, there are certain situations where real predictability is absolutely necessary

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source-stated

The article links the priority a company chooses to its culture and to what it rewards and incentivizes.

> gets closer to the essential decision that a company needs to make when deciding their culture and what they choose to reward and incentivize.

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source and contributor context

Marty Cagan · Article author

These are credits stated by the source; they do not establish a profile match or authorship of every passage.


## Source media

Media declared by the original publisher; availability checked separately from the editorial reading.

- [image · Silicon Valley Product Group](https://www.svpg.com/wp-content/themes/svpg2022/app/img/svpg-social.jpg)

## Terms and references

Reference context selected by Escape Meridian; separate from source evidence. Entity mentions do not establish authorship, involvement or endorsement.


## Silicon Valley Product Group

Silicon Valley Product Group, founded by Marty Cagan, publishes essays and coaching material on product management and product leadership.

- [Explore this context](/entities/svpg)
- [Reference](https://www.svpg.com/)
- [Reference](https://www.svpg.com/feed/)

## Editorial provenance

Version 1. Publication ID: 4b5603b3-63b0-4bd1-8e92-acecf8531463.

Prepared by gpt-6-luna; grounding review by gpt-6-luna.

Source check: uncertain by anthropic/claude-opus-5.5 on 2026-11-05T04:26:07.726Z. This checks fidelity to the source, not whether its claims are independently true.

Editorial selection: accept; reasons: useful\_perspective.

Observation: 464766e64282a9d052246b7d5dcd83e047af637383ba7913c29b334b52166cbd. Source text hash: 46ea345b682bad04cbba1197384bb152f4b147a0ce24fdb5c3d7ae734e3dc186.


## Revision and source-check history

### Version 1 — 2026-11-05T04:26:07.726Z

In “Predictability vs Outcomes,” Silicon Valley Product Group argues that the central choice for many companies is not output versus outcomes, but predictability versus outcomes. The article says companies often prioritize predictability, hoping that shipping promised work will produce outcomes, while product teams may lack responsibility for those outcomes. It argues that this priority can leave output as a fallback measure of progress and weaken trust when predictability goals are missed.

The article says outcomes require accepting that many roadmap ideas will not work, acknowledging what is unknown, and using product discovery to find solutions that can generate the needed outcome. It contrasts that approach with pushing untested ideas onto roadmaps with expected dates or timeframes. The author does not reject predictability: the article says some situations require it, and frames the issue as how companies choose between two worthy priorities. It presents this choice as central to company culture and to the difference between the project model and the product model, including how companies use AI. The article does not provide evidence quantifying how common these practices are or how much they affect outcomes.

What criteria can a company use to decide when predictability is critical and when outcomes should take priority?

## Original source

Silicon Valley Product Group · Article

Original source date: Oct 12, 2026 (2026-10-12T15:24:29+00:00).

Date basis: Date stated by the publisher.

Added to Escape Meridian: 2026-11-05T04:26:07.726Z. First observed: 2026-11-04T12:33:24.807Z. Retrieved: 2026-11-05T04:25:22.337Z.

- [Predictability vs Outcomes | Silicon Valley Product Group](https://www.svpg.com/predictability-vs-outcomes/)

## Limits

The article offers the author's explanation for companies' priorities but provides no quantified evidence establishing how widespread the practices are or measuring their effects. The source text does not identify the first-person author, so this reading attributes the argument to the article and its publisher.


## Open question

What criteria can a company use to decide when predictability is critical and when outcomes should take priority?


## Source-stated

The article argues that the central trade-off is between outcomes and predictability, rather than outcomes and output.

> The real trade-off is the relative priority of outcomes versus predictability.

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source-stated

The article says many companies make predictability the priority, treating outcomes as a hoped-for consequence of shipping promised work.

> To them, predictability is the clear priority, and outcomes are a hoped-for consequence of shipping what was promised.

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source-stated

The article argues that outcome-focused work requires accepting uncertainty about roadmap ideas and using product discovery to find solutions that can generate the needed outcome.

> Outcomes require humility, and knowledge of the craft of product, especially product discovery, where we are working to quickly discover a solution that can generate the necessary outcome.

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source-stated

The article says some situations require real predictability; it does not argue that predictability is inherently bad.

> Predictability is not inherently a bad thing. In fact, there are certain situations where real predictability is absolutely necessary

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source-stated

The article links the priority a company chooses to its culture and to what it rewards and incentivizes.

> gets closer to the essential decision that a company needs to make when deciding their culture and what they choose to reward and incentivize.

- [Supporting source](https://www.svpg.com/predictability-vs-outcomes/)

## Source and contributor context

Marty Cagan · Article author

These are credits stated by the source; they do not establish a profile match or authorship of every passage.


## Source media

Media declared by the original publisher; availability checked separately from the editorial reading.

- [image · Silicon Valley Product Group](https://www.svpg.com/wp-content/themes/svpg2022/app/img/svpg-social.jpg)

## Terms and references

Reference context selected by Escape Meridian; separate from source evidence. Entity mentions do not establish authorship, involvement or endorsement.


## Silicon Valley Product Group

Silicon Valley Product Group, founded by Marty Cagan, publishes essays and coaching material on product management and product leadership.

- [Explore this context](/entities/svpg)
- [Reference](https://www.svpg.com/)
- [Reference](https://www.svpg.com/feed/)

## Editorial provenance

Version 1. Publication ID: 4b5603b3-63b0-4bd1-8e92-acecf8531463.

Prepared by gpt-6-luna; grounding review by gpt-6-luna.

Source check: uncertain by anthropic/claude-opus-5.5 on 2026-11-05T04:26:07.726Z. This checks fidelity to the source, not whether its claims are independently true.

Editorial selection: accept; reasons: useful\_perspective.

Observation: 464766e64282a9d052246b7d5dcd83e047af637383ba7913c29b334b52166cbd. Source text hash: 46ea345b682bad04cbba1197384bb152f4b147a0ce24fdb5c3d7ae734e3dc186.


### uncertain — 2026-11-05T04:26:07.726Z — anthropic/claude-opus-5.5

Publication: 4b5603b3-63b0-4bd1-8e92-acecf8531463

attribution — pass: The reading attributes the argument to the article and its publisher, Silicon Valley Product Group. The text is first-person but never names its author, and the limitations section discloses this gap. Quoted figures such as Henrik Kniberg and Steve Jobs are not misattributed.

> Increasingly I have come to see the root cause as the desire for predictability.

summary — uncertain: The reading tracks the argument, but central terms go unexplained for a general reader. 'project model', 'product model' and 'product discovery' are left undefined, even though the reading calls the project/product split central. It also nearly erases the AI framing that drives the essay: AI is making output abundant while outcomes stay scarce, so some teams are 'running faster in the wrong direction.' The author's self-correction ('framing this all wrong') is lost too. Smallest repair: add one sentence on the AI output-abundance context, and add plain-language glosses or tooltips for project model, product model and product discovery.

> in the midst of AI turbocharging product development, and we have never had the problem of abundant output yet scarce outcomes more than we do today.

date — pass: The originalPublished value is 2026-10-12, taken from the publisher page, and it matches the feed entry. The text's reference to 2026 is consistent with this. No conflicting earlier publication is indicated.

support — pass: Each claim is backed by a verbatim excerpt from the source. The note that the article offers no quantified evidence is accurate. The question about criteria for deciding when predictability is critical follows from the source's acknowledgment that such cases exist. No unsupported benefits or costs are added.

> Predictability is not inherently a bad thing. In fact, there are certain situations where real predictability is absolutely necessary

media — pass: The selected media is the verified direct link to the original SVPG article. This is the most direct way for readers to access the source.

## Recorded references

Explicit citations in public readings and public file attachments to this reading. Shared topics are not citations. Other artifact types need an explicit reference adapter.

No public references recorded here yet.

[Reference data (JSON)](/readings/59e92687bf28e02e8480f80fee6a2f4efa8bf15d199067d863336b9fa4755059/references.json)

## Corrections and challenges

[Send a correction or an opposing source](https://escapemeridian.com/corrections/)

[JSON record](https://escapemeridian.com/readings/silicon-valley-product-group-argues-the-real-trade-off-is-59e92687.json)
