Who’s in, and who owes.

Today’s Event
View all events
Case study 03 · Kokoon Living
Kokoon gives students who’ve left home a room, food and care. I designed the system behind it from scratch: a web console for management, and a mobile app for wardens.




The console and the warden app: two ends of the same data. Names and figures are placeholders.
The brief
Rent, meals, electricity and complaints were tracked by hand across several hostels. Leadership wanted one place to see it all.
Simplify the management of the hostel, reduce costs and increase revenue, while giving students a better experience.The objective, from the project file
Monthly manual entry
Wardens log food and electricity once a month.
Three levels of access
Admins edit all. Wardens create. Accountants see finance.
Rent arrives two ways
Online from parents, or as cash to a warden, double-checked.
Nothing waits silently
A complaint pending 15 days alerts the admin.

02 · The workshop
I ran one design-thinking session with everyone who had a stake (names changed), so disagreements surfaced before design, not after. The PRD I wrote came out of it.
Leadership asked for visibility. Operations asked for fewer steps on the floor.
Structure
Data is entered once, by whoever is closest to it, and read everywhere else.
Students · inventory · food · electricity · attendance
Rent, through the payment integration
Complaints and feedback
Read everywhere

Same map, two screens
Same groups, same order: nothing to relearn between desk and floor.
| Console | Warden app |
|---|---|
| Finance | Finance |
| Hostels | Hostel |
| Complaints | Complaints |
| Students | Students |
| Employees | Employees |
| Food | Food |
| Leads | console only |
Money opens the console
It’s leadership’s first question each morning.
Complaints stand alone
Each belongs to a student, a room and a warden at once.
Leads sit beside rooms
Whoever knows a room is freeing up sees the parent asking.
Super Admin · analytics
One month on one screen: the trend, the totals behind it, the best hostels and where the money goes.







Revenue trendThe shape of the month before the number.
Four totalsRent, electricity, food and salary, each with its change.
Top 5 hostelsCompared without opening each one.
Financial breakdownProportions, not ledgers.




Income & expenditure
“Overall expenditure has gone up by 22.4% in the last 11 days.”
The screen does the comparison. Costs split into direct and indirect, and red means bad news, not just a rise.
Hostel details
Available rooms, rooms emptying next month and a floor-by-floor grid, ready when a parent asks.

Vocabulary
In hostel, outside, or gone. It decides meals, rent and rooms.
Type scale
Warden module · mobile
Wardens enter most of what the console reads. Every screen is built for a corridor, not a desk.
Who’s in, and who owes.


From “what’s free” to one room.
The entries the dashboard runs on.
Every room has its own meter. Food is bought in bulk and loose. Both are logged here and become the figures on the director’s dashboard.
Nothing goes quiet.

The bathroom tap on the second floor has been leaking since Monday. Water is collecting near the door.
06 · Details
The brief asked for a notification centre the admin could write to. One form sets the hostel, who receives it, the category, the channel and when it goes out.
Outcome
Where hostel data lives
registers and notebooks → one console
Rent
online and cash, tracked by hand → both logged in one rent log
Status
Shipped · handed over to Kokoon’s team
Looking back
The workshop got the structure right, but I never went back to the wardens once it was running. Six months of watching them use it would have changed several screens.
Screens from the project file; names, photos and figures are placeholders.