· 1 min read
From Insight Strategist to Decision Loop
Why the analytics team I established at JCorp was named "Insight Strategist" rather than "Insight Analyst" — and what naming a function decides about how it operates.
- data-architecture
- leadership
- digital-transformation
When we set up the analytics function at JCorp, the choice of name was load-bearing. Calling the team "Insight Analysts" would have told them that their job ended at the insight — a chart, a memo, a presentation. Calling them "Insight Strategists" told them that the chart was an intermediate artefact and the actual deliverable was a decision the business hadn't taken yet.
The renaming did most of the cultural work for us. Within two quarters the team had reorganised its own meeting cadence around decision owners rather than data domains. Within four, the format of an "insight readout" had shifted from a slide deck to a one-page recommendation with a named decision-maker and a value clock. The data work didn't change — the same SQL, the same dashboards, the same statistical literacy. The orientation changed.
The lesson, if there is one, is that the gap between data-driven and value-driven is rarely a tooling gap. It is an orientation gap, and orientation is mostly set by what you call people. We didn't promote the analysts and we didn't change the org chart. We just told them the destination was downstream of where they had been delivering, and they walked there.