Should One-on-Ones Be Status Meetings? What Managers Should Discuss Instead

A manager sits down for a weekly one-on-one and starts with a familiar set of questions:

"What did you finish this week?"

"Where are we with the client project?"

"When will the report be ready?"

"What are you working on next?"

Thirty minutes later, the manager knows exactly where every project stands. But they may know very little about how the employee is actually doing. That is the problem with turning one-on-ones into status meetings.

Project updates can be part of a one-on-one when they provide useful context. Managers need to understand what employees are working on, where problems are developing, and whether priorities are realistic. But routine project-status reporting should generally not consume the meeting.

There are usually better ways to track tasks and deadlines. One-on-one time is more valuable when managers and employees use it for conversations that require individual attention, such as feedback, support, workload, development, motivation, blockers, and working relationships.

The goal is not to eliminate project discussions. It is to use them differently.

What Is a Status Meeting?

A status meeting is primarily designed to understand the current state of work.

It usually answers questions such as:

• What has been completed?
• What is currently in progress?
• What is delayed?
• What is coming next?
• Who owns each task?
• What is the deadline?
• Is the project on track?

Those are useful questions. Managers need this information to coordinate work and make decisions.

However, they are not necessarily the best use of a private one-on-one.

A one-on-one should go beyond what is happening and explore questions such as:

• What is making the work difficult?
• Does the employee have the support they need?
• Are priorities realistic?
• Is the workload sustainable?
• What feedback would help?
• What does the employee want to learn?
• Are there team or communication problems?
• Is there anything the manager could do differently?

A status meeting primarily tracks the work.

A one-on-one should help managers understand the employee's experience of the work.

So, Should One-on-Ones Be Status Meetings?

Generally, no.

Some status discussion is normal and often useful. Managers need enough context to understand what the employee is dealing with.

The problem begins when reporting progress becomes the main purpose of the conversation.

Consider the difference between these questions:

"What's the status of the project?"

and:

"What's making this project difficult right now, and where could I help?"

The first question asks for information.

The second uses the project to start a deeper conversation.

Another example:

"When will this be finished?"

It is primarily a deadline question.

But:

"Is anything preventing you from meeting the timeline?"

invites discussion about blockers, workload, unclear expectations, dependencies, or support.

That is the distinction managers should make.

Project status can provide context for a one-on-one. It should not become the entire purpose of the meeting.

The American Press Institute also recommends making one-on-ones about development rather than status updates. Its guidance suggests using these meetings for listening, coaching, feedback, and professional growth while allowing employees to take an active role in the agenda. Regular, employee-focused conversations can strengthen trust, engagement, and development far more effectively than simply reviewing project progress.

Why One-on-Ones So Easily Turn Into Status Meetings

Even managers who understand the purpose of one-on-ones can gradually turn them into project reviews.

There are several reasons this happens.

1. Status Is Easy to Discuss

Projects give managers something concrete to talk about.

There are deadlines, tasks, milestones, and deliverables.

It is much easier to ask:

"Did you finish the proposal?"

than:

"What part of your role has been frustrating you lately?"

Topics such as motivation, career development, relationships, feedback, and workload require more thought and often more trust.

Because project status is easier to discuss, it can slowly take over the conversation.

2. Managers Want Visibility

Managers need to know what is happening across their team.

If there is no reliable system for tracking work, one-on-ones may become the place where managers collect that information.

The problem is not the manager's need for visibility. The problem is using valuable one-on-one time as the only way to get it.

3. Employees Think They Are Supposed to Report

If managers never explain the purpose of the meeting, employees may naturally assume:

"This is where I tell my manager what I've been doing."

They prepare a list of completed tasks and current projects.

The manager asks questions.

The employee reports.

Over time, this pattern becomes normal.

4. Status Feels Productive

A list of updates creates a visible sense of progress.

Tasks can be checked off. Deadlines can be confirmed. Decisions can be recorded.

A conversation about motivation or career goals may not produce such an obvious outcome.

That can make status discussions feel more productive, even when they are not the most valuable use of the meeting.

5. Status Helps People Avoid Difficult Conversations

Talking about project progress can also be a convenient way to avoid uncomfortable subjects.

It is often easier to discuss:

• Deadlines.
• Deliverables.
• Client requests.
• Project plans.

than:

• Poor performance.
• Workload concerns.
• Frustration.
• Career dissatisfaction.
• Conflict.
• Feedback for the manager.

A one-on-one can appear busy and productive while both people quietly avoid what actually needs to be discussed.

What Happens When Every One-on-One Becomes a Status Meeting?

A status-heavy one-on-one may still yield useful information, but important parts of the manager-employee relationship begin to disappear.

Employees Stop Bringing Their Own Topics

When the manager spends most of the meeting asking about projects, the employee learns what the meeting is really for.

They may stop bringing:

• Questions.
• Concerns.
• Feedback.
• Career topics.
• New ideas.
• Development interests.

The meeting begins to feel like the manager's time rather than a shared conversation.

Important Problems Stay Hidden

A project can be technically on track while the employee is struggling.

The employee may be:

• Working unreasonable hours.
• Frustrated with another team.
• Unsure about priorities.
• Losing motivation.
• Feeling disconnected.
• Having difficulty with the manager's communication style.

A status report can show that the work is moving.

It cannot always show what it is costing the person doing it.

Career Development Gets Pushed Aside

Development conversations rarely feel as urgent as project deadlines.

That makes them easy to postpone.

A manager may say:

"Let's talk about your career goals next week."

Then another deadline appears.

Next week becomes next month, and eventually, development only comes up during a formal review.

Employees need opportunities to discuss growth before they become dissatisfied with their current role.

Feedback Becomes One-Directional

Status meetings often put the manager in the role of question-asker.

The manager asks for information. The employee answers.

That structure can make it harder for employees to say:

• "I need more context from you."
• "That process isn't working."
• "I'm confused by how priorities are changing."
• "Your feedback came too late."
• "I need more independence."

A one-on-one should allow information and feedback to move in both directions.

The Meeting Becomes Redundant

If the employee has already updated:

• A project-management system.
• A shared dashboard.
• A weekly written report.
• A team stand-up.

Repeating the same information during a one-on-one creates little additional value.

The employee may reasonably wonder why the meeting is necessary.

The Manager Knows the Work but Not the Employee

This is perhaps the biggest problem.

A manager can know:

• Every deadline.
• Every project.
• Every deliverable.
• Every upcoming task.

and still know very little about:

• What motivates the employee?
• What frustrates them.
• What they want to learn.
• What support do they need?
• How they experience the team.
• Where they want their career to go.

Good management requires more than project visibility.

When Project Updates Do Belong in a One-on-One

Project discussions are not automatically wrong.

They become valuable when they help the manager understand or support the employee.

When the Status Reveals a Blocker

Suppose an employee says:

"The project is behind because I'm waiting for another team to approve the design."

The useful conversation is not simply about the delay.

The manager can ask:

• "How long have you been waiting?"
• "Is this happening regularly?"
• "Would it help if I stepped in?"
• "Is the dependency affecting other priorities?"

The project status exposes a support problem.

That belongs in a one-on-one.

When Workload Is Becoming Unrealistic

An employee may be managing several projects that are individually on track but collectively unsustainable.

Status information can help managers notice that.

The conversation can then move toward:

• Prioritization.
• Capacity.
• Deadlines.
• Delegation.
• Removing unnecessary work.

Instead of asking:

"Can you still finish everything?"

ask:

"Which priorities are competing for your attention, and what should we reconsider?"

When Priorities Conflict

Employees do not always need more effort. Sometimes they need a decision.

If two urgent projects require attention at the same time, the manager can help clarify which one matters most.

That is a good use of a one-on-one because the project discussion leads to clearer expectations.

When the Employee Needs a Decision

A project may be stuck because the employee needs:

• Approval.
• Resources.
• Direction.
• A decision from leadership.
• Access to another team.

The one-on-one can be used to identify that need and remove the blocker.

When the Work Creates a Coaching Opportunity

Projects often provide useful material for development.

For example:

"You handled the client presentation well. Would you like more opportunities to lead those conversations?"

or:

"You mentioned that planning the project was difficult. Is project planning a skill you'd like to develop?"

The project becomes a doorway into growth rather than simply an item on a checklist.

When Performance Needs to Be Discussed

Specific work results can provide important evidence during performance conversations.

For example:

"The last three reports were submitted after the agreed deadline. Let's talk about what's causing that and what needs to change."

That is different from reviewing every task simply to confirm completion.

The principle is straightforward:

Discuss the project when it helps you understand, coach, support, or give useful feedback to the employee.

Turn Status Questions Into Better One-on-One Questions

Managers often do not need to stop talking about work.

They simply need to change the questions.

The difference is not complicated.

Status questions collect information.

Better one-on-one questions use that information to understand what the employee needs.

Where Should Routine Status Updates Happen?

If managers stop using one-on-ones for routine reporting, they still need a reliable way to understand what is happening.

There are several options.

Project-Management Tools

A shared project system can track:

• Tasks.
• Owners.
• Due dates.
• Project stages.
• Dependencies.

This allows managers to check progress without asking employees to repeat information aloud.

Shared Dashboards

Dashboards can work well when managers need visibility across several projects or employees.

They are especially useful when the same metrics need to be reviewed regularly.

Written Weekly Updates

A short asynchronous update can include:

• What was completed?
• What is in progress?
• What's blocked?
• What happens next?

This keeps the one-on-one from becoming a verbal version of the same report.

Team Stand-Ups

Short stand-ups can help teams coordinate immediate work and identify blockers.

Detailed personal issues can then move to the one-on-one.

Project Meetings

Complex projects may need dedicated meetings where the right people can discuss:

• Dependencies.
• Deadlines.
• Technical decisions.
• Risks.
• Responsibilities.

Trying to conduct those conversations during individual one-on-ones can be inefficient.

Managers do not need all of these systems.

Choose the simplest approach that provides enough visibility without forcing employees to repeatedly report the same information.

How Much of a One-on-One Should Be About Status?

There is no universal percentage.

A fast-moving team may need more project discussion than a stable team. A new employee may need more guidance than an experienced employee. A major deadline may temporarily require more operational conversation.

The better test is this:

Does project reporting regularly consume most of the meeting?

If the answer is yes, the balance probably needs adjustment.

A 30-minute one-on-one might look something like this:

First 5 Minutes: Check-In and Immediate Priorities

Briefly discuss urgent work.

Use status only where context is necessary.

Next 10 Minutes: Employee Topics and Challenges

Give the employee room to lead.

Discuss:

• Blockers.
• Questions.
• Workload.
• Concerns.
• Team relationships.

Next 5 Minutes: Feedback and Manager Support

Ask:

• "What could I help with?"
• "Is there anything you need differently from me?"
• "Is there feedback we should discuss?"

Next 5 Minutes: Development and Longer-Term Topics

Talk about:

• Skills.
• Career interests.
• Motivation.
• New responsibilities.
• Learning opportunities.

Final 5 Minutes: Decisions and Follow-Up

Clarify:

• What needs to happen next?
• Who owns each action?
• What should be revisited later?

This does not need to be followed minute by minute.

A meaningful conversation should be allowed to take more time when necessary.

What Should One-on-Ones Focus On Instead?

Once routine reporting moves elsewhere, managers can use the meeting for conversations that are harder to have through tools or team meetings.

Challenges and Blockers

Ask:

• "What's getting in your way?"
• "What has been harder than expected?"
• "Where do you feel stuck?"

The goal is to identify what employees cannot solve on their own.

Workload and Priorities

Ask:

• "Which priority is taking more time than expected?"
• "Is anything becoming unsustainable?"
• "What could we deprioritize?"
• "Are expectations clear?"

Workload problems are easier to solve before they become burnout or performance problems.

Feedback

One-on-ones should make room for feedback in both directions.

Managers can give specific feedback while also asking:

• "What could I do differently?"
• "Where could I communicate more clearly?"
• "Was there anything you needed from me that you did not get?"

Development

Discuss:

• Skills the employee wants to build.
• New responsibilities.
• Stretch assignments.
• Career direction.
• Learning opportunities.

Development should not be limited to annual reviews.

Motivation

Ask:

• "What part of your work has been most energizing?"
• "What has been frustrating?"
• "What would you like to do more often?"
• "Has anything started to feel repetitive?"

Employees' motivation can change long before their performance visibly changes.

Team Relationships

One-on-ones provide a useful space for discussing collaboration.

Ask:

• "Where is teamwork going well?"
• "Where are handoffs becoming difficult?"
• "Is there anyone you need better communication with?"

Focus on work behavior and impact rather than gossip.

Manager Support

Sometimes the most useful question is simply:

"What do you need from me?"

The answer may involve:

• A decision.
• Context.
• Resources.
• Advocacy.
• Feedback.
• Greater autonomy.

Recognition

Do not reserve one-on-ones only for problems. Tell employees what they are doing well and why it matters. Specific recognition helps reinforce effective behavior.

The exact balance can vary depending on the purpose and cadence of the conversation. Different formats, including weekly, remote, career-development, performance, and new-hire meetings, may need different agendas. For a broader framework, see our guide to different types of one-on-one meetings.

Signs Your One-on-One Has Become a Status Meeting

Managers may not notice when the meeting gradually shifts toward reporting.

Watch for these signs:

• Most questions are about tasks and deadlines.
• The employee mainly lists what they completed.
• The same information already exists somewhere else.
• Career development rarely comes up.
• The employee rarely gives feedback.
• You know little about the employee's motivation or longer-term goals.
• The employee almost never adds topics to the agenda.
• Every meeting follows the same project checklist.
• Problems are discovered elsewhere, not in the one-on-one.
• The conversation feels like a duplicate of a team meeting.
• The meeting regularly ends once project updates are finished.
• Cancelling the meeting would not meaningfully affect the manager-employee relationship.

If several of these sound familiar, the problem may not be the frequency of your one-on-ones. It may be what you are using them for.

How to Stop Your One-on-One From Becoming a Status Meeting

You do not need to redesign the entire process.

A few practical changes can shift the conversation.

Step 1: Move Routine Reporting Elsewhere

Choose a simple place for project status.

This might be:

• A project tool.
• A weekly written update.
• A team meeting.
• A shared dashboard.

Avoid requiring employees to report the same information in multiple places.

Step 2: Explain the Purpose of the One-on-One

Do not assume employees know what the meeting is meant to accomplish.

Tell them.

For example:

"I can see most of the project status in our tracker. I'd like to use this time for challenges, feedback, support, development, and anything you want to raise."

That simple explanation can change what employees prepare for the meeting.

Step 3: Give Employees Agenda Ownership

Allow employees to add topics before the meeting.

You can begin with:

"What would be most useful for us to discuss today?"

This signals that the employee is not simply there to answer questions.

Step 4: Change Your Questions

Move from:

"What did you finish?"

to:

"What did you learn?"

Move from:

"Are you on track?"

to:

"What's making it difficult to stay on track?"

Move from:

"What are you working on next?"

to:

"Do your current priorities make sense?"

Small changes in questions can produce much richer conversations.

Step 5: Protect Time for Longer-Term Topics

Urgent work will always exist.

If career development is discussed only after every project issue has been resolved, it may never happen.

Make space periodically for:

• Career goals.
• Skills.
• Motivation.
• New responsibilities.
• Long-term development.

Step 6: Follow Up

If an employee raises a blocker or concern, act on it.

Either:

• Take action.
• Explain why action is not possible.
• Clarify who owns the next step.
• Return to the subject later.

Employees are more likely to use one-on-ones meaningfully when they see that meaningful conversations lead somewhere.

Step 7: Review the Meeting Periodically

Ask:

"Are these conversations useful?"

and:

"What should we spend more or less time discussing?"

One-on-ones should evolve as employees' needs change.

The Right Balance Depends on the Employee

Not every one-on-one needs the same level of project discussion.

New Employees

New hires often need more frequent discussion of:

• Priorities.
• Expectations.
• Progress.
• Processes.
• Responsibilities.

This can be useful because they are still learning how the organization works.

However, their meetings should also include:

• Onboarding questions.
• Feedback.
• Support.
• Team relationships.
• Early development.

High Performers

High performers may need less detailed status reporting.

Managers can use more time for:

• New challenges.
• Career development.
• Greater autonomy.
• Recognition.
• Leadership opportunities.

Constant task checking can feel unnecessarily controlling.

Employees Struggling With Performance

Specific work results may need more attention.

The manager should discuss:

• Expectations.
• Actual results.
• Gaps.
• Causes.
• Support.
• Required changes.

But even here, the meeting should not become a simple checklist of completed and incomplete tasks.

The goal is to understand why the gap exists and what needs to change.

Remote Employees

Remote managers may feel a stronger need for visibility because they cannot see day-to-day activity.

That can easily turn remote one-on-ones into monitoring sessions.

Focus on:

• Outcomes.
• Communication.
• Blockers.
• Workload.
• Connection.
• Support.

Remote work should not automatically justify more detailed surveillance.

Experienced Employees

Experienced employees often need less operational supervision.

Repeatedly asking for detailed task reports may feel like micromanagement.

Their one-on-ones may be more valuable when focused on:

• Strategic work.
• Development.
• Decision-making.
• Broader responsibilities.
• Organizational challenges.

Managers need visibility into work.

That does not mean employees should spend every one-on-one repeating project information that their manager could have reviewed elsewhere.

Project status belongs in the conversation when it provides context for something more meaningful, such as a blocker, a workload issue, a difficult priority, a coaching opportunity, a performance concern, or a decision.

Routine reporting can usually happen through project tools, written updates, dashboards, or team meetings.

Use one-on-one time for the conversations that those systems cannot replace.

Talk about:

• What is making the work difficult?
• Where does the employee need support?
• Whether priorities are realistic.
• What feedback needs to be shared?
• How is the employee developing?
• What motivates or frustrates them?
• What may the manager be missing?

A status meeting tracks the work.

A strong one-on-one uses the work to understand and support the person doing it.