I found the KotS method quite good. It put the encounter description a two-page thread (complete with stat-blocks, tacitcs and similar stuff), but (unlike this module), it kept in the flow of the adventure. I very much prefer the KotS approach. I don't like reading up on some story, see a reference to an encounter and then get back to the story. I want to know what happens in the encounter and how it will work into the flow of the story.
The "wasting" space stuff is good, though. Try to ensure that all relevant information is on one double page, even if this means that the previous and next page have some white space.
That's what generally love so far on the 4E Core books - the layout is really so much more helpful. Especially since I still remember how we basicall had our first 3.0 Total Party Kill - the DM send us against a single Giant, and he Greater Cleaved us in one and a half round - all thanks to the fact that the DM slipped into the wrong row, thanks to the page-spanning stat-block of the 3.0 DMG.