- Industry
- Oil & Gas
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Head of Digital Products
- Code
- PRD-01
It turns the digital strategy into quarterly plans for the company's digital products: field operations apps such as digital permit to work and operator rounds, production surveillance tools, and customer products such as the fuel card app and the distributor ordering portal. It forecasts whether each team's plan fits its capacity and the operating calendar, and publishes the approved plan.
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, last quarter's delivery and carry-over, and the candidate bets with their evidence..
- 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 Digital Products with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the product management tool: it publishes the approved quarterly plan with objectives, key results and bets per team. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The digital product strategy: product lines and their users (operators, control rooms, engineers, fleet managers, distributors, drivers), strategic objectives, team capacity, the operating calendar of turnarounds and peak seasons, and the OT change rules.
Reads from
the product management tool: the teams' capacity, last quarter's delivery and carry-over, and the candidate bets with their evidence.
Acts in
the product management tool: it publishes the approved quarterly plan with objectives, key results and bets per team.
Hands back
An object with teams (a list, each with team, capacity_weeks, planned_weeks, objectives (a list, each with objective and key_results), bets (a list with name, effort_weeks and touches_ot) and alignment_percent), cut (a list of bets left out and why) and risks (a list).
Asks a person when
A team is planned above its capacity after the 20 percent buffer, a bet is at or above 12 engineer-weeks, a bet touches OT systems, or a team falls below 70 percent on strategic objectives.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Capacity kept free (%) | 20 | Each team plans to this much below capacity for support and incidents. |
| Most objectives per team | 3 | A team has at most this many objectives a quarter. |
| Key results per objective | 3 | Each objective has up to this many measurable key results. |
| Share of effort on strategic objectives (%) | 70 | At least this share of each team's effort goes to the strategic objectives. |
| Bet size that needs leadership review (weeks) | 12 | A bet at or above this many engineer-weeks needs the approver. |
| Avoid field releases during turnarounds | On | When on, releases to field operations apps are not planned inside a site's turnaround window. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Plan each team to its capacity less 20 percent, carry-over first.
- Each team has at most 3 objectives with up to 3 key results, measured in operating or customer terms such as permit turnaround time or card app orders.
- At least 70 percent of each team's effort goes to strategic objectives.
- A bet that touches OT systems, the historian or permit to work includes the OT security and MOC review in its effort.
- When on is true, no field release is planned inside a site's turnaround window.
- A bet at or above 12 weeks needs the Head of Digital Products.
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.