{"id":1288,"date":"2026-11-21T00:40:00","date_gmt":"2026-11-21T00:40:00","guid":{"rendered":"https:\/\/planespart.com\/blog\/?p=1288"},"modified":"2026-11-21T00:40:00","modified_gmt":"2026-11-21T00:40:00","slug":"hangar-team-story-unwritten-assumptions","status":"publish","type":"post","link":"https:\/\/planespart.com\/blog\/hangar-team-story-unwritten-assumptions\/","title":{"rendered":"The Monday a Hangar Team Wrote Down Its Assumptions"},"content":{"rendered":"<p>What follows is a made-up tale, loosely modelled on weeks that small maintenance teams will know well. Its point is a practical one about parts and planning: when a job depends on things nobody has said aloud, the job slips, and the cheapest insurance is to write down your assumptions before the work starts.<\/p>\n<h2>A quiet morning in the hangar<\/h2>\n<p>A small maintenance shop had a regional turboprop booked in for a scheduled inspection. The planner, a calm person with a habit of drinking tea gone cold, had built the work package on a Friday afternoon. Everything looked tidy. Task cards were printed, a bay was reserved, and the parts list was marked complete. The crew arrived on Monday expecting a smooth start.<\/p>\n<p>By mid-morning the lead technician had stopped at a component that did not match the part on the shelf. It was close, the same family and almost the same fitting, but it was not the item the card called for. A quiet flurry of phone calls followed. The aircraft sat open, the bay stayed occupied, and the next booked aircraft started to look like a problem.<\/p>\n<h2>The assumptions the plan had taken for granted<\/h2>\n<p>Later, when the dust settled, the planner did something unusual. They sat down with the lead technician, the stores clerk and the quality inspector and asked a single question: what did we believe on Friday that turned out not to be true? Out came a list. Each person wrote on a sticky note, one belief per note, and the notes went onto a whiteboard.<\/p>\n<ul>\n<li>The part in stock matched the current revision called for on the card.<\/li>\n<li>The supplier&#8217;s delivery estimate included time to clear paperwork on arrival.<\/li>\n<li>The inspector would be available when the first stage was complete.<\/li>\n<li>The tooling for one fastener type was in the cabinet and in calibration.<\/li>\n<li>The weather would stay dry enough to leave a hangar door open for the engine run.<\/li>\n<\/ul>\n<p>Not one of these was careless. Each was a perfectly reasonable thing to believe. The trouble was that nobody had ever said them out loud, so nobody had checked them, and so a mismatch in a single part could ripple through the entire schedule.<\/p>\n<h2>Rating confidence, honestly<\/h2>\n<p>The team added a second mark to each note. The planner drew a small circle in one of three colours to show how sure they were: green for confirmed, amber for probable, red for a guess. It was uncomfortable at first. The stores clerk admitted that &#8220;in stock&#8221; really meant &#8220;I saw one on the shelf last month.&#8221; The inspector confessed that their availability depended on a colleague&#8217;s leave, which they had not mentioned to anyone.<\/p>\n<p>That honesty was the real turning point. A list of beliefs is only useful if people are willing to mark the shaky ones as shaky. The practice worked because nobody was being blamed; the question was about the plan, not about anyone&#8217;s competence.<\/p>\n<h2>Attaching a way to find out<\/h2>\n<p>For every amber or red note the team wrote a check. It was the dullest part of the exercise and the most valuable. &#8220;Compare the revision on the part tag with the card&#8221; is a ten-minute check done on Friday. &#8220;Ask the supplier whether the estimate includes goods-in&#8221; is a single email. &#8220;Confirm the second inspector for Thursday&#8221; is a quick conversation. Each check had an owner and a time. By the end of the session the whiteboard had turned from a worry wall into a short action list.<\/p>\n<p>The planner then added one more rule that sounds trivial and is not: any belief with high consequence and low confidence had to be checked before the aircraft was opened, not after. That single sentence would have saved the Monday.<\/p>\n<h2>The next job, a different morning<\/h2>\n<p>Two weeks later another aircraft arrived, a similar type with a similar package. This time the planner ran the whiteboard session on the Thursday before. A red note read: the parts supplier&#8217;s catalogue revision matches the aircraft&#8217;s modification status. The stores clerk checked, and found that one item had been superseded. A replacement was ordered the same day. The crew started on Monday with everything in hand, and the schedule held.<\/p>\n<p>There was nothing heroic in it. Nobody worked late or had a flash of brilliance. They simply moved a few uncertain beliefs into the light early enough for them to be corrected cheaply. The planner&#8217;s own summary was short: guessing is fine, hiding the guessing is not.<\/p>\n<h2>What buyers and planners can borrow<\/h2>\n<p>The same habit applies well beyond the hangar. A purchasing plan, for example, rests on beliefs about lead times, compatibility and supplier paperwork. Teams who buy components regularly will recognise the pitfalls described in this site&#8217;s piece on <a href=\"https:\/\/planespart.com\/blog\/control-system-parts-buying-mistakes-to-avoid\/\">common control system part purchasing slips<\/a>, and many of them trace back to an assumption nobody wrote down. Treat each purchase as a short list: what must be true for this part to fit, arrive and be accepted?<\/p>\n<p>A few practical rules fall out of the story.<\/p>\n<ul>\n<li>Write beliefs as plain sentences, one per line, with no jargon.<\/li>\n<li>Mark confidence honestly, and treat &#8220;I saw it once&#8221; as a guess.<\/li>\n<li>Pair every uncertain item with a specific, cheap check and a named owner.<\/li>\n<li>Do the checks before the aircraft is opened, while changes are still inexpensive.<\/li>\n<li>Keep the page, so that the reasoning behind a decision can be read later.<\/li>\n<\/ul>\n<h2>A side note on learning the habit<\/h2>\n<p>This style of explicit planning is common in other technical fields too. People who run IT operations write down what they expect before a change, then compare reality with the note. If that crossover interests you, NoOpsSchool is a training website based in India whose menu lists certifications, courses, consulting and services for IT people, and anyone curious can read <a href=\"https:\/\/noopsschool.com\/\">how the site describes its own programmes<\/a>, even though aircraft are outside its scope. The career-minded reader may also enjoy this site&#8217;s article on <a href=\"https:\/\/planespart.com\/blog\/level-up-your-engineering-career-with-devopsschool\/\">growing an engineering career through structured learning<\/a>.<\/p>\n<h2>How the story ends<\/h2>\n<p>The whiteboard from that first Monday is still on the wall, a little smudged, its sticky notes now curling at the edges. New apprentices ask what it is. The crew&#8217;s answer is always the same: it is the list of things we used to believe without checking. It remains the most-read document in the shop, partly because it is honest about what the team did not know and partly because it keeps proving its worth every time a package is planned.<\/p>\n<p>If your own planning feels brittle, begin small. Pick the next job on the board, give yourself ten minutes, and write down every belief the plan depends on. Rate them, attach a check, and see which ones surprise you.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>An invented but familiar story of a small maintenance crew, a mismatched part and the whiteboard of unspoken beliefs that changed how they plan each job.<\/p>\n","protected":false},"author":6,"featured_media":1289,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[617],"tags":[],"class_list":["post-1288","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aviation-maintenance"],"_links":{"self":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts\/1288","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/comments?post=1288"}],"version-history":[{"count":1,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts\/1288\/revisions"}],"predecessor-version":[{"id":1373,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts\/1288\/revisions\/1373"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/media\/1289"}],"wp:attachment":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/media?parent=1288"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/categories?post=1288"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/tags?post=1288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}