87 live methods
One shared registry powers the full library rather than a scattered set of disconnected pages or prompts.
The platform does not treat methods as isolated templates. Each method uses system-fed project context, pulls from the evidence already in play, and contributes back to the reasoning the team will rely on later.
One shared registry powers the full library rather than a scattered set of disconnected pages or prompts.
Methods surface according to evidence strength, project context, and whether the team is actually ready to run them.
Each method is grounded in the active project rather than reusing filler or hardcoded category assumptions.
Outputs feed the wider strategy system so findings do not get stranded in one-off readouts.
Inside Flowlytics, research methods are grouped by how useful they are right now for the active project. That keeps the library usable instead of forcing teams to sort through a long flat list every time they need to move forward.
The system pushes the highest-value options forward when the project already has enough signal to support a worthwhile run.
These methods still add value, but they sit behind the strongest next steps until the immediate gaps have been handled first.
The platform keeps them available without pretending they deserve equal attention in the current decision frame.
If discovery is incomplete or the evidence base is too thin, the method stays visible but clearly positioned as premature.
Flowlytics is not limited to one kind of research. The registry spans discovery, synthesis, framing, messaging, prototyping, optimisation, and the support work needed to make the final recommendation defensible.
Shape the decision itself before teams jump into execution.
Turn scattered findings into usable logic that can support a recommendation.
Build the market, competitor, and audience picture before assumptions start hardening.
Track what is moving, what is underperforming, and where the product experience is leaking value.
Push direction forward without losing the evidence that should be shaping the ideas.
Support the wider system with deeper coverage across messaging, design, and user understanding.
In Flowlytics, method outputs are meant to stay connected to the wider project logic. That means discovery context, active evidence, method reports, and the eventual recommendation all reinforce one another instead of breaking apart across different tools and meetings.
Methods use the current project frame and available evidence instead of asking the team to start from a blank prompt every time.
A strong result is project-specific, evidence-backed, and able to stand up without leaking into generic filler or recycled assumptions.
The library supports a final direction that can still be inspected later because the logic and proof remain connected.
The method library only works if the evidence, reasoning, and final direction still hold together when a real product decision needs to be made.