$100 Website Offer

Get your personal website + domain for just $100.

Limited Time Offer!

Claim Your Website Now

Splitting a Website Rebuild Into 15-Minute Steps, Explained

A website rebuild is one of those projects that everyone agrees must happen and nobody knows how to start. The old site is slow, the design looks dated, the content management system has become a maze, and the plan lives in a long document that no one has opened since the kickoff meeting. If this sounds familiar, the cure is not more planning. It is smaller steps. This guide explains, in plain language, how to split a website rebuild into fifteen-minute steps that a small team can finish between meetings, and why that makes the project easier to start, easier to track and harder to derail.

What “a step” means here

A step is a piece of work with one owner, one result and a size of about a quarter of an hour. The result matters most. It should be something you could show a colleague: a page list on a sheet, a screenshot of a layout, a set of redirects written down, a paragraph of copy saved in the right place. If the result cannot be shown, the step is too fuzzy, and it will tend to swell until it eats an afternoon.

Why fifteen minutes? It is long enough to do something real and short enough to fit into almost any day. It is also short enough that nobody needs to be in the right mood. A rebuild asks for plenty of decisions, and decisions are easier when the cost of getting one wrong is a single small step rather than a week of work.

Why rebuilds stall in the first place

Rebuilds stall for three practical reasons. First, the scope is blurry: “new website” can mean a fresh coat of paint or a full change of platform. Second, the work is spread across roles, so design, content, development and approvals each wait on each other. Third, there is no obvious first move, so people drift towards whichever task feels least uncomfortable, usually something visual, and leave the structural work for later. Slicing the project addresses all three. It forces the scope into a list, it labels who owns each step and it hands you the first move in black and white.

Slicing a rebuild, layer by layer

Layer one: the workstreams

Divide the project into five or six streams. A typical split is structure, content, design, build, testing and launch. Write each on its own card or row. At this level you are not planning anything, only naming the territory.

Layer two: the deliverables

Under each stream, list what has to exist when the stream is done. Under structure, you might have a page inventory and a navigation sketch. Under content, you might have a rewritten set of key pages and a list of pages to retire. If you are not sure which pages a business site should carry, the structural guide to the pages a company site cannot do without offers a helpful starting checklist.

Layer three: the steps

Finally, cut each deliverable into steps of a quarter hour. A page inventory, for instance, divides into: export the current page list, mark each page keep, merge or retire, group the keepers by purpose, flag pages with no clear owner, and write one line about the purpose of each kept page. Each of these is a quarter-hour job, and the sixth might need a couple of repeats. Work through every deliverable this way until nothing on the list is bigger than a sitting.

An example week

Here is how a small team of three might run the first week of a rebuild, with each person giving a quarter hour or two a day.

  1. Monday: export the current page list; mark each page keep, merge or retire.
  2. Tuesday: group the keeper pages into five or six sections; sketch a navigation on paper.
  3. Wednesday: write down who owns the words on each key page; list pages with no owner.
  4. Thursday: gather the logos, photos and brand notes that already exist into one folder.
  5. Friday: review the week’s four results together in a short call and choose the next five steps.

By Friday the team holds a real page inventory, a navigation sketch, a content owner list and a folder of assets, all produced without a single long workshop. That is far more concrete than most kickoff meetings manage.

Handling the awkward parts

Some steps cannot be done in a quarter of an hour because they depend on someone else. Approvals, access requests and supplier replies are the classic examples. Do not put the wait inside a step. Instead, make the request its own fifteen-minute step, then place a separate “check the reply” step a few days later. This keeps the list honest: you can see exactly what you are waiting for and who has it.

Another awkward part is the decision that has no right answer, such as choosing between two layouts. Turn it into a step that ends with a decision on paper: list the two options, write one sentence on what each favours, pick one and record why. If the choice turns out wrong, you will know what you were thinking, and the change can be small.

Keeping track without heavy software

A simple shared sheet is enough. Use columns for the step, the owner, the finished state, the date and the status. Sort by status so that “next” items are at the top. Resist adding fields. Every extra column is something someone must fill in and nobody wants to. If you want a longer view of planning before any building begins, the step-by-step walkthrough on getting a business site properly mapped out before anyone writes code is a helpful read, and it fits neatly with the slicing approach described here.

A short note on the wider web

Rebuilds rarely live in isolation. Websites often depend on outside services for things like login, payments or listings, and each of those connections is a good candidate for its own short steps: set up the account, make a test connection, check the result. As a quick illustration of a website that leans on a shared service, MotoShareGulf presents itself as a scooter and motorbike hire-and-share site and hands user login over to a shared account system. Think of any such connection in your own rebuild as its own mini-project with a handful of tidy steps.

A word on estimating

Do not worry if your first guesses are off. In the first week most teams discover that some steps take five minutes and others take twenty-five. That is useful data. Note the real time beside the plan, and by the third or fourth week your slicing will have settled into a rhythm that matches how your team actually works. The goal is not precision but a list in which no single item hides a mountain, so a rough fifteen minutes is plenty.

Common mistakes to avoid

  • Cutting by tool instead of by result. “Open the editor” is not a step. “Draft the home page headline and save it” is.
  • Leaving testing for the end. Add a small check after every few steps, such as opening the new page on a phone, so that problems appear early.
  • Letting steps grow. When a step runs long, split what is left into new steps rather than quietly extending the time.
  • Hiding the list. If the steps live in one person’s head, the method loses its main benefit, which is shared visibility.

Making it stick

Agree a regular slot, even a small one, and start every session by taking whatever sits first in the queue. Keep a visible count of steps finished against steps planned. Review the list once a week, drop what is no longer needed and add what you learned. A rebuild that proceeds this way tends to feel calm, because there is always an obvious next move and a trail of finished work behind it.

Should you remember only one idea, let it be this one: open your rebuild plan today, find the item that scares you most and cut it into pieces until the first piece fits in a quarter of an hour. Do that piece before the day is out.

Related Posts

Near Misses as a Career Skill for Web Developers

Why handling a caught mistake well is a learnable skill for CMS and web developers, and how to show it in a portfolio or interview.

Read More

Five Website Clean-Up Myths That Keep Your CMS Cluttered

Five comfortable beliefs about website housekeeping, and the simpler habit that replaces them: trim drafts, plugins and media files as you work.

Read More

Website Teardown Checklist: Audit a Finished Business Site First

A practical five-part checklist for taking apart a finished business website, structure, content, navigation and technical clues, before you plan your own CMS build.

Read More

Eight Plain-Word Fixes for Clearer Website Copy and CMS Labels

Menus, buttons, error messages and admin fields often use insider words. Eight practical fixes, each with a before and after, to make your site easier to read.

Read More

Page Cap, Plugin Cap or Palette Cap: Which Site Limit Fits?

A friendly comparison of three self-imposed limits for CMS builds, covering pages, plugins and palettes, with when each one helps and where it hurts.

Read More

Why Web Projects Slip: Diagnosing the Unchosen Trade-Off

Late, over budget and still rough? A diagnosis-first look at web projects that never decided whether speed, cost or quality would give, plus the written fix.

Read More
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x
()
x