Principles

Constructive irreverence. The willingness to kill existing processes. To look a client executive in the eye and say: we are not going to build an AI tool to help your team process these forms 40% faster. We are going to build a system that eliminates the need for these forms to exist entirely.

Outcome advocacy over user advocacy. Traditional UX minimizes user effort within the current task. FDD goes one level higher. Sometimes the right design is not to make the current job easier, but to eliminate the task and move the human into governance, judgment, or relationship work.

Political literacy. Workflows are not merely sequences of tasks; they are settlements among departments, professions, budgets, regulators, unions, managers, and status hierarchies. A field designer who cannot read the informal power map will mistake an org chart for an operating system. The real workflow is hidden in who can say no, who can override the system, and which spreadsheet everyone trusts more than the official dashboard.

Comfort with ambiguity. Pre-AI software is deterministic. AI is probabilistic, generative, and non-deterministic. FDD designs systems that accommodate flexible, conversational, or agentic interactions rather than rigid, linear pathways.

Proximity to mandate. "Forward deployed" is ultimately a metaphor for proximity to mandate: the authority to actually remove blockers and retire old workflows. Without that mandate, embedding is just tourism.