Here is a scene that plays out on many website projects. Someone builds a new page in the content management system, tweaks the layout for a week, fixes every spacing glitch, and only then shows it to a colleague. The colleague looks for ten seconds and asks, “Wait, who is this page for?” A week of polish now sits on top of a question nobody answered. Draft page feedback, asked for early, is the habit that avoids this. Let us explain it in everyday language, using the kind of work web teams do every day.
What “early feedback” means on a website
It simply means showing an unfinished page to another person before you make it pretty. In a CMS, that could be a draft post, an unpublished page on a staging copy of the site, or even a rough wireframe sketched on paper. The page does not have to work completely. It only has to be understandable enough for someone to react.
Think of it like a builder showing a client chalk marks on the floor before pouring concrete. Moving a wall at that stage costs a rub of the eraser. Moving it after the concrete has set is another conversation entirely.
Why polishing alone backfires
When you work by yourself for a long time, you stop seeing your own page the way a visitor does. You know where the buttons are, you know what the headings mean, and you know which parts are placeholders. A newcomer knows none of this. So the larger problems stay hidden: the page might target the wrong audience, bury the main action, or rely on a term your visitors do not use.
Small things like spacing and colour are easy to fix late. Big things like “this page should actually be two pages” are not. That is why the order matters. Share first, polish after.
What you can show, in a CMS
- A wireframe. Boxes and labels showing where the headline, the main text and the call to action will live.
- A draft with placeholder text. Real headings, rough paragraphs and “image goes here” notes.
- A staging page. A private copy of the page inside the CMS, ideally with a link only your reviewer can open.
- A rough outline of a template. If you are planning a new page layout that many pages will reuse, show the outline before you code it.
For developers, the equivalent is a draft pull request or a branch with a short note saying what is still missing. The principle is identical: get a reader involved while changing course is cheap.
Whom to ask
Choose one or two people. A colleague from the content or marketing side will react to the message and audience. A fellow builder will react to structure and technical choices. Someone who has never seen the project is valuable too, because they have no background to fill in the gaps.
Avoid sending it to everyone. If ten people comment, you will receive ten different opinions on button colours and no useful comment about whether the page makes sense.
The most important step: say what you want back
This is the secret ingredient. If you just say “thoughts?”, people will comment on whatever is easiest to notice, usually typos and colours. Instead, tell them the kind of feedback you are after. Here are some phrases that work:
- “Can you tell, within five seconds, what this page wants you to do?”
- “Is anything missing that a first-time visitor would look for?”
- “Please ignore the styling. It is a rough draft.”
- “Does the order of the sections feel natural?”
These questions point the reader at the big decisions and away from cosmetic ones. They also make it easier for the reader to be honest, because you have said out loud that the page is not finished.
A simple example
Say a small business owner wants a services page. The first draft is three headings and a few lines under each. It is sent to a friend with the note: “Rough draft, only checking whether the services are in a sensible order, please ignore the wording.” The friend replies that the most common request, the one visitors usually care about, is at the bottom. Moving it to the top costs two minutes. If the page had been built, tested and approved before anyone looked, the same move would have meant reworking menus, links and sometimes the design itself.
Writers on the topic often stress that a page’s structure should be planned before building starts; a planning walkthrough aimed at business owners before coding starts makes a handy companion read. And since first impressions depend on how a page opens, a look at how homepage design shapes what visitors think explains why the top of your draft deserves the most attention in a review.
A developer’s version of the same habit
Teams that build themes, plugins or custom templates have their own way of doing this. Instead of finishing a feature and then asking for a code review, they open a draft change early, with a description such as “this adds a new landing-page template; the approach is not final; I would like a view on how the fields are structured.” A teammate can then say, “These three custom fields could be one repeatable block,” before the work spreads across a dozen files. The rewrite is small because the question arrived early.
The same principle applies to a content model. If you are about to create a new content type, sketch its fields on a single sheet and show it to the person who will fill it in every week. Editors spot awkward fields instantly, such as a required box they will never have data for, and removing a field from a sketch is far easier than removing it from a live database with hundreds of entries.
How long should the review take?
Short. Aim for a quarter of an hour from the reader. If the draft needs more than that to understand, it is probably too long for a first look, and cutting it down is itself useful work. Ask for a response within a couple of days so the project does not stall, and settle beforehand what happens when nobody replies. One polite nudge is fine, after which a different reader takes over.
What to do with the comments
Collect them in one place and sort them. Put anything about structure, audience or purpose first. Then content, such as missing information. Finally, cosmetic matters. Fix them in that order, because a structural change can make some content and cosmetic comments pointless.
If two people say the same thing, it is almost certainly a real problem. If only one person says something and you disagree, you can set it aside, but write down why. A short note beside each comment, such as “changed”, “not changed because X”, keeps the process honest and helps you explain decisions to a client later.
A brief word on events and local content
Sites that promote local activities, like workshops or talks, often need a quick check on whether a page matches what readers expect. One outside example of how an events-focused site is organised is KeralaOrbit, a Kerala site with browsable event listings, places to hold events, a forum and a blog. Studying how a working site like that arranges its sections gives a reviewer something to compare against your rough page, and it reminds everyone that visitors usually arrive wanting to find one thing quickly, then leave.
Things to avoid
- Waiting until it looks good. That day arrives after the expensive mistakes have been made.
- Explaining while they read. Let the page speak. Confusion is information.
- Arguing with comments. Thank people, collect the remarks, then decide.
- Asking too many people. One or two readers is plenty.
- Skipping the question. Always say what you want feedback on.
Try it on your next page
- Create the draft page or wireframe and keep it rough.
- Jot a couple of lines on exactly what you need checked.
- Email it to a pair of handpicked readers and give them a few days.
- Sort the replies: structure, content, cosmetic.
- Fix in that order, then polish and publish.
It takes less than an hour overall, and it routinely saves days. The next time a page is almost ready and you feel the urge to refine one more detail, send the draft out first. The question you get back will probably be more interesting than any padding adjustment.