You can't miss the almost constant conversation about AI and analytics in project controls, and its easy to get lost in fancy dashboards with fifty metrics.
But when I talk to teams, the real discussion usually comes down to a a handful of numbers people actually trust and look at. Building dashboards should focus on answering clear and concise questions. Just because AI helps build dashboards faster, it shouldn't be a race to see how many numbers and charts you can put on a screen.
Curious how others approach building out their key reports and dashboards:
- Do you start by seeking out the questions that actually need answering?
- Do you often just start with what data is available?
- What is an example of a metric that was dropped because you discovered it didnt really answer anything?