top of page
top_img.jpg
Product Case Study / Cognitive Assessment Platform

Feuerstein Digital Assessment Platform

B2B EdTech • Cognitive Assessment • Sole Product Designer

Core challenge

This was not a clean-slate project. Development was already moving, but the product had no consistent UX/UI foundation. I had to introduce structure while preserving delivery momentum, supporting sensitive users, and translating complex assessment rules into reliable digital behavior.

I joined after development had already started. As the sole product designer for 2.5 years, I had to design forward while repairing the foundation — turning printed assessment logic and an active early build into a coherent production platform without stopping delivery.

* Due to the commercial nature of this platform, selected workflows, configurations, and business content were intentionally modified to protect sensitive business information.

Role

Sole designer for 2.5 years: UX, UI, accessibility.

Platform

Guided tests, role-based management, analytics, reports.

Users

Children, educators, clinicians, institutions, adult candidates.

Scope

Printed tests, timed flows, data capture, reports.

01 / PRODUCT AND USER PROBLEM

Designing forward while repairing the foundation

I inherited an active build, printed assessment logic, multiple roles, timed workflows, reports, and no consistent UX/UI foundation. The priority was not to redesign everything at once, but to stabilize the product lifecycle and create reusable logic that could support delivery as the system expanded.

Printed tests became digital logic

Paper instructions, timing, scoring, forms, and reporting rules had to become clear product states.

An active build, not a blank canvas

Structure had to be introduced without stopping development. Decisions were phased around the highest-risk workflows first.

Sensitive users shaped the system

Children with special needs and attention challenges required calm screens, predictable feedback, and reduced cognitive load.

03img.jpg
Cognitive load principle

In assessment environments, extra choices and unclear states increase cognitive effort. The interface had to show only what mattered now: status, progress, and the next action.

Professional context

The UX had to support varied cognitive and learning profiles

The product supported structured assessment and learning workflows, not self-diagnosis. It had to remain clear for participants with different attention, communication, language, motor, and learning needs while still serving professional teams.

01_prof2.jpg
01
Autism Spectrum Disorder (ASD)

Communication, sensory, and interaction patterns that affect how instructions and feedback are understood.

02
Attention and self-regulation

Focus, impulse-control, organization, and task-completion needs without assuming intellectual disability.

03
Developmental and language profiles

Language, cognition, motor planning, and social-skill differences required predictable screen behavior.

04
Specific learning differences

Reading, writing, math, and task-processing differences shaped the need for clear states.

02 / USERS AND ROLES

Users expanded from children to professional evaluation contexts

The product began with assessments for children and adolescents, helping professionals identify learning strengths, weaknesses, and suitable intervention paths. Over time it expanded into evaluation workflows for adults, professional candidates, and organizations assessing fit for roles, training, or certification paths.

03_n02.png
Children and adolescents

Children and adolescents needed calm, predictable screens that supported focus during assessment tasks.

03_n01.png
Educators and psychologists

Educators and psychologists needed reliable ways to run assessments and interpret outcomes.

03_n04.png
Administrators

Administrators needed to manage users, permissions, tests, reports, and institutional workflows.

03_n03.png
Adult candidates

Adults were later assessed for role fit, training programs, or professional authorization decisions.

03_n05.png
Institutions and organizations

Institutions needed structured outcomes, printable reports, and group-level analysis.

03 / PRODUCT ECOSYSTEM

A role-based assessment ecosystem, not a single test screen

The platform had to connect printed assessment logic, existing admin operations, multiple user roles, timed testing, reports, and localized versions into one coherent product ecosystem.

04img.jpg
04 / PRODUCT DECISIONS

Product judgment under active-development constraints

The work was less about following a fixed UX sequence and more about choosing what to stabilize first, what to preserve, and what to simplify as evidence and constraints changed.

Define the full lifecycle

Covered setup, permissions, delivery, data capture, reports, and analytics as one product flow.

Design for cognitive clarity

Used restrained colors, predictable layouts, and visible states for sensitive assessment contexts.

Separate roles and permissions

Created distinct workflows for administrators, educators, assessors, and participants.

Support reporting and analysis

Made printable outputs and analytical views part of the core platform, not an afterthought.

Build for phased expansion

Kept patterns flexible enough for nine tests and later adult evaluation contexts.

Stabilize UX after development began

Introduced structure and design logic after several months of development to reduce product risk.

05 / HOW THE WORK EVOLVED

The process was not linear. The product evolved as new evidence and constraints appeared.

I moved between product logic, interaction design, implementation support, and Design QA as the build progressed. Each stage exposed new constraints, so priorities changed without restarting the entire product.

infogra2.jpg
06 / PRODUCT MODULES

Product screens that made the system tangible

A visual overview of the main product surfaces delivered across intake, timed testing, education-staff operations, reports, and professional review.

07 / DEEP DIVE

Deep dive: one Word Organization assessment

This sample shows the detailed UX work behind one assessment: word banks, answer zones, RTL layout, selected states, scroll behavior, timers, and reliable progress.

ONE TEST SAMPLE

roughly 5% of the total test work

08_01.jpg
Structure
Word bank and answer zones

Word bank, answer fields, timer, and progress had to work as one screen.

08_02.jpg
Selection
Choosing relevant words

Selected states stayed visible while students mapped words.

08_03.jpg
Placement
Mapping words to answer zones

Drag, scroll, and answer states had to stay clear in RTL layout.

08_04.jpg
Progress
Maintaining reliable task flow

Timers, navigation, and completion feedback had to support timed assessment validity.

08 / UX PRINCIPLES

What I deliberately did not optimize for

I did not optimize for visual novelty. In assessment contexts, cognitive clarity, predictable states, role separation, and low visual noise mattered more than expressive UI. The interface had to help users complete sensitive tasks reliably.

06_01.png
Cognitive clarity

Focused layouts, restrained colors, and low visual noise helped users stay oriented during assessment tasks.

06_02.png
Predictable feedback

Visible states, clear errors, and consistent controls reduced uncertainty during timed and guided tasks.

06_03.png
Reusable product patterns

The same interaction logic supported setup, delivery, monitoring, reporting, localization, and future tests.

classes3.jpg
09 / BEFORE AND AFTER SCREENS

Before and after screens: from legacy management to a redesigned platform

The before section uses a screen recording of the old management system. The after section uses a collage of redesigned screens to show the scale of the product change.

Before

Old management system

After

Redesigned product platform

Feuerstein_end.jpg
10 / OUTCOME

From fragmented assessment logic to a scalable product foundation

The result was not a one-time redesign. It was a reusable product system that could absorb additional tests, languages, institutions, and adult evaluation workflows while preserving consistent interaction logic.

What changed

Printed and manual assessment processes became one structured digital ecosystem.

What improved

Teams gained clearer management workflows while participants received calmer, more predictable task screens.

What the work enabled

The same product logic could support more tests, languages, institutions, and adult evaluation workflows.

09_img.jpg

The Full Menu

Projects from recent years across product design, complex systems, digital transformation, and brand evolution.

View the Menu
end_thank_you.jpg
bottom of page