Innovation 101: Why You Should Start with a Ford, Not a Ferrari
How to Really Get Started with Innovation: Failing Forward, Experimentation, and Collaboration
Happy midweek!
I’ve been writing about getting started – taking that first bold step toward creating something new within your organization. But, in all honesty, what does “getting started” really mean? How do you take that nebulous idea and bring it to life without risking everything or spending weeks overthinking?
So today, let’s break down core principles of getting started in innovation – especially if you’re working within a larger organization and building something from the ground up. The focus is simple: try, fail cheap and fast, and learn as you go.
In a world where we’re often encouraged to wait until everything is “perfect,” embracing a “fail forward” approach can be the difference between a project that never launches and one that sparks genuine change.
Principle #1: Don’t Go for the Ferrari Right Away – Start with a Ford
When you’re diving into innovation (or any hobby, at some point), it’s tempting to want the best tools, the most advanced software, and the flashiest features right from the get-go. But here’s the truth: you don’t need a Ferrari when an old Ford can get you where you need to go. Innovation isn’t about starting with the perfect tool – it’s about getting from point A to point B efficiently and learning along the way.
Ask yourself: Does my idea really need all these resources right now? Or can I start with a basic, less expensive solution that still gets the job done? This mindset is crucial, especially if you’re in a corporate environment where budgets and timelines are scrutinized. Opt for tools that allow you to test your idea without a heavy investment. Once you’ve proven its value, you’ll have a stronger case for upgrading to that Ferrari-level solution.
Example: I’ve seen teams push for high-end software only to discover they didn’t actually need half the features - and the cost of development was higher, backlog was bigger with that external provider, so waiting time had also a cost to it. In one case, a team was interested in a sophisticated analytics tool to track user engagement but realized that a simple app developed in low-code could capture 80% of the insights they were looking for. Starting with the basics saved them time, money, and a lot of unnecessary complexity – proving that sometimes, less really is more.
Principle #2: Embrace ‘Failing Forward’
If you’re waiting for the perfect moment or the perfect tool before you launch, you’ll be waiting a long time. Innovation rarely comes from a series of wins; instead, it’s born from the lessons we gather along the way. The concept of “failing forward” means viewing each setback as an experiment, not a failure.
Imagine you’ve come up with an idea to streamline your department’s workflow. Instead of waiting until you have all the resources to build an automated solution from scratch, start small. Try a simple Excel sheet, a no-code app, or a straightforward script that addresses the basic needs. Track what works, where the gaps are, and adjust accordingly. Think of each mini-failure as a learning moment that shapes your approach for the next round.
Example: I once led a project where we wanted to implement a digital solution for managing inventory of our IT helpdesk (did you know that chargers get stolen really frequently in offices???). Instead of starting with a complex ERP system, we created a quick database on a no-code platform, connected it to SharePoint (our Intranet) so that we could put some basic no-code automations on it and tested it for a few weeks - this means automatic e-mails to the IT Director, confirmation messages to the requester.
It didn’t cover all the features we wanted, but it revealed which features actually mattered most to the team. And because we failed forward – adjusting and refining as we went – by the time we were ready for a larger investment, we had a clear roadmap for success. (It just didn’t solve the stealing coworkers’ chargers issue haha)
Principle #3: Don’t Be Afraid to Ask for Help
When you’re building something new, it’s easy to fall into the trap of thinking you need to have all the answers.
But innovation doesn’t happen in isolation – it’s a team effort. One of the most valuable things you can do is to tap into the knowledge of others. Maybe that’s seeking advice from someone who’s tackled a similar project, or reaching out to other departments to see if they’ve faced comparable challenges. The insights others can provide are often just what you need to overcome obstacles or find new approaches.
Don’t think of it as admitting defeat; think of it as collaboration. Sometimes, the simplest questions can spark an “aha” moment that changes the entire trajectory of your project. And by including others, you’re also laying the groundwork for broader buy-in and support down the line.
Example: During a project involving process automation, we reached out to the finance team to understand their pain points with the current process. While I did feel I needed to take an intensive course about SAP and cash allocation process, once I sat down with them step by step, I was able to hear their feedback, which led to an entirely new feature we hadn’t initially considered – one that eventually became one of the most valuable components of the final Minimum Viable Product. That simple act of asking for input not only improved our solution but also strengthened relationships across teams.
Bringing It All Together
So, if you’re standing at the edge of an idea and wondering how to get started, keep these principles in mind:
Start Small, Start Simple: Don’t go for the Ferrari right away – make sure you can drive the old Ford first. Use the resources you have to create a prototype, test it, and build from there.
Fail Forward: See every setback as a chance to learn. Innovation is iterative, and each step will bring you closer to the solution you’re envisioning.
Seek Support: You’re not in this alone. Reach out, collaborate, and use the knowledge around you to build something truly impactful. People like to feel heard, needed - so if you use that to your advantage, you win them over to like your ideas :)
Innovation doesn’t have to be a scary, difficult, perfection-driven process. It can be messy, full of small experiments, and even more small failures. But with each attempt, each adjustment, you’re moving forward. Remember, growth isn’t always linear, but it’s always forward.
Start small, stay curious, and before you know it, you’ll be well on your way to building something that makes a difference.
And one last thing… we have an exciting post coming up this Sunday about… spies! Yes, you read that right. I'm so excited for you to read this one – stay tuned!
Next Wednesday, we’ll dive deeper into concepts of innovation with one my most recent answers to “spirit animals”. Until then, embrace the idea of failing forward, and remember that every small step is progress.
Keep moving, keep learning, and vroom vroom - please hear a Ford noise, not a Ferrari, I don’t have those resources just yet
One last thing: next week I’m hosting a series of group session on ADP List - If you’re interested, you can join for free!
Next Tuesday 15/10 at 19h00 Amsterdam time, we meet to talk about Intrapeneurship essentials. It’s free to join, but spots are limited, so make sure to
On Tuesday 29th of October, at 19h, the second session will be about Finding the right problem to solve.
If you liked this and you’re on Substack, feel free to restack it with notes on what you liked… or didn’t like!
And if you haven’t already…