Consulting

Business analysis

We establish what must change, for whom, and how the result will be accepted.

Most technology problems are decided before anything is built. We run discovery, write the requirements and define acceptance, so the business, the vendor and the build agree on one thing.

Ink drawing of a ruled ledger on cream paper, with a row of tick marks and filled squares down the first column

What this covers

  • Discovery and problem framing
  • Current-state and future-state process
  • Requirements and acceptance criteria
  • System selection and vendor evaluation
  • Integration analysis and data flows
  • User acceptance testing

Typical engagements

  • Discovery before a business case
  • Requirements and acceptance for a system selection
  • Integration analysis between two systems
  • Acceptance testing lead for a release

How an engagement runs

  1. 01

    Enquiry

    You describe what has to change. We reply in writing with questions.

  2. 02

    Scoping

    One conversation to agree the problem, the people affected and how the result will be accepted.

  3. 03

    Proposal

    A written scope, acceptance criteria, a price and a start date.

  4. 04

    Delivery

    We lead the work. Decisions, risks and changes are recorded as they happen.

  5. 05

    Acceptance

    The result is checked against the criteria agreed at the start.

  6. 06

    Handover

    Documents, access and records pass to your organisation.

  7. 07

    Close

    A short written close-out, and a support retainer if you want one.

Who this suits

  • Organisations about to select, replace or integrate a system, and that need the requirement written before the contract is signed.

  • Programs already under way where the business and the delivery team describe the same change differently.

Typical platforms: Microsoft Dynamics 365, Microsoft 365, Workday, ServiceNow and Azure DevOps.

Tell us what has to change.

Contact