Taking pride in ignorance First and foremost, concentrate on your strengths. Put yourself where your strengths can produce results. Second, work on improving your strengths. Third, discover where your intellectual arrogance is causing disabling ignorance and overcome it...First-rate engineers, for instance, tend to take pride in not knowing anything about people. Human resources professionals, by contrast, often pride themselves on their ignorance of elementary accounting or of quantitative methods altogether. But taking pride in such ignorance is self-defeating. Go to work on acquiring the skills and knowledge you need to fully realize your strengths. Peter F. Drucker, Managing Oneself ignorancearrogance
What happens to user experience in a minimum viable product? An Article by Ryan Singer signalvnoise.com "Feature complexity is like surface area and quality of execution is like height. I want a base level of quality execution across all features. Whenever I commit to building or expanding a feature, I'm committing to a baseline of effort on the user experience." There’s a distinction to make: The set of features you choose to build is one thing. The level you choose to execute at is another. You can decide whether or not to include a feature like ‘reset password’. But if you decide to do it, you should live up to a basic standard of execution on the experience side. Features can be different sizes with more or less complexity, but quality of experience should be constant across all features. That constant quality of experience is what gives your customers trust. It demonstrates to them that whatever you build, you build well. Minimum Awesome Product qualityproductsfeaturesux