Home / Lessons / Choose the problem / 3 of 27

Stop building frontend, backend, then database

Three finished layers can add up to nothing a user can do.

Built in layersOne vertical sliceUserFrontend, finishedBackend, finishedDatabase, finishedVisible resultNothing works end to endUser actionInterfaceAPIDatabaseVisible resultOne complete journey works

normal movementretry or blockedmy decisionwritten, shared statestopped

In a layer-by-layer build, the interface gets finished, then the backend, then the database. Each one looks done. No user can complete a single task, and the risk of joining them stays hidden until late.

In a vertical slice, the team builds one narrow path through every layer it needs. It starts with something a user does and ends with something they can see. The slice is small, and it works as a product.

How I do it

Every piece of work I hand to agents is cut this way: user action, interface, API, database, visible result.

The rule

Cut work by what a user can do, never by technical layer.

The skill I use for this: /principle-sequence-verifiable-units. Made by Lauren Tan.

Read next

The ideas behind it

This lesson as plain text, for your agent. Or all 27 on one page.

Try “secrets”, “merge”, “handover” or “database”.