Back to home

Discovery

Business Analyst

Process before technology.

I scope from the very first contact with the client, gather needs, identify where value is being lost and estimate the effort.

Methods: stakeholder interviews, user stories and acceptance criteria, use cases, BPMN, wireframes, functional specifications.

Pipeline stagesDiscovery

Discovery: from first contact to proposal

These are the practices I use today. They are not a rigid process: I adjust them to each client, each project and what is already known about the process in question.

  1. Client The client presents a need or an idea.

  2. Me I follow up on the contact and capture the client’s idea.

  3. Me I work out what the client needs, what kind of development could help and what needs lie behind the request.

  4. Me I identify whether it is possible and form a macro view of how to execute it.

  5. Team I run validations with the team and explore different strategies and approaches.

  6. Me I consolidate the approaches into proposals, working out where there is value for the client and estimating the effort.

  7. Me

  8. YesTeam When the project or product calls for it, the proposal can proceed as a PoC for the client, or even an internal one, if there is no direct experience of the process yet. I then do R&D with the team: I work out what the technologies make possible, the type of delivery (cloud or on-premises), the requirements needed, the estimates and the costs.

    See how I evaluate and build
  9. NoMe When the proposal goes ahead as a project, I move on to management and organisation: kick-off, requirements, tender specification and deliveries.

    See how I run projects

Who does it: Me

Follow-up

I follow up on the contact and capture the client’s idea.

Facts and sectors

  • +6sectors

Among them

  • Healthcare
  • Industry
  • Banking
  • Legal
  • Social
  • Design

Skills map

Pick a skill to see where I have used it and what sits close to it.Only what belongs to this area appears here.

Business AnalysisProject Management andDeliveryStrategy, Adoption andComplianceTools

Business Analysis

Project Management and Delivery

Strategy, Adoption and Compliance

Tools

Perspectives

  • AI without process is just a new cost.

    Many companies are focused on implementing AI and pay little attention to understanding the process they want to improve. Without a diagnosis, AI adds costs instead of value.

  • The value is in the diagnosis, not the implementation.

    Understanding where value is being lost, and whether AI is really the answer, is worth more than the technology you choose.

  • Before automating a process, it is worth asking whether it should exist at all.

Shall we talk?

LinkedIn is the best place to find me.

Talk on LinkedIn (opens in a new tab)

Ask me

Answers written by me, not generated by AI.

Pick a question. The answers are mine.

Would you rather ask your agent? Connect it to me

No results.

Arrow keys to move, Enter to open, Esc to close.