Reporting
Intelligence.

Reporting is almost always on the list.

Whenever I ask project leaders where AI could help them, reporting is one of the first topics they raise.

There is a good reason. Weekly updates, monthly management presentations, steering committee meetings, financial reviews and function-specific briefings all demand preparation. Teams repeatedly collect information, check its accuracy, structure the message and translate it into a presentation.

And the report prepared for one meeting rarely transfers unchanged to the next. The project leader can spend a considerable amount of time explaining the same project to different groups.

The first question is usually: “Could AI prepare this report or presentation for us?” That is a useful starting point. In Building NEXA, we want to explore another layer: could NEXA take account of the audience, the questions the report must answer and the decision we are preparing for?

Could NEXA help us prepare for what needs to be understood—and what needs to be decided?

The facts stay consistent. The emphasis changes.

Imagine Project Orion entering its next reporting cycle. Tomorrow, the project leader meets Sales. The following day, it is Manufacturing and Engineering. At the end of the week, the steering committee meets.

The project and its current status are the same. What each audience needs to understand is different. Sales needs the implications for customers and launch commitments. Operations needs readiness and capacity information. Finance challenges the budget and expected business outcome. The steering committee considers the cross-functional consequences and the decision required.

This does not mean telling different audiences different versions of the truth. The evidence must remain consistent. The level of detail, emphasis and decision question should fit the audience.

A supplier delay may affect customer commitments, the sequence of production activities and additional cost at the same time. Good reporting makes those connections visible and explains why they matter to the people in the room.

A clear report connects the evidence to the decision.

When evaluating project leadership skills, we pay attention to communication: preparing a management summary, simplifying a complex issue, delivering an elevator pitch and building a clear story.

A technically complete report can still leave its audience asking: “What does this mean for the business?” “What exactly do you need from us?” “Why now?” “What happens if we wait?”

Storytelling should connect the current situation, its consequences, the available options and the decision requested. It should never make the situation look more favourable than the evidence supports.

For Orion, a useful reporting brief would identify the participants, their responsibilities, the meeting objective and the open questions from the previous discussion. Is the purpose to inform, seek guidance or obtain approval? Which decisions are within this group's authority?

Combined with verified project data, that context could help NEXA prepare a more relevant first draft. The project leader would review the accuracy, emphasis and suitability of the information before sharing it.

What if we could rehearse the steering committee?

Now imagine Orion needs additional budget for a critical response. The presentation describes the situation, recommends an action and states the funding request.

But how well prepared is the team for the questions that follow?

Finance may ask what the additional investment delivers and what happens without approval. Operations may question who can supply the resources and how other projects will be affected. Sales may challenge the assumptions behind a customer commitment. Engineering or Quality may ask how required validation will be completed.

Some answers may exist but be difficult to find in the presentation. Others may require analysis the team has not yet completed. Could NEXA expose those gaps before the actual meeting?

A virtual committee, grounded in the project.

We can think of the longer-term idea as a “steering committee digital twin”. A more concrete starting point is a simulation of the functions' responsibilities, requirements and decision criteria.

We should not assume that this model knows what an individual executive will think or how they will vote. Instead, it represents perspectives that challenge the financial case, operational feasibility, customer implications and technical risks.

Those perspectives should be grounded in Orion's actual governance, decision rights, resource constraints and agreed requirements. Generic role descriptions alone would not provide enough context.

NEXA could review a decision pack through these perspectives and surface weaknesses: an unclear decision request, alternatives that have not been compared, an unspecified resource deadline, unsupported claims, missing residual risks or an unexplored cost of delay.

Useful rehearsal needs useful context.

Current, traceable project information

Status data, risks, costs, dependencies, open decisions and resource commitments need a clear source and date. Conflicting or outdated inputs should be flagged before they become confident statements in a report.

The reporting and decision context

NEXA would need the audience, meeting purpose, decision rights and functional requirements. The same budget request may need different preparation for a working-level review and an approval meeting.

Relevant organisational memory

Previous minutes, decision records and feedback can show which questions have been raised before. They should only be used within the applicable access permissions. Past acceptance of an argument does not guarantee that it is sufficient today.

Changes in priorities and missing information must remain visible. Outputs should distinguish verified information, assumptions and possible questions. When an answer is missing, NEXA should identify the gap rather than invent a response.

The rehearsal succeeds when it finds a weakness.

A virtual committee saying “approved” is not a meaningful measure of success. The value lies in what the team discovers before the meeting: an unsupported claim, a missing alternative, an ambiguous resource request or an unanswered risk question.

The project leader and experts assess that feedback, complete the necessary analysis and improve the communication. The real sponsor and steering committee retain their decision authority.

Better preparation will not make every proposal acceptable. It may reveal that the recommendation should change—or that the request should be rejected. That is a valuable outcome too.

Could better preparation shorten the decision loop?

We want to test whether this approach reduces total preparation effort. Producing the first draft faster is only part of the picture; the time spent checking and correcting it also matters.

The second question concerns decision cycles. Could a clearer request and a more complete evidence base reduce the need to return to another meeting simply to supply missing information?

Not every delay is caused by reporting. Genuine resource conflicts, uncertainty and strategic disagreements do not disappear with a stronger presentation. The opportunity is to reduce avoidable repetition caused by incomplete preparation or unclear communication.

Suggested evaluation measures for a future pilot. No performance results are claimed.

Arrive with a report—and a stronger understanding.

Imagine Orion's team walking into the meeting with a current report, a clear decision request, assessed alternatives and well-prepared answers to critical questions.

That is the working approach we are exploring through Reporting Intelligence: connect project information with the audience's needs and strengthen the team's preparation for a real decision conversation.

We started by asking whether AI could prepare the presentation. We are now asking:

“Could NEXA help us prepare for what needs to be understood—and what needs to be decided?”

Which question do you most often wish your team had prepared for before a steering committee meeting?