The fidelity of a deliverable is always a tricky proposition. The business need to standardise a system is always going to be a bother, especially to solely fill spaces in a spreadsheet. I like exploring the possible fidelity of the deliverable, and seeing what I can get away with. If I can explain and convince the need for a loose assortment, especially when it goes against company policy is a great use of an hour.
Some projects only need a loose prototype, others, a rigid user flow map and a few key animations. High resolution prototypes with state transitions - photoshop comps with built in transition animations. Others need a very broad overview of the app but with an indication of a branding style guide to give the tone of the app. Standing in front of a white wall with coloured squares loosely stuck to it and walking back and forth with a Draper-esque assuredness and a fat sharpy and let someone else work on the details.
Finding the right mixture is important, and usually pretty obvious once the texture and grain of the project is evident. While we zoom in and out in our work - as part of our work - we also need to be zooming in and out across time. Grabbing possibilities that the finished project might entail and sprinkling them together, seeing what sticks. The perfect deliverable is complementing layers of time, quality, and interaction. Bouncing up and down the fidelity stack.