{"id":3040,"date":"2026-11-19T11:03:47","date_gmt":"2026-11-19T09:03:47","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3040"},"modified":"2026-11-19T11:04:04","modified_gmt":"2026-11-19T09:04:04","slug":"resolved-is-not-the-same-as-ready-to-launch","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/resolved-is-not-the-same-as-ready-to-launch\/","title":{"rendered":"\u201cResolved\u201d Is Not the Same as \u201cReady to Launch\u201d"},"content":{"rendered":"<p>The project board shows no open design comments. Someone asks whether the website can launch this afternoon. A clean feedback list is useful information, but it does not say which changes were checked or who accepted the current version.<\/p>\n<h2>Define the question behind the status<\/h2>\n<p>Consider a fictional agency preparing a service website. A button destination was corrected, a heading was shortened and an enquiry form was revised. All three comments now say \u201cresolved\u201d. The developer means the requested edits are implemented. The account manager reads the same label as client approval. Neither interpretation is visible in the label itself.<\/p>\n<p>Do not solve this simply by renaming the column \u201cdone\u201d. Agree which observed event earns each status. A completed edit, a successful check and an acceptance decision can happen at different times and involve different people. Your record should let someone distinguish them without reading every conversation.<\/p>\n<h2>Build a four-stage record<\/h2>\n<p>Use one row per item with these fields: request and affected location; implementation\/version; verification and result; acceptance or remaining decision. Add a release-level summary above the rows. This can be a table in an ordinary document; the useful part is the meaning of the fields, not the software.<\/p>\n<p>For implementation, write what changed and where it can be inspected. For verification, name the check actually performed and the observed result. For acceptance, name the appropriate decision owner and what they accepted. If the client has not reviewed the current text, say \u201cawaiting wording decision\u201d rather than allowing an implementation date to imply approval.<\/p>\n<h2>Fill one row completely<\/h2>\n<p>The button row might read: \u201cCollection enquiry button linked to the agreed enquiry page in review version B. Checker opened the button from the service page and confirmed the intended destination. Offer owner accepted that route for this service.\u201d This is much more informative than three green circles with no version attached.<\/p>\n<p>The form row may have a different result: \u201cField label changed in version B; test submission not yet checked through the actual receiving process; owner acceptance pending.\u201d The design comment can be closed as an implemented edit while the release summary still shows a dependency. Do not convert missing evidence into a favourable result merely to keep the board tidy.<\/p>\n<h2>Keep launch readiness above individual tickets<\/h2>\n<p>Now ask the broader question: is the agreed launch scope ready for its intended use? Review outstanding dependencies with the responsible people. These might include final content decisions, a receiving process that has not been exercised or a change made after the last acceptance. The relevant checks depend on the site and its actual purpose; a small brochure site and a transactional service have different requirements.<\/p>\n<p>A useful summary has three lines: ready within the agreed scope; remaining conditions; person authorised to make the release decision. Name the current version or review point. An old approval should not silently cover a material change made afterwards. This is a practical project record, not a substitute for specialist checks the project needs.<\/p>\n<h2>Handle a late change without rewriting history<\/h2>\n<p>Suppose the client changes the collection area after accepting version B. Retain the earlier acceptance, identify the new change and reopen the affected decision. Check the pages and messages that depend on that area. You do not need to erase all completed work, but you do need to show why the previous acceptance no longer settles this particular issue.<\/p>\n<p>A brief handoff could say: \u201cThe agreed button route is implemented and checked. The collection-area wording changed after acceptance, so that wording and its dependent enquiry instruction need a new decision before release.\u201d Anyone reading it can see both the progress and the remaining work.<\/p>\n<h2>Use the record in the release conversation<\/h2>\n<p>At the final review, ask people to point to evidence rather than count closed comments. Which version was checked? Which decision remains open? Does it prevent the intended launch, or is a clearly agreed narrower scope possible? Record the answer and owner. The aim is a decision the next colleague can understand, including the conditions under which it was made.<\/p>\n<p>Use status labels to describe an observed stage of work. When comparing review tools, check whether your team can keep implementation, verification and client acceptance distinguishable.<\/p>\n<p>For unclear requests before implementation, use <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/the-client-says-make-it-pop-what-do-you-ask-next\/\">the design-feedback clarification guide<\/a>. If the same issue appears after completion, compare <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/did-the-client-ask-again-or-did-the-website-change-again\/\">a repeated request with a new observation<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A cleared feedback list can hide unfinished checks. Track the changed item, its verification and the launch decision as different pieces of evidence.<\/p>\n","protected":false},"author":1,"featured_media":3076,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[35],"tags":[],"class_list":["post-3040","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-digital-tools"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.kaarne.fi\/superstore\/wp-content\/uploads\/sites\/7\/2026\/11\/np-04-01.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3040","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/comments?post=3040"}],"version-history":[{"count":7,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3040\/revisions"}],"predecessor-version":[{"id":3154,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3040\/revisions\/3154"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3076"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3040"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3040"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3040"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}