{"id":1646,"date":"2026-11-20T09:25:00","date_gmt":"2026-11-20T09:25:00","guid":{"rendered":"https:\/\/www.jetexe.com\/blog\/six-myths-start-stop-continue-air-travel-teams\/"},"modified":"2026-11-20T09:25:00","modified_gmt":"2026-11-20T09:25:00","slug":"six-myths-start-stop-continue-air-travel-teams","status":"publish","type":"post","link":"https:\/\/www.jetexe.com\/blog\/six-myths-start-stop-continue-air-travel-teams\/","title":{"rendered":"Six Myths About Start-Stop-Continue Reviews in Air Travel Teams"},"content":{"rendered":"<p>Teams that handle air travel information, from charter explainers to trip planning, tend to treat looking back as optional. Flights get booked, articles get published, the next request arrives, and nobody stops to ask what the last stretch taught them. The start-stop-continue review is a lightweight fix, yet it attracts a surprising number of misconceptions that stop teams from trying it. This post tests six of them against what the format actually does, using plain reasoning and examples from aviation-style operations rather than invented statistics.<\/p>\n<h2>Myth one: &#8220;A retrospective needs a long meeting&#8221;<\/h2>\n<p>The belief is understandable, since the word suggests a formal gathering with slides. In practice, the format works because it is short. Three headings, a handful of items each, and a fixed time limit keep discussion honest. Long sessions drift toward complaints and blame, whereas a tight format forces people to commit to concrete changes.<\/p>\n<p>Time-limiting each column helps. Ten minutes per list, with a visible timer, stops the first topic from swallowing the session and makes sure the Continue column gets its fair share of attention.<\/p>\n<p><strong>Verdict:<\/strong> busted. A session of about thirty minutes is enough for a small team, and the shortness is a feature. When a session keeps spilling over, the period under review was probably too long, and the cure is a shorter period, not a longer meeting.<\/p>\n<h2>Myth two: &#8220;Only failures belong in a review&#8221;<\/h2>\n<p>Many teams hold the review only after something goes wrong. That produces a lopsided picture, because successes teach just as much. The Continue column exists precisely to record what should be protected. Consider a team that explains how empty-leg flights work. If its habit of checking facts against operator information is the reason readers trust its pieces, that habit should be written down and defended.<\/p>\n<p>A good illustration is <a href=\"https:\/\/www.jetexe.com\/blog\/how-empty-leg-jet-flights-work\/\">an explainer on the way repositioning flights without passengers are handled<\/a>. Whatever process produced a clear article of that kind belongs in Continue, because losing it would cost more than any one error.<\/p>\n<p>The same logic applies to small routines, such as having a second person read every explainer before it goes live. Teams rarely notice the value of such habits until someone proposes dropping them to save time.<\/p>\n<p><strong>Verdict:<\/strong> busted. A review without a Continue list tends to remove working practices along with broken ones.<\/p>\n<h2>Myth three: &#8220;The lists should capture everything we noticed&#8221;<\/h2>\n<p>Teams new to the format often pile twenty items under each heading, feeling thorough. The effect is paralysis. Nobody can act on twenty changes at once, and most of the items quietly vanish. The evidence from nearly any process-improvement setting points the same way: a short list that gets done beats a long list that gets admired.<\/p>\n<p>A practical rule is to keep no more than four items per column and to rank them by how much they would change the next stretch of work. The rest go into a parking list that is reviewed next time.<\/p>\n<p><strong>Verdict:<\/strong> busted. Selection is the skill. Writing down everything is easy; choosing the few items that matter is where the review earns its keep.<\/p>\n<p>One way to practise the skill is dot voting. Each person gets three marks to place beside the items they think matter most, and the items with the most marks make the cut. It takes two minutes, keeps louder voices from dominating, and leaves a visible record of why the shortlist looks the way it does.<\/p>\n<h2>Myth four: &#8220;Costs and prices are too variable to review&#8221;<\/h2>\n<p>Some people argue that a field with moving prices has nothing stable to learn from. The opposite is true. Variable conditions make a record of decisions more valuable, because you can see which choices held up when circumstances changed. Pricing in private aviation depends on several moving factors, as <a href=\"https:\/\/www.jetexe.com\/blog\/factors-that-affect-private-jet-charter-pricing-2\/\">a discussion of what shapes charter pricing<\/a> explains, and a team that reviews how it explained those factors can improve its future guidance.<\/p>\n<p>The review does not need numbers to work. It needs observations such as &#8220;readers kept asking the same pricing question&#8221; or &#8220;our worked example confused people&#8221;. Those observations turn directly into Start and Stop items, such as adding a short example or removing a paragraph that caused confusion.<\/p>\n<p>Qualitative notes are not second-best here. A reader message saying a section was unclear is evidence, and a pattern of several such messages is stronger evidence still. The review simply gives that pattern a place to land.<\/p>\n<p><strong>Verdict:<\/strong> busted. Variability is a reason to review more often, not less.<\/p>\n<h2>Myth five: &#8220;Outside examples are a distraction&#8221;<\/h2>\n<p>Teams sometimes insist that only their own industry offers lessons. A look at other organised information sources suggests the reverse. When you study how a different website structures its material, you notice weaknesses in your own that familiarity had hidden. <a href=\"https:\/\/bestpilotsnow.com\/\">BestPilotsNow<\/a>, for instance, presents itself as an aviation discovery site and splits its material across separate parts for people, training and reference reading, then adds discussion and articles. A travel-information team can borrow the principle without borrowing any content, namely that clear, consistent sections make a large topic easier to approach.<\/p>\n<p>Make this a Start item if it fits: once per review, look at one outside example and write down one thing worth copying and one thing to avoid.<\/p>\n<p>Keep the comparison honest by looking at weaknesses as well as strengths. A site that looks tidy may still bury its most useful page, and noticing that teaches as much as admiring a clean menu.<\/p>\n<p><strong>Verdict:<\/strong> partly busted. Outside examples distract when they replace your own evidence, but they help when used as a quick comparison after you have done your own review.<\/p>\n<h2>Myth six: &#8220;Nothing changes, so reviews are pointless&#8221;<\/h2>\n<p>This is the most corrosive myth, and it usually comes from experience. Teams that held reviews, wrote the lists and then forgot them correctly conclude that the exercise achieved nothing. The failure, though, was in follow-through, not in the format. A review changes results only when each item has an owner, a date and a place where the team will see it again.<\/p>\n<p>Consider what happens when a team writes &#8220;Start: add a short glossary to every explainer&#8221; and then assigns one person to add it to the next two articles. Within a month the habit is visible in the work, and readers notice. Compare that with a list sitting in a forgotten folder.<\/p>\n<p>Follow-through can be tiny. One sentence pinned above the team&#8217;s shared page, reading &#8220;this fortnight we are testing the three agreed changes&#8221;, is enough to keep the lists alive between reviews. The act of seeing the commitment every day matters more than any elaborate tracking tool.<\/p>\n<p><strong>Verdict:<\/strong> busted, with a condition. Reviews work when someone follows up. They fail when the lists are filed and forgotten.<\/p>\n<h2>Scorecard: how the myths held up<\/h2>\n<p>Here is the tally in one place, ready to paste into your team&#8217;s notes, so you can judge which beliefs, if any, have been keeping you from a first attempt.<\/p>\n<ul>\n<li>Myth one, long meetings: false. Short reviews perform better.<\/li>\n<li>Myth two, failures only: false. Successes belong on the Continue list.<\/li>\n<li>Myth three, capture everything: false. Short lists get acted on.<\/li>\n<li>Myth four, prices too variable: false. Variability increases the value of a record.<\/li>\n<li>Myth five, outside examples distract: partly false. Use them after your own review.<\/li>\n<li>Myth six, nothing changes: false when there is follow-through.<\/li>\n<\/ul>\n<h2>A simple test you can run this month<\/h2>\n<p>If you are still unconvinced, run a small experiment instead of trusting a claim from anyone, including this post. Pick one stretch of work, perhaps a month of published pieces or a season of trip enquiries, and hold a thirty-minute review with the three lists. Choose one change from each list and write it down with an owner. At the end of the next stretch, compare notes: did the team do what it said, and did the work feel any smoother? That small comparison is evidence you can trust, because it comes from your own team.<\/p>\n<p>Add a line to your log about how the team felt, too, since morale is part of the evidence. Keep a short log of the results. Within a few rounds the log shows whether the practice earns its place, and you can adjust the format, the length or the frequency to suit your pace. Myths fade fast once your own notes are on the table.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Long meetings, failures only, endless lists: six common beliefs about retrospectives tested against how the format works for teams that write about air travel.<\/p>\n","protected":false},"author":7,"featured_media":1647,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[916],"tags":[],"class_list":["post-1646","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aviation-industry"],"_links":{"self":[{"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/posts\/1646","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/comments?post=1646"}],"version-history":[{"count":0,"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/posts\/1646\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/media\/1647"}],"wp:attachment":[{"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/media?parent=1646"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/categories?post=1646"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jetexe.com\/blog\/wp-json\/wp\/v2\/tags?post=1646"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}