Living
Systems
Design
Systems
Design
Nature has been solving complex adaptive problems for 3.8 billion years. This framework borrows its logic — not its aesthetics — to help you design services, businesses, and experiences that are genuinely resilient.
Most design frameworks are linear: research → define → ideate → deliver. But living systems don't work that way. They observe continuously, find recurring patterns, emulate what works, run small experiments, read feedback signals, propagate what takes root, and then cycle back — because conditions always change.
This tool guides you through the full lifecycle: from the naturalist's first field notes through to market deployment, customer experience, and long-term ecosystem health. At every stage it names both the biomimicry logic and the legacy SD/BD/CX equivalent so you can move between languages fluently.
The practitioner's role here is accompanist, not architect — you are helping a system find its own next form, not installing a solution. This matters because the same framework works for service design, community-led product development, and organisational change. The biology is the same. The questions are the same. What changes is who you are accompanying and what kind of threshold they are crossing.
Formation track
Develop your way of being as a practitioner — inquiry discipline, pattern recognition, comfort with not-knowing. The framework as a practice, not a process.
Method fluency track
Build command of specific tools — research methods, canvas structures, facilitation moves — so you can reach for the right instrument without thinking about it.
Core Principles
Principle 01
Observe before you interpret
Legacy: User research / ethnography
A naturalist fills the notebook before drawing conclusions. Most design fails because interpretation happens before observation is complete.
Principle 02
Patterns reveal the system's logic
Legacy: Synthesis / affinity mapping / insight generation
Nature repeats solutions that work: spirals, networks, edge effects, feedback loops. Find the recurring form — that's the design brief hiding inside the data.
Principle 03
Emulate what evolution already solved
Legacy: Insight synthesis / HMW / problem framing
Ask: what organism has already solved a version of this challenge? Mycelium, mangroves, immune systems, and ant colonies are all design precedents.
Principle 04
Test cheaply at the edge before scaling
Legacy: Prototyping / testing / MVP
Evolution runs billions of experiments simultaneously. Scale only what survives contact with reality. Failure is not a setback — it is the feedback loop working.
Principle 05
Design the whole ecosystem, not just the organism
Legacy: Business design / CX strategy / service ops
A service is not a product. It is a relationship between an organism and its habitat. The business model, the customer experience, and the operational infrastructure are all part of the same living system.
Principle 06
Return to the commons — plant where it can keep growing
Legacy: Sustainability / commons governance / knowledge transfer
The endpoint of good design is not market capture — it is ecosystem enrichment. Ask where your work can seed knowledge, build shared infrastructure, or enable others to carry the pattern forward without you.
How to use this tool
1
Enter your concept
Type your working concept in the bar at the top. Hit "Generate Journey" to AI-populate all stages, or work through them manually.
2
Follow the Research cycle
Work through Observe → Pattern → Emulate → Prototype → Adapt → Propagate. Each stage builds on the last.
3
Plan your Go-to-Field
When your concept is validated, move to the Field phase: soil conditions, actor agreements, germination plan, signal network.
4
Design the Business & CX
Use the Business Design canvas (metabolic strategy) and the CX canvas (habitat design) to complete the full ecosystem.
5
Export at any stage
Every panel has its own export. The Summary view gives you the full picture. Use Print for a shareable artifact.
6
Cycle back
Living systems don't stop at delivery. New field signals should feed back into your Observe stage. Use the Timeline to track where you are.
10
Return to the commons
After deployment: where does this learning belong? Open-source a method, seed a community of practice, publish findings, or hand the infrastructure to those it serves.
Field Guide
New to service design or this framework? Read the Limicelia Service Design 101 — the principles, vocabulary, and why this model works differently from conventional consulting.
The Full Lifecycle
A living system doesn't follow a linear process — it follows an adaptive cycle. Each phase below represents a distinct mode of engagement with the ecosystem. Click any phase to enter its workspace. The feedback arrows show where signals from later phases re-enter earlier ones.
Phase 1–2
Research & Define
Naturalist observing, finding recurring forms
Legacy SD: Discover + Define
Observe — field notes, sources
Pattern — observations, themes
Emulate — insights, HMWs
Phase 3
Develop & Test
Small experiments, fast failure, feedback loops
Legacy SD: Develop + Deliver (early)
Prototype — service concepts
Adapt — test plans, signals
Propagate — method selection
Phase 4
Go-to-Field
First germination — seed meets soil
Legacy BD: GTM strategy + pilot launch
Soil Conditions — readiness
Actor Agreements — partnerships
Germination Plan — pilot
Signal Network — metrics
Scale Threshold — replication
Phase 5
Business & CX Design
Metabolic strategy + habitat design
Legacy BD: Business model + CX strategy + Service Ops
Value Organism — value prop
Energy Flows — revenue model
Habitat Design — CX journey
Colony Health — service ops
The Living Systems Journey
Nature has solved every design challenge we face — scarcity, resilience, trust, feedback, adaptation. This framework borrows its structure from ecosystems: observe without agenda, find the deep patterns, emulate what works, experiment fast, iterate from signals, and propagate what takes root.
1
The Naturalist's Eye
Observe
Service Design: Inputs & Field Research
Gather without agenda. Articles, interviews, field notes, policy docs, lived stories. A naturalist doesn't classify on the first day — they just watch. Don't analyse yet.
2
Recurring Forms
Pattern
Service Design: Observations & Themes
Nature repeats its solutions: spirals, networks, feedback loops, edge effects. Look for what keeps appearing in different forms across your field notes. Name patterns as tensions, not topics.
3
Learn from Living Systems
Emulate
Service Design: Insights & Problem Statements
Biomimicry's core move: what has nature already solved that mirrors this challenge? Translate patterns into insights, then into HMW questions that borrow nature's logic.
4
Small Experiments
Prototype
Service Design: Concept Sketching
Nature tests constantly — billions of micro-experiments every season. Sketch service concepts at low fidelity. What's the minimum viable interaction that tests your HMW?
5
Feedback Loops
Adapt
Service Design: Testing & Learning
Healthy ecosystems run on feedback. Plan how you'll test each concept — who, what signal, what threshold. Failure is data. What does the system tell you when you act?
6
Scale What Takes Root
Propagate
Service Design: Methods & Next Steps
Seeds spread through wind, water, animals — not one mechanism. Choose the propagation methods that fit your ecosystem: co-design, blueprinting, safaris, system mapping.
1
Observe
Naturalist — watch before you classify
Service design: Inputs & field research — no analysis yet
⚑ Hard questions — Observe ▶
What are you not looking for that might be the most important thing present?
Who is absent from your research that would break your current understanding?
What would you observe if your current framing of the problem is completely wrong?
What do insiders treat as normal that an outsider would find strange?
If you removed yourself from the observation, what story would the data tell on its own?
List everything you're bringing to the table: articles, interviews, field notes, policy documents, lived experience stories, data. Don't interpret. A naturalist fills the notebook before drawing conclusions.
2
Pattern
Recurring Forms — nature repeats what works
Service design: Observations & themes — name tensions, not topics
⚑ Hard questions — Pattern ▶
Is this pattern structural (inherent to the system) or situational (particular to circumstances)?
Who benefits from this pattern staying exactly as it is?
What would have to be true about human nature for this pattern to exist?
Where does this pattern break down — what are the edges of its validity?
If this pattern is real, what does it predict about adjacent situations you haven't yet observed?
Read across your observations. Write "I notice…" statements first, then group into recurring patterns. Name each cluster as a tension or dynamic — not a topic. "Trust erodes faster than it builds" beats "Trust".
Observations (I notice…)
Themes (tensions & dynamics)
3
Emulate
Learn from Living Systems — reframe through nature's logic
Service design: Insights & HMW questions
⚑ Hard questions — Emulate ▶
Does your HMW assume a solution? Rewrite it so the solution space is genuinely open.
Who is the specific person this question is for — name them, don't describe a category.
What would your HMW look like if you moved the problem one level up in the system?
Is your insight a genuine surprise, or confirmation of what you already believed?
What's the most uncomfortable implication of your insight if it's true?
Biomimicry asks: what organism or ecosystem has already solved this? Mycelium distributes nutrients without central control. Mangroves protect edges. Fire clears for regeneration. Translate your patterns into insights — then into HMW questions that borrow nature's strategy.
Insights (unexpected truths)
Problem statements
A strong problem statement…
How Might We questions
HMW quality checks
4
Prototype
Small Experiments — nature tests billions of variations
Service design: Concept sketching — low fidelity, fast
⚑ Hard questions — Prototype ▶
What's the one assumption this concept cannot survive being wrong about?
Could someone with a different power position in the system use this in a way you didn't intend?
What would this look like at 10× scale — does the model hold or collapse?
What does the person with the least resources in your target system need from this?
If this failed, what would be the most likely cause — and have you designed against it?
Pick your strongest HMW. Sketch a service concept — describe the key interaction, touchpoint, or moment in enough detail to test. What does someone experience? What happens backstage? Keep it scrappy — the goal is to make the idea tangible, not polished.
Service concepts
5
Adapt
Feedback Loops — healthy systems respond to signals
Service design: Testing plan & learning criteria
⚑ Hard questions — Adapt ▶
What result would cause you to abandon this direction entirely — and are you actually willing to do that?
Are you testing what you believe, or what you hope?
Who would be harmed by a failed test — and have you accounted for them?
What would a negative result tell you that a positive result wouldn't?
Is your success signal behavioural (observable) or attitudinal (reported)? Which is more trustworthy here?
For each concept, define: who you'll test with, what you're measuring, and what signal tells you it's working (or not). Nature doesn't distinguish failure from data — both are feedback. Set a threshold before you start.
Test plans
6
Propagate
Scale What Takes Root — seeds spread through multiple vectors
Service design: Methods, activities & next actions
⚑ Hard questions — Propagate ▶
Who are the carriers — the people who spread this without you pushing it?
What network or community does this need to land in to sustain itself?
What would make this impossible for the target system to ignore?
How does this spread without requiring your continued presence?
What are you over-investing in versus what actually drives propagation?
Seeds don't wait for perfect conditions — they use wind, water, animals, and decay. Choose the propagation methods that match your ecosystem. Not all need equal investment; pick the vectors that reach the right soil.
Selected propagation methods
No methods selected yet.
Worked Example
Community Water Access — Biomimicry Lens
Stage 1
Observe
Field notes
UNICEF field reports on rural water point failure rates in Sub-Saharan Africa
Interviews with women who walk 3–6 km daily to fetch water
Community forum transcripts: what happens when a pump breaks
Academic literature: social dynamics of communal infrastructure
Case studies: where water access has been sustained for 20+ years
Stage 2
Pattern
Observations + tensions
I notice women are primary users but rarely primary decision-makers in water governance
I notice working pumps attract informal care networks; broken ones attract blame cycles
I notice external maintenance contracts collapse when funding ends
Pattern: Ownership and use are distributed differently — this mismatch is the failure point
Pattern: Care infrastructure scales from relationships, not from rules
Stage 3
Emulate
Insights + HMWs
Nature analog: mycelium networks — no centre, distributed sensing, rerouting when one node fails
Insight: Water point stewards need social legitimacy, not just technical training, because maintenance follows trust, not procedure
How might we design water governance so that the people who carry the most responsibility also hold the most authority?
How might we build maintenance systems that strengthen when one node fails — like a mycelium network?
Stage 4
Prototype
Service concepts
Concept A: A rotating stewardship council — women elected by water-point users, with a small maintenance fund they control
Concept B: A peer network of 3 water points: when one breaks, the others send a steward, not a complaint
Concept C: A visual maintenance log pinned at the pump — public, legible, names who is responsible this month
Stage 5
Adapt
Test plans
Test Concept A with 2 communities over 3 months — signal: does the council meet without external prompting?
Test Concept B with 3 neighbouring pumps — signal: mutual repair within 48h without NGO involvement
Failure signal: if the log is blank after 6 weeks, the concept didn't transfer ownership
Stage 6
Propagate
Methods & next steps
Service safaris: walk with stewards through their maintenance routines
Ecosystem mapping: visualise all actors, resource flows, and accountability gaps
Co-design sessions: redesign governance structures with users as co-authors
Service blueprinting: map what sustains beyond a pilot — who funds, who repairs, who decides
Stage 7
Go-to-Field
Deployment & soil conditions
Legacy: Launch Planning
Legacy: Launch Planning
Actor alignment 🟢 — Water committee chairs in 4 communities briefed; community water fund governance agreed
Root infrastructure 🟡 — Maintenance toolkit designed; technical training delivered to 8 stewards; spare parts supplier identified but not yet contracted
Signal network 🟡 — Monthly steward check-in scheduled; WhatsApp group active; NGO field staff as first-line support for 90 days
Germination window 🟢 — Pre-rainy season deployment: community water need is at its peak, motivation to solve is highest
Nutrient budget 🟡 — 12-month operating budget secured; community contribution model designed but not yet tested at scale
30-day signal: Do stewards convene for the first check-in without NGO prompting?
Stage 8
Business Design
Metabolic strategy
Legacy: Business Model
Legacy: Business Model
Value Organism — Reliable water access governed by the community it serves; the water point as infrastructure commons, not a commercial product
Habitat Segments — Primary: women aged 18–55 who currently walk >2km for water. Keystone: elected stewards. Edge: seasonal migrant households
Mutualist Partners — WASH NGO (technical capacity, initial funding) ↔ Community (governance legitimacy, local knowledge); local government (policy recognition) ↔ programme (proof points for policy)
Energy Returns — Community water fund (micro-levy per household per month): covers maintenance at ~80% collection rate; grant funding for capital replacement at 5-year intervals
Succession condition — NGO exits at month 18; community water committee holds full governance, financial, and technical accountability
Stage 9
CX + Ops
Habitat health
Legacy: Service Operations
Legacy: Service Operations
Habitat Experience Map (key phases)
Approach — Women know who the steward is and trust she can help if the pump breaks. Feeling: calm confidence.
Core — Pump working; collection takes <20 min. Steward visible in community. Signal: daily collection count on wall chart.
Stress — Pump breaks. Steward notified within 2h. Repair arranged within 48h. No return to the long walk.
Return — Monthly community meeting reviews water fund balance, maintenance record, and disputes. Trust renewed through transparency.
Colony Health (6-month check)
Staff Ecosystem 🟢 — Stewards report pride in role; knowledge shared informally; no burnout signals
Process Metabolism 🟡 — Levy collection at 74% (below 80% threshold); follow-up process for non-payers not yet standardised
Distress Signals 🟢 — One pump breakdown handled within 24h; one household dispute resolved by committee without NGO involvement
Adaptive Capacity 🟡 — Stewards identified levy communication as a gap; community agreed new approach; implementation pending
Go-to-Field
The seed has been tested. Now it goes into the ground. Go-to-Field translates your validated prototype into a deployable service — with the ecosystem conditions, actor agreements, and feedback infrastructure needed for it to survive beyond a pilot.
This is not "launch." In nature, propagation is an ongoing relationship between the seed and the soil — not a one-time event. This phase establishes that relationship.
G1
Soil Conditions
What must be true in the environment for this to germinate?
GTM equivalent: market readiness & ecosystem prerequisites
A seed needs the right soil chemistry, moisture, temperature, and light. Your service needs the right organisational, cultural, and systemic conditions. Map what must be true — and what isn't yet true — before you plant.
Conditions that are ready
Conditions that need preparation
G2
Actor Agreements
Which organisms in this ecosystem need to be in relationship?
GTM equivalent: partnerships, distribution, and stakeholder alignment
A fig tree cannot reproduce without the fig wasp. Your service cannot function without the actors who hold capacity, legitimacy, or access that you don't. Name the mutualist relationships required — and what each party gives and receives.
Required actors & their roles
Agreements to secure
G3
Root Infrastructure
What sustains the canopy when you are not watching?
GTM equivalent: operational model, staffing & backstage systems
The mycorrhizal network sustains the forest without any organism managing it deliberately. What backstage infrastructure must exist for your service to sustain itself? Staff capacity, data systems, funding flows, informal care networks, governance structures.
Infrastructure in place
Infrastructure to build
G4
Germination Plan
Where does the first seed go in, and what happens in the first season?
GTM equivalent: pilot plan, launch sequence & first cohort
Seeds don't germinate everywhere at once. They start in the most favourable microclimate — a sheltered north-facing slope, a nutrient-rich pocket of soil. Define your first planting site, your first season of growth, and what you will observe in those first weeks.
First planting site (pilot context)
First season timeline
G5
Signal Network
How will the system tell you it is healthy — or in distress?
GTM equivalent: metrics, feedback loops & early warning system
Trees under pest attack release chemical signals that neighbouring trees detect and respond to. Design your signal network — the indicators that tell you the service is healthy, the early warnings that tell you something is wrong, and the response protocol when distress signals fire.
Health signals (signs it's working)
Distress signals (early warnings)
G6
Scale Threshold
When has the ecosystem demonstrated readiness to expand?
GTM equivalent: scale criteria, replication model & exit from pilot
Ecosystems don't scale arbitrarily — they expand when conditions are right and capacity exists. Define the threshold: what must be true before you replicate? What signals show the service can survive in new soil without constant intervention?
Scale readiness criteria
Scale conditions we will require
Replication model
Business Design
Metabolic Strategy Legacy: Business Model Canvas / Value Prop
Every living organism has a metabolic strategy — a way of converting available energy into survival and growth. Your business model is your metabolic strategy. How does value flow in, transform, and sustain the organism?
Value Organism
What does this organism uniquely offer?
Legacy: Value Proposition
What pain does it relieve? What capability does it unlock? Who is it adapted for? What would be lost if it disappeared?
Habitat Segments
Which habitats and species does this serve?
Legacy: Customer Segments
Which communities/users thrive with this service? Who is the keystone user? Who is currently at the edge and underserved?
Mutualist Partners
Who must be in relationship for the system to work?
Legacy: Key Partners
Who are your fig wasps? What do they give / receive? Which partner is keystone — whose absence collapses the system?
Core Capabilities
What must this organism do exceptionally well?
Legacy: Key Activities
What activities are essential to delivering your value? What dies if you stop doing it? What is your competitive metabolism?
Root Resources
What infrastructure must exist underground?
Legacy: Key Resources
What physical, intellectual, human, and financial resources are essential? What is your mycorrhizal infrastructure?
Dispersal Channels
What vectors carry value to the right soil?
Legacy: Channels
How do people discover, access, and receive the service? What dispersal mechanism fits the ecosystem — wind, water, animal, decay?
Symbiotic Bonds
How does the relationship deepen over time?
Legacy: Customer Relationships
What kind of relationship does each segment need? How does it become mutualistic (not extractive) over time?
Energy Costs
What does it cost to maintain this metabolism?
Legacy: Cost Structure
What are your largest cost centres? What costs scale with volume? What costs are fixed regardless of growth?
Energy Returns
What flows back to sustain and grow the organism?
Legacy: Revenue Streams
How does value convert to energy returns? What revenue models fit your dispersal strategy? What is the path to metabolic surplus?
Habitat Design
CX + Service Ops Legacy: CX Strategy / Journey Mapping / Service Operations
A habitat is the full environment in which an organism lives — not just a touchpoint, but the complete sensory, social, and resource landscape. CX design is habitat design. Service ops is the ecology that sustains the habitat day-to-day.
Layer
Approach
Entry
Core Use
Stress Test
Return
What they do
How it feels
Friction points
Backstage
Health signal
Colony Health
Service Operations Legacy: Service Ops / Staff XP / Continuous ImprovementA colony sustains itself through distributed intelligence — no single organism manages the whole. Service ops is the colony's maintenance logic: what keeps every cell healthy and the whole system adaptive?
Staff Ecosystem
Who are the organism's frontline cells?
Legacy: Staff experience / employee journey
What do frontline staff need to do their best work? What invisible labour do they carry? How does the system support them?
Process Metabolism
How does the system maintain its internal rhythms?
Legacy: Process design / standard operating procedures
What processes must run reliably for the service to function? Where do processes currently break down? What should be automated vs. human?
Distress Signals
What does the colony signal when it's under stress?
Legacy: Quality metrics / KPIs / NPS
What signals tell you the service is unhealthy? How quickly do you detect them? What is the response protocol when distress fires?
Adaptive Capacity
How does the system learn and evolve?
Legacy: Continuous improvement / retrospectives / learning loops
How do you incorporate field signals back into the service design? How often do you run retrospectives? What is the cycle from signal to change?
Service Recovery
How does the ecosystem heal after damage?
Legacy: Service recovery / complaints / crisis management
What is the recovery protocol when service fails? How do you restore trust? What does the research on service recovery paradox tell you to do?
Succession Plan
How does the ecosystem mature beyond founders?
Legacy: Scale / sustainability / exit strategy
What must be true for this service to run without its founders? How does it build institutional memory? What does maturity look like?
Phase 10
Commons Return
Where to plant what you've learned
Legacy: Sustainability planning / knowledge commons / ecosystem stewardship
In living ecosystems, organisms don't just consume — they contribute. A forest adds soil. A river shapes its banks. Fungi create networks others inherit. Phase 10 asks: once your service is running, what does it give back to the ecosystem that made it possible? Where can the learning live independently of you?
Three Planting Models
Open Knowledge
What you publish
- Method guides released openly
- Research findings published
- Case studies contributed to field
- Tools built for reuse
- Data returned to community
Carries the pattern forward in form.
Community of Practice
Who you gather
- Peer learning circles for practitioners
- Shared frameworks and vocabulary
- Cohort programs seeded by learning
- Network of practitioners using the model
- Mentorship infrastructure
Carries the pattern forward in people.
Governed Infrastructure
What you hand over
- Service transferred to community ownership
- Cooperative governance model adopted
- Shared platform or protocol maintained collectively
- Commons fund or grant mechanism
- Exit designed as transition, not abandonment
Carries the pattern forward in structure.
Commons Return Questions
Who else could use this model — and what would they need to take it without you?
What knowledge is currently locked inside this project that the field needs?
If you stepped back in two years, what infrastructure would make this self-sustaining?
What community or network should be stewarding this — and are they ready?
What would it mean for this project to succeed so completely that it no longer needs its originators?
How do you design exit as an act of care rather than departure?
Your Commons Plan
Your Summary
No concept set