Define skills and knowhow for each role
Configure responsibilities, skills, judgment criteria and escalation rules.
Name the responsibility
Tie the role to a deliverable. An Apple QA role might review UI consistency, code and regression behavior, producing a checklist and findings rather than simply 'owning quality.'
Describe execution skills
Skills describe steps, required tools and output formats. Capture repeatable review, organization and testing procedures, including when to stop or escalate.
Describe judgment criteria
Knowhow supplies the business context for judgment. QA uses the team's design and code standards; finance uses payroll policies, expense rules and approval limits. Do not treat obsolete policies as current facts.
Define escalation boundaries
A finance role can prepare a payroll draft and exception list; its name does not grant payment authority. Escalate uncertain rules, conflicting evidence and out-of-scope requests to an authorized person.
Use a role brief
Have a business owner approve these five fields for each role. In collaboration, distinguish advice, revision ownership and final acceptance authority.
- Scope: reconcile bills and report discrepancies; payment authority is separate.
- Inputs: data sources and effective business policy revisions.
- Resources: tools, directories and cost ceiling.
- Acceptance: output format, evidence and human reviewer.
- Escalation: conflicting data, missing access, unusual amounts or repeated failures.
Evaluate and revise the role
Evaluate normal, incomplete, conflicting and unauthorized cases. Retain failures and reasons for changes, then rerun relevant cases after updating skills or knowhow. Editing a role description does not grant system access; review and verify access changes separately.