Most requirements begin with evidence: something a stakeholder said in a meeting, workshop or interview, or something captured in a document.
The challenge is not simply turning that material into a requirement. It is preserving the connection between what was said, what was interpreted, what still needs clarification and what was ultimately approved.
FLOW is Antozoe's five-stage methodology for carrying that evidence through analysis and into governed delivery artefacts: Find, Locate, Optimise, Write and Deliver.
Find: capture the evidence
FLOW begins with the source material itself — such as a meeting transcript, workshop record, interview notes or another stakeholder-produced document.
Rather than beginning with a rewritten summary of the conversation, Antozoe works from the underlying evidence and preserves its source context.
For transcripts, that means keeping the source transcript connected to what is subsequently identified from it.
The distinction matters. Once the original evidence and the analyst's interpretation become indistinguishable, traceability becomes much harder to maintain.
Locate: identify what matters
The next stage surfaces the information within that evidence that may matter to the engagement.
Candidate requirements, decisions, business rules, risks and unresolved questions can be identified and connected to their supporting source material.
The purpose is not to treat everything said in a workshop as a requirement. It is to establish an evidence-backed working set that a Business Analyst can examine, refine and challenge.
That gives the analyst something more useful than a generated document: a structured view of what the stakeholders actually contributed and where each item originated.
Optimise: work through gaps and conflict
Requirements work rarely becomes complete simply because the transcript has been analysed.
Stakeholders may describe the same process differently. Important conditions may remain unstated. A proposed requirement may be clear in intent but incomplete in detail.
FLOW keeps those gaps visible.
Where source material appears to conflict, the issue is surfaced for human review rather than silently resolved on the stakeholder's behalf.
This is also where Industry Benchmark Intelligence can provide additional context. When sourced benchmark material has been added for the relevant industry, it can be surfaced alongside the analysis. When no sourced benchmark is available, Antozoe does not manufacture a substitute.
An empty benchmark state is more useful than a confident-looking figure with no defensible provenance.
Write: turn reviewed evidence into governed artefacts
Once the evidence has been located and the important gaps have been considered, the analysis can be shaped into structured delivery artefacts.
Depending on the engagement, that can include requirements, user stories, business rules and process maps.
The important distinction is that the artefact does not have to become detached from the evidence that produced it.
Its source relationship remains available for review, while requirement attributes such as priority, clarity and approval state give the BA additional governance around how the artefact progresses.
A clarity score should be treated as a review signal rather than a substitute for professional judgment. Approval remains a separate human decision.
Deliver: curate the approved package
The final FLOW stage brings the reviewed and approved artefacts together into a governed delivery package.
The goal is not merely to export another requirements document.
It is to give stakeholders and delivery teams a coherent body of work in which the important decisions, artefacts and supporting evidence remain connected.
That makes later questions easier to answer because the reasoning does not have to be reconstructed from scattered meeting notes.
Why the order matters
FLOW deliberately separates evidence capture, interpretation, refinement, authoring and delivery.
Find comes before Locate because evidence should exist before conclusions are drawn from it.
Locate comes before Optimise because gaps and disagreements can only be examined once the relevant information has been identified.
Optimise comes before Write because uncertainty should remain visible long enough for a human to address it.
And Write comes before Deliver because generated artefacts should not become client-ready simply because they exist.
The sequence creates a chain from stakeholder evidence to governed output.
That chain is what allows a requirement to answer one of the simplest — and sometimes most difficult — questions in requirements work:
Where did this come from?
Antozoe is designed to keep that answer attached to the work. Source-linked artefacts retain their supporting evidence within the project record. Manually edited artefacts are protected from silent replacement by later analysis runs. Newly generated alternatives do not become the current version simply because another analysis has been performed; the BA remains responsible for selecting what progresses.
That is the difference between producing requirements and governing how those requirements came to exist.