Check-in Meetings

Many employees complain that their manager is not aware of the difficulties they have encountered or the successes they have achieved. Overcoming these challenges together, finding solutions, or celebrating successes, talking about how to achieve better are very important factors that increase employee motivation and performance. At this point, check-in meetings come into play, and having structured and effective check-in meetings is one of the most effective methods of achieving success. It is important to be prepared before check-in meetings, to clearly communicate the difficulties and successes experienced in the process. Some points to keep in mind while preparing for check-in are as follows;

• Review your own team goals.
• Revisit the priorities from the previous check-in.
• Record your progress against your goals in the system.
• Collect data to prove your progress and achievements.
• Identify the problems you are facing, the things that are slowing you down, and the challenges you are facing.
• Talk about ways to overcome these challenges and solve problems.
• Write down anything that needs clarity about the goals.
• Write down your suggestions, ideas, and workarounds for problems that need to be resolved.
• Look into the future and plan what you would suggest from your current position to achieve the organization's goals.

How Often Should You Hold Check-in Meetings?

Check-in frequency depends on the size of the organization, the nature of the goals, and the team's maturity. The general rule is this: in quarterly OKR cycles, weekly or bi-weekly check-ins produce the best results. Monthly check-ins are usually too late — problems grow, opportunities are missed.

For small teams (5-15 people), weekly 15-20 minute sessions are sufficient. In larger departments, a two-tier structure works better: team leads check in with their teams weekly, and department-level check-ins happen bi-weekly. The key is consistency — skipping one week and holding the next undermines the entire check-in culture from the ground up.

How to Run an Effective Check-in Meeting

A productive check-in meeting has three phases: looking back, assessing the current state, and looking forward. In the first phase, you address what changed since last week and which KRs saw progress. The second phase puts blockers and support needs on the table. The third phase clarifies next week's priorities and who will focus on what.

The meeting should not exceed 20-30 minutes. Overly long check-ins are usually a symptom of a structural problem — either the agenda is unclear, or the conversation has drifted into operational details. Check-ins are for discussing strategic progress, not daily operations.

Every check-in should end with concrete takeaways: who will do what by when, which blockers need to be removed, and any goal revisions if needed. These takeaways should be documented and followed up in the next check-in.

Essential Questions to Ask During Check-ins

Asking good questions is more valuable than getting good answers. Here are the key questions managers should ask during check-ins:

• Which key results did you make progress on this week? What percentage are you at?
• Is there anything slowing you down or blocking you? What do you need from me to remove that blocker?
• How confident are you that you'll complete this KR by end of quarter? (On a scale of 1-10)
• What will your most important priority be next week?
• Do you need support from another team or department?

The purpose of these questions isn't to take a controlling stance, it's to remove obstacles together. When a trust environment is built, check-ins transform from an accountability mechanism into a genuine development tool.

Common Mistakes in Check-in Meetings

• Turning the meeting into a performance review: Check-ins are development-focused, not interrogations. If the employee feels judged, they'll avoid sharing real problems.
• Coming unprepared: If neither the manager nor the employee prepares, the check-in becomes an unproductive chat. Progress data should be entered into the system beforehand.
• Diving into daily operations: The purpose of check-ins is strategic goal tracking. Questions like "how many emails did you send this week" kill the spirit of the check-in.
• Inconsistent frequency: Holding a check-in one week and skipping the next three creates a "this meeting doesn't really matter" perception. Lock in a fixed calendar slot and stick to it.
• Not documenting outcomes: If everything discussed stays in the air, the next check-in starts from the same point. Taking brief notes and following up on them is what matures the process.

Sample Check-in Agenda Template (20 Minutes)

The following template can be used for weekly one-on-one check-ins:

• First 5 minutes — Progress update: Brief status report for each KR. Percentage progress and confidence score.
• 5-10 minutes — Blockers and solutions: Challenges encountered, support needed.
• 10-15 minutes — Next week's priorities: Which KR to focus on, what actions to take.
• Final 5 minutes — Feedback and closing: Mutual feedback, recognition and appreciation if applicable.

Following this structure closely for the first few weeks creates a foundation for the team to adapt it to their own rhythm over time. What matters isn't rigid adherence to the template — it's leaving every check-in with a concrete outcome.

Tools and Methods That Support Check-ins

For check-in meetings to be productive, OKR progress data needs to be ready beforehand. OKR platforms like Devokr present KR progress percentages, confidence scores, and past notes in a single dashboard, ensuring both the manager and the employee come prepared.

Beyond digital tools, simple methods also work: having the employee write down "my proudest progress this week" and "my biggest challenge" before each check-in ensures the meeting runs quickly and stays focused. A team that prepares gets the most out of every check-in.