Delivery Under Constraint
Shipping inside someone else's world
You ship into an environment you don't control: their security review, their VPN, their change window, their fifteen-year-old schema, their procurement process. Speed here has almost nothing to do with how fast you type and almost everything to do with seeing what will block you three weeks from now.
Progression
What changes at each level.
- FDE I
Deployed
Works effectively within an environment someone else set up. Raises blockers early and specifically. Follows the customer's process for access, review, and deployment without needing reminders.
- FDE II
Embedded
Anticipates environmental blockers for their workstream and clears them ahead of need. Gets something demonstrable working early, even against incomplete access or partial data. Documents and hands over what they built so the customer is not dependent on them for routine operation.
- FDE III
Trusted
Owns the delivery path for an account: sequencing around freeze periods, security review, procurement, and competing internal projects. Consistently produces visible value before the environment is fully ready, which is what keeps a sceptical stakeholder engaged. Builds the operational hand-off in from the start.
- FDE IV
Principal
Changes what is possible to deliver, not just what gets delivered. Establishes the patterns, tooling, and pre-cleared paths that shorten every future deployment. Handles the environments others consider undeliverable, and turns what was learned there into something the next person inherits.