norvigs-law
Skill6 starsChanged 34 days agoMITView on GitHub
Apply Norvig's Law when evaluating growth claims about technology adoption, market size projections, "exponential growth" narratives, or headlines claiming a technology will "double" its reach when it's already dominant. Trigger on phrases like "X is growing exponentially", "this will double in the next year", "the market will 2x", or any context where someone is applying growth rate assumptions to a technology that already has significant penetration. Also useful when evaluating numeracy in tech journalism and analyst reports.
In this repository79 other files it gives its agents.
- adr-phase-coverageSkill
- aposd-red-flag-reviewSkill
- apple-on-device-aiSkill
- artifact-gatesSkill
- asc-app-create-uiSkill
- asc-build-lifecycleSkill
- asc-cli-usageSkill
- asc-crash-triageSkill
- asc-id-resolverSkill
- asc-localize-metadataSkill
- asc-metadata-syncSkill
- asc-notarizationSkill
- asc-ppp-pricingSkill
- asc-release-flowSkill
- asc-revenuecat-catalog-syncSkill
- asc-shots-pipelineSkill
- asc-signing-setupSkill
- asc-submission-healthSkill
- asc-subscription-localizationSkill
- asc-testflight-orchestrationSkill
- asc-wall-submitSkill
- asc-workflowSkill
- asc-xcode-buildSkill
- choose-boring-technologySkill
- ci-preflightSkill
- conways-lawSkill
- cost-routingSkill
- cost-tier-routingSkill
- cunninghams-lawSkill
- ddd-strategic-auditSkill
- ddd-tactical-reviewSkill
- debug-test-captureSkill
- developing-ios-appsSkill
- doerrs-lawSkill
- fitts-lawSkill
- fix-regression-guardSkill
- galls-lawSkill
- goodharts-lawSkill
- greenspuns-tenth-ruleSkill
- gsd-core-hooksSkill
- hofstadters-lawSkill
- hyrums-lawSkill
- ios-accessibilitySkill
- ios-simulator-boot-healthSkill
- kerckhoffs-principleSkill
- kernighans-lawSkill
- knuths-optimization-principleSkill
- lady-lovelaces-objectionSkill
- leaky-abstractionsSkill
- linuss-lawSkill
- mobile-ios-designSkill
- money-boundary-judgmentSkill
- moores-lawSkill
- no-deferSkill
- parkinsons-lawSkill
- peter-principleSkill
- postels-lawSkill
- post-fix-traceSkill
- qa-test-architectSkill
- rubber-duckSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
When someone says "smartphone adoption will double in the next 5 years," check the current penetration rate.
- Distinctive: line 34
When a saturated market shows "doubling," it usually means something changed about how the metric is being measured — a new geography, a …
- Distinctive: line 46
When you see a growth claim:
- Distinctive: line 57
When an analyst says this will "2x," are they assuming growth where growth is now constrained?
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Norvig's Law
"Any technology that surpasses 50% penetration will never double again." — Peter Norvig, 1999
The core idea
This is a deliberately simple, tongue-in-cheek observation about mathematics and the growth of technology. If a technology already reaches more than 50% of its target market, it cannot double again — because doubling would require more than 100% penetration, which is impossible.
More broadly: growth rates that sound impressive early in adoption become mathematically constrained as penetration increases. The "doubling" narrative that works at 1% doesn't work at 51%.
Why this matters
Evaluating growth claims: When someone says "smartphone adoption will double in the next 5 years," check the current penetration rate. If it's already at 60% of the relevant population, doubling is impossible. Claims like this reveal either innumeracy or deliberate misdirection.
Understanding S-curves: Technology adoption typically follows an S-curve:
- Slow initial growth (early adopters)
- Rapid growth through the middle (majority adoption)
- Flattening as the market saturates
A lot of projections implicitly assume you're always in the middle "rapid growth" phase, even when you're clearly approaching saturation. Norvig's Law is a quick check: where are we on the S-curve?
Skepticism about market reports: Analyst reports and press releases frequently cite impressive percentage growth rates for technologies that are approaching saturation. If a technology is at 60% penetration and grows to 65%, that's a ~8% growth rate — but the absolute potential for further growth is limited.
Recognizing when "growth" means something different: When a saturated market shows "doubling," it usually means something changed about how the metric is being measured — a new geography, a new segment, a redefinition of the market. That's worth understanding before acting on the number.
The broader principle: numbers need context
Norvig's Law is really an exercise in critical numeracy:
- Percentages need a denominator.
- Growth rates need a baseline.
- "Doubling" from a tiny base is very different from doubling from a large one.
- Market size claims need a clear definition of the market.
Applying it
When you see a growth claim:
- What is the current penetration rate?
- What is the total addressable market, and how is it defined?
- Is doubling mathematically possible given current penetration?
- Is the growth rate slowing as expected on an S-curve?
- Is the impressive-sounding percentage from a small or large base?
Key questions to surface
- What is the current adoption rate, and is doubling actually possible at this level?
- Is this market already in the saturation phase of the S-curve?
- When an analyst says this will "2x," are they assuming growth where growth is now constrained?
- Is this percentage growth claim from a small base (impressive) or a large one (mathematically limited)?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

