| name | stelow-product-evolutionary-principles |
| description | [stelow] Strategic product evolution and innovation exploration inspired by evolutionary systems thinking, novelty search, stepping-stones theory, and adaptive product ecosystems.
Activate when: - product strategy feels too objective-driven or roadmap-rigid - teams are prematurely optimizing toward fixed outcomes - exploring innovation, experimentation, or long-term adaptability - evaluating product direction beyond short-term metrics - prioritization discussions feel shallow or disconnected - teams need better framing for experimentation and discovery - discussing ecosystems, platforms, adaptability, or emergent behavior - exploring feature prioritization through connections and optionality - discussing product resilience, flexibility, or future evolution
|
| metadata | {"frequency":"rare","category":"research","context-cost":"medium","author":"calionauta","author-url":"https://github.com/calionauta"} |
| disable-model-invocation | true |
Evolutionary Product Thinking
A strategic thinking skill inspired by:
- evolutionary systems
- novelty search
- stepping-stones theory
- adaptive systems
- product ecosystems
- connection mapping
- exaptation
- emergent innovation
This skill helps teams:
- avoid premature convergence
- identify promising stepping-stones
- evaluate evolutionary potential
- explore non-obvious product directions
- prioritize enabling capabilities
- think beyond rigid roadmap logic
- cultivate adaptability and resilience
This is NOT:
- a strict prioritization framework
- a deterministic roadmap generator
- a KPI optimization method
- a growth-at-all-costs system
It is:
- a strategic reflection lens
- an evolutionary exploration framework
- a discovery-oriented planning perspective
- a system for evaluating adaptability and optionality
Cross-Domain Adaptation
This skill is not limited to digital products.
The same evolutionary principles can be adapted to:
- careers and professional growth
- habits and personal development
- relationships and communities
- organizational design
- education and learning
- research and scientific exploration
- creativity and artistic practice
- life strategy and decision-making
To adapt the skill to another domain:
- reinterpret “features” as capabilities, behaviors, practices, or structures
- reinterpret “users” as participants, stakeholders, or agents
- reinterpret “ecosystem” as the surrounding social, organizational, biological, or environmental context
- reinterpret “fitness” as long-term adaptability, resilience, usefulness, meaning, or sustainability depending on the domain
Focus on:
- increasing optionality
- enabling emergence
- preserving diversity
- discovering stepping-stones
- avoiding premature convergence around rigid goals
Core Philosophy
Evolution is Discovery, Not Goal Execution
The central premise:
Great products and innovations often emerge indirectly.
Instead of:
- rigid optimization toward predefined objectives
- narrow feature planning
- excessive convergence
- deterministic roadmaps
this skill encourages:
- exploration
- novelty generation
- adaptive discovery
- optionality creation
- ecosystem thinking
- accumulation of stepping-stones
The skill assumes:
- the future is partially unknowable
- valuable discoveries are often indirect
- many breakthroughs emerge from unexpected recombinations
- innovation frequently comes from adjacent exploration
- premature optimization can reduce long-term adaptability
Stepping-Stones Principle
A core idea of this skill:
Important innovations often cannot be reached directly.
Instead:
- one discovery enables another
- one capability reveals new possibilities
- one experiment unlocks future options
- one architectural decision enables future evolution
Therefore:
Evaluate ideas not only by:
- immediate ROI
- short-term impact
- direct business metrics
But also by:
- what they unlock
- what they connect
- what they enable
- what future paths they reveal
- what new niches they make possible
Activation Signals
Use this skill when:
- teams are stuck in roadmap rigidity
- innovation feels stagnant
- product planning is overly KPI-driven
- teams struggle to discover differentiated directions
- prioritization debates ignore optionality
- there is pressure to over-specify the future
- ecosystems and integrations matter strategically
- platform adaptability is important
- experimentation quality matters
- product evolution needs reframing
- teams are exploring future bets
- organizations need resilience instead of pure optimization
Core Operational Principles
Prefer Exploration Over Premature Optimization
Avoid:
- overcommitting early
- rigid long-term solution assumptions
- excessive convergence
- optimizing too early for a single direction
Encourage:
- adjacent exploration
- parallel experiments
- multiple hypotheses
- discovery-driven iteration
Preserve Diversity
Healthy product ecosystems usually benefit from:
- multiple workflows
- multiple user types
- multiple use cases
- multiple niches
- multiple solution paths
Avoid assuming:
- one interface fits all
- one workflow dominates forever
- one strategy eliminates all alternatives
Value Enabling Capabilities
Some features matter less because of direct user value,
and more because they:
- unlock future features
- simplify future experimentation
- connect systems
- create reusable primitives
- increase adaptability
- enable integrations
- support future exaptation
These enabling capabilities are often high-value stepping-stones.
Favor Evolutionary Optionality
Prefer solutions that:
- remain adaptable
- support recombination
- allow future reinterpretation
- support new workflows
- expose reusable primitives
- permit future emergence
Avoid:
- overly rigid architecture
- irreversible assumptions
- premature specialization
- tightly coupled systems
Evolutionary Forces
The skill analyzes ideas through six evolutionary forces.
1. Selection Pressure
Selection pressure acts as an optimization force.
In product systems, this includes:
- market forces
- business constraints
- user adoption
- operational viability
- sustainability
Questions:
- what pressures shape survival?
- what is being optimized?
- are we over-optimizing too early?
- are metrics narrowing discovery?
Warnings:
- excessive objective fixation can reduce innovation
- rigid KPIs can eliminate valuable exploration
- optimization without exploration leads to convergence
2. Mutation
Mutation represents small variations or unexpected deviations.
In products:
- accidental discoveries
- unusual user behavior
- unexpected workflows
- productive “misuse”
- surprising experiments
- emergent patterns
Questions:
- what unexpected behaviors could emerge?
- how might we create conditions for new behaviors to appear?
- what kinds of productive misuse should the system allow?
- what experimentation surfaces increase the chance of discovering novelty?
- what edge cases could become meaningful future patterns?
3. Genetic Drift
Drift represents subtle changes that accumulate over time.
In products:
- small workflow shifts
- architectural evolution
- gradual behavior changes
- incremental cultural adaptation
- unnoticed ecosystem shifts
Questions:
- what subtle shifts could compound into major future changes?
- what seemingly-neutral decisions may later reshape the ecosystem?
- what latent capabilities are worth accumulating even before they appear valuable?
- how can we preserve room for slow, emergent adaptation?
- what future possibilities become easier if we slightly change direction now?
4. Gene Flow
Gene flow represents cross-pollination between systems.
In products:
- integrations
- ecosystem participation
- importing external ideas
- interdisciplinary influence
- community extensions
- APIs and plugins
Questions:
- what external systems could introduce entirely new behaviors or workflows?
- what adjacent ecosystems could reshape how this product evolves?
- what ideas from other domains should intentionally migrate inward?
- how can outside communities influence future directions?
- what integrations could unlock unexpected combinations and niches?
5. Exaptation
Exaptation occurs when something built for one purpose
becomes valuable for another.
Examples:
- infrastructure reused unexpectedly
- workflows repurposed
- APIs becoming platforms
- internal tools becoming products
- side features becoming core value
Questions:
- what future purposes could emerge from this capability?
- what reusable primitives might become valuable later in unexpected contexts?
- how can we design this so future teams can reinterpret and repurpose it?
- what secondary uses could emerge if the product evolves into adjacent spaces?
- what would make this capability useful far beyond its original intent?
6. Local Competition
Local competition encourages niche diversity.
Instead of competing globally on everything,
products evolve by:
- specializing
- serving niches
- differentiating workflows
- reducing direct competition
Questions:
- what niche are we uniquely adapted for?
- where can diversity create resilience?
- are we converging too much with the market?
Genotype vs Phenotype
This skill distinguishes:
Genotype
The adaptable underlying structure.
Examples:
- architecture
- primitives
- APIs
- capabilities
- composability
- extensibility
- reusable systems
Phenotype
The visible expression experienced by users.
Examples:
- workflows
- templates
- configurations
- UI manifestations
- specialized use cases
Strategic insight:
Strong products often have:
- flexible genotypes
- multiple possible phenotypes
- contextual adaptability
- reusable primitives
Questions:
- does the system support multiple expressions?
- can users adapt it to different contexts?
- are templates/extensions enabling phenotypic diversity?
Connection Mapping
This skill strongly values connection mapping.
Evaluate not only:
But also:
- relationship networks
- enabling potential
- dependency structures
- ecosystem influence
- adjacency effects
Solution Space Mapping
Analyze:
- how features connect to other features
- what capabilities they unlock
- what workflows they influence
- what future paths they enable
Questions:
- what does this unlock?
- what becomes easier afterward?
- what future experiments become possible?
- does this increase optionality?
Problem Space Mapping
Analyze:
- how ideas connect to user intentions
- how multiple jobs-to-be-done overlap
- what adjacent use cases emerge
- what new user groups become reachable
Questions:
- what adjacent needs appear?
- what additional jobs become reachable?
- what communities benefit indirectly?
Evolutionary Prioritization
Prioritize not only by:
Also evaluate:
- enabling power
- network effects
- optionality creation
- future adaptability
- ecosystem leverage
- exaptation potential
- experimentation acceleration
- strategic flexibility
Evolutionary Evaluation Criteria
Use the following categories as reflection lenses.
These are NOT objective scoring systems.
They are:
- strategic prompts
- discussion catalysts
- prioritization lenses
- exploration aids
1. Strategic Alignment
Evaluate:
- alignment with long-term direction
- reinforcement of core principles
- contribution to organizational resilience
- support for strategic adaptability
Questions:
- does this strengthen strategic positioning?
- does this reinforce product identity?
- does this improve organizational health?
2. Differentiation and Niche Fitness
Evaluate:
- difficult-to-copy advantages
- differentiation quality
- niche strength
- unique positioning
- workflow superiority
- community potential
Questions:
- what makes this hard to imitate?
- what niche does this dominate?
- does this create meaningful distinction?
3. Flexibility and Adaptability
Evaluate:
- configurability
- modularity
- future extensibility
- support for multiple workflows
- reuse potential
- experimentation support
Questions:
- can this evolve?
- can users adapt it?
- does this enable future products?
4. Ecosystem and Connectivity
Evaluate:
- integration potential
- API leverage
- plugin ecosystems
- interoperability
- external participation
- cognitive diversity in design
Questions:
- what ecosystems connect here?
- can others build on top of this?
- does this encourage external innovation?
5. Sustainability and Long-Term Impact
Evaluate:
- human sustainability
- operational sustainability
- environmental implications
- organizational resilience
- long-term ecosystem health
Questions:
- does this improve long-term health?
- what hidden costs emerge later?
- should this even exist long-term?
- when should this be discontinued?
Important Warnings
Evolution is NOT Growth-at-All-Costs
Avoid:
- endless expansion
- monopolistic thinking
- convergence obsession
- extraction-only strategies
Healthy ecosystems often require:
- diversity
- coexistence
- specialization
- niche adaptation
- decentralized evolution
Survival Is Not Always the Goal
Some products or features should:
- evolve
- split
- transform
- merge
- disappear
- become stepping-stones for something else
The goal is not preserving every artifact forever.
The goal is:
- adaptive ecosystem health
- meaningful evolution
- resilient exploration
Metrics Can Blind Discovery
Metrics are useful.
But excessive objective fixation may:
- narrow exploration
- reduce novelty
- suppress experimentation
- eliminate stepping-stones
- create local maxima traps
Balance:
- optimization
with
- exploration.
Interaction Guidelines
When facilitating workshops or strategic discussions:
Prefer:
- exploratory questions
- connection mapping
- adjacency analysis
- optionality analysis
- ecosystem thinking
- scenario exploration
- evolutionary tension analysis
Avoid:
- pretending the future is fully knowable
- forcing false certainty
- premature prioritization closure
- over-specifying long-term roadmaps
Recommended Output Structure
1. evolutionary diagnosis
Analyze:
- current evolutionary constraints
- convergence risks
- ecosystem limitations
- adaptability bottlenecks
- exploration quality
2. stepping-stones analysis
Identify:
- enabling capabilities
- optionality creators
- future unlocks
- reusable primitives
- latent opportunities
3. evolutionary forces analysis
Evaluate the proposal through:
- selection pressure
- mutation
- drift
- gene flow
- exaptation
- local competition
4. connection mapping
Map:
- feature relationships
- workflow adjacency
- ecosystem leverage
- future capability unlocks
- problem-space overlap
5. evolutionary opportunities
Identify:
- experimentation paths
- future niches
- exaptation opportunities
- adaptability improvements
- diversification opportunities
6. risks of premature convergence
Identify:
- over-optimization
- rigidity
- lock-in
- narrow KPI dependence
- ecosystem fragility
7. strategic recommendations
Recommend:
- exploration directions
- enabling investments
- evolutionary sequencing
- optionality preservation
- ecosystem positioning
Relationship with Other Skills
This skill pairs especially well with:
-
stelow
for the complete product definition workflow (shaping, critique, planning, execution routing)
-
stelow-product-scope-executor
for routing approved scopes to the correct executor
-
stelow-product-discovery
for validating ideas with short learning cycles
Expected Behavior
Strong outputs:
- reveal hidden evolutionary potential
- identify enabling capabilities
- preserve optionality
- expose ecosystem dynamics
- encourage adaptive thinking
- balance optimization with exploration
- identify stepping-stones
- reveal long-term leverage
Weak outputs:
- rigid roadmap thinking
- overconfidence about the future
- excessive KPI obsession
- feature-factory logic
- simplistic prioritization
- convergence-at-all-costs
- ignoring ecosystem dynamics
- treating products as static artifacts
