KM.
← All work

Product design · Dashboard UI

StudyForge / OPS

A study deck built for two.

Category
Product concept
Role
Concept, UX, interface design, front-end
Year
2026
Status
Concept — deck & UI prototype

Overview

StudyForge / OPS is a study operations deck for exactly two people — two entirely different syllabi, one shared push. It tracks what you actually know rather than how long you sat there, and it puts a clock between the two of you that neither can quietly ignore.

Every topic carries two independent 0–100 scores. Competency is the mark you'd get today. Confidence is how sure you feel. The gap between them is the entire diagnostic, and it's the number the whole app is built around: confident and incompetent is the dangerous quadrant, and it's invisible in every hours-logged study tracker I've used.

I designed it around a real pairing — a university student and a matric student revising toward completely different papers, who still wanted the accountability of studying with someone.

  • 5Tabs, whole app
  • 2Scores per topic
  • 1Clock, server-owned
  • 0Spinners on load

01 — Design decisions

Built like an instrument, not an inbox.

Three decisions carry most of the product, and each one closes off a way of cheating yourself.

  1. Two scores, one gap

    Competency and confidence are entered separately and never averaged. Confidence above competency flags a topic you're about to walk into an exam over-trusting.

  2. The timer lives on the server

    A shared study clock that the client can't start, pause or fake. If it says four hours, four hours happened — that's the only reason the number between two people means anything.

  3. Scope the paper, score the gap

    Exams are defined by their topic list, so readiness is arithmetic over the scope rather than a feeling. Fail-closed writes and an observer mode keep the shared view honest.

02 — Presentation

The product deck

Sixteen slides and every screen: the subject view, the two-score topic list, the shared clock, exam scoping, the side-by-side stats and the report card.

Open the deck full screen ↗ View the product landing page ↗

Who it's for

The pairing is the product, and it generalises further than the original case: study partners on different courses, a parent and a matric student, a tutor and a tutee, or two people grinding toward separate certifications on the same deadline.

What they share isn't a syllabus. It's a date and a witness.

Outcome

What was produced. A sixteen-slide product deck covering every screen, plus a landing page with live interface fragments — the subject panel, the topic list with paired competency/confidence bars, and the stats comparison — all hand-built, no framework.

What I learned. Designing for two users at once changes the layout brief entirely: almost every screen needs a version that reads well when it's about you and when it's about them, without becoming a leaderboard.

What could be improved. Data entry is still the weak point. Scoring competency honestly takes effort, and if that ritual is heavy the whole system decays after a week.

Where it goes next. The server-owned clock is the piece worth building first — it's the smallest thing that can't be faked, and everything social in the product depends on it.