One Page Performance Review: The Annual 30-Minute Talk

Prepare the Page From the Actual Role

Write down the role and the review period before judging the person. Check what work the employee was assigned during that period. Time spent teaching another technician belongs in that account, even if it reduced the number of tickets they completed themselves.

Use the expectations already agreed for the job. Record a changed responsibility or an unclear standard as context, rather than quietly applying a new expectation to old work. Ask the employee to bring examples the manager may have missed.

Monica Ozaruk recommends clarifying the role and its job description, with a small set of measures, when examining an operational bottleneck. She also cautions that an operational improvement doesn't necessarily mean dismissing someone. That's her practitioner approach, and a useful reason to inspect the assignment before blaming the person.

I'd cut 'performance optimization' from the form. Write the task the technician needs to do and the result you expect to see. The manager should be able to explain that standard without translating the heading first.

Keep One Main Record

Use the page to hold the decisions, with references to the supporting examples. Don't compress the entire ticket history into smaller type. Give the employee the same record the manager uses.

A row of boxes is still empty if nobody can explain the tick.

Replace a label such as 'poor ownership' with the observed work and the agreed requirement it missed. Give positive feedback the same treatment. A completed handoff that let the next technician continue without repeating the diagnosis is more useful to discuss than a vague compliment.

Check the Records Before the Conversation

Choose examples that reflect the person's assignment. Compare completed volume only alongside the kind of work they handled. A specialist's difficult case and a routine request aren't equivalent merely because each closed a ticket.

Check whether the record is complete before interpreting it. Missing time can change a labor report without establishing what caused the omission. Bring the discrepancy to the conversation as something to resolve, rather than deciding in advance that it proves a lack of effort.

Share the page and examples before the meeting, with enough time for the employee to review them. Ray J. Green recommends letting a salesperson assess a selected call before coaching and asking for their own observations before supplying the manager's. Adapt that discussion sequence to a technician's work; it isn't a performance score for every MSP role.

Keep any client feedback with the work it concerns. Investigate a complaint and recognize a good result. Neither should displace the broader record of what the role required.

Use the 30 Minutes to Reach a Decision

Open the annual conversation with the employee's view of the work. Ask what the page misses and which result needs explanation. Keep disputed information marked for checking instead of demanding agreement to finish the form.

Then compare the observed result with the existing standard. Explain the consequence for the work, and let the employee add relevant context. Move from that comparison to the next useful action rather than filling the meeting with another reading of the ticket list.

For a hypothetical example, say the technician's handoff notes don't include the verification result the receiving team needs. Agree what a complete record looks like and identify work on which the technician can practice it. The technician owns completing the note; the lead owns providing a correct example and feedback.

Paul Green recommends breaking expected work into observable skills and practicing a skill with feedback before moving on. His examples concern new starters. Use that approach for a specific gap instead of assigning a broad training course and treating attendance as the finished result.

The manager records the agreed action and any facts still to check. If an unresolved disagreement needs another discussion, assign that follow-up. The 30-minute slot is a planned conversation length, not a reason to declare an unexamined concern settled.

Schedule the Help the Action Requires

Ask the person providing support to accept their part of the plan. Put their coaching time alongside the technician's practice time before assigning the same capacity to client work. An action that relies on unavailable help needs revising.

For a US cost example, the model's Tier 2 salary is $62,000. Applying its general burden multiplier gives $62,000 × 1.25 = $77,500 a year. Training and equipment are outside that burden and still need funding; the calculation is a labor-cost example, not a performance rating or a pay promise.

The model favors healthy margins so good people can be paid well. Keep a pay or promotion request in the record with the person responsible for deciding it. Don't make the development action depend on compensation that hasn't been approved.

Make the Six-Month Check-In a Booked Commitment

The manager books the six-month check-in when arranging the annual review. Use it to inspect the agreed work and update the plan. Keep current problems in ordinary management conversations instead of leaving them unanswered until that date.

Give the action a completion date based on the work and the available support. That date can fall before the six-month meeting. The check-in is a formal opportunity to review progress, not permission to postpone every action until it arrives.

Use this closing checklist before releasing the page:

• Employee: confirms the assigned action and raises any missing dependency.
• Manager: records the result to inspect and its agreed completion date.
• Coach or lead: accepts the teaching or feedback work and its scheduled time.
• Process owner: accepts any required change to a template or access arrangement.
• Manager: books the six-month check-in and next annual review, and shares the record.

At Monday's board check, an overdue review action should still show its owner and original due date in the appropriate internal work record. The manager checks what blocked it and records the next decision. Move the date only with a recorded reason; don't remove the overdue state by silently rewriting the promise.

Keep private employment details out of the shared client ticket board. The operational action can identify the task and responsible person while the review itself stays in the restricted personnel record. The lead needs enough information to schedule help, not access to the whole conversation.

At the six-month check-in, inspect the agreed evidence and record whether the action is complete or needs further work. Start the next annual page from those records. Book the conversation first, then prepare a page the employee can check before the meeting.