Your Power BI App Has Twelve Pages. The Room Uses Two

The app looks complete. It has twelve pages, every function got a tab, and every “nice to have” survived review.

The meeting opens two of them, every week. The rest are a navigation tax.

Pages are not a portfolio. They are a meeting surface

Report sprawl across workspaces is a different problem. That estate tax is dashboard sprawl: too many files and too few owners. This post is narrower. It is about one app, one audience, and too many pages inside the thing leadership already agreed to use.

Someone asked for a deep dive. Someone else asked for a regional cut. A contractor left three pages “for later.” The launch deck celebrated breadth, and nobody asked which pages the recurring review actually opens under time pressure.

Usage will tell you. So will the EA who builds the pack, and so will the silence while a leader hunts for the right tab and the room waits.

Extra pages feel like coverage. In a live review they feel like delay. Every unused page is another place to click, another place to misread, and another place a twin measure can hide.

This is not an argument against detail. Detail belongs behind the decision page, in a drill-through, a steward diagnostic, or a connected workbook on the same model. It does not belong as an equal peer in the nav for a thirty-minute operating review.

The costs of a twelve-page app the room ignores

1. The meeting starts with wayfinding. Leaders do not need a tour. They need the exception view. When the official app has twelve doors, the first minutes go to “which page are we on,” and that is tax, not insight.

2. Unused pages still refresh and still break. A page with zero opens can still depend on a measure, a relationship, or a visual that fails after a source change. Support time follows the estate, not the usage log.

3. Twins hide in the long nav. Page three and page nine can both show margin with slightly different filters and timing. The room trusts the app brand and then argues inside it: same company, same file, two truths. See why reports show different numbers.

4. Authors keep adding instead of retiring. A new request becomes a new page because adding feels safer than redesigning. The nav grows, and the two pages that matter stay crowded with leftover slicers from last year’s agenda.

5. Adoption looks fine while attention is thin. Opens on the app home can hide the fact that nine pages never load. Leadership thinks the program is broad while the operating review still runs on two screens and a spoken aside.

6. Training becomes a map of clutter. New managers learn twelve destinations and remember two. The rest become folklore, “we don’t use that one,” with no owner willing to delete it.

7. Mobile and projected views punish breadth. A wall screen or a laptop in a plant conference room does not forgive a dense nav. The room defaults to the pages that fit the agenda and ignores the rest forever.

8. Retirement never starts because everything is “in the app.” People defend unused pages as part of the product. How to retire a dashboard applies inside an app too. A page without an owner and a meeting is a candidate for retirement, not a feature.

How to fix it: cut to the pages the meeting owns

1. Name the recurring meeting before you defend the nav. Weekly ops, monthly commercial, close review. Write down the decisions that meeting must make, because pages exist to serve them. Everything else is a candidate to hide, merge, or retire.

2. Pull page-level usage for ninety days. Rank pages by opens from the roles in the room, and ignore authors testing their own work. The two or three pages the audience actually loads are your core. Treat the rest as provisional.

3. Interview the people who run the agenda. Ask which page opens first, which page settles arguments, and which page they never touch, and write the answers down. Usage plus agenda beats taste.

4. Design one decision page per meeting type. It shows exceptions, owners, as-of timing, and the next approved cut, and it is the front door. Deep detail moves to drill-through or a clearly labeled steward view, not to peer tabs in the executive nav.

5. Merge twins instead of labeling them. If two pages answer the same decision with different filters, collapse them. One page with clear slicers beats two near-copies that drift. Shared measures live in the semantic model, not in duplicate canvases.

6. Hide or archive pages that lack an owner. Every surviving page needs a business owner and a meeting that uses it. No owner means no place in the official nav. Sandbox pages can live elsewhere, but not beside the certified view.

7. Rewrite the agenda around the two pages. Put the page names in the calendar invite and open them in the room. Stop walking the full app like a museum. Breadth that never makes it into the minutes is decoration.

8. Set a quarterly page review. Use the same ritual as report retirement: owner, replacement, date. New requests must say which page they change or replace. Stop commissioning a dashboard per question applies to pages too. Intake without an exit is how you got to twelve.

9. Measure success by meeting time, not page count. Did wayfinding shrink? Did follow-ups stay on the trusted pages? Did anyone miss a retired tab? If silence follows a hide, you were paying tax on a ghost.

What a two-page app looks like in practice

The operating review opens the same exception page every week. The commercial review opens a second page built for its cadence. Both sit on one governed model, and drill-through handles the “which customers” and “which lines” questions without a peer tab for every cut.

Analysts still build measures, diagnostics, and clearly labeled sandbox pages. Those surfaces do not compete with the meeting’s front doors.

Leaders stop hunting and the room starts on the decision. Commentary and judgment still matter, but navigation no longer eats the first five minutes.

Nobody opens the dashboard sometimes describes an empty estate. Sometimes it describes a full app with nine pages nobody was meant to open in the first place.

Executive takeaway

Twelve pages is not coverage. It is a bet that leadership will browse, and mid-market reviews do not browse. They open what the agenda needs and leave.

Cut to the pages the room uses, move detail behind them, and retire the rest on a date. Fund the model and the decision path, not an ever-growing nav.

Want to know which Power BI pages your meetings actually open? Book a session with Alluvium. We will map one app, its page-level usage, and the nav that should shrink. To check the model underneath, request a free Model Health check.