Business analysis
Turning a business need into clear requirements, aligned decisions and concrete solutions.
- From scoping to implementation
- Bridging business, IT and management
- Specifications, user stories, tests
Sound familiar?
- The business expectations are there, but vague or spread across several people.
- The need is poorly translated for the technical team/ IT.
- Testing comes too late to correct course without affecting the timeline or budget.
- Several projects run in parallel, without an overall view for management.
What I bring
- Clear requirements, understood the same way by the business, IT and management.
- A defined scope, a monitored schedule and documented decisions.
- Acceptance testing led through to go-live and adoption.
- On a larger project, practical governance and closely managed providers.
How I work
-
Understand the need
I start from the business context and everyone's expectations, before moving into functional analysis.
-
Turn it into requirements
I translate the needs into clear requirements, shared by the business, IT and management.
Functional specifications, user stories -
Scope and follow up
I define the scope, monitor the schedule and document decisions.
Scope, schedule, documented decisions -
Test and support
I lead acceptance testing and support validation through to go-live and adoption.
Test scenarios, acceptance testing
Aligning CRM processes across several independent organisations
Within an organisation made up of several independent entities, each with its own way of working, I coordinated the harmonisation of processes around one shared system.
The work involved listening to each team, documenting the real needs behind the requests being made and building a set of requirements accepted by all three parties.
A fuzzy process? Start by describing it.
The Process Scan walks you through one concrete process: who is involved, which information, which rules, where it gets stuck. In a few minutes, it shows whether you should rather simplify → automate → augment with AI or simply change nothing for now.
5 minutes · Free · No commitment
In detail
Context
Your organisation is starting a digital or CRM project. The business expectations are there, but they remain vague, spread across several people, or poorly translated for IT.
The result can be an incomplete set of requirements, a build that does not address the real need, or testing that comes too late to make corrections without affecting the timeline or budget.
When several projects are moving forward at the same time, the challenge changes. Each project has its own deadlines, dependencies and resource needs. Without a clear project governance structure, decisions are made case by case and management loses the overall view of actual progress.
My role
I translate your business needs into clear requirements. I write functional specifications, user stories and test scenarios. I bridge the gap between the business, IT and management, making sure everyone shares the same understanding of the need, priorities and decisions to be made.
I also structure project follow-up. I define the scope, monitor the schedule and document decisions. I lead acceptance testing and support validation through to go-live and adoption by the teams.
On a larger project, I put practical governance in place: regular steering committees, a shared reporting format and clear escalation paths for decisions that go beyond the operational level. I also manage external providers, with rigorous contract follow-up and quality control of deliverables.
My background in marketing and digital environments helps me understand the business context of a project quickly, before moving into functional analysis.
Are your business needs still unclear, or is a project moving forward without a clear framework?
Describe the context: together we will identify what is blocking progress and what the possible next steps are.