Queries define what matters.
Widgets define how it is understood.
Once governance-ready queries are created, the next step is
converting them into visual widgets that leadership can interpret immediately.
The objective is not to create more charts.
The objective is to create clear, decision-ready views.
Step-by-Step Guide
Step 1: Create a Widget from an Existing Query
Every widget must start with a structured query.
To Create a Widget:
Navigate
to Dashboards
Open
the desired dashboard
Click
Add Widget
Select
the relevant Query
Always select a pre-defined, governed query.
This ensures:
The
widget reflects approved governance logic
The
same query can be reused across multiple dashboards
Data
consistency is maintained across weekly reviews
Widgets do not redefine logic.
They visualize it.
Step 2: Choose the Appropriate Widget Type
Selecting the correct widget type is critical.
The format you choose directly affects how leadership interprets the data.
Different governance questions require different visual
formats.
Use a KPI or Statistic Widget when:
You
need to show overall status
You
want to highlight a single critical number
Leadership
needs a quick health indicator
Example: Total overdue items or overall completion
percentage.
Use a Trend or Line Chart when:
You
need to show movement over time
You
want to highlight improvement or slippage
Leadership
needs to see direction, not just a snapshot
Example: Week-over-week change in delayed activities.
Use a Distribution Chart (Bar or Pie) when:
You
need to show concentration
You
want to compare categories
Leadership
needs to understand where impact is accumulating
Example: Risks grouped by impact level or workstream.
Use a Table when:
Detailed
validation is required
The
PMO needs to drill deeper
Specific
items must be reviewed
Tables should support discussions, not dominate executive
dashboards.
Guiding Principle
Choose the widget type based on the question being answered.
If leadership needs a quick decision view, use summary
visuals.
If validation is required, use structured detail.
Using the wrong widget creates confusion and slows down
discussions.
Step 3: Configure the Widget for Clarity
Once the widget type is selected, configure it for immediate
clarity.
Best Configuration Practices
Use
a clear, question-driven title
Example: “Open Plan Items Past Expected Date”
Select
meaningful grouping or aggregation
Example: Group by Workstream, Owner, or Priority
Control
what data is visible by default
Avoid overwhelming leadership with excessive detail
A well-configured widget should be understandable within
seconds.
If a widget requires explanation during the meeting, it
needs redesign.

Step 4: Align Widgets to Steering Committee Needs
Steering dashboards are not operational dashboards.
They are decision dashboards.
Steering Committee Focus Areas
What
is on track
What
is at risk
What
requires a decision
Steering Dashboard Principles
Highlight
exceptions, not everything
Surface
trends, not raw lists
Emphasize
impact, not activity
Widgets should drive structured discussion, not data
validation.
Practical Example: Weekly Health Review Dashboard
A structured weekly dashboard may include:
1. Summary Widget
Displays overall delivery health or progress percentage.
2. Trend Widget
Shows slippage or improvement over time.
3. Distribution Widget
Highlights concentration of risks or overdue items.
4. Drill-Down Table
Supports quick validation if deeper insight is required.
Each widget must answer one governance question.
If a widget does not answer a question, it should not exist.
Important Practice: Maintain Execution Data
Dashboards reflect live project data.
If:
The widgets will misrepresent reality.
Real-time dashboards require real-time execution discipline.
Data hygiene is a shared responsibility.
Key Takeaway
Queries define what matters.
Widgets define how it is understood.
When structured correctly:
A well-designed dashboard reduces reporting noise and
increases governance clarity.