Is simplicity the main key for a successful MVP?
Do you think simplicity is the main key how to achieve success with your MVP?
Some context: I am building a job board for Symfony Developers. I ran into a problem, how to encourage recruiters to post on a new job board. I wanted manually to add few offers as they would do it.
But... My "create job offer" form has about 20 fields to fill. For me it became boring, so it became obvious: recruiters won't waste 10 minutes filling my ultra-big form.
So today I have cut out over 60% of fields in my 'create job offer' form
Simplified version:
Previous, ultra-big form:
In a few days, I am going to upload it to production and test the simplified version. We'll see if that help me gain some users
The key to an mvp is solving a customer's problem. Might be simple, might not.
I would call up recruiters and see how you can help them. That may mean talking to them on the phone to get their info and you filling out the form. It may mean you find some people you can just send potential leads to and they don't interact on your website yet. Figure out exactly how to help them and do it. That's an MVP.
Your focus must be your customer pain point. This pain point must be so hurtful to your customer that he will be ready to throw money at you if you can solve it.
If you want to know what it is just look for your potential customer (recruiter of Symfony Developpers). You find the place online where they gather and ask them this simple question: "When it comes to look for the best recruite, what's your biggest problem"?
Now you are no longer building something based on your understanding of the problem but based on what your ideal customer told you. You can even add something like "What do you do actually to tackle that problem"? Jus to know if there is a solution to that problem that they are currently using.
Now you can focus on just that problem and the perfect solution for it.
Hope it helps
Hey SMK!
In past I've worked on similar challenge. Where we delt with 40+ input fields.
My learnings form A/B testing was that you can also hide the complexity without removing it completely. And it is not the quantity of filds that's discouraging but everything presented at once, overwhelms the user.
For your case I'd like to give you few tips.
Hope it helps.
Good luck.
Wooow, I think it's a great improvement on ux, congrats!
Do you have metrics to see how this change goes? It would be cool to see the results
Right now I don't have any, but I'll set up some analytics for future changes, to know the results and do not make changes 'blindly'.