Digital Product Planning Agent
Turns the omnichannel strategy into quarterly plans for the online store and app.
- Industry
- Retail
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- E-commerce Director
- Code
- PRD-01
It turns the omnichannel strategy and each digital team's capacity into a quarterly plan for the online store and app: the objectives (online conversion, click-and-collect share, app adoption, returns rate), the bets that serve them, the team each bet goes to and the key results each is measured by. It forecasts whether the plan fits capacity with the buffer left free and the peak code freeze respected, and creates the approved plan in the roadmap tool.
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 roadmap tool: the teams' capacity, last quarter's bets and results, and the candidate bets..
- 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 E-commerce Director with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the roadmap tool: it creates the approved quarterly plan with objectives, key results and bets. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The digital strategy: company objectives for online and omnichannel, team charters (search and browse, product page, basket and checkout, accounts and loyalty, app, fulfilment options), team capacity, the peak trading code freeze and last quarter's results.
Reads from
the roadmap tool: the teams' capacity, last quarter's bets and results, and the candidate bets.
Acts in
the roadmap tool: it creates the approved quarterly plan with objectives, key results and bets.
Hands back
An object with objectives (a list, each with objective, key_results with metric, baseline and target), bets (a list, each with name, team, effort_weeks, objective and review_needed none, pci or privacy), capacity (a list, each with team, capacity_weeks, planned_weeks and buffer_weeks) and deferred (a list).
Asks a person when
The plan exceeds a team's capacity after the buffer, drops a committed company objective, or schedules a customer-facing release inside the peak freeze.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Capacity left free (%) | 20 | Share of each team's capacity kept for incidents, peak support and unplanned work. |
| Most objectives per team | 3 | A team carries at most this many objectives. |
| Key results per objective | 3 | Each objective has at most this many key results. |
| Peak code freeze (weeks) | 6 | Weeks around Black Friday and the holidays in which no customer-facing change ships; bets in that quarter must finish before it. |
| Unfinished bets from last quarter | re-justify | How unfinished bets are treated. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Plan each team to its capacity minus 20 percent.
- Give each team at most 3 objectives and each objective at most 3 key results, each a number with a baseline.
- Every bet serves a named objective; a bet that changes checkout, payments or account data names its PCI DSS or privacy review.
- In a quarter with peak, customer-facing bets finish before the 6-week freeze or move to the next quarter.
- Unfinished bets follow the re-justify policy.
- A plan that drops a committed objective or exceeds capacity goes to the E-commerce Director.
See the Digital 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.