The Moore Memorandum — Briefing #009
Standards as Power
The architecture of markets, platforms, and adoption
Executive Summary
Standards set the terms under which products connect, buyers evaluate, regulators recognize, platforms admit, and ecosystems invest.
A standard allocates power through five levers: interface control, certification control, installed-base control, intellectual-property control, and timing control.
Standards can enlarge a market by reducing incompatibility, uncertainty, and buyer risk. They can also concentrate advantage by defining who qualifies, who certifies, who pays, whose architecture becomes ordinary, and whose intellectual property becomes difficult to avoid.
The executive error is late discovery. A company reaches commercialization and then learns that the market has already chosen a protocol, certification path, procurement language, safety test, data format, platform rule, or licensing regime.
Standards strategy belongs before product freeze, procurement entry, platform dependence, and regulated launch.
The executive question is direct:
Which standard governs the market we intend to enter, and what power does it allocate?
1. The Pattern
Most companies encounter standards after the commercial thesis is already formed.
The product works.
The prototype performs.
The sales team has prospects.
The customer expresses interest.
The launch plan is underway.
Then the market asks a different set of questions.
Can the product certify?
Will procurement accept it?
Does the platform permit it?
Is the interface compatible?
Does the buyer require a recognized standard?
Does the regulator incorporate a technical standard by reference?
Does a competitor control essential intellectual property?
Does the customer’s system already operate around another schema, protocol, safety rule, or evidence format?
At that point, standards work becomes remediation: redesign, license, test, certify, delay, narrow the market, revise claims, or accept dependency.
The stronger posture begins earlier:
Which rules of interoperability, certification, safety, evidence, terminology, performance, security, data exchange, and governance will define this market before our product reaches it?
Standards are often quiet during strategy formation. Their effects become visible at market entry.
2. Why Standards Carry Power
Standards carry power because they determine what counts as compatible, acceptable, measurable, safe, certifiable, or compliant.
A. Standards define interfaces
A standard may determine how devices connect, how software exchanges data, how systems authenticate, how measurements are calculated, how components fit, or how evidence is reported.
The interface then becomes a strategic location. Firms that conform can participate more easily. Firms built around a different architecture face adaptation cost, licensing cost, certification cost, or customer resistance.
B. Standards reduce buyer uncertainty
Buyers prefer legible risk. A recognized standard turns a difficult technical judgment into a structured compliance judgment.
This matters in enterprise procurement, healthcare, energy, cybersecurity, manufacturing, infrastructure, financial services, defense, education, and other markets where the buyer must justify adoption to another authority.
The WTO’s Technical Barriers to Trade framework reflects this commercial reality at the trade level: it addresses technical regulations, standards, and conformity assessment procedures, and encourages international standards as a way to facilitate trade while preserving legitimate objectives such as health, safety, and environmental protection.
C. Standards coordinate complementary investment
A standard tells complementors where to invest.
Hardware vendors, software developers, certifiers, laboratories, systems integrators, distributors, purchasers, and regulators can organize around a common rule. Network-effects scholarship explains why compatibility matters: the value of a networked product often depends on the number of compatible users, products, or complements around it.
D. Standards create gates
The gate may be formal: certification, accreditation, regulator recognition, platform approval, procurement qualification, conformity assessment.
The gate may be commercial: customers decline to buy products that do not follow the familiar standard.
ANSI’s American National Standards process illustrates the governance function: ANSI describes American National Standards as voluntary consensus standards developed through due-process requirements intended to ensure openness, balance, consensus, and responsiveness to directly and materially interested parties.
E. Standards allocate future bargaining power
A standard can embed a data schema, testing procedure, reference implementation, certification body, interface protocol, security model, or patented technology.
Once the market builds around those elements, bargaining power changes. The standard becomes part of the industry’s economic structure.
3. The Standards Power Map
| Lever | What It Controls | Strategic Question |
|---|---|---|
| Interface control | how systems connect and exchange value | Whose architecture becomes the default? |
| Certification control | who can prove compliance and at what cost | Who controls market access? |
| Installed-base control | which existing users, assets, and complements matter | Who benefits from inertia? |
| IP control | which patents, know-how, licenses, or pools are required | Who gets paid when the market complies? |
| Timing control | when the market coordinates around a rule | Are we shaping the rule or adapting after it hardens? |
This table should appear in every product, platform, regulated-market, and ecosystem review where standards govern adoption.
4. Interface Control
Interface control is the most direct form of standards power.
The firm that shapes an interface shapes the path of adoption. It can make complements easier or harder. It can lower switching costs or increase them. It can expand participation or narrow it. It can commoditize adjacent layers or preserve a proprietary layer.
This is why platform firms care deeply about APIs, authentication standards, data schemas, plugin architectures, model formats, device protocols, payment rails, app-store rules, and interoperability requirements.
An interface standard can create a broader market. It can also move margin toward the layer that defines the interface.
Board question: Are we building on another party’s interface, shaping the interface, or becoming dependent on an interface we cannot influence?
5. Certification Control
Certification converts a standard into a market-access pathway.
A product may work technically while still failing commercially because a buyer, regulator, insurer, hospital, platform, utility, or procurement office requires proof through testing, audit, accreditation, conformity assessment, or certification.
NIST’s Standards.gov frames this field broadly: the NIST Standards Coordination Office advances technical standards, conformity assessment, laboratory accreditation, and quality management systems to promote U.S. innovation and international trade.
For executives, the implication is practical:
Certification often functions as the commercial route into a market.
The company that cannot certify may lose access to buyers whose risk systems require certification, even when the product is technically strong.
Certification review should ask:
| Question | Why It Matters |
|---|---|
| What standard must be met? | defines the evidence target |
| Who tests or certifies? | defines gatekeeper power |
| What does certification cost? | affects margin and launch timing |
| How long does certification take? | affects runway and market entry |
| What happens after failure? | defines redesign and retest exposure |
| Does certification renew? | creates ongoing obligation |
| Does procurement require it? | determines buyer access |
6. Installed-Base Control
Standards interact with installed bases.
A legacy installed base can protect an incumbent because customers, suppliers, integrators, and users already operate around that standard. A new standard can weaken an incumbent by shifting compatibility to a new interface. A transition standard can preserve incumbents while allowing limited entry.
Standards disputes often appear technical. Adoption behavior usually reflects installed-base economics.
The critical questions:
| Question | Strategic Meaning |
|---|---|
| Which installed base does the standard preserve? | incumbent protection |
| Which installed base does it strand? | displacement potential |
| Which complements become more valuable? | ecosystem shift |
| Which switching costs fall? | entrant opportunity |
| Which switching costs rise? | lock-in risk |
| Which buyer has authority to force transition? | adoption pathway |
A company can win the technical argument and lose the adoption race if it misreads installed-base power.
7. Intellectual-Property Control
Some standards incorporate patented technology. When patented technology becomes essential to practicing a standard, implementers may need access to that intellectual property in order to make compliant products.
This is the field of standard-essential patents and RAND / FRAND licensing commitments. Lemley’s work on intellectual property rights and standard-setting organizations remains useful because it explains that SSO intellectual-property rules influence whether a standard is open or closed, who can sell compliant products, and how standards evolve as technology improves.
The company entering a standards-based market should treat IP analysis as product strategy.
Strategic questions:
| Question | Why It Matters |
|---|---|
| Do we own potentially essential IP? | licensing leverage |
| Do competitors own essential IP? | FTO and cost exposure |
| Are RAND / FRAND commitments attached? | licensing expectations |
| Are royalties predictable? | margin model |
| Is a patent pool relevant? | transaction cost and access |
| Is cross-licensing realistic? | negotiating position |
| Is design-around feasible? | product architecture freedom |
| Could injunction or exclusion risk affect launch? | downside exposure |
A standards strategy that ignores IP is incomplete.
8. Timing Control
Standards have life cycles.
Early, the architecture is fluid. Terminology, evidence, interface design, safety metrics, test methods, and certification procedures are contested.
Later, the standard hardens. Customers adapt. Procurement language copies it. Regulators may reference it. Vendors certify to it. Investors recognize it. Complementors build around it.
The late entrant faces compliance. The early participant may shape.
The U.S. federal system recognizes this strategic importance. OMB Circular A-119 sets policy for federal participation in the development and use of voluntary consensus standards and conformity assessment activities, while the National Technology Transfer and Advancement Act provides a statutory foundation for federal reliance on such standards. NIST’s Standards.gov also notes that the 2025 United States Standards Strategy responds to rapid technological change and geopolitical competition in a world where standards shape emerging industries.
Executive implication: Standards strategy belongs before product architecture hardens.
9. Standards as Ecosystem Strategy
Standards can enlarge a market by reducing fragmentation and enabling complements. They can also determine where profit collects.
A firm should distinguish four strategic positions.
| Position | Meaning | Power Profile |
|---|---|---|
| Standard setter | shapes the rule, interface, or certification path | highest influence; highest coordination burden |
| Standard contributor | contributes technology, evidence, language, or implementation detail | meaningful influence; lower control |
| Standard implementer | builds compliant products efficiently | faster market access; limited rule-shaping power |
| Standard taker | adapts after the rule hardens | highest dependency; lowest influence |
None is inherently superior.
A startup may choose implementer status to reach customers quickly. A platform company may require setter status. A deep-tech company may pursue contributor status to legitimate its architecture. A regulated entrant may need certification strategy before technical superiority matters.
The error is occupying a position by accident.
10. Standards and Innovation
Standards can support innovation by reducing fragmentation, increasing interoperability, lowering buyer uncertainty, and encouraging investment in complementary products.
They can also slow innovation when a premature standard freezes an inferior architecture, protects incumbents, increases certification burden, or shifts attention from performance to compliance.
The executive posture should be exacting.
| Question | Governance Use |
|---|---|
| Does the standard enlarge the market? | market creation |
| Does it reduce buyer risk? | adoption acceleration |
| Does it improve complementor investment? | ecosystem growth |
| Does it preserve incumbent control? | competitive structure |
| Does it freeze technical direction too early? | innovation risk |
| Does it shift margin to the interface owner? | profit-pool analysis |
| Does certification burden exclude smaller innovators? | market-access analysis |
| Does the standard incorporate essential IP? | licensing and FTO |
A standards review should examine both coordination value and constraint cost.
11. Standards Strategy Protocol
Use this protocol before entering a standards-sensitive market.
Step 1 — Identify governing standards
List formal standards, de facto standards, certification regimes, procurement requirements, platform rules, regulatory references, and buyer-mandated practices.
Step 2 — Map the interface
Identify what the standard controls: data exchange, device connection, security, evidence, safety, terminology, measurement, identity, interoperability, or performance.
Step 3 — Map power holders
Name the standards bodies, platform owners, certifiers, dominant implementers, IP holders, regulators, procurement authorities, laboratories, and installed-base owners.
Step 4 — Assess IP exposure
Identify standard-essential patents, RAND / FRAND commitments, patent pools, cross-license needs, royalty expectations, and design-around paths.
Step 5 — Assess certification economics
Estimate time, cost, testing access, laboratory capacity, evidence burden, audit requirements, renewal obligations, failure consequences, and launch impact.
Step 6 — Choose strategic position
Select setter, contributor, implementer, or taker deliberately.
Step 7 — Set governance
Define who owns standards participation, who approves technical commitments, who monitors IP obligations, who manages certification, and who reports standards changes to management.
Step 8 — Review before product freeze
A standard discovered after architecture hardens becomes redesign cost.
12. Standards Governance Ledger
| Item | Required Answer |
|---|---|
| Market standard | Which standard, protocol, certification, or platform rule governs entry? |
| Interface controlled | What connection, data, evidence, or performance rule does it define? |
| Gatekeeper | Who certifies, accredits, recognizes, admits, or rejects? |
| IP exposure | Which patents, licenses, pools, or commitments matter? |
| Installed base | Which existing system benefits from the standard? |
| Complementors | Which third parties invest because of the standard? |
| Certification path | Time, cost, evidence, and retest requirements |
| Strategic position | Setter, contributor, implementer, or taker |
| Owner | Executive accountable for standards strategy |
| Review cadence | When standards changes are reviewed |
| Product impact | Features, architecture, roadmap, claims, and launch implications |
| Stop rule | Standard change, IP issue, or certification failure requiring escalation |
This ledger belongs in product, legal, regulatory, and strategy reviews.
13. Failure Modes
Failure Mode 1 — Late Standard Discovery
The product reaches commercialization before management identifies the governing standard.
Correction: Standards review before architecture freeze.
Failure Mode 2 — Interface Dependence
The company builds around an interface controlled by another party without understanding access, change, fee, or compatibility risk.
Correction: Interface-control analysis and contingency design.
Failure Mode 3 — Certification Underbudgeting
The model treats certification as a minor launch task.
Correction: Certification economics in the cash calendar and launch plan.
Failure Mode 4 — Installed-Base Misread
The company underestimates customer dependence on legacy systems.
Correction: Installed-base and switching-cost review before market entry.
Failure Mode 5 — SEP Surprise
Standard-essential patent exposure appears after product commitments have been made.
Correction: IP and standards analysis as part of product strategy.
Failure Mode 6 — Committee Absence
Competitors participate in standards bodies while the company waits for published outcomes.
Correction: Deliberate standards participation decision: observe, contribute, shape, or implement.
Failure Mode 7 — Compliance Narrowness
The team treats standards as technical compliance while missing market-access, procurement, IP, and ecosystem implications.
Correction: Standards ledger reviewed by product, legal, commercial, and operations together.
14. Board and Executive Questions
Boards and executive teams should ask:
- Which standards define our market access?
- Which standards define customer trust?
- Which interfaces must we conform to?
- Which standards bodies, committees, or consortia matter?
- Which competitors participate in those bodies?
- Which certifier or conformity-assessment process controls adoption?
- Which standard preserves the incumbent installed base?
- Which standard could make our architecture obsolete?
- Which standard-essential patents or IP policies shape the market?
- Are we setting, contributing, implementing, or adapting?
- What changes in product architecture if the standard changes?
- Who owns standards strategy inside the company?
The tenth question clarifies strategic posture. The twelfth turns posture into accountability.
Closing
Standards are instruments of market architecture. They determine what connects, what qualifies, what certifies, what scales, and what becomes normal.
The company that treats standards as a late compliance matter enters a market whose rules have already been shaped. The company that treats standards as strategy can understand where power will collect, which interfaces matter, which certification gates control adoption, which installed bases resist change, and which IP positions will influence bargaining.
The rule is simple:
Find the standard before it defines the market for you.
Sources
- Michael L. Katz and Carl Shapiro, “Network Externalities, Competition, and Compatibility,” American Economic Review 75, no. 3 (1985): 424–440. The classic economics reference for compatibility and network effects in markets where user value depends on network size and interoperability.
- Joseph Farrell and Garth Saloner, “Standardization, Compatibility, and Innovation,” RAND Journal of Economics 16, no. 1 (1985): 70–83. A canonical paper on standardization and compatibility as innovation-coordination problems.
- Mark A. Lemley, “Antitrust, Intellectual Property and Standard-Setting Organizations,” California Law Review 90, no. 6 (2002): 1889–1980. Lemley analyzes how SSO IP rules affect whether standards are open or closed, who can sell compliant products, and how standards evolve.
- WTO, “Technical Barriers to Trade.” The WTO explains that the TBT Agreement seeks non-discriminatory technical regulations, standards, and conformity assessment procedures while avoiding unnecessary trade obstacles and encouraging international standards to facilitate trade.
- NIST, “Standards.gov.” NIST describes standards coordination as supporting innovation and international trade; it also notes that the 2025 United States Standards Strategy responds to technological change and geopolitical competition in which standards shape emerging industries.
- Tim Simcoe, “Standard Setting Committees: Consensus Governance for Shared Technology Platforms,” American Economic Review 102, no. 1 (2012): 305–336. Useful for understanding standards committees as governance institutions for shared technology platforms.
- Marc Rysman and Tim Simcoe, “Patents and the Performance of Voluntary Standard-Setting Organizations,” RAND Journal of Economics 39, no. 1 (2008): 192–212. Useful for understanding patents, standard-setting, and the performance of voluntary SSOs.
