Requirements Gathering & Process Mapping

Know exactly what to build before anyone commits a budget.

Overview

Most projects do not fail in delivery — they fail in definition. I run structured elicitation across your stakeholders so that scope, rules and dependencies are understood and agreed before a single line of code or a single process change is committed.

Interviews, facilitated workshops, document analysis and job shadowing are translated into requirements everyone can read: business, functional and non-functional, traced end to end.

What you receive

  • Stakeholder map and RACI for decision-making
  • Business Requirements Document (BRD) and functional specification
  • Epics, user stories and acceptance criteria ready for a backlog
  • As-is and to-be process maps in BPMN 2.0
  • Requirements traceability matrix and gap analysis
  • Prioritised scope with MoSCoW ranking and sign-off pack

Outcomes you can expect

  • A single agreed definition of scope that stops mid-project churn
  • Fewer change requests and rework cycles during delivery
  • Developers and vendors quoting against clear, testable requirements
  • Faster stakeholder sign-off with evidence behind every decision

How the engagement runs

  1. 01 — Discover

    Stakeholder mapping, document review and current-state interviews.

  2. 02 — Elicit

    Facilitated workshops, shadowing and structured requirement capture.

  3. 03 — Model

    As-is and to-be process modelling with gaps and risks made explicit.

  4. 04 — Agree

    Prioritisation, walkthroughs and formal sign-off with your sponsors.