Writing Defence delivery

Why I'm writing

A short note on what this site is for, who it is for, and the three threads I intend to follow.

· 1 min read

For fifteen years my writing has gone into documents other people read behind closed doors: CONOPS, interface specifications, test plans, proposals. Almost none of it was meant for a wider audience, and most of it never could be. This site is an attempt to write down the part that can be shared.

I lead the C2/CUAS and Border Surveillance product lines at a UAE defence technology company in Abu Dhabi. Before that I spent seven years at Embraer and Saab, and four years running product and technical operations teams across Austria, China and the UK. Along the way I have formed some opinions, and I would rather test them in public than keep them to myself.

Three threads will run through everything here:

  1. AI-enabled mission systems. Where detection, sensor fusion and decision workflows genuinely change what an operator can do, and where they only look good in a demo.
  2. Technical leadership of distributed teams. What it takes to run engineering and customer-facing technical people across borders and time zones, and to build local capability rather than dependency.
  3. How defence programmes really get bought and delivered. Requirements, demonstrations, proposals, acceptance: the long arc from a first conversation to a fielded system.

I will keep it short, first-hand, and free of customer and programme specifics. If something here is useful, or you think I have got it wrong, I would genuinely like to hear it. LinkedIn is the easiest place to find me.

Follow on LinkedIn Written by Giovani Lucasech. Views are my own; no customer or programme specifics are discussed.