The First 100 Days of People Ops in a Startup: What Actually Matters
đź§ The First 100 Days of People Ops in a Startup: What Actually Matters
You’re the first People hire in a fast-moving startup.
The founder says: “We need HR, but make it lean.”
Now what?
đź’ˇ The Reality of Day One
Startups don’t need full HR “infrastructure” at the beginning.
But they do need clarity, compliance, and culture scaffolding.
And the first 100 days in a People Ops role aren’t about complexity.
They’re about momentum and trust.
This article lays out the must-handle priorities and what to ignore early on, whether you’re a new HR Manager, Fractional Head of People, or founder-turned-ops lead.
âś… What Actually Matters in the First 100 Days
1. Build Context Before You Build Systems
Don’t roll out policies on Day 2.
Start by learning:
What’s working (and what’s breaking) in the team today?
What does the founder expect from you — really?
How does this team actually communicate and make decisions?
đź§ Start with interviews, not frameworks.
📌 Bonus: Review your scope. You might’ve been hired as a "Head of People" when what they really need is a People Ops Generalist.