Reference library
APPENDIX K
Sample 90- to 100-Day OFA 1 Onboarding Plan
An illustrative week-by-week onboarding schedule tied to Modules 1 through 11, adaptable to real assignments.
Onboarding Plan Overview
A.
Purpose and Approach
- 1.The plan below is an illustrative starting point a mentor can adapt to a specific new OFA's real assignments and pace, rather than a fixed schedule every learner must follow exactly.
- 2.It is deliberately broken into weekly milestones, tied explicitly to Modules 1 through 11, so it can be used directly as the scaffold for a formal learning program rather than only as a loose guideline.
- 3.Module 10 business case exercises should be assigned throughout the plan as real assignments allow - ideally beginning as early as Week 4 - rather than saved only for the final weeks.
- 4.A mentor should feel free to compress or extend any individual week based on how much real assignment volume is available; the milestones matter more than the exact day count.
Week-by-Week Schedule
A.
Weekly Milestones, Weeks 1 Through 15
| Week | Days | Primary Module Focus | Milestone |
|---|---|---|---|
| 1 | 1-7 | Module 1: The OFA Role and the Stewardship Model | Can explain the stewardship model, the four stewardship areas, the six competency areas, and where OFA 1 sits in the career path |
| 2 | 8-14 | Module 2: OFA 1 Role Definition and the Six Core Behaviors; begin Module 3 | Can name all six OFA 1 core behaviors and has started a personal glossary |
| 3 | 15-21 | Module 3: Learning OFA Terminology and Team Processes | Has documented this team's requirements, testing, and escalation processes; glossary has at least 15 confirmed entries |
| 4 | 22-28 | Module 3 completion; begin Module 5 | Meets Module 3 Completion Indicators; has practiced open questions in at least one real or observed conversation; first Module 10 business case assigned |
| 5 | 29-35 | Module 5: Discovery and Communication Basics | Produces a first real meeting summary with decisions and open items separated, reviewed by a mentor |
| 6 | 36-42 | Module 5 completion; begin Module 4 | Meets Module 5 Completion Indicators |
| 7 | 43-49 | Module 4: Contributing to Requirements Documentation | First requirements note drafted under supervision and reviewed by a mentor with specific feedback, in written and, where appropriate, diagrammed or presented form |
| 8 | 50-56 | Module 4 completion; begin Module 6 | Meets Module 4 Completion Indicators |
| 9 | 57-63 | Module 6: Maintaining Notes, Action Items, and Artifacts | Maintains a real action item tracker for an assigned meeting series, reviewed as accurate and current without prompting |
| 10 | 64-70 | Module 6 completion; begin Module 7 | Meets Module 6 Completion Indicators |
| 11 | 71-77 | Module 7: Supporting Testing and Validation | First real test execution record completed with zero unflagged discrepancies |
| 12 | 78-84 | Module 7 completion; begin Module 8 | Meets Module 7 Completion Indicators |
| 13 | 85-91 | Module 8: Supporting the Launch of Fundamental Solutions | Completes a first real launch-readiness check, reviewed by a mentor, verifying deliverables against documented requirements before go-live |
| 14 | 92-98 | Module 8 completion; begin Module 9; Module 10 practice continues; Module 11 readiness conversation | Meets Module 8 Completion Indicators; has completed at least two Module 10 business cases; supervisor holds a first readiness conversation using Module 11 criteria |
Using the Plan
A.
When a Learner Falls Behind Schedule
- 1.A learner who reaches Day 98 without yet meeting every milestone above has not failed the plan - the milestones describe a reasonable pace, not a hard deadline.
- 2.A mentor should use any gap as specific, actionable feedback (which module needs more real assignment volume, which behavior needs more repetition) rather than as a judgment on the learner's overall potential.