Issue 06 : The 30-60-90 Day Onboarding Framework
An operational case study from Northgate Services Group, exploring the decisions, constraints, and outcomes behind the issue.
Overview
Company : Northgate Services Group
Revenue : $85M
Industry : Facilities Management
Primary Dimension : D09 - Onboarding Effectiveness
Secondary Dimension : D01 - Process Documentation Coverage
Characters : Diana Reyes, Anika Patel, Paul Stevens
PART A
The new operations hire who started fixing things before she understood what she was fixing
Diana Reyes, the COO, had made the ERP hire specifically.
Anika Patel, Director of Operations Technology, came with exactly the credentials the role required: seven years in enterprise technology, two major implementations on her resume, and a track record of delivering on schedule.
She had been recruited to lead the ERP consolidation at Northgate Services Group — the project intended to resolve three legacy systems running simultaneously after two acquisitions. The ERP was the reason the role existed.
By the end of Week 2, Anika had a presentation ready for Diana. It was a recommended implementation sequence for the ERP consolidation.
The logic was sound. The sequence was defensible on its technical merits.
Diana read it carefully and asked Anika to hold.
What the presentation missed was context that can only come from knowing the organization well — vendor contracts tied to specific legacy system integrations, workarounds that field operations teams had built into the existing systems that any new system would need to replicate or consciously deprecate, and PE operating partner data visibility requirements for any transition period that no one had mapped against the proposed implementation sequence.
The two acquired companies' teams also held fundamentally different mental models of what 'operational data' meant — a conceptual difference that would surface as a data migration problem the moment implementation began.
Anika's recommendations were technically correct in the abstract.
They were missing the operational context that would have made them appropriate for Northgate specifically.
Diana asked Anika to spend the next four weeks in observation mode before making any implementation recommendations.
Anika pushed back.
She had been hired to lead an implementation. She wanted to start implementing.
Diana's response:
"You've been hired to lead an implementation that's appropriate for this company. You can't build that yet. You need 30 days of context first. The implementation will be better for it. I promise."
The pushback was understandable.
The standard instinct for any senior hire is to demonstrate value quickly to show the organization that the hiring decision was correct by moving fast on the problem they were hired to solve.
In most roles, that instinct is appropriate.
In operations leadership roles, where the problems being solved are deeply embedded in organizational context, moving fast on incomplete understanding produces recommendations that require more remediation than starting with a month of structured observation.
The most expensive operations hire is the one who starts making changes on Day 15. The most valuable is the one who spends Day 1 through Day 30 learning to understand what they are about to change.
The context problem affects every operations hire who joins from outside. The skills that made them excellent at a prior company were developed in a different operational environment.
Applying those skills to Northgate's specific situation requires first understanding what makes it different — the specific constraints, the informal workarounds, and the institutional decisions that look like process failures but reflect deliberate choices nobody has written down.
The observation phase is not a delay. It is the investment that determines whether the subsequent 11 months produce transformational outcomes or an expensive reset.
PART B
The senior hire who moves fast without context is not adding value. They're spending it.
Large companies have structured onboarding programs for senior operations hires — 30-60-90 day plans built before the hire arrives, a designated orientation sponsor, scheduled stakeholder introductions, and protected time for learning before producing.
Large companies have institutionalized the expectation that a senior hire needs 90 days before making consequential recommendations.
Mid-market companies have a start date, an urgent project, and a hiring process that surfaced the candidate's prior accomplishments in detail.
The implicit message is that the hire was made because of what they know and what they've done. Asking them to spend 30 days observing before acting feels like not using what you paid for.
This instinct is wrong in exactly the environments where it feels most justified, specifically when the project is urgent and the hire was recruited because of demonstrated execution capability.
In those situations, the 30-day observation phase is not a delay.
It's the minimum viable investment in making the execution appropriate to the actual environment.
What does the same problem look like at $85M, with an ERP consolidation already 18 months delayed and a new Director of Operations Technology who had a presentation ready by the end of her second week?
What The Data Shows
Anika Patel's 30-day observation phase at Northgate Services Group, enforced by Diana Reyes over Anika's initial objection, produced two specific discoveries that fundamentally changed the ERP implementation approach.
Discovery 1:
Nobody at Northgate, including Diana, knew that field operations teams from the two acquired companies were reconciling their daily activity data with Northgate's central reporting system manually, every Monday morning, completed by three people over approximately four hours.
This reconciliation was invisible in any documentation. It was the single largest source of data integrity risk in the ERP migration.
If Anika had begun implementation on Day 15, the consolidation would have inherited this manual reconciliation without understanding it.
The data integrity issues would have surfaced mid-migration, when they would be most expensive to resolve.
Discovery 2:
Anika could not determine whether the primary vendor contract for the field management software included data portability provisions.
It did not.
The absence of these provisions meant the ERP consolidation timeline needed to include a vendor renegotiation for the data export format before migration could begin.
Pilot result in Phase 2: A simplified data entry process for field teams reduced Monday reconciliation time from four hours to 45 minutes over a two-week pilot.
Paul Stevens's (VP of Vendor and Contract Management) assessment of Anika's decision quality at Day 90:
"Much better than what we would have gotten if she had started making changes in Week 2."
The Observation-First Onboarding Architecture : Three Phases
Phase 1: Observation Only (Days 1–30)
There is only one rule: No changes.
The new hire's job is to observe, document, and understand — not to fix things.
There are two reasons:
- The new hire lacks context to distinguish things that are broken and should be fixed from things that look broken but reflect a deliberate decision or a constraint not immediately visible.
- If genuine observation is done properly, it often reveals that the most obvious problems are symptoms of deeper causes that a quick fix wouldn't address.
The observation schedule must be built before Day 1.
It includes:
- Shadowing every team they'll interface with (minimum one full day per team).
- Reading all relevant documentation.
- Conducting the five-question interview with every key person.
- Reviewing the last 12 months of operational data in relevant domains.
The five-question interview used with every person the new hire meets in their first month:
- "What is working well in operations that you'd want me to understand and protect?"
- "What is consistently broken that has been accepted because it seems unfixable?"
- "What decision do you wish someone would make that nobody has made yet?"
- "What information do you need to do your job well that you consistently cannot get?"
- "What is the most important thing I should understand about this company or this function that I won't find in any document?"
The Phase 1 deliverable:
A written First Impressions Document submitted at the end of Day 30.
It is not an action plan but an observation log.
- 3–5 things working well and worth protecting.
- 3–5 things that appear broken, with honest acknowledgment that root causes aren't fully understood yet.
- Three questions the new hire can't yet answer because information is missing or inaccessible.
- One item for immediate discussion with their manager.
Phase 2: Hypothesis Testing (Days 31–60)
The new hire selects three improvements from the First Impressions Document and designs a bounded, reversible test for each.
Each test follows the same format:
- A hypothesis ("if we change X, then Y will improve").
- A test design (what specifically will be done, at what scope, in what timeframe).
- Success criteria (how will we know if this worked).
- A reporting date.
The Phase 2 deliverable:
A Hypothesis Report at Day 60.
- Three hypotheses.
- Three tests.
- Three outcomes.
- A recommendation on which improvements to scale, which to abandon, and which need more data.
Phase 3: First Domain Ownership (Days 61–90)
The new hire takes full ownership of one operational domain and executes it independently. Their manager is available for consultation but does not make decisions within the domain.
This phase tests whether the context built in Phases 1 and 2 produces better decision-making than an earlier start would have produced.
The Day 90 evaluation:
- Can the new hire operate this domain without daily guidance?
- What did they learn about their judgment in unfamiliar situations?
- Where does the organization need to invest in their further development?
What The Observation Phase Prevented
Anika's First Impressions Document contained 12 observations and three questions she described as "questions I cannot answer yet because the data I need is either inaccessible or nonexistent."
Two of those three inaccessible-data questions became the most important findings of the entire observation phase.
The Monday reconciliation discovery and the data portability gap would both have surfaced mid-implementation without the observation phase at the exact moment when they would be most expensive to address.
Diana's summary:
"The 30 days of observation didn't slow the project down. It prevented a project restart."
Dimensions
Apply
- The 30-60-90 Day Operations Hire Onboarding Checklist
- The 30-60-90 Day Operations Hire Onboarding Plan
Comments ()