← Back to resources
TrustedOps
How to complete the 30/60/90 Ramp Plan
Designed to produce a plan you review weekly, not a document you file away.
Keep it outcome-based and measurable. A good ramp plan answers "What will be true by Day 30/60/90?" for anyone who reads it.
Step 1: Confirm the role definition
5 min- Write the role mission in 1–2 sentences.
- List 5–7 responsibilities that define the role (avoid long task lists).
- State in scope and out of scope explicitly.
Step 2: Define success measures
10 min- Choose 3–6 KPIs tied to the role outcomes.
- For each KPI, define the source of truth (system/report) and the cadence.
- If you don't know the baseline, write "TBD" and set a date to establish it.
Step 3: Write 30/60/90 as outcomes
15 min- Learning goals: what they must understand to operate safely and independently.
- Deliverables: concrete outputs (shipped, implemented, documented, reduced, improved).
- Ownership milestones: what they own end-to-end by the end of the phase.
- Dependencies / risks: access, training, stakeholder time, data availability.
Step 4: Set the operating cadence
5 min- Schedule a weekly check-in and use the same agenda each week.
- Review evidence (dashboards, tickets, artefacts) rather than opinions.
Quality bar
- Anyone reading the plan should be able to answer: "What will be true by Day 30/60/90?"
- If a statement can't be observed or evidenced, rewrite it.
- Prefer fewer, clearer commitments over long lists.
Tip: After the first two weeks, adjust the plan based on reality — access delays, scope changes, new priorities. The plan should evolve.
TrustedOps – Better Talent Economics · 30/60/90 Ramp Plan Guide v1.0
30/60/90 Ramp Plan
Fill in the plan, then print or save as PDF.