Work
EBA Reader
Guided read-along that keeps momentum without turning it into homework
Read case →I build products for the moment users don’t feel like doing the thing they know they should do. The work is designing small, reliable loops that reduce friction, clarify the next step, and keep progress moving even when attention is low and stakes feel high.
Think back to being ten, sitting an exam that feels like it decides your future.
You can be capable and trying, and still freeze when the clock starts. This is the reality for ~100,000 students in the UK every year.
What I look for: where people disengage, where stakeholders start guessing, and where teams lack signal
When the next step feels hard, people do not fail. They disengage. They skip, rush, or stop showing up.
Built: Short, repeatable loops that make the next step obvious and give fast feedback, so momentum survives real conditions.
When progress is not visible, stakeholders start coordinating manually. Reminders, follow-ups, and back-and-forth become the product.
Built: Visibility and accountability loops so what is next is clear without chasing, and trust does not degrade into nagging.
If you only see outcomes, you cannot diagnose why they are happening. Interventions become late, generic, or wrong.
Built: Lightweight checkpoints that surface leading indicators like effort, errors, and confidence dips without heavy overhead.
People do not need extra options. They need a calmer path forward. I keep the next step clear, reduce friction, and support the workflow around the user so progress is repeatable.
A few short quotes from parents. I keep them here because they reflect the outcomes the system was designed to create: calmer practice, clearer routines, and fewer battles.
“My son had his tutoring with Exam Bytes. Keerthikan was so amazing. My son secured an academic scholarship at a prestigious independent school.”
I’m at my best when the problem is real, the constraints are clear, and we’re allowed to iterate. I like teams that write things down, make trade-offs explicit, and treat feedback as a normal part of the week.
If you’d like, I can walk through the interventions above: what triggered each build, what changed after launch, and what I’d do differently with more time and sharper instrumentation.