LESSON 4 OF 6 · BEGINNER
Use 30/60/90-day plans carefully
Set milestones that reflect the actual learning curve, resources and role. Distinguish learning objectives from performance commitments and explain how feedback works. Treat a plan as a shared working document, not an inflexible promise of output. Review assumptions when conditions change.
Draft one learning and one work milestone for each 30-day period.
About 2 minutes reading + 12 minutes practice. Take longer when needed.
Apply the method
Use 30/60/90-day milestones as a shared plan, not a universal productivity promise. Define the work, required learning, resources and dependencies for each period. Make milestones observable and review them with the employee. If a prerequisite is delayed, adjust the work plan transparently rather than evaluating the person against an impossible condition. Separate a learning objective from a performance commitment. Record who supplies support and what would prompt a change in timing. The plan should make progress understandable rather than create an inflexible schedule detached from the role.
A worked application
Fictional example: A new customer-success employee should first learn the service workflow, then handle supervised cases, then manage a defined workload. Required permissions are delayed, so the manager changes the practice schedule and escalates the access issue. The employee’s readiness is assessed after the dependency is restored. A senior technical hire may need a different sequence and evidence standard.
Common mistake to avoid
Do not copy the same milestones across roles merely because the 30/60/90 format looks organized.
Work through the case
FICTIONAL SCENARIO
A service employee cannot meet a customer-response milestone because required system permissions are delayed. The plan should surface that dependency rather than label the employee unsuccessful.
Make it practical
Draft one learning and one work milestone for each 30-day period.
Compare your reasoning with a worked response
Make milestones observable and assign support. A missed dependency should trigger a response, not a retroactive change of expectations.
Takeaway
Use the method to explain your decision, identify what you still need to verify and choose an accountable next step.
Treat the response as a model for reasoning, not the only possible wording. Adapt it to the role, evidence and appropriate organizational guidance.