Navigating the Structural Shifts of Leadership

Leadership is rarely about technical work; it is about managing the ripple effects of structural change. When a peer becomes a manager or a mistake creates friction in a team, the immediate instinct is often to retreat or over-correct. This conversation shows that effective leaders do not suppress these tensions. They treat them as data points to be co-created. By shifting from reactive defense to proactive alignment, leaders can turn potential conflicts into institutional trust. This analysis helps mid-career managers and leaders move beyond surviving workplace dynamics to build the systems and rules of engagement that allow high-performing teams to sustain their momentum.

The Hidden Cost of Fixing the Dynamic Alone

When a structural change occurs, such as a friend becoming a direct report, the most common failure is assuming the relationship must change in a specific, often colder, direction. Muriel Wilkins notes that leaders often sweep it under the rug, which allows the awkwardness to fester. The systems-thinking approach is to recognize that the dynamic is co-created. If you assume the relationship is broken, you will act in ways that break it.

"In any types of relationships when the structure of it changes, which is what this is right? The structure has changed. The form of it has changed unless you can explicitly say, oh, because the structure has changed, here is what is going to change about the dynamic or the intangible parts of our relationship."

-- Muriel Wilkins

The downstream effect of acting like a manager by creating distance is a loss of trust. The direct report feels the wall go up, assumes the manager is withholding information, and the feedback loop of transparency is severed. The advantage lies in doing the uncomfortable work of naming the elephant in the room early. By co-creating rules of engagement, such as keeping personal and professional communication channels separate, leaders can preserve the essence of the relationship while respecting the new structural reality.

The Four-Part Architecture of Damage Control

When a mistake happens, like an accidental email CC, the immediate impulse is to apologize and move on. Wilkins argues this is insufficient because it ignores the systemic need for accountability. She outlines a four-part framework: Accept, Acknowledge, Apologize, and Act.

The Act phase is where most leaders fail. They apologize for the intent, but they do not provide a mechanism to prevent recurrence. If you cannot explain what you will change in your process to ensure the mistake is not repeated, the system remains vulnerable.

"If you cannot show that there is some action behind it, how do we have confidence that this will not happen again?"

-- Muriel Wilkins

This is a clear distinction: remorse is a personal feeling, but action is a systemic investment. By explicitly stating how you will change your workflow, such as moving sensitive feedback from email to direct conversation, you rebuild the system reliability.

Why Low-Hanging Fruit Often Masks Deeper Systemic Needs

High-energy leaders often try to sustain team motivation through additive measures, like weekly happy hours or new perks. Wilkins suggests this is a failure of systems thinking. Managers often solve for the visible problem, such as low energy, without identifying the root cause.

The competitive advantage goes to the leader who goes to the source. By asking the team what sustains their motivation, you shift from guessing to engineering. In the example provided, a team that felt bogged down by success needed creative space, not more perks. By institutionalizing a monthly problem-solving session, the leader created a low-effort, high-impact system that allowed the team to recover their creative energy without disrupting their core deliverables.

The Power of Upward Feedback Through Curiosity

Micromanagement is often treated as a character flaw in a boss, but Wilkins encourages viewing it as a habit or a reaction to a system. The non-obvious move is to use jujitsu by approaching the manager with curiosity rather than confrontation.

By asking, "Can you help me understand what is behind this request?" you force the manager to articulate their system. If they are micromanaging because they lack trust, you have identified the specific constraint. If they are doing it out of habit, you have opened a window to negotiate an experiment. This requires the patience to be vulnerable, but it avoids the defensive escalation that usually follows a direct demand to stop micromanaging.

Key Action Items

• Co-create Rules of Engagement: Within the next week, sit down with any direct report who was previously a peer. Explicitly define what will change and what will remain the same regarding your friendship. (Immediate)
• Apply the Four A’s: When a mistake occurs, move past the apology. Identify the specific process change, the Action, that prevents this specific error from recurring. (Immediate)
• Audit Your Motivation Systems: Instead of assuming what your team needs, ask them specifically: "What is one thing we could change that would give you more energy in your daily work?" (Next 30 days)
• Use Curiosity as a Hedge: When faced with a micromanager, use the jujitsu approach. Next time they redo your work, ask for the specific context behind their request before defending your own. (Next 2-3 interactions)
• Establish Communication Boundaries: If you are in a new management role, set clear expectations for how and when you communicate with friends on your team to avoid the perception of favoritism. (Ongoing/Next 14 days)