A nine-month scaffolded leadership case study. You will serve as an advisory team supporting a director navigating real consequences inside a growing, pressured organization. Each month reveals what happened next.
This case study runs the full length of the Threshold program. Each month you receive a new scene from inside Northstar. The story mirrors how real organizational problems develop: slowly, invisibly, and then all at once. Your job is not to solve the problem. Your job is to help one leader see it clearly enough to begin.
You are an advisory group of three to four people supporting Director Alex Morgan inside Northstar Services. You are not consultants brought in to fix the organization. You are not Alex's supervisor. You are not problem-solvers.
You are functioning as mentor leaders: experienced peers who can see what Alex cannot yet see, who are close enough to be trusted and far enough to be honest. Think of yourselves as a small, high-trust advisory board for one leader trying to navigate something genuinely hard.
Your three functions are:
You are not here to rescue Alex. You are not here to fix Northstar. You are here to help one leader grow in real time, inside a real system, with real consequences already in motion.
One more thing before you begin. Your advisory group is not going to agree on everything. That is not a problem. It is the point. When your Challenger says something that makes the Observer uncomfortable, when the Interpreter's read on Alex's intent conflicts with the Regulator's read on Alex's emotional state, work through it rather than around it. The skills you are building for Alex, naming what is hard to name, holding tension without collapsing it into false consensus, staying curious when the instinct is to defend, those are the same skills your advisory group needs to practice right now. Disagreement inside this room is evidence that the work is real.
Each month follows the same rhythm:
Your group receives new case material and works through the assigned tasks independently. No facilitator guidance during this time. The group is expected to read the material carefully, use the advisory roles assigned, and produce a real group output, not a rough sketch.
Groups come back together with the facilitator. Each group shares their primary findings, tensions, and questions. The facilitator connects the case back to the frameworks you have been learning and surfaces transfer to your real organizations.
Every month ends with a group deliverable. That deliverable is shared with the facilitator at the debrief. It should be specific, evidence-based, and built from the case material you have been given. You will not be asked to make things up. All the information you need is in the case. If your group finds itself speculating rather than analyzing, go back to the material.
Northstar Services is a mid-sized, multi-location organization providing operational and support services across four regions. Over the past three years, Northstar expanded from 5 to 14 locations, doubled revenue, added two service lines, and promoted multiple internal leaders into management roles. From the outside, Northstar looks like a success story. Internally, it feels different.
Vision-driven, growth-focused. Believes Northstar has strong people who just need to execute better. Does not yet see the systemic patterns building underneath the metrics. Will act when the cost becomes visible.
Operationally sharp and increasingly frustrated with inconsistency. Has been pushing for more structure but getting limited traction. Watching Alex's region more carefully than Alex knows. Will not stay quiet when the cost becomes concrete.
Every month you produce one advisory artifact. These are not worksheets. They are the cumulative record of your group's thinking across the full engagement. By Month 9, your portfolio will tell a complete story: what you saw, what you diagnosed, what you recommended, what the evidence showed, and what Northstar must build next. Nothing you produce is a one-and-done deliverable. You will return to earlier artifacts. You will revise them. That is the point.
Before a leader can fix a system, they have to stop distorting it. This month you observe Alex in a real leadership meeting, three weeks into the Director role. Your job is not to judge what you see. Your job is to see it clearly and help Alex understand what is happening and why it matters.
You are mentor leaders. Alex has not asked for your help yet. You are observing, analyzing, and preparing. By the end of this session your group will produce a Leadership Awareness Brief: a clear, evidence-based picture of Alex's patterns, triggers, and leadership risks. This will be the foundation everything else is built on. Take it seriously.
Alex Morgan has been in the Director role for twenty-two days. The promotion came after five years as a high-performing regional manager. Alex's former team hit its targets consistently. When things broke down, Alex fixed them. When people struggled, Alex stepped in. Senior leadership noticed the results and promoted accordingly.
What senior leadership did not fully account for was what drove the results. Alex's former team delivered because Alex was deeply embedded in every decision. Not by design. By instinct. When something felt uncertain, Alex moved toward it. When a team member hesitated, Alex took over. When a problem surfaced, Alex solved it before anyone else had a chance to.
The team performed. The team also stopped developing. Nobody noticed because the numbers were good.
Now Alex is a Director, responsible for multiple managers across multiple sites. The volume of work that Alex used to absorb personally is now many times larger. The instinct that served Alex as a manager has followed Alex into this role. It is already creating problems that Alex cannot yet see.
The following is a reconstructed account of a regional leadership meeting held in Conference Room B at Northstar's central office on a Tuesday morning. Eight people are present: Alex, four site managers (Marcus, Priya, Devon, and Kayla), the operations lead (Simone), the people services lead (Thomas), and a note-taker. Riley stops in briefly at the forty-minute mark.
"The team has strong people but I think we need to tighten up our execution culture. I've been stepping in where needed to keep momentum going while we get everyone aligned. I feel good about the direction. The challenge is getting everyone operating at the pace and standard the region needs. I'm going to focus on accountability structures next."
Use the expandable sections below if your group has questions about specific aspects of the case. These provide additional context that may help your analysis.
Marcus: Four years at Site 4. Highest tenure on the team. Was a finalist for the Director role Alex received. Has not said this aloud to anyone at Northstar but it is known. Performs well. Has a reputation for being methodical and thoughtful. Responds poorly to being rushed.
Priya: Two and a half years at Site 3. Strong technical skills. Described by her team as the most reliable manager in the region. Has a habit of raising systemic issues that others avoid. Peers trust her judgment. Senior leadership sometimes finds her "challenging."
Devon: Eighteen months at Site 2. Still growing into the role. Has benefited significantly from mentorship. Watches how senior people navigate before deciding how to respond. The parking lot moment in the meeting registered.
Kayla: Three years at Site 6. Strong relationship manager. Avoids conflict. Her instinct when stressed is to resolve quietly and report after. This is what happened with the client escalation.
Based on conversations with peers and Alex's own reflection notes, the following beliefs appear to be operating:
These beliefs worked at the manager level. They are not wrong in all contexts. At the Director level, with four managers who are themselves experienced, these beliefs are producing the opposite of their intended effect.
Alex arrived at the meeting having had three difficult conversations earlier in the week: a client complaint that required executive involvement, a missed deadline from one of the sites, and a performance concern flagged by HR about an employee Alex did not yet know well.
When Riley walked in at the forty-minute mark, Alex's pace visibly increased. Multiple people noticed. The final ten minutes of the meeting were faster and more directive than the first eighty.
Alex has described the first three weeks as "a lot to hold." Alex has not said this to anyone at Northstar. Alex said it to a former colleague in a text message that began with "don't tell anyone but."
The internal experience: Alex feels pressure to demonstrate that the promotion was deserved. Any moment of visible struggle feels like evidence that it was not. This is producing a pattern where uncertainty is met with control rather than inquiry.
Thomas had been working on a standardized reporting template for six weeks before Alex arrived. It was nearly complete and had been shared informally with Marcus and Priya for input. Thomas had been waiting for a Director to be in place before formally proposing it, since the previous Director role had been vacant for several months.
When Alex announced in the meeting that "I'll build a standardized template and send it out this week," Thomas said nothing. After the meeting, Thomas saved his draft to a folder on his desktop and closed the document.
He has not mentioned it again.
Using the SCARF model (Status, Certainty, Autonomy, Relatedness, Fairness):
Northstar promoted Alex because Alex delivered. Northstar's promotion criteria are almost entirely result-based. There is no formal assessment of leadership behavior, team development outcomes, or organizational health indicators. The implicit message the culture sends is: if the numbers are good, the leadership is good.
This means Alex learned to lead in an environment that rewarded the exact behaviors now creating problems. Stepping in, taking over, moving fast, and being decisive were the moves that got Alex noticed and promoted. Nothing in the system gave Alex feedback that these behaviors had a cost.
The pattern is not purely Alex's fault. The system built it. Your job is to help Alex see both truths simultaneously.
Before your group begins, assign one role to each person. The Observer opens every task by reading their observations aloud first, without interpretation. This grounds the group in what is actually visible before meaning-making begins. The Interpreter responds next, building on the Observer's data. The Regulator adds the emotional and physiological read after the Interpreter has spoken. The Challenger goes last and is the only role with permission to say: "I think we are missing something." No one rebuts the Challenger in the moment. The group writes down what the Challenger names and returns to it before finalizing any deliverable. Roles do not shift mid-session. If your group has fewer than four people, one person holds both Interpreter and Regulator. The protocol exists so the group does not collapse into one voice. If you find everyone agreeing too quickly, that is a signal that someone is not playing their role fully.
What is happening behaviorally? Name only what is visible and documentable from the case. No interpretation yet.
What meaning is Alex making? What story is running underneath the behavior? What does Alex believe is true?
Where is pressure showing up in Alex's body and behavior? Which SCARF domains are activated and when?
What is Alex not seeing? What assumption is going unexamined? What uncomfortable truth needs to be named?
northstar-participant-portfolio-forms.pdf (Month 1 section)Your group's Leadership Awareness Brief is your deliverable for today. Come to the debrief prepared to share your Risk Statement and one key insight from your intent vs. impact analysis. The facilitator will connect what groups found to the frameworks from this month's module and open the conversation to how this pattern shows up in your own organizations. Have fun with it. The best advisory teams disagree with each other before they agree. That tension is the work.
The numbers still look fine. That is exactly the problem. Six weeks in, Alex's region is producing results, but something quieter and more consequential has been building underneath the metrics. This month you move from observation to diagnosis. Your job is to see the system, not just the leader inside it.
Before your group opens the new case material, pull your Month 1 Leadership Risk Statement. Read it aloud as a group. Then ask: Has anything you have observed in your own organizations since last month changed, sharpened, or complicated what you wrote? Do not rewrite it yet. Just hold it alongside what you are about to read. You will know by the end of this session whether it still holds.
You are still mentor leaders to Alex. But your function this month shifts. In Month 1 you observed behavior. This month you diagnose systems. The question is no longer only "what is Alex doing?" It is "what conditions made this pattern possible, and what is the system already producing as a result?" The Iceberg Model is your primary tool. Most of what matters is below the waterline.
The advisory group's discipline this month is to resist the pull toward solutions. You do not have enough information yet to intervene. You have enough to diagnose. Stay in the diagnostic posture until your deliverable is complete. If your group finds itself writing recommendations, you have moved too fast.
Disagreement this month will likely surface around the technical versus adaptive distinction. One person will want to call something a process problem. Another will want to call it a culture problem. Both may be partially right. The Challenger's job is to hold that tension rather than resolve it prematurely. A diagnosis that is too clean is usually wrong.
Six weeks have passed since the regional leadership meeting. Alex's region is still delivering. The quarterly numbers are strong. Jordan mentioned Alex by name in a senior leadership update as an example of "the kind of execution mindset we need more of across the organization." Riley said nothing in response.
Underneath the surface, the team has been quietly reorganizing itself around Alex's behavior. Not through any deliberate decision. Through the accumulated logic of self-protection. When a system learns that certain behaviors produce certain responses, it adapts. Alex's team has been adapting for six weeks. What follows is the record of that adaptation.
The following is a reconstruction of Marcus's weekly team sync at Site 4, observed by Thomas as part of a routine operational review. Thomas submitted the observation notes to the regional file. Alex has not read them.
Riley requested a thirty-minute check-in with Alex at the six-week mark as a standard onboarding practice. The following is a reconstruction based on Riley's notes filed after the meeting.
Marcus has stopped raising problems in regional syncs. His agenda items now report only what is going well. Priya has adopted the same pattern independently. Devon watched both of them and arrived at the same conclusion without being told. Three of the four most experienced managers in the region have now learned that surfacing problems in Alex's presence carries a cost that is not worth paying. They have not discussed this as a group. They did not need to. Systems teach without speaking.
The metric implications have not yet appeared. The compliance metrics are strong. The quality scores are holding. From the outside, and from Alex's vantage point, the region is performing. The candor collapse is invisible in the data because silence does not show up in a dashboard. It shows up six weeks later when the problems that were not raised have grown into problems that cannot be hidden.
"I feel like the region is starting to find its rhythm. People are executing against clear standards, which is what I set out to establish in the first 90 days. The team is professional and I think they respect the structure we've put in place. My focus for the next few weeks is building stronger accountability loops so that strong performance is recognized and gaps are addressed quickly. I think we're in a good place."
Use the expandable sections below if your group has questions about specific aspects of the case. These provide additional context that may help your analysis.
The Iceberg Model distinguishes between what is visible above the waterline (events) and what drives those events below it (patterns, structures, mental models). Applied to Northstar:
Above the waterline (visible): Strong metrics. Managers complying with new processes. Alex stepping in to resolve issues. The region appearing to perform.
Just below the waterline (patterns): Managers have stopped raising problems. Agenda items have become reporting-only. Decision-making has migrated upward. Team members are waiting to be told rather than acting independently.
Deeper below the waterline (structures): The escalation protocol has removed manager discretion. The reporting template has standardized output but not thinking. The one-on-one schedule has made access to Alex scarce and formal. These are structural changes that produce the behavioral patterns above them.
At the bottom (mental models): Alex believes that clarity, standards, and consistency produce capability. The team has learned that clarity means compliance, standards mean surveillance, and consistency means predictability of consequence. These are not the same mental models. The gap between them is the root cause.
Technical problems have known solutions that can be implemented by an authority. Unclear escalation thresholds are technical. A standardized reporting template is a technical solution to inconsistent reporting.
Adaptive challenges require changes in values, beliefs, or behaviors among the people who have the problem. The candor collapse is adaptive. You cannot solve it with a clearer protocol. The managers already know they should raise problems. They have decided the cost is too high. That is a values and culture problem, not a process problem.
Alex has been applying technical solutions to adaptive challenges. The escalation protocol did not solve the decision rights confusion. It created a new reason for people not to decide. The reporting template did not solve inconsistency. It solved the symptom while deepening the root cause.
The diagnostic question for your group: For each problem you identify in Alex's region, is it technical, adaptive, or does it have both dimensions? The answer determines the intervention type. Getting this wrong is the most common and most expensive mistake in organizational change work.
Riley has now had two interactions with Alex that contained warning signals. In Week 3 Riley observed the meeting and said nothing. In Week 6 Riley gave Alex a direct but gentle warning that was not received as a warning.
Riley filed a note in Alex's onboarding record: Awareness gap: significant. Riley has the information to act. Riley has the authority to intervene more directly. Riley has not done so.
This is not negligence. Riley is operating inside Northstar's cultural norm: give people space to find their way, do not intervene until the cost is visible. This norm has a logic to it. It also has a cost. The cost will become visible in Month 4.
For your group: Riley is part of the system. What would it require for Riley to intervene earlier? What is the organizational condition that makes Riley's current approach rational? And what does that tell you about the change that needs to happen beyond Alex?
Thomas is the people services lead. His function is organizational health. He has been observing the region for seven weeks and has made fourteen documented entries in a private file he has shared with no one.
Read that again. The person whose job it is to surface organizational health concerns is keeping a private record instead of raising a formal flag. This is not caution. This is a sophisticated professional making a calculated judgment that the organization is not yet ready to receive what he is seeing.
Thomas is the most systems-aware person in this case study. He sees more than anyone else. He is also the most institutionally constrained. He gave Marcus one piece of advice: document what you are noticing. He cannot do more than that yet, within the norms of his role and the culture of the organization.
When Thomas's private document becomes relevant in a later month, your group will want to have understood what it represents: an organizational health professional who has been watching a slow-motion crisis and does not yet have the organizational permission or the evidence threshold to act on it.
Why are managers not raising problems? Because raising problems in regional syncs has not produced helpful outcomes and has produced uncomfortable responses.
Why has raising problems produced uncomfortable responses? Because Alex tends to reframe problems as execution failures and move quickly to directives rather than collaborative diagnosis.
Why does Alex reframe problems this way? Because Alex's mental model of leadership is that a Director's role is to maintain standards and resolve uncertainty, not to hold uncertainty with the team.
Why does Alex hold this mental model? Because it produced results at the manager level and was never interrupted by feedback that named the cost of this approach to team development.
Why was there no feedback? Because Northstar's promotion and performance systems measure output, not leadership behavior. Alex was never shown the cost because the cost was not measured.
This is the root cause. Not Alex's personality. Not the team's sensitivity. The organizational system that built Alex's leadership pattern and then promoted it without examining what it was producing below the waterline.
Kayla resolved a client escalation successfully, independently, and on her own judgment. She then chose not to report it in real time, even though the protocol requires it. When asked why, she said it did not meet the threshold. She was technically wrong about the threshold. But she was not wrong about the underlying judgment: the escalation was handled and reporting it in real time would have triggered a process she had learned to avoid.
This is significant for three reasons. First, Kayla is demonstrating that she is still capable of good judgment. The candor collapse has not eliminated competence. Second, Kayla is beginning to route around the system rather than through it. She is solving problems outside the formal structure because the formal structure has become more burdensome than useful. Third, when Alex corrected her and Kayla did not respond, that silence was not deference. It was the visible absence of engagement.
A manager who does not respond to a correction has stopped seeing the correction as meaningful. That is a later-stage signal than anything your group saw in Month 1. The system is not just adapting. It is beginning to disengage.
The role structure is the same as Month 1. The emphasis shifts. The Observer this month is tracking system-level patterns, not just individual behaviors. What has changed between Week 3 and Week 7? What has the system produced? The Interpreter is working the Iceberg: what is below the waterline that explains what is visible above it? The Regulator is asking where emotional and psychological pressure is showing up across the system, not just in Alex. What is Marcus carrying? What is Thomas holding? The Challenger is watching for the group's tendency to diagnose the symptom and call it the root cause. Push past the first answer on every task. If your root cause can be solved with a memo or a new protocol, it is not the root cause.
What has the system produced between Week 3 and Week 7? Name the patterns, not just the events.
What is below the waterline driving what is visible above it? Work the Iceberg from the bottom up.
Where is pressure showing up across the system? What is Marcus carrying? What has Thomas decided?
Is the root cause actually a root cause, or is it still a symptom? Push past the first answer every time.
northstar-participant-portfolio-forms.pdf (Month 2 section)Come prepared to share your root cause finding and your consequence map projection. Your facilitator will surface what the case is teaching beneath the surface and run the Ownership Arc. The best diagnostic work names what is hard to name. If your root cause is comfortable, it is probably not deep enough. Bring your discomfort too. That is where the real conversation starts.
© 2026 OCA Consulting Group · All content is proprietary and confidential · For enrolled program participants only · Not for reproduction or distribution
You now have a diagnosis. The region is performing on paper. The system underneath is degrading. This month you must design a scoped, realistic intervention for a leader who does not yet believe they have a problem. That is not a design flaw. That is the design challenge.
Before opening the new material, pull your Month 2 Root Cause Analysis. Read your organizational root cause aloud as a group. Then ask: Does the charter we are about to design actually address this root cause, or does it address a symptom? That question should stay on the table through every task this month.
You are still mentor leaders. But this month your function shifts from diagnosis to design. You are being asked to produce a real intervention charter, not a reflection document. Riley has asked your group a direct question and needs a defensible answer backed by evidence. Treat it that way.
The constraint that shapes everything this month: Alex does not fully believe there is a problem. Any charter that ignores this constraint is not a real charter. It is wishful planning. Your Challenger's primary job this month is to ask of every element: "Does this work if Alex is not bought in?"
The group dynamic to watch for this month is over-scoping. When participants care about a problem, they tend to design interventions that address everything at once. That is how interventions fail. Your Challenger should flag any charter that cannot be executed with the resources and relationships currently in place.
Eight weeks have passed since the regional meeting. Alex's region continues to deliver on core metrics. Riley has received Thomas's informal observation notes and flagged them internally. A request for a formal advisory check-in has been submitted to Jordan, who approved it. Riley is now actively monitoring the region.
In Week 9, Riley requested an informal meeting with the advisory group. The question on the table: "We have strong numbers and a team that appears to be struggling. I need to know if we have a leadership problem or a people problem, and I need a recommendation."
Alex, informed that Riley had raised a concern, responded in a one-on-one with Thomas: "I think some people are still adjusting. I'm not sure what problem we're solving here. The numbers are good. I'm going to stay focused on execution."
Use the expandable sections below if your group has questions about specific aspects of the case.
A charter is not a plan. It is the authorization document that defines what the intervention is, what it is not, who owns it, and how success is measured before execution begins. Applied to this case:
Scope: What specifically will this intervention address? Leadership behavior change in one director, or also structural changes to reporting and escalation protocols? Both may be necessary, but they require different actors and different timelines.
Success criteria: What does success look like that is measurable and behavioral? "Alex becomes a better leader" is not a success criterion. "Three or more managers voluntarily surface problems in regional syncs within 90 days" is a success criterion.
Stakeholders: Who must be involved for this to work? Alex is the primary subject. Riley is the sponsor. Jordan must at minimum be informed. The management team is both a beneficiary and a gauge of success.
Out of scope: What will this intervention explicitly not address? This boundary is as important as scope. If the charter does not define it, scope creep is inevitable.
Assumptions: What must be true for this charter to hold? The most critical assumption in this case: Alex engages genuinely. Your charter must include what happens if that assumption fails.
Priya is the highest-performing manager on Alex's team. Her transfer request is in a 60-day hold. Alex does not know. This is a significant compounding factor for your planning.
If Priya's transfer is approved before the intervention produces visible results, the intervention loses its most important data point: whether the highest-performer responds to genuine change in Alex's behavior. Priya staying and re-engaging is the most powerful evidence of success. Priya leaving is the evidence that the intervention came too late for at least one key relationship.
Your charter should account for this. Does the intervention need to move faster because of Priya's timeline? Does Riley need to be informed that Priya's presence is a factor in the intervention's design? These are real planning questions, not hypotheticals.
Alex's response to Thomas contains three classic low-readiness markers: attribution of the problem externally ("that's on them"), dismissal of the evidence ("the numbers are strong"), and redirection to a comfortable frame ("I'm going to keep my focus there").
None of these are signs of bad character. They are signs of a leader who has not yet received feedback in a form that penetrates the defense. Thomas's approach, informational and non-confrontational, was appropriate for his role. It was not sufficient to shift the readiness level.
What would shift it? Evidence that is harder to dismiss. A consequence that is more visible than a transfer request Alex does not yet know about. Or a direct conversation with someone whose opinion Alex weights heavily, delivered with enough specificity that the defense cannot hold. Riley has the authority and the information. Riley has not yet fully used either.
Jordan forwarded Alex's self-assessment to Riley with one word: "Good?" That question mark is doing a lot of work. Jordan is either genuinely asking Riley to confirm that things are good, or Jordan is signaling skepticism in a way that is too indirect to act on.
Either way, Jordan has the information to ask a more direct question and is not asking it. This is a pattern at the senior level that mirrors the pattern at the team level: warning signals being transmitted without being received, because the transmission is too indirect and the recipient is not oriented to hear them.
For your charter: does it account for Jordan? Does senior leadership need to be aligned before the intervention begins, or is Riley's sponsorship sufficient? What happens to the intervention if Jordan's "Good?" is interpreted as approval rather than concern?
This month the Challenger's role is the most important. Intervention planning is where groups are most prone to wishful thinking, over-scoping, and designing for an Alex who is more ready than the case evidence shows. The Challenger holds the group honest about what is realistic. The Observer tracks what the case evidence actually supports. The Interpreter works the readiness question: what story would Alex have to change to engage genuinely? The Regulator asks what conditions would need to exist for Alex to receive this intervention without triggering the same defenses Thomas just encountered. Every task this month runs through that readiness lens.
What does the case evidence actually support in terms of Alex's readiness? Name only what is visible and documentable.
What story would Alex have to change to engage genuinely? What would need to crack the current frame?
What conditions would allow Alex to receive this intervention without triggering the same defenses Thomas encountered?
Does this charter actually work if Alex is not bought in? Flag every assumption that requires readiness Alex does not yet have.
northstar-participant-portfolio-forms.pdf (Month 3 section)Come prepared to share your advisory response to Riley and your charter scope statement. Your facilitator will surface what the case is hiding and run the Ownership Arc. The Month 3 charter is not finished work. It is a draft that Month 4 will test. Bring it knowing it will be revised.
This is the month everything changes. The cost of unaddressed leadership behavior becomes concrete and public. Priya resigns. Riley intervenes directly. Jordan acts. Alex, for the first time, stops defending and starts listening. Your job is to analyze what made that possible and respond in real time.
Before opening the new material, pull your Month 3 Intervention Charter. Read the scope statement and your top three risks aloud as a group. As you work through Month 4, track: which assumptions broke? Which risks materialized? Which elements of the charter are now more or less relevant? You will formally revise the charter in Task 5.
This month you move from planning to responding. The situation you were designing for has arrived, faster and harder than your charter anticipated. Your function is now crisis analysis and real-time advisory. Alex has asked your group directly: "What am I not seeing?" That question is the moment this entire program has been building toward. Answer it well.
One thing to hold carefully this month: Alex is cracked open, not transformed. Cracked open means the defense is down and the question is genuine. It does not mean the work is done. Your response must build awareness without triggering a shame response that closes Alex back down. There is a precise line between honesty that opens and honesty that shuts down. Your group must find it.
The second teaching this month: leaders sometimes need external intervention to see what they cannot see alone. Riley's move was not a failure of coaching or gentle feedback. It was a necessary escalation. Analyzing what made it work is as important as analyzing what it revealed about Alex.
Priya submits her resignation in Week 11. In her exit conversation with HR she is direct: "I stopped being able to do my job. Every decision I made was second-guessed or taken back. I brought this to Alex twice. Nothing changed. I am not a fit problem. This is a leadership problem." HR flags the exit notes immediately. Riley reads them within the hour and escalates to Jordan. Jordan calls Riley: "We cannot afford to lose people like Priya. This has to stop. Get in front of it."
Use the expandable sections below if your group has questions.
Riley's confrontation worked for four specific reasons. First, Riley named the source explicitly: Priya's exit interview. This is evidence Alex could not dismiss as opinion or interpretation. It was a direct quote from a person Alex respects, in a formal organizational record.
Second, Riley named their own accountability: "I gave you a signal that didn't land. That's on me." This is a regulated response from a senior leader. It models the behavior being requested of Alex without demanding it directly.
Third, Riley held the line on the consequence while reframing the meaning: "This is an investment, not a punishment." This kept Alex's Status domain from triggering a defensive shutdown while making the non-negotiable nature of the mandate clear.
Fourth, Riley did not answer Alex's question immediately. "I think you need to sit with it for a few days." That choice preserved Alex's autonomy and cognitive processing time, which is the opposite of what most organizations do when they have finally decided to confront a leader.
Jordan mandated the coaching. The HR file describes it as voluntary. This is an organizational honesty gap that has direct implications for Alex's development and for the intervention's design.
If Alex believes the coaching is genuinely voluntary, Alex may engage with it as a performance of compliance rather than a genuine development commitment. The research on mandated coaching is mixed, but the evidence is clear that coaching mandated by external pressure without internal motivation produces surface-level behavior change that does not sustain.
What could make the difference: whether Riley's confrontation and Thomas's document have shifted Alex's motivation from external compliance to internal recognition. The sentence "I thought I was helping" suggests that Alex's frame has cracked. That crack is the opening for genuine engagement. Whether it holds is the question Month 5 will answer.
Devon submitted three agenda items that contained operational problems. This is the first time Devon has surfaced a problem in a formal agenda in six weeks. Devon did not know about Riley's confrontation with Alex. Devon did not know about the coaching mandate. Devon simply noticed that something had shifted in the air of the organization and made a small, early bet that it might be safe to raise a problem again.
This is how systems respond to leadership change: not all at once, not dramatically, but through small individual bets made by people who are watching the signals. Devon's three agenda items are the earliest system-level evidence that something is shifting. They are also easily reversed if the signal does not hold.
For your group: what does this tell you about the timeline for team recovery? And what would it take for Devon to bet bigger next time?
The emotional stakes in Month 4 are higher than any prior month. Alex has asked a direct question. The Regulator's role this month is critical: your group must produce a response to Alex that is honest enough to be useful and regulated enough not to trigger shame and shutdown. The Observer tracks specific behavioral evidence from the crisis week that supports or complicates your prior analysis. The Interpreter works the turning point question: what story did Alex have to change to ask "What am I not seeing?" The Challenger asks whether your revised charter actually accounts for what just happened, or whether it is still designed for the situation that no longer exists. The Regulator manages the tone of the group's response to Alex. Direct does not mean harsh. Honest does not mean overwhelming. Find the line.
What specific behavioral evidence from this month confirms or shifts your prior analysis? Name the moments.
What story did Alex have to change to ask "What am I not seeing?" What cracked the frame?
How does your group's response to Alex stay honest without triggering shame? Find the line.
Does the revised charter account for what just happened, or is it still designed for the situation that no longer exists?
northstar-participant-portfolio-forms.pdf (Month 4 section)Come prepared to share your response to Alex and your revised charter scope. The Month 4 debrief is the turning point of the full program. The work you do in the room today sets the direction for everything that follows. Come ready to go deep.
The individual change is real. The system has not kept pace. This month you learn to hold both truths simultaneously. Alex is doing the work. The team is watching and waiting. The psychological contract is damaged. A changed leader does not automatically repair a broken culture.
Before opening the new material, pull your Month 4 Revised Intervention Charter. Read your updated success criteria aloud as a group. Then ask: Is Alex meeting those criteria? Is the team? Which gaps are about Alex, and which are about the system? Keep those two columns separate as you work.
You are still mentor leaders to Alex. But this month your function expands. You are now advising on the team system, not just on one leader. The question is not only "how is Alex doing?" It is "what does the team need that is different from what Alex needs?" Those are two different intervention streams and your group must hold them simultaneously.
The temptation this month is to celebrate Alex's progress and close the analysis too soon. The Challenger's job is to hold the group to the harder question: if the team is not yet fully re-engaged, what does that tell you about what still needs to change?
Six weeks have passed since Riley's confrontation and Jordan's mandate. The coaching is happening. The check-ins are happening. Alex is visibly different in meetings.
Six weeks have passed since Riley's confrontation and Jordan's mandate. Alex is working with an external coach. The bi-weekly check-ins with Riley are happening. Thomas is now keeping a shared development observation file rather than a private one. From the organizational chart, everything looks like it is in motion.
From inside the team, it is more complicated. Alex is different in meetings. The change is real. But the team does not yet know how to respond to a different Alex. The behaviors they developed to protect themselves over eleven weeks do not dissolve because the leader changes. They persist because the team is watching and waiting to see if the change is real or temporary.
Alex is demonstrating genuine behavioral change across six observable dimensions: asking before directing, staying quiet while others fill space, attributing good ideas to their source rather than absorbing them, inviting disagreement explicitly, completing bi-weekly sessions with the coach without canceling, and reducing the volume of late-night Slack messages by approximately 80 percent since Week 11. These are real changes. They are not yet consistent under high pressure. Month 5 has not produced a high-pressure test.
The team is still operating on habits built over eleven weeks of a different leadership environment. Managers are checking their instinct to surface problems because that instinct was extinguished and has not yet been fully rekindled. The psychological contract between Alex and the team was damaged. A changed leader does not automatically repair a damaged psychological contract. The team needs to see the change hold under pressure before they will bet on it with their full candor and initiative.
Priya has not withdrawn her resignation. The 60-day hold expires in three weeks. Whether she stays or goes will depend significantly on what she hears from Marcus, Devon, and Thomas over that period, not from Alex directly.
Use the expandable sections below if your group has questions about specific aspects of the case.
Priya is watching from a distance. She has access to Marcus and Thomas. She is hearing that Alex is different. She has not withdrawn her resignation because she has been here before: a leader gets feedback, improves temporarily, and reverts when the pressure rises. Her resignation is not a rejection of the new Alex. It is a rational hedge against the possibility that the new Alex is not durable.
The system repair question is not whether Alex changes. It is whether the change is real enough and visible enough that the people who left the psychological contract feel it is safe to re-enter. Priya's decision in the next three weeks is the most important early indicator of whether the intervention is actually working.
A psychological contract is the set of unwritten expectations that govern the relationship between a leader and their team. It includes things like: if I raise a problem, I will be heard. If I make a decision, I will be supported. If I disagree, I will not be dismissed. Alex's leadership behavior over the first eleven weeks broke several elements of this contract without Alex knowing the contract existed.
Repairing a psychological contract requires three things: acknowledgment of the breach (Riley's confrontation began this), consistent behavioral evidence over time that the new norm is real, and at least one high-stakes test where the leader's changed behavior holds under pressure. Alex has provided the first two beginning. The third has not yet happened. Month 5 ends before the high-stakes test arrives. That test comes in Month 6.
Kayla is the manager whose adaptive behavior most closely resembles full disengagement rather than strategic caution. Marcus is watching and waiting. Devon has made a small bet. Kayla is not yet betting. Her agenda items remain completion-status only after fifteen weeks.
This is significant because Kayla's profile, strong relationship manager, avoids conflict, resolves quietly, is exactly the profile that organizational cultures tend to lose silently rather than dramatically. Kayla will not resign the way Priya did. Kayla will simply stop contributing beyond the minimum, stop developing, and eventually stop caring. That outcome is harder to see in the data and harder to reverse.
For your group: what would it take to re-engage Kayla specifically? And what does Alex not yet know about how close Kayla is to the edge of functional disengagement?
The Strategist role enters this month's advisory structure. You have moved from diagnosis to execution, and you now need someone tracking the sequence of recovery: what must happen before what else can happen. The Observer tracks behavioral evidence of Alex's genuine change versus performative change. The Strategist sequences the team recovery: what must be true before Kayla can re-engage? What must Devon experience before Marcus bets fully? The Challenger identifies where the system itself, not Alex, is blocking recovery. The Regulator holds the emotional truth: it is genuinely hard for a team to re-enter trust after it has been damaged.
What behavioral evidence confirms Alex's growth is real, not performative? Name specific moments.
What does the team need from Alex now that Alex's behavior is changing? Sequence the recovery.
Where is the system itself preventing the team from responding to Alex's growth? Name the structural barriers.
What does it feel like for a team to have psychological safety eroded and then offered back? What does re-entry require emotionally?
northstar-participant-portfolio-forms.pdf (Month 5 section)Come prepared to share your dual-layer analysis and your re-entry conditions design. The best insight from Month 5 is usually the one that separates Alex's work from the system's work. Bring the distinction clearly.
Alex is now asked to do the very thing that was done to them: give direct feedback and coach instead of rescue. One manager is underperforming. The test is whether Alex has genuinely internalized new behavior or will revert under pressure.
Before opening the new material, pull your Month 1 Leadership Risk Statement. Read it aloud. Then pull your Month 5 behavioral evidence of Alex's change. Hold both as you work through this month. Task 4 asks you to build a formal before-and-after map.
You are mentor leaders watching a critical test. This month Alex must do the hardest version of what they have been working on: give direct, uncomfortable feedback to a person they manage, without rescuing them or taking the work back. Your job is to analyze how Alex navigates that moment and what it tells you about the durability of the change.
The Challenger this month holds the performance diagnosis honest. Coaching is not always the right intervention. Sometimes the problem is a skill gap. Sometimes it is a will gap. Sometimes it is a systemic conditions gap that Alex created. Getting the diagnosis wrong means applying the wrong remedy. Your group must name the actual problem before recommending the intervention type.
Priya did not withdraw her resignation. The 60-day hold expired and HR processed the transfer. Priya is now in a different region. Alex was informed by Riley. Alex's response to Riley was: "I understand. I wish I had seen what I was doing sooner." Riley noted it as the most regulated response Alex had given to a difficult piece of news since Month 1.
The team has continued its gradual recalibration. Devon made two more independent decisions and reported both to Alex after the fact. Marcus led the cross-training presentation and received strong peer feedback. Kayla attended a facilitation training she requested independently, the first professional development she has self-initiated in eight months.
Derek, a manager on Alex's team, has missed two milestone deliverables in the past six weeks. His team's quality metrics have dropped 18 percent. This is the first visible underperformance situation Alex has faced since the development mandate.
Alex did not take the work back. Alex asked a question instead of giving an answer. The instinct to rescue was present and Alex did not act on it. This is the behavior change in practice. It is small. It is significant. It is also not the end of the story: Derek still has a missed deliverable, a team member conversation he has been avoiding, and a quality gap that needs to close.
Use the expandable sections below if your group has questions about specific aspects of the case.
Skill gap: Derek lacks the capability to do what is being asked. Evidence for: he has been in the role for eighteen months and these milestone types are relatively new to his portfolio. Evidence against: Derek has successfully managed similar deliverables in prior quarters.
Will gap: Derek has the capability but not the motivation or commitment. Evidence for: his explanation shifted quickly when questioned, suggesting the original rationale was not the real one. The avoidance of the team member conversation for six weeks despite three informal flags is classic will-gap behavior. Evidence against: Derek appears stressed rather than disengaged.
Systemic conditions gap: The environment Alex created, including unclear decision rights and suppressed problem-surfacing, may have created conditions where managers learned to avoid difficult conversations. Derek's avoidance pattern may have been reinforced by eleven weeks of watching what happened when problems were raised. The root cause may be Alex's prior leadership behavior, not Derek's individual capability or motivation.
Your diagnosis determines your recommendation. If it is a skill gap, Derek needs training. If it is a will gap, Derek needs a direct performance conversation. If it is a systemic conditions gap, Alex is part of the intervention, not just the intervener.
In Month 1, Alex would have intervened at Week 14. Alex would have taken over the deliverable, rebuilt the plan, and reported it done. The team would have hit the metric and Alex would have added another action item to an already full calendar.
Waiting until Week 19 before having the conversation is evidence of a different approach. It is also not obviously correct. Six weeks is a long time for a quality gap to compound. There is a version of Alex's new behavior that is restraint and coaching. There is also a version that is avoidance of the discomfort of a performance conversation. Your group should consider which is more likely, and what the difference looks like in practice.
Thomas writes: "The harder test will come when Derek's team member situation escalates and Alex must give direct feedback rather than coach toward self-awareness." This is not a Month 6 event. It is a preview of what Month 6 is building toward and what your group should be preparing Alex for.
Coaching someone toward their own insight, which Alex did with Derek, is the more regulated and sophisticated approach. But it does not work in every situation. When a team member's performance is affecting others and the problem is clear, the intervention may need to be a direct feedback conversation rather than a reflective question. Alex has not yet done that version under the new behavioral commitments. That test is coming.
The Observer this month tracks the specific behavioral evidence that Alex is coaching rather than rescuing. Name the exact moments. The Strategist determines the performance diagnosis for Derek and sequences the intervention: what must happen in what order. The Challenger holds the group to the harder diagnostic question: is this Derek's problem, or is this a delayed consequence of Alex's prior leadership environment? The Regulator tracks what it cost Alex emotionally to not rescue Derek, and what that restraint means for the sustainability of the change under increasing pressure.
What specific behaviors evidence that Alex is coaching rather than rescuing?
What is the performance diagnosis for Derek and what intervention does it require?
Is this Derek's problem or a delayed consequence of the leadership environment Alex created?
What did it cost Alex not to rescue Derek and what does that tell you about sustainability?
northstar-participant-portfolio-forms.pdf (Month 6 section)Come prepared to share your performance diagnosis and your before-and-after behavioral map. The map is critical portfolio material. Your facilitator will push on whether your diagnosis is precise or convenient. Come ready to defend it.
Alex is leading a regional implementation initiative. The skills are real. The organization around Alex is not keeping up. This month you must distinguish individual execution discipline from systemic adoption barriers, and figure out how to use Alex as an organizational asset rather than a cautionary tale.
Before opening the new material, pull your Month 5 Team Culture Assessment and Conditions Plan. Read your re-entry conditions aloud. Then ask: Have those conditions been met? What evidence do we have that the team environment has recovered enough to handle external implementation pressure?
You are entering the monitoring phase. Alex is not the primary problem anymore. The system is. Your function this month is to evaluate implementation evidence, diagnose adoption barriers, and make a recommendation about how the organization should use Alex going forward.
The Evaluator and Architect roles enter this month. The Evaluator makes judgments about what is working using evidence. The Architect designs what organizational conditions would need to exist to make this initiative succeed across all regions. Disagreement between these roles is the productive tension this month depends on.
Northstar has launched a regional coordination process across three pilot regions. Alex's region is six weeks in with genuine adoption. Managers are raising problems during implementation. Devon ran a pilot debrief independently. Marcus flagged a sequencing issue before it became a client problem. The adjacent regions are a different story.
Alex is now doing for the organization what the advisory group has been doing for Alex: observing patterns, naming what is not being named, and bringing a concern to the right person in the right way. This is the Multiplier in early formation.
Use the expandable sections below if your group has questions.
Rollout is the delivery of a change: training completed, templates distributed, milestones submitted. Adoption is when the change becomes how people actually work. Region 3 is a case study in rollout without adoption: 94 percent milestone completion, zero observed behavior change. Jordan reads this as success. Riley does not. Your group must articulate why they are both looking at the same data and arriving at different reads.
The Region 2 director's pattern, public compliance and private stalling, is most consistent with conviction-based resistance: a sincere belief that the model is not appropriate for their context, paired with a reading of the culture that says expressing that belief directly is risky. The capacity argument is real but not the primary driver. Compare this to Region 3, where compliance-oriented resistance means doing what is asked without internalizing why it matters. These are different problems with different solutions.
Four roles for the Systems and Transfer phase. The Evaluator builds the evidence case: what is actually working versus what appears to be working? The Strategist sequences the organizational response to Region 2. The Architect designs the systemic conditions that would make this succeed across all three regions. The Advocate prepares how to present this to senior leadership in a way that compels action without overstating the evidence.
What is the measurable evidence that the implementation is working? What would a skeptic challenge?
What is the adoption barrier in Region 2? What must happen in what order to move them forward?
What systemic conditions would make this initiative succeed across all three regions, not just Alex's?
How does Alex present this concern to Riley without overstepping or being dismissed?
northstar-participant-portfolio-forms.pdf (Month 7 section)Come prepared to share your adoption analysis and your barrier removal plan. The facilitator will name what the case is teaching about the difference between a leader who changed and a system that is still broken. Bring the distinction clearly.
Eight months in. Jordan wants to know if the investment was worth it and how to replicate it. Riley wants to know what the organization has not yet fixed. You have the data. You have the pattern knowledge. Build both cases with evidence, not narrative.
Before opening the new material, pull your Month 1 Leadership Risk Statement and your Month 6 Before-and-After Behavioral Map. These are the two anchors of your evidence base this month. Read them both aloud. Then ask: does the distance between Month 1 and Month 8 constitute genuine development or behavioral compliance? Your answer to that question shapes the entire Month 8 and Month 9 argument.
You are in the final preparation phase. This month you are assembling everything you have learned into a defensible evidence base and a set of systemic recommendations. You are not summarizing the case. You are making an argument. Jordan and Riley need to make organizational decisions based on what you tell them. Those decisions have real consequences. Build accordingly.
The most important discipline this month: separate what Alex's development demonstrates from what the organization still needs to fix. They are related arguments. They are not the same argument. Conflating them will weaken both.
Jordan has requested a formal summary from the advisory group ahead of a board discussion on leadership development ROI. Riley has added a second request: "I also want to know what we almost missed. And what we have to fix at the organizational level so we are not dependent on a single leader having a crisis before we catch this." The advisory group has four weeks to prepare the Month 9 executive presentation. Month 8 is the build month.
Use the expandable sections below if your group has questions about specific aspects of the case.
Behavioral compliance means doing the new behavior because someone is watching or because there is a consequence for not doing it. It is externally motivated and it does not hold when the external pressure is removed. Alex's first several weeks of the development mandate were likely partially compliance-driven: the coaching is mandated, Riley is checking in bi-weekly, the cost of not changing has been named explicitly.
Sustained behavior change means the new behavior has become the default pattern, driven by internal recognition of its value rather than external pressure. Evidence that Alex has crossed this line: Alex noticed the pattern in Region 2 and brought it to Riley without being asked. Alex waited until Week 19 to address Derek rather than intervening immediately, which required tolerating ambiguity that would have been intolerable in Month 1. Alex's self-assessment at Week 28 is accurate and includes accountability for impact, not just intent.
The risk of overstating this: the most rigorous test, a sustained period of organizational pressure without external coaching support, has not yet happened. The coach assessment notes reduced risk of reversion, not zero risk.
Northstar almost lost three managers: Priya (left), Devon (was considering transfer), Kayla (was approaching functional disengagement). Northstar almost failed a pilot implementation initiative in two of three regions for similar reasons. And Northstar had a director whose behavior was eroding a team for eleven weeks while the performance metrics looked strong.
None of these were caught by Northstar's existing systems. They were caught because Thomas kept a private document and eventually shared it with Riley, because Priya was direct in her exit interview, and because the advisory group was watching. That is not a system. That is luck and individual courage operating in a system that was not designed to catch this.
Riley's question is: what does Northstar need to build so that the next Alex is identified and supported before the crisis? That is the organizational case. It is separate from Alex's individual development story and it is arguably more important.
All four Systems and Transfer roles are active this month. The Evaluator assembles the evidence base: what does the data actually show versus what does it appear to show? The Strategist builds the systemic recommendations: what does Northstar need to change at the organizational level? The Architect designs the leadership operating system that would prevent recurrence. The Advocate prepares the executive presentation argument: how do you present eight months of complexity in a way that compels senior leaders to act?
What does the evidence actually show? Separate proven from inferred. Name what you cannot prove.
What systemic changes address the root causes that created the Alex situation in the first place?
What leadership operating system would Northstar need to build to prevent this from recurring?
How do you present eight months of complexity in a way that compels senior leaders to commit to action?
northstar-participant-portfolio-forms.pdf (Month 8 section)Come prepared to share your organizational root cause report and your recommendation list. The facilitator will separate the Alex story from the organizational argument and push you on which one is stronger. Bring both ready.
Nine months of diagnostic, planning, execution, and evaluation work converge in one high-stakes deliverable. You are presenting to Jordan, Riley, and senior leaders from your own organizations. This is not a summary of what happened. It is a recommendation for what Northstar must do next, backed by the most rigorous evidence base you have ever built.
Before beginning, confirm that your group has all eight prior portfolio artifacts available. List them. The Month 1 Risk Statement is your before-state. The Month 8 dashboard is your evidence base. The Month 2 root cause is your systemic diagnosis. Every artifact has a role in the final argument. Do not build this presentation from memory. Build it from the record.
You are presenting to a live executive panel. Jordan and Riley are in the room. So are senior leaders from your own organizations. This is not a classroom exercise. Your group has been inside this case for nine months. You have earned the right to say things that are true, specific, and require courage to say. Do not protect the room from what you have learned.
The Ownership Arc runs in full during the Month 9 debrief. All four questions, across the full cohort, in front of the executive panel. Come prepared to answer all four, not just the first one.
The Multiplier Transfer Plan is the deliverable most groups underspecify. It is not about Alex becoming an inspiration. It is about Alex becoming a method. The question is whether what Alex learned can be transferred to other leaders systematically, without requiring each of them to have a crisis first. That is the organizational ask.
Jordan's question to your advisory group: "We invested in one of our regional directors this year. Not because they were failing by the numbers, but because we saw something that needed to be addressed before it became a bigger problem. I want to know if it worked. And I want to know if we can replicate the model."
Riley's question: "I also want to know what we almost missed. And what we have to fix at the organizational level so we are not dependent on a single leader having a crisis before we catch this."
The board is watching. Northstar is planning to expand to four more regions in eighteen months. The leadership pipeline question is urgent and the answer has to come from your group.
Use the expandable sections below before building your presentation.
An executive presentation makes a recommendation and asks for a decision. A debrief reports what happened and invites reflection. These require different structures.
The structure that works: problem first, evidence second, what it means third, recommendations fourth, specific ask last. Do not lead with Alex's story. Lead with Northstar's problem. Alex's story is the evidence for the problem, not the problem itself. Executives need to understand the organizational problem before any solution makes sense to them.
Each recommendation needs a specific ask: not "we recommend leadership development investment" but "we are asking Jordan and Riley to approve a 90-day structured peer cohort pilot for the four directors entering expanded roles in Q2, with Thomas as the internal lead." Vague recommendations get vague responses.
The Multiplier Transfer Plan is not about Alex becoming an inspiration. It is about Alex becoming a method. The question is whether what Alex learned can be transferred to other leaders systematically without requiring each of them to have a crisis first.
A real transfer plan names: who receives the transfer, in what format, over what timeline, with what support structures, measured how. "Alex mentors other directors" is not a transfer plan. "Alex co-facilitates the first two sessions of a structured peer cohort for new regional directors, focused on the distinction between output-driven and development-oriented leadership, with Thomas tracking behavioral indicators over 90 days" is a transfer plan.
Most groups underspecify this because it requires making a concrete organizational design recommendation, which feels presumptuous. It is not presumptuous. It is exactly what an advisory group that has been watching this case for nine months is positioned to do. Make the specific recommendation.
Every strong advisory presentation names the limits of its evidence. It is not a weakness to say "we can demonstrate this and we cannot yet prove this." It is a credibility marker. Executives who trust the advisory group's honesty about what it cannot prove are more likely to act on what it can prove.
What you can prove with case evidence: specific behavioral changes across named months, retention data, adoption data, Thomas's observation record. What you cannot prove: whether the change would hold without external support, what Priya would have decided if the intervention had happened earlier, whether Region 2 would have responded the same way Alex did. Name both. The honesty makes the case stronger.
All four Systems and Transfer roles are active in their fullest form. The Evaluator owns the evidence quality: is every claim supported by case data, and are the limits of the evidence named honestly? The Strategist owns the recommendation sequence and priority. The Architect owns the systemic argument: does the presentation make the case for organizational change, not just individual development? The Advocate owns the room: is the presentation structured to compel action from Jordan and Riley specifically?
Is every claim supported by case data? Are the limits of the evidence named honestly and specifically?
Are the recommendations ordered by priority and feasibility? Is the decision request clear and time-bound?
Does the presentation make the organizational case, not just the individual development story?
Is the presentation structured to compel action from these specific people in this specific room?
northstar-participant-portfolio-forms.pdf (Month 9 section)Nine months. Eight artifacts. One case that stayed alive because you kept asking the harder question. The best presentations do not just inform Jordan and Riley. They model the kind of leadership thinking Northstar needs to build. Show them what it looks like.