LimiceliaPORTAL Practice
Home Field Guides Studio Admin Advisor Circle
Practice · Studio

Service Studio.

Studio is where the practice designs, tests, and prices its services — using a Living Systems Design framework drawn from biomimicry: the idea that nature has been solving complex adaptive problems for 3.8 billion years, and that a consultancy practice can borrow its logic to build services that are genuinely resilient.

The Philosophy

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.

The SDG phases (Ecology through Commons Return) aren't a checklist. They're a posture: the practitioner as 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.

Two Tracks
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.
References
Drawn from biomimicry (Janine Benyus), service design (This is Service Design Doing), and complexity theory (Donella Meadows). See the library below.
The Eight Phases — hover for artifacts
Artifacts
Problem Ecology canvas Stakeholder map Power/interest grid
e.g. "A health authority sits at the centre, but the people who experience care most acutely have no voice in redesign."
01 · Ecology
Who is the ecosystem?
Map the actors, tensions, and conditions that make this problem possible. Who is affected? Who holds power? What pressures are building?
Artifacts
Field notes I-notice statements Interview transcripts
e.g. "I notice every manager describes the same meeting differently — the hierarchy is invisible to itself."
02 · Observation
What did you witness?
Field evidence — interviews, moments, surprises. What did you hear that challenged assumptions? A naturalist fills the notebook before drawing conclusions.
Artifacts
Affinity clusters Named tensions Recurring dynamics map
e.g. "Who controls data controls story" — not just a topic, but the structural tension underneath four different client situations.
03 · Pattern
What repeats?
Across clients, sectors — what structural dynamics keep appearing? Name patterns as tensions, not topics. Nature repeats spirals, networks, feedback loops.
Artifacts
Insight statements HMW questions POV madlib
e.g. "Community leaders need to be decision-makers, not just informants, because trust is built by sharing power, not by sharing information."
04 · Insight
The reframe.
A single non-obvious sentence that changes the frame. Good insight makes people say "I've always felt that but never said it." Format: [Who] needs [what] because [unexpected truth].
Artifacts
Service brief Scope narrative Delivery model sketch
e.g. A 12-week org memory sprint: structured knowledge harvest, then co-designed field guide for the team's own use.
05 · Concept
What is the service?
Name it, scope it, describe who it is for and how it is delivered. This is the offering — what a client actually buys.
Artifacts
Day-rate model Sector modifier table Complexity score
e.g. 18 days base, 1.2x complexity mod for multi-org conflict, 0.85x non-profit sector — range shown to client with floor/ceiling.
06 · Pricing
What does it cost?
Day-rate model with sector and complexity modifiers. Transparent to the client, sustainable for the practice. Value estimation, not time-selling.
Artifacts
Bet hypothesis Signal definition Risk register
e.g. "We bet that mid-level managers — not executives — are the real leverage point. Signal: facilitation requests increase from this cohort within 60 days."
07 · Bet
What has to be true?
State the hypothesis. What would prove this service works — or doesn't? What signal are you watching for? Evolution runs billions of experiments; we run one at a time.
Artifacts
Case study Field guide Open-source toolkit
e.g. An anonymised org memory framework from a client engagement, adapted into a public field guide in the Limicelia commons.
08 · Commons Return
What goes back to the field?
Every engagement creates knowledge. What can be anonymised and returned? The endpoint of good design is ecosystem enrichment, not market capture.
Six Core Principles
Principle 01
Observe before you interpret
Equivalent: 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
Equivalent: synthesis / affinity mapping
Nature repeats solutions that work: spirals, networks, edge effects, feedback loops. Find the recurring form — that is the design brief hiding inside the data.
Principle 03
Emulate what evolution already solved
Equivalent: insight synthesis / HMW 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
Equivalent: prototyping / MVP / pilots
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
Equivalent: service ops / CX strategy / business design
A service is not a product. It is a relationship between an organism and its habitat. The business model, CX, and operational infrastructure are all part of the same living system.
Principle 06
Return to the commons — plant where it can keep growing
Equivalent: 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.
Service Design Library
This Is Service Design Doing
Stickdorn, Hormess, Lawrence, Schneider — 2018
The practitioner's bible. Methods, tools, and facilitation moves across the full service design lifecycle. Dense and hands-on.
Open site ↗
Biomimicry: Innovation Inspired by Nature
Janine Benyus — 1997
The founding text. Benyus argues that nature is our best model, measure, and mentor — 3.8 billion years of R&D, available for free.
Open site ↗
Thinking in Systems
Donella Meadows — 2008
How feedback loops, delays, and system structure produce emergent behaviour. Essential for understanding why linear interventions fail in complex organisations.
Open site ↗
Service Design Tools
Roberta Tassi — online resource
Open-source library of service design methods with descriptions and examples. Good for finding the right tool for a specific phase of work.
Open site ↗
Design Justice
Sasha Costanza-Chock — 2020
Who gets to design? Who is designed for? Essential reading for community-centred practice — rethinks participation, power, and the politics of the design process.
Open MIT Press ↗
Field Guide to Human-Centred Design
IDEO.org — 2015
Free, practical. 57 methods for community-centred work. Particularly strong on inspiration-phase field research and participatory ideation.
Open site ↗
Value Proposition Design
Osterwalder, Pigneur et al — 2014
The canvas model for designing services around jobs, pains, and gains. Most useful in the Concept phase when translating insight into a clear offering.
Open site ↗
Liberating Structures
Lipmanowicz & McCandless — online
33 facilitation microstructures for including everyone and generating distributed intelligence. The accompanist's toolkit for group work across every phase.
Open site ↗
Practice Tool
Service Design Gym
An interactive workspace for running the Living Systems framework on any challenge — from field notes through to How Might We questions, service concepts, and Bets. Built for solo sprints and team sessions.
Open Gym ↗
Create
Design a new service
Start from scratch, intake a past engagement, or remix two existing services into something new.
Recently touched
Where you left off
Loading…
All services
What the practice offers
Loading services…

Start from a blank canvas, intake a past engagement, or remix two existing services into something new.

Draft unsaved
01

Ecology

Who lives the problem? What enabling conditions matter? What signal shows that change is wanted?

Empty
02

Observation

What sources, past client evidence, and field notes ground this?

Empty
Drop PDF / txt or click to upload
03

Pattern

What's the recurring tension across the evidence? Name the dynamic.

Empty
04

Insight

What's the core insight? What might-we question? Nature analogue?

Empty
05

Concept

Service name. Domain tags. Delivery type. Who it's for.

Empty
Translation layers
L1 — What gets commissioned The thing they pay for. One sentence max.
L2 — What actually changes The real outcome beneath the deliverable.
L3 — Why it matters The deeper organizational or social stake.
06

Pricing

Days per team member, sector modifier, complexity. Calculates live.

Empty
07

Bet

What's the falsifiable hypothesis? What signal says this worked?

Empty
08

Commons return

What do we give back to the field from this work?

Empty
Generated page + media plan
Click Generate to create page copy, media plan, and operational brief from your canvas.
Production readiness

Start a new canvas

Give it a working name — you can change it any time.