
01 / 05
Cockpit
Start my day, four status counts, the ranked “What needs me today” list, and the active projects table.
- Serves designers, writers and researchers
WorkSortie
A project cockpit that shows a product team who owns each piece of work, what happens next and what is blocking it.
Screens show a demo workspace. Project names, tasks and people are sample data.

01 · Background
I built a working version first, to solve my own problem. Then I went back and did the product design properly: who it is for, what it must do, and how it should look. This case study follows that second pass.



02 · The problem
Nobody on my team could answer “where is this project, and what happens next?” without asking three people.
I was a senior UI designer at KUBRA, carrying several projects across multiple products. Each project lived in pieces: the ticket in Jira, the design and its feedback in Figma, decisions in Slack, priorities with the PM, build status in an engineer’s standup update. Every tool did its own job. None held the connection between the people.
The company saw the problem and hired an operations manager to run projects, sprints and progress tracking. That helped the team leads. The designers, writers and researchers doing the work still pieced the picture together themselves.
03 · The patterns
Published research suggests this is common. Asana’s 2023 survey of 9,615 knowledge workers found 58% of the day goes to “work about work”. Atlassian’s 2025 survey of 12,000 knowledge workers and 200 executives found a quarter of the week goes to searching for information.
04 · Who it is for
Sortie is built first for the people a process fix did not reach: designers, writers and researchers.
| Persona | Role | What they need |
|---|---|---|
| Maya Chen, primary | Senior Product Designer | To know what needs her today in under a minute, and to stop relaying status |
| Daniel Reyes, primary | UX Writer | The full context of a ticket, and the current design file, before writing a word |
| Aisha Rahman, primary | UX Researcher | To know what is coming, and to see whether a finding changed a decision |
| Priya Nair, secondary | UX Team Lead | To see who is stuck and who is overloaded before a date slips |
| Marcus Bell, secondary | Product Manager | To know if design is on track without booking a meeting |
Engineering leads, the operations manager and stakeholders read from Sortie more than they write to it.
These personas are composites drawn from my own experience on the team. They are assumptions to validate with interviews, not research findings.
05 · Process
I worked from the problem outward, so every screen traces back to a named gap.
Why it exists, the problem, the audience and the projected impact, with cited research.
Five personas in three tiers, plus three supporting roles.
One project across seven stages, from request to status report. Today’s journey sits above the same journey with Sortie.
Every screen grouped into six areas: Cockpit, Projects, Sprints, People, Agents and Settings.
Daily check-in, new request to sprint, and agent proposal and approval.
Five core screens in greyscale, to settle layout before style.
Tokens, type, components, icons and logo, mapped to the app’s code.
The five screens in dark and light modes.




06 · Key design decisions
Five decisions carry the product. Each answers one of the patterns above.
Jira’s “In progress” says nothing about what happens next. Sortie requires a next step with a due date on every active project, and flags any that are missing. On the project page, the next step and the blocker sit side by side at the top, above everything else.
The Cockpit opens on “What needs me today”: a ranked list with one action per row. The standup update is generated as a Slack post, an email or an executive summary, so nobody rebuilds status from memory.
The record holds the ticket link, the design files, the team, the decisions and the handoff. Sortie links out to Jira and Figma. Replacing them would have meant asking a team to migrate, and the problem was never the tools themselves.
Upkeep is the reason trackers go stale, so agents do it. But an agent never changes the record silently. Each proposal shows a field-level diff with Approve and Reject. An autopilot dial per project sets how far agents may go: Suggest, Draft or Act. Every change can be undone.
The collaboration orbit puts one person or project at the centre, with direct collaborators on the inner ring. It surfaces overload, single points of failure and who work is waiting on. A lead sees this before a one-on-one, not after.

07 · Design system
The design system and the code share one vocabulary: each semantic token carries the CSS variable it comes from.
One restraint shaped the look. Gold is the only strong colour in dark mode, so it always means “act here” or “this is active”. Red is reserved for blocked and at-risk work.




08 · The screens

01 / 05
Start my day, four status counts, the ranked “What needs me today” list, and the active projects table.

02 / 05
Next step and blocker at the top, then tasks, activity, links, team, slip risk, decisions and handoff.

03 / 05
Scope against real capacity, what was cut and why, and load by person.

04 / 05
Who works with whom, and where the team is overloaded or exposed.

05 / 05
Agent proposals with a visible diff, approve or reject, autopilot levels and history with undo.
09 · Projected impact
The target is 4.4 hours saved per person per week, or 11% of a 40-hour week. This is a projection built on published research, not a measured result.
| Where the time goes | Research baseline | Target reduction | Hours saved per week |
|---|---|---|---|
| Unnecessary status meetings | 2.8 h | 50% | 1.4 |
| Searching for information | 10 h | 20% | 2.0 |
| Reorienting after switching apps | Just under 4 h | 25% | 1.0 |
| Projected total per person | — | — | 4.4 |
For a team of eight, that is about 35 hours a week. The figure sits under the 4.9 hours that workers themselves told Asana better processes would save. The reduction percentages are my own assumptions.
An early version helped my team see tickets, links and statuses more clearly, but the time it saved was never measured. A four-week pilot with one product team would replace the projection with real numbers: hours spent on status and searching, standup length, time to clear a blocker, and design questions after handoff.
10 · What I learned
The hardest part was deciding what Sortie should not be.
11 · What comes next
Want this kind of thinking on your product?