WEBVTT 00:00:00.875 --> 00:00:03.840 A useful dashboard helps you decide what to ask next. 00:00:04.088 --> 00:00:09.353 We'll read three parts of this demonstration portfolio: review turnaround, delay 00:00:09.353 --> 00:00:11.228 patterns, and reporting completion. 00:00:11.500 --> 00:00:13.790 Each answers a different management question. 00:00:15.000 --> 00:00:16.815 Begin with review turnaround. 00:00:17.062 --> 00:00:21.102 Read the reporting periods along the chart and look at the direction over time. 00:00:21.350 --> 00:00:23.778 A shorter turnaround may be encouraging. 00:00:24.038 --> 00:00:28.478 Ask whether the scope, workload, and review quality stayed comparable. 00:00:29.680 --> 00:00:31.458 Next, look at the delay causes. 00:00:31.743 --> 00:00:35.320 Design coordination has the largest count in this example. 00:00:35.592 --> 00:00:40.120 That points to a focused question: which projects need coordination support? 00:00:40.368 --> 00:00:45.020 A count helps you investigate; it does not establish the cause of every delay. 00:00:46.240 --> 00:00:49.730 The responsibility chart groups the recorded delay events. 00:00:49.990 --> 00:00:54.392 Use it to locate the underlying records and understand the team's assessment. 00:00:54.652 --> 00:00:59.430 Keep that distinction clear when you discuss responsibility in a management meeting. 00:01:00.678 --> 00:01:03.242 Finally, follow the reporting stages. 00:01:03.515 --> 00:01:09.255 Sixteen of twenty four final reports are issued, shown as sixty seven percent after 00:01:09.255 --> 00:01:09.692 rounding. 00:01:09.977 --> 00:01:13.792 That is report completion, not physical project progress. 00:01:14.065 --> 00:01:16.242 The gap tells you where to ask for follow up. 00:01:17.505 --> 00:01:22.895 For your next meeting, choose one trend, one recurring issue, and one reporting gap. 00:01:23.155 --> 00:01:27.445 Ask what changed, which records support the finding, and who will follow up. 00:01:27.718 --> 00:01:29.970 Those questions make the dashboard useful.