How do you build a bare minimum feature?
&gt;<i>So far your instinct as product designer&#x2F;manager&#x2F;engineer might be to take what customers say they want at face value.</i><p>That would be the worst way to go about building anything. Taking solutions from customers as opposed to problems to identify jobs-to-be-done and reasons for non consumption isn&#x27;t something someone who knows how to build products does.<p>The question then becomes how does someone who generally knows how to build the right things build the bare minimum feature, the original question and title of the post, given the constraints on time and resources cited in the first paragraphs.<p>One can do several things. For example, writing the description and code examples for a yet to be library and shop it around, see if it makes sense, then write the library.<p>That&#x27;s what I did for example with this library: <a href="https:&#x2F;&#x2F;pypi.org&#x2F;project&#x2F;bmc" rel="nofollow">https:&#x2F;&#x2F;pypi.org&#x2F;project&#x2F;bmc</a> after shopping it around here: <a href="https:&#x2F;&#x2F;github.com&#x2F;minio&#x2F;minio-py&#x2F;issues&#x2F;829#issuecomment-658703470" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;minio&#x2F;minio-py&#x2F;issues&#x2F;829#issuecomment-65...</a><p>I also do that for internal tools, libraries, SDKs. I&#x27;ll send client code around and see if it makes sense to engineers. I also had non engineers who never coded use libraries to do something useful. I just give them a laptop and docs and see how they use the thing. If they can do it, I know programmers can.<p>To get back to the original problem, prioritizing can lead towards minimal features. We have a section called &quot;Instances&quot; in our issue templates. If a feature issue does not have several instances where the problem manifested for several people, we just won&#x27;t do it. We need concrete examples of a problem being frequent and expensive &#x2F; high impact (loss of work, or prevents work in the first place).<p>For example, I&#x27;ll look at the analytics for our internal platform and see that my colleague who we built the thing for is not using it. Why, we ask. It turns out the Docker images are too large and take a lot of time. He loses patience. They contain several libraries that he does need.<p>We built a minimal image that can get him to start after 30 seconds instead of 2 minutes, and we saw usage increase.<p>Yesterday, I saw he was giving a demo using his local environement, not the product. I&#x27;ll ask why. What&#x27;s wrong. What sucks. Why did he use his laptop instead of the platform.<p>The general sentiment of the article is sound. Always observe, ask questions, look for the underlying problems and how frequently they happen, how expensive they are (as in what are they doing to solve that, is there someone working on it, does it cost opportunities, etc)