What follows is an invented tale that blends habits common to web teams. Nobody in it is real, yet anyone who has run a website project will recognise the setting: a redesign that kept growing, a stakeholder list that kept expanding, and a launch date that kept slipping. The thing that unstuck them was a single sheet of paper, not software.
The situation
A regional training provider, which we will call the Northgate Academy, had a content management system that had grown organically for years. Its marketing lead, a developer, a designer and a part-time editor were asked to refresh the site. The brief at the start was a few lines in an email. By the third week, it had turned into a shared folder of mood boards, a spreadsheet of pages, and a chat channel with more than a hundred unread messages.
The symptoms were clear. The designer revised the homepage three times because feedback contradicted itself. The developer built templates that had to be reworked. The editor did not know which pages to migrate first. Everyone was busy, and nothing was finished.
The turning point
At a tense review meeting, the editor asked a deceptively simple question: could someone write down, on one page, what exactly we are trying to ship by the end of next month? Nobody could do it on the spot. That, she pointed out, was the real problem.
The team agreed to try. The marketing lead drafted a page, the developer and designer marked it up, and the group argued over every line for an hour. By the end, they had something they had never had before: a shared statement of scope.
What went on the page
The summary used five headings, and each one forced a choice.
Purpose
One sentence: refresh the public site so that prospective learners can find a course, understand what it involves and enquire in under two minutes. Anything that did not serve that sentence was off the list.
Scope in, scope out
Two short lists. In: new homepage, course listing template, course detail template, enquiry form, and migration of the most visited pages. Out: a blog redesign, a members area and a new search engine. Writing the second list was the hardest part, and it removed about half of the arguments.
Decisions already made
The CMS stays. The visual style follows the approved palette. The enquiry form sends to one shared inbox. Listing these stopped the team from reopening old debates.
Risks and open questions
Three items, each with an owner: content for the course pages was not yet written, the form needed a privacy check, and the hosting plan might need an upgrade.
Next steps
Four dated actions, each with one name against it. The page ended there.
What changed in practice
The effects were visible within days. Feedback became more specific, because reviewers compared work against the page rather than against private expectations. The designer stopped redoing the homepage once the purpose line settled what the page was for. The developer queued template work in the order the scope list implied. The editor knew precisely which pages to migrate first.
Equally important, the page gave the marketing lead a way to say no politely. When a senior colleague asked for a members area, she did not argue. She pointed to the out-of-scope list and offered to schedule it for a later phase. The request was parked without friction.
The lessons the team took away
- A scope that cannot fit on one page is not yet understood.
- The “out” list matters more than the “in” list.
- Recording decisions already made saves more time than any tool.
- Each risk needs a named owner, or it belongs to nobody.
- The page is a living document, with a date at the top and one person responsible for updates.
Teams that plan before they build usually go through a similar exercise, and a how-to article on sketching out a company site before any coding begins covers much of the ground that the Northgate team had to rediscover the hard way. Another useful companion is a guide to the core pages every business site tends to need, which would have shortened their scope debate considerably.
The after-story
The redesign shipped a few days later than the revised date, but it shipped, and the team’s mood improved sharply. When a second project came along, they started with the one-page summary on day one. The kickoff meeting that used to take two hours now took forty minutes.
They also adopted the habit for incidents. When a form stopped delivering messages for an afternoon, the developer wrote a short page afterwards: what failed, who was affected, what was fixed and what would be monitored. It took ten minutes and spared the group a long email chain. That practice is borrowed from operations teams, and one source of teaching material on it for Chinese-speaking audiences is DevOpsSchool China, which the team’s developer had bookmarked as an example of a site that offers training and cloud-migration support.
Why this works for CMS projects in particular
Content management projects are prone to scope creep for a structural reason: every page is a small project of its own, and every stakeholder owns a few pages. Without a shared boundary, the list only grows. The page acts as that boundary. It also helps with handover, since a new editor or a freelancer can read it in five minutes and understand what the site is meant to do.
Marketing-focused pieces such as the one about service pages that convert browsers into clients come at it from the opposite direction: pages should be built for a purpose, and the purpose should be written down.
How to try it on your next project
- Draft the one-page summary before you open a design tool.
- Get every key stakeholder to read it and say yes or no to each line.
- Record the out-of-scope list as prominently as the in-scope one.
- Assign an owner to every open risk.
- Date the page and revisit it at each milestone.
The Northgate team is fictional, but their experience is not unusual. The shift they made was small in effort and large in effect: they stopped treating the project as a pile of tasks and started treating it as a decision that could be written down. Once the decision was clear, the tasks sorted themselves.