Strategic Context for Strategy Team Onboarding

A new strategy hire — senior PMM, director of marketing, chief of staff — typically spends their first 90 days trying to understand what the company believes about itself. They attend meetings, read documents, ask senior peers questions, and gradually assemble the strategic picture. The process is slow, inefficient, and produces variable outcomes: some hires ramp quickly and accurately; others take 6 months and still operate with incomplete context.

The onboarding infrastructure below collapses the 90 days to 14. It's the same strategic-context infrastructure that serves the CEO-transition need but applied specifically to onboarding new hires. The investment is the same — the four context documents from the strategic-context memory work. The onboarding application is a specific, high-return use case.

The onboarding infrastructure

The infrastructure is the same four documents that serve strategic-context memory more broadly:

• The positioning brief (current version, with version history)
• The strategic-decisions log (chronological, with reasoning)
• The open-questions inventory (what's currently unresolved)
• The market-and-competitive landscape (what's happening externally)

Plus one onboarding-specific artifact: a reading-sequence guide that orders these documents for fastest comprehension.

The 14-day reading sequence

The 14-day sequence replaces ambient learning with structured reading plus targeted conversations. The new hire covers the strategic context in a deliberate order that mirrors how understanding builds.

The 14 days are structured reading plus targeted conversations. The new hire emerges with context approximately equivalent to what ambient learning would produce in 90+ days.

What to put in each document specifically for onboarding

The four documents exist for strategic-memory purposes broadly. The onboarding use case benefits from specific additions.

Addition to the positioning brief: the "what's contested" section

A section in the brief that names what's currently contested about the positioning. Which layers are solid; which are still in active discussion. A new hire encountering the brief benefits enormously from knowing which parts to take as canonical and which parts are still being worked.

Example 'what's contested' entries

Without the contested section, new hires assume the whole brief is canonical and can't tell what to treat as working-draft. The section saves confusion.

Addition to the decisions log: the "still-living" flag

Some decisions in the log are closed (executed and observed). Others are still-living — the decision has been made but the execution is ongoing or the reversal conditions haven't played out yet. A flag on each entry indicating status helps new hires understand which decisions are historical reference and which are active operating commitments.

Addition to the open-questions inventory: priority ranking

The inventory lists questions the company is carrying. Not all are equally urgent. A priority ranking (P0, P1, P2) helps new hires understand which questions matter most in the next 90 days and which are longer-horizon. Without the ranking, new hires either under-prioritize urgent questions or over-focus on non-urgent ones.

Addition to the landscape: "what changed recently"

The quarterly landscape document includes a specific "what changed since last quarter" section. For new hires reading the most recent version, this section highlights what's most important to understand. Without it, new hires have to diff the current version against the prior version themselves.

The manager's role

The new hire's manager plays a specific role in the onboarding beyond setting up the documents.

The manager's time investment in the 14 days is roughly 4–5 hours total. This is the specific time cost that accelerates ramp; without it, the documents exist but the new hire's interpretation is unguided.

What this replaces

Onboarding through structured sequence replaces three specific slower patterns.

Pattern 1: The 90-day ambient learning. The default pattern at most companies. New hire attends meetings, reads random documents, has ad-hoc conversations with people. Eventually assembles context. Takes 90 days typically.

Pattern 2: The "just start working" approach. No explicit onboarding; the new hire starts working on whatever their role's first task is. Learns context through the task. Produces context gaps that show up as mistakes in their first month's work.

Pattern 3: The extensive training program. Formal training on company history, product, processes. Takes 2–4 weeks but often focuses on operational content (how we use Salesforce, how our approval process works) rather than strategic context. Leaves strategic understanding to ambient learning.

The 14-day sequence is faster than pattern 1, more structured than pattern 2, and more strategically focused than pattern 3. For strategy hires specifically, the combination produces better outcomes than any of the three alternatives.

When the sequence doesn't apply

The 14-day sequence is calibrated for senior strategy hires. It doesn't fit all roles equally.

Works well: Senior PMMs, chiefs of staff, directors of strategy, heads of marketing, competitive-intelligence leads, VPs of strategic functions.

Works moderately: Senior ICs in strategic roles who need strategic context for their work but aren't primarily strategic themselves. Adjusted sequence (maybe 10 days instead of 14) works.

Doesn't fit: Engineering roles, sales IC roles, CS roles, operational roles where strategic context is relevant but not primary. Standard role-specific onboarding plus lighter exposure to some of the documents is more appropriate.

The sequence is deliberately heavy on strategic-context work because that's what strategy hires need. Applied to non-strategy roles, it would produce under-trained role-specific capability.

The compounding value

Companies that maintain the strategic-context infrastructure and run structured onboarding find that strategy hires ramp consistently faster. The hire-after-hire improvement compounds: the first hire to go through structured onboarding ramps in 5 weeks instead of 10; the second hire benefits from improvements the first identified; by the third hire, the onboarding is refined to where ramp is consistent.

Companies without the infrastructure ramp each hire through ambient learning, which produces variable outcomes that never improve. The first hire takes 10 weeks; the tenth hire still takes 10 weeks because nothing compounded.

The investment — maintaining the four documents continuously plus the manager time for onboarding — is modest. The return across multiple hires over multiple years is substantial. Strategy functions that onboard this way become meaningfully more productive than strategy functions that don't.