Companies mistakenly bundle management with authority, forcing top performers onto a management track to gain influence. Separate them. Define management's role as coordination and context-sharing, allowing senior individual contributors to drive decisions without managing people.

The traditional view of HR as a support function is obsolete. In today's talent-driven economy, HR leaders must act as strategic business partners, using commercial acumen and analytical rigor to shape the company's direction, not just execute existing priorities.

The debate over whether Go-to-Market Engineering (GTME) should report to RevOps is a distraction. The focus should be on creating clear job descriptions, a system for alignment, and a shared roadmap. Where the role sits organizationally is secondary to how it functions and collaborates.

The need for a Solution Architect often signals a failure in organizational design. It's a workaround for teams not communicating effectively, a problem better solved by applying principles from frameworks like Team Topologies to foster cross-team collaboration directly.

Many leaders fight bureaucracy like an external threat. The real cause is the organization's design: too many layers, functional silos, and distant decision-making. To fix bureaucracy, you must fundamentally change the organizational structure, not just treat symptoms.

The process of clarifying roles is itself a decision-rights question that is typically unowned. This creates a paradox where the organization is stuck in turf wars because the very authority required to solve the problem is what's in dispute. The system lacks a mechanism to fix itself.

Job descriptions are poor approximations of your actual work. A disconnect between what you do, what your boss thinks you do, and what your team needs creates friction. Proactively discussing and defining the real job with stakeholders is a neutral and highly productive conversation to improve performance and happiness.

Brad Jacobs designs org charts based on the optimal structure for achieving goals, defining necessary roles first. He resists shaping the chart around existing employees and their "fiefdoms." This role-first approach means leaving a seat empty is preferable to filling it with a poor fit, ensuring the structure dictates personnel, not the other way around.

Instead of asking employees what they do, map your core business processes (e.g., customer acquisition). Then, assign each step to a person. This bottom-up approach reveals who is truly driving value and who is overburdened, leading to more accurate role definitions based on business impact.