Audience
Small-team leads preparing a short check-in.
FICTIONAL CASE STUDY / Dashboard
Dayline
See what the week is asking of you.
Make blocked tasks visible beside work already moving.
Try the design ↓
Constraints
Every count needs a time period and a status label.
My contribution
Status taxonomy, reporting summary and a linked task list.
FICTIONAL CONCEPT DESIGN
Design outputs
Three views of the Dayline interface.
Weekly overview
Status counts summarize the current reporting period. The task list below shows what contributes to those counts.
Open full size ↗
Blocked tasks
Both active filters stay in view, and the one matching task agrees with the summary count.
Open full size ↗
Task detail and next action
The blocked task opens beside its list. A next-action panel gives the team a concrete step for the check-in.
Open full size ↗TRY THE DESIGN
A small task to try.
Switch to Next week, filter to Blocked and check the matching count and task.
Fictional design prototype with sample data. Changes stay on this page.
THE TRADE-OFF
What else could work?
A chart makes trends visible. A count paired with tasks supports specific follow-ups.
DESIGN NOTE 01
The decision in view.
The summary describes the exact filtered list. Each change updates both together.
NEXT TEST
What I’d check next.
Ask someone to find next week’s blocked work and explain what the count includes.
KEEP EXPLORING
