But for systems-heavy games this falls apart. For a game like SimCity or Minecraft, making a proper vertical slice would mean building 70% of the game! That doesn't really help de-risk anything. :). For systems games it's much better to do iterative prototypes, accumulating systems with increasingly longer feedback loops...
(Source: my experience making systems-heavy games :) )
Still I'd say that it does not apply to all RPGs. For example, the recent Divinity: Original Sin games are quite system-heavy, so I don't think it would be possible to have a vertical slice without building most systems. But for Diablo-like games, it would work great!
I only did some level design back in the day, so I don't have much experience with games, but I find this 'prototyping' thing to be hugely valuable in web development and design work I've done. I often just try all sorts of shit (whether front-end or back-end or design), focusing on quick feedback and iteration, and once things coalesce/work/'click', I might just scrap the whole thing and start with a more 'formal' version.
Especially with design stuff I've found that just getting something and then playing around with it works so much better than trying to go for a more formal approach from the start. And making a clear distinction between the 'playground' and 'formal' phase has also helped a bunch.
Finally, I've all but stopped doing the 'Lorem Ipsum' and image placeholder work. If I'm going to 'prototype' a design, it can be a bit messy, but it has to be as real as possible.
It sort of becomes a fractal process as well, where I'll end up with a sandbox zone for each different segment of the game, which then evolve into the production stages for each different area.
It is a moot effort to build out the game until you have refined the game mechanic and the fun aspect. Iterations need to be quick and with as little tech weight as possible.
Even in small prototypes you can find fun that you could have never planned for, and see when something you thought would be fun just isn't yet or work with it to make it fun.
Finding the fun is the most unknown part of a development so it must be in the playground/sandbox and iterated on quickly.
Playtesting is also important but prototyping usually has lots of that from the developer themselves even.
'the classic horseshoe design' - show inaccessible teasers of later areas of the stage near the beginning to drive the player forward
Then I start incorporating them into production levels, build out an intro zone, etc.
The test zone pattern isn't really a conscious decision, but it almost invariably develops in everything that I end up shipping.
I like Mark Cerny though. I wonder if the 'Cerny Method' was used for Sonic 3 (as an aside, though Sonic 3 is a great game, it contains one of the single worst video game UX nightmares of all time — https://www.youtube.com/watch?v=FogRh7CALFY).