You've been asked to build a People strategy, or maybe just to "be more strategic." You know the words: alignment, impact, partnership. But when you sit down to actually write the plan, you don't know where to start. So you start where it's comfortable, with what People teams usually do. L&D, an engagement survey, a hiring plan.
A People strategy doesn't start with People. It starts with the business, and it runs in one direction only.
Most People strategies fail before they're even presented, because they're built backwards. The instinct is to start with what the function knows how to do, then go looking for ways to connect it to the business afterward. What you end up with is a list of HR activities with a business rationale bolted on. Leaders can tell the difference, even when they can't say exactly why.
Once that happens, they stop treating you as a strategic partner and start treating you as a service provider. Getting back to the table takes a lot longer than getting there in the first place.
Every business exists to create value and grow it. Product is how it creates that value: what it builds or offers. Growth is how it turns that value into revenue and profit.
People sits at the intersection. Not a third lever. The thing that powers the other two. Hiring, structure, performance, culture: none of it matters by itself. It matters because it helps the business create value, grow value, or protect what it's already built.
You can't build a People strategy from inside People. Have direct, business conversations with your leaders, not HR conversations. Ask about where things stand, what's coming next, what's working and what isn't. Back it up with real sources: business plans, product roadmaps, revenue and financial reports, customer feedback.
In a lot of emerging-market businesses, none of that lives in a document. It lives in the founder's head, shaped by whatever they're dealing with that week. That's not a dead end. It just means more of what you learn comes from conversation, not paperwork, and from paying attention to where the money and time are actually going.
An assumption is a specific sentence about where the business is headed, not a vague sense that "things are tight." For example: "We're under margin pressure because of inflation, so leadership wants revenue up without growing the team." Or: "We're entering a new market where good people are hard to find and easy to lose."
You can't see the implication until you've written the assumption down. Skip that step and you end up guessing at solutions instead of building from evidence.
It's also why a People strategy can't be borrowed: not from a case study, not from your last company, not from your own playbook of things that worked before. A solution that worked once, somewhere else, isn't wrong. It's just the answer to a different question. Context isn't something you add at the end. It's what the whole thing has to be built from.
Business fact. Strategic assumption. People implication. That's the chain, and it only works in that order.
Pick one thing on your People plan right now. Can you say, in one sentence, the business fact and the assumption it traces back to? If you can't, that's what needs fixing, not the plan around it.