The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
I met a client last month whose course wasn’t getting results. They asked me to audit it.
I expected to find a content problem. The lessons were good. The problem was the curriculum map. Nothing was wrong with any single lesson, but together they didn’t build toward the outcome the course promised, so students were doing the work without feeling like they were getting anywhere.
Once the map was fixed, the same content started to make sense.
If your course has good content but students stall or drop off, the map is where I’d look first. Send me a message and I’ll take a look.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Before making a prototype, write down the decision it should help you make.
Will someone understand this workflow?
Can the data support the idea?
Is this useful enough to build further?
That question gives the prototype a purpose and a stopping point. It also makes feedback easier to interpret: you know what you were trying to learn.
Writing the decision down also tells you what to fake. When I prototype with AI, if the question is the workflow I hardcode the data, and if it's the data I skip the UI polish entirely.
CampusOS is a system I built for universities in East Africa.The problem is simple: Lecturers are overwhelmed. Marking 200 research papers takes about 33 hours. Student results are scattered in paper registers and Excel. And student data is kept on foreign cloud servers, which breaks Uganda's Data Protection law.CampusOS fixes that in one place, on the university's own server.It has 3 parts:For Students - submit assignments, do timed exams, see results.For Lecturers - AI helps mark using the lecturer's own rubric, lecturer approves. Saves half the time.For Admin - see which questions students fail most, track performance, keep full audit trail.
The submission form looks really clear.
iQube.OX brings courses, live sessions, workgroups and mentors into one place. The challenge was density. A learner needs to see progress, what’s coming up, and who can help, without feeling buried.
The dashboard answers “where am I?” first, with a monthly learning chart and course cards that show hours, lessons and a progress bar at a glance. Featured and pending workgroups, a calendar and upcoming activities sit side by side, so planning your week takes one look. The Courses page uses color coded cards and progress bars to show what’s ongoing, completed or not started, so the next step is obvious.
Upcoming Activities opens as a focused panel instead of a new page. Learners browse sessions on the left and read the full agenda, speakers, time and a “Join Now” button on the right, without losing their place.
Learning also needs people, so I designed the Workgroup space like a lightweight Slack. A slim rail on the left switches between groups. The main feed has Discussion, Resources and Tasks tabs, with role badges for mentors and advisors so learners know whose advice they’re reading. Each post supports reactions, replies, saving and pinning, and a rich text composer sits at the bottom so starting a conversation is always one tap away. The right side keeps the group’s context nearby: the project overview, the next session with a Register button, and saved messages.
I designed everything manually, from the layout grid and components to the states and spacing, which gave me full control over the details.
The course layout reads well.