The request is not the intent
Separate what someone asked to build from the business reality they want to change.
Start with what needs to change
“Build us a new system.”
That is a proposed answer. It is not the problem.
Modeller helps teams understand the business situation, decide what should change, and model the right intervention. Sometimes that intervention is software. Sometimes it is not.
Runs in your browser at modeller.website. No install, no account.
RequestBuild a new approval system
Observed problemDecisions take 12 days
Desired outcomeDecide within 48 hours
Selected technology interventionSystem Design: document checks
Meaning remains connected from problem and outcome through intervention to System Design
Understand firstTurn a requested fix into an evidence-backed problem
Choose deliberatelyCompare interventions against the outcome
Model what mattersCarry the reason into every detailed model
Before the architecture
A well-modelled system can still solve the wrong problem.
Most change requests arrive with the solution already embedded: automate this, replace that, build a portal. Modeller creates space to understand the situation before the requested implementation becomes inevitable.
Software is one intervention
Let process, people, policy, structure, information, and technology compete honestly.
The reason must survive
Keep every chosen intervention connected to outcomes, evidence, assumptions, and decisions.
One initiative, distinct ways of thinking
From business reality to deliberate change.
Each stage has its own purpose and interaction style. Modeller connects them without collapsing discovery, shaping, and detailed modelling into one oversized canvas.
- 01Business discovery
Discover
Understand the situation
Facilitate the conversation. Capture affected people, current pain, desired outcomes, constraints, assumptions, risks, and open questions.
- 02Problem brief
Frame
Agree what better means
Turn the conversation into durable intent with explicit success measures, non-goals, and evidence.
- 03Initiative shaping
Shape
Compare possible interventions
Explore process, people, organisation, policy, information, technology, experiments, and no action.
- 04Design workspaces
Design
Describe the chosen change
Open the right design step for each selected intervention. A technology intervention continues into System Design, where the team describes actors, capabilities, behaviours, rules, workflows, and lifecycles.
Begin at Discover
Start a Discovery Session in your browser.
Discovery runs at modeller.website. There is nothing to install and no account to create. You need a change request and someone who understands the situation it came from.
Capture the request
Open modeller.website, paste the change request in the words it arrived in, and name yourself and your Domain Expert.
Invite the Domain Expert
Starting the Initiative gives you a shareable link. They see the question waiting for them, not the whole cockpit.
Work through Discover and Frame
Ask, answer, and accept. Each accepted response becomes part of the structured record behind the Initiative.
More than an IT solution
The right response may cross several kinds of change.
Process
Remove friction or change how work flows.
People
Change roles, authority, capacity, or skills.
Policy
Change the rules that shape the outcome.
Technology
Model a system only when technology earns its place.
Example initiative
Reduce customer approval time from twelve days to two.
- ProcessRemove a duplicate approval
- PeopleDelegate low-risk decisions
- TechnologyAutomate document checks
One outcome. Three coordinated interventions. Only the technology intervention continues into System Design.
The technology design step
System Design gives a technology intervention durable meaning.
System Design is one workspace within Modeller. Teams open it when a selected intervention requires technology, and describe the intended system through actors, capabilities, behaviours, workflows, rules, decisions, and lifecycles.
Model the meaning
Describe domains, concepts, relationships, behaviours, and constraints in a form people and tools can understand.
Choose the architecture
Apply an explicit template pack that turns intent into the conventions and boundaries your team has chosen.
Evolve without drift
Regenerate predictable structure as the model changes while keeping owned code clearly separated and safe.
Case studies
See one change travel from a user need to a working model.
Real examples show where Modeller helps today and where the product still needs work. More case studies can join this collection as the public workflows grow.
Child Care
Request more evidence before an ACCS eligibility decision
Follow a case worker need through the lifecycle, rule, validation, diagram, and safe generation workflow.
How System Design works
Design once. Realise it deliberately.
System Design connects the vocabulary of your domain to the structure of your application without hiding the decisions in between.
- 1
Describe
Capture concepts, behaviours, rules, and relationships.
- 2
Shape
Select the architecture and conventions that fit the system.
- 3
Generate
Create navigable software structure with clear ownership boundaries.
- 4
Evolve
Change the model and bring the implementation forward with it.
What teams gain
Alignment that survives the handoff.
- A shared language for product and engineering
- Architecture expressed as reusable decisions
- Consistent projects without copy-and-paste scaffolding
- AI assistance grounded in an explicit model
Model the change
Understand first.
Change deliberately.
Follow Modeller as it grows from intent-first system design into a connected way to understand and shape organisational change.