Sometime in my third year at Hana Group I opened a filing cabinet in a back office at a Sam's Club unit and found a stack of personal development plans. Fourteen of them. All signed. All dated eleven months earlier. All identical in one specific way. They had been written, signed, filed, and never opened again.
Not one of the general managers who had signed those plans could tell me, without checking, what was on their own. Two of them had forgotten they had one at all. The plans were beautifully written. They had SMART goals and development areas and stretch assignments. They were, by every measure of the paper on which they were printed, professional documents. They were also, by every measure of the operating week, invisible.
That filing cabinet is why I stopped writing PDPs the way I had been taught in corporate training and started writing them the way I write them now. What I want to give you is the version that actually holds. Not the version that reads well in a talent review. The version a general manager opens on their phone at 6 am on a Monday and can act on before the door unlocks.
Why the drawer eats most PDPs
A PDP dies for three reasons, and all three of them are the writer's fault, not the employee's.
The first is length. Most PDPs are three to five pages of goals, competencies, learning resources, stretch assignments, and reflection prompts. Nobody opens a five-page document more than once. The document is the failure mode. Any development plan longer than one page is, in practice, a plan the employee will read in the meeting where they sign it and then never again.
The second is vagueness. Corporate training loves phrases like "improve executive presence" or "strengthen stakeholder communication" or "develop strategic thinking." Those are not goals. Those are wall art. You cannot audit them, you cannot measure them, and you cannot argue about them at the monthly checkpoint. The reason nobody argues about them is that there is nothing to argue about.
The third is disconnection from the operating rhythm. The PDP gets set inside an annual review process, and then the operating week eats it. Weekly one-on-ones focus on the P&L, the schedule, and this Friday's private event. The PDP sits at a different cadence, and any document sitting at a different cadence from the work will lose to the work every single time.
The document is the failure mode. If your development plan does not fit on one page, the employee is not going to open it a second time, and the plan is already dead.
Three lanes, and only three
Every real development goal an operator has fits in one of three lanes. Technical, leadership, business. If you cannot fit a goal in one of the three, it is not a development goal. It is a task, a project, or a personal wish.
Fig. 1 · One page. Three lanes. Three outcomes. Ninety days.
The technical lane
Technical is the craft of the operator's job. For a general manager that means reading a P&L line by line and knowing what is off, scheduling labor to a demand curve, running inventory discipline in the walk-in, and being fluent in the point-of-sale and back-office systems the unit runs on. For a shift lead it might be closing paperwork accuracy, cash handling, food safety, or the recipe book. The technical lane is about how well the person operates the machine in front of them.
The mistake I made for years was skipping this lane because it felt too basic. It is not too basic. A general manager who cannot open a P&L and name their three biggest variances in 60 seconds has a technical development need, no matter how many years they have been in the job. The technical lane is where the unit actually gets protected. Skip it and every leadership goal you write is going to sit on top of nothing.
The leadership lane
Leadership is the people work. Coaching cadence, delegation, hard conversations, retention. This lane is the one most people think a PDP is entirely about, and they are wrong. It is one third of the plan, not the whole plan. When it becomes the whole plan you get a general manager who is beloved by the team and losing money every month.
The reason the leadership lane needs its own outcome is that leadership growth is slow and easy to fake. You can convince yourself you are getting better at coaching without a shred of evidence. A measurable leadership outcome forces evidence. Ten documented one-on-ones. A written coaching plan for each of your three lowest-performing shift leads. Two hard conversations completed with a specific person by a specific date. Numbers, dates, artifacts.
The business lane
Business is how the person is starting to think beyond their own unit or shift. Guest experience initiatives, brand consistency, community relationships, the beginnings of a growth idea. This is the lane that says "you are not just running the machine, you are becoming the person who could design the next one."
Most PDPs skip this lane entirely, which is why most PDPs cannot tell you who on the bench is ready to promote and who is not. A general manager who is scoring well on technical and leadership but has never touched a business-lane outcome is not ready to become a district manager. The business lane is the earliest visible signal of a future multi-unit leader, and it is invisible until you write it down.
What a measurable outcome actually looks like
One outcome per lane. Each outcome has three parts: a number, a target, and a date. Anything softer than that gets rewritten before the plan is signed.
Here is a real example from a general manager I worked with at Zareen's, the Bay Area group where I ran the turnaround. She was a strong operator with a weak grip on the P&L. Her old plan said "become more financially literate." Her new plan said this:
- Technical: Open the weekly P&L review as the presenter for 12 consecutive Mondays, walking labor, food, and top three variances without notes, by November 15.
- Leadership: Run a documented 30-minute one-on-one with each of the four shift leads every week for 12 weeks, tracked in a shared sheet, by November 15.
- Business: Design and launch one guest experience initiative (choose from the three ideas we mapped in September), measure impact on guest satisfaction score for 30 days, present the result at the November regional operating review.
Every one of those outcomes is auditable at day 90. Either she opened the P&L 12 times as presenter or she did not. Either the shared sheet has 48 one-on-one entries or it does not. Either the initiative launched and she has 30 days of guest satisfaction data or she does not. There is nothing to argue about. There is only what happened.
If you cannot audit an outcome in 30 seconds at day 90, it is not an outcome. It is a wish. Wishes do not belong on development plans.
The monthly checkpoint is the whole thing
Here is the piece almost everyone gets wrong. The plan is not the important artifact. The monthly checkpoint is. Three 45-minute meetings, booked on the calendar the day the plan is signed, same day of the month, standing agenda.
The agenda for the checkpoint is four questions, in this order. What moved. What stalled. What is blocked. One thing to try in the next 30 days. That is the whole meeting. It works because it is short, it works because it is the same every month, and it works because it forces the employee to have opened the plan before they walk into the room. If they have not opened the plan, the first question has no answer, and they will not let that happen to themselves twice.
When I say "the checkpoint is on the calendar the day you sign the plan," I mean literally. Not "we will schedule monthly checkpoints going forward." Book all three at once. Send the invites. Protect the time. If those three meetings are not on the calendar by the end of the meeting where you signed the plan, the plan is already dead and you have not noticed.
Who owns what
The employee owns the plan. They wrote it. They open it. They drive the checkpoint conversation. They bring the evidence. They ask for the resources they need.
The manager owns the cadence. The manager holds the calendar, protects the checkpoint from getting bumped for operational fires, provides the unblocking when the employee names a blocker, and makes sure the plan gets edited at day 90 rather than filed. That is it. The manager does not own the plan itself, and the moment they start to, the employee stops owning it, and the plan is dead again.
I ran this the wrong way for years. I owned the plans for my 21 general managers, tracked their progress in my own spreadsheet, and quietly wondered why they never brought up their PDPs unless I did. It was because they were my plans, not theirs. The version that works starts with the employee writing the first draft, in their own words, with the four questions on a blank page.
Day 90: edit, do not file
At day 90 the plan is not archived. It is edited, in a 60-minute session, in front of the employee. One outcome moves to done and gets celebrated in a specific sentence. One outcome rolls forward into the next 90 days, usually with a bigger number attached. One outcome gets replaced entirely because the world moved or the priority changed. The next three monthly checkpoints get booked before the meeting ends.
That is what makes a PDP hold. Not the goal-setting framework. Not the competency model. The fact that at day 90 there is a working draft of the next 90 days, and everyone knows the next three checkpoints are on the calendar. The plan is a living document because you never let it stop being one.
What this actually gets you
Across the 21-unit region I ran at Hana Group, the year I switched to this format, three things happened that I did not see coming. First, the general managers started bringing their plans to their one-on-ones without being asked, because the plan and the operating conversation stopped being separate documents. Second, promotion conversations got a lot easier, because the business lane made "who is ready" a matter of evidence rather than gut. Third, the general managers who were not going to make it self-identified inside 90 days, because the checkpoint asked them a question they did not want to answer.
Development is not a talent-review artifact. It is an operating rhythm. Write the one page, book the three checkpoints, own your side of it. The drawer stays empty.
Cadence beats charisma. Even here.