Aerospace Project Execution & Prioritisation

Module 01 -- Prioritisation

Prioritisation Frameworks

Apply proven prioritisation methods to manage the competing demands of aerospace programmes -- from urgent safety directives to long-range R&D investments.

⚖ Eisenhower Matrix

Click a task on the left, then click a quadrant to assign it. Remove tasks by clicking the X.

← Urgent Not Urgent →

🔴

Do First

Urgent & Important

🔵

Schedule

Not Urgent & Important

🟠

Delegate

Urgent & Not Important

⬜

Eliminate

Not Urgent & Not Important

↑ Important | ↓ Not Important

🎯 MoSCoW Method

Categorise requirements into four priority buckets to ensure critical deliverables are protected.

🔴

Must Have

Non-negotiable

Requirements without which the system will not be safe, legal, or functional. These are the minimum usable subset.

Safety-critical functions -- Flight control laws, structural load limits, fire suppression

Regulatory compliance -- FAA/EASA certification requirements, DO-178C objectives

Contractual obligations -- Milestone deliverables tied to payment gates

Decision rule -- If removed, the project fails or cannot ship

Click to expand

🟠

Should Have

High Priority

Important requirements that add significant value but have workarounds. Painful to omit but survivable.

Performance enhancements -- Drag reduction features, weight optimisation

Operational efficiency -- Automated test sequences, improved maintenance access

Customer satisfaction -- Preferred cabin configurations, noise reduction targets

Decision rule -- If removed, the product works but is significantly weaker

Click to expand

🔵

Could Have

Desirable

Nice-to-have features that enhance the product. Include only if time and budget permit without impacting Must/Should items.

Enhanced avionics displays -- Synthetic vision, head-up display upgrades

Extended range options -- Auxiliary fuel tanks, winglet refinements

Tooling improvements -- Better jigs, automated inspection systems

Decision rule -- If removed, impact is minimal and easily accepted

Click to expand

⬜

Won't Have (This Time)

Deferred

Requirements explicitly excluded from this iteration. Documented to manage expectations and feed future planning.

Future platform variants -- Freighter conversion, stretched fuselage

Next-gen technologies -- Electric propulsion, hydrogen fuel cells

Market-specific customisations -- Regional airline configurations

Decision rule -- Agreed out of scope; revisit in future programme increments

Click to expand

📈 WSJF Calculator

Weighted Shortest Job First -- prioritise work items by dividing Cost of Delay by Job Size.

WSJF Priority Score

Rate each factor 1-10. WSJF = (Business Value + Time Criticality + Risk Reduction) / Job Size

Business Value (1-10)

Time Criticality (1-10)

Risk Reduction (1-10)

Job Size (1-10)

WSJF Score

3.00

(5 + 5 + 5) / 5 = 3.00

📚 Additional Frameworks

Complement the core frameworks with these supplementary prioritisation approaches.

💰

Cost of Delay (CoD)

Economic Framework

Quantify the financial impact of delaying a feature or deliverable. Drives urgency with hard numbers rather than gut feel.

Revenue impact -- Lost revenue per week/month if delivery is delayed. For airlines, this includes lost route revenue and lease penalties

Market share erosion -- Competitors capturing orders while your programme slips. Each month of delay may shift orders to rival OEMs

Penalty clauses -- Contractual liquidated damages for late delivery. Typical aerospace contracts include $50K-$500K/day penalties

Escalation costs -- Standing army costs, facility leases, and supplier commitments that continue regardless of progress

Certification windows -- Missing a regulatory submission window can add 6-12 months to the schedule

Click to expand

🎯

RICE Scoring Model

Quantitative Ranking

Score items on Reach, Impact, Confidence, and Effort. Produces a comparable numeric score for transparent prioritisation.

Reach -- How many people/systems does this affect per time period? In aerospace: how many aircraft, flights, or passengers impacted

Impact -- How much does this move the needle? Score: 3=massive, 2=high, 1=medium, 0.5=low, 0.25=minimal

Confidence -- How sure are you of your estimates? 100%=high, 80%=medium, 50%=low. Penalises uncertain bets

Effort -- Person-months required to deliver. Larger effort = lower RICE score, favouring quick wins

Formula -- RICE = (Reach x Impact x Confidence) / Effort. Compare scores across competing items

Click to expand

⚖

Value vs. Complexity Matrix

2x2 Decision Tool

Plot items on a value (y-axis) vs. complexity (x-axis) grid to quickly identify quick wins, strategic initiatives, and items to avoid.

Quick Wins (High Value, Low Complexity) -- Do these first. Examples: tooling upgrades, process automation, supplier consolidation

Major Projects (High Value, High Complexity) -- Worth the investment but plan carefully. Examples: new aircraft variant, avionics suite upgrade

Fill-ins (Low Value, Low Complexity) -- Do if resources are available. Examples: documentation updates, minor UI changes to ground support equipment

Money Pits (Low Value, High Complexity) -- Avoid or defer. These consume resources for minimal return

Click to expand

🚀

Kano Model

Customer Satisfaction

Categorise features by their effect on customer satisfaction: basic needs, performance needs, and delighters.

Must-Be (Basic) -- Expected by default; absence causes extreme dissatisfaction. In aerospace: safety, airworthiness, basic performance

One-Dimensional (Performance) -- More is better, linearly correlated with satisfaction. Examples: range, fuel efficiency, payload capacity

Attractive (Delighters) -- Unexpected features that create disproportionate satisfaction. Examples: advanced connectivity, predictive maintenance

Indifferent -- Features customers don't care about either way. Eliminate to save cost and complexity

Reverse -- Features some customers actively dislike. Example: complexity that increases training burden

Click to expand

📋 Prioritisation Maturity Self-Assessment

Rate your team's prioritisation maturity. Check each practice you consistently follow.

Module 02 -- Meeting Management

Meeting Effectiveness

Aerospace programmes consume thousands of meeting hours. Make every minute count with structured agendas, clear decisions, and accountability tracking.

📋 Meeting Effectiveness Scorecard

Check each item that was true for your last meeting. Score 75%+ for an effective meeting.

📝 Agenda Template Builder

Build a structured agenda with topics, owners, and time allocations.

Build Your Agenda

Topic

Owner

Time (min)

📄 Decision Log Template

Track decisions made during programme reviews and design gates.

Programme Decision Log

ID	Decision	Date	Owner	Status
DEC-001	Approve composite wing spar design for fatigue testing	2026-03-15	Chief Engineer	Approved
DEC-002	Defer auxiliary power unit supplier selection to PDR	2026-03-22	Programme Mgr	Deferred
DEC-003	Reject titanium landing gear proposal due to cost overrun	2026-04-01	Cost Board	Rejected
DEC-004	Proceed with dual-source avionics procurement strategy	2026-04-05	Supply Chain	Approved
DEC-005	Escalate engine integration schedule conflict to steering committee	2026-04-10	Integration Lead	Escalated

Module 03 -- Estimation

Estimation Under Uncertainty

Aerospace projects face enormous uncertainty early in the lifecycle. Use proven techniques to quantify uncertainty and communicate realistic timelines to stakeholders.

🎨 Cone of Uncertainty Visualiser

Drag the slider to see how estimate accuracy improves as the project progresses through lifecycle phases. The cone narrows from 4x variability at concept to near-exact at delivery.

Concept Concept

Estimate range: 0.25x -- 4.0x (16x variability)

📊 PERT Three-Point Estimator

Enter optimistic (O), most likely (M), and pessimistic (P) estimates in any unit (days, weeks, months). The calculator computes the weighted mean and standard deviation.

Optimistic (O)

Most Likely (M)

Pessimistic (P)

Weighted Mean (E)

7.67

(O + 4M + P) / 6

Std Deviation (SD)

1.67

(P - O) / 6

68% Confidence Interval

E +/- 1 SD = 6.00 to 9.33

📈

Estimation Anti-Patterns

Common Pitfalls

Avoid these common traps that lead to chronic under-estimation in aerospace programmes.

Planning Fallacy -- Underestimating duration by focusing on best-case scenarios rather than base rates

Anchoring Bias -- Estimates locked to initial numbers regardless of new evidence

Scope Amnesia -- Forgetting to account for integration, testing, certification, and rework

Pressure Estimates -- Giving management the number they want rather than the realistic one

Single-Point Fallacy -- Providing one number instead of a range with confidence level

Click to expand

🚀

Reference Class Forecasting

Evidence-Based

Use historical data from similar aerospace projects to calibrate estimates instead of bottom-up optimism.

Step 1 -- Identify a reference class of similar completed projects

Step 2 -- Determine the statistical distribution of outcomes (cost, schedule)

Step 3 -- Position your project within the distribution based on specific factors

Example -- Military aircraft programmes average 46% cost growth and 22-month schedule slip (RAND data)

Key insight -- Outside view consistently outperforms inside view for large programmes

Click to expand

📊

Monte Carlo Simulation

Probabilistic Method

Run thousands of random scenarios using PERT distributions to produce probability curves for schedule and cost outcomes.

Input -- Three-point estimates (O, M, P) for each task in the schedule network

Process -- Randomly sample durations from each task's distribution across 10,000+ iterations

Output -- S-curve showing probability of completing by any given date

P50 vs P80 -- P50 = 50% chance of hitting; P80 = 80% chance. Most aerospace programmes commit to P80

Correlation -- Account for risk correlations -- if one supplier is late, related tasks are also likely delayed

Tools -- Oracle Crystal Ball, @RISK, Primavera Risk Analysis, or custom Python scripts

Click to expand

🛠

Estimation Calibration

Improving Accuracy

Track actual vs. estimated outcomes to calibrate your team's estimation skill over time. Systematic improvement through feedback loops.

Track ratio -- Record actual/estimated for every task. A well-calibrated team averages 1.0 over time

Identify patterns -- Are you consistently 30% optimistic? Apply a correction factor until calibrated

Category analysis -- Break down accuracy by work type (design, test, manufacturing, certification)

90% confidence test -- When you give a 90% range, does the actual fall inside 90% of the time?

Team calibration -- Some engineers are perpetual optimists, others pessimists. Track individual bias

Click to expand

📋 Estimation Confidence Self-Check

Evaluate the robustness of your current project estimate. Check each item that applies.

Module 04 -- Competing Priorities

Managing Competing Priorities

Aerospace teams juggle safety, schedule, cost, and performance demands simultaneously. Use structured tools to align stakeholders and make transparent trade-offs.

📋 Priority Stack Ranker

Drag tasks to reorder them by priority. The highest priority task should be at position 1.

🤝 Stakeholder Priority Alignment

Rate how each stakeholder group prioritises the four programme constraints. Use the sliders to model different perspectives and find alignment.

Alignment Summary

Compare stakeholder priorities to identify conflicts and find consensus.

⚖ Trade-off Decision Frameworks

When priorities conflict, use structured approaches to make transparent, defensible decisions.

🛠

Iron Triangle Trade-offs

Scope-Schedule-Cost

You can optimise two of three constraints but not all three. Make the trade-off explicit and get stakeholder buy-in.

Fixed scope, flex schedule -- Deliver everything but accept the date will slip. Common in certification-driven programmes

Fixed date, flex scope -- Hit the delivery date by descoping to Must Haves only. Use MoSCoW to decide what stays

Fixed budget, flex scope + schedule -- Stay within budget by adjusting both scope and timeline. Rare in aerospace contracts

The trap -- Promising all three are fixed leads to death marches, quality cuts, and safety corners. Never commit to all three

Communication -- Present trade-off options to stakeholders, not solutions. Let them choose the constraint to relax

Click to expand

🌐

Decision Matrix (Pugh)

Multi-Criteria Analysis

Score alternatives against weighted criteria to make objective, repeatable decisions when multiple options compete.

Step 1 -- List decision criteria (safety, cost, schedule, performance, risk, certification effort)

Step 2 -- Assign weights to each criterion reflecting programme priorities (safety always weighted highest in aerospace)

Step 3 -- Score each alternative 1-5 against each criterion. Use a consistent scale

Step 4 -- Multiply scores by weights and sum. Highest total score wins

Sensitivity test -- Vary the weights by +/-10% to check if the winner changes. Robust winners survive weight changes

Documentation -- The scored matrix becomes an audit trail for the decision rationale

Click to expand

💡

RAPID Decision Framework

Role Clarity

Assign clear roles for each decision: Recommend, Agree, Perform, Input, Decide. Eliminates confusion about who owns the call.

Recommend -- The person or team who proposes the solution. Typically the subject matter expert or working team

Agree -- People who must formally agree before the decision proceeds. In aerospace: safety, legal, customer

Perform -- The person or team who will execute the decision once made

Input -- People consulted for expertise but who don't have veto power

Decide -- The single person who makes the final call. One person, not a committee. In aerospace: the DER, chief engineer, or programme director depending on impact

Click to expand

📈

Conflict Resolution Protocol

Escalation Path

When stakeholders disagree on priorities, follow a structured escalation path to prevent gridlock.

Level 1: Data Resolution -- Present objective data (cost analysis, schedule impact, risk assessment). Most conflicts resolve with better information

Level 2: Criteria Agreement -- If data doesn't resolve it, agree on the decision criteria and weights first, then re-score

Level 3: Facilitated Discussion -- Bring in a neutral facilitator (often the programme manager) to mediate between parties

Level 4: Executive Decision -- Escalate to the next management level with a clear statement of options, trade-offs, and recommendation

Golden rule -- Disagree and commit. Once the decision is made, everyone executes with full commitment regardless of their initial position

Click to expand

Module 05 -- Scope Protection

Scope Protection & Change Control

Uncontrolled scope creep is the leading cause of aerospace programme overruns. Establish formal change control to protect baselines while enabling necessary evolution.

📄 Scope Change Request

Change Request Title

Requested By

Justification

Schedule Impact (weeks)

Cost Impact ($K)

Risk Level

Affected Systems / Subsystems

Alternatives Considered

🏭

Change Control Board (CCB)

Governance Structure

The formal body responsible for evaluating, approving, or rejecting scope changes against programme baselines.

Chair -- Programme Manager or Chief Engineer with authority to approve/reject

Members -- Systems Engineering, Cost Estimating, Schedule Planning, Quality, Customer Rep

Cadence -- Weekly during design phases, bi-weekly during production, ad hoc for critical items

Criteria -- Impact on cost, schedule, technical performance, safety, and certification

Outputs -- Approved/rejected/deferred decision with rationale, updated baselines, action items

Golden rule -- No baseline change without CCB approval, no matter how small

Click to expand

🛡

Scope Creep Warning Signs

Early Detection

Recognise these patterns early to prevent uncontrolled growth before it derails the programme.

Gold plating -- Engineers adding features "because we can" without formal requests

Verbal approvals -- Changes agreed in hallway conversations without documentation

Requirement ambiguity -- Vague specs that different teams interpret differently

Customer additions -- "While you're at it, can you also..." requests mid-build

Integration surprises -- Subsystem interfaces that assumed different scope boundaries

Test expansion -- Test plans growing beyond what was baselined without formal review

Click to expand

❄ Requirements Freeze Checklist

Complete all 10 items before declaring the requirements baseline frozen. This protects downstream design and manufacturing work.

Module 06 -- Action Planning

Project Execution Playbook

A print-friendly summary of all frameworks, checklists, and tools from this guide. Use this as your quick-reference card for programme execution.

Aerospace Project Execution Playbook

Quick Reference Summary

01 Eisenhower Matrix

Urgent + Important = Do First (safety events, certification blockers)

Not Urgent + Important = Schedule (architecture decisions, team development)

Urgent + Not Important = Delegate (routine reports, admin requests)

Not Urgent + Not Important = Eliminate (unnecessary meetings, low-value status updates)

02 MoSCoW Prioritisation

Must Have -- Safety-critical, regulatory, contractual minimums

Should Have -- Significant value, painful to omit, has workarounds

Could Have -- Nice-to-have, include only if budget/schedule allows

Won't Have -- Explicitly deferred; documented for future increments

03 WSJF Formula

WSJF = (Business Value + Time Criticality + Risk Reduction) / Job Size

Higher WSJF = do first. Re-evaluate as conditions change

04 Estimation Rules

Always use ranges, never single points. State confidence level

PERT: E = (O + 4M + P) / 6, SD = (P - O) / 6

Cone of Uncertainty narrows from 4x at concept to 1.0x at delivery

Use reference class forecasting for large programmes

05 Meeting Rules

Every meeting needs an agenda, time-box, owner, and documented decisions

Score your meetings -- target 75%+ on the effectiveness checklist

Maintain a living decision log with clear ownership and status

06 Scope Protection

No baseline change without CCB approval

Every change request must document schedule, cost, and risk impact

Complete 10/10 on the requirements freeze checklist before baselining

Watch for gold plating, verbal approvals, and scope amnesia

07 Stakeholder Alignment

Map every stakeholder's priorities across safety, schedule, cost, and performance

Identify alignment gaps early -- misalignment > 4 points signals risk of conflict

Use the RAPID framework to clarify who Recommends, Agrees, Performs, Inputs, and Decides

Document trade-off decisions with the Iron Triangle framework -- never commit to all three constraints fixed

08 Weekly Execution Rhythm

Monday: Review priority stack rank and adjust for new information

Tuesday-Thursday: Execute against top priorities, protect focus time

Friday: Score meeting effectiveness, update decision log, review scope change requests

Monthly: Re-run WSJF scoring on backlog, update Cone of Uncertainty position, recalibrate estimates

Quarterly: Stakeholder alignment exercise, prioritisation maturity self-assessment, lessons learned

⭐ Key Principles for Aerospace Execution

Internalise these principles to guide your daily execution decisions.

🛡

Safety is Non-Negotiable

Principle 1

Safety always takes priority over schedule, cost, and performance. Any decision that compromises safety is the wrong decision.

Never pressure engineers to sign off on work they're not confident in

Build safety margin into every estimate -- it is not "padding," it is engineering prudence

Create a culture where raising safety concerns is rewarded, not punished

When in doubt, stop work and investigate. The cost of a stop is always less than the cost of a failure

Click to expand

📚

Transparency Over Optimism

Principle 2

Honest reporting of status, risks, and estimates builds trust and enables better decisions at every level of the organisation.

Report problems early -- bad news does not improve with age

Use data-driven status reporting, not subjective "green/amber/red" assessments without criteria

Admit uncertainty openly -- stakeholders respect honesty more than false confidence

Track earned value (BCWP vs ACWP vs BCWS) to give objective progress visibility

Click to expand

🔧

Discipline Enables Speed

Principle 3

Process discipline -- change control, configuration management, verification -- prevents costly rework and actually accelerates delivery.

Skipping process to "save time" creates technical debt that compounds exponentially

Configuration management prevents the "which version are we building?" crisis

Formal verification evidence built as you go is 5x cheaper than retroactive documentation

Teams with strong processes spend less time fighting fires and more time creating value

Click to expand