Delivery planning
Find the missing responsibility.
Use the shape of your project to identify which expertise you need. This is a planning guide, not a directory of verified Oprill partners.
Explore the responsibilities ↓9 responsibilities
Educational roles and synthetic exercises. These cards do not list people, companies or verified Oprill partners.
Information architecture
Knowledge
Sources disagree or repeat the same information.
Review question
Which source is authoritative, and who can retire an obsolete copy?
Synthetic exercise
Create two synthetic policy documents with different dates. Ask the reviewer to identify the current rule and explain why the older copy should not determine the answer.
Permission review
Knowledge
An answer could reveal information outside its audience.
Review question
What should change when a source becomes restricted?
Synthetic exercise
Give two test identities different access to the same synthetic collection. Verify that each expected answer uses only the sources available to that identity.
Answer evaluation
Knowledge
A fluent answer is difficult to verify.
Review question
What evidence distinguishes a useful answer from a confident guess?
Synthetic exercise
Write a question with a known answer, a question with conflicting evidence and a question that the collection cannot answer. Agree on the expected behavior before testing.
Workflow boundaries
System actions
A proposed action could change a business record.
Review question
Which steps may read, draft or write, and who approves the write?
Synthetic exercise
Sketch a synthetic ticket update. Separate drafting a reply from sending it, and identify the point at which the support reviewer can reject the proposal.
Recovery planning
System actions
A request may be repeated or stop halfway through.
Review question
How will the reviewer recognize a partial result and recover safely?
Synthetic exercise
Describe a two-step update where the second step fails. Record what the reviewer would see, how duplicate work is detected and when another attempt is appropriate.
Metric definitions
System actions
Different teams interpret the same number differently.
Review question
Which population, time window and exclusions define the result?
Synthetic exercise
Use a fictional account list with one account that closes during the reporting period. Document whether it belongs in the calculation before writing the explanation.
Reviewer preparation
Adoption
People are unsure what they are responsible for checking.
Review question
Can the reviewer explain when to accept, correct or stop the draft?
Synthetic exercise
Give a reviewer one supported draft and one draft that omits a source limitation. Ask them to explain the difference and record the evidence they checked.
Feedback ownership
Adoption
Repeated corrections never reach the underlying process.
Review question
Who decides whether a correction belongs in the source, instructions or evaluation?
Synthetic exercise
Record a synthetic correction, classify its cause and assign an owner. Repeat the original example after changing the relevant material to check that the issue is resolved.
Scope decisions
Adoption
A small exercise is expanding without new evidence.
Review question
What result would justify a next step, and what result would stop it?
Synthetic exercise
Write three criteria for a narrow pilot and an explicit stop condition. Review the evidence against those criteria before adding another audience or workflow.
No matching responsibilities
Try a broader term or choose a different project challenge.
When the challenge is fragmented knowledge.
Look for experience in information architecture, source ownership and permission-aware retrieval. Ask how the team would identify stale material and test whether restricted content stays restricted.
Request an explanation of the evaluation method before accepting a demonstration. A useful demonstration should include a question that cannot be answered from the approved sources.
When the challenge is a system action.
Look for expertise in the target system’s change controls. Define what the workflow may read, what it may propose and which writes require a person to approve.
Ask how duplicate requests, partial failures and rollback would be handled. A draft response and a completed record change must be distinguishable to the user.
When the challenge is adoption.
Include people who understand the team’s actual work. Have them explain the current process, recurring exceptions and the output they would trust enough to review.
An enablement plan should name the review owner and explain how feedback changes the exercise. Do not treat attendance at a training session as proof that the workflow helps.