Designing systems people actually use
How services, incentives and interfaces work together. A service can look simple on a screen and still be difficult to use in real life. People experience the whole system: the rules, hand-offs, information, technology, staff behaviour and recovery paths around the interface. Systems-oriented design makes those connections visible before teams commit to a solution.
Why it matters
Complex problems are rarely contained within a single product or department. A change in one place can create friction elsewhere. Research therefore maps actors, flows, rules, incentives and feedback, then tests where a small intervention may improve the overall experience without shifting costs or risks to someone else. Better questions help teams separate visible symptoms from the conditions that create them—and choose evidence that can support a real decision.
How do we design the complete system around a real human need—not just one touchpoint?
See the whole system before changing a part
A conceptual framework created by Redisry to organise the question and decide what evidence to gather next. It is not a predictive model.
What we look at.
These lenses help turn a broad topic into a tractable investigation. The right mix depends on the audience, setting, sector and decision at hand.
End-to-end journey
What does a person need to do across channels, teams and time—not just within one interface?
Dependencies & hand-offs
Where does information, responsibility or context get lost between actors or systems?
Incentives & governance
Which rules and measures shape behaviour, and who can change them?
Feedback & resilience
How does the system detect failure, learn and recover when conditions change?
From observation to useful evidence.
Methods are selected for the question—not used as a checklist. Secondary research can be combined with interviews, observation, data review and small experiments where appropriate.
Frame the system boundary
Agree what is in scope, who is affected and which outcomes matter.
Map actors and flows
Visualise users, teams, policies, data, resources, hand-offs and dependencies.
Find leverage points
Identify causes and constraints rather than treating every symptom as a separate problem.
Prototype and learn
Test changes with affected people, monitor side effects and adapt based on evidence.
What might tell us to look closer?
Signals are prompts for investigation, not proof. Check each against context and evidence.
- A local improvement creates a new problem for another team or user group.
- People must repeat information because systems do not share context.
- The formal process differs from how work is actually completed.
- Success is measured at one step while end-to-end outcomes remain poor.
Make the research useful.
Research can help clarify the problem, expose assumptions, compare options and identify a practical next step.
- Service design and digital transformation
- Cross-functional operating processes
- Public and social service delivery
- Product ecosystems and platform design
- Policy, process and organisational change
Start with credible sources.
Selected reports and frameworks from established organisations. They are starting points, not an endorsement of every conclusion. Check each source's scope, method and date.
Have a question worth taking to market?
Have a complex product, service or process challenge? Redisry can help frame the system, surface evidence gaps and identify a sensible next step toward market. When the next step is validating demand, reaching the right audience or planning a launch, explore a structured Go-to-Market approach.