Start with the responsibility the team owns
The team requesting content is not always the team that owns the process. HR may coordinate onboarding while IT provisions accounts and managers approve role readiness. Sales enablement may maintain the resource library while product owns the claims. Choose a team page below to explore the specific handoffs, review responsibilities and deliverables relevant to that audience.
Agree the learning task and the operating dependency
A training brief becomes more useful when it identifies the task a person needs to complete and the conditions required to complete it. If the real issue is missing access, an inconsistent process or a product failure, content alone may not resolve it. I can help separate those problems and define the work that belongs in the content scope alongside any implementation requirement.
Make the review and maintenance role visible
A useful engagement names the source owner, the subject reviewer and the people who publish and update the material. Those may be different roles. The same distinction helps when content crosses departments: an approved explanation needs a clear authority, and a production workflow needs someone who can move it through review without losing the source context.
Choose a concrete first brief
Send one recurring question, onboarding task or process your team needs to explain. Include the audience and any existing slides, documents or recordings. We can start with a representative module, review how it works in practice and decide whether the approach should expand into a wider library.