← ALB News · curated headline

Skip-Level Meetings: Benefits, Risks, and Design Considerations Informed by Bypassed Managers' Experiences

arXiv Software Engineering · WORLD · Compilers · 11/19/2026, 12:00:00 AM

arXiv:2611.23271v1 Announce Type: new Abstract: Skip-level meetings (SLMs), bidirectional, relationship-oriented meetings between employees and managers two or more levels above, are common but not universal, and often recommended in professional outlets. They entail benefits and risks for employees, direct and skip-level managers, and organizations, with multiple factors related to shaping the value-risk balance and appropriate approach. However, SLMs have received limited scholarly attention, particularly regarding bypassed managers' views of that managerial practice. This exploratory qualitative study examined the experiences and perspectives of 25 first-tier software engineering managers from diverse personal and organizational contexts in the multicultural, dynamic, innovation-driven, and high-turnover U.S. tech sector as bypassed managers in SLMs between their direct reports and these reports' second-tier managers. Their accounts, integrated with directly related literature, as well as on intersecting topics such as employee voice, psychological safety, and cultural and generational differences, revealed broad support and preference for exclusion from SLMs, contrary to concerns in prior literature, broad implementation, and high sensitivity to design and contextual factors, such as the significance of follow-up involvement and of individual backgrounds. Findings position SLMs not as a universally beneficial managerial practice, but as context-dependent, requiring deliberate design and implementation, or avoidance. The study extends limited research on SLMs and hierarchy-bypassing interactions, recommends directions for further research, and offers evidence-informed guidance for deciding whether and how to use SLMs to maximize value while mitigating risks.

Continue to arXiv Software Engineering →

You are being forwarded in 6s — stay on this page