Weekly Check-In: A Practical Guide for Small Business
Weekly check-ins for small business: 15-25 min structure, question banks, cadence decisions, common mistakes, and how they differ from 1:1 meetings.
Weekly Check-In
A practical guide for small business managers
The first time I introduced weekly check-ins at a company I was running, I made the mistake almost every founder makes the first time. I scheduled 60-minute meetings with each direct report, called them check-ins, and ran them like miniature performance reviews. Within four weeks, two of my direct reports had quietly stopped preparing for them, one was dreading them on the calendar, and I was getting the kind of cautious, polished updates that signal an employee has stopped trusting the conversation. The fix took me another three months to figure out: weekly check-ins are not 1:1 meetings, they are not performance reviews, and they should not be 60 minutes. They are short, structured, status-focused conversations that produce alignment without producing meeting fatigue.
Most articles on weekly check-ins fall into two camps. The vendor articles treat check-ins as a feature their performance management software handles, focusing more on the tool than the practice. The generic management articles offer abstract advice (be a good listener, ask open-ended questions) without giving you the specific structure that turns the practice from theory into something you can actually run with a small team. Both miss the operational reality: at small business scale, the founder or owner is usually the one running these check-ins, and what they need is a clear 15-25 minute structure that works without enterprise tooling.
This guide is different. It is written for small business owners and managers who want to use weekly check-ins as a practical management tool, not as another corporate ritual that produces meetings nobody finds useful. You will get the honest distinction between weekly check-ins and 1:1 meetings (most articles confuse them), the 15-25 minute structure with five segments, question banks for six different contexts, cadence decisions for different employee situations, the template structure that produces useful written records, advice for first-time managers, and the common mistakes that turn check-ins into status reports. I built FirstHR for this audience because most performance management content assumes a level of organizational sophistication small businesses do not have.
What a Weekly Check-In Actually Is
The simple working description: a weekly check-in is the answer to four questions every week. What happened? What is in the way? What comes next? What do you need from me? The answers come from the employee; the manager listens, asks clarifying questions, surfaces context where useful, and commits to specific follow-ups. The whole conversation should fit in 15-25 minutes; longer than that usually means the conversation has drifted into 1:1 territory.
Three things are true about every weekly check-in that produces useful results. First, the cadence is consistent. Skipping weeks erodes the practice faster than reducing the duration; once check-ins become optional, employees stop preparing and the conversation loses its productive structure. Second, the employee drives the agenda. Check-ins that are managed by the manager turn into directive sessions; check-ins driven by the employee surface the information the manager actually needs. Third, the conversation produces a written record. Without written priorities and commitments, check-ins become conversations that everyone forgets by the next day.
Most check-in failures happen because at least one of these three is missing. The cadence breaks. The manager talks too much. Or no notes get taken. Each missing piece reduces the practice's value by 30-50%; missing all three produces what most teams call "check-ins that did not work."
Weekly Check-Ins vs 1:1 Meetings
The most common confusion in this topic is between weekly check-ins and 1:1 meetings. Many articles treat them as synonyms or use the terms interchangeably; they are different practices serving different purposes, and combining them produces meetings that fail at both.
The pattern: weekly check-ins are operational; 1:1s are developmental. Weekly check-ins keep work flowing; 1:1s build the relationship and the career. Both matter; they require different cadences and different conversation structures. The strongest pattern in small business: run weekly check-ins as the operational rhythm, plus separate biweekly or monthly 1:1s for development conversations.
Some small teams successfully run only weekly check-ins, but they usually do so by intentionally extending one check-in per month to cover broader development topics. This is a workable simplification when calendar time is tight; it works less well as the team grows and development conversations need their own dedicated space. For the broader practice of running 1:1 meetings that complement weekly check-ins, the 1:1 meeting guide covers the conversation structure that produces meaningful development discussions over time.
Why Weekly Check-Ins Look Different for Small Business
Most weekly check-in articles are written for enterprise companies with formal performance management infrastructure, dedicated HR teams, and check-in software. The frameworks assume that someone other than the manager is providing structure, prompts, and accountability. None of that applies at small business scale, where the founder or owner is usually running check-ins themselves without supporting infrastructure.
Three implications for small business check-ins. First, the practice has to be self-sustaining. There is no HR team reminding the manager to run check-ins, no software prompting the employee to fill out a form. The cadence depends entirely on the manager's discipline. The implication: build the practice into a calendar block that is harder to skip than to keep.
Second, the founder is usually doing more check-ins than they think. A founder with 8 direct reports doing weekly 25-minute check-ins is committing 3+ hours per week to this practice. That is significant time; it should be treated as one of the most important blocks on the calendar, not as overhead to be optimized away. Founders who try to compress check-ins below 15 minutes or skip them under deadline pressure usually pay for it later in retention, alignment, and surfaced problems.
Third, the relationship density is higher. In a 12-person company, the founder's check-ins shape most employees' direct working relationship with leadership. A bad check-in pattern affects a large share of the team; a strong pattern compounds across the whole company. The leverage cuts both ways. SHRM's performance management toolkit covers the broader principles of structured manager-employee practices that apply at any organizational scale.
The 15-25 Minute Check-In Structure
The structure below produces useful check-ins consistently. It is designed to fit in 15-25 minutes and to surface the information that matters most: status, blockers, alignment for next week. Skipping segments or letting any segment run too long produces less useful check-ins.
Two rules for running the structure. First, the time allocations are guidelines, not deadlines. If blockers need 8 minutes one week, take the 8 minutes; the manager just needs to compress somewhere else. The total should stay within 15-25 minutes; the internal balance flexes with what the conversation needs. Second, the segments are sequential for a reason. Personal connection first sets a productive tone; status before blockers gives context for what is at risk; priorities last anchor the next week's work in the conversation just had. Reordering segments usually produces less useful check-ins.
For first-time managers running this structure, the practice gets faster within 4-6 weeks. The first few check-ins feel awkward and run over time; by week 6, the structure becomes natural and the conversations start producing real value. Stick with it through the awkward early weeks; the practice compounds. Gallup research on managers consistently finds that the manager-employee relationship is the strongest predictor of engagement; weekly check-ins are one of the most concrete practices for building that relationship.
Questions by Context
Generic check-in questions every week produce generic answers. The questions should match the context: new hires need different prompts than established employees, OKR check-ins focus on key result confidence, retention conversations surface different signals than performance recovery. Below are six question banks for the most common situations.
Two rules for using question banks. First, do not ask all five questions every week. Pick 2-3 that match what the employee actually needs to talk about; leave room for them to surface what is on their mind without forcing all the prompts. Second, rotate the question bank as situations change. A new hire transitions to default questions around day 60-90; an OKR check-in cycle ends and reverts to default; a high performer showing disengagement signals warrants the retention bank for a few weeks. Static question sets become ritual; rotating sets stay productive.
For the broader practice of asking effective questions in management conversations, the employee feedback guide covers feedback delivery techniques that complement check-in questions. Gallup research on feedback consistently finds that engagement rises when employees see their feedback acted on; check-in questions only produce engagement if the manager actually responds to what surfaces.
When Daily, Weekly, Biweekly, or Monthly
Weekly is the right cadence for most working relationships, but specific situations call for more or less frequency. Below is the practical decision framework.
| Situation | Cadence | Reasoning |
|---|---|---|
| New hire, first 30 days | Daily or every other day | First weeks have the highest information density. New hires need quick course-correction, not weekly waiting |
| New hire, days 31-90 | Twice weekly tapering to weekly | By day 31 the basics are clear; by day 90 they should be on the standard team cadence |
| Established employee, project active | Weekly | Default for most working relationships; matches OKR cycle and natural project rhythms |
| Established employee, stable role | Weekly check-in plus monthly 1:1 | Status weekly, broader development monthly. Both serve different purposes |
| Senior/strategic role | Biweekly check-in | Strategic work has longer feedback loops; weekly status creates noise without signal |
| Remote employee | Weekly minimum | Remote employees need more, not less, structured connection. Skipping weeks compounds isolation |
| Performance concerns | Twice weekly to daily | Performance issues require closer cadence to catch and correct before they compound |
| High performer trajectory | Weekly check-in plus quarterly career conversation | Status keeps work flowing; quarterly career time addresses the retention factor |
Three rules for cadence decisions. First, default to weekly unless context clearly calls for different. Most employees in most situations benefit from weekly cadence; deviating without clear reason usually leads to the practice degrading over time. Second, increase cadence rather than decrease in uncertain situations. New hires, performance concerns, project transitions, and remote employees all benefit from more frequent check-ins, not less. Third, the cadence is a manager decision, not an employee preference. Some employees say they do not need check-ins; usually they are wrong, even when sincere. Weekly check-ins serve the working relationship, not just the employee's stated needs.
For employees on goal cycles where check-ins integrate with OKR tracking, the how to write OKRs guide covers the goal-setting framework that gives check-ins specific content to discuss week-over-week.
A Practical Check-In Template
The template below fits in a single page (any shared document tool). Each row represents what should be captured in the running document week-over-week. The whole template is intentionally simple because complexity does not produce better check-ins; consistency does.
| Field | Why include it |
|---|---|
| Date and attendees | Basic record-keeping; useful for tracking cadence consistency over time |
| Wins this week | What got accomplished; gives the conversation a positive anchor before moving to challenges |
| Status on each priority from last week | Did last week's priorities ship? If not, why not? Direct accountability for stated commitments |
| Blockers and risks | What is in the way; what could derail; what concerns are surfacing. Highest-value field |
| Confidence on goals (1-10) | Subjective signal of how the employee is feeling about their key work; trend over weeks reveals issues |
| Priorities for next week (2-4 items) | Clear written list of what gets focused next week; shapes how the employee spends their time |
| Manager commitments | Specific things the manager will do (introduce to X, follow up on Y, decide Z by Wednesday) |
| Open questions or topics to discuss | Items the employee wants input on; ideas they want to surface; concerns to raise |
| Next check-in date | Confirms the cadence continues; never skip the scheduling |
Three rules for using the template. First, the document should be shared between manager and employee, with both able to edit. Single-owner templates produce single-owner check-ins; shared templates produce shared check-ins. Second, the document accumulates week-over-week rather than getting overwritten. Each new check-in adds a section dated and below the previous one; this creates a running record of priorities, blockers, and commitments that becomes one of the most useful management documents over time. Third, manager commitments deserve special attention. Anything the manager says they will do should be written down explicitly; without the writing, commitments evaporate within days and the employee learns that manager promises are not reliable.
For First-Time Managers
The first 6-8 weeks of running weekly check-ins as a new manager are awkward. The structure feels rigid; the conversations run over time; the employee may seem unsure of what to bring. The patterns below help first-time managers navigate the early period and build the practice into a sustainable rhythm.
The most useful single advice for first-time managers: the practice gets better with time and consistency, not with cleverness. Stick with the basic structure for the first 8-12 weeks; resist the urge to redesign the format every few weeks. The early conversations will feel uneven; that is normal. By week 8, the rhythm becomes natural, both parties know what to expect, and the conversations start producing real value. Most first-time managers who give up on weekly check-ins did so within the first month, before the practice had time to mature.
Work Institute research on retention consistently finds that the manager relationship is among the top reasons employees leave; weekly check-ins are one of the most concrete tools for strengthening that relationship over time. The investment compounds; the practice pays back across years of tenure.
Weekly Check-Ins for Remote Teams
Remote teams need more, not less, structured check-in practice than in-person teams. The informal hallway conversations that happen in offices do not exist remotely; without weekly check-ins, remote employees can go entire months without meaningful manager interaction. Below are the practical adaptations for remote check-ins.
| Aspect | In-person practice | Remote adaptation |
|---|---|---|
| Format | Often happens at desk or quick walk | Always video call (not audio only); audio loses half the signal |
| Document sharing | Sometimes paper notes or laptop | Always shared screen with check-in document during call |
| Cadence flexibility | Easy to add ad-hoc check-ins | Calendar discipline matters more; ad-hoc rarely happens remote |
| Personal connection | Naturally surfaces in office | Must be intentional; ask the personal question, do not skip it |
| Body language signals | Visible naturally | Must read facial expressions on video; harder than in-person |
| Distraction risk | Lower (in shared physical space) | Higher (employee may have other windows open); video on helps focus |
| Documentation discipline | Sometimes informal | Critical; written records are the primary continuity |
| Frequency under pressure | Easier to skip | Should not skip; remote isolation compounds faster |
Three rules specifically for remote check-ins. First, video on, always. Audio-only check-ins lose facial expression, body language, and most of the engagement signals. Both parties should have video on; if the employee resists video, address it directly rather than accepting audio-only as the new norm. Second, share the screen with the check-in document during the call. Both parties should see the same notes being updated in real time; this anchors the conversation in writing and prevents the "what did we agree to" ambiguity that emails are bad at resolving. Third, do not skip remote check-ins because of timezone difficulty or busy weeks. Skipping remote check-ins compounds isolation faster than skipping in-person ones; the absence of informal interaction means the structured check-in carries more weight.
Weekly Check-Ins During OKR Cycles
When the team is running OKRs, weekly check-ins become the engine that translates quarterly OKRs into weekly behavior. Without the check-in cadence, even well-written OKRs become forgotten documents within 6 weeks. The check-in structure adapts to make OKR progress the central thread.
| Standard check-in element | OKR-cycle adaptation |
|---|---|
| Personal connection (2-3 min) | Same; do not skip even during goal cycles |
| Status (5-7 min) | Reframe around key results: which moved, which did not, which require attention |
| Confidence score | Add explicit 1-10 confidence on each key result; track trend over weeks |
| Blockers (3-5 min) | Focus on what is at risk for specific key results; what could derail this quarter |
| Next week priorities (3-5 min) | What specifically moves each key result; commit to 2-3 measurable actions |
| Manager commitments | What the manager will do to unblock or support specific key results |
| Wrap (1-2 min) | Confirm OKR adjustments if reality has shifted significantly |
The pattern: OKR cycles do not require a different check-in structure; they require the same structure with key results as the explicit anchor. Without this anchor, weekly check-ins drift away from OKRs and the cycle becomes disconnected from daily work. With the anchor, OKRs stay alive across the full quarter. For the broader practice of writing and running OKRs at small business scale, the OKR guide covers the framework that gives check-ins their substantive content during goal cycles.
Weekly Check-Ins With New Hires
New hire check-ins follow a different cadence pattern than established employee check-ins. The first 90 days have higher information density than any other tenure stage; the cadence should reflect that. Below is the practical structure across the first 90 days.
| Period | Cadence | Focus |
|---|---|---|
| Week 1 | Daily 15-minute check-ins | What is becoming clear, what is still confusing, who have they met, immediate blockers |
| Week 2-4 | Every other day, 15-25 minutes | Onboarding milestones, role clarity, integration with team, first project progress |
| Days 31-60 | Twice weekly, 20-25 minutes | Project ownership, scope expansion, deepening relationships, surfacing structural questions |
| Days 61-90 | Weekly, 25 minutes | Standard check-in cadence, transitioning to full team rhythm |
| Day 91+ | Weekly, 15-25 minutes | Standard team cadence; new hire is now fully integrated |
The pattern: new hire check-in cadence starts at daily and tapers to weekly over 90 days. Skipping this taper produces predictable failures. New hires put on weekly cadence from day one usually accumulate confusion, miss early integration opportunities, and disengage before week 6. New hires kept on daily cadence past week 4 usually feel micromanaged. The taper is what matches the cadence to the actual information density of the period.
For the broader practice of running effective onboarding that gives weekly check-ins substantive content to discuss, the onboarding best practices guide covers the foundational structure that determines whether new hires are set up to succeed in their first 90 days.
Common Mistakes in Weekly Check-Ins
The mistakes below appear consistently across managers running weekly check-ins for the first time. All are avoidable once you understand the patterns.
The pattern across these mistakes: treating check-ins as one-way information transfer rather than as structured two-way conversations that surface the information the manager actually needs. The fix for most check-in failures is not better questions or better software; it is more disciplined treatment of what makes the practice useful: consistent cadence, employee-driven agenda, balanced talk time, written records. SHRM's research on organizational employee development consistently finds that consistent feedback rhythms outperform sporadic deep conversations; weekly check-ins are one of the most concrete applications of this principle.
Measuring Whether Check-Ins Are Working
Most managers run weekly check-ins without ever measuring whether they are actually working. The signals below let you assess whether the practice is producing value or has degraded into ritual.
| Signal | What it tells you |
|---|---|
| Cadence consistency | Are check-ins actually happening every week, or being skipped frequently? Track over a quarter; below 80% cadence consistency means the practice is failing |
| Blockers surfaced per check-in | Healthy check-ins surface 1-2 blockers most weeks. Zero blockers consistently means the employee is not surfacing real issues |
| Employee preparation | Does the employee come ready with status and questions, or does the manager have to extract information? Preparation level signals whether the practice is producing value for the employee |
| Time to resolution on blockers | How long between a blocker being raised and being resolved? Long resolution times suggest the manager is not actually acting on what surfaces |
| Quality of priorities | Are next-week priorities specific and measurable, or vague? Specificity over time signals the practice is producing real planning |
| Employee engagement signals | Does the employee bring up retention concerns, growth questions, hard problems? Open conversation signals trust; closed conversation signals the practice has lost value |
| Manager commitment follow-through | Are the things the manager said they would do actually happening? Pattern of unfulfilled commitments destroys the practice faster than almost anything else |
For most small businesses, tracking cadence consistency and time-to-resolution on blockers covers most of the diagnostic value. If both are healthy (80%+ cadence, blockers resolved within 1-2 weeks), the practice is working. If either is failing, address the underlying issue before adding more sophisticated measurement. OPM's performance management framework covers the broader principles of structured measurement that supports management practices at any scale.
Tools and Software for Weekly Check-Ins
The tooling for weekly check-ins at small business scale should be lightweight. Most teams over-engineer the tooling and under-invest in the discipline of running the practice consistently. Below is the practical breakdown of options.
| Tool | Best for | Tradeoffs |
|---|---|---|
| Shared document (any docs tool) | Most small businesses | Simple, flexible, accessible. Each employee gets one ongoing doc updated week-over-week |
| Spreadsheet template | Teams that prefer structured fields | Easier to track patterns over time; less flexible for narrative content |
| Internal wiki page | Teams already using a wiki | Integrates with other team docs; useful for cross-referencing |
| Dedicated check-in software | Larger teams with formal performance management | Built-in prompts and reminders; adds cost and complexity often unjustified at small scale |
| Calendar block only (no document) | Teams just starting | Simple to start; degrades over time as commitments are forgotten; not recommended past month 2 |
For most small businesses, a shared document per direct report (one document per employee, updated weekly with new sections at the top) covers everything. The tooling does not produce useful check-ins; the discipline of running the practice consistently does. Resist the temptation to invest in check-in software before establishing the practice; software amplifies what is working but does not fix what is broken.
How FirstHR Fits
The honest disclosure: FirstHR is not a dedicated weekly check-in or 1:1 platform. We do not have built-in check-in scheduling, prompt automation, or check-in template features. The platform handles onboarding, employee profiles, document management, org charts, and the operational HR foundations that most small businesses need. Weekly check-ins, when you adopt them, will live in your shared documents alongside your other planning notes, not in dedicated FirstHR software.
That said, weekly check-ins work better when the underlying people operations are working. A team running check-ins on top of broken onboarding will spend most of the check-in time compensating for unclear role expectations the new hires never had. A team running check-ins on top of consistent onboarding, clear documented roles, and structured employee profiles will produce check-ins that actually drive alignment and growth. FirstHR exists to handle the operational HR foundation at flat-fee pricing ($98/month for up to 10 employees, $198/month for up to 50), so that owners can focus on the higher-impact work of running consistent weekly check-ins that produce real outcomes.
For the foundation that determines whether new hires are ready for productive weekly check-ins from day one, the onboarding best practices guide covers what makes new hires arrive equipped to engage in meaningful conversations.
For the broader management foundation that weekly check-ins sit on top of, the people management guide covers running a small team without enterprise overhead.
Frequently Asked Questions
What is a weekly check-in?
A weekly check-in is a 15-25 minute structured conversation between a manager and an employee focused on this week's progress, blockers, and next week's priorities. It is the engine that keeps work aligned, surfaces problems early, and maintains the manager-employee relationship through consistent rhythm. Unlike 1:1 meetings, which are typically longer and focused on broader development, weekly check-ins focus on operational alignment: what moved this week, what is blocking, what comes next. The cadence is what makes them work; sporadic check-ins produce most of the cost without most of the benefit.
How long should a weekly check-in be?
15-25 minutes is the right range for most situations. Shorter than 15 minutes usually means skipping segments; longer than 25 minutes usually means the conversation is drifting into 1:1 territory and should be split. The structure: 2-3 minutes personal connection, 5-7 minutes status, 3-5 minutes blockers, 3-5 minutes next week priorities, 1-2 minutes wrap. Hour-long weekly meetings are a different practice; they conflate check-ins with 1:1s and dilute both. Keep weekly check-ins short and focused; have separate longer 1:1s for development conversations.
What is the difference between a weekly check-in and a 1:1?
Weekly check-ins focus on operational alignment: status, blockers, priorities. They are 15-25 minutes weekly. 1:1 meetings focus on career growth, broader development, and the manager-employee relationship. They are typically 30-60 minutes biweekly or monthly. Both practices serve different purposes; combining them produces meetings that are too long for status updates and too rushed for real development conversations. The healthy pattern: weekly check-ins for ongoing work, plus separate biweekly or monthly 1:1s for development. Some teams run only check-ins or only 1:1s; the strongest pattern uses both at different cadences.
What questions should I ask in a weekly check-in?
Five questions cover most situations: what did you accomplish this week that you are proud of, what is blocking your progress right now, what are your top 2-3 priorities for next week, what do you need from me to be successful, and on a scale of 1-5 how confident are you about hitting your current goals. The questions should match context: new hires get different questions (about clarity, surprises, hesitations) than established employees, OKR check-ins focus on key result confidence, retention conversations focus on energy and growth. Generic questions every week produce generic answers; rotate the question set based on what the employee actually needs to talk about.
How often should you have weekly check-ins?
Weekly is the default for most working relationships. New hires in their first 30 days benefit from daily or every-other-day check-ins; days 31-90 taper to weekly. Senior or strategic roles can sometimes shift to biweekly without loss. Remote employees need weekly minimum, never less. Performance concerns require closer cadence (twice weekly to daily) until issues resolve. The pattern: cadence should match the information density of the work and the experience level of the employee. Weekly is the safe default; deviate when context clearly calls for more or less frequency.
What should be in a weekly check-in template?
Nine fields produce a useful template: date and attendees, wins this week, status on each priority from last week, blockers and risks, confidence on goals (1-10), priorities for next week (2-4 items), manager commitments, open questions or topics to discuss, next check-in date. The most important fields are blockers (highest-value content), priorities (shapes next week's work), and manager commitments (creates accountability). Without a written template, check-ins become conversations that everyone forgets within 48 hours; with the template, they build on each other week over week.
Should I have weekly check-ins with new hires?
Yes, but the cadence should be more frequent than weekly for the first 30 days. New hires have the highest information density of any employee tenure stage; daily or every-other-day check-ins for the first 2-4 weeks let issues surface and resolve before they compound. By day 30, most new hires can transition to twice-weekly check-ins; by day 90, they should be on the standard weekly team cadence. Weekly check-ins from day one are too infrequent for new hires; the first month produces too many questions and unclear moments to wait a full week for resolution.
How do you do weekly check-ins with remote employees?
Same structure as in-person check-ins: 15-25 minutes, video call (not audio only), shared document for notes, weekly cadence as minimum. Remote employees need more, not less, structured connection because the informal hallway conversations that happen in offices do not exist. Skipping weekly check-ins with remote employees compounds isolation faster than it does for in-person teams. Two specific adaptations for remote: keep video on (audio-only check-ins lose half the signal), and put the shared notes document on screen during the meeting so both parties can see what is being captured.
What is the biggest mistake managers make in weekly check-ins?
Letting check-ins become status reports. When 80% of the time is the employee narrating what they did, the check-in is broken. Status updates can happen in chat or email; check-ins should be conversations focused on blockers, risks, alignment, and what the employee needs from the manager. The fix: steer the conversation away from narration toward problem-solving. The second-biggest mistake is skipping check-ins when busy. Skipping creates a pattern where check-ins become optional, the relationship erodes, and problems emerge that earlier check-ins would have surfaced. Move check-ins, do not cancel them.
How do you make weekly check-ins effective for high performers?
High performers usually do not need help with status; they need help with growth, scope, and engagement. The weekly check-in for high performers should still cover blockers and priorities (everyone needs alignment) but should leave room for retention-focused questions: what kind of work do you want more of, what is one thing the company does that frustrates you, where do you see yourself growing. Without these questions, high performers' check-ins become routine status updates and the manager misses signals of disengagement until the resignation arrives. High performers leave for opportunity, not for problems; weekly check-ins are where opportunity gets created.
Should weekly check-ins replace 1:1 meetings?
No, the two practices serve different purposes. Weekly check-ins are for operational alignment (status, blockers, priorities) at 15-25 minutes. 1:1 meetings are for broader development (career, growth, relationship) at 30-60 minutes biweekly or monthly. Replacing 1:1s with check-ins eliminates the dedicated time for development conversations; replacing check-ins with 1:1s produces hour-long weekly meetings that drift into status discussions. The strongest pattern uses both: weekly check-ins as the operational rhythm, plus separate biweekly or monthly 1:1s for development. Some small teams successfully run only weekly check-ins, but they usually do so by intentionally extending one check-in per month to cover development.
How do you handle weekly check-ins when there are performance issues?
Increase cadence first, not check-in length. Performance issues require closer feedback loops: twice weekly check-ins to daily check-ins until the issue resolves. The structure stays the same (status, blockers, priorities) but the rhythm tightens to catch problems earlier. Two rules apply specifically to performance situations. First, document the check-ins more explicitly than usual; written records of priorities and commitments matter when performance conversations escalate. Second, do not use the regular check-in to deliver formal performance feedback; that should happen in a separate, scheduled conversation. Mixing performance feedback into routine check-ins damages the practice for everyone.