The first 90 days should test the operating model that the company hired for. A generic onboarding plan delays the moment when role assumptions meet real deployment work.
Days 1–30: build the system map
The new FDE should understand the product surface, customer workflow, production environment, decision owners and current deployment failure modes. Pair documentation with observation: join customer calls, inspect incidents and trace one feature from request to use.
Days 31–60: ship a thin deployment slice
Choose work small enough to complete but rich enough to expose real interfaces. The objective is not an impressive standalone project. It is evidence about discovery, scoping, technical constraints and the support the role actually receives.
Days 61–90: establish the learning loop
Complete the deployment, inspect adoption and turn one repeated field pattern into a product, tooling or playbook improvement. Review where ownership was unclear and update the role contract.
Run a 90-day operating review
- Which assumptions in the original brief were wrong?
- Where did work wait on another team?
- Which evidence dimension was more important than expected?
- What field learning is now reusable?
- What should the next deployment do differently?
Use the first 90 days to validate the FDE system, not only the individual. If the role succeeds through heroics, the operating model still needs repair.
© 2026 Balncs. This article may be shared with attribution. It is general information, not legal, financial or employment advice.