PLATFORM
Personas and collaboration
Give work a role, responsibility, context and a human review path.
Overview
Use personas to make responsibility and operating boundaries explicit. A persona is a work configuration, not a substitute for a named human owner or a real-world professional qualification.
Define the role
Specify purpose, scope, expected outputs, prohibited actions and escalation conditions.
Give bounded context
Provide only the information needed for the task, consistent with the user’s permissions and data classification.
Limit tools
Expose only the actions needed for the job. Separate read-only research from write or execution privileges.
Set review gates
Require a human decision for material, sensitive, irreversible or externally consequential actions where appropriate.
Measure outcomes
Review quality, rework, exceptions and feedback—not just speed or volume.
Worked example
Keep a persona within its role
A research persona can prepare a recommendation without having authority to change the production system.
- 1Define its objective, inputs, expected artefacts and escalation conditions.
- 2Provide only the context needed for that role.
- 3Allow research and draft-generation tools, but omit production write permissions.
- 4Ask a named human owner to review the recommendation.
- 5Give execution permissions only to an explicitly authorised workflow or operator.
Was this guide useful?
Send feedback or flag a gap. Include the article link so the team can improve the right guide.