Why Does Stark Build More Than One Product?

Uwe Horstmann says Stark moves to more than one product because militaries describe their own capability gaps and the company does not see an abundance of offerings in the work it does.

Stark watches each gap closely while it is still being analyzed and formulated. The team then asks whether it can be a good supplier, whether it has a right to offer a solution, and whether one is already in the market. The portfolio choice follows from that exercise, and the same check reaches several products quickly. The push is almost a mandate: the team has to try, and it also has to counterbalance the complexity and loss of focus that come with multiple programs. The first reaction is still that a gap is evolving, Stark tries to contribute to how the gap is defined, and the team will probably keep asking whether it can help.

Technology and the concept of operations can move from the aerial domain to the maritime domain. Intent planning and mission planning do not change if the asset is flying or swimming. Navigation in denied environments where there is jamming happens in the maritime domain and in the aerial domain. Object detection and recognition carry over, and so does homing in on a target. Stark can reuse a lot of the work across domains, which it also calls dimensions.