The Challenge
01
The work existed. The structure didn’t.
Wibey had grown feature by feature, and it showed. This wasn't a fix for one broken flow. The redesign was about making Wibey genuinely good to use: clean, readable, and fast, with new features that let people enjoy the experience and get their work done without friction.

Solutions
02
How It Came Together
Rather than stopping at static screens, we vibe coded all of this into a working prototype: functional, clickable, close to real behaviour instead of just a picture of it. That made it much easier for product, engineering, and design to actually collaborate. Engineering could see how something behaved instead of guessing from a mockup, and design decisions could be tested and argued over in something that felt real, not just implied.
Impact
03
Why this matters.
Faster switching.
Fewer clicks to switch conversations or trace a source
Shared workspaces.
Teams build together in one shared workspaces
instead of scattered tools.
One tool, not three
No more leaving Wibey to create in Studio or browse the Catalog elsewhere.
Fewer repeat questions.
Ask Wibey and FAQs from real threads answer things before they're asked twice.
Cleaner pages.
Library, Settings, and Metrics are faster to scan and easier to use.
Chat, anywhere.
Chats are reachable from anywhere, without breaking your flow.
Reflection
04
What I’d take forward.
This project taught me to work with a scope that keeps moving. I joined to help with the sessions panel and sidebar, and ended up shaping Library, Documentation, Settings, Metrics, and Catalog too. It also meant designing around constraints I didn't control, like Metrics, where only the experience around the data was mine to shape. Vibe coding the prototype turned a lot of "I think this could work" conversations into "let's just try it" ones, a habit I want to keep.




