Very much agree with this approach / philosophy: reduce scope (i.e. focus), go deep, ship on time, and ship frequently. Pretty common philosophy these days, but it’s very hard to actually do it…so tempting to keep adding features.
A good idea in general, but I prefer to just build a working prototype instead – accomplishing the same thing but less of a time sink. This depends entirely on the size of your team and the skillsets involved, however. In my case, I’m not that good at Photoshop or Keynote, but I’m pretty quick with HTML & CSS (largely thanks to SASS).
Some good points, the key one being that you shouldn’t need textures and depth to make your product easy-to-use:
“Your product is easy to use because you designed information to be easy to find, because it’s in the exact place the user is looking for it, because your text is clear and easy to read, because you crafted a user a flow that pulls them through the process seamlessly.”
Good read all around, although I’m probably still going to use a bit of subtle depth on my next project.