Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", or "tech go-to-market". Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy. Trigger with 'crossing', 'the', 'chasm'.
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", or "tech go-to-market". Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy. Trigger with 'crossing', 'the', 'chasm'.
allowed-tools
Read, Glob, Grep
license
MIT
author
Wondelai <hello@wondelai.com>
version
1.0.1
compatible-with
claude-code, codex, openclaw
tags
["business","crossing-chasm"]
Crossing the Chasm Framework
Strategic framework for marketing and selling disruptive technology products, particularly for transitioning from early adopters to mainstream customers.
Core Principle
There is a chasm between early adopters and the mainstream market. Most tech companies fail not because they can't build great products, but because they can't cross from visionaries who love new technology to pragmatists who just want solutions that work.
The foundation: Early adopters and mainstream customers want fundamentally different things. What wins over innovators actively repels the early majority. You must change your strategy—and your whole product—to cross the chasm.
Scoring
Goal: 10/10. When evaluating go-to-market strategy for tech products, rate 0-10 based on alignment with chasm-crossing principles. A 10/10 means proper beachhead selection, whole product strategy, and positioning for pragmatist buyers; lower scores indicate early-market tactics applied to mainstream market. Always provide current score and improvements needed to reach 10/10.
The Technology Adoption Life Cycle
Innovators → Early Adopters → [CHASM] → Early Majority → Late Majority → Laggards
2.5% 13.5% 34% 34% 16%
The Chasm: The gap between early adopters (13.5%) and early majority (34%). This is where most tech products die.
The Five Buyer Groups
Segment
% Market
Psychology
What They Buy
What They Need
Innovators
2.5%
Technology enthusiasts
The newest, coolest tech
Product exists, technical specs
Early Adopters
13.5%
Visionaries seeking advantage
Change, revolution, competitive edge
Vision, big potential, strategic value
[THE CHASM]
—
—
—
—
Early Majority
34%
Pragmatists
Productivity improvements
Whole product, references, de-risked
Late Majority
34%
Conservatives
Avoid being left behind
Commodity, support, low risk
Laggards
16%
Skeptics
Only when forced
Cheap, simple, necessary
Critical insight: Early adopters and early majority look similar but want completely opposite things.
Early Adopters (Visionaries):
Want to be first
Willing to work around bugs
Buy the future vision
Don't need references
Want custom solutions
High risk tolerance
Early Majority (Pragmatists):
Want proven solutions
Need it to "just work"
Buy present value
Need references from peers
Want standards
Low risk tolerance
Why this matters: Marketing to both simultaneously is impossible. Visionary testimonials scare off pragmatists. "Revolutionary" positioning is a red flag to the early majority.
Geoffrey A. Moore is a consultant, venture partner, and author focused on disruptive innovation and market development. His work at The Chasm Group and Chasm Institute has influenced go-to-market strategy for enterprise technology companies for over 30 years. Crossing the Chasm has sold over 1 million copies and is required reading at many business schools and tech companies. Moore serves on the boards of several technology companies and advises Fortune 500 firms on technology adoption.
Overview
Navigate the technology adoption lifecycle from early adopters to mainstream market.
Prerequisites
Access to the logging environment or API
Required CLI tools installed and authenticated
Familiarity with logging concepts and terminology
Instructions
Assess the current state of the logging configuration
Identify the specific requirements and constraints
Apply the recommended patterns from this skill
Validate the changes against expected behavior
Document the configuration for team reference
Output
Configuration files or code changes applied to the project