Use Goals, Results, and Recognition in Performance Conversations Between Formal Reviews
Make check-ins between formal reviews concrete by grounding them in goals, reported results, and specific recognition—then leave with one adjustment and a date.
Don't save the whole story for review season
A formal review packs months of work into one room. It arrives too late to change much and leans on memory, mood, and the last two weeks. The useful conversations happen earlier, in smaller pieces, close to the work.
Three inputs keep those conversations honest: goals tell you what mattered, results tell you what happened, and recognition tells you how it happened and who noticed. Bring all three and a check-in becomes a working conversation, not a verdict.
Bring a short record, not a blank page
Don't walk in with a feeling. Walk in with three pieces of evidence.
- The goal. Bring the objective, key result, target, owner, and reporting period. In Wudd, OKRs are set with targets and reporting periods, and progress is tracked against them. The question is not only “did the number move?” It is “does this goal still point at the strategy?”
- The result. Bring the current result and its status. For business KPIs, Wudd gives each metric an owner who reports the period's result, while another person reviews and approves it. That separation keeps the talk on evidence, not assertion. OKR outcomes are recorded as delivered, partially delivered, missed, or abandoned—more useful than pass/fail.
- The recognition. Bring one or two specific examples tied to a Company Value. In Wudd, recognition is tagged, weighted, and capped per giver and receiver. That turns a thank-you into a signal you can discuss without letting one enthusiastic giver distort the picture.
Data is a prompt, not a verdict. Ask what it does not show.
Run a 15-minute check-in that changes something
- Start with one goal. Pick the goal that matters most now. Ask what you said you would do by this point.
- Read the result aloud. Separate fact from story. “The KPI is at 82% against a 90% target” is a fact. “The team is struggling” is an interpretation. Discuss both. Don't blend them.
- Name what helped and what got in the way. Look for system causes: unclear ownership, a changed priority, missing data, a target built on an assumption that no longer holds.
- Put recognition beside the result. Ask which value was tagged and what the person actually did. “You were recognized for Ownership when you caught the handoff gap” is useful. “You're a great team player” is not.
- Agree one adjustment. Change the action, target, owner, or constraint. Write down who does what by when.
- Choose the next signal. Pick one result and one behavior to review next time. That keeps the next conversation from starting at zero.
If you are on the receiving end, ask for the same specificity: “Which result should I protect, and which behavior should I repeat?”
Use recognition as evidence, not applause
Recognition goes wrong in two directions: it disappears into a thread, or it becomes a popularity contest. Wudd treats recognition as a first-class action, not a buried text. A thank-you can be sent in a Wudd Connect thread through a slash command or wizard, tagged to a Company Value, weighted, and capped.
Use that structure to ask better questions:
- Which behaviors are being noticed?
- Which teams are quieter than expected?
- Are a few people dominating the signal?
Wudd calculates culture KPIs from recognition activity, with signals recomputed nightly. If your company has configured it, eligible Control Room metrics can be linked to company objectives in Strategy Alignment, so you can see how culture signals support strategy, including where data is missing.
Wudd's performance view reads behavioral signals such as recognitions, badges, and task completions. That is useful input for a check-in, not a replacement for one.
Don't turn recognition into a leaderboard verdict. Caps limit volume. They do not replace judgment.
Keep goals alive between reviews
A goal that appears only in a review is an artifact, not a working target. Check the reporting period, the owner, and the link to strategy. Confirm whether you are looking at an approved result or a loose estimate. If the goal changes, record the change, owner, and date. A goal that moves every week is not a goal; it is a mood.
In Wudd, KPI targets, OKR progress, and recognition signal live together. That gives you a shared reference point, so the meeting goes to decisions instead of archaeology.
Avoid the common traps
Recency bias: “In the last two weeks...” Pull examples from the full period using recognition records and reported results.
Ambush feedback: “We need to talk about March.” Raise it at the next short check-in, close to the event.
Scoreboard theater: “You're ahead on points.” Discuss the behavior and outcome, not the rank.
Goal drift: “The priority changed but the old OKR stayed.” Record the change, owner, and date.
Close the loop
End every check-in with a short note: the goal, the result, the recognition, the adjustment, and the next date. Share it. If you use Wudd, keep the result and the recognition in the same place as the goals so the next conversation has a trail.
Formal reviews can still summarize the year. They should not be the first time anyone hears what happened. Use goals, results, and recognition in between, and the review becomes confirmation of a conversation already underway—not a surprise.
Product benefits depend on company configuration and adoption. Use your own baseline to assess results.