Content Comparison

Section 1: General Layout / Visualization Notes

Category	Current State	Recommended Changes + Example	Can it be addressed? (Y / N; VR or Ona?)
Layout	Filter function: Placement of filter function makes it appear as though it only applies to the coverage indicator	Place Filter function on top of page: Place filter function at the top of the page (below page title) to convey that it applies to the entire dashboard. Also pin the filter / freeze pane if possible, so it is	Y - Ona
Layout	Unpredictable Layout: Layout is currently not optimized for "Z-direction" user reading	Make layout predictable: Start with summary table, point in time indicator graphic and then historical / disaggregated graph for ALL indicators. This helps adopt a "top down" approach for displaying the visuals. Example: Example Mock Up – Utilization Indicators	Y - Ona
Layout / Storyboard	PAV Provincial Dashboard Flow – Order in which the indicators appear – is it optimized to what the end user wants to see?	PAV Provincial Dashboard Flow: Please confirm whether the storyboarding of the dashboard makes sense. Is this the order that the end user wants to see the information in? If not, how would you re-order the charts? Please see below for specifics	Y –VR to provide content; Ona to execute
Visualization	Disaggregated charts with no "key takeaway" table: makes it difficult to glean any meaningful insights from noisy charts	Include a summary table for each indicator group: Above the left and right charts for each indicator group, include summary tables with min/max or other notable summaries. Please see below for specifics	Y –VR to provide summary table ideas; Ona to execute;
Visualization	Color use is not strategic: Different colors used for the same antigens, hard to visually gauge patterns	Use same colors on all antigens: Use the same colors for each antigen on every indicator's graph/chart. E.g. in all charts corresponding to DPT, DPT will be in dark blue	Y - ??
Visualization	No anchor / benchmark on visualizations: It is hard to assess from the charts if performance is "good" or "bad"	Add a benchmark / anchoring data point to charts: For coverage line chart, add a dotted line for "Target Coverage Rate"; For stock-out line chart, add a dotted line for "National Stock-out Average" etc. Please see below for specifics Differentiate CCV on Coverage Charts: Since CCV is not an antigen, can it be depicted with dotted lines in the charts it shows up in?	Y –VR to provide summary table ideas; Ona to execute;
Visualization	District charts in "national view" of dashboard are overwhelming: Seeing ALL the districts on one chart is overwhelming	Grouping districts belong to a province: Is there a way to group the district level charts e.g. leave space between bars corresponding to a different provinces or add labels below the districts to communicate which province they belong to?	Not sure – please comment
Content	Lack of data due to lag in uploads: Lots of blank space due to lack of data.	Add the period view: Fix the period view of the dashboard to address this. Clay to play around with options discussed on 16^th October call. For charts saying "last year", change to "last 12 months": Timoteo – Please confirm.	Y - Ona
Content	Table placement and structure: When in National mode, the tables can get very unwieldly. The way tables are currently structured, you see provinces appear multiple times. This can be confusing	Remove table from main view and add a link to tables below visualizations: Adding a link below the visualizations for each of the indicators (as shown in our layout mock-up) will help the user deep dive to the tables if needed. Suggestions for deep dive tables: Re-organize table columns: Have the first column be year, then month, then province, and then all the vaccines. This ensures that the user can view the performance of a province / geography within the context of a period. This makes it easier to compare the situation Add table headers for vaccine groups: For vaccines with multiple schedules / multiple types available, have a header to convey that they are related. E.g. Polio 1, Polio 2, Polio 3, should have a header called "Polio", which helps group them.	Y - Ona
Content	Language of indicator titles: Currently some in Portuguese, some English.	Standardize language of indicator titles: Change the ones in English to Portuguese: Examples: Mobile Brigades Execution Rate, Community Mobilization Execution Rate etc. Timoteo – Please provide accurate translations	Y –VR to provide content; Ona to execute
Content	Title Syntax: Ensure that title syntax is standardized across all indicators	Standardize Syntax titles: E.g. Indicator - Geographic level of Disaggregation – Period Timoteo – Please provide desired syntax / format for all titles	Y –VR to provide content; Ona to execute
Content	Dashboard Caption: No caption currently on use / context of dashboard	Add Dashboard Caption: Add a caption to dashboard title to reinforce use case. Example: Dashboard Title Context on Dashboard, intended use and intended user	Y –VR to provide content; Ona to execute
Content	Inconsistent use of descriptions for indicators: Not all indicators have a description to go with them E.g. Community Mobilization Indicator	Add descriptions for all indicators: add descriptions for ALL groups of indicators – e.g. mobile brigades as well. Timoteo – Please provide desired content for all titles Example: Indicator Name Context on Indicator, rationale for inclusion, key things that user should look out for.	Y –VR to provide content; Ona to execute

Section 2: Indicator-specific Visualization Notes

High level notes here, more detailed notes can be found in the file "PAV Dashboard_Indicator List_10-24-2018_vSent" on Dropbox.

Indicator Category	Indicator + Recommended Visualization + Notes + Mock Up	Can it be addressed? (Y / N; VR or Ona?)
COVERAGE – Existing Indicator	Visualization: 1. Cobertura Vacinal - Último Ano (Vaccine Coverage - Last Year): Line Graph 2. Cobertura de todas as vacinas - último mês estatístico (Vaccine Coverage - All vaccines - last statistical month): Bar Chart Notes: Layout: Put the Bar chart on the left and then the detailed Line Graph on the right, in keeping with layout notes in Section 1.	Y – Ona to execute;
COVERAGE - Summary Indicators	Summary Indicator + Visualization: 1. 3 Antigens with lowest % of coverage (last year): Summary Table w/ Conditional Formatting (traffic lights) 2. Months with lowest % of coverage (last year): Summary Table w/ Conditional Formatting (traffic lights) Mock Up: Mock Up Summary Indicator 1.: Mock Up Summary Indicator 2.:	Y – Ona to execute;
VACCINE UTILIZATION: Summary Indicators	Summary Indicator + Visualization: 1a. Districts with highest % of utilization (last year): Summary Table 1b. Districts with lowest % of utilization (last year): Summary Table 2. Months with highest % of utilization (last year): Summary Table Mock Up: Mock Up: Summary Indicator 1a and 1b. Mock up: Summary Indicator 2.	Y – Ona to execute;
VACCINE STOCK-OUT: New Indicator	Indicator + Visualization: 1. Vaccine Stock-out - Antigen-specific (last statistical month): Bar Chart 2. Vaccine Stock-out - Antigen-specific (last year): Line Chart Mock up:
VACCINE STOCK-OUT: Summary Indicator	Summary Indicator + Visualization: 1. Antigen with highest % of stock-out (last month): Summary Table w/ Conditional Formatting 2. Months with highest % of stock-out (last year - average across vaccines): Summary Table w/ Conditional Formatting Notes: Conditional Formatting Criteria + Traffic Lights Color-Amber: Low -Orange: Medium -Red: High Mock Up: Mock Up: Summary Indicator 1.: Mock Up: Summary Indicator 2.:	Y – Ona to execute;
VACCINE BREAKAGE: Existing Indicator	Visualization: 1. Vaccine Break by District - DPT, Measles, BCG (for last statistical month): Bar Chart 2. Vaccine Break by District - Antigen-specific (for last 12 months): Bar Chart  DPT1 to DPT3  Sarampo1 to Sarampo2  BCG to Sarampo 1 Notes: -Visualization change: Please change the visualization for indicator 2. above - Vaccine Break by District - Antigen-specific (for last 12 months) to a bar chart (it is currently a line chart). -Summary indicator: What summary indicator is most suitable for this? Timoteo – Please provide your thoughts on this	Y – Ona to execute;
MOBILE BRIGADES: Existing Indicator, New Viz	Indicator + Visualization: 1. % Execution Rate of Mobile Brigades: Table with conditional formatting (traffic lights) Notes: Conditional Formatting Criteria + Traffic Lights Color-More than planned = Greater than 100% Execution Rate = Green -As planned = 90% - 100% Execution Rate = Yellow -Less than planned = Less than 90% Execution Rate = Red Mock-Up:	Y – Ona to execute; VR to provide calculation support
MOBILE BRIGADES: Summary Indicator	Summary Indicator + Visualization: 1. Distribution of Districts based on Mobile Brigade Execution Rate: Summary Table with Conditional Formatting (traffic lights) Notes: Conditional Formatting Criteria + Traffic Lights Color -More than planned = Greater than 100% Execution Rate = Green -As planned = 90% - 100% Execution Rate = Yellow -Less than planned = Less than 90% Execution Rate = Red Mock Up:	Y – Ona to execute; VR to provide calculation support
SOCIAL MOBILIZATION: Existing Indicator, New Viz	Indicator + Visualization: 1. % Execution Rate of Community mobilization through Radio: Table with Conditional Formatting 2. % Execution Rate of Community mobilization through Lecture: Table with conditional formatting Notes: Conditional Formatting Criteria + Traffic Lights Color-More than planned = Greater than 100% Execution Rate = Green -As planned = 90% - 100% Execution Rate = Yellow -Less than planned = Less than 90% Execution Rate = Red Mock-Up:	Y – Ona to execute; VR to provide calculation support
SOCIAL MOBILIZATION: Summary Indicator	Summary Indicator + Visualization: 1. Distribution of Districts based on Community Mobilization through Radio Execution Rate (%): Summary Table with Conditional Formatting 2. Distribution of Districts based on Community Mobilization through Lecture Execution Rate (%): Summary Table with Conditional Formatting Notes: Conditional Formatting Criteria + Traffic Lights Color-More than planned = Greater than 100% Execution Rate = Green -As planned = 90% - 100% Execution Rate = Yellow -Less than planned = Less than 90% Execution Rate = Red Mock Up: Summary Indicator 1: Mock Up: Summary Indicator 2:	Y – Ona to execute; VR to provide calculation support

Section 3: TBD - Indicator Visualizations To be determined?

Please note: These are indicators that we current don't have data for, so it is unclear what the visualizations will look like. Timoteo – your input here would be helpful.

Indicator Category	Indicator + Recommended Visualization + Notes + Mock Up	Can it be addressed? (Y / N; VR or Ona?)	Addressed?(✘ or ✓)
FINANCIAL EXECUTION OF HSS FUNDS	Visualization: 1. % of Financial execution of HSS Founds at National Level: What type of visualization? 2. % of Financial execution of HSS Founds by province: What type of visualization? Notes:	?
RED / REC	Visualization: 1. Index of realization of the expansion of the RED, REC for new districts (% of realized VS planned): What type of visualization? Notes:	?

Appendix A: Research on Dashboard Best Practices

Category	Best Practice
Purpose	Principle P1: Clarify purpose. Is it a) an Analytics dashboard? B) Operational dashboard? Rationale:. Operational dashboards are used to track operational activities. Main goals of the operational dashboard are to present data deviations to the user quickly and clearly, show current resources, their status. It's a digital control room designed to help users be quick, proactive, and efficient, and respond to time-sensitive tasks. Strategic dashboards are higher level operational dashboards which provide high level data needed to make quick decisions Analytics dashboards are at the lowest level of granularity, and allow user to detect patterns. Action based on an analytics dashboard is not time sensitive.
Layout	Principle L1: Organize a dashboard such that you start with the important information on the top left, and move in a "Z" pattern Rationale: Important information should be on the top left hand corner because it is the first thing that the user "reads" in certain language conventions (in English, Portuguese etc). Examples:
	Principle L2: Increase white space between elements Rationale: Negative space helps focus on the graphic element being displayed Examples:
	Principle L3 Group related pieces of information. Grouping horizontally shows going from one topic to another, grouping vertically shows disaggregation of the same topic. Rationale: Having related piece of information in the same line (or unified by a title) will help the user understand the "story" being told.
Content	Principle C1: Consider using Tableau's "Story Points" to guide the user through the narrative or sequence of events you want to tell Rationale: Instead of having multiple tabs that the user has to navigate, we could position the tabs as different "chapters" in the Narrative, and have a succinct captions for the Story Example: *
	Principle C2: Do not rely on too many interactions for user to get the information they need. Rationale: Understanding usage behavior in terms of time spent interacting with data helps clarify how much visual real estate we have to pack information. Interactions help surface secondary information. Fully relying on them as the main way to work with the dashboard is a big mistake
	Principle C3: Show summaries or condensed views. Rationale: Depending on the user being targeted, they generally watch a summary of the situation which provides a quick "takeaway" to inform decision-making.
	Principle: Include a BAN ("Big A Number") for each visual. Rationale: Don't bury the important fact. The number anchors the user's eye, while the chart (with historical data) provides context. Example: Sub-Principle: Compare your BAN against your target Rationale: This is a way to quickly state the "current state" and compare it to the "ideal state" Example:** *