- Industry
- Banking
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Head of Retail Banking
- Code
- PRD-01
It turns the bank's strategy, such as growing SME deposits, cutting onboarding time or lifting digital adoption, into quarterly plans for the product teams behind accounts, cards, lending and the mobile app. Mandatory regulatory and scheme changes take capacity first, and every objective is tied to a bank KPI before the plan is published.
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 product management tool: the teams' capacity, the backlog of candidate objectives, the regulatory change calendar and last quarter's results..
- 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 Retail Banking with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the product management tool: it publishes the quarterly plan with objectives and key results per team. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The product strategy pack: strategic themes, bank KPIs (deposit growth, loan book growth, net interest margin, digital adoption, onboarding time, complaint resolution time), the regulatory and card-scheme change calendar, team capacity and the product governance process.
Reads from
the product management tool: the teams' capacity, the backlog of candidate objectives, the regulatory change calendar and last quarter's results.
Acts in
the product management tool: it publishes the quarterly plan with objectives and key results per team.
Hands back
An object with quarter, teams (a list, each with team, capacity_weeks, planned_weeks and objectives (each with objective, kpi, key_results and mandatory)), left_out (a list, each with objective and reason) and risks (a list).
Asks a person when
A mandatory change does not fit in the quarter, a team is over capacity, or the plan includes a new product that has not passed product governance.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Capacity kept for mandatory change (%) | 30 | This share of each team's capacity goes first to regulatory and card-scheme changes. |
| Capacity buffer (%) | 15 | Left unplanned for incidents and urgent fixes. |
| Most objectives per team | 3 | A team gets no more objectives than this. |
| Key results per objective | 3 | Each objective has this many measurable key results. |
| Unfinished objectives | re-justify | How last quarter's unfinished work is treated. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Mandatory regulatory and card-scheme changes take capacity first, up to 30 percent of each team, more if their deadlines require it.
- Leave 15 percent of capacity unplanned and give no team more than 3 objectives.
- Every objective names the bank KPI it moves and has 3 measurable key results.
- Unfinished objectives are handled by the re-justify policy.
- A new product or a change to a product's risk profile needs product governance approval before it enters the plan.
- Name every candidate left out and why.
See the Product Planning Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.