Every New Board Question Takes My Analysts a Week – Why, and What Fixes It

By the team at Human Ready · Updated July 2026

When a board or CEO question takes your analysts a week to answer even though the data exists, the cause is almost never the analysts – it's the pipeline the question has to travel: request, queue, extract, build. Each new question re-enters that pipeline from the start, because dashboards and standard reports only cover questions someone anticipated. This page breaks down why the cycle exists, what a week of latency actually costs, and a practical framework for shortening it.

Why does a new board question take a week when the data exists?

It takes a week because a new question – one no existing report answers – has to be answered by people, and people work in a queue. In Human Ready's conversations with finance leaders across European mid-market and enterprise companies, this exact pattern is among the most consistently repeated things buyers say:

A chief procurement officer at a large enterprise, verbatim: "Cada pergunta nova demora uma semana" – every new question takes a week. This at a company with a dedicated dashboards team, which he described as becoming "a monster": more views, more maintenance, and still a week per new question.
A finance leader at a global manufacturing group described the full anatomy: a non-standard question means IT has to extract the data first, and then an analyst works about a week before the question is answerable. Two queues, in series.
The managing director of a mid-market manufacturer told us that in every monthly board meeting there is always one question – "sempre aquela pergunta" – that he cannot answer in real time. It goes on a list, and the answer arrives days later, after the moment that needed it.

These three examples have something in common: nobody is missing data. The warehouse is populated, the reports run, the team is competent. The week is structural, not personal.

What are the four stages of the week?

The week is the sum of four stages – request, queue, extract, build – and most of it is waiting, not working:

Stage	What happens	Why it's slow
Request	The board question becomes a ticket or email to finance/BI	The question is compressed and context is lost; clarification loops begin
Queue	The request waits behind every other request	Analyst and IT capacity is the scarcest resource in the building
Extract	IT pulls data the standard reports don't expose	Data access is gated; the analyst can't self-serve below the dashboard layer
Build	An analyst assembles data, model, and slides	Manual work, single-threaded, redone from near-zero for every new question

Survey data confirms how much of finance's capacity this pipeline eats. The 2024 FP&A Trends Survey found only 35% of FP&A professionals' time goes to high-value work like generating insights – the rest disappears into data collection and validation. In the 2025 AFP FP&A Benchmarking Survey, 60% of practitioners named lack of accessibility to data as a barrier – with more than half of teams operating at least eight categories of reporting tools that don't merge cleanly. Eight tools, and still a week: the tooling multiplied, the latency didn't move.

What does a week of latency cost?

A week of latency costs the decision window, which is worth more than the analyst hours inside it. McKinsey's research on decision-making found organisations that decide quickly are twice as likely to report high-quality decisions as slow deciders – speed and quality are correlated, not traded off. And executives already spend nearly 40% of their time on decisions, most of it self-reported as poorly used; a week of "we'll come back to you on that" makes every one of those decision hours less effective.

There's also a subtler cost: the questions that stop being asked. When every new question costs a week of analyst time, executives ration their curiosity. The second and third follow-up questions – the ones that actually locate the problem – never get asked, because nobody wants to burn another week. Latency doesn't just slow answers; it silently narrows the analysis.

How do I shorten the question-to-answer cycle? (A practical framework)

Shorten the cycle by triaging questions into three classes and fixing the class that actually causes the week. Most teams treat all questions the same way; the leverage is in separating them:

Recurring questions (same question, every period). These belong in dashboards and standard reports. If a recurring question is still answered manually, that's a reporting-hygiene fix – automate it once.
Predictable variants (same question shape, different slice: "same analysis, but for Region X / product Y / last quarter"). These belong in parameterised reports or self-service views. If analysts rebuild these from scratch, invest in templates before anything else.
Genuinely new questions (the board's "what happens if...", "why did...", "which of our..." – the ones that were never thought of before). This class causes the week, and no amount of dashboard-building fixes it, because by definition the question didn't exist when the dashboard was designed. This class needs a different capability: a way to ask new questions of governed data directly, in plain language, without the extract-and-build cycle.

Then measure one number: question-to-answer latency – the elapsed time from a class-3 question being asked to a decision-ready answer. Most finance teams measure close time and forecast cycle time but have never measured this, which is exactly why the week survives. (As one CFO in our conversations put it: "We don't even notice the time we lose." The full pattern – why this pain goes unregistered – is in the hub essay: why every new finance question takes a week.)

One warning for class 3: speed without traceability fails at the board. An answer produced in minutes that nobody can verify will be re-checked by an analyst anyway – reintroducing the week through the back door. Any tool answering new questions for a board audience must show how it got the number, line by line, back to source data. We cover what that requires in how AI analytics can show exactly how it got the number.

What role does Human Ready Advisor play?

Human Ready Advisor is built for class 3: it sits above your existing data stack (warehouse, Power BI, ERP – nothing gets replaced) and answers genuinely new finance questions in plain language, with every figure traceable to how it was produced. The board asks; you ask Advisor; the answer – with its workings – arrives inside the meeting, not the week after. If "every new question takes a week" sounds like your team, that's the specific gap Human Ready Advisor exists to close – humanready.io.

Related reading in this series:

Buyer quotes come from Human Ready's conversations with finance leaders at European mid-market and enterprise companies, anonymised to role and company profile. Portuguese quotes are translated faithfully.