Help a conversation become a decision someone can act on.
Yabbu helps teams make decisions and monitor progress without needing to meet face to face. The workspace has to connect discussion with the decisions, tasks and people that make it useful.
What I owned
I led the UX/UI restyling and new feature design, with customer journeys, usability evaluation, interaction design and prototyping documented in the career material.
The design tension
Evolve an existing workspace across desktop and mobile while preserving familiar navigation for returning users.
Inside the original workThe published case includes the earlier interface, the redesign, a delivery-process diagram, semantic UI states and mobile sequences.
Original before / after
A familiar workspace. A more deliberate structure.
The original comparison keeps a familiar navigation rail while moving from a dense meeting list to more distinct cards, filters and navigation.
01 / Earlier interfaceA dense meeting overview
02 / Published redesignDistinct meeting cards and clearer filters
02 / From understanding to decisions
The why. Then the interface.
A closer reading of the original work: the problem each choice addresses and the value it is intended to create.
01
Discussion needs an actionable structure
What the work shows
The original comparison moves from a dense meeting list to larger meeting cards, with more distinct filters and navigation.
The design response
Keep the navigation rail, and give each meeting a stronger visual identity. The wider product work connects sessions to tasks, decisions and participants.
Why it matters
Help someone understand why the session exists and what needs attention.
02
A state should mean the same thing everywhere
What the work shows
The style guide separates brand colors from success, warning and danger, and documents button states.
The design response
Use semantic color, type hierarchy and interaction states consistently across the workspace.
Why it matters
Help people read the interface and anticipate what an action will do.
03
The design has to survive delivery
What the work shows
The original process includes evaluation, approvals, design, staging, testing and post-implementation UX testing.
The design response
Connect the design work to review and implementation, with mobile flows that address a smaller screen.
Why it matters
Give the team a repeatable way to carry design intent into the product.
03 / Connecting the experience
A redesign you can trace.
Select a stage to explore its purpose.
01
The moment
Collect feedback and evaluate the direction.
The design intention
Include an approval point before detailed design.
A condensed redraw of the original delivery-process diagram. The published sequence includes approval points before design and before testing.
04 / The interface, up close
From the conversation to what happens next.
The published redesign, reframed to show how information becomes a workspace.
01 / Original interface
Redesigned desktop product
The redesigned desktop brings meeting context, schedule, agenda items and discussions into distinct regions while preserving navigation through other meetings.
Design intentionKeep the purpose of the workspace visible as the interface adapts.
The mobile presentation carries preparation and discussion into narrower views. These are selected details from the published mobile design, with the original typography, colours and content preserved.
Original mobile presentation
Prepare before the meeting
The agenda overview brings discussion items and unread activity into a compact list. The published annotation connects this view to preparation before a meeting.
Original mobile presentation
Keep the purpose with the conversation
The original discussion view keeps the agenda item and its replies together, connecting the conversation to a defined topic.
Original presentation boards6 source artifacts +
The complete originals behind this case study. Open a board to inspect the source presentation.
A complete interface restyling, new feature designs and a responsive system, with an original before/after comparison and documented delivery process.
For the person
Distinct places for the purpose, conversation, decisions and assigned work.
For the product
A clearer structure for the collaboration it already supports.
For delivery
Documented typography, semantic states, responsive grids and review steps.
A tradeoff worth keeping visible
A redesign can improve hierarchy while disrupting habits. Keeping the navigation rail gives returning users a familiar anchor while the content organization changes.
Proposed validation / Next iteration
Ask a returning user to find the latest decision and its related task.
Check whether an assignee can identify what they own and when it is due.
Observe the same task on mobile, including longer titles and crowded participant lists.
Evidence & presentation notes +
The comparison shows a concrete change in interface structure. Reduced meeting time or increased adoption has not been measured in the available evidence.
These explanations and presentation layouts are newly prepared from the available original artifacts. The validation tasks are proposals, not research already completed.
The date shown is the publication year of the Behance presentation. Screens are original project artifacts; no quantified usability outcome is asserted.