01 / 04
AI & COLLABORATION / WEB APP
Work still got lost between tasks, decisions and people.
Decisions made in meetings stayed in someone's notes, and calendar clashes were found by whoever showed up late. Version 6.0 is the redesign.
42 screensdesigned for version 6.0
- Role
- UX Designer & Researcher
- Timeline
- Version 6.0
- Platform
- Web app, desktop
- Tools
- Figma
01 / 09
The product is a project management web app with an AI assistant that reads the board and flags risk, like tasks likely to slip, uneven workloads and columns filling up. The first version put that assistant inside the Kanban board so teams could stop chasing status.
6.0 started with one question: where does work still slip once the board is set up? Two places stood out. Meetings, where decisions get made and then live in someone's head. And the calendar, where a conflict usually gets found by the person who shows up late. The redesign is built around closing those two gaps without making the product any louder.
The role: the Focus rules, interaction and visual design for every 6.0 screen, the component updates behind them, and the developer handoff.
- 42
- screens designed for 6.0
- 6
- product areas, from Projects to Meeting AI
- 2
- flows designed end to end, from first click to result
- 51
- open questions logged for engineering instead of guessed
The board, with AI Insight open

Figtree, and nothing else
Aa
Figtree
Website Launch
Review suggestions
In 2 days · UI/UX Design
Colour only where it means something
- Primary#0B57D0
- AI#7F5DF6
- High#C5221F
- Medium#B06000
- Low#137333
- Canvas#EFF3FB
02 / 09
The first version fixed status chasing on the board. Looking at the product as it stood in 5.0, the problems that were left sat around the board, plus some noise on it.
- Meetings ended, and the decisions stayed there: Action items lived in someone's notes. Owners were implied, dates were vague, and turning any of it into tasks was a manual job after the call.
- Conflicts showed up at the last minute: Booking a meeting meant checking other people's calendars by eye. Overlaps were found when someone arrived late, and focus time was the first thing to get run over.
- The board said everything, everywhere: Every card carried a comment count and a priority word, some carried an AI sentence too, and AI showed up in more than one place on the same screen.
- Controls repeated themselves: The calendar offered filtering and sorting in two places, so people had to guess which one was in charge.
03 / 09
Making
Before any layout changed, a short set of Focus rules came first. Every 6.0 screen follows them, and they are what keep 42 screens feeling like one product.
When a screen started to get busy, the rules were the first check. Most of the cleanup in 6.0 is a rule applied, not a one-off fix.
- Two header rows on every work screen: The title row holds the project and its actions. The view row holds the view switch plus only the controls that view needs.
- One AI entry point per screen: AI sentences live in the AI panel. Cards carry a small At risk chip, nothing more.
- Cards answer who, what and when: ID and people, a title of two lines at most, then a priority meter, due date and label. No comment counts, no priority words.
- Colour only where it means something: Each priority level has its own colour: High red, Medium amber, Low green. Beyond that, only overdue, AI and meeting category get colour.
- AI suggests, people decide: Every AI action ends with a choice, and the copy says so: nothing changes until you pick one.
- Side panels make room: Opening a panel switches the header to its narrow version, so the work underneath keeps its space.
Before · 5.0

After · 6.0

04 / 09
Making
Meetings are where a lot of decisions happen, and the worst place to keep them. Action items end up in a doc nobody opens, owners are implied, and the follow-up depends on whoever remembers.
If a decision never becomes a task, the board is wrong from the start, and every AI insight built on top of it is wrong too. Getting meetings into the board is what makes the rest of the product worth trusting.
The result: the person who ran the meeting reviews a draft instead of writing one, and the board reflects what was actually agreed.
- Take Notes: Start from the meeting pill, the week view or the day panel.
- Consent: Everyone agrees before anything is captured.
- Live notes: Summary, decisions and action items build as people talk.
- Report: A private draft with a timestamp on every line.
- Review: Fix owners and dates, then create only what is checked.
- On the calendar: Tasks land on their due days, linked to the notes.
Consent comes first, and it is specific
Notes you can check against the source
Suggestions stay suggestions until reviewed
Every task knows where it came from
05 / 09
Making
Scheduling across a team meant opening calendars and comparing them by eye. Conflicts got found when someone showed up late, and focus time was usually the first thing to give.
A booked conflict costs everyone in it. Catching it while the event is still a draft costs almost nothing, as long as the check is quick and honest about what it looked at.
The result: conflicts get handled while they are cheap to fix, and people still make the final call.
- New event: Pick a title, time and people in the new-event dialog.
- Overlap hint: The dialog flags an overlap as soon as it exists.
- Overlap check: Every conflict sits on one small timeline.
- Open times: Pick a time that works, or Book Anyway.
Warn while it is still a draft
Show the conflict, then the way out
Focus time can bend. Meetings can't.
Honest about what it checked
The week, looked at afterwards

06 / 09
Making
The two features carry the story, but most of 6.0 is the same Focus rules applied screen by screen. These are the changes worth looking at first.
One place for what needs attention
Project health, with its reasons
Automations you can describe in a sentence

Filter for what you see. The view menu for how.


A card that answers who, what and when
07 / 09
Making
Every screen below is from 6.0.

The board
Two header rows, one AI entry point and three-row cards. The rest of 6.0 follows from these rules.

List
The same tasks grouped by status, with owner, label and due date in columns that line up.

My Tasks
Everything assigned to you across projects, sorted by when it is due.

A task, full screen
Description, subtasks, linked tasks and files on the left; the details and activity on the right.

Asking about project health
The assistant answers in the side panel while the board keeps its space beside it.

The month
Tasks and meetings on the days they land, overdue work marked where it sits.

The week, before a meeting
A meeting about to start shows in the header with Take Notes one click away.

Notes during the call
The summary, decisions and action items build in a panel beside the call as people talk.

Screen snapshots
When someone presents, the notes ask again before keeping any snapshots of the shared screen.

Overlapping three events
Every clash on one timeline, then the open times that work for everyone.

A day, in a side panel
Click a day for its meetings and tasks, with Take Notes on the meeting that is coming up.

Starting a project
Three short steps: details, the default view, and who is in it.

The view menu
Day, week or month, and what to show, all in one menu.
08 / 09
Outcome
There are no numbers for 6.0 to report yet. The figures below are from the first launch, as published in the original case study. They describe the earlier product, not 6.0.
- Meeting suggestions: how many get created versus dismissed, and how often owners or dates get fixed first.
- Time to the board: how long it takes from the end of a meeting to tasks on the board.
- The overlap check: how often it ends in a different time instead of Book Anyway.
- The AI Insight panel: whether people open it more once AI stops appearing on every card.
- +78%
- daily active users after the first launch, from 2.1k
- −43%
- project completion time after the first launch, from a 14-day average
- +125%
- cross-team interactions after the first launch, from 320 a month
- 4.7 / 5
- customer satisfaction after the first launch, up from 3.2 across 1,250 reviews
- 92%
- feature adoption after the first launch, up from 34%
09 / 09
- Rules scale better than screens: Writing the Focus rules first made it easier to say no. Most of the cleanup in 6.0 came from applying a rule, not from redesigning a screen.
- Show the basis, then ask: an AI feature should show what it looked at and wait for a decision, not act and apologize. Every AI surface in 6.0 works that way.
- The edges took the most thought: Consent, a task with no owner, a week where no time works for everyone. The screens nobody screenshots were the hardest ones to get right.
- Handoff keeps you honest: Writing the developer handoff surfaced 51 open questions, from consent for late joiners to what Undo should do on AI notes. They're listed for the team instead of papered over.
Keep reading


