September 30, 2026
A Leadership Shadow Framework for Reviewing One Difficult Interaction
Use an Interaction Review Card to separate observed behaviour, protected self-image, and untested interpretations before choosing a leadership experiment.
A leadership shadow framework can help you examine the gap between the leader you mean to be and the behaviour other people encounter. Start with one recent interaction: record what happened, separate your interpretation from observable facts, name the self-image you were protecting, and choose a small behavioural experiment. Keep the explanation provisional until you have feedback.
For an entrepreneur or team leader, the useful question is often painfully ordinary: why did I interrupt that person after asking for their view? A private reflection can make that contradiction easier to notice. It cannot tell you what someone else was thinking, prove an unconscious motive, or replace a conversation about the work itself.
Begin with the meeting, not your personality
Choose a bounded moment from the past week. A decision meeting, a delayed reply, or an uncomfortable delegation handoff gives you something you can describe. Avoid starting with a verdict such as “I am controlling.” That label is broad enough to explain everything and precise enough to change nothing. Write the words you used and the action you took instead.
You might record: “When the designer questioned the launch date, I answered before she finished and moved to the next agenda item.” This does not establish why you interrupted. It establishes an event you can revisit. Add the deadline, available information, and who held decision authority. Sometimes the explanation involves an unclear brief or an unrealistic workload as much as an inner conflict.
Use the Interaction Review Card
Set aside fifteen minutes and write one sentence under each prompt. Treat the card as a reflection aid developed for this article, not a validated assessment or a score of leadership maturity. You can leave a line unanswered rather than invent an explanation.
- Scene: Which meeting, message, or handoff am I examining?
- Observable action: What did I say or do that another person could have witnessed?
- My interpretation: What meaning did I attach to the other person’s response?
- Protected image: What did I feel I had to remain: decisive, helpful, agreeable, indispensable, or always informed?
- Alternative explanation: What practical or interpersonal explanation have I not checked?
- Impact question: What can I ask about the effect of my action without demanding reassurance?
- Next experiment: What observable action will I change in the next comparable conversation?
Keep facts and interpretations on separate lines. “Nobody spoke after my answer” is an observation. “They knew I was right” is a story. So is “They all distrust me.” Either story may feel convincing in the moment; neither follows automatically from silence. This separation is the part of the framework worth returning to when reflection starts becoming self-accusation.
Worked example: the founder who needs to sound certain
Imagine a founder, Maya, leading a launch review. She has promised investors a date and sees herself as someone who creates confidence. When a designer asks whether onboarding is ready, Maya says the team needs solutions rather than objections. The discussion ends quickly. Later, she writes that her colleagues were being negative.
On the card, Maya changes that interpretation into a question. The observable event is that she cut off a concern without asking for the underlying evidence. Her protected image might be the confident founder. An alternative explanation is that the designer knows about unresolved usability problems. Maya cannot resolve that possibility by thinking harder about her own motives; she needs to ask about the work.
Her next message is specific: “I cut across your point in the review. What onboarding problem were you trying to flag, and what evidence should we examine?” She does not ask the designer to confirm that she is a good leader. At the next review, her experiment is to hear the concern and restate it before offering a decision. The launch date may still stay unchanged, but the reason should be explicit.
Ask about impact without making someone manage your feelings
A useful feedback request names a behaviour and leaves room for an unwelcome answer. Try: “When I answered immediately, did that close off something you needed to explain?” Give the other person the option to respond later. A direct report may find it difficult to challenge the person who allocates their work, even when the invitation sounds friendly.
Amy Edmondson’s 1999 study of psychological safety and team learning found an association between team psychological safety and learning behaviour in 51 manufacturing teams. That research offers a reason to take the conditions for speaking up seriously. It does not validate this reflection card or establish that a single reflective exercise changes a team’s culture.
Choose a behaviour you can actually observe
“Be less defensive” is difficult to review. “Ask one clarifying question before defending the plan” gives you an action to notice. Other experiments might include stating uncertainty before asking for estimates, naming the decision owner before offering advice, or allowing a colleague to finish without supplying the solution. Pick the action that fits the original incident.
After two comparable conversations, record what happened. Did you perform the action? Did it reveal information you previously missed? Did the other person describe the interaction differently? Two conversations cannot demonstrate lasting change, but they can tell you whether the experiment is usable. If nothing changed, check the setting and the behaviour before concluding that you have discovered a fixed character flaw.
Keep shadow language inside its proper boundary
Use this framework for your own reflective inquiry. Calling a colleague’s disagreement “their shadow” turns an interpretation into authority and makes it harder to discuss the actual disagreement. Do not use the card to evaluate employees, demand personal disclosure, or explain away intimidation, discrimination, or other harmful conduct. Those concerns need appropriate organisational processes and qualified support.
This is coaching reflection, not diagnosis or therapy. If the exercise brings up overwhelming distress, stop and seek suitable professional support. An insight about your intentions does not settle the impact of your actions. Where a repair is needed, name the action, listen to the effect, and agree what will happen differently.
Bring one unfinished question to the next conversation
If the card gives you one clear adjustment, test it in the next comparable conversation and record what changes. If it keeps pointing to the same hidden pattern across delegation, visibility, or conflict decisions, book a Discovery Session to explore whether Jungian coaching is an appropriate container for that leadership work. If you want a private reflection first, use The Hidden Pattern Audit to trace the repeated cue before you bring it into a coaching conversation.
If your pattern is to help before understanding the request, read When Advice-Giving Becomes a Leadership Shadow Pattern. If the difficult moment comes after setting a limit, the apology reflex after a leadership boundary explores that narrower situation. Take the card into the next relevant interaction with one question still open; discovering that your first interpretation was wrong is a useful result.