I'm good at stats. Why can't I turn a vague ask into one?
You tell yourself you can do the stats but not the framing. Look closer. Every analysis you have ever done well was already framed for you — by a textbook, a boss, a template from last quarter. Someone else did the translating, and you mistook their work for the absence of a problem. Now no one is doing it for you. Someone says 'figure out why churn is up' and waits for a chart. You wait for the question to get sharper on its own. It will not. It is vague because whoever asked it has not decided what they would do differently depending on the answer. Forcing that decision out of them — or out of yourself — is the actual job. With a team, this fails in a familiar way: everyone waits for someone else to speak first, so the vagueness survives the whole meeting. But a team can also force the question faster than one person alone, if someone simply starts talking.
The gap is not your math. It is that you wait for someone to hand you a finished question, and no one will. Name the decision the analysis must serve. Write your guess at the answer first. Ask what evidence would change that guess. That is the translation — do it badly, today, with your team.
What changes unlock by starting
- You stop waiting for a clean question and start building one yourself.
- Your team spends less time analyzing the wrong thing.
- Stakeholders trust you more because you hand questions back sharper than they gave them.
- You can start work the same day instead of stalling on 'what are they really asking?'