Episode story
Panel 1: The table is too quiet
Hana Resources opened the conference room door and immediately noticed three warning signs.
The manager had a scorecard. The employee had a tight smile. Conflict Cat had selected the center of the table as neutral territory.
“This will be quick,” the manager said.
Hana looked at the stack of printed charts, the unopened water glass, and the review form already angled toward disaster.
“Quick is not the same as clear,” she said.
Panel 2: The scorecard attacks
The manager slid the review across the table.
It kept sliding.
The form rotated sideways, knocked a pen into a glass, and stopped directly in front of Conflict Cat, who placed one paw on the rating box as if issuing a final judgment.
The employee stared at the numbers.
“Is this about last week, last quarter, or the project from February?”
The manager blinked. “Yes.”
Panel 3: Hana stops the wobble
Hana placed her glowing clipboard flat on the table.
The room steadied.
“One topic at a time,” she said. “Specific examples. Clear expectations. No mystery ratings.”
The scorecard stopped twitching.
The employee exhaled. The manager lowered the chart. Conflict Cat reluctantly removed one paw from the form.
Panel 4: Feedback gets a spine
Hana drew three columns.
What happened. Why it matters. What changes next.
The manager moved from vague judgment to actual examples. The employee moved from defense to questions. The review moved from awkward theater to structured conversation.
“So the issue is deadline communication,” the employee said, “not my entire personality?”
“Correct,” Hana said.
Conflict Cat looked disappointed.
Panel 5: The next step
The final review did not become perfect.
But it became usable.
There was a timeline, a follow-up meeting, a manager note, and a list of expectations the employee could actually act on.
The chair rolled back into place.
The scorecard faced forward.
Hana closed her clipboard.
“Feedback should help people understand the path,” she said. “Not make them guess where the floor went.”
The real HR lesson
Performance reviews go sideways when they mix vague ratings, old frustrations, surprise criticism, unclear standards, and no follow-up plan. A useful review is specific, timely, documented, and connected to the job.
Managers should prepare examples before the meeting, explain expectations in plain language, separate performance issues from personality judgments, and give employees a reasonable opportunity to ask questions and understand next steps.
Hana’s field notes
- Do not surprise people with old problems. Major issues should usually be addressed when they happen, not saved for review day.
- Use examples, not labels. “Missed three client update deadlines” is more useful than “not proactive.”
- Separate facts from conclusions. Start with what happened before deciding what it means.
- Make next steps measurable. A review should produce actions, timelines, support, and follow-up.
- Train reviewers. Managers need help giving fair, consistent, job-related feedback.
Final panel
The meeting ended without anyone falling through the conference table.
Payroll Panda stamped the follow-up date. Onboarding Owl filed the action plan. Compliance Samurai nodded once from the doorway.
Policy Goblin peeked from the handbook shelf.
“So,” he asked, “annual reviews again next year?”
Hana smiled.
“Only if we talk to people before then.”