A drone is only as useful as the answer it brings back. Yet in practice, drones are often chosen first and given a mission afterwards, and the gap only shows up in the field. This keynote argues for the opposite: start from what the mission needs to deliver; turn those needs into clear, measurable requirements; and let them shape the aircraft. That means its configuration, size, payload and the way it flies.
The talk follows this idea through three situations that operators face in practice:
- One mission that demands a purpose-built aircraft;
- Many missions served by a single multipurpose platform;
- Missions that change over time, handled by an aircraft designed to be reconfigured.
Each case draws on systems that were designed, built and tested in real operating conditions, from geophysical surveying to emergency response. Together, they show how a single requirement can drive the whole design, why flexibility is never free, and how to decide how much of it a mission really needs.
The talk then brings these lessons together in a simple map for choosing between dedicated, multipurpose and reconfigurable designs. It closes with the open challenges that still separate a working prototype from a reliable tool that people trust in their daily work.