Practice the new intake workflow
Use this fictional shared-reporting scenario to practice describing a need before proposing a solution.
Worked example: improve a weekly report
A useful request gives reviewers enough context to understand the problem and consider next steps.
-
1
Describe the current problem
A team spends time combining updates from several sources to prepare its weekly summary.
-
2
Explain who and what are affected
The summary is used by the team's leads to review recurring work; manual collation makes it harder to compare the same information each week.
-
3
State the intended outcome
The requester wants a more consistent way to bring the information together, while leaving the implementation approach open for review.
-
4
Add preferred timing and submit
The requester notes when the improvement would be most useful and submits it through the approved intake route for review.
Two checks that make the handoff clearer
Use these short checks before submission and during review.
Requester check
Make the need understandable without relying on a proposed solution.
- Name the current problem and who experiences it.
- Describe the expected benefit in practical terms.
- Include preferred timing and relevant non-sensitive context.
Reviewer check
Check for enough context to route or clarify the request.
- Confirm the problem and affected audience are clear.
- Ask a focused question when an important detail is missing.
- Keep review distinct from any later prioritization decision.
Practice materials on this page
Use the worked scenario and checks above, then compare the role responsibilities.