Skip to content

Discovery, business analysis and solution design

Bring us the problem before you have a specification.

Most projects that go wrong were defined too early. You do not need a requirements document to start a conversation with Blacklight. Our business analysts work with your teams to understand the problem, the people, the processes and the systems involved, then help you decide what to configure, integrate, buy, develop or leave alone.

What this work covers

Proportionate to the size of the decision. A focused review can take days. A multi-system programme needs more.

Discovery

Workshops and conversations with the people who do the work, not only the people who sign it off. You get a clear statement of the problem, the processes involved, the systems that touch it and the outcomes that would count as success.

Requirements and priorities

Requirements written in plain language, prioritised with you, with constraints and acceptance criteria attached. Everyone can see what is in scope, what is not, and how "done" will be judged.

Options appraisal

An honest comparison of the realistic routes: configure what you already own, integrate it with something else, buy a product, develop a bespoke component, or improve the current system in phases. Each option comes with its trade-offs, risks and rough cost shape, so the business case rests on facts.

Solution design

An agreed design for architecture, user experience, data, security and integration. It names the systems of record, how data moves between them, who can see what, and what has to be true before go-live.

Why the analysis and the delivery sit in one team

A design handed from one company to another loses detail at every step. At Blacklight, the analysts who run discovery work beside the developers and delivery managers who will implement the result. Questions about feasibility get answered in the room, not weeks later.

It also keeps the advice honest. Blacklight delivers Dynamics 365, Microsoft 365, Power Platform and bespoke .NET software, so no single product needs to win. Sometimes the right answer is to configure what you already pay for. Sometimes it is a small integration. Sometimes it is to do nothing yet.

Discovery does not commit you to a build with Blacklight. You keep the findings and the design.

Evidence

Sulzer: understanding the audit requirement before writing code

  1. Problem

    Sulzer's engineering teams shared technical data across countries in spreadsheets. Their accreditation required version control and an audit trail that spreadsheets could not give.

  2. Analysis

    Blacklight worked with Sulzer to understand the full scope of its data management and auditing requirements before any development started.

  3. Result

    OED, one central .NET system covering 88 engineering sheet types, with role-based access, automatic unit conversion and a release process that holds the audit trail.

Proveca: scoped to what the study needed

  1. Problem

    Proveca needed data capture for a clinical study. The off-the-shelf clinical trial products it assessed were designed for much larger trials and cost too much for the requirement.

  2. Decision

    A bespoke .NET portal on Azure, scoped to the study, with role-based access aligned to Good Clinical Practice requirements.

  3. Result

    A clean data-entry portal for investigators, with reporting built in and an admin interface Proveca runs itself.

Where this fits in the delivery

Discovery, requirements, options and design are the first four stages of the Blacklight delivery approach. Each one ends with something you can read and a decision you can make.

See how we deliver →

Frequently asked questions

We do not have a specification. Is that a problem?

No. A clear description of the problem is enough to start. Writing the specification with you is part of the work.

Do we have to use Blacklight for the build afterwards?

No. You own the discovery findings and the design. Most clients continue with the same team because the knowledge is already there, but the choice is yours.

How long does discovery take?

It depends on the size of the decision. A focused review of one process is short. A programme that touches several systems and departments needs more time. The scope and cost of discovery are agreed before it starts.

Talk to us

Tell us what is not working.

Describe the problem in your own words. You will get a straight view of the options and what a sensible first step looks like.

Get in contact