In your goal setting, you need to define what you are hoping to learn. You're going into an MVS process knowing that you're going in to learn something. So define exactly what it is that you want to learn.
Step 2: Forming Theories
Rather than just trying to create one theory around how you're going to reach this goal and getting consensus around that, embody more of a design thinking, divergent approach to thinking. Do this if you're doing this on your own.
If you're doing it as a group, have everyone time box an hour or a day at the most, and come up with as many ideas and as many theories around how you might reach that goal as possible and do that in a way that is open. Don't be judgmental. The goal here is to get as many ideas as possible. So it's really about quantity over quality at this point.
Then you have a huge list you can work off of and as a group or as an individual, you can then reflect, maybe you take a day to reflect on those or a week, depending on how urgent this is for you. You go through and figure out the top three or top five theories or ideas that you bet are the most likely ones to pay off. So winnow it down and converge into the highest probable ideas that you think are going to work.
Step 3: Act Swiftly and Decisively
Probably the most important step of this entire framework is to act and to act swiftly and decisively. The real beauty of this is that we are not talking about years or months to get to this point of action. This approach works because of your ability to act quickly and to get real world reactions to your ideas as quickly as possible. If you don't act quickly, then you're basically just doing a half-assed strategic plan at this point. So that's not helpful either.
So act swiftly. Get your ideas into the world, test them, get them into the market, get customer feedback or client feedback or supporter feedback depending on the type of idea it is.
Step 4: Evaluate and Iterate
If you're testing those ideas, you have to have some kind of way to tell if the idea is working, if it's working to the extent that you hoped it would, to even score these different ideas amongst each other or against each other to figure out: should we continue three of these five ideas? Are none of them good? Is one obviously the best? These are all outcomes that can happen.
In your evaluation and iteration, define one of three outcomes of your experiment:
- We kill it, we're never doing this, it's gone forever. It failed.
- We nailed it. Let's keep adding to it.
- Let's shelve this. It's not right right now, but it has potential. We may come back to it. We're not ready for it yet for one reason or the other.
You need to define those boundaries for yourself. How do you know you're going to kill that thing? Or how do you know you're going to pour more fuel on it?
So goal setting, forming theories, acting, evaluating, and iterating based on that data. That's a pretty simple framework, but the power of it is in its simplicity and in its ability to get you into action as quickly as possible.
An Important Caveat
We don't think this approach is right for everything. Although we do think it can be used for a lot of things.
Let's talk about another Silicon Valley adage: Move fast and break things. This comes out of Zuckerberg and Facebook. That is not an appropriate culture for a lot of social impact work.
Let's just be clear — especially when we're talking about causes and issues where people's lives might literally be on the line — you don't want to move fast and break things when the things that are breaking are people's lives. And we would never suggest using this approach for something like critical support or infrastructure. But it could be used for a new communications plan or an iterative improvement to one of your programs or a new section that you want to build into your overall marketing strategy.
We want to acknowledge that an organization has to be careful about this MVS framework or applying just more broadly Silicon Valley, startup, or lean startup methodology to social impact in general or even design thinking to social impact.
Understand Your Audience's Readiness
When the move fast, break things mantra was introduced, the internet was a different place. Especially as early adopters of the internet and social media, we were ready. We were hungry to work with products and use products that weren't perfect, and we were ready and willing to give feedback on what we liked and what we didn't like.
It's different now, even in the tech space. You may have noticed that for all these, for your iPhone and for different software you use, there are beta programs. But they're always opt-in: do you want to be a participant in this version of our product? It's not done yet. It's still buggy. And you're basically signing up, saying you're willing to give you feedback. We think that exists for a reason because you can't just ship unfinished products to the masses anymore.
If you put an app on the App Store tomorrow that's not complete, you're going to get crushed with bad reviews and your product, your service, or your company is dead. So it needs to be ready and be valuable when you launch it.
In some cases, the same thing goes for a minimum viable strategy. You need to know if the audience you're testing this with is ready to work with an unfinished strategy. Maybe you're shopping this with stakeholders who know you really well or understand where you're trying to go, but are willing to think creatively with you and operate with this less than perfect outcome or this less than perfect product.
You really do need to be honest with yourself if you are employing the minimum viable strategy. Who is actually seeing this and are they ready for it?
Strategic vs. Tactical Applications
Let's apply the MVS framework to a communications or a marketing application.
Let's say one of your goals is to increase engagement on your social media posts. You might start an MVS framework and identify that goal, come up with a huge variety of options around how you might do that. And one of your ideas might be that you’re going to test more polarizing hooks in your content. Or maybe not polarizing hooks, but more just enticing curiosity-driven hooks in your content.
You don’t need to tell people you're doing that in this case because — what's the downside? If a post flops, the implications are so minimal, there's no need. You're likely not going to create any bad taste in your user's mouth or your supporter's mouth by doing this. You have to right size this and determine the implications if it doesn't go well.
What if your organization decides that there's a strategy here? Let’s say you want to become content producers as part of your marketing strategy. Part of our outreach strategy is going to be producing high quality content. How do you test the production of a unique piece of content that you're distributing via email in a way that doesn't set the expectation with your audience that this is what you're doing now?
Maybe you release this piece of content to a subset of our audience who you know is willing to consume it with an open mind and give you feedback on it. They are going to validate whether or not a content production role is the right strategy for your organization as opposed to AB testing on an email campaign, which is also valuable, but it's a much smaller, more tactical, tightly scoped, low downside, that kind of thing.
Common Pitfalls and How to Avoid Them
Shiny Object Syndrome
Let's talk about other caveats to this framework and maybe some near enemies or traps to avoid. There’s something we can speak about from experience — shiny object syndrome.
We’ve seen a lot of founders and especially executives have this. It's common to people who get really excited by new things and new programs and new ideas — sometimes to the detriment of other really important activities and attention that time should be spent on.
This is something that has to be kept in check, and it almost sounds a little contradictory to the MVS framework because there can be this shiny object syndrome that can come into play, and then not testing a lot of shiny object ideas out.
This is something to keep in check and be careful about with this framework. When you see MVS in use and see what the potential power of it can be, you might be tempted to just start to apply it to everything. Then all of a sudden you're losing track of what you really should be focusing on — some of your core responsibilities as a leader or even as an organization.
Communication and Capacity Issues
Some potential pitfalls for social impact leaders who are considering something like this include:
Not communicating clearly enough to the whole team things like the learning outcomes or the decision-making triggers. There may be a little bit of an inability for your team to communicate what these new initiatives are to your audiences in a way that is positive and uplifting. There needs to be more communicating about the reason for this experiment.
Not evaluating well enough the team's ability to do the iterating and the capacity to actually do the iterating once they were up. If you're going to take this approach, you have to be sure that you have the team capacity to do the iterating that you've promised to do.
Step four in the MVS framework is: Evaluate and Iterate. Not just evaluate.