This is a post by Emiliano Villarreal who is our “designer” at Spark59.
One of the top questions I get when helping entrepreneurs, especially those who have not achieved product/market fit, is “How much should I invest into the design of my… landing page, MVP, smoke-test, pitch deck,… etc.” The commonly cited answer is that “it depends.” But it depends on WHAT?
Calculating the right level of form in relation to function is one of the longest running debates across all the disciplines of design. In simple terms, it’s deciding the balance between the utility a product provides (function) and the beauty of it (form). As the classic example below taken from the Universal Principles of Design book shows, focusing heavily on one area greatly impacts the end result.
For a Startup
When discussing this dilemma for Lean startups I like to make the terms more contextual – function becomes features and form becomes design.
Feature is what solves the problem(s) your product is targeting. As an example, if file sharing is the problem the feature could be software that automatically syncs files (Dropbox) or software that uses the power of multiple seeds for fast distribution (p2p).
Design then for a product is its visceral form and how the interaction between the features and user occurs. Sticking with the file sharing example, the design components could be a simple email-like interface (Yousendit) or traditional OS integration (Dropbox).
Why this gets risky
Most startups in the beginning face a limited runway for becoming sustainable. Given a finite amount of time & money, most prioritize features at the expense of design.
Which seems logical as a product that fails to build strong features essentially provides little value to the customer. If the features aren’t compelling, it is likely that customer retention will be low, referrals will be non-existent, and there isn’t much prospect for growth.
On the flip-side, a product that fails to invest enough in its design might suffer from perceptions about quality, frustrations from usability, or simply fail to get a customer’s attention. This renders any value derived from features moot.
The catch is under investing in either one can kill the startup. So the question is not omitting one at the cost of the other, it’s finding the minimum needed for both.
A different approach
Just like there is a minimum feature set that must be defined to build your MVP, there is a minimum design level that must be reached for every product to be effective regardless if it is a landing page, smoke test, or paid app.
Where most people are afraid that a MVP means constructing a half-baked product, I find many people fear minimum design level means a slick design with fancy controls. Far from it.
Minimum design level is the basic design components needed to make your features or content effective in delivering their purpose.
The important point is this minimum level of design should not be decided by how much the startup can afford to build but rather by how much is needed by the customer.
It’s a critical distinction that requires a shift in thinking but provides the path for answering the “How much” question. The good news is it’s simple; it starts with understanding your customer segment.
In the next post, we’ll dive into how a startup baselines their minimum design level while using Lean principles.