01
Give tutors their own home
A tutor's home answers three questions: what's waiting for review, when is my next class, and is my availability set. No more landing on the learner's home.
All workUX audit · Edtech
RoboPandit
A UX audit of an AI and robotics learning platform, done with the founder's permission. Each role now gets its own home, starting with tutors.
- 10issues ranked
- 6strengths kept
- 4quick fixes
- 10page report
/What I found
A well-built platform with a strong admin console. The biggest wins are about roles: tutors and admins both land on the learner home, so the work they came to do is one or two clicks away. One home per role fixes most of it.
/How I reviewed it
I reviewed RoboPandit's public demo with the founder's permission, logging in as a tutor and as an admin, plus the learner home they both land on. I covered the dashboard, assignments to review, my availability, live classes, the admin dashboard and the users table, with a heuristic review of each role's main tasks.
The pattern showed up quickly. The platform is well built and its admin console is strong, but every role starts on the learner's home, so the work they came to do is one or two clicks away.
So the redesign gives each role its own home, starting with tutors, and uses only data RoboPandit already has.
/What already works
Keep what's strong
- KPIs say what they're compared to: "vs previous 7 days"
- Alerts clear themselves when the cause is fixed
- A strong, well-organised admin console
- Consistent components across roles
/Top fixes
Three fixes that matter most
02
Put "Needs attention" first
Admins first saw a revenue chart flat at ₹0. The list of things to act on moves under the KPIs, and developer setup alerts move to their own System page.
03
A real first day for new tutors
With no data yet, the home still tells a new tutor what to do next: add weekly hours, then wait for the first booking.
/Before and after
Before and after
Tutor home before and after, the new-tutor empty state, and the admin view it fixes. Names and numbers in the redesign are sample data.
/The report
A report you can act on
10 pages: scope and verdict, what works, 10 issues ranked by priority and effort, the redesign, a day-one empty state and a roadmap.
/Result
The redesign uses the same product and components, and only data RoboPandit already has, so the team can build it without new features. Quick fixes like sending admins straight to their console can ship this week.
Get an audit like this for your product: Dashboard UX Audit, $250
/FAQ
Want an audit like this?
How much does an audit like this cost?
$250 for up to 10 screens, delivered in 3–4 days, with one key screen redesigned in Figma.
Will you share my audit publicly?
Only with your permission. RoboPandit's founder agreed to share this one. By default, your audit stays private.
Can you review more than one user role?
Yes. An audit covers up to 10 screens, so I can split them across roles, like tutor and admin here.
Have a project in mind?
Tell me what you're building. I'll tell you honestly if I'm the right fit.
Your time: —My time (Pakistan): —I reply within 24 hours on weekdays.