Designing clarity for live meetings

What shipped

Infange is a meeting productivity workspace — a calendar paired with live agendas that keep teams aligned before, during, and after meetings.

I was the sole product designer. I led this end to end: research, interaction design, prototyping, stakeholder alignment, and engineering handoff.

Where meetings break

Most meeting problems don't show up during the meeting. They show up after — when people leave with different interpretations of what was decided.

Infange already existed when I joined, but it was mostly a utility. It captured information without guiding teams through planning, live discussion, or follow-through. My job was to turn it into something that actually helped teams stay on track.

That direction shaped the structure: a calendar for planning and a live agenda for execution.

What I inherited

This was the product when I joined. Functional, but bare-bones. Weak hierarchy, inconsistent spacing, and no clear sense of progress during a meeting. Active and completed states looked the same, so users had to interpret what was current versus what was done.

Designing as team of one

The company had never worked with a product designer before. My direct report was the CEO — not a design lead, not a PM — and he had strong opinions about the product without a frame of reference for how design decisions get made.

That became clear in weekly presentations. He challenged everything. Early on, when he asked "why did you do this?" I froze. I didn't have an answer ready because I hadn't built the habit of documenting my reasoning as I worked.

One example: he pushed back on white space in the interface. He thought it was wasted space and wanted it filled with more data. I defended the decision using established research — white space isn't decorative, it directs focus. In a meeting productivity app where users need to find the active agenda item immediately, reducing visual noise is the point, not a side effect.

That exchange changed how I worked. I started documenting the rationale behind every design decision as I made it — not after. So when challenges came up in weekly crits, I was prepared. Over time, his rigor stopped feeling like resistance and started feeling like quality control. He wasn't hostile to design. He just wouldn't accept "it looks better" as justification.

Metrics that mattered

Before touching any screens, I set three targets:

• Alignment — 60% of users report meetings being more aligned and productive after adopting Infange
• Efficiency — Users accomplish agenda items 25% faster compared to traditional meetings
• Engagement — 35%+ satisfaction on ease of collaboration and communication

These kept the project honest. Without them, "make meetings better" stays vague.

Calendar as home base

The calendar is the home base. I designed it so users could open Infange and orient themselves in seconds.

Surfaced today in one glance

Today's date, upcoming summary, and key status blocks above the fold. The most important context should be visible without scrolling.

Kept navigation out of the way

The sidebar collapses to icons by default and expands when needed. Navigation stays available without competing with core content.

Supported three creation styles

Users can create from a modal (Meeting, Note, Objective) or jump straight through Command+K. Same actions, optimized for different working styles.

Live agendas at the center

Live agendas are the core behavior. Once a meeting starts, attendees follow one shared sequence in real time.

Made live progress obvious

The active item is clearly highlighted. Each agenda item has its own comment thread, and completed items collapse to keep focus on what's next.

Kept completion one tap away

I fixed the complete action to the bottom of the viewport so users never have to hunt for the next step.

Recovered context in one tap

Previous meetings are one tap away. The system matches related sessions by metadata so users can recover context without digging through notes.

Results

The redesign shipped and became the default workspace for all internal meetings. Shorter meetings, fewer post-meeting "what did we decide?" messages, and higher agenda completion rates.

Beyond the product, I left behind a design system and a decision-making process the team could maintain without a designer in the room.

What this taught me

The best thing that happened to me as a designer was a stakeholder who wouldn't accept "it looks better."

Being forced to justify every decision with evidence doesn't slow you down — it builds a design instinct backed by reasoning instead of gut feel. I came out of this role a fundamentally different designer. The discipline of having a documented rationale before anything hit a crit became my default, and it's made every presentation, every design review, and every stakeholder conversation since then easier to navigate.