What are the key takeaways from this The Product Experience episode?

Key insights include: **Integrative Decision Making Process:** When managing 10 founding customers plus regulators, split stakeholders into streams by audience (pilots, cabin crew, mechanics, quality departments). Use a structured process: present proposal, clarify questions, reaction round, amend and clarify, voting, then final decision with objection handling. This heavy workshop approach achieved consensus across competing interests and regulatory requirements for aviation software approval.; **Mandatory End User Involvement:** Contract founding customers to provide representative end users from each stakeholder group for every workshop session. Swiss Aviation hired an actual captain during the pandemic to co-create concepts and present to other pilots. Without direct pilot involvement from concept phase, the product would have failed to address real cockpit conditions like cold weather, five-finger glove use, and bright sunlight visibility issues.; **Under Commit and Triple Validate:** Limit scope to maximum five founding customers instead of 10, and validate in three distinct phases: pre-development with prototypes, during development with key users, then in real operational conditions on the tarmac and in cockpits. Test extreme scenarios like outstation connectivity loss, pilots who haven't logged in for three months, and actual flight delays rather than happy path lab environments.

What did Cristina Bustos discuss on The Product Experience?

Cristina Bustos, Product Manager at Swiss Aviation Software, details building their first mobile native application for pilots during the pandemic. The case study covers managing 10 founding customers, securing regulatory approval from European aviation authorities, replacing paper processes with digital workflows, and navigating the complex stakeholder landscape of pilots, cabin crew, mechanics, and regulators. Key topics include: **Integrative Decision Making Process:** When managing 10 founding customers plus regulators, split stakeholders into streams by audience (pilots, cabin crew, mechanics, quality departments). Use a structured process: present proposal, clarify questions, reaction round, amend and clarify, voting, then final decision with objection handling. This heavy workshop approach achieved consensus across competing interests and regulatory requirements for aviation software approval.; **Mandatory End User Involvement:** Contract founding customers to provide representative end users from each stakeholder group for every workshop session. Swiss Aviation hired an actual captain during the pandemic to co-create concepts and present to other pilots. Without direct pilot involvement from concept phase, the product would have failed to address real cockpit conditions like cold weather, five-finger glove use, and bright sunlight visibility issues..

How long is this episode of The Product Experience?

This episode is 33 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

The Product Experience

Building products for pilots: a case study - Cristina Bustos (Swiss AviationSoftware)

January 21, 2026

33 min episode · 2 min read

Cristina Bustos

Episode

33 min

Read time

2 min

Topics

Relationships, Leadership, Design & UX

AI-Generated Summary

Published Jan 21, 2026

Key Takeaways

✓Integrative Decision Making Process: When managing 10 founding customers plus regulators, split stakeholders into streams by audience (pilots, cabin crew, mechanics, quality departments). Use a structured process: present proposal, clarify questions, reaction round, amend and clarify, voting, then final decision with objection handling. This heavy workshop approach achieved consensus across competing interests and regulatory requirements for aviation software approval.
✓Mandatory End User Involvement: Contract founding customers to provide representative end users from each stakeholder group for every workshop session. Swiss Aviation hired an actual captain during the pandemic to co-create concepts and present to other pilots. Without direct pilot involvement from concept phase, the product would have failed to address real cockpit conditions like cold weather, five-finger glove use, and bright sunlight visibility issues.
✓Under Commit and Triple Validate: Limit scope to maximum five founding customers instead of 10, and validate in three distinct phases: pre-development with prototypes, during development with key users, then in real operational conditions on the tarmac and in cockpits. Test extreme scenarios like outstation connectivity loss, pilots who haven't logged in for three months, and actual flight delays rather than happy path lab environments.
✓Strict Process Documentation Requirements: In regulated aviation environments, document and version every business process and use case with formal review and approval stamps. When any element changes, reapprove the entire process. This applies to default workflows and each customer's specific version. Agile user stories for conversation are insufficient; aviation authorities require written, stamped, versioned documentation for compliance and regulatory approval letters.
✓Real-Time Data Integration Benefits: Digital cockpit applications enable mechanics to receive issue reports nine hours before aircraft landing, plan repairs during next shift, and have replacement parts ready upon arrival. This eliminates paper-based delays where mechanics must physically retrieve documents, verify issues, check parts inventory, and order missing components. The system also removes three tons of paper annually per customer while enabling predictive maintenance through consistent data collection.

What It Covers

Cristina Bustos, Product Manager at Swiss Aviation Software, details building their first mobile native application for pilots during the pandemic. The case study covers managing 10 founding customers, securing regulatory approval from European aviation authorities, replacing paper processes with digital workflows, and navigating the complex stakeholder landscape of pilots, cabin crew, mechanics, and regulators.

Key Questions Answered

•Integrative Decision Making Process: When managing 10 founding customers plus regulators, split stakeholders into streams by audience (pilots, cabin crew, mechanics, quality departments). Use a structured process: present proposal, clarify questions, reaction round, amend and clarify, voting, then final decision with objection handling. This heavy workshop approach achieved consensus across competing interests and regulatory requirements for aviation software approval.
•Mandatory End User Involvement: Contract founding customers to provide representative end users from each stakeholder group for every workshop session. Swiss Aviation hired an actual captain during the pandemic to co-create concepts and present to other pilots. Without direct pilot involvement from concept phase, the product would have failed to address real cockpit conditions like cold weather, five-finger glove use, and bright sunlight visibility issues.
•Under Commit and Triple Validate: Limit scope to maximum five founding customers instead of 10, and validate in three distinct phases: pre-development with prototypes, during development with key users, then in real operational conditions on the tarmac and in cockpits. Test extreme scenarios like outstation connectivity loss, pilots who haven't logged in for three months, and actual flight delays rather than happy path lab environments.
•Strict Process Documentation Requirements: In regulated aviation environments, document and version every business process and use case with formal review and approval stamps. When any element changes, reapprove the entire process. This applies to default workflows and each customer's specific version. Agile user stories for conversation are insufficient; aviation authorities require written, stamped, versioned documentation for compliance and regulatory approval letters.
•Real-Time Data Integration Benefits: Digital cockpit applications enable mechanics to receive issue reports nine hours before aircraft landing, plan repairs during next shift, and have replacement parts ready upon arrival. This eliminates paper-based delays where mechanics must physically retrieve documents, verify issues, check parts inventory, and order missing components. The system also removes three tons of paper annually per customer while enabling predictive maintenance through consistent data collection.

Notable Moment

The team conducted shadow flights where pilots performed official processes on paper while simultaneously testing the new application without any training. This parallel run approach intentionally tried to make the system fail in real cockpit conditions with actual delays, connectivity issues, and operational pressures. The findings were reported directly to European aviation authorities as part of securing the nontechnical objection letter required for regulatory approval.

Know someone who'd find this useful?