A layout is a set of decisions about importance. Design it before the argument is settled and those decisions get made by column widths and module sizes. Write what each page has to establish, and in what order, then let design express a decision instead of making one.
The pattern
The website project starts with a sitemap and a set of page comps. The science content is described as “TBD, from the deck.” Design proceeds. Six weeks later the layouts are approved and the real content arrives.
It does not fit. The platform explanation needs four steps and the module was built for three. The mechanism figure needs a caption longer than the design allows. The pipeline has two programs at the same stage that the layout implies are sequential.
What follows is not a content problem being solved. It is a design being amended, repeatedly, by people who are now protecting a layout rather than an argument.
Why it breaks
A page layout is a set of decisions about relative importance. How much space something gets, what appears before what, what is above the fold, what is a heading and what is a caption — those are all statements about hierarchy.
When the layout is designed first, those statements get made by default: by column widths, by how much lorem ipsum happened to be in the module, by which section the designer built first. Then the real science is fitted into decisions that were never made about it.
The narrative loses in every one of those negotiations, because the layout is the thing that already exists and looks finished.
What changes
Settle the argument before anything is drawn.
Write what the site has to make an investor understand, in order. Decide what leads on each page and what supports it. Decide which scientific relationships need sequence, which need comparison, and which are single facts that can sit in a sentence. Decide what is coming off the site entirely.
That output is not copy. It is a structure: a ranked list of what each page has to establish, and in what order. Design then has a brief that is about meaning rather than about filling modules.
The practical result
Layouts get built around the shape of the actual argument, so fewer of them need a second version.
Scientific content stops being an attachment to the design and starts driving it: a mechanism that needs four states gets an interaction, because the structure said it needed four states before anyone drew a box for it.
The review cycle changes too. Stakeholders argue about the structure while it is still cheap to change, rather than about a comp that took two weeks and now carries everyone’s expectations.
Design is very good at expressing a decision and very bad at making one. Give it the decision first.
