Product Strategy · User Experience · Analytics · Growth
My experience spans gaming and iGaming products, combining product ownership, gameplay systems, user experience, monetisation, and cross-functional delivery. These case studies demonstrate how I approach product problems, translate user and business needs into actionable decisions, and define measurable outcomes.
CASE STUDY 01
YSECIT Software — Casino Product Retention &
Monetisation
Improving
player engagement through analytics-led product decisions
1. The problem
Casino
products operate in a competitive environment where attracting players is only
the first step. Sustained engagement, repeat sessions and a consistent player
experience are important to long-term product performance.
Across
Virtual Sports, Live Casino and Slots, the product challenge was to identify
opportunities to improve player engagement while balancing business priorities,
technical dependencies and delivery constraints.
The key
product questions were:
- Where could improvements to
the player journey reduce friction?
- Which engagement and
progression opportunities deserved priority?
- How could player behaviour
inform roadmap decisions?
- How could product changes be
evaluated against measurable outcomes?
Product
objective: Use
player behaviour insights to inform product improvements that support retention
and engagement.
2. Discovery and analysis
My
product approach connected player behaviour with prioritisation decisions
rather than treating individual stakeholder requests as the roadmap.
The
analysis framework included:
- Reviewing player behaviour
and cohort patterns using Mixpanel and Amplitude.
- Examining retention and
engagement trends across relevant player segments.
- Evaluating player journeys,
progression touchpoints and engagement mechanisms.
- Identifying opportunities
for product iteration.
- Considering business value,
engineering effort and delivery dependencies when prioritising
improvements.
The
intention was to establish a clearer relationship between observed behaviour,
product hypotheses and roadmap decisions.
3. Product decisions
I focused
on three areas of product improvement.
A. Player
journey optimisation
Evaluate
the player experience across initial and repeat sessions, looking for
opportunities to improve clarity, continuity and engagement.
B.
Engagement and progression
Assess
how rewards, progression milestones and repeat-engagement mechanisms fit into
the broader product experience, identifying opportunities for iteration.
C.
Evidence-based prioritisation
Use
behavioural insights, business priorities and implementation constraints to
determine which opportunities should enter the product backlog first.
The
guiding principle was to connect product decisions to observable user behaviour
and measurable objectives.
4. Execution and delivery
As
Product Owner, I coordinated product requirements and delivery across multiple
casino product lines and channels.
My
responsibilities included:
- Maintaining and prioritising
product roadmaps.
- Translating business needs
into product requirements and delivery-ready documentation.
- Aligning engineering, QA and
business stakeholders.
- Coordinating dependencies
across products and platforms.
- Supporting sprint planning,
UAT, release validation and delivery sign-off.
- Maintaining product
documentation to support consistent execution.
This
connected product planning with implementation, testing and release readiness.
5. Outcomes and measurement
My
existing CV draft reports the following improvements:
|
Metric |
Reported result |
|
Player
retention |
Approximately
18% uplift |
|
Player
engagement |
Approximately
22% uplift |
Important: These figures are reported in my
existing CV draft and are not independently verified in this case study. Before
presenting them as confirmed outcomes, I will validate the measurement period,
baseline, cohort definitions, calculation method and attribution to specific
product changes.
The
relevant measurement framework includes:
- D1, D7 and D30 retention.
- Average session duration and
sessions per active player.
- Feature adoption and repeat
engagement.
- Relevant conversion and
monetisation metrics.
- Experiment performance
against a defined control or baseline.
6. Key learning
Product
analytics creates value when it influences what a team builds. Connecting
player behaviour to roadmap decisions helps product teams prioritise
opportunities more systematically and align delivery effort with measurable
objectives.
Product
Management capabilities demonstrated: Roadmap ownership, product analytics,
prioritisation, experimentation, stakeholder alignment and cross-functional
delivery.
CASE STUDY 02
Insane Eagle — First-Time User Experience &
Player Progression
Designing
a clearer path from first gameplay to repeat engagement
1. The problem
A mobile
game's first session is an opportunity to communicate its value. Players need
to understand the core gameplay, experience meaningful progress and recognise a
reason to return.
When the
initial experience is confusing, progression is difficult to understand or
rewards lack context, players may disengage before discovering the product's
full value.
The
design challenge was to consider how onboarding, progression and rewards could
work together to create a more intuitive early-player experience.
Product
question: How can
the first-time experience help players understand the core gameplay loop,
achieve an early milestone and progress towards repeat play?
2. Discovery and user journey
The first
step is to map the player journey and identify where the experience may
introduce unnecessary friction.
The
journey can be assessed across six stages:
- First impression: Does the player understand
the game's purpose and appeal?
- Core mechanics: Are the essential actions
introduced clearly?
- First meaningful
interaction: Can
the player experience the core gameplay without excessive instruction?
- Initial reward: Is the outcome
understandable and satisfying?
- Progression: Can the player see what
they have achieved and what comes next?
- Next-session motivation: Is there a clear goal that
encourages continued play?
The
assessment focuses on whether players understand the next action, recognise the
value of rewards and can progress without unnecessary complexity.
Evidence
note: This is the discovery framework for the case study. Specific historical
friction points should be included only where supported by actual playtesting,
player feedback or analytics.
3. Product and design decisions
The
design approach prioritises clarity and early value before introducing
additional complexity.
A.
Simplify the initial experience
Introduce
core mechanics progressively, allowing players to learn through gameplay rather
than relying entirely on instructions.
B.
Establish an early achievement
Help
players experience a meaningful gameplay outcome early in the journey,
reinforcing their understanding of the core experience.
C.
Connect rewards to progression
Make the
relationship between gameplay, rewards and subsequent milestones easy to
understand.
D.
Clarify the next objective
Give
players a clear next goal, such as an appropriate milestone, unlock or
challenge, without overwhelming them with too many systems at once.
These are
the design principles to document against the features actually implemented in
the project.
4. Execution approach
The proposed product workflow translates the player journey into testable design and delivery requirements.
|
Workstream |
Deliverable |
|
Journey
design |
First-session
journey map |
|
Onboarding |
Tutorial
and introductory gameplay flow |
|
Progression |
Milestones
and next-step objectives |
|
Rewards |
Reward
rules and feedback |
|
Implementation |
Documented
requirements and acceptance criteria |
|
Validation |
Playtesting,
usability feedback and relevant analytics |
Design,
engineering and QA collaboration would ensure that the intended experience was
implemented consistently and tested before release.
Where
traffic and instrumentation permit, a controlled experiment can compare the
existing experience with the revised version. Usability testing can also reveal
comprehension issues before broader rollout.
5. Success metrics and validation
The
primary success metric would be Day 1 retention, supported by onboarding
and early-engagement measures.
|
Metric |
What it measures |
|
Tutorial
completion rate |
Whether
players complete the introductory experience |
|
Time to
first meaningful achievement |
How
quickly players experience core value |
|
First-session
completion |
Whether
players reach the intended early milestone |
|
D1
retention |
Whether
players return the following day |
|
D7
retention |
Whether
early engagement continues |
|
Early-session
drop-off |
Where
players leave the initial journey |
Illustrative
experiment — not a historical result
Suppose
baseline D1 retention is 28%. A proposed experiment could test whether a
revised onboarding experience increases it to 32%.
- Absolute improvement: 4
percentage points.
- Relative improvement:
approximately 14.3%.
These are
hypothetical values for illustrating experiment design, not claimed results
from the Insane Eagle project. A real result would require an appropriate
sample size, consistent cohort definitions, a predefined measurement window and
statistical evaluation.
No
verified historical retention result is asserted in this case study.
6. Key learning
Onboarding
is more than a tutorial-design problem. It is an activation problem: helping
users understand the product's value and reach a meaningful outcome with
minimal friction.
The same
principle applies to fintech, SaaS, e-commerce and subscription products, where
a successful first experience can influence continued usage.
Product
Management capabilities demonstrated: User journey mapping, activation strategy, UX
prioritisation, requirements definition, KPI selection and iterative
validation.
CASE STUDY 03
Real Steel: World Robot Boxing — Combat Experience
& Player Progression
Connecting
core gameplay with meaningful player advancement
1. The problem
In a
mobile fighting game, engaging combat is central to the experience, but players
also need a reason to continue beyond individual battles.
Progression
provides a connection between immediate gameplay and longer-term goals. When
players understand how their actions contribute to advancement, the experience
can feel more purposeful.
The
design challenge was to support an engaging combat experience while considering
how gameplay and progression fit together.
Product
question: How can
gameplay systems support a satisfying combat experience and give players a
clear sense of advancement?
2. Product discovery
A
structured design review can examine three connected aspects of the player
experience.
Combat
experience
- Are the core gameplay
mechanics understandable?
- Does the combat experience
provide appropriate feedback?
- Is the challenge suitable
for the intended player experience?
Progression
experience
- Are goals and advancement
understandable?
- Can players recognise their
progress?
- Does the experience provide
a clear sense of accomplishment?
Player
motivation
- Does the game give players a
reason to continue?
- Are gameplay outcomes
connected to meaningful goals?
- Does the experience maintain
an appropriate balance between challenge and reward?
These
questions provide a framework for reviewing the experience. They should not be
interpreted as verified findings from historical research unless supported by
project evidence.
3. Design approach
My
contribution was within game design for a licensed-IP mobile fighting game. The
portfolio should describe the specific gameplay systems and features I
personally designed, rather than attribute the entire product strategy or
commercial performance to my role.
The
relevant design principles are:
A.
Support the core combat experience
Ensure
that gameplay features reinforce the central fighting experience and remain
understandable to players.
B. Make
advancement understandable
Where
progression systems are part of the implemented feature set, communicate goals
and advancement clearly.
C.
Connect gameplay with player motivation
Consider
how gameplay outcomes and longer-term objectives work together to encourage
continued engagement.
D.
Balance clarity and challenge
Review
the relationship between feature complexity, player understanding and gameplay
difficulty to preserve an accessible but engaging experience.
Evidence
note: Specific robot upgrades, reward structures, progression rules or
difficulty-balancing decisions should be added only after confirming which
systems were part of my direct contribution.
4. Execution and collaboration
Game
design work connects creative intent with implementable requirements.
The
relevant delivery process includes:
- Defining gameplay mechanics
and feature behaviour.
- Documenting requirements and
intended player interactions.
- Collaborating with
engineering and other design disciplines on implementation.
- Reviewing gameplay behaviour
and identifying refinements.
- Supporting testing and
iteration against the intended experience.
The
precise features, tools and delivery responsibilities should be described
according to the historical project documentation and my actual role.
5. Product impact and measurement
Real
Steel: World Robot Boxing reportedly surpassed 5 million downloads within days of its October
2013 launch, according to the launch announcement referenced in my CV
draft.
This is a
title-level achievement, not a measure of the individual impact of my design
work. It demonstrates the scale of the product I worked on, but does not
establish that my contributions independently caused that reach.
No
verified feature-level retention, upgrade-adoption or progression-completion
figures are currently asserted in this case study.
For a
progression-related feature, the appropriate evaluation framework would
include:
|
Metric |
Product question |
|
Progression
milestone completion |
Are
players advancing through the intended journey? |
|
Feature
adoption |
Are
players engaging with the relevant gameplay systems? |
|
Repeat-session
rate |
Are
players returning to continue playing? |
|
Session
frequency |
Does
the experience support repeat play? |
|
D7 and
D30 retention |
Does
engagement persist over time? |
|
Player
feedback |
Are the
systems understandable and satisfying? |
These are
proposed evaluation metrics, not historical results from the project.
6. Key learning
Gameplay
design and product thinking share a common goal: create experiences that users
understand, value and want to continue using.
Clear
mechanics, meaningful feedback and appropriate progression can support
engagement. The same principles apply to learning platforms, fitness
applications and loyalty programmes, where users need understandable goals and
visible progress.
Product
Management capabilities demonstrated: Feature design, systems thinking, user motivation,
experience design, requirements definition and KPI-oriented evaluation.
My product philosophy
I
approach product development by understanding the user journey, identifying
opportunities for improvement, prioritising work against business and technical
constraints, and defining how success should be measured.
My
experience in gaming and iGaming gives me a practical foundation in engagement,
progression and monetisation. My Product Management approach builds on that
foundation through structured discovery, clear requirements, cross-functional
execution and measurable outcomes.