The Strictlydev Way
Understand before you prescribe.
A brief tells us what a client is asking for. Our job is to understand what outcome the organisation actually needs — and whether the requested intervention is the best route to it.
Systems thinking in practice
We start with the system, not the requested output.
We look at the relationships surrounding a challenge: people, processes, institutions, incentives, technology, information, regulation, resources and dependencies. That wider view often changes what the right solution looks like.
The five stages
Understand. Challenge. Design. Deliver. Improve.
Not every engagement uses the stages in a rigid sequence; complex projects often require iteration.
-
Understand
Define the objective. Map the system. Gather the evidence. Identify constraints, stakeholders and dependencies.
-
Challenge
Test assumptions. Separate symptoms from causes. Compare alternative interventions. Surface risks and trade-offs.
-
Design
Structure the intervention around what is effective, efficient, feasible and sustainable in context.
-
Deliver
Translate the solution into workstreams, ownership, milestones, controls, stakeholder engagement and reporting.
-
Improve
Use performance evidence and implementation learning to adapt the approach and strengthen outcomes.
Worked example
“We need an app.”
An illustration of how the same request can resolve into a different, more useful intervention once the system around it is understood.
| Stage | What we find | What it changes |
|---|---|---|
| Understand | The delay clients complain about sits in approvals and handovers, not in the absence of an application. | The objective becomes cycle time, not software delivery. |
| Challenge | An app over the current process would digitise the queue rather than remove it. | The requested intervention is tested against alternatives. |
| Design | Redesign the process first, then automate the steps that remain, with clear ownership at each decision point. | Process redesign + targeted technology + change management. |
| Deliver | Sequence the work so process change and system build land together rather than months apart. | One coordinated programme with visible dependencies. |
| Improve | Measure the cycle time the client originally cared about and adjust where the evidence points. | Performance is judged on the outcome, not the deliverable. |
Technology-enabled by design
Useful, but never a substitute for understanding.
We use technology where it can improve speed, accuracy, transparency, collaboration or decision-making — but never as a substitute for understanding the problem.
What this means for clients
Expect to be asked difficult questions.
You should expect us to make the reasoning behind recommendations visible, and to remain focused on implementation rather than ending at the presentation deck.
Advise with delivery in mind. Deliver with the original outcome in view.
Engagement
Start with the problem.
Tell us the outcome you need and we will begin by understanding it.