Module Quiz: The First 90 Days

Correct: A. The three failure modes are: (1) The Savior Complex — arriving with a pre-built playbook from a previous company and implementing it before understanding the current organization; (2) The Analyst's Paralysis — spending 90 days listening and learning without making any visible moves, causing the organization to interpret silence as indecision; (3) The Political Innocent — understanding revenue but not organizational power dynamics, resulting in costly political missteps. Research shows 68% of CROs fail within 18 months, and these three patterns explain the majority of early failures.

Why not B: These describe management styles, not the specific onboarding failure modes identified in CRO transition research. The failure modes are about how CROs misread organizations in their first 90 days, not about their day-to-day management approach.

Why not C: While firefighting is common for new CROs (especially in turnaround situations), these are not the three failure modes discussed in the module. The module's failure modes focus on the diagnostic and political errors that compound over time.

Why not D: These are leadership archetypes, not failure modes. The module distinguishes between leadership style (which varies) and transition failure patterns (which are consistent across CRO tenures).

Correct: C. Days 1-30 are about discovery and orientation. The mindset is "curious, humble, observant" — a physician conducting an intake examination, not a surgeon scrubbing in. Key activities include 40+ stakeholder conversations, revenue architecture mapping (using the Module 2 framework), stakeholder mapping, and establishing an operating rhythm. The sequencing is critical because conclusions drawn in this phase shape every subsequent decision. Misdiagnosis in the first 30 days compounds — you solve the wrong problems with the wrong people at the wrong speed.

Why not A: Quick wins belong in Days 31-60. Attempting quick wins before completing discovery risks solving the wrong problems or triggering political resistance you have not yet mapped. Quick wins require the diagnostic foundation that Days 1-30 provide.

Why not B: The board presentation typically falls in the Days 31-60 window. Presenting a strategic plan before completing discovery is premature and risks the Savior Complex failure mode — acting before understanding.

Why not D: Restructuring in the first 30 days is the defining behavior of the Savior Complex failure mode. Without complete discovery, you lack the information to know who is underperforming versus who is constrained by broken processes.

Correct: D. The Skeptic engagement strategy has three components: (1) Lead with listening — ask the CFO what they see as the company's biggest revenue-related financial challenges before pitching your vision. (2) Find a quick win that benefits their function — improving forecast accuracy serves the CFO's planning needs and demonstrates analytical rigor. (3) Share your process, not your conclusions — skeptics convert when they trust your judgment, which comes from seeing how you think. The recommended cadence is weekly 1:1 for the first 60 days.

Why not A: This is the strategy for Allies. Proactive communication and public credit are appropriate for stakeholders already aligned with you. Applying Ally strategies to a Skeptic assumes trust that has not been earned and skips the listening phase that converts skeptics.

Why not B: This is the strategy for Blockers, not Skeptics. A Skeptic is uncertain, not oppositional. Building a coalition against a skeptic will likely convert them into an actual Blocker — a self-fulfilling prophecy and a costly political error.

Why not C: Monthly check-ins are for the Monitor quadrant (low influence, negative disposition). A CFO is a high-influence stakeholder who controls budget, compensation structures, and hiring approvals essential to your agenda. Monthly cadence for a high-influence Skeptic is dangerous underinvestment.

Correct: C. Compensation restructuring at Day 35 violates the "Low Political Risk" gate on multiple levels. First, it requires CFO buy-in before you have established trust with the CFO. Second, it changes the income of individual contributors before you have built relationships with the team — this is literally "moving someone's cheese" before earning the right. Third, if it goes poorly (attrition, morale damage), you have created a crisis rather than a credibility builder. All five gates must pass for a legitimate quick win. High impact and measurability alone are insufficient.

Why not A: Passing two of five gates is not sufficient. The Five Gates are all-or-nothing: a legitimate quick win must pass all five. The impact projection of 25% is also an estimate that could be wrong, creating a credibility problem if it underdelivers.

Why not B: While the timeline concern is valid (comp restructuring often takes longer than 30 days), the more fundamental issue is political risk. Even if you could execute it in 30 days, you should not — the political cost exceeds the operational benefit at this stage.

Why not D: Directional alignment and visibility are necessary but insufficient. Political risk assessment is the most commonly overlooked gate and causes the most damage when ignored.

Correct: D. This question follows all three principles of non-defensive discovery: (1) It asks about the system ("how a deal moves"), not the person. (2) It expresses genuine curiosity ("what does that journey actually look like"), not camouflaged criticism. (3) By asking what it "actually" looks like, it implicitly validates that there may be a gap between the documented process and reality, opening the door for honest observation without defensive reactions.

Why not A: Leading with a negative metric puts the VP on the defensive. The framing implies accountability for the decline. The protocol principle is "Ask about the system, not the person." Introduce data later in the conversation after trust is established.

Why not B: Sharing fix ideas in your first 30 days, before completing discovery, is the Savior Complex failure mode in miniature. The discovery protocol surfaces information — it does not pitch solutions. If you enter with solutions, the other person tells you what you want to hear.

Why not C: This violates the protocol on multiple levels. "Several people have told me" reveals that you are collecting negative feedback about this person's domain. "Do you agree?" forces a binary response. People who feel investigated share what you want to hear, not what you need to hear.

Correct: A. Both approaches have defensible logic, but CRO Alpha's approach is more appropriate because it resolves the tension between transparency and relationship protection through the CEO preview mechanism. By previewing the finding with the CEO before the meeting, the CRO satisfies "Never surprise your CEO" and can align on messaging (including whether to name the account). The board presentation framework explicitly requires including findings with hard truths — concentration risk at 45% in two accounts is material. Omitting it entirely (CRO Beta's approach) creates a worse risk: if the board later discovers the at-risk account and learns the CRO knew at Day 50, credibility is permanently damaged. The CEO preview is what makes Alpha's approach work — it converts a transparency-vs-relationships tradeoff into a both-and solution.

Why not B: CRO Beta's approach has surface appeal — protecting relationships and validating before presenting are reasonable instincts. However, it underweights two factors. First, a 45% pipeline concentration is material risk that the board has a fiduciary need to understand regardless of the at-risk account detail. Omitting concentration data entirely is not an option, and presenting concentration without the risk signal is misleading by omission. Second, "validate first and present next quarter" assumes the risk will wait — if the account churns before the next board meeting, the CRO's credibility is destroyed. The CEO preview mechanism in Alpha's approach addresses Beta's legitimate concerns without accepting the downside risk of omission.

Why not C: The two approaches are not equally valid. Module 3's board presentation framework and political navigation principles provide clear criteria for evaluating them. Treating a judgment call as random ignores the analytical frameworks the module teaches.

Why not D: Skipping a board meeting is not a realistic option and signals a lack of readiness. The first board presentation is a credibility-establishing moment — avoiding it delays credibility-building by 90 days and creates board concern about the new CRO's engagement.

Correct: B. Three fundamental problems: (1) Restructuring the SDR team from 12 to 8 in the first 30 days is the Savior Complex in action — a 33% headcount reduction before completing discovery will terrify the organization and destroy trust. (2) A full strategic plan to the board at Days 31-60 is premature — Module 3 specifies that the first board presentation is a credibility presentation, not a strategy presentation. (3) No stakeholder mapping or political assessment anywhere means this CRO is flying blind on power dynamics. Additionally, the compensation plan at Days 31-60 violates the Low Political Risk criterion.

Why not A: Missing metrics and aggressive hiring are legitimate but secondary concerns. The critical failures are sequencing (structural changes before discovery) and political awareness (no stakeholder mapping). These are the problems that cause CRO tenure failure.

Why not C: "Too ambitious overall" is vague feedback that does not identify the specific failure patterns. CRM changes and win/loss analysis are actually reasonable early activities — the problem is that they coexist with far more disruptive changes that crowd out discovery time.

Why not D: The compensation plan is one of several serious problems. Calling it the "only" problem misses the SDR restructuring (Savior Complex), the premature board strategy presentation, and the complete absence of stakeholder mapping.