Stop Counting Blades of Grass

Someone asks you for a report. You go off, pull the data, build the slides, present the findings. They look at it and say... that's not what I meant. So you go again. Different angle, different numbers, same frustration. A week later, they ask for the same thing in a slightly different way and the whole cycle starts over.

Sound familiar? It should. I've watched this pattern play out in dozens of organisations and I've been guilty of it myself. Years ago, a boss asked me to make a deck on something. I dutifully went off, built a beautiful presentation, came back feeling pretty pleased with myself. Until the question came back... what was this actually for? What were you going to do with it?

Turned out they just wanted to show someone that we were up to some stuff. They didn't need the detail. They needed a story. And the story I'd told wasn't the one they needed to hear.

That was the moment I stopped answering questions and started asking them instead.

The blades of grass problem

Here's an analogy I keep coming back to. Imagine someone asks you how many blades of grass are on the lawn. So you go and count them. Then they ask how thick the blades are. So you measure those too. Then they want to know the height of each blade, the growth rate, the moisture content.

You can spend weeks on this. You can build a brilliant dashboard. You can produce the most comprehensive grass report anyone has ever seen.

But the question they were actually trying to answer was... do we need to mow the lawn or not?

And if you'd known that at the start, the answer would have taken you five minutes.

This is what happens when we respond to requests for information without understanding the intent behind them. We create enormous reporting burdens for ourselves and our teams, we pull people out of actual delivery to produce data that nobody acts on, and we end up in a cycle where the requester keeps asking because they're not getting what they need... but neither of you knows what that is.

Four questions that change everything

Before producing any report, any presentation, any data pack, ask these four things. In this order.

What do they need to know? Not what do they want to see. What do they actually need to know? Because often the person asking doesn't know either. They've been asked by someone else who's been asked by someone else. Find the original question. It's almost always simpler than you think.

What do they need to do with it? Every piece of information should drive an action. If there's no action attached to it, question whether it needs to exist. "Here's how many units are at risk" is data. "Here's how many units are at risk, here's why, and here's the decision you need to make" is useful. The action is what makes it useful.

Why does it matter to them? Not why does it matter to you. To them. Because the way you'd explain your job to yourself is completely different from the way your boss needs to understand it. They don't need the mechanics of your day-to-day. They need to know the impact, whether they should pay attention, and what they should do about it.

What needs to happen next? If you want to deliver X, then Y needs to be true. If you want this target, then these are the parameters. If you want certainty, then here's what that costs. Frame the trade-offs. One slide. Clear choices. Because that provokes the conversation that actually matters.

The credibility shift

Here's the thing that surprised me. When you stop answering every question with everything you know and start framing it around what the audience needs to act on, your credibility goes up, not down. It feels counterintuitive because the instinct when someone's digging into your data is to give them more. Prove you've got it. Show the detail. Defend the numbers.

But the detail is where trust goes to die. Because the more granularity you expose, the more questions people have. Not because the work is wrong, but because they don't have the context to interpret it. They'll find something that looks odd, they'll pull at that thread, and suddenly you're spending four days explaining something that was never the point.

The leaders who command the most credibility in my experience are the ones who push the conversation up, not down. They say, here's what you need to know. Here's what I recommend. Here's the decision in front of you. And if you want to go into the detail, I've got it, but I don't think it's where your time is best spent.

That takes guts. But it works. Every time.

Mow the lawn

So next time someone asks you for a report, a data pack, a presentation, a briefing... pause. Don't go and count blades of grass. Ask them one question first.

What are you going to do with this?

If they can tell you, brilliant. You'll know exactly what to produce and it'll take a fraction of the time. If they can't tell you, that's the conversation that needs to happen before any data gets pulled. Because without it, you're just generating noise. And noise is exhausting for everyone.

The question has to be actionable. The data has to drive a decision. And the decision has to belong to someone.

Everything else is just grass.