Articles

News from FNH and the industry

Articles

News from FNH and the industry

Articles

News from FNH and the industry

The FAA Ground Stop Looks a Lot Like Every Failed Software Rollout I've Lived Through

The FAA Ground Stop Looks a Lot Like Every Failed Software Rollout I've Lived Through

The FAA's nationwide ground stop came three days after it expanded a new AI traffic tool, and a top official blamed new technology overwhelming an old system. The cause is still being sorted out, but the pattern is one I've watched sink agency platform rollouts. Here's the process I use now, and the two questions that decide whether a new tool helps or just creates more work.

Whatever caused the FAA ground stop, it mirrors how most software rollouts fail: a new tool gets bolted onto an old way of working by people who won't use it, before anyone answers what problem it solves.

Whatever caused the FAA ground stop, it mirrors how most software rollouts fail: a new tool gets bolted onto an old way of working by people who won't use it, before anyone answers what problem it solves.

Whatever caused the FAA ground stop, it mirrors how most software rollouts fail: a new tool gets bolted onto an old way of working by people who won't use it, before anyone answers what problem it solves.

Author

Rich Roginski

(Founder, FutureNova Health)

(Founder, FutureNova Health)

Topic

Marketing Operations

Published date

Subscribe to Signals

Stay up-to-date with the latest innovations, features, and tips in no-code website building!

By checking the box above, I agree to receive marketing communications from FutureNova Health and can unsubscribe at any time.

On the afternoon of Friday, November 13, the Federal Aviation Administration (FAA) stopped every departure in the country. My first reaction was the one I always have when something system-wide goes down: what caused it? Is it a tech problem or a people problem? Microsoft Outlook had gone down the same week, and I was asking the same question then.

Three days before the ground stop, the FAA had expanded SMART (Strategic Management of Airspace, Routes and Trajectories), its new artificial intelligence (AI) traffic management tool, to all 22 air route traffic control centers. To be fair, nobody has confirmed the full root cause yet, and the FAA says SMART played no role. Its November 15 update points to an aging telecommunications network that became unstable when excessive data traffic flooded it. Homeland Security Secretary Markwayne Mullin said new technology introduced into an old air traffic control system overwhelmed it.

Whatever the final answer is, one detail stuck with me. When SMART first launched in September, Rep. Don Beyer said he had been told air traffic controllers were not consulted on its design and were not trained on it before it was adopted. That part I recognized. I've watched large agencies roll out new platforms the same way. All the energy goes into the rollout, but the pieces that matter most happen before it, starting with sign-off from the people who are actually going to live in the platform.

Why a Failed Software Rollout Starts Before Anyone Logs In

Here's one I lived through. I won't name names. We were an agency running our projects on a well-known work management platform, and it was good at what it was built for. The problem was that we also wanted it to manage finances and resourcing. It just wasn't the platform to do that.

The vendor said they could make it happen with custom coding and a stack of special workarounds. That's always my red flag. When a platform I'm pretty sure can't do something says it can, it usually means a pile of patches, a backwards process and a lot of extra labor.

We end up working for the tool. The tool doesn't end up working for us.

I knew it was going sideways the moment it was signed off. The decision came from people who weren't in the day-to-day. They weren't doing the work. They weren't going to be in the platform. The people who were, and who would ultimately be responsible for making it work, weren't brought into the final decision, or much of the process at all.

The real reason it failed is short. It was doomed from the beginning. There was no real buy-in, and no process built to do what we needed it to do. Just backwards workarounds that created more work for the team using it.

Bolted On vs. Integrated: Why New Tool Adoption Stalls

The key word is bolted on. If it's bolted on, it's not going to work. A new tool has to be integrated into the systems you already run, or you build new systems around the new process. Anything that sits off to the side as a separate piece gets ignored.

That's worth remembering right now, with biotech and pharma marketing teams adding new tools, AI tools especially. Before anything new gets added, I want to know whether we'll have to enter the same data twice. Every time you re-enter data or move it around, you compromise the data, and you compromise the end product. I want to know whether it moves the work forward and actually saves time. And I want to know whether the lead from every department that will touch it has been heard. Not just told. Asked for feedback.

Integrating something is a lot harder than bolting it on. It takes more time and a lot more architecture, and that part is almost always ignored. "We have this new tool" quietly turns into "it doesn't really fit into your day-to-day," and that's where adoption dies.

How to Run a SaaS Implementation That Actually Sticks

Whether it's a new SaaS (software as a service) platform or a new internal process, when a complex rollout works, it's because the work up front got done. This is the process I use now.

  • Name the problem first. A lot of the time we just feel like we need something new. Often the process we already have is fine and needs a few tweaks. Everything gets rooted in the problem.

  • If it can't solve the problem cleanly, it's out. If it needs a pile of customization or a bunch of hoops to get there, it's out. And why spend all that effort, time and money on something that only marginally improves the process?

  • Get a small core group to make it work and break it. They test how it fits into the process and map the architecture that connects it to the apps and programs you already use, so it doesn't become one more thing that's a hassle or never gets done.

  • Build the plan. Cost, timeline, and one more check: is it still solving the problem?

  • Stay in the build. Don't let a vendor go away and come back with something. Keep a small, representative group in every step of development. You'll never get buy-in from the whole organization, and trying is a headache, but letting someone else make the decisions for you gets you a tool that isn't what you asked for.

  • Beta on one account or team. Do full runs, and set up an easy way to capture feedback as issues happen.

  • Roll out with key performance indicators (KPIs). The implementation plan matters as much as anything else. How does it reach everyone, what does that look like, and how will you prove it's working? If you don't have KPIs when you launch a new initiative, you're in trouble.

The Two Questions That Decide Every Rollout

If I were in the room with a biotech marketing lead about to roll out a new tool or process next month, I'd ask two questions.

First: what problem are you solving? If they can't answer that right off the bat, they're going to fail. Every other decision in the rollout depends on that answer.

Second: how does this solve that problem? If they can't answer that, or the answer is that it doesn't, then what are we doing here?

If both answers hold up, then we dig deeper. If they don't, there's no reason to go any further.

Whether or not SMART had anything to do with the ground stop, the lesson is the same one I learned inside agencies. Everyone watches the rollout. The things that decide whether it works happen long before anyone flips the switch.

FREQUENTLY ASKED QUESTIONS

Did the FAA's SMART tool cause the November 13 ground stop?

Nobody has confirmed the full root cause yet. The FAA says SMART played no role, and its November 15 update points to an aging telecommunications network that became unstable when excessive data traffic flooded it.

Why do new software rollouts fail?

The problems often start before launch. The decision comes from people who won't be in the platform, the people who will be aren't brought in, and the tool is bolted on instead of integrated into the systems already in use.

How do you run a software implementation that sticks?

Name the problem first, and drop any tool that can't solve it cleanly. Have a small core group test it and map how it connects to the systems you already use, build the plan, stay in the build, beta it on one team, and roll out with KPIs.

Subscribe to Signals

Stay up-to-date with the latest innovations, features, and tips in no-code website building!

By checking the box above, I agree to receive marketing communications from FutureNova Health and can unsubscribe at any time.

Author

Rich Roginski

(Founder, FutureNova Health)

Topic

Marketing Operations

Published date

Subscribe to Signals

Stay up-to-date with the latest innovations, features, and tips in no-code website building!

By checking the box above, I agree to receive marketing communications from FutureNova Health and can unsubscribe at any time.