{
  "blyg": "0.3",
  "id": "5vt4cvsxvs6h2m5yqzk2hn4d4v",
  "kind": "fragment",
  "version": 5,
  "at": "2026-10-07T06:47:51Z",
  "note": null,
  "pinned": true,
  "origin": "https://www.msweet.net/notes/",
  "author": {
    "name": "Matthew McDowell-Sweet",
    "url": "https://www.msweet.net/"
  },
  "content_md": "**Protocol Thinking for Product People, Or How to Move Slow and Unlock Things**\n\n[Protocol thinking](https://summerofprotocols.com/the-unreasonable-sufficiency-of-protocols-web) is way more distinct from product thinking than I appreciated. Not different by degree. Not even different by kind. It’s different at the [paradigmatic](https://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system) level. In short:\n\n1. Expanding available moves over achieving specified outcomes\n2. Surrendering majority stakes in value capture and credit\n3. Higher standards and tighter reins around change governance\n4. Evolutionary search and selection over solutions engineering\n\n---\n\n**First**, traditional product thinking is [outcome-based](https://www.producttalk.org/product-discovery/). One picks a target state, evaluates [risks](https://swellandcut.com/2025/07/24/the-sixth-product-risk/), and constructs [archetypical cases](https://swellandcut.com/2023/11/08/archetypical-case-making/) to steer toward it. Success is arriving at the intended destination.\n\nProtocol thinking optimises for something else entirely: an expansion of the moves available to [players of the game](https://contraptions.venkateshrao.com/p/the-curiously-playable-universe?r=233ko&triedRedirect=true). The protocol designer *does* have near-term goals, such as interoperability, legibility, and a low cost of compliance, but beyond them, they deliberately under-determine what gets built. That restraint is the point. Every outcome specified is a move taken off the board for someone else.\n\nThis is why indexing on outcomes, or even a cluster of them, fails. The upside a good protocol unlocks isn’t just hard to predict; it’s *unnameable in advance*. Steering toward a target state, however carefully chosen, narrows the space that’s meant to be widening. The question is whether others can now do surprising things in surprising ways neither they nor we could have specified beforehand.\n\n**Second**, because protocol thinking solves for, essentially, unanticipated upside and future ecosystem optionality, one’s stance toward value capture and accumulated credit must change dramatically. Not softened. Largely relinquished.\n\nCredit requires attribution, and attribution requires a nameable outcome. The moment one starts keeping score, one is pulled back toward the outcomes one can point at, which is to say back toward product thinking.\n\nValue capture does the same damage more directly: every toll taken is a tax on the very moves the protocol was meant to make available. The aim is to expand *others’* agency, not enlarge the designer’s share.\n\nProtocol thinking in this sense asks for something product thinking never does: exercising one’s agency in setting the rules, then surrendering most claims to credit and value capture in exchange for others’ capacity to accrue them.\n\n**Third**, inbound changes must be guarded far more judiciously. In product, a feature request is a signal to weigh against a roadmap. In a protocol, a proposed change is an amendment to the rules everyone plays by, and it deserves scrutiny proportional to that, especially when it foregrounds someone’s value capture.\n\nThis isn’t at odds with expanding available moves; it’s what makes it possible. The rules have to be conservative precisely so the play can be permissive. *Move slow and unlock things*.\n\nSome open-source projects have closed themselves to outside contributions rather than drown in evaluating them. That’s one answer. The better one is explicit criteria and quality gates that make the bar legible before anything is proposed. The bar must be high because, in a protocol, the letter and the spirit have to be synonymous.\n\nProduct teams can lean on intent, norms, and a terms-of-service page. Protocols can’t. Anything the rules permit will eventually be done; anything extractable will be extracted, as [maximal extractable value](https://ethereum.org/en/developers/docs/mev/) shows with grim reliability. A change that’s harmless in spirit but exploitable in letter is simply *exploitable*. If the spirit isn’t encoded in the letter, it doesn’t exist.\n\n**Fourth**, it is more a game of evolution than engineering. Discovery-delivery loops, and even the market-level kinetics [Wardley Maps](https://www.wardleymaps.com/) describe, assume that search is expensive: one reasons one’s way to a good design because one can’t afford to try many. AI breaks that assumption.\n\nWith general intelligence on tap, generating and testing variants becomes cheap enough that search and selection outcompete design, [especially in formalised domains](https://github.com/openai/math). What survives isn’t what was best engineered, but what best satisfies global constraints, fits hyper-local [last-mile requirements](<https://en.wikipedia.org/wiki/Last_mile_(transportation)>), and suits the tastes of the particular humans doing the selecting.\n\nThe protocol’s job is to be a good substrate for that search, not to anticipate its results. It’s akin to an [immune system](https://en.wikipedia.org/wiki/Immune_system) with its valence inverted: both generate variants no one specified and let selection sort them, but one does so to eliminate the novel, the other to propagate it.\n\nIn a sense, protocol thinking is the [Bitter Lesson incarnate](https://msweet.net/notes/117-fern-terns) for product people.\n\n---\n\nA few critical questions remain in order to truly describe the nature of protocol thinking for product people. A running list for reference:\n\n- Structures and dynamics of protocol maintenance, care and cost\n- Measuring protocol success without naming outcomes in advance\n- Managing death states and navigating failure modes\n- Tensions between designing for human vs. machine play and participation\n- The enduring place and value of product thinking\n\nOngoing gratitude to the [Blygger contributors](https://blygger.org/contributors/) for inspiring the above.",
  "content_html": "<p><strong>Protocol Thinking for Product People, Or How to Move Slow and Unlock Things</strong></p>\n<p><a href=\"https://summerofprotocols.com/the-unreasonable-sufficiency-of-protocols-web\">Protocol thinking</a> is way more distinct from product thinking than I appreciated. Not different by degree. Not even different by kind. It’s different at the <a href=\"https://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system\">paradigmatic</a> level. In short:</p>\n<ol>\n<li>Expanding available moves over achieving specified outcomes</li>\n<li>Surrendering majority stakes in value capture and credit</li>\n<li>Higher standards and tighter reins around change governance</li>\n<li>Evolutionary search and selection over solutions engineering</li>\n</ol>\n<hr />\n<p><strong>First</strong>, traditional product thinking is <a href=\"https://www.producttalk.org/product-discovery/\">outcome-based</a>. One picks a target state, evaluates <a href=\"https://swellandcut.com/2025/07/24/the-sixth-product-risk/\">risks</a>, and constructs <a href=\"https://swellandcut.com/2023/11/08/archetypical-case-making/\">archetypical cases</a> to steer toward it. Success is arriving at the intended destination.</p>\n<p>Protocol thinking optimises for something else entirely: an expansion of the moves available to <a href=\"https://contraptions.venkateshrao.com/p/the-curiously-playable-universe?r=233ko&amp;triedRedirect=true\">players of the game</a>. The protocol designer <em>does</em> have near-term goals, such as interoperability, legibility, and a low cost of compliance, but beyond them, they deliberately under-determine what gets built. That restraint is the point. Every outcome specified is a move taken off the board for someone else.</p>\n<p>This is why indexing on outcomes, or even a cluster of them, fails. The upside a good protocol unlocks isn’t just hard to predict; it’s <em>unnameable in advance</em>. Steering toward a target state, however carefully chosen, narrows the space that’s meant to be widening. The question is whether others can now do surprising things in surprising ways neither they nor we could have specified beforehand.</p>\n<p><strong>Second</strong>, because protocol thinking solves for, essentially, unanticipated upside and future ecosystem optionality, one’s stance toward value capture and accumulated credit must change dramatically. Not softened. Largely relinquished.</p>\n<p>Credit requires attribution, and attribution requires a nameable outcome. The moment one starts keeping score, one is pulled back toward the outcomes one can point at, which is to say back toward product thinking.</p>\n<p>Value capture does the same damage more directly: every toll taken is a tax on the very moves the protocol was meant to make available. The aim is to expand <em>others’</em> agency, not enlarge the designer’s share.</p>\n<p>Protocol thinking in this sense asks for something product thinking never does: exercising one’s agency in setting the rules, then surrendering most claims to credit and value capture in exchange for others’ capacity to accrue them.</p>\n<p><strong>Third</strong>, inbound changes must be guarded far more judiciously. In product, a feature request is a signal to weigh against a roadmap. In a protocol, a proposed change is an amendment to the rules everyone plays by, and it deserves scrutiny proportional to that, especially when it foregrounds someone’s value capture.</p>\n<p>This isn’t at odds with expanding available moves; it’s what makes it possible. The rules have to be conservative precisely so the play can be permissive. <em>Move slow and unlock things</em>.</p>\n<p>Some open-source projects have closed themselves to outside contributions rather than drown in evaluating them. That’s one answer. The better one is explicit criteria and quality gates that make the bar legible before anything is proposed. The bar must be high because, in a protocol, the letter and the spirit have to be synonymous.</p>\n<p>Product teams can lean on intent, norms, and a terms-of-service page. Protocols can’t. Anything the rules permit will eventually be done; anything extractable will be extracted, as <a href=\"https://ethereum.org/en/developers/docs/mev/\">maximal extractable value</a> shows with grim reliability. A change that’s harmless in spirit but exploitable in letter is simply <em>exploitable</em>. If the spirit isn’t encoded in the letter, it doesn’t exist.</p>\n<p><strong>Fourth</strong>, it is more a game of evolution than engineering. Discovery-delivery loops, and even the market-level kinetics <a href=\"https://www.wardleymaps.com/\">Wardley Maps</a> describe, assume that search is expensive: one reasons one’s way to a good design because one can’t afford to try many. AI breaks that assumption.</p>\n<p>With general intelligence on tap, generating and testing variants becomes cheap enough that search and selection outcompete design, <a href=\"https://github.com/openai/math\">especially in formalised domains</a>. What survives isn’t what was best engineered, but what best satisfies global constraints, fits hyper-local <a href=\"https://en.wikipedia.org/wiki/Last_mile_(transportation)\">last-mile requirements</a>, and suits the tastes of the particular humans doing the selecting.</p>\n<p>The protocol’s job is to be a good substrate for that search, not to anticipate its results. It’s akin to an <a href=\"https://en.wikipedia.org/wiki/Immune_system\">immune system</a> with its valence inverted: both generate variants no one specified and let selection sort them, but one does so to eliminate the novel, the other to propagate it.</p>\n<p>In a sense, protocol thinking is the <a href=\"https://msweet.net/notes/117-fern-terns\">Bitter Lesson incarnate</a> for product people.</p>\n<hr />\n<p>A few critical questions remain in order to truly describe the nature of protocol thinking for product people. A running list for reference:</p>\n<ul>\n<li>Structures and dynamics of protocol maintenance, care and cost</li>\n<li>Measuring protocol success without naming outcomes in advance</li>\n<li>Managing death states and navigating failure modes</li>\n<li>Tensions between designing for human vs. machine play and participation</li>\n<li>The enduring place and value of product thinking</li>\n</ul>\n<p>Ongoing gratitude to the <a href=\"https://blygger.org/contributors/\">Blygger contributors</a> for inspiring the above.</p>",
  "content_hash": "sha256:725bbff6ece6e13dda112013ccbd357adbe2fa632de5d66563c8066d275d8d03"
}
