Solution · Review and sign-off
Roadmap and prioritization
Every roadmap change decided by the person who owns the roadmap.
Ask, then Lena decides, then Roadmap.
Who decides · Lena Fischer · Head of product · a change to the committed quarter
How it runs
Requests for scope arrive from sales, support and engineering. The agent sizes them against the committed roadmap; the person who owns it decides.
A seat is a role a person and an agent hold together; the escalation matrix says who decides above each limit, seat by seat.
PRD-R03
changes to a committed quarter need the roadmap owner
- Agent carries10:00CRM: a key account asks for multi-entity invoicing
- Agent carries10:10Sized against the quarter’s commitments and the payments initiative
- Rules check10:12
PRD-R03
changes to a committed quarter need the roadmap owner
- Person decides14:00Lena defers it to next quarter; the account is told why
Your issue tracker · Billing
BIL-482
Multi-entity invoicing, asked for this quarter
- Assigned to
- THBilling product manager seat
- Status
- Needs Lena
Illustration · Halden, a fictional company
- 01Sales, support or engineeringRaise the request where they work: the CRM, a ticket, a thread. It becomes a request with an owner.
- 02The product manager’s agentSizes it against the quarter’s commitments and the initiatives, and prepares the trade-off.
- 03The product managerInside the quarter’s commitment, decides; a change to a committed quarter goes up (PRD-R03).
- 04The Head of productDecides a change to the committed quarter, with the trade-off in front of her.
- 05The agentUpdates the roadmap and the backlogs, and tells the requester why.
Where the decisions sit
Decision, who decides, up to where, and above that whom.
- Scope change on a committed featureDecides: the product managerUp to: inside the quarter’s commitmentAbove that: the Head of product
- A change to a committed quarterDecides: the Head of productUp to: the quarter’s capacityAbove that: the CEO
- Priority inside a teamDecides: the team’s lead seatUp to: the team’s capacityAbove that: the department head
How much the agent decides, to start. Asks every time: a roadmap change is a person’s decision. The agent sizes the request and prepares the trade-off.
The record it leaves. The request, the trade-off it was decided on, the decision, who took it and who was told.
How it plugs in
No new inbox, no new tool to learn.
- 01
An app in your tools
Connects to your repositories, trackers and chat as an app
- 02
A check, not a meeting
Holds a decision as a check the owner clears
- 03
Where people already work
Asks the owner where they already work, and carries out what was decided
Roadmap · this quarter
A change to the committed quarter
Waiting on Lena Fischer · Head of product
Multi-entity invoicing in place of a smaller item
The tools it runs through
- Issue trackers
Azure DevOps BoardsGitHub IssuesJiraLinear
- Chat and email
Email
- Alerting and incidents
DatadogGrafanaOpsgeniePagerDutySentry
- CRM
HubSpotSalesforce
- Business systems
Microsoft Dynamics 365SAPServiceNow
We connect to the systems you run, and build the connection before the demo.
Where it leads
- Strategy to executionOne brief, owners named on day one, a daily roll-up.
- Customer escalations into the backlogEach escalation owned, answered and fed back to the roadmap.
- Code review and release that keep pace with coding agentsEvery pull request to its owner; above a limit, up the escalation matrix.
Start with howyou run today.
Bring one piece of work that breaks at the handoffs: a pull request waiting on three reviewers, an initiative spread across twelve tools, a release nobody owns. We model the seats it crosses, give one of them an agent, and follow one decision to its record.