Management information is not a bigger pack
Reporting grows because each request is reasonable. Performance control starts by asking which decision the information is for.

Ask a leadership team whether they have enough information and the honest answer is often both yes and no. The pack is long. The meeting still opens with someone asking for a number that is already on page fourteen. The problem is not a shortage of data. It is that the information was not designed around a decision.
Management information is the smallest set of measures, comparisons and commentary that lets a specific group of people take a specific decision, at a specific frequency. Board information, executive information and team information are different products. Combining them into one pack usually serves none of them well.
Start from the decision, then retire a report
A practical way in is to list the decisions each meeting is allowed to take. For each decision, write the information that would change the answer, the threshold that would force a conversation, and the action that should leave the room. Anything that does not serve a decision is a candidate to stop. Stopping a report is part of the design. If nothing is removed, the new routine will sit on top of the old one.
Systems come after that conversation, not before it. A new dashboard that encodes an unsettled argument about performance will be expensive and ignored. Specify what the routine needs. Then decide whether the current tools can provide it. Often they can, once someone is willing to publish less.
The test of a performance-control routine is behavioural. Do managers arrive having read it? Do variances produce an owner and a next step? Does the board see less, and ask better questions? If the pack is admired and the meeting is unchanged, you have designed a document, not a control.