For product managers
“Why did we decide it this way?”
You know the answer. It is in a call from March, a thread nobody saved, and your own memory. SecondBrain 365 is an AI agent inside your Microsoft 365: invite it to the call, add it to the thread, and it writes the decision down as you take it — so the reason is still attached to the feature a year later.
See how SecondBrain 365 supports product managers, from the refinement call to the question nobody can answer a year later.
The decision gets made twice
Six months on, somebody asks why the import caps at 5,000 rows. Nobody remembers it was a timeout in testing, so the cap gets questioned again — and this time it is decided by people who do not know what the first decision knew.
64%
of teams keep critical knowledge “primarily in people's heads”, and only one in five use a standard format to document decisions.
refactoring.fm, State of Product Development 2026 — n=340
60%
of product professionals say unplanned work disrupts their schedule frequently. Only a quarter spend most of their time on strategic work.
Product Focus 2026 — n=677, 83% Europe
27%
of engineers say that when they read a ticket, both the problem and what “done” means are clear.
refactoring.fm, State of Product Development 2026
You keep owning the product. What you stop owning is being the only place the reasoning is stored.
The feature page
The reason travels with the feature
Every decision keeps the date it was taken, the call or thread it came from, and the reason it was taken that way — which is the part that disappears first.
Written while you decide, not after
The agent is in the refinement call and on the thread. The page exists because the conversation happened, not because somebody found an afternoon to write it up.
A constraint looks different from a preference
“We cap at 5,000 because validation timed out” is a fact you can re-test. “We cap at 5,000” on its own is an arbitrary rule somebody will want to change.
It stays when you are not there
One team in eight says institutional knowledge simply disappears when someone leaves — seventeen per cent at organisations with a thousand engineers or more.
Bulk import
Shipped v2.4 · owner: product
How it got this way
- 12 Feb· Customer feedbackThree customers ask to import from a spreadsheet.All three were re-typing data they already had in a file.
- 3 Mar· Refinement callImport is limited to 5,000 rows per file.Above that the validation step timed out in testing — a limit, not a preference.
- 19 Jun· Design reviewNo automatic merge on duplicates: the user decides.A wrong merge is not reversible, and support would carry the cost.
Nobody wrote this page. It was assembled from the calls and threads where each decision was actually taken — which is why the reasons are still attached to them.
What goes in, what comes out
You write the rules once, in the context file. Giuseppe's own example: a feature list, a roadmap, and a description page for each feature.
In
- Refinement and design calls
- The Teams threads where scope actually moves
- Customer feedback, as it arrives
- The specs and decks you already write
Out
- A page per feature, with what it does today
- The decisions behind it, dated and sourced
- A roadmap that reflects the last conversation
- Open questions, still open
- An alert when two descriptions disagree
A concrete case
The feature that means two different things
In the spec — The export is described as “all the data of the current workspace”. That is what development builds.
Three weeks later — The release notes say “export of the selected records”. Support starts answering on that basis.
Right after — The agent had read both. What it does next is on the right — and the customer meets whichever version they find first.
Specification · 4 Mar · Feature spec
Export returns all the data of the workspace.
Release notes · 25 Mar · Release 4.2
Export returns the selected records.
SecondBrain 365Agent
The same feature, documented two ways
The spec says all the data of the workspace. The release notes say the selected records. Which one is the product?
Scope:all the data of the workspace
Until someone decides, the page keeps all the data of the workspace and the alert stays open.
Support answers on one version, development built the other. The agent spots it the day the second one is written, not when a customer does.
And when the roadmap moves on
The why survives
Not just what was shipped, but the reason it was shipped that way — the part that never gets written down.
Sales and support read the same thing
One source, in SharePoint, that Copilot can answer from.
The next PM
Inherits a documented product instead of a backlog and a folder of decks.
Getting the product team's reasoning to sales and support is the everyday case of knowledge crossing from one team to another without anyone republishing it. Microsoft retired Viva Topics, which promised exactly this kind of recall. What a Viva Topics alternative has to do — and why finding pages was never the hard part.
FAQ
Questions product managers ask
No, and it is not trying to. A backlog holds what is going to be built; this holds what was decided and why. The two answer different questions — “what is next?” versus “why is it like this?” — and the second one is usually the one nobody can answer six months later. The agent reads the conversations around the work, not the tracker.
You tell it, in two ways. It only sees what workspace members share with it — a meeting it was invited to, a thread it was added to. And the context file says what to keep: “a feature list, a roadmap, a description page for each feature” is the example our product owner gives. If a call was not worth recording, you do not invite it.
It writes what was said, with the date and the source attached, so you can check it against the call it came from. If approval is switched on, nothing reaches the knowledge base until you sign it off. And the pages are ordinary SharePoint pages: when the wording is not yours, you edit it by hand.
It will not reconstruct what it never saw. Share the documents you already have and it reads those; from the day it joins, the reasoning stops leaking. The honest expectation is that the trail starts thin and gets valuable around the third month, when the first “why did we decide this?” lands on a page instead of in your memory.
In your own Microsoft 365 tenant: a SharePoint site under the product's Teams group. Nothing is copied to a third-party platform, and your existing permissions and retention rules apply to it because it is not a separate system. The detail your IT will want is on the how it works page.
Need it for something else?
Same agent, same mechanism. What changes is the rules you write in the context file.
Project management
Stop chasing people for updates: the agent asks, and the plan stays current
HR
The answer your team already wrote, found by the next person who asks
IT service desk
Forward the reply you just sent. That is the whole documentation step
ISO audit
Evidence recorded as it happens, not reconstructed the month before
RFP & bids
The tender's deadlines pulled out of the pack, and the chasing done for you
Onboarding & offboarding
What leaves with a person becomes smaller — and it is honest about the rest