Your Own Queue: Fixing the First Ten Minutes of the Day

Boards Are Organised for Planning, Not for Doing

Project boards are structured by project, which is right for almost everything: planning, prioritising, reporting, discussing scope. It's wrong for exactly one moment - the beginning of your day, when the question isn't "what's happening in Backend?" but "what needs me?"

On a team with four or five active projects, answering that means visiting each board, filtering to yourself, and holding the results in your head. So people build a shadow system instead: a notepad, a personal to-do app, a pinned message to themselves. That shadow list is always slightly wrong, and it's where work goes to be forgotten.

The Four Things That Can Need You

A useful personal view isn't just "tasks assigned to me". There are four distinct ways work can be waiting on you, and a list that only covers one of them sends you back to checking three other places.

• Something with a date. Overdue or due soon. First, because it's the only category with a clock that isn't yours.
• Work you own. Open tasks assigned to you, across every project.
• Questions waiting on you. Unresolved @mentions. Someone is blocked on your answer, which usually makes these more urgent than your own tasks.
• Work you're following. Tasks you watch but don't own - the dependency you're waiting on, the bug you reported, the thing you handed off but still care about.

Each item appears once. Something assigned to you, watched by you and overdue shows up under the date, not three times.

Mentions Belong on the Work List

This is the part most tools get wrong. Mentions live in a notification feed, separate from the task list, and notification feeds are things people check when they remember to.

But a mention is work. Someone asked you something and stopped. If it sits in a different place from your tasks, the predictable outcome is that you spend the morning working through your own list while three people wait on answers you could have given in a minute each.

Putting unresolved mentions in the same view as assigned work makes the tradeoff visible: you can see that answering two questions unblocks two people before you start your own first task. That's usually the right call, and it's invisible in any layout that separates the two.

A Lens, Not a List

The important design property: there's nothing to maintain here. No adding items, no ticking them off separately, no sync to keep honest.

It's a view over tasks that live in their projects. Change something here and you've changed the task itself. Complete it and it leaves. Someone assigns you something and it appears, in real time, without a refresh.

Every personal-productivity layer that requires manual upkeep eventually diverges from reality and gets abandoned. The only version that survives contact with a busy week is one that's derived rather than curated.

Reading It as a Diagnostic

Once you've used it for a couple of weeks, the shape of the page tells you things.

A permanently full date section means your team is setting dates nobody honours. Either they're not real deadlines, or they're real and you're consistently late - both need addressing, and neither is fixed by looking at the list again tomorrow.

An always-empty watching section means you're not following the work you depend on. When your task gets blocked by someone else's, you'll find out by discovering it rather than by being told.

Mentions that linger are the clearest signal of all. Every unresolved mention is a person who has adapted by working around you.

Twenty assigned tasks isn't a full queue, it's an unmade decision. Nobody works twenty things. The other nineteen are a backlog with your name attached, and pretending otherwise makes your capacity invisible to everyone including you.

What It Deliberately Isn't

It's a personal view, not a management dashboard. There's no way to look at someone else's.

That's a design choice, not an oversight. A "what is everyone working on right now" screen gets used for surveillance far more often than for coordination, and teams that get one start optimising for how their queue looks rather than for shipping. Team-level questions have better answers in aggregate metrics, which show throughput and trends without turning individual queues into a leaderboard.

How to Use It

• Open it before the board. Clear dates and mentions, then go to a project for focused work.
• Treat mentions as an inbox with a zero. Replying resolves them automatically.
• Don't work from it all day. It's for orienting, not for deep work. Once you know what you're doing, go to the task and stay there.
• Watch generously. Watching is cheap - notifications for watched tasks can be in-app only - and it's what makes the fourth section useful.

Summary

The gap between "what's happening in this project" and "what needs me" is where personal to-do lists get invented and where work quietly falls through. Closing it needs four categories - dated, assigned, asked, watched - derived automatically rather than maintained by hand, and kept private enough that nobody is tempted to manage by it.

Get started with FlowBoard, or read about context switching and the weekly review.

Frequently Asked Questions

How do I see my tasks across all projects?

FlowBoard's My Work page gathers everything that needs you from every project in the workspace - dated work, assigned tasks, unresolved mentions and tasks you watch - into one page that updates in real time.

Is this a separate to-do list I have to maintain?

No. It's a view over tasks that live in their projects. Nothing is added or ticked off here separately, and items leave as they're resolved.

Can I see what my teammates are working on?

Not through this view - it shows only your own work, by design. Team-level questions are better answered by aggregate metrics than by inspecting individual queues.

Why are mentions in the same place as my tasks?

Because a mention is work - someone is waiting on your answer. Keeping them beside assigned tasks makes it obvious when answering two quick questions unblocks two people before you start your own list.

What if my assigned list has twenty tasks on it?

That's a prioritisation problem rather than a workload display problem. Nobody works twenty things at once; the rest are a backlog with your name on them, and treating them as a queue hides your real capacity.