Video Game Product Roadmap: From Concept to Launch and Live Ops

7 min read ยท 2026-10-08

A video game product roadmap is built around one question that software roadmaps rarely face: is it fun? Every phase, from concept to live operations, should either prove the core loop is enjoyable or scale content around a loop that already is. Teams that skip this test early often spend months producing art and levels for a game nobody wants to keep playing.

This roadmap covers a one-year plan for a small or mid-sized team in six phases: concept, prototype, vertical slice, production, launch and live ops. Each phase includes typical deliverables, a gate milestone and the metrics to watch, plus guidance on scope control, playtesting, marketing timing and post-launch content.

The roadmap at a glance

Goal: Ship a commercially viable video game and sustain it with post-launch updates driven by player data. Duration: 12 months

  1. Concept (Month 1)

    Define the game's core fantasy, target audience and scope that fits the team.

    • Write a one-page pitch covering genre, core loop, hook and target player.
    • Research comparable titles on Steam, consoles or mobile and study their reviews.
    • Choose an engine such as Unity, Unreal or Godot based on team skills and platform.
    • Estimate scope with a content list and compare it to team capacity honestly.
    • Define target platforms and whether the game is premium or free-to-play.

    Milestone: An approved pitch with a scoped feature list the team believes it can ship.

  2. Prototype (Months 2-3)

    Find the fun by testing the core loop with placeholder art.

    • Build several rough prototypes of the core mechanic using greybox assets.
    • Playtest with people outside the team and watch without explaining anything.
    • Measure whether testers want to play again after a session ends.
    • Cut prototypes that do not produce engagement and iterate on promising ones.
    • Document the core loop, controls and feel that make the game work.

    Milestone: Outside playtesters ask to keep playing a greybox prototype of the core loop.

  3. Vertical Slice (Months 3-5)

    Build a short, polished section that represents final quality.

    • Produce one level or session at near-final art, audio and UI quality.
    • Establish the art pipeline, naming conventions and asset budgets.
    • Set up version control with Git LFS or Perforce and an automated build pipeline.
    • Launch a Steam page with a capsule image, trailer and wishlist button.
    • Use the slice to pitch publishers or apply to festivals and showcases.

    Milestone: A vertical slice that plays at target quality and a live store page collecting wishlists.

  4. Full Production (Months 5-9)

    Produce the full content set and reach a feature-complete alpha.

    • Build levels, characters, items and systems from the locked content list.
    • Run regular playtests and use telemetry to find difficulty spikes and drop-off points.
    • Implement save systems, settings, accessibility options and controller support.
    • Release a demo for events like Steam Next Fest to grow wishlists.
    • Hold a scope review each month and cut features that threaten the date.

    Milestone: Alpha build with all features implemented and the game playable start to finish.

  5. Polish and Launch (Months 9-11)

    Reach beta quality, pass platform requirements and launch on schedule.

    • Fix bugs by severity and optimize performance on minimum spec hardware.
    • Run a closed beta or early access to test stability with real players.
    • Complete platform certification requirements for consoles if applicable.
    • Send keys to press and content creators ahead of launch.
    • Prepare launch trailer, store assets, community channels and a day-one patch plan.

    Milestone: Gold build approved and the game launched on all target platforms.

  6. Live Ops (Months 11-12)

    Retain players and grow the audience through updates based on real data.

    • Monitor crash reports, reviews and community feedback daily after launch.
    • Ship quick patches for top bugs and balance issues.
    • Publish a public post-launch roadmap of updates and content drops.
    • Plan seasonal events, DLC or new modes based on what players engage with most.
    • Use sales events and platform features to bring in new players.

    Milestone: Stable review score and a first content update shipped on the announced date.

Finding the Fun Before Spending on Content

The most expensive mistake in game development is producing polished content around a core loop that is not engaging. Prototypes should be ugly and fast. Use greybox levels, simple shapes and placeholder audio, and focus entirely on whether the core action feels good and creates a reason to keep going.

Playtest with people who match your target audience and do not know the game. Watch where they get confused, bored or excited, and resist explaining things. A strong signal is a tester asking to play again or describing a strategy they want to try next time. If prototypes do not produce that reaction, iterate or pivot before moving to the vertical slice.

Controlling Scope

Scope creep is the classic reason games miss their dates. Lock a content list after the vertical slice and treat every addition as a trade-off against something already planned. Separate features into must have, nice to have and post-launch buckets, and protect the launch date by moving items into the post-launch bucket aggressively.

A vertical slice is also your best estimation tool. Measure how long it took to produce one level, enemy or area at final quality, then multiply by the content list. If the math does not fit the schedule, cut content now rather than crunch later. Smaller games finished well usually outperform larger games shipped rough.

  • Lock the content list after the vertical slice.
  • Estimate production using real slice timings.
  • Run monthly scope reviews with the whole team.
  • Move uncertain features into the post-launch plan.

Marketing Timing and Wishlists

Marketing a game starts long before launch. For PC games, a Steam page should go live as soon as you have a compelling capsule image and trailer, typically around the vertical slice. Wishlists accumulate over months, and wishlisted players get notified at launch, which helps visibility in the store.

Plan beats throughout production: announcement trailer, festival appearances, a demo during Steam Next Fest, content creator outreach and a launch trailer. Share development progress on social platforms and build a Discord community for your earliest fans. These players become playtesters, bug reporters and advocates at launch.

Metrics to Track Before and After Launch

Before launch, track wishlist growth, demo playtime, demo completion rate and playtest feedback themes. Use telemetry in playtests to see where players quit, die repeatedly or get lost. These signals point directly at design and difficulty problems.

After launch, watch day 1, day 7 and day 30 retention, average session length, review score, refund reasons, crash rates and, for free-to-play games, conversion and revenue per daily active user. Segment metrics by platform and acquisition source. A spike in negative reviews often points to a specific bug or design issue you can fix quickly.

Variations by Business Model and Platform

Premium games invest most heavily before launch and use post-launch updates to sustain reviews and sales. Free-to-play games need monetization, progression and live ops systems from early production, plus a soft launch in select regions to tune retention and economy before global release.

Console releases add platform certification, age ratings and dev kit access to the roadmap, while mobile games add app store optimization, device fragmentation testing and ad monetization decisions. Early access on Steam can work well for systemic games like roguelikes or simulations, letting players shape development, but it requires a reliable update cadence and transparent communication.

Common mistakes to avoid

  • Producing final art before the core loop is fun; prove engagement with greybox prototypes first.
  • Adding features throughout production; lock the content list after the vertical slice and move extras to post-launch.
  • Launching the Steam page too late; publish it around the vertical slice to collect wishlists for months.
  • Playtesting only with friends and teammates; test with target players who will be honest and unfamiliar with the game.
  • Ignoring performance until the end; profile on minimum spec hardware throughout production.
  • Going silent after launch; publish a post-launch roadmap and ship fixes and updates on the dates you announce.

Frequently asked questions

How long does it take to make a video game?

It depends heavily on scope and team size. A small indie game with a tight scope can be built in about a year, while larger projects take several years. The vertical slice is the best estimation point, because it shows how long final-quality content actually takes your team to produce.

What is a vertical slice in game development?

A vertical slice is a short, playable section of the game built at near-final quality across art, audio, gameplay and UI. It proves the team can deliver the target experience, sets the production pipeline and gives a realistic estimate for the rest of the content. Publishers often request one.

When should I launch my Steam page?

Launch the Steam page once you have a strong capsule image, screenshots and a short trailer that shows real gameplay, often around the vertical slice. Earlier pages give wishlists more time to accumulate, but a weak page can hurt first impressions, so prioritize quality assets.

Which game engine should I use?

Choose based on team experience, target platforms and genre. Unity is widely used for mobile and indie projects, Unreal Engine is strong for high-fidelity 3D, and Godot is a popular open source option for 2D and smaller 3D games. Prototype in your chosen engine early to confirm it fits.

What should a post-launch game roadmap include?

A post-launch roadmap should include bug fix and stability patches, balance updates, quality of life improvements requested by players and planned content such as new levels, modes, seasonal events or DLC. Publish it publicly with approximate timing to keep players engaged and show the game is actively supported.

Generate this roadmap with AI