What it is
Business analysis is the work of understanding what a business needs, turning that into clear requirements, and making sure the solution (whether a system, a process, or both) actually delivers it. It is the layer of work that sits between "we want to do X" and "here is how the system should work."
Process design is the companion to that: mapping how work actually flows, identifying where it breaks down, and designing the to-be state that a new system or way of working will support.
When you need it
You need it when you are implementing a new system and need to make sure what gets built is what you actually need. You need it when a current process is not working and you cannot pinpoint why. You need it when different teams have different ideas about how a process works and nobody has mapped it.
What we deliver
- As-is process documentation
- To-be process design
- Requirements gathering and documentation
- Gap and root-cause analysis
- User stories and acceptance criteria
- Process maps (swimlane and flow)
- Data and system requirements
- Prioritised improvement backlog
How it connects
Business analysis feeds directly into CRM implementation (the requirements that drive the configuration), change management (you need to understand what is changing before managing the change), and project management (the scope that determines what gets built and what gets deferred).