LexAI
Adaptive software does its best work invisibly, which is the problem. I made the personalisation something the learner could see.

Context
LexAI adapts lessons to how each learner learns, adds practice with native speakers, and returns feedback in real time. The competition brief asked for an AI language tutor. The design problem underneath it was that adaptive systems do their most valuable work invisibly.




Process








Decisions · 01
Design for the gap between sessions
Chose
Progress tracking and goal setting aimed at the days when the app is closed.
Rejected
Putting that effort into a richer in-lesson experience.
Why
Language learners don't quit inside a lesson. They quit between them, so that's where the design had to work.
Evidence
The streak screen defines itself on the spot — a streak counts how many days you have practised in a row — and the size of the commitment is the learner's to set at 5, 10, 15, 30 or 60 minutes before day one.



Decisions · 02
Show the learner what the system changed, and why
Chose
Surfacing each adaptation in plain language at the moment it happens.
Rejected
Silent adaptation, the default and the smoother interaction.
Why
If the app quietly adjusts your lesson and never says so, it reads as an ordinary app that changed its mind. Made visible, the same behaviour reads as attentiveness.
Evidence
The Smart Reading Tutor returns pronunciation as one chip per word rather than a score, and the Speaking Test transcript marks each error at the point in the sentence where it happened.






Decisions · 03
Break practice down to the unit that actually fails
Chose
Practice split to the individual grammar unit — independent, dependent, noun, adjective and adverbial clauses — each with its own fifteen questions and its own score.
Rejected
One Grammar module with a single progress bar.
Why
A learner who keeps missing adverbial clauses does not need more grammar. They need that one unit. A combined score can only tell them to try harder, which is not an instruction.
Evidence
Every clause type carries its own question count and its own correct/wrong tally, and answers are marked right or wrong in place rather than totalled at the end.



Shipped







What I'd change
It won on the strength of the concept, but it was never tested with a learner over more than one session, which is exactly the timescale the motivation argument depends on. I'd treat that claim as unproven until it is.