Strategic analysis with Advisor

Advisor does many things, but its most powerful use is strategic, cross-process analysis — reasoning across your entire Process Index 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.

​

What strategic analysis with Advisor means

Most tools analyze one process at a time. Advisor analyzes across them. Because your Process Index holds how work actually happens — your organization’s “company brain” — 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.
• 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 company 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 capture (Discover) and a clean, well-structured index (Structure) matter so much: they’re 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 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.

​

Where to go next