Manager Operating System (Part 2): Running Better 1:1s, Team Meetings & Pipeline Reviews
Meetings are among the most familiar parts of management, but familiarity does not guarantee effectiveness. In this session, Mike Bates, Director at Vector People Consultants, explored how managers can improve one-to-ones, team meetings and pipeline reviews through clearer purpose, stronger participation and more consistent follow-through.
The challenge is rarely a lack of knowledge. Most managers understand that meetings need an agenda, actions and accountability. The problem is applying those principles consistently when calendars are crowded, priorities compete and established habits are difficult to change.
Start by questioning why the meeting exists
Many businesses continue to hold meetings because they have always held them.
The weekly update, monthly sales meeting or recurring pipeline review remains in the calendar, even when its purpose is unclear. Over time, the discussion becomes repetitive, attendees disengage and the meeting becomes an information-sharing exercise rather than a tool for making progress.
Every meeting should answer two questions:
Why are we meeting?
What must be different by the end?
A useful meeting should lead to a decision, an action, a change in direction or a clearer understanding of an important issue. If the same outcome can be achieved through a dashboard, written update or shared document, a meeting may not be necessary.
Use the four Ps to create meeting discipline
A simple framework can help managers improve almost any recurring meeting.
Purpose
Define the reason for the meeting and the outcome it needs to produce.
Avoid broad objectives such as providing updates. Be clear about what needs to be decided, challenged, resolved or progressed.
Prepare
Decide what attendees need to know or consider in advance.
Preparation does not need to involve lengthy reports. A short summary or two focused questions may produce better thinking than a large information pack that nobody has time to read.
Managers should also tell people in advance when they are expected to lead an item or bring a recommendation.
Participate
Be explicit about how people will contribute.
A meeting is not effective simply because the right people are present. Managers need to create an expectation that attendees will discuss, challenge or decide.
Quieter team members may benefit from seeing questions beforehand. More vocal participants may need to pause and create room for others. Silence does not always indicate a lack of ideas. Some people need time to process before contributing.
Progress
Finish with clear ownership.
Confirm what has been agreed, who will act, when the action will be completed and how progress will be reviewed.
Without this step, a meeting may feel productive while producing little real change.
Make accountability visible
Actions often fail because ownership remains vague.
A group may agree that something needs to happen, but nobody leaves with direct responsibility for delivering it. At the next meeting, the same subject is discussed again.
Managers can prevent this by summarising commitments before the meeting ends. Each action should have one clear owner and a realistic deadline.
Those actions must then be reviewed. Accountability weakens quickly when people learn that commitments will not be revisited.
However, managers should also examine the volume of work being assigned. If every request is treated as a priority, teams will struggle to distinguish what matters most. Strong accountability requires clear prioritisation as well as clear ownership.
Treat one-to-ones as shared meetings
A one-to-one should not be a meeting that the manager organises and the employee passively attends.
Both people should prepare. The employee should be ready to discuss progress, priorities, concerns and support. The manager should understand what needs attention and what outcome the conversation should produce.
Across a regular cycle of one-to-ones, managers should cover three areas:
- Performance.
- Development.
- Wellbeing.
The balance will change depending on the person and the situation. A pressing performance issue may require most of the available time, while another conversation may focus on workload or development.
The important point is that none of these areas should be neglected over time.
Use a simple structure for better one-to-ones
A consistent structure helps managers cover what matters without making the conversation feel mechanical.
Check in properly
Begin by understanding how the person is doing.
A generic question can easily produce a generic answer. Managers should be specific and pay attention to whether the employee’s words match their tone and body language.
Where trust exists, it is reasonable to explore further when something does not appear right.
Review progress
Look back at what has changed since the previous conversation.
Discuss completed actions, areas of movement and commitments that remain unresolved. A simple red, amber and green status can make progress easier to assess.
Look beyond the immediate week
Recruitment teams can become absorbed by urgent vacancies, live deals and daily delivery demands.
Managers should help people scan further ahead. Upcoming client reviews, sales targets, reporting deadlines and quarterly priorities should be considered before they become urgent.
Identify what is getting in the way
Ask directly about obstacles.
These may include workload, unclear decisions, dependencies or a lack of confidence. The manager may also be contributing to the problem through too much control, insufficient support or slow approvals.
One useful question is: how do you need to be managed?
Different people require different levels of autonomy, direction and contact. Employees may need time to consider their answer, but the discussion can help managers adapt their approach.
Agree the right support
Managers should help people perform without taking over their responsibilities.
In a fast-moving recruitment business, it can be tempting for an experienced manager to step in and complete a task because it appears faster. This may solve the immediate issue, but it can also reduce ownership and prevent the employee from building capability.
Support should remove obstacles, provide direction and improve confidence without creating dependence.
Close with commitment
Protect the final few minutes of the one-to-one.
Summarise what the employee will do, what the manager will do, when actions are due and what will be reviewed next time.
This creates clarity and brings the conversation to a deliberate close rather than allowing it to end abruptly when the next meeting begins.
Match the cadence to the team
There is no single correct length for a one-to-one.
A practical model may include a short weekly check-in of around 20 minutes, supported by a more detailed monthly conversation. Additional time can be provided when a significant issue requires it.
Managers should consider team size and individual need. Eight one-hour meetings every week would consume a full working day and may not represent the best use of management time.
Frequent conversations should support autonomy rather than encourage employees to seek approval for every decision.
A useful opening question is: what is the most important thing we need to discuss today?
This gives the employee meaningful input while allowing the manager to protect time for essential business issues.
Shorten team updates and increase contribution
Weekly team meetings often lose value because updates are too long.
A more focused meeting may ask each person to explain their priorities in two or three minutes, followed by discussion of risks, challenges or support required.
This approach can reduce a 60-minute meeting to 30 minutes while increasing relevance.
Managers should design the meeting around the week ahead rather than asking everyone to provide a detailed account of activity. Routine information can be shared elsewhere. Meeting time should be used for discussion, decisions and coordination.
Give people permission to move on
Some discussions continue after the point has been made.
ELMO, meaning “enough, let’s move on”, is a simple way to signal that a conversation has become repetitive, moved away from the agenda or reached a level of detail that is no longer useful to the group.
The method only works when it is agreed in advance and used respectfully. Its purpose is not to silence people. It protects time and helps the team maintain focus.
Turn pipeline reviews into action reviews
Pipeline reviews should not become a detailed narration of every opportunity.
The most useful questions are:
- What has changed?
- Where are you stuck?
- What requires a decision?
- What is the next meaningful action?
A red, amber and green system can provide enough visibility without creating unnecessary complexity.
A team review may encourage shared problem-solving and create useful social accountability. An individual review may be better suited to sensitive or detailed discussions. Recruitment leaders can separate pipeline reviews from one-to-ones or combine them, depending on the needs of the business and the individual.
Whatever format is chosen, the review should remain light touch. The aim is to help consultants progress their pipelines, not to consume time that could be spent taking action.
Build the habit before judging the result
Better meetings are built through consistent practice.
Sending questions in advance, limiting updates, involving quieter voices and closing with clear actions may initially feel unnatural. Team members may also resist changes to familiar routines.
Managers should give a new structure enough time to settle. Testing it consistently for a month provides a better basis for evaluation than abandoning it after one or two meetings.
The principles are straightforward: establish a purpose, prepare people, create meaningful participation and finish with progress.
The commercial value comes from applying them repeatedly.