It’s about building a version of a product with just enough features that meet a customer’s needs, that they can give feedback on, which will shape the next version.
Benefits of this approach:
- It’s faster to build the ‘smallest’ version of a product rather than the final one.
- Getting early feedback means the customer inputs into the design, so they get a better quality product at the end.
- Reduces risk and saves time spent fixing issues afterwards.
So that’s the MVP concept. Want to apply it to comms? I’d recommend it! Try the worked example below. And also see our other posts: #1 sprint, #2 backlog.
Example
First step, tell your stakeholder/s you’re trialling an MVP approach to improve the way you work together.
Design a comms or a plan that has just enough content/activities that meet their needs, that they can give feedback on, which you’ll use to shape the next version.
Benefits of this approach:
- It’s faster to draft the first version rather than the final polished article or fully populated plan.
- Getting early stakeholder feedback means it’s more likely to be correct and relevant.
- Saves everyone time and energy through:
- Fewer rewrites
- Ongoing inputs so no need for lengthy reviews, so quicker sign-off.
Give it a try! Let me know how you get on! 🙂