Skip to main content
Advisor does many things, but its most important job in Define is strategic, cross-process analysis — reasoning across your entire Work Brain to tell you where your biggest opportunities are, what to do about them, and in what order. This page is about that big-picture use: what it can do, what you need, and how to approach it.
For the step-by-step of running an Insights analysis, see Advisor: analyze processes. For ready-made prompts to start from, see the Advisor prompt library. This page focuses on the thinking — what’s possible and how to aim it.

​
What strategic analysis with Advisor means

Most tools analyze one process at a time. Advisor analyzes across them. Because your Work Brain (the Process Index) holds how work actually happens, Advisor can reason over an entire value stream or value chain at once, comparing processes and the observations within them to find patterns no single-process view would reveal. This works at any scale. Whether you point it at 5 processes, 50, 500, or 1,000+, the approach is the same — Advisor reads the relevant slice of your index and reasons over all of it together.

​
What it can produce

Pointed at a value stream or set of processes, Advisor can:
  • Find your biggest areas of opportunity — where time, cost, risk, or friction concentrate across many processes.
  • Tell you where to start — prioritized, not just a flat list of findings.
  • Compare across processes and observations — surfacing inconsistencies, duplicated effort, and best practices worth standardizing.
  • Tell you where to deploy agents first — ranked against the evidence, with the non-agent alternative named for each.
  • Generate future-state designs — what the improved process or value stream could look like.
  • Build the project plan — turning recommendations into a sequenced roadmap you can act on.
The headline: analysis that used to take a consulting team two-plus weeks — a transformation roadmap across a value stream — Advisor can produce in about two minutes.

​
The one prerequisite

Strategic analysis is only as good as the index behind it. The single requirement is that your Work Brain — your Process Index — is in place and populated. Once it is, the only real limit is your imagination for the kinds of big-picture questions you ask. That’s why Discover matters so much: capture, and a clean, well-structured Work Brain, are what make this stage possible. If your analysis feels thin, it’s usually a sign there’s more to capture first.

​
How to approach it

  1. Start from a question, not a feature. The best analyses begin with a real strategic objective — “where can we take 20% of cost out of Procure-to-Pay?” — not “let me run Advisor.” Frame the outcome you want.
  2. Scope to the value stream or process set that question touches, then let Advisor reason across all of it.
  3. Treat the report as a conversation. Advisor’s output is a starting point — ask it to explain its evidence, drill into a finding, or take the next step (e.g., draft the solution set, the future-state design or the project plan).
  4. Iterate. Refine scope and questions as findings sharpen your thinking.
For concrete prompts to get going by role and objective, see the Advisor prompt library.

​
From analysis to a solution set

Strategic analysis tells you where the gap sits and why. The next step is choosing the mix of changes that closes it, from removing and reengineering work to automation and system and organizational change, with an owner for each. See Define your solution set.

​
Where to go next

Advisor: analyze processes

How to run an Insights analysis, step by step.

Advisor prompt library

Ready-to-use prompts by persona and use case.

Define your solution set

Choose the mix of changes that closes the gap.

Using the Within MCP

Connect Within to your own AI client, and how it compares to Advisor.
Need help? Use the in-app chat — click the chat bubble in the bottom-right corner of Within (staffed 24×5) — or email support@within.ai.