You sit in a leadership meeting and someone says margins are under pressure, a competitor is undercutting on price, or currency movement has pushed costs up. You nod along. You don't actually know what any of that means for the business, or what you're supposed to do with it. So you wait for the conversation to reach something you understand, and start there instead.
When you hear something in a business conversation you don't fully follow, it's almost always one of three things: a money question, a macro question, or a customer question. Naming which one it is turns confusion into a question you can actually ask, instead of a nod.
Most People professionals are never taught to read a business. So when leadership talks about margin, inflation, or customer churn, the instinct is to either stay quiet or nod and hope it doesn't come up again. That gap costs more than a moment of discomfort in the room. Without it, you cannot tell whether what you just heard is something solid enough to build on, or just noise that sounded important.
This shows up later as a People roadmap built on a misread. You hear "we need to control costs" and jump straight to freezing headcount, when the real driver might be turnover: replacing people usually costs more than keeping them, so investing in retention could save the business more than a hiring freeze would. By the time the plan doesn't land, it looks like a strategy problem. It was a literacy gap the whole time.
A business runs on three things worth being able to read: its money, the environment around it, and the customer it exists to serve.
None of these are optional extras for a People professional. They're what let you actually understand what's happening in the business, instead of just repeating back what leadership said.
Revenue, margin, and cash flow sound similar but tell you different things: what's coming in, what's actually left after costs, and whether the business has money on hand right now. People often use them loosely in conversation, so if someone says revenue is up but sounds worried, that's your cue to ask about margin or cash flow instead. That's usually where the real problem is.
Build this over time by finding your finance leader and asking them to walk you through your own company's numbers like you're five: what the current margin actually is, what's driving it, what would need to be true for it to improve. Real numbers from your business will teach you more in one conversation than a general finance module will in a week. Napkin Finance's business and entrepreneurship section is a plain-language reference for the vocabulary itself.
If your CFO, or whoever holds the finance seat, says, "We had a strong revenue quarter but margins are getting squeezed by input costs," the number that mattered wasn't the one they led with. Margin, not revenue, is the one to ask about next.
Currency movement and inflation usually matter more here than any other macro condition, since they hit cost and pay directly and can move fast. Interest rates matter too, but further downstream. When any of these come up in a leadership conversation, connect it to something specific instead of letting it pass as background noise. Ask what it actually means for cost, pay, or hiring in this business, right now.
Build this over time by noticing where macro conditions actually show up: a budget conversation, a pricing decision, a line about costs or hiring. If inflation, currency, and interest rates feel like unfamiliar territory, Economics 101 by Alfred Mill is a plain-language walkthrough of exactly this, without the textbook density.
When leadership says, "Costs have gone up everywhere and we need to hold headcount flat," that's a currency and inflation story translating directly into a People decision. That's the connection worth naming out loud.
Ask what the customer is actually experiencing, not what a dashboard says about them. When a complaint or a piece of feedback comes up, work out whether it points to a capacity problem, a training gap, or something else the People team could act on.
Build this over time by getting close to the customer directly: sit in on a sales call, shadow a sales visit, listen to a handful of customer care calls. Hearing how a customer actually talks about what they need teaches you more in an hour than a satisfaction score will.
If customer complaints keep citing slow response times, that's not only a customer service issue. It could be a capacity gap, a training gap, or a retention problem on the frontline team, and each is a different question worth asking.
By the time the plan doesn't land, it looks like a strategy problem. It was a literacy gap the whole time.
Next time someone in a meeting mentions a number, a macro condition, or a customer complaint you don't fully follow, ask one clarifying question in the room instead of nodding and moving on.