{"id":6436,"date":"2026-11-21T07:58:42","date_gmt":"2026-11-21T07:58:42","guid":{"rendered":"https:\/\/www.cmsgalaxy.com\/blog\/?p=6436"},"modified":"2026-11-21T08:00:42","modified_gmt":"2026-11-21T08:00:42","slug":"how-to-keep-assumptions-log-website-build","status":"publish","type":"post","link":"https:\/\/www.cmsgalaxy.com\/blog\/how-to-keep-assumptions-log-website-build\/","title":{"rendered":"How to Keep an Assumptions Log for Your Next Website Build"},"content":{"rendered":"<p>The owner of a small bakery decided to rebuild her website over a long weekend. By Sunday night the new design looked lovely, and by Monday morning three problems had surfaced: the ordering form needed an email address that nobody had set up, the product photos were far too heavy for mobile visitors, and the person expected to approve the text was on holiday. Nothing about the build was wrong. What had gone wrong was a stack of unwritten beliefs about the project. This how-to shows how to catch them early with a written assumptions log for any CMS or web development job.<\/p>\n<h2>Step 1: Open a plain document before you open the CMS<\/h2>\n<p>Create a single page and title it &#8220;What we are assuming&#8221;. Resist the urge to start in the dashboard. Whatever platform you use, the first hour of any web project is better spent on this page than on theme settings, because it is the one place where beliefs can be listed before they harden into design decisions.<\/p>\n<p>Pick a format you will actually maintain: a shared note, a spreadsheet tab or the first section of the project ticket. If several people are involved, put it where they can all comment.<\/p>\n<h2>Step 2: List what you believe about content<\/h2>\n<p>Content causes more delays than code. Write a line for each of these, in the form &#8220;we assume that\u2026&#8221;:<\/p>\n<ul>\n<li>the final text exists and will arrive before the build starts;<\/li>\n<li>images are available in the right sizes and the usage rights are clear;<\/li>\n<li>the pages planned match what the business needs, such as service pages and an about page;<\/li>\n<li>someone named by role, for example &#8220;the shop owner&#8221;, approves wording within an agreed number of days.<\/li>\n<\/ul>\n<p>If you are unsure which pages a business site must carry, a <a href=\"https:\/\/www.cmsgalaxy.com\/blog\/essential-pages-every-business-website-should-include-a-complete-structural-guide\/\">complete outline of which pages a firm&#8217;s website ought to have<\/a> works as a prompt: for each page it suggests, add an assumption about who writes it and when it lands.<\/p>\n<h2>Step 3: List what you believe about the platform<\/h2>\n<p>Next come the technical beliefs. They are easy to miss because they feel like facts until a plugin misbehaves. Typical examples:<\/p>\n<ul>\n<li>the hosting plan supports the PHP version and storage the theme needs;<\/li>\n<li>the chosen plugins work together and are still maintained;<\/li>\n<li>the site can send email from the contact form without landing in spam;<\/li>\n<li>backups run automatically and can actually be restored.<\/li>\n<\/ul>\n<p>Mark each one. &#8220;We assume forms send email&#8221; is worth a confidence label of unknown until someone submits a test message and reads it in a real inbox.<\/p>\n<h2>Step 4: List what you believe about visitors<\/h2>\n<p>The bakery owner assumed most customers would browse on a desktop. A quick look at past order messages suggested the opposite. Write down your beliefs about devices, connection speeds, languages and what visitors want to do first. Then, wherever you have even rough data such as previous enquiries or social media comments, note it beside the line. Where you have no data, say so plainly; an honest &#8220;guess&#8221; tells the team where to gather information.<\/p>\n<h2>Step 5: Add confidence and a check to every line<\/h2>\n<p>Create two more columns. In the first, write firm, likely or unknown. In the second, name the quickest action that could settle the question. For example:<\/p>\n<ol>\n<li>Form emails: send three tests from a phone and a laptop, and check the spam folder too.<\/li>\n<li>Photo weight: open the staging page on a mid-range phone over a mobile connection and time it.<\/li>\n<li>Approval: message the approver now and agree a deadline in writing in the project thread.<\/li>\n<\/ol>\n<p>This is where the log earns its keep. Instead of a long list of worries you have a short list of small jobs.<\/p>\n<h2>Step 6: Tie the log to your plan<\/h2>\n<p>An assumption that nobody can act on is only trivia. For each unknown or likely line that would hurt if it failed, decide whether it changes the schedule. A <a href=\"https:\/\/www.cmsgalaxy.com\/blog\/how-to-plan-a-business-website-before-development-starts-a-complete-step-by-step-guide\/\">sequenced guide to laying the groundwork for a firm&#8217;s new site<\/a> is a good companion at this stage, because it covers the sequence of preparation work, and your log tells you which of those steps you can trust and which need extra time.<\/p>\n<h2>Step 7: Review at every milestone<\/h2>\n<p>A log that is written once and filed away does nothing. The review is where most of its value appears.<\/p>\n<p>After each stage, whether wireframes, content load or launch rehearsal, open the log and update it. Move lines from unknown to confirmed or disproved, and add any new beliefs the work has surfaced. Keep a short dated note when a belief changes, such as &#8220;approver now available only on Thursdays&#8221;. When the project is audited later, the page explains why the schedule moved.<\/p>\n<h2>A note on outside training<\/h2>\n<p>Developers and site administrators who want to build wider operations skills sometimes look at courses beyond their CMS. One example is <a href=\"https:\/\/noopsschool.com\/\">a training portal run from India that, in its own words, offers certification-style courses, consulting and related services to IT practitioners<\/a>. Whichever route you take, bring a real project to practise on, because an assumptions log only teaches you something when it is attached to live work.<\/p>\n<h2>How the bakery story ended<\/h2>\n<p>On the second attempt, the owner opened a page before touching the dashboard. She wrote eleven lines, marked four of them unknown, and spent one evening settling them. The form got a working mailbox, the photos were compressed, and a backup approver was named. The relaunch took half the time of the first try, and the notes became a checklist for the next update.<\/p>\n<h2>Why this suits CMS work in particular<\/h2>\n<p>Content management projects mix technical and human dependencies more than most. A theme update, a plugin conflict, a late paragraph from a client and an unanswered approval email can each stall a launch, and they rarely show up in a build estimate. An assumptions log is the one document that holds all of them side by side, so a developer, an editor and a client can read the same page and agree on what still has to be true.<\/p>\n<p>It also protects maintenance work after launch. Months later, when someone asks why a plugin was chosen or why a page layout looks the way it does, the dated lines explain the reasoning without anyone having to remember it.<\/p>\n<h2>Pitfalls to avoid<\/h2>\n<ul>\n<li><strong>Writing tasks instead of beliefs.<\/strong> &#8220;Compress images&#8221; is a to-do. &#8220;Images are already small enough&#8221; is the assumption behind it.<\/li>\n<li><strong>Leaving out people.<\/strong> Approvals, sign-offs and availability are assumptions too.<\/li>\n<li><strong>Treating the log as a blame record.<\/strong> Its purpose is to make the next decision better, not to find fault.<\/li>\n<li><strong>Letting it go stale.<\/strong> If it was last edited a month ago, it is describing a different project.<\/li>\n<\/ul>\n<p>A written log costs an hour at the start and saves a weekend of rework near the end. Open that page first next time, list what you believe, and let the project prove you right or wrong in small, cheap steps.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A bakery relaunch stumbled on beliefs nobody wrote down. This seven-step how-to shows web teams how to log assumptions about content, platform and visitors.<\/p>\n","protected":false},"author":14,"featured_media":6437,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1455],"tags":[],"class_list":["post-6436","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-development"],"_links":{"self":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6436","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/comments?post=6436"}],"version-history":[{"count":1,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6436\/revisions"}],"predecessor-version":[{"id":6539,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6436\/revisions\/6539"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media\/6437"}],"wp:attachment":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media?parent=6436"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/categories?post=6436"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/tags?post=6436"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}