Across America, public infrastructure projects are frequently cast as monoliths of inefficiency; bloated, delayed, and sometimes inert. A McKinsey report laid bare the crisis: major infrastructure projects typically overshoot timelines by 20%, and budgets by up to 80%. These are not just project management hiccups. They are an indicator of a bigger problem. These systems operate as if they were set in an earlier era and stand in opposition to technological improvements. McKinsey report In the times of this dysfunction, a subtle shift was taking place inside the workings of the state agency in Massachusetts that is charged with the responsibility of transportation infrastructure and services. No headlines were written about it. There were no press conferences, no grand declarations of reform. But change did come, and it came not from above, but from the quiet, persistent efforts of a Senior Data Analyst, Deepak Chanda. In the bowels of the state agency’s project workflows, Deepak encountered a familiar kind of stagnation. Blueprint review meetings dragged on for hours. Project approvals declined in bureaucratic limbo. No one was negligent, but the system was unyielding. A cathedral built to honor tradition over function. He saw the waste not just in time or money, but in human energy. People showing up, day after day, to enact a process no longer fit for its purpose. What marked Deepak’s work was not a flash of disruption, but a gradual reimagining. He didn’t shout. He asked questions. Why are we still gathering around tables to inspect blueprints? Could this not be digital, asynchronous, and fluid? With that inquiry as his compass, he sought tools that could chip away at this inertia. Enter Bluebeam, a digital collaboration platform. It wasn’t new to the world, but it was new to the state agency’s blueprint review pipeline. Deepak didn't just make suggestions; he would test and de-risk them, put them into operations, train others, and become part of that operational DNA of the department. Whereas teams previously would either review slow-moving documents in face-to-face meetings, now they were engaged in real-time interaction from their own screens. The result? Each project began to save dollars, significant in the public sector, where every dollar saved can mean another pothole filled or rail fixed. But beyond these figures, there was a transformation in posture. Deepak had demonstrated that the system was not unchangeable. He had, with patience and precision, introduced a new way of working. And the momentum continued. In another corner of the transportation department, Deepak encountered a different but equally stubborn bottleneck. Road construction inspectors were required to sign off on certain work milestones within 21 days. These sign-offs were vital; they triggered quality checks, milestone payments, and regulatory compliance. But with inspectors juggling multiple sites and no centralized tracker, critical deadlines were routinely missed. SharePoint forms had replaced paper, but the process still suffered in silence. There were no warning glimmers, no indicators, no ways to detect what was slipping through the cracks, until it was already too late. Deepak looked past the tools and into the logic. He asked: “What’s blocking progress, and how can we use data to unblock it?” The fix was deceptively simple. Using SQL, he added a single derived field to the data pipeline: Days Remaining for Sign-Off. It calculated how many days were left, or how overdue the sign-off was, and fed this directly into a dynamic report connected to SharePoint. On the BI layer, overdue items flashed in red. But Deepak didn’t stop there. He built two views: a site-specific dashboard for inspectors and a consolidated one for managers. Suddenly, the inspectors had clarity. Team leads had visibility. The guesswork disappeared. The impact was immediate. Delays dropped. Inspectors began checking the dashboards not out of obligation, but because it made their jobs easier. Managers could intervene before problems escalated. No new app. No overhaul. Just SQL, SharePoint, and focused storytelling. Sometimes, real transformation isn't about building something new, but it is about seeing something that is already there more evidently. This moment at the organization was not a climax, but a beginning. Deepak’s role evolved from data analyst to process architect. No longer just parsing figures, he started shaping the workflows that produced them. He carried these skills and the mindset that enabled them into the broader arenas of healthcare and insurance. These sectors are, in some ways, even more complex than transportation. They’re bound not only by regulation and tradition, but by a moral gravity. Mistakes here don’t just cost time; they can cost lives. Deepak’s interventions had to be not just effective, but elegant. His core idea remained unchanged: good data should not merely report the world, it should help shape it. He began to build adaptive data pipelines that embraced real-time responsiveness over static reporting. At the heart of this system was automated anomaly detection, software that doesn’t wait to be told something is wrong. It flags issues as they happen, sometimes before humans even notice. This shift, from batch to real-time, from reactive to proactive, is where Deepak’s work began to challenge the conventional boundaries of data engineering. His systems did more than process data. They learned from it, adapted to it, and fed insights back into the operational bloodstream of the organizations they served. In healthcare, this meant fewer delays in diagnostics and better coordination of care. In insurance, it meant faster claims assessment, fraud reduction, and improved user trust. And that kind of progress appears silent; a hidden reshaping of the environment it inhabits. Alongside these practical contributions, Deepak has added to the intellectual structure of his field. His publication, “The Role of Data Engineer and Analyst in Health Insurance and Coordination,” appeared in the International Journal of Data Science and Machine Learning. It is not a manifesto, but a careful meditation on how structured data practices can unlock systemic efficiency in health systems. It bridges theory and fieldwork, showing how analytics can reshape operations from within, without grand overhauls. Outside of the institutional corridors, Deepak offers his time and insight to the next generation. He often takes a mentor or judge role at science fairs and international hackathons, interacting and challenging young tech people, sometimes learning from them: it is a conversation, not a lecture. What makes his journey distinct is not only what he did but also how he did it. He resisted the urge to disrupt for disruption’s sake. He didn’t seek transformation through demolition, but through careful iteration. His changes took root not because they were loud, but because they were right. He often says, “I think some of the most meaningful changes begin when someone simply refuses to ignore what everyone else has grown used to.” That kind of attention, deliberate, patient, unyielding, has followed him into industry after industry. He works with an ethic rarely seen in the technological world, where speed often dominates substance. In that way, his work brings to mind an older concept: progress is not wrought through genius alone but through empathy and attention to detail. So while there may never be breaking news about his impact, it doesn’t make it any less significant. In a world clamoring for transformation, Deepak Chanda has quietly shown that sometimes, the real revolution is paying attention and making things work just a little better than they did before.

This story contains new, firsthand information uncovered by the writer.

How Data Innovation Changed a State’s Infrastructure Engine

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

$INK: The Solana Memecoin with a Vision for Utility

4 Data Transformations Made Spreadsheet-Easy

Processes and New Technologies in Data Transformation

Unleashing the Power of Data: From Burden to Driving Force

Why My Brain Is Wired for Clojure

$INK: The Solana Memecoin with a Vision for Utility

4 Data Transformations Made Spreadsheet-Easy

Processes and New Technologies in Data Transformation

Unleashing the Power of Data: From Burden to Driving Force

Why My Brain Is Wired for Clojure

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps