The shift you're already making
If you're reading this, you've probably seen the pattern: senior operators — VPs, directors, founders — who used to run teams of 5-15 people are now shipping the same output alone, with AI as their force multiplier.
That's not hype. That's the new operating model. The market calls them High-Impact Individual Contributors. Mike Krieger (Instagram co-founder, now at Anthropic) is the canonical example: from CPO of a 4-person founding team to senior engineer at 35.
But becoming an HIC isn't about "using ChatGPT more". It's about restructuring your entire workflow around what AI does well — and refusing to do what it doesn't.
What AI is good at (for operators)
- Drafting memos and decision docs: rough draft in 90 seconds vs your 45 minutes
- Synthesizing research: 12 PDFs to 3 bullets in 10 minutes
- Meeting prep: agenda + talking points + likely objections, structured
- Pattern matching: "what would a great pitch deck for this look like, given these constraints?"
- First-pass screening: 80 LinkedIn profiles to 10 worth a call
- Boilerplate: hiring outreach, vendor evals, status updates
What AI is bad at (for operators)
- Knowing your context without you telling it
- Making real decisions (it can structure options, but the call is yours)
- Reading rooms (don't outsource human dynamics)
- High-stakes external comms (board, investors, key customers — review every word)
The HIC's CLAUDE.md
Same idea as a developer's, but for *your* operating context. Instead of stack, conventions, code structure — yours captures:
- Who you are (role, scope, what you actually own)
- Who your stakeholders are (board, peers, reports, customers — and what each expects)
- What you're optimizing for (this quarter, this year)
- Your communication style (tone, length, channels you prefer)
- Boundaries (don't draft this kind of message; don't make this kind of decision for me)
Claude reads it every session. You stop re-explaining who you are every time.
The HIC's MEMORY.md
What makes you faster is persistent context: the decisions made, the people involved, the patterns that worked.
Pattern that landed: opened with what we cut (not just shipped), then asked for help on the 1 thing we're stuck on.
Don't repeat: 18 slides on metrics. Board prefers narrative + 1 chart per claim.
Next time: bring exec summary as 1-page memo, slides as backup only. ```
Three months later you're prepping for another board meeting. You read this in 10 seconds. You don't relearn the lesson.
The shift from manager to maker
Most operators got promoted by getting good at coordinating: meetings, alignment, removing blockers for others.
The HIC mindset is the opposite: what is the actual artifact I'm producing today?
- Not "I'm having a strategy review meeting"
- "I'm producing the Q3 strategy doc"
- Not "I'm in 5 customer calls"
- "I'm producing the customer feedback synthesis + 3 product asks"
The meetings serve the artifact, not vice versa. AI helps because it can take half-formed thinking and turn it into a first draft of the artifact in 5 minutes.
Your first task
Open the CLAUDE.md that came with your pack. Skim it. Then sit for 20 minutes and answer:
- What are the 3-5 artifacts I produce that have outsized impact? (memos, decision docs, pitches, hiring screens, etc.)
- Which one of those, if I had a great AI workflow for it, would save me 5+ hours next week?
That's your starting point. In Module 1 we'll build the foundation: structuring your AI stack so it knows what *you* produce, for *whom*, and *why*.