A 1:1 is a recurring, informal conversation between a manager and a report, typically weekly or biweekly, designed to catch problems early and maintain the relationship. A performance review is a formal, documented assessment that creates an official record of performance for HR, promotion, and compensation purposes.
The relationship between the two matters most: nothing that appears in a performance review should be news to the report. If a problem is raised for the first time in a formal review, the 1:1s failed.
Key takeaways
- 1:1s are for early detection and relationship maintenance; reviews are formal records.
- A performance review should contain zero surprises if 1:1s are working.
- The two serve different audiences: 1:1s are for the report, reviews are for the organization.
- Poor 1:1s do not show up immediately; they show up in the performance review as delayed problems.
Why it matters
The most common failure mode is treating both as versions of the same conversation. Managers who let 1:1s turn into status reports end up delivering feedback for the first time in a formal review, which is both unfair and ineffective.
1:1s function as a pressure-relief valve. They are where the report can raise a problem before it becomes a crisis, and where the manager can address a concern before it calcifies into a pattern. The review is where that pattern is formally documented, not where it is first identified.
How it works in practice
How to keep them distinct
-
Reserve the review for what is already documented
If something is worth putting in a performance review, it should already be in your 1:1 notes. The review formalizes what the 1:1 rhythm made continuous. Write the review by reading your 1:1 notes, not by recalling impressions.
-
Run 1:1s on the report's agenda, not yours
Status updates are not a 1:1 topic. If the report's first words are a project update, ask what is making the work hard. 1:1s exist for what is not visible on the ticket board.
-
Do not deliver new feedback in a review
Before the review, ask yourself: has this person already heard everything I am about to write? If the answer is no, either delay the review or have a separate conversation first. Surprises in a formal document are not feedback; they are a grievance.
-
Use 1:1s to prepare the review
Keep a running notes file from each 1:1. When review season arrives, the draft is already written. If the notes are sparse, the review will be impressionistic, and that is a problem for both parties.
-
Treat them as different feedback loops
1:1s are the fast feedback loop, weekly or biweekly. Reviews are the slow loop, quarterly or annual. Both are necessary. Teams that only run one of them either accumulate unaddressed issues or lose the organizational record.
Common mistakes
Turning 1:1s into status meetings
If the first fifteen minutes of every 1:1 is a project rundown, you have replaced a relationship conversation with a second standup. Protect the agenda. Ask questions that cannot be answered by a Jira board.
Saving feedback for the review
Managers who avoid difficult 1:1 conversations often deposit everything into the annual review. The report experiences this as ambush. If it was not said in a 1:1, it should not lead the review.
Skipping 1:1s when things are busy
The 1:1 is most important when both parties are overloaded. Busyness is precisely when problems accumulate. A cancelled 1:1 in a difficult period signals to the report that the relationship is optional.
Treating the review as a one-way conversation
A performance review where the manager talks and the report listens is a monologue. Build in explicit time for the report to respond to each section. If the rating surprises them, the review will generate grievance, not growth.
What it sounds like
Manager and report debrief after an annual review cycle.
“I did not know the communication piece was an issue,” Merav said. “You never mentioned it in our 1:1s.”
Guy paused. “You are right. I should have raised it in October, not in February’s review.”
Daniel made a note: every 1:1 going forward would include a standing slot for ‘what is not working that I have not said out loud.’
Questions managers actually ask
How often should 1:1s happen?
Weekly is the default for direct reports with active workloads. Biweekly is acceptable for senior, autonomous reports. Monthly is not a 1:1; it is an occasional check-in and will miss too much.
How long should a 1:1 be?
Thirty minutes is right for most direct reports. Forty-five if the work is complex or the relationship is strained. One hour is rarely necessary and usually becomes unfocused.
What do you do if a report has nothing to bring?
That is a signal, not a pass. Ask directly: what is the hardest thing about your work right now? What would make next week better than this week? Silence in a 1:1 is data.
Should 1:1 notes go in the performance review?
Yes. Your review narrative should be traceable to your 1:1 notes. If you cannot point to a 1:1 conversation for every substantive claim in the review, you are working from memory, and that is a fairness problem.
What belongs only in the performance review and not in a 1:1?
The formal rating, compensation implications, and the organizational record of documented decisions like a performance improvement plan. These are not 1:1 topics; they require the formal structure and HR visibility of a review.
Can a performance review replace several missed 1:1s?
No. A review is not a catch-up session. It is a formal document. Compensating for missing 1:1s with a dense annual review makes the review adversarial and the relationship weaker.
See how Leap improves execution in your meetings
Leap sits in your meetings, captures decisions and owners in real time, and shows you where execution breaks down before the week is out.