Vertical slice
Building one complete thread of a product end to end, data to screen for one role or feature, before starting the next, instead of all databases first and all screens last.
Updated October 2026 · with examples from our own builds
What does vertical slice mean in practice?
A vertical slice delivers something usable on its own: the data model, the API, the screens and the tests for one role or feature. The next slice builds on it, and progress is counted in working slices rather than in layers that only work once all of them are finished.
Progress becomes visible and testable early. Each slice can be demonstrated, checked against the plan and corrected before the next begins, and if the budget runs short, what exists actually works.
The discipline is finishing each slice properly, tests included, and building data before the screens that read it.
Vertical slice at a glance
- Each slice includes
- Data, API, screens and tests
- Benefit
- Working software at every stage
- Order
- Data before the screens that read it
Where has vertical slice come up in our builds?
We build the real app one role-complete slice at a time, data before the screens that read it. Nine slices, from invitation-only sign-in to the product-kinds model, are built, each with its own battery of API checks, scripted browser click-throughs or both.
After the 44-document plan, the platform was built in slices, each verified by an API probe and a scripted browser walk before the next began.
Common questions about vertical slice
Why not build the whole database first?
Because a database without screens can't be tried by anyone, and mistakes in it only surface when the screens arrive. Building slice by slice tests each part of the data model as soon as it exists.
Can I see progress after each slice?
You should be able to use it. A slice that can't be demonstrated with real screens and data isn't finished.
Related terms
Planning a product and not sure where vertical slice fits? Ask us, or browse all 116 terms in the glossary.