The right level of granularity depends entirely on the audience and the decision being made -- there's no fixed rule that more resolution is always better. Test yourself on three fresh scenarios below and judge whether each one needs more granularity, less, or is calibrated correctly as-is.
Why this is a judgment call, not a rule
The aggregate-to-granular scale is continuous, not a binary switch, and the correct point on that scale shifts depending on who's reading and what they need to decide. These three scenarios are new -- none reuses wording or setup from this batch's other tone articles (the vague-request fix, the too-granular redirect, or the executive-synthesis piece) -- so you can practice the judgment call itself rather than recognizing a repeated example.
Test yourself: three scenarios
Scenario 1: A junior analyst sends the VP of Sales a 40-tab spreadsheet with every individual deal broken out by rep, week, and product line, with no summary tab.
Verdict: too granular for this audience -- a VP needs the top-line trend and the two or three deals that matter, not the full transaction log.
Scenario 2: A product manager tells engineering "the onboarding flow needs to be smoother" with no further detail, and engineering has to guess which of twelve steps is the actual problem.
Verdict: not granular enough -- the PM needs to name which step, which user segment, and what "smoother" should mean concretely.
Scenario 3: A finance analyst gives the budget committee a one-page summary with three line items (headcount, tooling, marketing) and a one-sentence explanation for the one item that's over budget.
Verdict: granular enough -- it names the specific driver without dumping every sub-line-item on a committee that only needs to approve or flag the total.
Want to learn "Granular" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →"Correctly not-granular: a company-wide OKR update that states the single headline number and defers the twelve-team breakdown to a linked doc for anyone who wants it."
"Correctly granular: a support-team retro that names the exact three ticket categories causing the backlog, rather than a vague 'we're behind on tickets.'"
"Incorrectly too granular: a one-on-one status update that walks through every commit from the week instead of the two blockers that actually need the manager's help."
The mistake to avoid
The mistake this quiz targets is applying one fixed rule ("more granular is always better" or "keep everything high-level") instead of judging each situation against who's reading it and what they need to decide.
The two questions that decide every verdict
Notice that all three scenarios above resolve the same way: by asking who's reading this, and what decision are they actually making with it. A VP approving budget doesn't need every line item; an engineer fixing a specific step needs exactly that specificity; a committee voting yes or no on a total doesn't need the sub-line detail behind it. The content itself isn't inherently too granular or not granular enough -- its fit depends entirely on those two questions, asked freshly each time.
Why fresh scenarios matter for this skill specifically
This is a skill that resists being learned from a single memorized example, because the "right" verdict for any one scenario is only right for that audience and that decision -- change either one, and the same level of detail could flip from correct to wrong. Practicing the judgment call itself, on scenarios you haven't seen the answer to yet, builds the actual transferable skill in a way that reading a single worked example never quite does.
Practice scenarios
Practice using granular in situations like:
- judging whether a specific scenario needs more granularity, less, or is already calibrated
- naming who the audience is and what decision they actually need to make
- resisting the assumption that more resolution is always the better choice
Useful practice phrases:
- "This is too granular for a VP audience -- they need the top-line trend."
- "This isn't granular enough -- name which step and which segment."
- "This is granular enough for a committee that only needs to approve the total."
Too granular, not granular enough, or just right -- the audience and the decision decide, not a fixed rule.
Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.