Menu

A 30/60/90 plan is just a checklist with deadlines
πŸ“°

A 30/60/90 plan is just a checklist with deadlines

DEV Community: beginnersΒ·LXSAIHUBΒ·1 day ago
#26YMXGtL
#devtobeginners#devto#dev#plan#week
Reading 0:00
15s threshold

The worst onboarding plan I ever got said "get oriented in month one." I oriented. I also shipped nothing, met no one, and by day 45 still couldn't tell what "success" meant. "Get oriented" is not a plan; it's a hope with a deadline.

So when I built a generator for onboarding, the only job was to turn that hope into milestones with owners.

Why 30/60/90 and not "week one to week twelve"

The three-bucket structure forces a shape onto the first quarter. Days 1–30 are about access, context, and first small win. Days 31–60 are about owning a piece of the work. Days 61–90 are about operating without hand-holding. That arc is obvious in retrospect and invisible when you're writing a plan from scratch at 5pm on a Friday, which is exactly when these get written.

The role-tuned part matters because a sales hire and an engineer hire have nothing in common in week two.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.