The Initiative That Didn’t land
- Smriti Sridhara

- 4 days ago
- 4 min read
Updated: 3 days ago

What a failed 5G pre-order launch taught me about the hidden cost of chasing ideas that aren’t ready to ship.
Key Takeaways
Calling something a priority does not make it executable. Readiness needs to be validated.
When a high-profile initiative stalls, the cost is not just that project. It is everything your team could not do while they were pulled into it.
The hardest skill in program management is not driving execution. It is knowing when to stop and say so.
Ambiguity in the foundation (geography, tools, eligibility) will surface at the worst possible moment, which is usually during delivery.
Speaking up early about unresolved dependencies is not pessimism. It is the most valuable thing a program leader can do.
Why This Matters
Every team has faced this at least once. A senior leader champions an idea. The business case sounds solid. Resources get assigned. Meetings multiply. And then, somewhere in the middle of execution, it becomes clear that the underlying conditions were never in place to make it work.
What makes this particularly costly is not just the initiative itself. It is the collateral damage: the other work that slows down, the team bandwidth that gets absorbed, and the credibility that quietly erodes when the initiative quietly disappears from the roadmap.
This is not a failure of effort. It is a failure of validation. And it is more common than most leaders want to admit.
The Experience That Changed My Perspective
A few years into my time as a Program Manager at Verizon, a senior executive came to the team with an idea that made intuitive sense: allow customers to pre-order 5G home internet service before the infrastructure was fully deployed in their area. The logic was straightforward. Capture demand early, accelerate sales momentum, get ahead of the rollout.
It was declared a priority as the deployment was just a few months away. We were tasked with making it happen.
What followed was months of effort against a problem that, in hindsight, was not yet solvable. The geographic coverage map was still fluid. We did not know with certainty which areas would be serviceable, or when. Service representatives had no reliable way to check eligibility at the point of sale. The systems that would need to manage a pre-order queue and later convert it into an active account were not built for that workflow.
Every dependency revealed another one underneath it. And yet, because the initiative carried executive sponsorship and had been declared a priority, the team kept working. Other programs with clearer paths to delivery were deprioritized to make room for this one.
Eventually, the initiative was quietly shelved. The problems were too numerous and too foundational to work around. But by the time we stopped, we had spent months on it. The team was fatigued. Other work had suffered. And we had very little to show for it.
I wish I had pushed back harder, earlier. Not to derail the idea, but to get the right conditions validated before we committed the team’s capacity.
The Insight Most People Miss
In large organizations, there is enormous pressure to treat executive enthusiasm as a green light. When a director or VP frames something as a priority, the path of least resistance is to start executing. Asking hard questions can feel like resistance. Raising risks can feel like a lack of confidence.
However, here is what I have come to understand. The most dangerous initiatives are not the ones with obvious problems. They are the ones with enough momentum and conviction behind them that the foundational gaps never get examined closely enough.
The pre-order program was not a bad idea. It might have been a great one at a different point in the infrastructure timeline. The failure was not the concept. It was the absence of a readiness check before resources were committed.
The questions that needed to be answered were not complicated:
Is the geographic data stable enough to make commitments to customers?
Can our systems support a pre-order workflow end to end?
Do our reps have the tools they need to check eligibility in real time?
If the answers to those questions are “not yet,” that is the answer, and it needs to be heard before the team is deployed, not after.
How I Approach This Today
I now treat execution readiness as a non-negotiable step before any initiative gets resourced. That means asking a set of grounding questions at the start of every program, not to slow things down, but to surface the blockers that will slow things down later if left unaddressed.
Specifically, I look for:
Geographic or eligibility dependencies that are not yet locked, anything that introduces variability into what we can actually deliver
Tool and systems gaps: can the people doing the work do it with what they have today?
Downstream workflow readiness: what happens after the customer says yes, and is that path fully built?
Opportunity cost visibility: what will not get done if this team is pulled into this initiative?
I also make it a practice to document what I see, name the risks explicitly, and bring them to the right decision-makers early. Not as a reason to stop, but as the input needed to make a real decision about whether to proceed, pause, or invest in resolving the gaps first.
The goal is not to be the person who slows things down. It is to be the person who prevents the kind of six-month slog that ends with a shelved initiative and a depleted team.
Let’s Connect
If this resonates, I would love to hear from you. Whether you are navigating a stalled initiative, trying to build better prioritization habits across your team, or simply want to think through a program that feels harder than it should, reach out directly.
Smriti Sridhara is an execution-driven telecom leader with over a decade of experience at Verizon, where she has led high-impact, revenue-generating programs from strategy through national launch. She has spearheaded major pricing and value-proposition transformations, including large-scale Unlimited plan initiatives that drove hundreds of thousands of new accounts and strengthened customer growth.
Known for aligning cross-functional teams across Marketing, Network, IT, Finance, Customer Care, and Supply Chain, Smriti brings clarity and momentum to complex programs. Her expertise spans product strategy, go-to-market execution, AI-enabled delivery practices, and large-scale operational rollouts—consistently translating vision into measurable business results.



Comments