Experiment Driven Design

In this episode, we dive into the concept of Experiment-Driven Design (EDD) and how it eliminates waste from software development. Ever felt overwhelmed by software features that seem unnecessary? You’re not alone—64% of enterprise software features go unused! Discover how InfoBeans’ Experiment Driven Design approach tackles this issue by focusing on smaller, calculated experiments to validate assumptions and guide product development. Learn about different types of experiments, like paper prototyping and “Wizard of Oz” MVPs, and how to use an experiment dashboard to stay aligned and efficient. We also explore how this mindset not only minimizes waste in software but can transform other aspects of your work and life. If you’re looking to make every line of code and every design decision count, this episode is for you!

Experiment Driven Design (EDD) is a software development process that prioritizes rapid experimentation and user feedback to minimize waste and maximize business outcomes. This iterative approach involves breaking down large projects into smaller, testable experiments that validate hypotheses about user needs and product features. By emphasizing learning over immediate business results, Experiment Driven Design helps teams quickly identify and discard ineffective features, saving time and resources. This process, popularized by companies like InfoBeans, relies on tools like Experiment Dashboards to track hypotheses, experiment progress, and user insights, fostering collaboration and informed decision-making throughout the development lifecycle. Through continuous testing and iteration, Experiment Driven Design helps create user-centered software that delivers value while minimizing the waste commonly associated with traditional development methods.

Transcript

Ever get that feeling like when you’re using some software, it’s like they just threw every feature they

could think of at it. Like you’re wading through features you never use, and the important stuff is like

buried totally. And it can feel so overwhelming. You know, you just want the software to do what it’s

supposed to do without all the extra baggage. Exactly. And you know, it’s crazy. I was reading an article

from Info Beans, these software wizards, and they said that 64% of features in enterprise software are

rarely or never used. 64%. That’s like more than half, right? It’s like building a whole house when all you

need is a single room. It’s wild. And I think it often boils down to that old build it and they will come

mentality. Yeah, but like in today’s world, building the wrong thing quickly. It’s still a mess. Absolutely.

Speed without direction is just spinning your wheels. So how do we escape this wasteland of like wasted

carved info. Been seems to have a compass experiment driven design or Ed for short Ed is like a breath

of fresh air. You know what I love about it? It’s not this rigid, step by step process. It’s collaborative,

creative, versatile. You adapt as you go. I do love adaptability. Yeah. So paint me a picture. What does

Ed actually look like in action? Okay, so instead of betting everything on a single idea, you’re making

these smaller, calculated bets along the way. I’m intrigued. Tell me more about these bets. Each one is an

experiment. Could be as simple as a sketch on paper, or as involved as a pilot program with real users,

and the goal of each bet is to validate an assumption. You’re basically saying, okay, we think this is true,

but let’s test it out and see. So it’s about being willing to be wrong. Exactly. You’re framing every

solution as a hypothesis which takes the pressure off. It’s like we’re not married to this idea. We’re here to

learn. That makes a lot of sense. Yeah. So where do we even begin with testing these hypotheses? I

mean, there are so many different types of experiments, right? Info beans talks about a bunch of them.

You’ve got your lightweight options like, you know, paper prototyping, literally just sketching things out.

Love that. Lo fi, but effective. Exactly. And then you’ve got things like Wizard of Oz MVP’s, which

sound way more complicated than they actually are. Wizard of Oz MVP’s. Okay, you have to explain that

way. Basically, you’re simulating the functionality of a feature without actually building it. So like a

movie set creating the illusion without the massive budget? Exactly. You’re behind the scenes, pulling the

levers to give users a taste of what the experience could be like. Genius. So you’re saying you start small,

test your assumptions, and then gradually increase the like, the realness of your experiment? Exactly.

Think of it like climbing a ladder of confidence. Each experiment you run, each bet you make brings you

one rung higher. And by the time you get to the top of the ladder, you’re feeling pretty darn good about

your solution. Exactly, because you validated every step of the way with real data and real user feedback.

And the best part is, you can course correct early on, you know? If something’s not working, you don’t

waste time and resources building it out fully. It’s about minimizing that waste, right? Making sure every

line of code, every design decision counts. Exactly. Now, with all these experiments running around,

things could get messy. How do you keep track of it all? Yeah, it’s easy to get lost in the weeds with all

that data. That’s where the experiment dashboard comes in. It’s your command center for everything, Ed.

Okay, so, like our central hub for making sense of the chaos. Precisely. You’re tracking your hypotheses,

your experiments, and most importantly, your learnings. What worked, what didn’t and why. So it’s not

just about running experiments. It’s about documenting the journey, capturing those aha moments, and

having all that information in one place. It helps teams make smarter, data driven decisions. It’s like in

those crime shows, when they finally pin all the evidence on that big old board, right? But instead of

catching a criminal, you’re like catching insights to build better products that people actually love. Love

that. And you know, speaking of catching things, one article mentioned how this whole data driven

approach can actually wrangle teams into alignment o 100%, especially in bigger companies, right?

Getting everyone on the same page. It’s like herding cats sometimes. Tell me about it. So, are you saying

the experiment dashboard is the magic cat herder? It’s pretty close because it acts like this single source

of truth, right? Everyone’s singing from the same song sheet. No more crossed wires or

miscommunications. So transparency is the name of the game? Exactly. And it’s not just some pie in the

sky idea, you know? Info beans actually gave a really compelling example that case study with the South

American Petrochemical Company. Oh yeah. The one where they used Ed for like, their whole digital

makeover. Wasn’t that like eight weeks to launch a whole new dashboard for their customers? Eight

weeks, which is mind blowing when you think about it, because that industry not exactly known for its

speed, that’s for sure. What I loved about that story was how it just totally busted that myth that Ed is

only for, like, you know, those super agile tech startups. Exactly. If a big old school company like that

can embrace it, anyone can. Proof is in the pudding. So this edX thing, it’s less about the what you’re

building and more about the how. Right 100% the principles there universal software marketing. Heck,

even just trying to optimize your morning routine. It all comes down to testing what you think you know

and learning from every experiment. It’s bringing that scientific method into like, every corner of our

lives. And speaking of science info Bean’s made a big deal about how edX can seriously cut down on

waste and software development. What’s that all about? Remember that 64% of unused features we

talked about all that wasted time, effort, money? edX helps avoid that. I’m making sure every line of code

actually earns its keep. Exactly. Every single design choice has to be justified. It’s like decluttering your

digital closet and getting rid of all the stuff you never wear. I love a good closet cleanout. Yeah, so we’re

talking about intentionality being laser focused on what truly moves the needle. Absolutely. And that

mindset. You know, minimizing waste. It doesn’t have to stop with software. It can bleed into, well,

everything your work, your life, the whole shebang. Streamlining, maximizing impact, getting the biggest

bang for our buck. That’s something we can all get behind 100%. And the best part? It doesn’t have to be

overwhelming. Start small. One experiment, one assumption at a time. Okay, so for our listeners out

there who are ready to, like, dive headfirst into this ed world, what’s the first step? Where do they even

begin? Well, I’d say the first step is like taking stock. What are those assumptions you’re clinging to? The

ones that might be holding you back without you even realizing it? Ooh, I like that. It’s like challenging

your own internal biases. Right. Exactly. Let’s say, for example, you’re putting together this killer

marketing campaign and you’re totally convinced that Instagram is the place to be been there. Right? But

instead of just going all in on Instagram because it feels right, Ed would say, hold on a sec, let’s test that

assumption. So instead of putting all your eggs in one basket, you’re like experimenting with a few

different baskets at the same time. See what happens exactly. Test different messages, different visuals,

different audiences. You gather the data, you analyze it, and then you let that data guide your decisions,

letting the evidence lead the way, which, you know, that could be tough, especially for those of us who

like we love to trust our gut. It’s true. But honestly, that’s where the real magic happens. When you

embrace that experimental mindset, it opens up so many doors. And the beauty of Ed is that it gives you

a structure to work within. You’re not just experimenting for the sake of experimenting. It’s about having

a system, right? So you’re not just running experiments in isolation. You’re capturing what you learn,

iterating and getting better over time. Absolutely. You’re building a culture of experimentation within

your team. You know, everyone feels empowered to challenge assumptions, trying new things, and most

importantly, learn from their mistakes. So it’s less about, I think, and more about let’s find out 100%. And

the more you do that, the more innovative your work will become. It makes me think of that George

Bernard Shaw quote the reasonable man adapts himself to the world. The unreasonable one persists in

trying to adapt the world to himself. Therefore, all progress depends on the unreasonable man. I love that

quote. It’s like Ed gives us permission to be a little unreasonable, to shake things up, and to always be

pushing for something better. Yes, because at the end of the day, that’s what it’s all about, right? Pushing

boundaries, exploring the unknown, creating something truly remarkable. Couldn’t have said it better

myself. So for all our listeners out there ready to embark on your own ed adventures, remember start

small. Identify one assumption, one tiny thing you want to test and just go for it. Exactly and have fun

with it. Experimentation is about discovery and playfulness to love that energy. And on that note, we’ll

wrap up this deep dive into the world of experiment driven design. Thanks for tuning in, everyone. And

until next time, keep those experiments going.