An early version should do enough of the real job to teach you something important. Strip away features that do not help test that job, while keeping the conditions necessary for safe and honest use.
A fictional reporting template needs coherent fields, clear units and one completed example before a new user can evaluate it. It may not yet need dashboards, automation or several colour themes. Removing essential explanations would make the test less informative rather than more efficient.
Name the uncertainty
Are you testing whether people understand the method, whether the output supports a decision or whether they would pay for implementation help? Choose a version that exposes that uncertainty.
Tell testers what is incomplete and how their information will be used. Keep the test audience proportionate to the work's readiness. A private trial may be appropriate before public release.
Improve from use
Record where people struggle, what they skip and what they unexpectedly find useful. Separate a missing feature from a missing explanation. You may solve the problem with a better example instead of a larger product.
Set a point for deciding whether the idea deserves another version. A first useful version should lead to a clearer decision. It should also be complete enough that the person helping you is evaluating actual work rather than filling in the whole design on your behalf.