The Wider
Shot

How to build an indie game vertical slice that proves your idea works

A vertical slice is a short, playable section made close to the intended final quality. Its purpose is to test the game’s central promise and reveal what full production will require.

Games4 min read
A glowing orange ring above a dark volcanic sea
Original editorial illustration

An indie team wants to make a game about climbing across a flooded city. The player will travel between rooftops, rescue stranded people and decide which districts receive limited supplies. The design document describes all of this, but a potential publisher still needs to know whether climbing feels good, whether the city is readable and whether the team can build the game within its budget.

This is where a vertical slice can help.

What a vertical slice is

A vertical slice is a short section of the game that includes the main disciplines, design, code, art, animation, sound and interface, working together at or near the intended final quality. It is called “vertical” because it cuts through many layers of production in one small area.

The slice concentrates on one representative section of the game. The flooded city team might build a fifteen minute route across several rooftops, one rescue and one supply decision, leaving other districts, character types and upgrades for later production.

Decide what the slice needs to prove

List the three biggest uncertainties in the project. For this game they might be:

  • Can movement across rooftops feel fluid and precise?
  • Can players understand where to go without a large map marker?
  • Can the team create the city at the planned visual quality quickly enough?

Every part of the slice should help answer one of these questions. Include a character customisation screen only when customisation presents one of the central risks.

Create one complete play loop

The player begins with a clear goal: reach a rooftop clinic. They identify a route, climb and jump, encounter an obstruction, choose another path, rescue someone and deliver supplies. The sequence has a beginning, a series of decisions and an ending.

A complete loop tests more than the climbing mechanic. It shows whether instructions are clear, whether failure and checkpoints work, whether audio supports navigation and whether the final decision feels meaningful.

Use finished quality in a small area

Choose one representative section where character animation, environment art, lighting, effects, sound and interface reach the final target together. Other parts of the route can remain clearly labelled work in progress.

This gives the team a production measurement. If one finished rooftop takes an environment artist two weeks, the schedule for fifty rooftops must account for that. The slice is valuable even when it reveals that the original scope is too large.

Test without explaining

Give the build to players who have not heard the pitch. Watch what they do. Do they see the clinic? Do they understand which surfaces can be climbed? When they fail, do they know why?

Observe the test without offering guidance, since each explanation can hide a problem the game itself may need to solve. Afterward, ask what players thought the goal was and why they chose their route. Their answers reveal the mental model created by the design.

Connect the build to a production plan

A publisher needs more than a playable file. State who made the slice, how long it took, what remains temporary and what the next funding stage would pay for. Include milestones, team roles, platform assumptions, budget and major risks.

If the slice revealed that city production is slow, explain the response: a modular building kit, a smaller number of districts or another environment artist. A known problem with a plausible plan creates more confidence than pretending no problem exists.

When the slice is finished

Set measurable exit conditions. The route runs at the target frame rate on named hardware. New players complete it within an expected range. The climbing controls work with the planned input methods. The team knows how long representative content takes to produce.

A good vertical slice proves three things: the central experience is enjoyable, the team can deliver the intended quality and the production plan reflects what the team learned while building it.

The Wider Shot

A vertical slice turns ambition into something a team can examine. It gives creative excitement a scale, a production cost and a set of unanswered questions.

That honesty matters in an industry where small teams are often encouraged to promise enormous worlds before they have the resources to build them. We believe responsible scope is a creative strength. Funders and publishers should value teams that reveal risks and respond to evidence, while developers should treat the slice as a learning tool rather than a polished performance of certainty. Sustainable games emerge when the plan is allowed to become wiser than the original pitch.

Keep reading

All stories