While I see the value of that advice (longer flow periods), for academic or technical writing it is often impossible. It might work for fiction or punditry, but detailed analysis requires frequently looking to citations and notes.
This does not work very well for me; if anything, I like to have an outline and miscellaneous file open. In fact, I meant to write a short post with screenshots of my current workspace embedded, but by accident I went away an hour ago and am back with a much larger post discussing many aspects of the article in question that just so happens to have some screenshots of the way I've been working embedded, along with explanations. Sorry! http://jseliger.com/2011/08/11/how-to-be-a-faster-writer-don...
If the plan is really high level, or embedded (i.e. topic intros), maybe that's different.