Shape
Turn concepts into decisions
Converted rough creative ideas into scoped tasks, prototypes, game-design documentation, roadmaps, milestones, dependencies, budgets, and release plans.
01 / At a glance
A production system for a game, a world, an economy, and a community.
- Company
- Wilder World
- Project
- Open-world, racing, and combat game production
- My role
- Game-production and technical program lead
- Scope
- Technical Project Management · Creative Production · Go-to-Market Operations · Community & Ecosystem
- Release model
- Three integrated roadmaps spanning concept, art, design, engineering, QA, launch, and support
- Operating environment
- Distributed art, design, engineering, QA, marketing, community, and technical-vendor teams
02 / The world
The production system had to carry cinematic ambition into playable releases.
Original portfolio video
Midnight in Wiami — Wilder World teaser
Midnight in Wiami — Wilder World teaser
Environment and world-building scope
Community, platform, and launch roadmap
03 / The problem
The studio was building a game, a world, an economy, and a community simultaneously.
Wilder World combined cinematic art direction, open-world environments, action combat, competitive racing, customizable avatars, blockchain ownership, token utilities, and an active player community.
Art, game design, engineering, QA, product, marketing, community, and vendors were moving concurrently from concepts that were still evolving. Without a shared production system, the team risked overloading resources, missing dependencies, and carrying unclear ideas too far into development.
The plan had to create clarity without freezing a game that was still becoming itself.
04 / What I owned
I owned the connective tissue across the entire game-production lifecycle.
Ship
Synchronize production
Connected game design, art, engineering, QA, production, marketing, community, and vendors while balancing visual ambition against technical and resource constraints.
Learn
Close the release loop
Owned playtesting, bug prioritization, release readiness, support planning, and the feedback loops that moved player insight into updates and future roadmaps.
05 / The lifecycle
The production model changed with the work instead of forcing every phase into the same process.
Turn possibility into decisions
Defined scope, responsibilities, platforms, tools, mechanics, story, characters, art direction, budgets, constraints, and the prototypes needed to validate the direction.
Keep art, design, and engineering synchronized
Managed milestones, sprints, resources, assets, code, scope changes, creative reviews, performance constraints, playtesting, bugs, and cross-discipline decisions.
Ship, listen, and plan the next release
Coordinated readiness, optimization, patches, content updates, marketing, platform delivery, community feedback, and future downloadable content.
06 / The production system
One operating loop carried evolving ideas into testable, releasable game modes.
The workflow gave every discipline shared decision points while preserving room for creative iteration.
01
Frame
Vision + scopeMake the idea actionable. Define the player experience, release objective, scope boundaries, decision owners, resources, and success conditions.
02
Prototype
Mechanics + gameplayUse failure early. Test core mechanics, interactions, and technical assumptions before they become expensive production commitments.
03
Plan
Roadmap + dependenciesConnect the disciplines. Build milestones and task systems across art, design, engineering, QA, platforms, marketing, community, and vendors.
04
Produce
Assets + codeKeep the shared plan current. Manage sprints, resources, asset production, code delivery, scope change, performance constraints, and creative reviews.
05
Validate
Playtest + QAAdvocate for the player. Coordinate playtesting, bug tracking, polish, usability, visual quality, and release risk across the team.
06
Release
Launch + supportShip and reopen the loop. Align production, platform, marketing, and community; then turn performance and player feedback into the next roadmap.
07 / Launch + learning
Community feedback was not a postscript. It was production input.
The operating principle
Release readiness connected production, QA, platform, marketing, and community teams. After launch, player concerns, engagement, and technical performance became prioritized inputs for fixes, updates, expansions, and downloadable content.
08 / What shipped
Three major releases moved through one connected production lifecycle.
- Three game releasesRacing, combat, and open-world gameplay delivered through coordinated roadmaps
- 1,000+ assets and tasksProduction work, dependencies, and decisions tracked across the program
- #9 on Epic wishlistA clear market signal for the title during its development and launch journey
- One release systemPlanning, asset production, code, playtesting, QA, marketing, and community feedback connected
The durable outcome: an evolving, distributed studio gained a repeatable way to move ambitious game concepts through production without separating creative vision from technical reality.
09 / What this proves
I can lead creative-technical work when the product is still becoming itself.
Technical Project ManagementOwned the lifecycle across three roadmaps, dependencies, resources, QA, release readiness, and post-launch support.
Creative ProductionProtected cinematic ambition while translating concepts into assets, mechanics, technical constraints, and achievable milestones.
Go-to-Market OperationsConnected platform, marketing, launch, community, and production readiness around major releases.
Community & EcosystemTurned player feedback and engagement into prioritized work for fixes, updates, and future content.
Structure without rigidity is the real game-production skill.
Enough clarity to protect delivery, enough technical understanding to surface real constraints, and enough creative judgment to know when exploration is part of the work.