Delivering value in design vs. engineering

Ken Norton published something the other day called 10x not 10%.

If you’re not familiar with Ken, he was a long time product manager at Google and is now a partner at Google Ventures where he works directly with their portfolio companies on engineering and product. 

In the piece he talks about Kodak, and the concept of risk in product development and design. It’s worth reading in full (including the references) but it got me thinking about something else: how online platforms weigh design vs. engineering. 

Early stage companies often struggle to balance the two. A good core product that delivers value is worth a lot even if it’s not sexy. But, of course, you’ll eventually need good, clean UI / UX design in order to deliver your product to a larger audience. There’s value in that, too. 

My experience is that the relationship between engineering and design works on a spectrum, but that spectrum is very different based on whether you’re going for 10x or 10%. If you don’t know which you’re aiming for it can really mess with your product. 

More simply, if you are providing 10x value via engineering you can get away with design being clunky, sometimes for a very long period. But if you’re aiming for the 10% increase in value, than design + user experience + on-boarding are most of the battle.