Business Analysis & Improvement
Sometimes the solution you ask for isn’t the problem you need to solve. Prelude helps organisations understand the current state, define what needs to change, test assumptions and make better decisions before committing time and money to a solution.
Start with the problem
A request is not a requirement.
Most projects start with a request. Good decisions come from working down the chain before choosing a solution, so that what gets built or bought addresses the cause rather than the symptom.
- RequestWhat someone has asked for: a course, a website, a system, a new feature.
- ProblemWhat is actually not working, and for whom.
- EvidenceWhat we can observe or verify about the problem.
- CauseWhy the problem is happening, rather than how it shows up.
- RequirementWhat any solution must achieve to address the cause.
- SolutionThe option that meets the requirement best, at a cost that makes sense.
What Prelude can help with
Practical business analysis, without the jargon.
- Business problem definition
- Current-state and future-state analysis
- Stakeholder analysis
- Requirements elicitation
- Process mapping
- Root-cause analysis
- Proposition analysis
- Product and service review
- UX/UI review
- Accessibility review
- Operating-model analysis
- System requirements
- Options appraisal
- Procurement and business cases
- Market and competitor analysis
- Implementation roadmaps
- Benefits and measures
- Decision support
Accessibility and UX reviews are expert assessments against recognised principles, not formal certification. Prelude does not provide legal, financial or cybersecurity advice; where a decision needs it, we will say so.
From assumption to evidence
Every finding is labelled for what it is.
Prelude reports separate what is known from what is concluded and what is still to be tested. Decision-makers can see how much weight each finding will bear.
- Evidence
- Directly observable or supported.
- Inference
- A reasonable conclusion drawn from evidence.
- Assumption
- Something not yet proven.
- Recommendation
- What should happen next.
Not every solution survives the analysis
The request changed once the problem was understood.
Two recent pieces of work where the deeper question turned out to be more valuable than the original brief.
Anonymised example from recent consultancy work
Owner-led service business
- Initial request
- Improve the digital presence and generate more enquiries.
- What the analysis revealed
- The more important question was what would happen if demand actually increased. The binding constraints were owner dependency, pricing, systems, operating capacity, delegation and quality control.
- Work expanded into
- Business and growth strategy · operating model · systems requirements and options analysis · processes and policies · workforce structure and quality · implementation planning
Anonymised example from recent consultancy work
Digital platform / start-up
- Initial request
- An independent product and UX review.
- What the analysis revealed
- The product had progressed further than some of the proposition and behavioural assumptions underneath it.
- Work examined
- Proposition · users · business model · user journeys and UX/UI · trust · accessibility risks · requirements · evidence and assumptions · measures · priorities · launch readiness
- Outcome of the review
- A narrower, evidence-led route forward: prove the core proposition before investing in further breadth. The recommendation was not simply “build more”.
These examples are shared without client names, sector detail or commercial figures. Full case studies will be published only with the client’s permission.
Have a problem but not sure what the solution is?
Discuss it with Prelude. The first conversation is about the problem, not a pitch.