Project 01 / 3
Studyboard
Individual interface and data-model concept
The challenge
Coursework was spread across calendars, notes, and task lists in this personal-project scenario. I designed a weekly board that separates what is planned, in progress, and done without asking the user to maintain a complicated system.
My contribution
Individual interface and data-model concept
The decisions
I kept the initial scope local and single-user. A task has a course, title, due date, and state. Overdue work remains visible in its original column, with a clear label instead of being moved automatically. That keeps the user’s organization predictable.
The evidence
The interface concept uses realistic task content and clear status labels. The edge-case checklist covers an empty week, a missing due date, a long course name, and an overdue item. The photograph gives software-development context; it is not a working application screenshot.
The outcome
The concept defines the primary screen, task schema, and interaction states. The next step would be a working prototype with keyboard testing and a persistence test before introducing accounts or synchronization.
Limits and next steps
A small tool becomes easier to trust when its state changes are predictable.
The next conversation
Let’s make something useful.
Your approved contact links go here. This fictional candidate cannot be contacted.