In aerospace and defense, the buyer and the user are rarely the same person, and the real user is often behind a clearance you can't reach. Most products get designed to a spec written by acquisition staff and never tested with the warfighter or engineer who lives with it. We run real product design and research inside human-factors, MIL-STD, and classification constraints – so you build what the mission needs, not just what the RFP says.
The Problem
Your buyer and your user are two different people
The program office writes the requirement and signs the contract, but the soldier, pilot, or maintainer is the one who actually uses what you build. When design optimizes for the acquisition spec instead of the operator, you ship something that passes the requirement and frustrates the user. That gap shows up in poor field adoption and brutal feedback during follow-on competitions. Designing to the buyer alone turns good capability into a product nobody wants to use.
Your real users are behind a clearance you can't easily reach
Standard product research means talking to users, but in defense the user may be in a classified environment, deployed, or unreachable through normal channels. So teams skip research entirely and design from assumptions, secondhand reports, and the written requirement, building a product on guesses about how the mission actually runs. The constraint is real, but treating it as an excuse to do no research is a choice that costs you in the field.
MIL-STD and human-factors requirements get treated as a checklist, not a design input
Environmental, ruggedization, and human-factors standards are not bureaucratic boxes – they encode how the product survives and gets used under real conditions. When engineering treats them as compliance to pass at the end, you bolt on fixes that compromise usability and cost. Design that integrates these constraints from the start produces something both compliant and usable. Most A&D products are designed around the standards instead of with them.
Dual-use products try to serve two masters and serve neither well
A product line meant for both commercial and defense markets often ends up compromised for both – too hardened and expensive for commercial buyers, too consumer-grade for the mission. Without a deliberate strategy for which requirements are shared and which are market-specific, engineering makes the tradeoffs implicitly and nobody owns the decision. A dual-use product without dual-use design discipline becomes a worse version of two products.
How We Help
We start by separating the buyer from the user, because in defense they are almost never the same person and designing for one at the expense of the other is the core failure mode. We map who signs the contract, who writes the requirement, and who operates the product in the field, then build a plan that serves all three without losing the operator. The first deliverable is usually a clear picture of the real user and the mission context the written requirement leaves out.
From there we figure out how to do real research inside the access constraints, because the answer is rarely no research – it is different research. We find the reachable proxies for your locked-out users: former operators now in industry, cleared advisors, training environments, unclassified analogs of the mission. The research approach respects classification and OPSEC while still putting your design decisions in contact with how the work is actually done, so the constraint shapes the method instead of killing the effort.
We treat MIL-STD and human-factors requirements as design inputs from the first sketch, not compliance to bolt on at the end. Bringing environmental, ruggedization, and human-factors constraints in from the start means usability and compliance are built together rather than fought against each other. This is where strong product design earns its keep – producing something that survives the field and that the operator actually wants to use.
We build a deliberate dual-use design strategy for product lines that serve both commercial and defense markets. We decide explicitly which requirements are shared, which are market-specific, and where the product should branch, so the line keeps the commercial version viable and the defense version mission-credible instead of becoming an unowned compromise.
We connect design and research to your broader product and marketing motion so what you learn shapes positioning, not just engineering. The insight about how operators really use the product becomes the proof points your product marketing and capture teams need, and we measure design against field adoption rather than whether the spec was met.
What we deliver
- Buyer-versus-user map – a clear separation of who signs, who specs, and who operates, with the operator kept central to design
- Constraint-aware research plan – a method to reach proxy users and mission context inside clearance and OPSEC limits
- Standards-integrated design – human-factors and MIL-STD constraints built into the product from the first sketch
- Dual-use design strategy – explicit decisions on shared versus market-specific requirements for commercial and defense lines
- Research-to-positioning handoff – field insight turned into proof points for product marketing and capture
In defense, the person who buys the product almost never uses it. Design for the program office and you pass the spec; design for the operator behind it and you win the next competition.
Our Methodology
Our engagement starts with a user-access audit rather than a design sprint. We map the buyer, the requirement-writer, and the real operator for your product, and figure out exactly which of those users you can reach and how. Most A&D teams discover they have been designing from the written requirement alone because they assumed the actual user was unreachable, when in fact reachable proxies exist.
The second phase builds the research and design approach inside the constraints. We design a method that respects classification and OPSEC while still reaching proxy users and mission context, and pull human-factors and MIL-STD requirements into the design as inputs rather than end-stage compliance. For dual-use lines we set the shared-versus-specific requirement strategy explicitly so the product does not silently compromise.
The third phase puts the work against real design decisions and measures it on adoption. Unlike a design studio that delivers concepts and leaves, we stay connected to engineering and program feedback, tracking whether the research changed decisions and whether operators adopt the result. After each cycle we tighten the method and feed field insight into positioning.
How We Work
Product design and research engagements are built around your development milestones, so the rhythm follows your design and program reviews. The first 30 to 45 days are the user-access audit and standing up a research method that works inside your clearance and OPSEC limits, after which we move into a cycle of research, design input, and validation tied to your development calendar.
The team is a strategist who understands defense buying and the buyer-user split, working with design and research specialists who can operate inside human-factors and MIL-STD constraints. You provide access to your engineering and program leads and help us reach the proxy users and advisors who stand in for your locked-out operators. We bring the research method; your team owns the engineering and standards compliance.
We run research and design reviews tied to your development milestones, with each round of field or proxy insight feeding the next design decision. Because access is hard-won, the proxy networks we build compound across the program – the second study is faster and sharper than the first. Most A&D teams see value within the first design cycle, as research surfaces operator realities the written requirement missed.
- Operator-centered design – products built for the user behind the requirement, not just the acquisition spec
- Research inside the line – real user and mission insight gathered within clearance and OPSEC constraints
- Built-in compliance – human-factors and MIL-STD requirements integrated as design inputs, not bolted-on fixes
- Coherent dual-use lines – explicit design strategy that keeps both commercial and defense versions credible
If your aerospace & defense company needs product design & research leadership, we should talk.
Expand your marketing team output with our experts
Let us take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.
Frequently asked questions
How do you do user research when our actual operators are behind a clearance?
We rarely need to reach the classified user directly. We find reachable proxies – former operators now working in industry, cleared advisors, training environments, and unclassified analogs of the mission – and design a research method around them. That respects classification and OPSEC while still putting your design decisions in contact with how the work is actually done. The constraint changes the method, not the existence of real research.
Why does the buyer-versus-user gap matter so much in defense product design?
In defense the program office writes the requirement and signs the contract, but the soldier, pilot, or maintainer actually uses the product. If you design only to the acquisition spec, you can pass the requirement and still ship something the operator hates – which shows up as weak field adoption and harsh feedback in the next competition. Keeping the operator central to design is how you win the follow-on, not just the first award.
How do you handle MIL-STD and human-factors requirements in the design process?
We treat them as design inputs from the first sketch rather than compliance to pass at the end. Environmental, ruggedization, and human-factors standards encode how the product has to survive and be used in the field, so designing with them produces something both compliant and usable. Bolting fixes on at the end compromises usability and adds cost. Integrating the standards early makes them the shape of the product instead of a tax on it.
What makes Winston Francois different from a traditional design or research agency?
Most design agencies have never worked inside clearance limits, MIL-STD constraints, or the buyer-user split that defines defense products. We operate from an operator-first mindset and stay connected to your engineering and program feedback rather than delivering concepts and leaving, measuring success by field adoption and competition feedback instead of a polished deliverable. The difference is research and design that actually changes engineering decisions inside real defense constraints.
How do you measure the ROI of product design and research in defense?
We measure whether the research actually changed design decisions and whether those changes improved real outcomes – field adoption, usability as an advantage in competitions, and fewer late-stage compliance fixes. We track which insights moved engineering and which design choices held up with operators. The point is design that earns its keep in the field and in the next award, not a study that sits on a shelf.
What type of aerospace and defense company is the right fit for this service?
This fits suppliers building products that real operators use – especially those designing primarily to the written requirement because they assumed the user was unreachable. If you have a dual-use line silently compromising for both markets, there is usually real value to capture. The first step is a user-access audit that maps your buyer, requirement-writer, and operator, and finds the reachable proxies you can research.
