The leadership team's trust in a newly appointed CRO cannot be decreed: it is built over 90 days through structured one-on-ones with each executive peer, a first collective presentation grounded in a data-driven diagnostic, and disciplined behavior in the monthly rituals. Unlike the CEO, who expects a vision, or the teams, who expect a framework, the leadership team peers evaluate a harder dimension: perceived competence, operational reliability, and respect for functional boundaries. A CRO who neglects this audience loses the political battle before it has even begun.
In B2B scale-ups between €10M and €100M in ARR, the leadership team is the hardest audience for a CRO taking on a new role. Each member arrives with their own frame of reference, accumulated frustrations with the revenue function, and a defensive agenda around their own territory. On the ground, our Revenue Health Score diagnostics conducted with B2B scale-ups reveal a consistent pattern: CROs whose tenure exceeds 24 months have systematically run a structured 60-minute one-on-one with each leadership team member in their first 30 days, presented their collective diagnostic before day 40, and put in place a monthly ritual where they share not just numbers but also decisions to be arbitrated. Conversely, CROs whose tenure gets cut short have treated the leadership team as a secondary audience, focused solely on the CEO.
This guide details the five leadership archetypes on the leadership team and their evaluation criteria, the three-pillar trust-building framework, the agendas for the five bilateral one-on-ones in the first 30 days, the structure of the first collective presentation on day 35, the behaviors that build or destroy trust, peer-specific tactics, the monthly ritual to put in place from day 60 onward, and the signals used to assess the onboarding at 90 days.
Key Takeaways
- The leadership team is not a single audience: five archetypes (CFO, CMO, CTO, CHRO, COO) with five distinct evaluation criteria, each requiring a different approach strategy.
- Bilateral one-on-ones take place in the first 30 days, never at the same time as the collective diagnostic. The CRO listens to each person before speaking to everyone.
- The first collective leadership team presentation takes place on day 35, backed by the data-driven diagnostic. Not before, not after.
- Three pillars of trust: competence (proven by an accurate reading of the numbers), reliability (keeping commitments, even small ones), and respect (not encroaching on functional territories).
- Four behaviors destroy trust: overpromising, taking credit for others' successes, ignoring peers' expertise, and playing political moves instead of keeping commitments.
- Monthly ritual: the CRO arrives at the leadership team meeting with two numbers, one decision to make collectively, and one topic where they ask for help. This format repeats identically every month.
- Success criterion at 90 days: at least three out of five leadership team members publicly defend an initiative led by the CRO in a meeting where the CRO is absent. This signal is worth every internal NPS score.
"The political capital of a new leader is not built by winning victories, but by avoiding unnecessary defeats. Every poorly chosen conflict costs more than it delivers, and every well-built alliance delivers more than it costs."
Michael Watkins, The First 90 Days (Harvard Business Review Press)
Why the Leadership Team Is the Hardest Audience for a New CRO
The CRO-CEO relationship is structured by hierarchy. The CRO-team relationship is structured by authority. The CRO-leadership team relationship is structured by nothing: these are peers, each with their own mandate, their own established credibility, and their own interests. It is this absence of imposed structure that makes the exercise difficult.
Peers, Not Subordinates
A CMO or CFO who has sat on the leadership team for three years has no hierarchical obligation toward the new CRO. They will judge, compare, filter what they share, and unilaterally decide how much credit to give the newcomer's proposals. In our diagnostics, CROs who fail their onboarding almost all share one mistake: they treated their leadership team peers as people to convince rather than partners to understand. Alliances fail to form, silent opposition emerges at the worst possible moment, and the CRO onboarding stalls despite a solid diagnostic.
An Audience That Has Already Seen Other CROs Come and Go
In scale-ups with more than 50 people, the incoming CRO is often at least the second person to hold this role. Leadership team members have long memories: broken promises, failed restructurings, imported playbooks that didn't work. Our diagnostics show that in 60% of cases, at least one leadership team member expresses a reservation inherited from the previous CRO during individual interviews, often without the CEO being aware of it. Identifying this reservation in the first 30 days is a critical lever that most CROs overlook.
The Leadership Team Is the Invisible Tribunal of the Mandate
The CEO formally decides whether a CRO mandate continues, but the leadership team influences that decision massively. A CRO who loses their CFO's trust sees their budgets challenged. A CRO who loses their CMO's trust sees their marketing-sales alignment deteriorate. A CRO who loses their CHRO's trust sees their hiring slow down. Each peer holds levers that can make the CRO's life very difficult without ever triggering open conflict.
The 5 Leadership Archetypes on the Leadership Team and Their Evaluation Criteria
Each leadership team member evaluates a new CRO through a specific lens tied to their own function. Understanding these five lenses makes it possible to tailor the message and the evidence to bring.
The CFO: Fiscal Discipline and Unit Economics Credibility
The CFO is looking for an operator who understands unit economics, speaks fluently about ARR, NRR, and CAC payback without confusion, and doesn't ask for more budget than they can justify.
| Dimension Evaluated | Expected Evidence | Warning Signal |
|---|---|---|
| Unit economics understanding | CAC payback, NRR, and burn multiple cited spontaneously | Talks only about pipeline and closing rate |
| Forecast discipline | Forecast accuracy analyzed against the prior quarter | Forecast with no variance analysis |
| Budget discipline | Quantified requests with ROI and timeline | "We'd need more..." |
| Data literacy | Asks for P&L by business unit, cohorts, retention | Only asks for sales figures |
| Posture | Partner who challenges assumptions | Salesperson defending their budget |
Winning over the CFO requires immediate proof: in the first one-on-one, arrive with two or three precise questions about current unit economics, show that you've read the latest revenue reporting, and put forward a hypothesis on an angle they haven't explored.
The CMO: Alignment or Territorial Defense
The CMO is often the most complex counterpart. Marketing-sales friction has historically been the arena where the CRO arbitrates, which puts them on the defensive. They wonder whether the new CRO will respect their autonomy or absorb marketing into the revenue sphere.
| Dimension Evaluated | Expected Evidence | Warning Signal |
|---|---|---|
| Respect for territory | Talks partnership, not integration | Suggests a reorganization on day 1 |
| Marketing cycle understanding | Distinguishes brand, demand gen, lifecycle | Only talks about "leads" |
| SLA capability | Proposes a measurable marketing-sales SLA | Imposes MQL quotas with no discussion |
| Recognition of contributions | Cites campaigns that worked | Attributes all pipeline to sales reps |
| Posture | Co-owner of the pipeline | "Marketing should serve sales" |
The CRO-CMO relationship is often sealed on a single topic: formalizing a jointly written SLA within the first 30 days. A CRO who imposes a unilateral vision creates a permanent adversary.
The CTO: Data and Tooling Constraints
The CTO evaluates the CRO's ability to frame data needs that are compatible with technical constraints. They have often been frustrated by previous CROs who demanded CRM integrations without understanding technical debt.
| Dimension Evaluated | Expected Evidence | Warning Signal |
|---|---|---|
| Data maturity | Understands data warehouse vs. CRM vs. BI | Wants everything in Salesforce with no prioritization |
| Respect for IT process | Asks IT for input before signing a tool | Shows up with a tool already selected |
| Technical debt | Accepts a 6-12 month phasing | Demands everything for the next quarter |
| CRM governance | Talks data ownership, quality | Treats the CRM as an isolated tool |
| Posture | Partner who factors in constraints | Client who demands deliverables |
The CTO's trust is earned by spontaneously addressing CRM data quality and CRM governance as early as the first one-on-one, while acknowledging the complexity.
The CHRO: HR Practices and Process
The CHRO judges a CRO on their ability to manage people issues without creating HR chaos. A CRO who doesn't address this upfront finds that their hiring takes three months instead of three weeks.
| Dimension Evaluated | Expected Evidence | Warning Signal |
|---|---|---|
| HR process | Asks about comp and hiring policies | Announces comp plans outside the framework |
| Departure management | Informs before any departure decision | Learns about a departure through the grapevine |
| Hiring | Shares scorecards and interview frameworks | Unstructured interviews |
| Retention | Talks patterns, not isolated cases | Treats every departure as an accident |
| Posture | Co-owner of the revenue team's climate | Autonomous on people matters |
Winning over the CHRO requires a specific initiative: asking for the retention patterns of the past 12 months and sharing your analysis a week later with 2-3 hypotheses to challenge together.
The COO or CPO: Operational Maturity
The COO evaluates the CRO's ability to put in place structured processes and robust management rituals, rather than steering by instinct with chaos that spreads through the organization.
| Dimension Evaluated | Expected Evidence | Warning Signal |
|---|---|---|
| Process discipline | Written playbooks | Everything runs on sales charisma |
| Management rituals | Pipeline reviews, QBRs, executive reviews | Ad hoc meetings based on mood |
| Cross-functional interfaces | Documented handoffs with product, support, ops | Case-by-case management |
| Scalability | Choices that hold up if the team doubles | Small-scale solutions |
| Posture | Disciplined operator | Solo operator |
The COO is won over by presenting, on day 20, the calendar of rituals to put in place, with objectives and how they connect across functions.
The Three-Pillar Trust-Building Framework
The leadership team's trust is built on three cumulative pillars: demonstrated competence, repeated reliability, and respect for boundaries. None of the three is sufficient on its own, and the absence of just one is enough to weaken the whole structure.
Competence Demonstrated Through Facts
Perceived competence doesn't come from a resume, but from repeated micro-signals: correctly reading a cohort table at a glance, spotting an anomaly in a funnel, citing a precise figure without checking notes. Every leadership team peer tests this competence without saying so.
| Signal Type | Concrete Example | Perceived Impact |
|---|---|---|
| Quick data reading | "Your churn shifted in Q3, is that linked to the January 2026 cohort?" | Strong competence |
| Precise technical vocabulary | Correct use of NRR, GRR, logo retention, CAC payback | Immediate credibility |
| Anomaly detection | "Win rate is climbing but ACV is dropping, what's the trade-off?" | Operational expertise |
| Industry benchmarks | Referencing sector medians with no approximation | Analytical maturity |
| Common mistakes | Confusing ARR and MRR, gross churn and net churn | Instant loss of credibility |
Reliability Through Commitments Kept
Keeping commitments, even the smallest ones, signals an operational discipline that reassures peers. Missing a minor commitment, "I'll send you the document tomorrow" followed by three days of silence, costs far more than it appears to. The CROs who inspire the most trust only make commitments they can keep, and proactively communicate when a deadline is going to slip.
Respect for Functional Boundaries
A CRO who comments on the CMO's brand choices, the CTO's stack, or the CHRO's compensation decisions triggers defensive mechanisms that are hard to defuse. Respecting boundaries isn't passivity: the CRO can challenge decisions that affect revenue, but through a prepared bilateral dialogue, never in a leadership team meeting before testing the argument in a one-on-one.
One-on-Ones with Each Leadership Team Member in the First 30 Days
The five bilateral one-on-ones structure the listening phase beyond the first one-on-one with the CEO. Each one-on-one lasts 60 minutes, takes place face to face, and follows an agenda tailored to the archetype. The goal isn't to sell a vision, it's to listen, map, and build the three pillars of trust.
Sample Agenda: One-on-One with the CFO (60 min)
| Block | Duration | Objective | Key Questions |
|---|---|---|---|
| Context and current view | 15 min | Understand their view of revenue | What are the 3 numbers you track monthly? Where do you see the biggest risks? |
| Unit economics and forecast | 20 min | Demonstrate technical mastery | What has forecast accuracy been over the past 6 months? Which cohort worries you most? |
| Investment priorities | 15 min | Understand the constraints | Where are you willing to invest, and where do you hold strict discipline? |
| Ritualization and reporting | 10 min | Align expectations | What reporting frequency and format do you expect from the CRO? |
Sample Agenda: One-on-One with the CMO (60 min)
| Block | Duration | Objective | Key Questions |
|---|---|---|---|
| Marketing and revenue vision | 15 min | Understand their view of the funnel | How do you define marketing success in this organization? |
| Historical frustrations | 15 min | Map past tensions | What recurring friction have you had with sales? What has been tried and abandoned? |
| SLA and ownership | 20 min | Co-build the rules | What would be your ideal definition of an MQL? Who owns the pipeline? |
| 2026 priorities | 10 min | Align on milestones | What are your 2-3 big marketing initiatives this year? |
Sample Agenda: One-on-One with the CTO (60 min)
| Block | Duration | Objective | Key Questions |
|---|---|---|---|
| Data architecture | 20 min | Understand technical maturity | What is the source of truth for revenue data today? Where is the single source? |
| CRM technical debt | 15 min | Identify constraints | Which CRM changes are feasible in 6 months vs. 18 months? |
| Governance and security | 15 min | Understand the framework | What tooling governance principles should I know about? |
| Ways of working | 10 min | Align on process | How do you want to be consulted on revenue tooling decisions? |
Sample Agenda: One-on-One with the CHRO (60 min)
| Block | Duration | Objective | Key Questions |
|---|---|---|---|
| State of the revenue team | 15 min | Listen to their view | How do you assess the health of the sales team today? |
| Retention patterns | 15 min | Identify early warning signals | Who has left in the past 12 months, and why? |
| Comp and hiring policy | 20 min | Understand the framework | What comp plan and hiring principles need to be respected? |
| Ways of working | 10 min | Establish the protocol | How do you want to be involved in sensitive decisions? |
Sample Agenda: One-on-One with the COO or CPO (60 min)
| Block | Duration | Objective | Key Questions |
|---|---|---|---|
| Process maturity | 15 min | Understand their standards | Which operational rituals work well today? Which are missing? |
| Cross-functional interfaces | 20 min | Map the handoffs | Where are the main friction points between revenue and other functions? |
| Operational priorities | 15 min | Align on expected maturity | What level of structure do you expect from the revenue function within 12 months? |
| Ways of working | 10 min | Establish the cadence | How do you want us to collaborate on cross-functional initiatives? |
Evaluez votre maturite sur les 8 piliers en 2 minutes. Score instantane, gratuit.
Faire le quiz gratuit →The First Collective Leadership Team Presentation (Day 35)
The day-35 presentation is the tipping point: the listening phase ends and the shared-diagnostic phase begins. The point isn't to present a roadmap, but to demonstrate that you've listened, understood, and are ready to offer a structured perspective.
Presentation Structure (60 min)
| Block | Duration | Content | Objective |
|---|---|---|---|
| What I did in 35 days | 5 min | Interviews, data reviewed, sources | Rigor of the diagnostic |
| Data-driven state of play | 15 min | 8 to 10 key metrics with benchmarks | Factual understanding |
| Major findings | 15 min | 5 to 7 findings with business implications | A fresh perspective |
| Points requiring attention | 10 min | Risks requiring a leadership team decision | Engaging peers |
| Priorities for the next 60 days | 10 min | 3 to 5 initiatives with named sponsors | Projecting what's next |
| Discussion and questions | 5 min | Opening up dialogue | Testing reactions |
The supporting document must be written, shared 48 hours before the meeting, and fit into 15 to 20 slides. Every finding must trace back to at least two independent sources: a CRM figure, an interview verbatim, a financial figure. The presentation explicitly names leadership team members' contributions when they inform a finding. A CMO who hears "as [First Name] identified in our one-on-one" feels heard. This small gesture has an outsized effect.
Six behaviors to avoid: announcing structural decisions (the decision phase comes later), publicly criticizing a peer (breaks the implicit alliance), running past 60 minutes (operational indiscipline), presenting without a written document shared beforehand, using jargon-heavy vocabulary, ignoring contributions received during one-on-ones.
Behaviors That Build Trust Versus Those That Destroy It
The leadership team's trust is built through hundreds of micro-interactions over the first 90 days. The list below consolidates the patterns observed in our diagnostics.
| Behavior That Builds Trust | Behavior That Destroys Trust |
|---|---|
| Underpromise and overdeliver | Overpromise and underdeliver |
| Credit peers for their contributions | Take credit for collective successes |
| Inform before acting on a cross-functional matter | Act first, inform afterward |
| Acknowledge a mistake quickly | Minimize or deflect responsibility |
| Honor minor commitments to the letter | Let small commitments drag on |
| Share information proactively | Withhold information as leverage |
| Acknowledge peers' expertise on their territory | Challenge expertise without preparation |
| Raise disagreements in one-on-ones before the group | Challenge a peer in a leadership team meeting with no warning |
Four behaviors consistently emerge as the major destroyers of trust. Overpromising: announcing as early as day 10 that you'll double the pipeline signals either a disconnect from the ground or a worrying degree of narcissism. Taking credit for success: a CRO who says "my team delivered" where a peer would have talked about a collective success gets noticed negatively. Playing politics: using access to the CEO to influence decisions without prior bilateral dialogue creates lasting resentment. Ignoring peers' expertise: questioning the CMO's marketing vision, the CTO's architecture, or the CHRO's comp practices without acknowledging their expertise leads to prolonged conflict.
Peer-Specific Tactics to Win Their Alignment
Beyond the general framework, each peer is won over by a tactic that answers their specific evaluation criteria.
Winning the CFO: Unit Economics Before They Ask for Them
Presenting a CAC payback table by segment, trailing 12-month retention cohorts, and a comment on the burn multiple before the CFO asks for them reverses the usual dynamic. They stop being a controller who questions and become a partner who arbitrates.
Aligning the CMO: Writing an SLA Jointly
Proposing on day 30 to jointly build a formal marketing-sales SLA, completing it together by day 45, and announcing it jointly at the leadership team meeting on day 60 creates a strong operational alliance. The CRO signals that they see marketing as a co-owner of the pipeline, not a vendor.
Winning the CTO's Buy-In: A Phased Data Initiative
Proposing a revenue data initiative phased over 6 to 12 months, with quarterly deliverables and a clear acknowledgment of existing technical debt. Presented as an IT-Revenue project, not a CRO request to IT.
Building the Relationship with the CHRO: Retention Patterns
On day 20, ask for the departure patterns of the past 12 months within the revenue function, then come back a week later with an analysis and 2-3 hypotheses to challenge together. This initiative signals a CRO who treats their team's retention as a strategic matter.
Winning the COO or CPO: The Ritual Calendar
Sharing, on day 20, the calendar of operational rituals to be put in place within 90 days, with objectives, participants, and interfaces with other functions. This short document demonstrates the expected operational maturity.
The Monthly Leadership Team Ritual: Building Lasting Trust
From day 60 onward, the CRO takes part in the monthly leadership team meetings as a full member. A format repeated month after month builds the predictability that reassures people.
| Section | Duration | Content |
|---|---|---|
| Two numbers that matter | 3 min | The number that reassures, the number that worries |
| One decision to make collectively | 5 min | A trade-off where the CRO needs the leadership team |
| One topic where I ask for help | 3 min | Acknowledging a difficulty and asking peers for input |
| What's changing this month | 2 min | New rituals, adjustments |
| Leadership team questions | 7 min | Direct answers, no defensiveness |
This 20-minute format builds three virtuous dynamics: the monthly request for help normalizes collaboration, the collective decision gives peers an active role, and predictability reduces political uncertainty. Three disciplines protect it over time: never overpromise in "what's changing," systematically acknowledge peers' contributions from the previous month, and never use the ritual to settle scores.
Trust at the Board Level, When Relevant
In scale-ups that have raised funding, the CRO must also build credibility with board directors. This audience evaluates strategic maturity and the ability to tell a revenue story that holds together, more than operational execution.
| Dimension Evaluated | Positive Signal | Negative Signal |
|---|---|---|
| Strategic maturity | The CRO talks mix, cohorts, investments | They only talk about the current month or quarter |
| Narrative ability | They articulate a clear revenue thesis | They recite numbers with no storyline |
| Market understanding | They cite relevant industry benchmarks | They only talk about internal matters |
| Reading early signals | They anticipate risks 6-12 months out | They comment on past numbers |
| Posture | Partner in the growth plan | Operator who executes |
The first board presentation is prepared around day 60 or 90, working on the narrative structure beforehand with the CEO and CFO. It isn't a sales report: it's a strategic address.
Template: 30-Day Leadership Team Interaction Plan
| Day | Interaction | Duration | Main Objective |
|---|---|---|---|
| Day 1 | Initial CEO one-on-one | 90 min | Align expectations and secure the mandate |
| Day 2 | CEO summary email | 30 min | Confirm points of alignment |
| Day 4 | CFO one-on-one | 60 min | Listen to their view of revenue, demonstrate unit economics competence |
| Day 6 | CMO one-on-one | 60 min | Map frustrations and open the SLA topic |
| Day 8 | CTO one-on-one | 60 min | Understand the data debt and position the collaboration |
| Day 10 | CHRO one-on-one | 60 min | Listen to retention patterns and frame the processes |
| Day 12 | COO or CPO one-on-one | 60 min | Share the vision for rituals and listen to expectations |
| Day 15 | CEO one-on-one (check-in) | 60 min | Share signals gathered from leadership team one-on-ones |
| Day 18 | CFO follow-up: unit economics analysis | 45 min | Deliver a perspective, prove competence |
| Day 20 | CHRO follow-up: retention analysis | 45 min | Deliver a perspective, prove competence |
| Day 22 | CTO follow-up: data initiative proposal | 45 min | Provide a framework, prove structure |
| Day 25 | CMO follow-up: SLA project | 60 min | Co-build the marketing-sales SLA |
| Day 28 | COO follow-up: share ritual calendar | 30 min | Provide operational structure |
| Day 30 | CEO one-on-one (leadership team prep) | 60 min | Align on the diagnostic before the collective presentation |
| Day 32 | Diagnostic document shared | async | Send the leadership team deck 48 hours before the meeting |
| Day 35 | First leadership team presentation | 60 min | First collective moment, listening phase complete |
This schedule is a reference, not a rigid plan. It must adapt to peers' availability and business emergencies. What matters is respecting the logical sequence: listen to each person one-on-one, come back with a prepared analysis, and only then address the group.
Signals to Assess the Onboarding at 90 Days
At 90 days, the CRO should be able to objectively assess the quality of their relationship with the leadership team. The following signals are diagnostic.
| Signal | Interpretation If Present | Interpretation If Absent |
|---|---|---|
| A peer publicly defends a CRO initiative | Alliance built, positive political capital | Emerging isolation |
| A peer spontaneously asks the CRO's opinion on their own territory | Mutual respect established | Strictly transactional relationship |
| The CFO approves the 2026 budget with no major pushback | Financial credibility established | Doubt about unit economics discipline |
| The CMO offers to co-sign a pipeline initiative | SLA and collaboration in place | Defensive boundary maintained |
| The CHRO treats revenue hiring as a priority | Operational trust established | Persistent HR bottleneck |
| The CTO offers to get ahead on a data initiative | Technical partnership built | Client-vendor relationship |
| The CEO shares positive feedback received about the CRO | External capital built for the CRO | Siloed CEO-CRO relationship |
A CRO who checks off at least five of these seven signals at 90 days can consider their leadership team onboarding a success. Below three, they should have a frank conversation with their CEO to identify areas for correction before day 120.
The Mistakes That Sink a CRO's Standing with the Leadership Team in Under 90 Days
Some mistakes are disproportionately costly because they set in as first impressions that are hard to correct.
Publicly Challenging a Peer in a Leadership Team Meeting
A CRO who openly disagrees with the CMO, CFO, or CTO in a leadership team meeting, even on a factually justified point, creates an enemy for at least 12 months. The topic should have been addressed in a bilateral one-on-one before the meeting.
Missing a Commitment Made to a Peer
Promising the CFO a document by Friday and not sending it, with no advance communication, spends a reserve of trust that will take weeks to rebuild. Most CROs taking on a new role underestimate the discipline required around minor commitments.
Publicly Taking Credit for a Collective Success
The first visible revenue success in the first 90 days is often the result of several functions working together. A CRO who takes credit for this success without acknowledging marketing, ops, or support turns a moment that should have strengthened alliances into a trust destroyer.
Going Around a Peer Through the CEO
Using privileged access to the CEO to secure a decision on a peer's territory, without prior bilateral dialogue, is the most costly political violation. The peer involved will find out and will view the sequence as a lasting betrayal.
Treating the Leadership Team as an Audience to Convince
A CRO who approaches every leadership team interaction as a sales pitch positions themselves as an outsider. Peers feel pitched to and react defensively. The effective approach is the opposite: a full member, co-owner of revenue alongside their peers.
Additional Resources
- CRO 100-day plan: taking on the role
- CRO revenue audit: onboarding method
- First CRO-CEO one-on-one: structured agenda
- Leadership team revenue alignment: rituals
- Executive Review: management ritual
- Revenue reporting: essential metrics
- B2B CAC: customer acquisition cost
- Revenue financial control: unit economics
- Marketing-sales SLA: MQL-SQL
- Aligning marketing, sales, and customer service
- Sales forecast: accuracy
- CEO real-time visibility: dashboards
- Internal communication and sales alignment
- ACROSS Methodology
Sources Cited
- Our Revenue Health Score diagnostics conducted with B2B scale-ups (€10M to €100M ARR)
- Michael Watkins, The First 90 Days: Proven Strategies for Getting Up to Speed Faster and Smarter, Harvard Business Review Press, revised edition, 2013
Article written by Charles-Alexandre Peretz, founder of ACROSS Insight. Last updated: August 12, 2026.