Decision inputs
Facts that change the policy answer
The working material is customer evidence, effort estimates and strategic goals; the intended result is a suggested feature priority. Recording that pair prevents a vague approval from spreading to other uses.
- 1Task and owner
- Product manager wants to prioritise product features. Record the person who will stand behind a suggested feature priority after the tool has finished.
- 2Information involved
- Customer evidence, effort estimates and strategic goals. The classification must cover what the tool can retrieve as well as what the requester types.
- 3Tool and account
- An approved company account. Confirm the approved account, retention setting and any connected service before the request begins.
- 4Intended result
- The expected result is a suggested feature priority. The policy needs to know what happens after generation, including publication, communication and automated use.
- 5Consequence if it is wrong
- Weights can hide subjective choices or undervalue customers absent from the data. That risk sets the level of review and the person who should receive an exception.
- 6Human review
- product leadership team should inspect, change, reject or stop the result. Review is meaningful only when that person has enough context and authority to change the result.
Possible policy routes
The task name alone cannot decide it.
A published workplace policy can return different answers for the same task. These are the practical branches worth encoding.
A routine policy route may be possible
The request may fit ordinary policy handling once the exact account is approved, only the minimum internal product and customer information is used, a suggested feature priority remains within the stated purpose, and product leadership team reviews it before use.
Approval may be required
Send the request for approval if the account or data handling is uncertain, weights can hide subjective choices or undervalue customers absent from the data, or a suggested feature priority reaches people or systems beyond the requester’s authority.
The request may need to stop or change
The company may need a safer design when restricted information would enter an unapproved service, the output would act before product leadership team can intervene, or publish criteria and let accountable owners challenge the ranking cannot be maintained. Consider less information, a controlled account or a non-AI process.
Request checklist
Questions to ask before using the tool
- 01
Is the exact account approved for prioritise product features, including its plug-ins and connected sources?
- 02
Who is permitted to expose customer evidence, effort estimates and strategic goals to this tool and for this purpose?
- 03
Who receives a suggested feature priority, and what will they do with it?
- 04
What evidence will product leadership team use to accept, correct or reject the result?
- 05
Is this genuinely one request, or will repeated use turn it into an embedded process?
Worked request
What the employee should submit
This example supplies decision facts without pasting the underlying material into the approval record.
- requester
- product manager
- task
- Use AI to prioritise product features.
- information
- customer evidence, effort estimates and strategic goals
- tool
- An approved company account
- frequency
- Recurring work
- region
- Where the work and affected people are located
- purpose
- Analyse
- impact
- Product decision
- review
- Complete human review
- owner
- product leadership team
Useful safeguards
Controls that fit this request
- ✓
Publish criteria and let accountable owners challenge the ranking
- ✓
Keep whole files, mailboxes and datasets out of the prompt when a short part of customer evidence, effort estimates and strategic goals is enough.
- ✓
Keep the use within analyse and run another check if the audience, tool or intended effect changes.
- ✓
Preserve who accepted a suggested feature priority, when they did so and which rule version they applied.
Questions people ask
About this AI use
Is using AI to prioritise product features automatically allowed?
Permission depends on the facts submitted for this request. A different tool, information class, region or use of a suggested feature priority can produce another route.
How specific should the workplace AI request be?
Describe a suggested feature priority, identify customer evidence, effort estimates and strategic goals, name the exact tool and account, explain who will receive or rely on the output, and state how product leadership team will review it.
How should a later reviewer understand this decision?
Preserve who accepted a suggested feature priority, when they did so and which rule version they applied. A classification and controlled reference may be enough when copying customer evidence, effort estimates and strategic goals would create unnecessary risk.