In this article from psnews.com.au, Michelle explores skip-level meetings, where an employee meets with a senior executive without their direct manager present. She explains the pitfalls and possibilities, sharing practical advice to strengthen connections, support career development and protect trust across all three relationships.
Michelle Gibbings explains the pitfalls and possibilities of a skip-level meeting, where an employee meets a senior executive without the worker’s direct manager being present.
One of my clients was recently preparing for a skip-level meeting with her organisation’s senior executive.
In this case, the invitation landed in their inbox with no context or supporting details. In a highly political, complex environment, the hardest part wasn’t deciding what to say, it was working out why the meeting was happening and what they were expected to do.
Depending on where you sit, the same invitation can look like an opportunity, an assessment, a chance to connect or an unwelcome intrusion.
Because the conversation affects three relationships (the employee, their manager and the senior leader), each may arrive with vastly different assumptions about its purpose.
Done well, skip-level meetings strengthen connection, support development and give senior leaders a clearer view of what is happening across the organisation.
Done poorly, they can create suspicion, undermine the manager, expose the employee to unnecessary risk, and establish a shadow reporting line.
Relationships above your immediate reporting line matter to both your career and your ability to do your work.
A skip-level meeting does not guarantee advocacy. It does, however, give a senior leader the opportunity to understand your contribution in a broader context, offer insights you may not otherwise receive, and connect you to possibilities beyond your immediate line of sight.
Employees gain broader context about strategy and decisions, while senior leaders gain a clearer understanding of how those decisions are being experienced.
In busy, complex and increasingly hybrid workplaces, these connections may not happen naturally, so they need to be created deliberately. However, simply scheduling a skip-level meeting is not enough.
The senior leader carries particular responsibility for setting the conversation up well. They hold the most organisational power, and are best placed to remove uncertainty about why the meeting is happening.
The senior leader may genuinely want to build connection, understand what is happening closer to the grassroots, or identify emerging talent. They may also be holding the meeting because HR has asked them to, without being clear about what they want to achieve.
The employee may see it as a valuable opportunity to demonstrate their contribution, gain visibility or ask questions they cannot easily raise elsewhere. They may also use it to air frustrations about their manager or attempt to influence a decision from above.
Meanwhile, the manager in the middle may view the conversation as a healthy part of organisational life, or worry their leadership is being assessed.
None of these motives is automatically wrong. The risk arises when they remain unspoken. When the purpose is unclear, people fill the gap with their own assumptions and agendas. That’s why the senior leader needs to establish a clear starting point.
This does not mean scripting every moment or preventing other useful issues from emerging. It does mean giving everyone a shared understanding of why the meeting is happening and what it’s intended to achieve.
Naming its primary purpose creates useful boundaries, helps the employee prepare, and reassures the manager the meeting is not a covert assessment of their leadership.
The senior leader should state the purpose in the invitation and reinforce it when the conversation begins. For example: “Today is about your development, understanding where you want to grow, what experience would help and how I can support your next step. It is not a performance discussion or an assessment of your manager.”
The manager in the middle should know the conversation is happening and understand its purpose. Hearing about a skip-level meeting second-hand creates avoidable suspicion before the conversation has even begun.
The senior leader should understand what the employee works on, what they have contributed and the pressures their area is facing — enough to ask informed questions.
They should think ahead about what information may need to be acted on, shared or kept private. Deciding this during the conversation and once the issue has surfaced increases the risk of making promises they can’t keep.
It is also important they should not dominate the conversation. The employee may ask about the senior leader’s career journey and perspective, but they should not let their own stories take over.
They ought not to promise absolute confidentiality as there may be circumstances involving misconduct, safety or serious organisational risk where action is required.
If the senior leader agrees to follow up on something, do it. If the employee hears nothing further, they are unlikely to raise something important again.
Preparation is also important for the employee because, no matter where they sit in the organisational hierarchy, they play a role in shaping whether the meeting becomes a useful conversation.
The employee should seek to clarify the purpose, because if the reason for the meeting is unclear, asking whether the focus is development, connection, context or something else will help them prepare appropriately.
They should bring a question that someone at that level is particularly well placed to answer. It might relate to future direction, how competing priorities are being balanced or which capabilities will matter most in the years ahead.
It is entirely reasonable to want the senior leader to understand the value the employee brings, so they should focus on contribution rather than activity.
They should connect their work to organisational priorities, the problems they are helping solve, the outcomes they are working towards and what they have learned.
If raising a concern, they should describe what is happening, why it matters and what may help improve the situation. Avoid turning the conversation into a critique of the manager, team members or colleagues.
A useful conversation becomes even more valuable based on what happens afterwards. Where relevant, the employee should share the broad themes or actions from the meeting with their manager so it does not acquire an unnecessary sense of secrecy.
A skip-level meeting involves two people, but it affects three relationships.
The senior leader should not use the conversation to work around the manager. The employee should not use it as a shortcut around normal accountability.
The manager should not interrogate the employee afterwards or attempt to control what is discussed beforehand.
Michelle Gibbings is a Melbourne-based workplace expert and an award-winning author. She’s on a mission to help leaders, teams and organisations create successful workplaces — where people thrive and progress is accelerated. She can be contacted at support@michellegibbings.com. A fuller version of this article first appeared at https://www.changemeridian.com.au/latest-news/.