Back to Posts
Role emerging now: the π—€π˜‚π—²π˜€π˜π—Άπ—Όπ—» π—”π—Ώπ—°π—΅π—Άπ˜π—²π—°π˜

Role emerging now: the π—€π˜‚π—²π˜€π˜π—Άπ—Όπ—» π—”π—Ώπ—°π—΅π—Άπ˜π—²π—°π˜

The board asked for a report ASAP.
There is a job that does not have a title yet. And it may already be the most important one in your organisation.

2006: The Alignment Era
5–6 people. 3–7 days. Monthly cadence, quarterly for the board.
60–80% of analyst time spent on data preparation, not analysis.
The report's value? Getting everyone to agree on the number.

Role that emerged: the Data Analyst, someone whose entire job was bridging raw systems and human decisions.

2012: The Consistency Era
BI tools centralised reporting. Cognos. BusinessObjects.
3–4 people. 1–2 days. Weekly cadence is becoming standard.
Value shifted from alignment to repeatability.

Role that emerged: the BI Developer, someone who built and maintained the reporting layer so analysts could stop rebuilding from scratch.

2018: The Visibility Era
Automated pipelines. Self-service dashboards.
1–2 people. Hours. Daily updates, on demand when needed.
The bottleneck moved from production to interpretation.

Role that emerged: the Analytics Engineer, someone who owned the data models sitting between raw data and business dashboards.

2025: The Agentic Era
The first draft of the report writes itself
AI agents monitor metrics, detect anomalies, generate narratives, and flag decisions continuously, without prompting.
Close to zero people are assembling it.
Cadence? Continuous. The report is always running.

Role emerging now: the π—€π˜‚π—²π˜€π˜π—Άπ—Όπ—» π—”π—Ώπ—°π—΅π—Άπ˜π—²π—°π˜, there is no job posting for this yet. But there should be.

The challenge has moved upstream: not producing insight, but framing the question that produces useful insight.

This is the skill redesign hiding in plain sight.
Old model: data extractor β†’ analyst β†’ reconciler β†’ slide builder
New model: metric owner β†’ decision owner β†’ question architect

Each era did not just change the tool.
It retired one role and created another.
The mistake organisations keep making is adopting the new tool without redesigning the role around it.

Fewer people are assembling information.
The bottleneck moves from data to decision-making capacity.

So when the board asks for a report ASAP,
The real question worth asking is:
Do we have the people to turn real-time data into real-time decisions?

Acceleration in reporting only helps when understanding accelerates too. The rare skill now is framing the question before the answer exists.
The Question Architect. No job posting exists for it yet. But it will.