State the transition, constraints, ownership, and evidence before commitment.
A deliberate alternative to LeSS
Less guessing.
Less guessing.
MoRE clarity.
MoRE turns multi-team product intent into explicit, reviewable work through modelling, readiness contracts, and focused participation.
Prepared refinementStart with written context
Explicit readinessCommit to contracts, not guesses
Reviewed delegatesRepresentation without permanent authority
Fluid executionTeams choose how to collaborate
Why MoRE
Shared understanding does not scale by itself.
Coordination fails when scope lives in conversations, decisions depend on attendance, and implementation starts before teams agree on their seams.
Product Owners and delegates shape work so broader refinement starts from something challengeable.
Keep decisions written and let owners choose their internal workflow.
Fundamental ideas
Document understanding before committing.
MoRE makes important communication durable. Intent, assumptions, boundaries, decisions, and evidence become a shared record instead of context that disappears after a meeting. Defined scope makes outcomes more predictable; that predictability lets people plan realistically and commit to Work Items with confidence.
Computational thinking
Decompose complex outcomes into understandable state transitions with explicit inputs, outputs, constraints, and observable proof.
Black-boxing
Describe what a box must do without prescribing how it works. Complex systems are compositions of smaller boxes, and each composition can itself be treated as a box.
Seams
Make the boundaries where boxes and teams meet explicit. Seams expose dependencies, handoffs, and shared contracts so coordination happens where it matters.
The lifecycle
One Work Item. Three phases.
Each item moves independently. The phases produce three lifecycle states: Candidate, Ready Work Item, and Result.
PO + delegates
Modelling
Turn product intent into a prepared Candidate with boundaries, reasoning, and provisional priority.
StateCandidate
PO + delegates; teams as needed
Readiness
Make the contract strong enough for informed commitment and resolve or explicitly accept challenges.
StateReady Work Item
Owner or owners
Execution
Implement, prove, and deliver through the owners' chosen workflow.
StateResult
Modelling · Readiness · Execution
Scale the clarity, not the meeting.
Use the framework for explanation, the rules for normative requirements, and the practice tools when working on a real boundary.