The true essence of technological advances comes with our understanding of the surroundings, getting better with the aid of tools that never existed before. As analytics continues to evolve at a blistering pace, it brings with it the ability to take decisions that affects the lives of millions around us. Out of seeming nothingness we get concrete patterns that could only have been imagined few decades back.
As interesting scenarios continue to emerge in a changing superfluous landscape, the veil is lifted gradually as we intensely dig deeper using instruments ready to redefine our future. Our profound ignorance often becomes bluntly evident as we start to passionately navigate the curves of the charts, allowing us to gradually achieve a level of awareness at which we learn to be amused rather than shocked. The below graphical representation using Tableau of Coronavirus statistics of India depicts statistics of confirmed cases, cured cases and death cases across all the states as of Aug 22nd 2020. It’s strikingly concerning when clicking through the percentages of health stats, we find some states which seemingly have low confirmed cases are not doing too well in overall death percentage. Or states that appear dangerously higher up in rankings of confirmed cases are often actually doing comparatively well considering their cured percentages. The below analytics can be best viewed on a larger screen display.
var divElement = document.getElementById(‘viz1660271990537’); var vizElement = divElement.getElementsByTagName(‘object’)[0]; vizElement.style.width=’100%’;vizElement.style.height=(divElement.offsetWidth*0.75)+’px’; var scriptElement = document.createElement(‘script’); scriptElement.src = ‘https://public.tableau.com/javascripts/api/viz_v1.js’; vizElement.parentNode.insertBefore(scriptElement, vizElement);
The metaphor of counting hails in a hailstorm is not accidental. When data arrives in torrents, when numbers shift daily and the ground beneath the analysis keeps moving, the instinct is to wait for the storm to pass before making sense of it all. But that luxury does not exist in a situation like the one unfolding across the country. Decisions about hospital capacity, lockdown zones, resource allocation and public health messaging cannot wait for clean, settled data. They need to be made now, with whatever imperfect information is available. That is where analytics earns its place at the table.
What makes the Coronavirus dataset particularly challenging for any analyst is the sheer inconsistency in how data is reported across states. Testing rates vary wildly. Some states ramped up testing infrastructure early while others lagged behind for weeks. A state reporting lower confirmed cases might simply be testing fewer people rather than having fewer infections. This distinction is critical and it is one that raw confirmed case numbers alone cannot reveal. When we layer in testing data alongside confirmed cases in Tableau, the picture shifts dramatically. States that looked safe on the surface suddenly appear undercounted. States that seemed overwhelmed start to look like they are simply being more transparent.
The cured percentage metric is another layer that rewards careful exploration rather than surface level reading. A high cure rate in absolute terms sounds reassuring but it needs to be weighed against the timeline. If a state had its major outbreak early and has since plateaued, a high cured percentage is expected because most of the active cases have had time to resolve. A state in the middle of its surge will naturally show a lower cured percentage not because its healthcare system is worse but because the clock has not run long enough on its recent cases. Tableau allows us to bring in the time dimension through animations and date filters, letting the viewer watch how these percentages evolved week by week rather than judging them at a single frozen point.
The death percentage metric demands perhaps the most careful interpretation of all. It is the number that generates the most fear and the most headlines but it is also the number most susceptible to reporting inconsistencies. How a death is classified, whether comorbidities are factored in, whether deaths outside hospital settings are counted, all of these vary from one state health department to another. When building the Tableau visualization, the temptation was to present this as a simple ranked bar chart. But ranking states by death percentage without context would have been misleading. Instead, placing it alongside confirmed cases and cured percentages in a combined view lets the viewer form a more nuanced understanding. The story is never in a single number. It is always in the relationship between numbers.
One of the design choices that proved valuable in this visualization was using percentage based measures rather than absolute counts for comparison purposes. Maharashtra and Goa cannot be meaningfully compared on absolute confirmed cases. Their populations, urban density, testing capacity and healthcare infrastructure are fundamentally different. But when you shift to percentages, to case fatality rates, to recovery ratios, to cases per unit of testing, the comparison becomes more honest. It does not eliminate the differences in context but it at least puts the numbers on a more comparable footing. Tableau makes this shift between absolute and relative views almost effortless with parameter controls and calculated fields.
The interactive nature of the visualization is what separates this kind of analysis from a static report. A printed table of numbers for all states would contain the same data. But the ability to click on a state, to hover over a bar and see the underlying figures, to filter by region or sort by a different metric entirely, that interactivity transforms the experience from passive reading to active exploration. The viewer becomes a participant in the analysis rather than a consumer of conclusions. This is especially important with a dataset as emotionally charged as pandemic statistics. People need to be able to interrogate the numbers on their own terms to build trust in what the data is telling them.
Building this kind of dashboard during an active crisis also taught a practical lesson about the difference between accuracy and timeliness. In a normal analytics project you have the luxury of waiting for data to stabilize, for revisions to come in, for reconciliation to happen. During a pandemic that luxury disappears. The data you have today will be revised tomorrow. Numbers will be corrected, backdated, reclassified. An analyst has to make peace with the fact that the dashboard published today will not perfectly match the historical records compiled six months from now. The value is not in being perfectly accurate. The value is in being directionally correct and available when the decision needs to be made.
The experience also reinforced how important data storytelling is when the audience extends beyond the analytics team. Not everyone looking at a Coronavirus dashboard understands what a logarithmic scale means or why a seven day moving average smooths out reporting artifacts. The labels, the tooltips, the color choices and the layout all need to be designed with the least technical viewer in mind. If a concerned citizen in a small town opens this visualization, they should be able to find their state, understand the key numbers and draw a reasonable conclusion without needing a tutorial. That is the standard every public facing dashboard should aspire to meet.
There is also a humbling aspect to working with data of this nature. Behind every data point is a person. Behind every increment in the confirmed cases count is someone who received a diagnosis that changed their life for weeks or months. Behind every increment in the death count is a family that lost someone. It is easy to become detached when you spend hours adjusting axis ranges and formatting tooltip text. But the best analysts find a way to hold both realities at once. The technical precision that makes the visualization trustworthy and the human awareness that keeps the work grounded in why it matters.
As the situation continues to evolve and new data arrives with each passing day, the visualization will need to be updated and potentially restructured. Metrics that seem important now might become less relevant as the situation changes. New dimensions might emerge that we have not yet accounted for. The hailstorm is still raging and we are still counting. But with each iteration of the analysis, the picture becomes a little clearer, the patterns a little more defined, and our ability to act on what the data is telling us a little more confident.
