Six Myths About Slicing Big Aviation Projects Into 15-Minute Steps

Six Myths About Slicing Big Aviation Projects Into 15-Minute Steps

People who manage complicated aviation work, from itinerary coordination to documentation clean-ups behind a charter operation, tend to be sceptical of anything that sounds like a productivity trick. That scepticism is healthy. It is worth applying to the idea of cutting large projects into fifteen-minute steps, which is often waved away with a handful of confident objections. Six of the commonest are examined below, each checked against how projects actually move forward. It stays at the level of working method and makes no statement about charter services, safety or regulation.

Myth one: “Serious projects need serious blocks of time”

The intuition is understandable: complicated work seems to deserve long stretches of attention. The evidence from everyday practice is more mixed. Large projects are mostly made of ordinary, separable chores: collating files, confirming a detail, drafting a paragraph, updating a record. Those chores do not require a three-hour trance. The planning and judgement parts do benefit from longer sittings, but they are a minority of the total. Slicing lets you give the chores quarter-hour slots and save the long blocks for the genuinely deep parts, which is a more honest use of a diary.

Myth two: “Small steps mean small ambition”

Step size and goal size are independent. A person can build something very large out of very small pieces, as any builder of anything has known for a long time. What small steps change is how you approach the goal, not how high it is. A planner with an enormous goal and no first step produces less than a planner with a modest goal and a clear first step, because starting is the scarce resource. Ambition is a property of where you point the work. Step size is merely how you take the next stride.

Myth three: “Stopping and starting wastes more time than it saves”

Restart cost is real, but it is not fixed. It depends heavily on how a sitting ends. If you stop mid-thought with nothing written, the next start is expensive. If you close each sitting with a one-line note saying what is done and what comes next, the restart costs seconds. The myth confuses slicing without notes, which is indeed wasteful, with slicing done properly. Treat the closing note as part of the step, not an optional extra, and the supposed overhead largely disappears.

Myth four: “You can only slice tasks that are already well defined”

This is nearly backwards. Vague tasks are exactly where slicing helps most, because the first fifteen-minute step can be “write down what done would look like”. A coordinator facing a messy, half-documented process can spend one quarter-hour listing the pieces that exist and another listing the pieces that are missing. Those two lists are a definition, produced in thirty minutes, where a month of worrying had produced none. Nobody needs the task to be clear before slicing; slicing is a method for making it clear.

Myth five: “It only suits people with calm, predictable days”

Planners with unpredictable days are the strongest case for the method. A day full of interruptions rarely offers a three-hour window, but it nearly always offers scattered quarter-hours. A project that can be advanced in those fragments will move, while a project that needs a long window will wait. It helps to keep a short visible list of ready-to-go steps, so that when a gap opens, there is no deciding to do. If you want a model of working in short sittings across a trip-style puzzle, the guide on getting to know the city of Jaipur shows how a large destination can be explored one small district at a time.

Myth six: “Slicing is just procrastination in a tidy outfit”

Procrastination can disguise itself as planning, and some people do spend a week designing the perfect list of steps without doing any. The test is simple: does each step end with a finished product? A step that produces a note, a sketch, a sent message or a ticked box is work. A step that produces a feeling of being organised is not. Also watch the ratio. If you spend more time maintaining the list than doing the steps, trim the list to the next three items and delete the rest.

An illustration: tidying a document archive

Consider a back-office team that has inherited a shared drive of mixed-up files: trip sheets, supplier notes, old checklists, duplicates with names like “final_v2_really”. Nobody has time for a grand reorganisation, which is why nobody has done one. Sliced into quarter-hours, the job looks different. First sitting: list the top-level folders and what each seems to hold. Second: choose one folder and decide a naming pattern, written as a single line. Third: rename the files in half of that folder. Fourth: finish the other half and delete exact duplicates. Fifth: write two sentences explaining the pattern at the top of the folder.

Each sitting has a visible result, none requires special permission, and the team can stop at any moment without leaving things worse than before. In a month, a handful of folders are in order and the pattern is established for the rest. The archive did not need a project sponsor or a quiet quarter; it needed a first step and a repeatable size.

Why the objections share a flaw

Each objection quietly reads the size of a step as a verdict on how serious the work is. In practice, size is a tool. You pick the size that gets you moving and keeps you moving, and you review it when it stops working. A project that finishes late because it was cut into small pieces is rarer than one that never finishes because nobody could begin. Where the real constraint lies is usually in starting, not in stamina, and starting is exactly what a quarter-hour step makes easy. That is also why the method deserves a fair trial before it is dismissed.

A word for sceptical teams

If you lead a group rather than work alone, resist the temptation to impose the method. Invite one volunteer to try it on one stalled task for a week and report back in a sentence or two. A small, voluntary trial produces honest feedback and avoids the eye-rolling that follows any new routine announced from above. If it works, others will ask how; if it does not, you have lost almost nothing.

How to test the idea yourself

Rather than take any article’s word for it, run a small experiment. Choose a project you have been avoiding. Write five steps, each with one verb and one visible result. Complete one per day for five days. At the end, ask three questions: Did I start more easily than usual? Did the finished steps feel like progress? Would I have done this much in one long block? Your own answers will be more persuasive than any argument made here.

  1. Pick one stalled project and name its finish line in a sentence.
  2. Write five steps that each fit in fifteen minutes.
  3. Do one step a day and write a closing note each time.
  4. After five days, review what changed and adjust the step size.

A glance at an unrelated website

Short, finishable actions underpin ordinary web services as well. One example is a motorbike-and-scooter rental and sharing portal, where visitors pass through one central account sign-in first. It is a small illustration of the point that large-looking services are assembled from compact, repeatable parts.

Learning plans are projects too

If your own large project is building skills rather than documents, the same logic holds. The overview of technical training paths in Japan is a reminder that long learning journeys are assembled one short module at a time, and nothing stops you from scheduling each module as a quarter-hour step.

The six myths share one remedy: try it in small, measurable doses, and let the results speak. If fifteen-minute steps do not help you, drop them. Most people who give them an honest week find that the myths lose their grip.