Roadmap Prioritization Agent
Ranks roadmap items by value and effort.
- Industry
- Insure AI
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Head of Product
- Code
- PRD-02
It scores roadmap items for the insurance products and their digital journeys on premium reach, impact on loss ratio or conversion, confidence and effort, puts mandatory regulatory items above the line, and ranks the rest. Once approved it writes the new rank and score to each item in the product change backlog and flags low-confidence items for discovery first.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the policy administration system: the product change backlog with each item's line of business, current rank, status, effort and linked regulatory obligation, and policy counts and gross written premium by product..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of Product with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the policy administration system: it updates each backlog item's rank, score and discovery flag. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The roadmap scoring guide: how reach is counted in policies and gross written premium, the impact scale for loss ratio, conversion and retention, the strategic themes for the year and the list of regulatory obligations with their dates.
Reads from
the policy administration system: the product change backlog with each item's line of business, current rank, status, effort and linked regulatory obligation, and policy counts and gross written premium by product.
Acts in
the policy administration system: it updates each backlog item's rank, score and discovery flag.
Hands back
A list in rank order, each with rank, name, line_of_business, score, reach, impact_kpi, confidence_percent, effort_weeks, regulatory (true or false), theme (or null), previous_rank (or null), needs_discovery (true or false) and reason.
Asks a person when
A committed item moves 5 places or more, a regulatory item would fall below the line, or the published top 10 changes.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Scoring model | RICE | How each item is scored before theme weighting. |
| Boost for a strategic theme (x) | 1.3 | An item that serves a named strategic theme has its score multiplied by this. |
| Most uplift from premium at stake (%) | 25 | Gross written premium at stake can raise an item's score by at most this much, so one large broker or scheme cannot buy the roadmap. |
| Send to discovery below confidence (%) | 50 | Items scored with confidence below this are ranked but marked for discovery before build. |
| Items published as committed | 10 | Only the top items up to this count are published to the agent and broker portal as planned. |
| Rank moves that need review (places) | 5 | A committed item that moves this many places or more needs the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Items needed to meet a regulatory obligation or a conduct finding sit above the line and are not scored against discretionary work.
- Score the rest with RICE, counting reach in policies or gross written premium and impact on a named KPI such as loss ratio, quote-to-bind conversion or claims turnaround time.
- Multiply the score by 1.3 for an item serving a named theme, and let premium at stake raise a score by no more than 25 percent.
- Mark items with confidence below 50 percent for discovery before build.
- Publish only the top 10 items as planned on the agent and broker portal; never publish dates for items that depend on a rate filing not yet approved.
- A committed item moving 5 places or more is shown to the Head of Product with the reason.
See the Roadmap Prioritization Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.