Our mvp’s scope was ridiculous.

Photo by Chris Henry on Unsplash

Ideas, Projects, Business models and the Brainstorming of actual solutions, alongside the operations, features, resources, time, effort, experience and budget are all things that come basically straight away. ‘How will we do?’ ‘What’s it going to cost?’ ‘Do you have the experience or the know how to get started?’ But then comes the timeline and product features of the item you plan to actually build. You have the vision and expectation of being the most amazing product on planet earth from day one, and, you think it’s all possible within the next month.

Scope cutters get a bad rap, that’s for sure! It’s seem as if you’re taking shortcuts or not driven enough to build the entire product solution. However it’s just so important to consider what you’re actually building, before you begin. A lesson, I wish I had read about or knew a little earlier. At Instant, we had plans to introduce spectacular, game changing features from day one. We were to set ourselves massively apart from anything or anyone in the accelerated checkout space, and as a fact, thought we could pump this product out rocket speed. Whilst planning all this wasn’t a bad thing, as, we most definitely have a pretty spectacular long term roadmap, we had to consider what our core product offering was, to fast track our speed to market, and hence, gaining our first customer. All on the limited resources, budget and time we have on hand.

We’ve all experienced a time where plans get changed. It’s frustrating, especially under pressure, or you feel as if you’re not performing enough. What’s too remember here is that this is actually of benefit. We didn’t need full consumer dashboards, allowing such ‘extra’ features. We just needed a simplistic dashboard, enabling a buyer to edit their information. We didn’t need to build an entire merchant and admin dashboard. These have already been built before, so instead we’ve partnered with one of the worlds largest payment gateways to work alongside us on this. So we removed them. When trimming scope, it’s important to consider and remember your overall outcome. If it’s to launch an accelerated checkout in our case, it was obviously super important to ensure this action could still be performed, as the priority.

You should be encouraged, no matter the size or scale of your product to reduce your scope, especially in such early stages. Less complexity will give you and your team a clearer roadmap, with focused areas of intense development sprints. You’ll feel fulfilled and accomplished, completing what you planned out to do within time. Speak with and get some experienced people apart of the conversation!

Clubhouse is the perfect example of cutting scope, or, not being perfect from day dot. Product design, support, user experience, etc were all pretty ordinary at their launch, however, grew to millions and millions of users with these ‘not so very modern’ features. I still don’t even think they’ve even finalised a company logo!

Don’t destroy your overall outcome, and stay focused towards your end goal — but don’t be afraid to cut some things out!

17 yr/old Founder of Instant. Here I share my startup life, journey and fun stories!