when design met logic
BUCC consulted me to build a website for the chaplaincy helpdesk. i spent my whole weekend on it, every detail, every layout, every hover state. by 1am on monday i delivered.
the person who reached out said i did a wonderful job. i was excited that something i built would finally be used by students. then i saw the launch post and it wasn’t my design.
the main people in charge preferred something simple. it stung, but it taught me not to fall in love with work that isn’t yours and not to overcomplicate what doesn’t need fixing.
table of contents:
the brief
BUCC asked for an intuitive helpdesk site for the chaplaincy. the goal was clear, but i treated it like a chance to push for a clean, modern experience that would actually help students.
the build
i worked through the weekend, focusing on clarity and smooth interactions. small decisions mattered, and i wanted the experience to feel effortless for students looking for support.
the launch
when they launched, a different version went live. apparently the stakeholders preferred a simpler approach. at first i was disappointed, then i accepted it as part of how real projects work.
lessons
don’t overcomplicate what isn’t complicated. communicate early with the people who make final calls. and never fall so hard for a project that you forget it might not be used as you intended.
links
this is what i built: solace-bucc.vercel.app
this is what they launched: bucc-chaplaincy-helpdesk.vercel.app
let’s build something worth talking about
