Didn’t we already decide this? Who actually decides this? Why are we doing it this way? I thought we agreed on something else. Why am I explaining this again? # The shared decision record for your team and its AI agents. Connect decisions to your purpose, strategy and work. Your people and agents can check what’s agreed, why, and whose call it is. [Start your workspace ↗](https://work.productbrain.io/sign-up)[See how it works →](/product/) Keep working in your connected agent. Early access · For small teams using agents across functions. From work to outcomes ## Your team gets work done. Results still take too long. From **Work** - Rebuilding context - Waiting for clarity - Doing work again To **Outcome** A conceptual journey from work to an outcome. Rebuilding relevant context, waiting for clarity and doing work again can delay value. These are possible sources of delay, not a measured timeline or a complete account of every constraint. Keep direction, knowledge and decision authority connected to the work. One record. Across the team. ## One shared record. Your agents put it to work. Decisions, reasons, direction and roles—connected to the work. Your agents consult the same record. [Direction Where we’re going](/product/#orient)[Decisions What we’ve agreed](/product/#capture)[Work What we’re doing](/product/#capture) **Shared decision record** Role-governed Current agreement + its reason Owning role · scope · history **Product** People + agents **Operations** People + agents **Commercial** People + agents Your connected agents read and maintain the record as you work, within their roles. How it fits your day ### Keep your tools. Connect your agent. Your agent brings the team’s agreements into the work you delegate. Set its role and working instructions; keep working where you are. [See supported agents →](/product/#practice) The routine → your agent [**Find what applies.** Decisions, reasons and related work. ↗](/product/#orient)[**Record your way.** Show you first, or capture as you go. ↗](/product/#capture-preference)[**Use it next time.** The next agent can build on the shared record. ↗](/product/#reuse) You make the calls. Your agent handles the record. [Connect your agent →](/get-started/#setup)[See the full work loop →](/product/) Used to write the page you’re reading ## A decision becomes a starting point. A fresh agent looked up our positioning from its coding environment and drafted this page’s introduction. 01 · The task ### Write our homepage intro. “Who is it for, what does it do, and why should they use it?” 02 · The existing decision Accepted · DEC-1924 ### Teams using agents. Across functions. **Why** · Keep purpose and strategy connected to daily work. **Owner** · Team Lead, Product Brain **History** · Recorded 5 October. 03 · Used in this page ### The intro above. “Connect decisions to your purpose, strategy and work. Your people and agents can check what’s agreed, why, and whose call it is.” Edited from the agent’s draft, with the decision as its starting point. [See it in place ↑](#hero) Our workspace · Read-only · 11 October 2026. Retrieval proof; no customer result or new acceptance. [Try the work loop →](/product/#orient) What we retrieved—and what was missing The agent ran `pb orient --task 'Write a homepage intro for Product Brain. Who is it for, what does it do, and why should they use it?' --full --json`, then opened the relevant records in full with `pb get-many`. CLI 0.1.0-beta.9860. Selected unchanged text from DEC-1924: “agent-first teams are teams where every person works through agents, across proposals, contracts, operations, program design and marketing analysis, not only engineering.” The previous coding-only positioning is archived. The decision’s returned published history attributes acceptance to the founder’s agent acting as Team Lead. This run read that existing record; it did not accept or change it. **Orientation was partial.** The agent followed up by reading the decisions, their owner, related definitions and published histories. A briefing is a starting point; missing context needs a lookup or a question before acting. The fixed headline was already approved separately. We asked the agent for a supporting paragraph and edited its draft. This is one writing task, not a complete product recording, fresh-workspace onboarding test or measured time saving. Early use · UpCurrent ## Their first impressions. On governance and decision-making “This is governance heaven.” **Ralph Zebregs** CEO, UpCurrent On using Product Brain “Product Brain gives me so much piece of mind” **Sylvie van den Meerendonk** Co-founder, UpCurrent Knowledge stays with the team ## They’re away. The reason isn’t. When someone is away—or leaves—their recorded choices and reasons stay available. [See shared reuse →](/product/#reuse) Decision author · unavailable Accepted decision ### One customer. One scoped experiment. **Reason** · Learn what it takes before adding it to the offer. **Owner** · Product Lead Sales + agent Delivery + agent Marketing + agent Customer-request walkthrough · Recorded knowledge stays; it doesn’t replace a person’s expertise. Why a shared decision record? ## Keep the practice. Connect the record. | Your current practice | What Product Brain brings together | | --- | --- | | Agent rules files | Reasons, owners and history across functions. | | A wiki decision log | Agent access during work, with role-controlled changes. | | An agent’s personal memory | Knowledge other people and agents can consult. | | Threads and people’s heads | Recorded reasons available while the author is away. | Briefs, logs and agent instructions can preserve this too. Product Brain connects the record with direction, work and role-controlled changes. Your connected agents help maintain it during work. **Randy Hereman** Founder, Product Brain Why this exists ## The decisions were there. Keeping them useful was a job. I saw a connected record produce useful briefs and surface contradictions. Keeping it current became a job. I built Product Brain so your agents can help keep that record useful while you work—with clear authority for changes. Founder’s experience, not a measured customer result. The experience behind Product Brain On a replatforming project for a business doing about €20 million in revenue, I saw what a connected record could do: surface contradictions and produce briefs that were on point. Keeping it current felt like a full-time role. This experience inspired Product Brain; it is not a measured result from customers using the product. [Meet the person building it →](/get-started/#setup-call) ## Connect your agent. Keep working. Start with one real decision, in a task you already need to do. [Start your workspace ↗](https://work.productbrain.io/sign-up)[Get help starting →](/get-started/#setup-call)