AutoStandup
Helping distributed teams stay aligned without unnecessary meetings.
- Industry
- Productivity SaaS
- Year
- 2026
AutoStandup is a collaborative productivity platform that automatically collects standups from Slack and other workplace tools into a single, organized workspace.
The concept focuses on reducing manual updates while improving visibility across teams.
- Industry
- Productivity SaaS
- Timeline
- 2026 · Concept exploration
- Services
- UX Strategy, Product Design, Dashboard Design
- Platform
- Figma
- Role
- Self-initiated UX & product concept
Transforming fragmented team updates into a unified workflow that managers and contributors can quickly understand.
Challenge Visual
1600 × 900
What we went looking for
Mapping how distributed teams already report, we found the update itself was rarely the problem — it was the reassembly. Contributors wrote clear notes in Slack; managers then spent their mornings scrolling channels to reconstruct a picture that had existed in fragments all along. The work of the standup had moved, not disappeared.
Research Synthesis
2400 × 1350
“The status meeting survives because the alternative has always been worse. It doesn't have to be.”
Structure before surface
AutoStandup treats the existing message as the source of truth and does the assembly automatically. Contributors keep writing where they already write; the product's job is to collect, structure and surface. The interface is designed for two very different readers — the person adding one line, and the person reading forty.
Structure & Flow
2400 × 1350
Legible before it is anything else
The visual direction is built for a screen someone checks at nine in the morning without especially wanting to. Restrained type, strong hierarchy, and colour held back almost entirely, so a blocker is the only thing on the page that raises its voice.
Visual Direction
2400 × 1350
Documented like a manual
A dashboard kit of update cards, team rollups, filters and blocker callouts designed to stay legible whether a team has four people or forty.
Component Sheet
2400 × 1350
Screen by screen
Core Product
2400 × 1600
The manager view opens on exceptions rather than everything: blockers first, then what changed since yesterday, then the full feed for anyone who wants it. The contributor view is a single composer that confirms what was captured, so nobody has to check whether their update landed.
Blockers first
The manager view opens on exceptions rather than everything: what is stuck, then what changed since yesterday, then the full feed for anyone who wants it. A dashboard's value is what it filters out.
Signature Flow
2400 × 1600
Built to hold up
Specified as a working prototype with defined integration surfaces for Slack and comparable workplace tools, including the parsing rules and fallback states for updates that arrive malformed or not at all.
In Production
2400 × 1350
It works where the work already is
Contributors keep writing where they already write. The product collects, structures and surfaces — with defined integration surfaces for Slack and comparable tools, parsing rules, and fallback states for updates that arrive malformed or not at all.
Across Platforms
2400 × 1350
What we'd carry forward
The hardest decision was showing less. Every stakeholder wanted the full feed on the landing view, and the concept only worked once we accepted that a dashboard's value is what it filters out, not what it contains.
