Few things frustrate an aviation team more than a project that keeps slipping. It might be a new reporting procedure, a revised training schedule, a records clean-up or a hangar scheduling tool. The symptoms are familiar: deadlines drift, spending creeps up, and the people doing the work feel the result is not what anyone hoped for. Here the situation is handled like a clinic visit for a plan. It lists the symptoms, finds the common root cause in the fast, cheap, good triangle, and sets out a repair that a manager can start this week. The method is deliberately plain and rests on observations, not on special tooling.
The presenting problem
A typical stalled project shows at least two of these signs at once. The calendar keeps moving, and each revision is described as “just a few more days”. The budget has been topped up once or twice. The team has quietly stopped mentioning the original scope. Meetings revolve around who is to blame for the delay rather than what to do next. Staff on the floor have begun to ignore the new process because it keeps changing. None of these signs points to a single culprit. They point to a plan that promised too much at the outset.
Diagnosis step one: write down the original promises
Find the first document or message that launched the project and list what it promised. In stalled projects, the list nearly always contains all three of: done by a firm date, done within a modest budget, and done to a high standard. That is the root cause in most cases. A plan that commits to all three corners cannot be fully honored when something goes wrong, and something always goes wrong, whether it is a staff absence, a late delivery or a requirement that turns out to be harder than assumed. When pressure arrives, one corner has to give, and because the plan never said which one, the team makes the choice badly, in private, and under stress.
Diagnosis step two: find out which corner is actually giving
Look at the evidence rather than the statements. If the date keeps moving while the budget and quality hold, speed is the sacrificed corner by default. If the date holds and spending grows, cost is paying. If both hold and the work is being rushed, quality is quietly eroding, which is the most dangerous case in this industry. Ask a few people on the team a simple question: if you had to drop one thing, which would you drop? Compare answers. Disagreement among them is itself a finding, because it shows the project has no shared decision.
Diagnosis step three: check for corner-cutting that nobody approved
The worst version of the problem is when quality is the quiet casualty. Signs include skipped reviews, informal sign-offs, documents closed without a second look, and a growing list of things to be fixed later. In an environment where procedures and records matter, this deserves a direct conversation. Nothing about the triangle justifies trimming required checks. Standards set by your regulator or your own safety rules are fixed constraints and sit outside the trade-off entirely. The triangle applies only to everything else: the pace, the budget and the extras above the required minimum.
The treatment: choose the corner openly
Once you know where things stand, the repair has four parts.
- Reset the promise. State, in one sentence, which two corners the project will now protect. For example: “We will meet the standard and the budget, and the finish date will move to the end of next quarter.”
- Cut the scope to fit. Remove or postpone features that were hostages to the old promise. Write down what was deferred so that it is not mistaken for forgotten.
- Tell everyone at once. The new promise should reach the team, the sponsors and the people affected by the change in the same message, so there are no rumors.
- Set a checkpoint. Pick a date two or three weeks ahead to see whether the new promise is holding. If not, adjust again, openly.
An illustration of the repair
Imagine a maintenance planning team rolling out a new way to track work orders. The original plan promised go-live in six weeks, no overtime budget, and zero disruption to the shop floor. By week five, the tracker is half-finished, the team is working evenings, and the floor staff are confused. The diagnosis is plain: all three corners were promised and none could be kept. The repair is a conversation. The manager resets the promise to protect quality and cost, moves the go-live date by two months, and drops the two least important reports from the first release. Evenings stop, confusion drops, and the work resumes at a steady pace. Nothing about the project’s difficulty changed. What changed was the honesty of the plan.
Differential diagnosis: what else could it be?
Not every late project is a triangle problem, so rule out the lookalikes before applying the treatment. Unclear ownership produces the same drift: if nobody can say who decides, work waits. Missing inputs, such as an approval that never arrives or a supplier that has gone quiet, create delay without any trade-off being made. Staffing gaps mimic a scope problem, because the plan was sound and the people were simply not there. A quick test separates these from the triangle: ask whether the team could finish on time, on budget and to standard if the missing input arrived tomorrow. If yes, fix the input. If no, the plan itself was overpromised and the steps above apply.
Measuring recovery
Recovery should be visible within a couple of checkpoints. Look for modest, observable changes: meetings that end with a decision, fewer revisions to the same document, floor staff who stop asking when the process will change again, and a backlog list that stays the same size instead of growing. If none of these improve after two checkpoints, the new promise was probably still too ambitious, and it is better to reset once more than to hope. Record each reset with its date and reason. The log is useful when the next project begins, because it shows how long similar work really took.
Resist the urge to turn recovery into a blame review. People who expect blame tend to hide bad news, and hidden bad news is precisely what let this project drift. A short, factual note on what the promise was, what happened and what the new promise is gives everyone the same picture without spending trust.
Why a short written promise helps
A single sentence naming the protected pair acts like a handrail. When someone proposes a new feature, ask which corner it will cost. When someone asks for a faster date, ask which corner pays. The conversation becomes about trade-offs, not about attitude. Teams that adopt this habit often find that arguments get shorter, because the facts are on the table. A short note on a whiteboard or a shared page is enough, provided that it is visible and dated.
A parallel from the technology world
The same pattern is well known in software and cloud teams, where releases get rushed or overspend when a plan tried to be quick, cheap and polished at once. A blog titled A CloudOps Blog describes itself with brief, plain-language articles on operating services in the cloud, so it is one place to read how that world discusses delivery choices. We reference it purely for the parallel. Aviation’s rules, procedures and safety standards come first in any trade-off you make.
Aftercare: preventing the next stall
- Begin every new project by writing the pair of protected corners and the corner being relaxed.
- Review that sentence at each milestone, not only when something goes wrong.
- Keep a list of “decisions made under pressure” and review it after the project, looking for patterns.
- Reward people who raise a trade-off early, even when the news is unwelcome.
- Remember that schedule slips are information. They are not proof of failure, and they are rarely fixed by shouting.
A stalled project is a symptom, and the underlying condition is almost always an unspoken triangle. Name it, choose, and tell people. The treatment costs a meeting and a sentence, and it often recovers weeks of drifting effort. In an industry that values clear procedures and honest records, a plan that says what it gives up is simply good practice.
