Roles
Business leaders
Release on the business's schedule, not IT's.
Finished work goes live the day the business is ready — and can be stopped in seconds if it misbehaves.
- Faster to market. A feature goes live the day the business is ready, not on the next release date.
- Lower release risk. A feature that misbehaves is stopped in seconds, and the rest of the release carries on. Records already created with it, such as a policy, a claim or an exposure, stay, and the toggle decides how they are processed from then on.
- Lower cost of delivery. Less merging, shorter test cycles, and teams share environments instead of each needing its own.
- The business in control. Launch to one brand, one state or a share of customers first. Every switch is recorded: who, what and when.
- Try before you commit. Canary releases, A/B tests and pilots with one brand or market — set up by the business, without a release.
- Nothing to replace. FTF works with the LaunchDarkly or ConfigCat account you may already have.
The DORA research finds the best-performing delivery organisations are 2.3× more likely to use trunk-based development — the way of working FTF makes safe.