Case Study

Case Study

Case Study

AJAX Beta Testing Platform

AJAX Beta Testing Platform

AJAX Beta Testing Platform

Interface

Interface

Desktop/Web Application

Desktop/Web Application

Desktop/Web Application

Role

Role

Role

Product & UX/UI Designer

Product & UX/UI Designer

Product & UX/UI Designer

Timeline

Timeline

April 2025 - May 2025

April 2025 - May 2025

April 2025 - May 2025

Perth Park is a major city-shaping activated precinct
development located at Burswood Park, designed to expand
Western Australia’s capacity to host world-class sport,
entertainment and cultural events.

This project was part of the Product Design course at
Projector Institute, where we worked with AJAX Systems
to design dedicated platform solution for their Beta
testing program.

AJAX Systems is the largest security systems
manufacturer in Europe. Before launching new devices
AJAX conduct an open beta testing with real end users in
real-world environment, alowing the team to polish
devices and experience based on real world usage data.
But thats where the problems begin - the program is
scattered across different flows, causing problems and
inefficiency. AJAX need new, dedicated solution.

The buildings that Populous designs are formidable in both scale
and complexity, and our experience in bringing tens of thousands of
people together in one space is unrivaled. We offer a unique
approach to the design of our projects, marrying unsurpassed
technical expertise with internationally recognized design capability.
Complex projects require a truly integrated design strategy, with the
synthesis of multiple design disciplines into a singular bold,
beautiful and intelligent design. Our culturally diverse team of
architects and designers work from offices across the world to bring
a unique combination of international and local expertise to their
work - ensuring ever more unique, innovative and thoughtful
outcomes for every project.

This project was part of the Product Design course at
Projector Institute, where we worked with AJAX Systems
to design dedicated platform solution for their Beta
testing program.

AJAX Systems is the largest security systems
manufacturer in Europe. Before launching new devices
AJAX conduct an open beta testing with real end users in
real-world environment, alowing the team to polish
devices and experience based on real world usage data.
But thats where the problems begin - the program is
scattered across different flows, causing problems and
inefficiency. AJAX need new, dedicated solution.

The problem of beta testing
And our challenge

The problem of beta testing
And our challenge

The problem of beta testing
And our challenge

Submission Problem

Submission Problem

Many foreign testers often do not submit reports or submit them very late.
AJAX assume that the problem lies in their Telegram bot - the main tool for
submission, not only its UI is not user-friendly, but foreign testers don't like
and don't use Telegram in general.

Many foreign testers often do not submit reports or
submit them very late. AJAX assume that the problem
lies in their Telegram bot - the main tool for submission,
not only its UI is not user-friendly, but foreign testers don't
like and don't use Telegram in general.

Many foreign testers often do not submit reports or submit them very late.
AJAX assume that the problem lies in their Telegram bot - the main tool for
submission, not only its UI is not user-friendly, but foreign testers don't like and
don't use Telegram in general.

Many foreign testers often do not submit reports or submit them very late.
AJAX assume that the problem lies in their Telegram bot - the main tool for
submission, not only its UI is not user-friendly, but foreign testers don't like
and don't use Telegram in general.

Communication Problem

Communication Problem

Current communication with testers heavily relies on direct manual intereaction
while also being fragmented across different platforms like messengers, email
and even physical mail. AJAX need to automate communication processes and
minimise manual touchpoints.

Current communication with testers heavily relies on
direct manual intereaction while also being fragmented
across different platforms like messengers, email and
even physical mail. AJAX need to automate processes of
communication and minimise manual touchpoints.

Current communication with testers heavily relies on direct manual intereaction
while also being fragmented across different platforms like messengers, email
and even physical mail. AJAX need to automate communication processes and
minimise manual touchpoints.

Channel Fragmentation

Channel Fragmentation

Whole testing is fragmented across different services: testers received tasks
via messenger channels, submit reports via a rigid Telegram bot, ask questions
through group chats, and AJAX processing and management goes via CRMs.
We need to find a solution to addresses all the problems and brings efficiency
to the testing flow.

The whole program is fragmented and across different
services: different tools for communication, separate
Telegram bot, CRMs, spreadsheets for tetsers base and
rating and many more. We need to find a solution to
adress all problems and brings efficiency to programme.

The whole program is fragmented and across different services: different tools
for communication, separate Telegram bot, CRMs, spreadsheets for tetsers base
and rating and many more. We need to find a solution that adresses all problems
and bring efficiency of the programme.

Whole testing is fragmented across different services: testers received tasks
via messenger channels, submit reports via a rigid Telegram bot, ask questions
through group chats, and AJAX processing and management goes via CRMs.
We need to find a solution to addresses all the problems and brings efficiency
to the testing flow.

Research and Solution Framing

Research and Solution Framing

Ajax Systems is a Ukrainian technology company that develops wirelessand wired security systems and is the
largest manufacturer of securitysystems in Europe, with over 4 million users in 187 countries.

AJAX have an open beta program for testing their devices close torelease. This is specifically open beta, which
goes after their closed betawhere they test products for every cases and scenarios in strictly controlled
conditions. Open beta is completely different, this beta goes among end users, chosen by team. AJAX find
number of testers and give them devices for testing. The testing lasts for a few weeks, usually up to a month,
during which time the testers shouldcomplete several test cases specified by the AJAX developers andsubmit
reports for the testing period. This final testing allows the team topolish the device, find and fix bugs, as well as
refine the user experienceafter receiving real-world feedback and seeing real user interaction with the device.

Ajax Systems is a Ukrainian technology company that
develops wirelessand wired security systems and is the
largest manufacturer of securitysystems in Europe, with
over 4 million users in 187 countries.

AJAX have an open beta program for testing their
devices close torelease. This is specifically open beta,
which goes after their closed betawhere they test
products for every cases and scenarios in strictly
controlled conditions. Open beta is completely different,
this beta goes among end users, chosen by team.
AJAX find number of testers and give them devices for
testing. The testing lasts for a few weeks, usually up to a
month, during which time the testers shouldcomplete
several test cases specified by the AJAX developers
andsubmit reports for the testing period. This final
testing allows the team topolish the device, find and fix
bugs, as well as refine the user experienceafter
receiving real-world feedback and seeing real user
interaction with the device.

Ajax Systems is a Ukrainian technology company that develops wirelessand wired security systems and is the
largest manufacturer of securitysystems in Europe, with over 4 million users in 187 countries.

AJAX have an open beta program for testing their devices close torelease. This is specifically open beta, which
goes after their closed betawhere they test products for every cases and scenarios in strictly controlled conditions.
Open beta is completely different, this beta goes among end users, chosen by team. AJAX find number of testers
and give them devices for testing. The testing lasts for a few weeks, usually up to a month, during which time the
testers shouldcomplete several test cases specified by the AJAX developers andsubmit reports for the testing
period. This final testing allows the team topolish the device, find and fix bugs, as well as refine the user
experienceafter receiving real-world feedback and seeing real user interaction with the device.

Dashboard - the home and control
panel of the Platform

Dashboard - the home and control
panel of the Platform

Dashboard - the home and control
panel of the Platform

The Dashboard serves as the platform’s central hub - the first
page testers see and a key element of the overall experience.
It provides a structured overview of the most important
information, helping testers stay informed and focused on
the actions that require their attention.

The Dashboard serves as the platform’s central hub -
the first page testers see and a key element of the
overall experience.
It provides a structured overview of the most important
information, helping testers stay informed and focused
on the actions that require their attention.

The Dashboard serves as the platform's central hub - the first
page testers see and a crucial element in our design solution. It
provides a structured overview of the most important
information, keeping testers informed and action-oriented.

Two key elements of the Dashboard are Active Tests, which
highlight tests requiring action from the tester, and the
Calendar, which provides a quick overview of upcoming
deadlines and important events.

Two key elements of the Dashboard are Active Tests,
which highlight tests requiring action from the tester,
and the Calendar, which provides a quick overview of
upcoming deadlines and important events.

The Dashboard serves as the platform's central hub - the first
page testers see and a crucial element in our design solution. It
provides a structured overview of the most important
information, keeping testers informed and action-oriented.

Submissions & Reports - a unified solution to
simplify the process and experience.

Submissions & Reports - a unified
solution to simplify the process and
experience.

The main problem of current Submission and Report flow
is the main tool for this - AJAX's Telegram bot.
It lacks any conventional interface to guide users in the
process, it is so unpopular among testers that they prefer to
report bugs just directly in group chats.

The solution: Instead of logically and structurally different
flows for submissions and bug reports, I combined them into
single interface. In it's core its a simple multi-step interface
with UI that adapts to the process.

To decrease cognitive load, the flow is devided into 3 steps:
Answer questions - Add Feedback - Review and Submit.
This clears the process and guides users without overwhelm

The main problem of current Submission and Report
flows is the main tool for this - AJAX's Telegram bot.
It lacks any conventional interface to guide users in the
process, it is so unpopular among testers that they
prefer to report bugs just directly in group chats.

The solution: Instead of logically and structurally different
flows for submissions and bug reports, I combined them
into single interface. In it's core its a simple multi-step
interface with UI that adapts to the process.

To decrease cognitive load, flow is divided into 3 steps:
Answer questions - Add Feedback - Review and Submit
This clears the process guiding users without overwhelm

This multi-step approach showed its effectiveness off in later usability testing, where new bug
reporting flow demonstrated greater interface clarity and reduced cognitive load, during both
first use and full-flow walkthroughs.

During the initial validation, the redesigned reporting flow significantly reduced the time required
to complete testing and bug reports, cutting the overall process time from ~7 min to ~3 min.
Moreover, the process showed progressive increase in fill-up speed with each new submission.

This multi-step approach showed its effectiveness off
in later usability testing, where new bug reporting flow
demonstrated greater interface clarity and reduced
cognitive load, during both first use and full-flow testings.

During the initial validation, the redesigned reporting flow
significantly reduced the time required to complete
testing and bug reports, cutting the overall process time
from ~7 min to ~3 min. Moreover, the process showed
progressive increase in fill-up speed with each new submission.

Test information page - everything testers need.
All in one place.

Test information page - everything
testers need. All in one place.

Testing page - keeps all the information about Testings, all in one place, information about
device, instructions, test cases and links to communication channels.
This is a direct answer to a problem of testers overwhelming AJAX Managers teams with
questions about testings and test cases.

Testing page - keeps all the information about Testings,
all in one place, information about device, instructions,
test cases and links to communication channels.
This is a direct answer to a problem of testers
overwhelming AJAX Managers teams with questions
about instructions and test cases.

Usability Testing & Design Refinement

Usability Testing & Design
Refinement

Usability Testing & Design Refinement

To evaluate the system under realistic operational conditions, We conducted a moderated
usability testing using a multi-phase prototype with members of AJAX Testing team and with
power users to evaluate different conditions and case scenarios.
I personally got an AJAX Tester Manager who previously was a beta tester himself.

We structured the evaluation across two contrasting flows:
Cold start - we begun with a flow that resembles first use of the platform, log-in,
first hardware assignment without instructional prompts, observing interaction paths
and mental model alignment.

Targeted Probing - We moved to the next flow with the platform fully configured.
Users were asked to complete a series of tasks to evaluate how quickly they could
recognize edge-case status changes and complete bug submissions under simulated
time pressure.

To evaluate the system under realistic operational
conditions. We conducted a moderated usability testing
using a multi phase prototype with members of AJAX
Testing team and with power users to evaluate different
conditions and case scenarios. I personally got an AJAX
Tester Manager who previously was a beta tester himself.

We structured the evaluation across two main flows:
Cold start - we begun with a flow that resembles
first use of the platform, log-in, first hardware
assignment without instructional prompts,observing
interaction paths and mental model alignment.

Targeted Probing - We moved to the next flow with
the platform fully configured. Users were asked to
complete a series of tasks to evaluate how quickly
they could recognize edge-case status changes
and complete bug submissions in simulated time
pressure.

To evaluate the system under realistic operational conditions, We conducted a moderated
usability testing using a multi-phase prototype with members of AJAX Testing team and with
power users to evaluate different conditions and case scenarios.
I personally got an AJAX Tester Manager who previously was a beta tester himself.

We structured the evaluation across two contrasting flows:
Cold start - we begun with a flow that resembles first use of the platform, log-in,
first hardware assignment without instructional prompts, observing interaction paths
and mental model alignment.

Targeted Probing - We moved to the next flow with the platform fully configured.
Users were asked to complete a series of tasks to evaluate how quickly they could
recognize edge-case status changes and complete bug submissions under simulated
time pressure.

Project Impact & Takeaway
Final Client Presentation

Project Impact & Takeaway
Final Client Presentation

  • 57% Time Reduction: The guided 3-step reporting flow cut completion time from
    ~7 minutes down to ~3 minutes.

  • Zero Cognitive Fatigue: The automated timestamp matching eliminated the
    primary frustration point observed in log submission.

  • Clear Role Consistency: Validated that the interface provided the immediate
    scannability managers needed while keeping the reporting flow clean and
    distraction-free for installers.

  • 57% Time Reduction: The guided 3-step
    reporting flow cut completion time from ~7 min
    down to ~3 minutes.

  • Zero Cognitive Fatigue: The automated
    timestamp matching eliminated the primary
    frustration point observed in log submission.

  • Clear Role Consistency: Validated that the
    interface provided the immediate scannability
    managers needed while keeping the reporting
    flow clean and distraction-free for installers.

The final deliverable provided AJAX Systems with an integrated MVP platform
architecture and an adaptable component system designed to ground their
beta testing operations. By removing administrative clutter and respecting the
field technician’s time, the platform restored focus to where it belonged:
observing, testing, and perfecting the physical device.

The final deliverable provided AJAX Systems
with an integrated MVP platform architecture
and an adaptable component system designed
to ground their beta testing operations. By
removing administrative clutter and respecting
the field technician’s time, the platform restored
focus to where it belonged: observing, testing,
and perfecting the physical device.

The final deliverable provided AJAX Systems with an integrated MVP platform
architecture and an adaptable component system designed to ground their
beta testing operations. By removing administrative clutter and respecting the
field technician’s time, the platform restored focus to where it belonged:
observing, testing, and perfecting the physical device.

Link 1

Link 2

Link 3

Link 4

Link 5