Real stories from shipped and in progress games

Before committing to a study, it helps to see how the work actually lands inside real projects. These case studies trace the path from early warning signs in analytics or community feedback, through structured usability testing, to the specific design changes teams shipped as a result.
View services

Selected projects across genres and platforms

Each project here started with a vague unease: players were leaving too soon, getting stuck in odd places, or describing the game with words that did not match the team’s intent. Through a mix of usability testing, analytics review, and structured feedback loops, we helped teams turn that unease into specific, testable hypotheses and practical design decisions.
casual mobile puzzle game interface

Casual puzzle onboarding reset

This casual puzzle project arrived with a polished art style, clever core mechanic, and worrying early metrics. Most players installed, tapped through a few tutorial screens, then quietly left. Our role was to unpack that silence. Through short remote playtests, diary style follow ups, and a close read of onboarding events, we discovered that players were being asked to memorise rules before they ever felt a satisfying move. By reordering steps, trimming non essential explanations, and introducing a clear first win within two minutes, the team saw more players reaching level clusters where the game’s personality really emerged. Feedback shifted from “confusing” to “addictive in a good way,” and support tickets about stuck tutorials dropped noticeably.
cooperative action game squad session

Co op retention and squad cohesion

A cross platform co op title with layered systems needed help understanding why new squads failed to stick together. Match data showed early disconnections and abandoned runs, yet session length looked healthy for a small subset of players. We ran in person and remote squad sessions, capturing both group dynamics and individual perspectives. The issue was subtle. Players who already knew similar games carried over mental models that masked onboarding gaps, while newcomers felt lost in role expectations, map flow, and communication tools. Our recommendations focused on a short, guided first run with clear shared goals, better surfacing of quick chat options, and more generous early checkpoints. The team implemented changes over several updates, using our reports as a north star for squad cohesion. Subsequent tests showed players describing runs as “chaotic, but in a good way,” rather than simply chaotic.

From confusing tutorial to confident first session

Mobile puzzle onboarding

A mobile puzzle team came to us with a familiar complaint: early analytics showed a steep drop during the first ten minutes, yet no one could agree on why. Designers believed the tutorial was already too simple. Product leads worried that cutting steps would hide important mechanics. Our task was to replace guesswork with clear evidence. We ran a series of remote moderated sessions with players new to the genre, combining screen recordings, think aloud prompts, and short post session interviews. We tagged every hesitation, skipped tooltip, and restart, then layered this with event data from the live build. The pattern was sharp. Players were reading, not playing, for far too long. Key mechanics were introduced in isolation, without the small moments of success that anchor learning. We proposed a reshaped flow using what we call our ramp and reward pattern: teach through tiny, winnable challenges, then explain only what the player has already felt. After two design iterations and a follow up test, more players reached the first meaningful puzzle, reported less confusion, and described the game as “clever, not exhausting.”

Balancing action, information, and visual noise

A PC action title with a complex HUD was struggling with mid game retention. Players who pushed past the opening hours tended to stay, but many never made it that far. The team suspected difficulty spikes, yet combat metrics alone could not explain the churn. We designed a mixed study: lab based play sessions focused on combat encounters, followed by targeted surveys and a review of anonymised heatmaps. During sessions, we noticed a recurring pattern. Players were not failing because enemies were strong; they were failing because they could not parse health, cooldowns, and objectives quickly enough. Eyes darted between corners of the screen, while key audio cues went unnoticed. In our report, we mapped eye movement, input timing, and death moments onto a simple visibility matrix, then suggested a phased HUD approach. Early hours would show only essentials, gradually layering advanced information once players demonstrated comfort with the basics. We also recommended clearer feedback for low health and cooldown readiness. After implementation and another round of testing, players described combat as intense but readable, and far more of them reached the narrative hooks the writers had crafted.
We were drowning in dashboards and still arguing about what was actually going wrong. The sessions with Wislaimasoascusi gave us a shared language. Instead of “players are confused,” we had clips, timelines, and clear patterns. That made it much easier to prioritise changes without derailing the roadmap.
Meera Kulkarni, Senior Game Producer

Production lead on a live mobile title, working with Wislaimasoascusi across several update cycles to refine onboarding and live event clarity.

Meera Kulkarni
Across recent projects

What our recent usability studies add up to

These aggregated figures span a mix of mobile, PC, console, and VR projects. They reflect a young studio focused on depth over volume, using each round of testing to reduce recurring usability issues and refine how quickly teams can move from confusing moments to confident design decisions.

See how other teams turned vague player frustration into concrete, testable changes

Looking at other teams’ usability journeys is a safe way to pressure test your own plans. These case studies show how small, focused studies can surface the quiet friction points that analytics alone struggle to explain, and how structured iteration can turn confusing moments into confident play without flattening your creative intent.

Bring your game, your doubts, and your constraints to the table

If you recognise fragments of your own game in these stories, the next step is simple. Share where players are slipping away, what you have already tried, and which constraints you cannot change. We will outline a study design that fits your timeline, your build stability, and your appetite for iteration, so each round of testing moves you closer to the experience you want players to remember.

Start a project