What a Space Shuttle Experiment Taught Me About ERP Innovation

When people hear that one of my early research projects went into space aboard a NASA shuttle, they usually expect a story about technology.

However, what I really took away from that experience wasn't about science at all; it was about ERP innovation and how ERP in the cloud can drive innovation.

"Innovation distinguishes between a leader and a follower." Steve Jobs, Co-Founder of Apple

It was the moment I realized that big breakthroughs, whether they happen in orbit or in business, aren't born from certainty.

They're born from curiosity, collaboration, and the courage to ask why one more time.

From Petri Dishes to Possibility

Back then, I worked in clinical diagnostics for a startup developing tools to detect bacterial infections faster.

We were a small team with a bold goal: design something so precise and reliable that it could survive the rigors of space flight.

Every decision and every experiment was a test of both the product and our thinking. We had to plan for what we couldn't predict.

There was no "manual for shuttle science."

This kind of structured curiosity is precisely what today's businesses need when considering cloud-based ERP systems, such as Microsoft Dynamics 365 Business Central.

So we ran trial after trial, questioning every variable, every assumption.

• What if microgravity changed the way cells behaved?

• What if our calibration failed mid-orbit?

• What if we were solving the wrong problem?

We didn't innovate by following a checklist. We innovated by challenging it.

(And by drinking more coffee than I'd like to admit.)

Innovation Begins Where Certainty Ends

That experience taught me that innovation doesn't start with the answer. It begins with the question you dare to ask when the answer isn't obvious.

In the lab, asking why led to discoveries that made our product space-ready.

In business, asking why reveals the unseen inefficiencies, assumptions, and habits that hold teams back.

When I transitioned from science to ERP consulting years later, I realized I was still doing the same work: diagnosing systems, identifying variables, testing hypotheses, and measuring results.

Only now, the "organisms" were ERP Systems.

Just like an experiment, every business challenge has inputs, controls, and desired outcomes. If one variable is off, say, data visibility, workflow design, or communication, your results will be inconsistent.

The fix isn't guesswork; it's structured curiosity.

For more information, read Inefficiencies in B2B Processes: Curiosity Fuels Innovation.

Innovation isn't a lightning bolt of genius; it's Mission Control on the ground: testing, monitoring, and adjusting every variable so that bold ideas can safely take flight.

The Shuttle Lesson: Build ERP Innovation for What You Can't See

When we designed the diagnostic kit for space, we had to imagine conditions we couldn't observe directly. That forced us to think differently.

We had to simulate scenarios, document every dependency, and design redundancies for the unknown.

That same mindset applies to modern business ERP innovation and ERP implementation best practices.

Whether you're implementing a new ERP system, rolling out automation, or re-engineering your customer experience, you can't plan for every outcome.

But you can design for resilience.

In other words: build ERP systems that don't just work when everything goes right.

Build ones that adapt when they don't.

In cloud ERP platforms like Microsoft Dynamics 365 Business Central, this means creating feedback loops, workflow optimization, enhancing visibility through a Business Central dashboard, and implementing processes that evolve with your business.

You're not just configuring software; you're engineering adaptability.

Because if there's one thing space (and business) will teach you fast, it's that things rarely go exactly as planned.

And that leads to two of the most common questions I hear from growing businesses embracing this kind of transformation, whether that's cloud-based ERP or a Business Central cloud migration strategy.

Which Change Management Practices Actually Prevent ERP Adoption Failure and Accelerate Time-to-Value for a Mid-size Company?

Successful ERP adoption depends less on technology and more on managing people and process change.

Mid-sized companies achieve the best results when they establish visible executive sponsorship, involve end-users early, and focus on role-specific impacts.

Instead of a one-size-fits-all approach, effective change programs map how daily workflows will shift, empower frontline "change champions," and deliver tailored training that reflects real data and user workflows.

To accelerate time-to-value, prioritize phased rollouts over big-bang go-lives and focus on quick wins that build confidence.

Embed behavioral KPIs into performance metrics, like system usage or process adherence, and pair them with targeted incentives to reinforce new habits.

Lastly, post-go-live hyper care, with real-time monitoring and user feedback loops, ensures that adoption issues are identified early and addressed before they become barriers.

What's the Best Way to Test and Iterate Business Central Workflows to Make the System Resilient to Change?

The best way to test and iterate Business Central workflows is to start with sandbox environments that closely mirror the production system.

This allows teams to simulate real-world scenarios and conduct pilot tests with select users to validate processes before full deployment.

Leveraging tools like Analysis Mode in Business Central, you can monitor how workflows perform under different conditions and gather actionable insights, whether it's data flow issues, user behavior patterns, or bottlenecks in approval processes.

Sandboxes also offer a safe space to trial new extensions, customizations, or updates without disrupting live operations.

Equally important is building structured feedback loops into the workflow testing process.

Engage end users early and often to capture their observations and challenges; this is where change management meets quality assurance.

Combine qualitative feedback with quantitative usage metrics to refine workflows iteratively.

As changes are promoted to production, establish governance processes to monitor performance and ensure continuity of operations.

Over time, this test-and-learn approach makes your Business Central cloud ERP system more resilient, agile, and aligned with your evolving business needs.

What Space Taught Me About Teams

Perhaps the most human lesson from that mission was the importance of collaboration under pressure.

No one person could own the entire solution. We had scientists, engineers, quality experts, and NASA advisors all asking different versions of the same question: What if?

That kind of psychological safety, the freedom to question, is the heartbeat of innovation.

In business, I see the same dynamic.

The best project outcomes come from teams where it's safe to challenge the plan, revisit the data, and admit when something doesn't make sense.

Curiosity thrives in that space between expertise and humility.

And so does growth.

And let's be honest, if a scientist can admit they've mislabeled a test tube in front of a NASA engineer, your project manager can probably handle rethinking a workflow in front of IT.

Bringing the Lab Mindset to the Boardroom

Every ERP engagement I take on today begins with the same discipline that guided our shuttle experiment:

• Observe first. Gather data before jumping to solutions.

• Define the hypothesis. What problem are we really trying to solve?

• Test small. Pilot the process. Measure. Adjust.

• Repeat. Innovation isn't an event; it's an iterative process.

When clients see me mapping workflows like an experiment or documenting assumptions like a lab protocol, it's not overkill.

It's how we uncover the real variables that drive success.

A business system is like a living organism: every process, workflow, and department is interconnected.

You can't heal one part without understanding how it affects the whole.

That's how we turn technology projects, such as Dynamics GP to Business Central migrations, into transformation engines.

Whether you're planning a GP to Business Central migration or building a cloud ERP foundation, the lab mindset applies.

And yes, I still wear my metaphorical lab coat sometimes. (Though these days it's usually a Microsoft Dynamics sandbox instead of a petri dish).

Innovation Is a Habit, Not a Moment

The shuttle project didn't just succeed because we had great tech.

It succeeded because we were relentless in our pursuit of learning.

Just as astronauts can't survive without oxygen, innovation can't survive without curiosity. It fuels every experiment, conversation, and breakthrough.

That's the same spirit I bring to every business conversation today.

Whether I'm working with a manufacturer to refine its production processes or a professional services firm trying to improve utilization, my first question is still the same one I asked in the lab: Why?

Because every "why" opens a door to a better way of working.

And every time we stay curious long enough to walk through it, we discover that innovation isn't rocket science after all. It's disciplined curiosity applied with purpose.

For more insights, read: A Scientific Approach to ERP Consulting Success

Final Thought

Innovation isn't something that happens in a lab or even in space.

It happens every time a leader chooses to question instead of assume, to test instead of guess, and to learn instead of defend.

True innovation happens in that narrow orbit between what we know and what we imagine. It's where curiosity pulls us forward, and courage keeps us there long enough to find something new.

The space shuttle experiment taught me that the distance between where you are and what's possible isn't measured in miles. It's measured in mindset. 

And if curiosity got my experiment into orbit, it could probably get your business a little closer to lift-off, too.

So, what's the one question your business hasn't asked lately that could change everything?

About the Author 

Terri Marello, President of Key Partner Solutions, is a thought leader in the Microsoft Dynamics space and the author of the LinkedIn newsletter "Why Ask Why?", where she explores the intersection of technology and business strategy.

Subscribe now for more insights straight to your inbox.

Key Partner Solutions is an experienced Microsoft VAR with the in-house skills to optimize your business and smoothly migrate to cloud-based Microsoft Dynamics 365 Business Central.