Case study · 02
Insti App Redesign
A role-aware redesign of IIT Bombay’s campus platform, expanding a student discovery feed into a workflow for creating, reviewing, revising, and publishing events.
Read the project overview
Who was hurting
A rejected event returned only a status with no reason or next step. The gap affected creators and approvers as well as the students discovering events.
Roles and research
The workflow maps three roles—Student, Creator, and Approver—using informal conversations with campus communication operators rather than a formal study.
From feed to workflow
The brief moved from cleaning up a feed to supporting create, submit, review, decide, revise, and publish as one connected lifecycle.
Organized around intent
The information architecture follows what each role arrives to do instead of forcing students, creators, and approvers through one undifferentiated stream.
Core decisions
Creation mirrors the published event, lifecycle status follows the event everywhere, and approvers receive a dedicated queue with inline decisions.
What remains
The concept was not launched and has no post-launch metrics. Open work includes clearer rejection reasons, IA tree testing, time-to-decision, and reject-to-resubmit measurement.
