DYNAMIS

Compete. Learn. Rise. Making academic progress visible so students can act on what they know and what they need to practice.
edtechlearning loopprogress
Role
Product / UI/UX
Focus
Learning visibility
Impact
visible learning loops
DYNAMIS

COMPETE. LEARN. RISE.

Student Performance System

Compete. Learn. Rise. Making academic progress visible so students can act on what they know and what they need to practice.

Role
Product Designer / UI/UX Designer
Platform
Web / Mobile
Audience
Secondary-school students, parents and schools
Project type
EdTech / Education
The challenge
Academic preparation can feel isolated, with limited visibility into progress and areas for improvement.
The users
Students preparing for BEPC, GCE and Baccalauréat, with supporting visibility for parents.
My role
Product strategy, UX architecture, user flows, wireframing, UI design and prototyping.
The outcome
A connected learning experience combining practice, feedback, progress tracking and competition.

Why DYNAMIS?

DYNAMIS connects learning content, performance measurement and motivational systems. The product aims to make academic progress visible and actionable so students, parents and schools can understand growth in context.

The learning loop

DYNAMIS learning loop

Instead of treating learning, assessment and motivation as separate features, DYNAMIS is designed around a continuous feedback loop. Interact with the nodes to explore each stage.

LEARNPRACTICEFEEDBACKUNDERSTANDTRACK PROGRESSIMPROVECOMPETEDYNAMISCompete. Learn. Rise.

The problem wasn't just access to content

How might we create a learning experience that makes progress visible, actionable and motivating?

Education frequently separates learning from measurement. Feedback arrives too late. The challenge was shortening that loop and making progress a live, navigable experience.

Who are we designing for?

PERSONA 01 — THE STUDENT

Goals
  • Improve academic performance
  • Prepare for examinations
  • Understand weak areas
  • Practice consistently
  • Stay motivated
Pain points
  • Limited feedback
  • Difficulty identifying weak topics
  • Exam preparation can feel isolated
  • Progress isn't always visible
  • Motivation drops without feedback

PERSONA 02 — THE PARENT

Goals
  • Understand child's academic progress
  • Know where support is needed
  • Monitor consistency
  • Stay informed
Pain points
  • Limited visibility into day-to-day learning
  • Results often arrive after the learning process
  • Difficult to know where intervention is needed

User needs → Product responses

Student need
  • Show me whether I'm improving → Progress tracking
  • Help me know what to practice → Recommended learning activities
  • Tell me why I got this wrong → Explanations and feedback
  • Give me motivation to continue → Competitions and achievements
Parent need
  • Help me understand progress → Parent reports
  • Tell me where support is needed → Performance insights

From needs to structure

Once the core needs were clear, I translated them into a product structure that supports multiple user journeys without overwhelming students.

DYNAMIS information architecture

Major areas: Dashboard, Learning, Practice, Competitions, Leaderboard, Performance, Profile, Parent visibility.

Why it works: the dashboard is the starting point; learning and practice form the core; performance closes the feedback loop; competition adds motivation; parent visibility provides monitoring.

Designing the core learning loop

The primary journey was designed around one continuous loop: Learn → Practice → Get feedback → Understand → Track progress → Improve → Learn again.

Key flow breakdown

Discover
Dashboard: recommended activities surface the most relevant practice based on recent performance and learning plan.
Learn / Practice
Students select a subject and topic, then work through targeted questions that map to learning objectives.
Feedback
Immediate feedback explains why an answer is correct or incorrect, highlighting misconception areas and next steps.
Measure
Scores are translated into performance summaries that visualise strengths, weaknesses and progress over time.
DYNAMIS main flow

From structure to screens

Before visual polish, wireframes validated hierarchy and primary actions.

Wireframe 1
Wireframe 2

The design principles

Make progress visible
Make the next action obvious
Feedback should teach, not just score
Competition should support learning
Keep the student in control

Building the DYNAMIS experience

The final experience

What I learned

Make progress visible, not intimidating. Competition must tie back to reflection and practice to be meaningful.

Next project

Uzzen Sheerah Initiative
View next →