SME Responsibilities – Detailed Outlines

START → Identify policy → Prepare explanation → Conduct training session 
→ Q&A → Confirm understanding → END

1. Review the policy to be explained.
2. Create a concise slide deck or cheat‑sheet.
3. Schedule a training or Q&A session.
4. Deliver content and illustrate real‑world scenarios.
5. Collect questions and address them.
6. Distribute reference materials.
7. Verify comprehension through quick quizzes or sign‑offs.

START → Draft change → Conduct risk assessment → Submit to management → 
Receive approval or request revisions → Approve → Update documentation → END

1. Identify the change needed.
2. Draft the updated policy or procedure.
3. Perform a risk or impact analysis.
4. Prepare a change request package (impact, benefits, risks).
5. Submit to the relevant manager or governance board.
6. Attend review meeting if required.
7. Incorporate feedback and obtain formal approval.
8. Publish the updated artifact and notify stakeholders.

START → Identify target consumers → Prepare messaging → Disseminate 
communication → Collect feedback → Adjust messaging if needed → END

1. Define the consumer personas.
2. Draft clear, non‑technical descriptions of goals and deliverables.
3. Select appropriate channels (email, webinars, support docs).
4. Publish or broadcast the message.
5. Monitor consumer questions and concerns.
6. Update communications to address emerging queries.

START → Identify problem → Reproduce issue → Root‑cause analysis → 
Develop solution → Validate → Document fix → END

1. Receive incident or error report.
2. Recreate the scenario in a controlled environment.
3. Conduct root‑cause analysis (logs, metrics).
4. Design a solution or workaround.
5. Test the fix in dev/staging.
6. Deploy to production (if applicable).
7. Update knowledge base and inform stakeholders.

START → Receive draft → Cross‑reference facts → Verify with authoritative 
sources → Return feedback → Incorporate corrections → END

1. Obtain the draft or deliverable.
2. Identify all claims that require validation.
3. Use trusted references (law texts, vendor specs).
4. Mark inconsistencies or gaps.
5. Provide annotated feedback.
6. Ensure revisions are incorporated.
7. Finalize the document.

START → Receive artefact → Evaluate against criteria → Provide feedback → 
Team revises → Re‑evaluate (if needed) → END

1. Define feedback criteria (standards, policies, best practices).
2. Inspect the artefact in its current stage.
3. Highlight issues and recommend improvements.
4. Discuss changes in a brief meeting or via comments.
5. Re‑inspect after revisions.
6. Approve when criteria are met.

START → Identify test objectives → Draft scenarios → Review with 
leadership → Execute tests → Validate results → Document findings → END

1. Clarify what must be tested (policy, compliance, performance).
2. Draft test scenarios (inputs, expected outputs).
3. Present scenarios to leadership for sign‑off.
4. Set up testing environment.
5. Execute tests (manual or automated).
6. Capture results and compare against expectations.
7. Report findings; recommend mitigations if needed.

START → Define UAT criteria → Recruit end‑users → Provide test scripts → 
Execute UAT → Log defects → Verify fixes → Sign‑off → END

1. Define success criteria in collaboration with business stakeholders.
2. Select representative end‑users.
3. Deliver UAT documentation and training.
4. Observe test execution and capture issues.
5. Prioritise defects and schedule fixes.
6. Re‑test fixed items.
7. Obtain formal sign‑off.

START → Receive deliverable → Verify against spec → Run validation tests 
→ Document compliance → Approve or request changes → END

1. Retrieve the final deliverable (code, report, product).
2. Cross‑check against the specification or acceptance criteria.
3. Run automated validation tests or manual checks.
4. Log any deviations.
5. If acceptable, sign off; otherwise, forward to the responsible party.
6. Archive validation evidence.

START → Identify documentation needs → Gather content → Draft documents → 
Peer review → Revise → Publish → Disseminate → END

1. Conduct a documentation gap analysis.
2. Draft the content with clear structure (introduction, procedures, FAQ).
3. Review with subject peers and stakeholders.
4. Format for consistency (templates, style guide).
5. Publish in the knowledge base or LMS.
6. Notify relevant audiences.
7. Update documents as the project evolves.

START → Determine training objectives → Design curriculum → Develop 
materials → Conduct training → Assess learning → Iterate → END

1. Identify the learning objectives and target audience.
2. Create or curate training content (slides, demos, handouts).
3. Schedule training sessions and logistics.
4. Deliver the training (in‑person, webinar, e‑learning).
5. Administer quizzes or practical exercises.
6. Collect feedback and adjust content.
7. Archive training records.

START → Gather project data → Compile status report → Review with SME 
team → Send to stakeholders → Receive questions → Follow‑up → END

1. Pull status data from PM tools and logs.
2. Summarise progress against milestones, budget, risk.
3. Draft concise communication (email, dashboard, meeting).
4. Circulate to stakeholders and solicit comments.
5. Record any concerns and schedule actions.
6. Update stakeholder database.

START → Receive legal request → Review case facts → Prepare expert report 
→ Meet with legal counsel → Provide testimony → Respond to cross‑examination → END

1. Receive the subpoena or legal brief.
2. Identify the technical issues at stake.
3. Gather evidence and data from the organization.
4. Draft an expert opinion report, following legal format.
5. Meet with the legal team to align on strategy.
6. Attend deposition or trial, present evidence, and answer questions.
7. Provide post‑trial support as required.