Minimalism in technical documentation states that we should only deliver info that the user needs. But how can we know what each individual user already knows (and does not need)? The answer is: we cannot. And this is why we should use progressive disclosure techniques to optimize the help we offer to our customers, so that each individual customer can decide for himself whether more info is needed or not, and on which aspects more info is needed.
There is one important catch: Implementing progressive disclosure can be a lot of work and be too costly to do. The solution to this budgetary problem is to use a well-defined structure in your content (preferably DITA) and an XSLT that automatically adds the required hooks and handles (triggers and targets) to make progressive disclosure work.