It isn't easy to create a startup when the team has various visions of how it should be designed, namely, what type of functionality and visuals should be in the MVP.
When the euphoria of launching a new product overpowers the mind, you come up with crazy ideas, like the idea that you need all the functionality in the world and the most beautiful design ever. Or, on the contrary, we'll do it poorly because speed is the key.
I want to show you how to deal with it properly.
Social platform — Product design case study
When I joined the team, I knew they had MVP design and the developers started working on it two months ago.
But the project design counted 275 screens. Too many for MVP, huh?
Perhaps it might seem that the product had a complete design, but:
<aside> 😡 I could not pass any user or technical scenarios from the start till the end. The flows broke off at completely incomprehensible and illogical interface elements.
</aside>
The more questions I asked, the more questions I had. But one thing was clear — nobody could clearly understand 100% the logic of the design mockups, even the one who designed them.