Protocol Thinking for Product People, Or How to Move Slow and Unlock Things
Protocol thinking 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 level. In short, it means:
- Expanding available moves over achieving specified outcomes
- Surrendering majority stakes in value capture and credit
- Higher standards and tighter reins around change governance
- Evolutionary search and selection over solutions engineering
- Care given via individual stewardship and collective goodwill, not exchange
- Measuring what’s given away to the wider world, not what’s captured
First, traditional product thinking is outcome-based. One picks a target state, evaluates risks, and constructs archetypical cases to steer toward it. Success is arriving at the intended destination.
Protocol thinking optimises for something else entirely: an expansion of the moves available to players of the game. 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.
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 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.
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.
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.
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 others’ agency, not enlarge the designer’s share.
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.
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.
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. Move slow and unlock things.
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.
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 maximal extractable value 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.
Fourth, it is more a game of evolution than engineering. Discovery-delivery loops, and even the market-level kinetics Wardley Maps 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.
With general intelligence on tap, generating and testing variants becomes cheap enough that search and selection outcompete design, especially in formalised domains. What survives isn’t what was best engineered, but what best satisfies global constraints, fits hyper-local last-mile requirements, and suits the tastes of the particular humans doing the selecting.
The protocol’s job is to be a good substrate for that search, not to anticipate its results. It’s akin to an 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.
In a sense, protocol thinking is the Bitter Lesson incarnate for product people.
Fifth, because of points one to four, protocols don’t fit the constraints of market logic. Transactional exchange, the canonical quid pro quo, powers projects, platforms, products and services, but not protocols. Every funding mechanism one reaches for asks for something a protocol can’t give without ceasing to be one.
- State funding needs outcomes it can justify to voters
- Standards bodies answer to members who eventually steer toward their own capture
- Community groups have the spirit but not the means, so care becomes unpaid heroics
- Academia runs on attribution, not on maintaining systems
- Venture capital needs an order-of-magnitude exit multiple and a capturable share
- Crypto builds value capture into the rules themselves, which turns governance into a contest over the spoils
None of these work. That’s because each is a form of exchange, and protocols belong to a different paradigm: the gift.
Exchange settles accounts so both parties can walk away. A gift keeps moving and creates a loose, unenforceable obligation to pass something on. A protocol gives moves away and asks only that players keep the game going—ideally acting to make the game more interesting for others.
Gift economies are good at circulation but bad at upkeep. Nobody owes the giver anything, so nobody is on the hook for the roof. Protocol maintenance today rests on collective goodwill and on individuals who take up a role as benevolent dictators for a bounded period, carrying the cost of care and prophetic cognition for a while before handing it on.
The bound matters, because without it such stewardship hardens into ownership. Neither collective goodwill nor individual stewardship is really a funding model—at least not in the sense of capital compensating labour for technological development. How protocols pay for their own care, sadly, remains unsolved.
Sixth, in product thinking, most things one cares to measure are proxies for what the market legitimises as value. CAC, LTV, retention, conversion: each stands in for the same question. Namely: how much of the value generated does the generator get to keep?
Protocols, as established in point five, sit outside market logic. Their metrics can’t be proxies for capture, because capture is the very thing they forgo. Yet they still need something to be proxies for.
That something is value generated but not captured. It’s what a protocol is for, and it’s almost impossible to measure directly. No transaction happens. No one invoices. Nobody is counting. That’s the point. So, as with CAC and LTV, one does need proxies. Four will do:
- Different people: the game is played by many players and owned by none
- Different implementations: the spec, not a codebase, holds things together
- Different uses: the play has spread to surprises beyond original intent
- Durability: all three persist over time, by choice, because exit is easy
Any one of these is cheap to fake. All four at once, sustained, is not.
- Fake adopters share an implementation
- Fake implementations serve a single use
- Fake uses come from the same few hands
- Durability turns every fake into a running cost with no market return
They’re a set, not a menu. Game them for long enough and the four dimensions become indistinguishable from the real thing: a successful, sustainable protocol.
There are two things they deliberately don’t do, though. They don’t judge whether the play is good; that’s what the rules are for, per point three. And they don’t forecast. The four dimensions are organic, real-time signals, not targets one steers toward, because selection does the steering, per point four. The moment they become targets, for funders or anyone else, the paradigm of exchange dominates again and we bow out of protocol land.
Assuming the market can’t be the measure for a protocol, perhaps the M in TAM, SAM and SOM can stand for something else? Meaning added to the universe.
A few critical questions remain in order to truly describe the nature of protocol thinking for product people. A running list for reference:
- Managing death states and navigating failure modes
- Tensions between designing for human vs. machine play and participation
- The enduring place and value of product thinking
- The most appropriate metaphors for protocol thinking
- Protocol thinking is also not process thinking
Ongoing gratitude to the Blygger contributors for inspiring the above.