See what every product team is working on

As a product leader, the hardest question to answer well is also the most basic: what is each of my teams actually working on right now? Status meetings are a tax on the teams and still hand you a curated version. Slack threads scroll away. By the time it reaches you, the discovery work — the part that decides whether you're building the right thing — has usually been flattened into "on track."

There's a better source: the tree itself.

Discovery already records itself

If your teams run continuous discovery, each team's thinking lives in an Opportunity Solution Tree — an outcome at the top, opportunities from customer research, the solutions they're trying, and the assumptions they're testing. Every change to that tree is recorded, with who made it and when.

So you don't need a team to write you an update. You can ask an AI assistant to read the week's changes and write it for you.

What that looks like

Connect Claude (or any MCP client) to Outcomify and ask:

"Summarize the most important changes in our activation tree over the last week. I'm the CPO and want to know what the team is doing."

A few seconds later you get something like this:

This week: 9 new nodes, 11 status changes, nothing deleted — most of it landed as Completed. A productive week; the headline is that the self-serve onboarding bet shipped.

🚀 Shipped

• The "guided setup" solution closed out, along with its three assumptions — two validated, one invalidated (managers didn't want the video walkthrough).
• "Start from a sample schedule" moved to Completed.

🛠 In progress

• "Publish reminders" moved Proposed → In Progress.

🆕 Newly surfaced

• A new opportunity cluster around shift swaps — staff want to trade shifts without manager back-and-forth. Three opportunities, all Proposed. The freshest signal of where the product goes next.

🗑 Consciously dropped

• "In-app tutorial" was Archived — deliberately deprioritized, not forgotten.

Bottom line: the team shipped its onboarding bet and validated most of it; the un-started shift swaps cluster is the likely next focus.

That's not a vibe — it's the actual change history of the tree, with attribution, turned into prose. (The example above is illustrative; yours reflects your real tree.)

Why it beats a status meeting

• No prep tax. Teams don't stop to assemble an update — the update is a by-product of doing the work.
• It surfaces what changed, including what was dropped. A status update tells you what someone chose to mention; the tree tells you what's new, validated, invalidated, and deprioritized. That "consciously dropped" line is often the most useful one on the page.
• It's on demand and asynchronous. Ask before a board meeting, a 1:1, or on Monday morning — no calendar required.
• It points at decisions. A good summary ends on the thing that needs you: the un-started cluster, the invalidated assumption, the outcome that stalled.

It scales to many teams

This is where it earns its keep. Keeping up with one team is easy; keeping up with eight is not. Because every team's discovery is a tree, the same prompt works per team — or you can ask for a cross-team rollup: "across all of our trees, what were the biggest changes, and which outcomes stalled this week?" You get a portfolio view without eight status meetings, and you can still drop into any one team's tree for the detail.

How to set it up

The summary runs through Outcomify's MCP server, so it works in Claude Code, Claude Desktop, or Cursor — and read-only access is enough. The MCP setup guide walks through connecting it in about two minutes.

After that, it's one prompt whenever you want to know what your teams are really working on.

Start a free trial and connect your assistant — your next status update can write itself.