Tasks tie to your objectives. Flo ranks them by what actually moves the needle right now — what’s blocking, what’s slipping, what your manager just flagged — and tells you why each one is first.
I’ve put your highest-leverage task first — it’s blocking your top objective and your manager flagged it. One other thing is slipping.
Flo reads every task against your objectives, due dates, blockers, and the signals on the thread — then orders your day by leverage, not by what’s loudest or newest. Each task comes with a plain-English reason it’s there.
“I moved this to the top because it’s blocking KR2 and your manager flagged it — not because the thread was busy.”
Link a task to an objective and a key result. Flo flags work that isn’t tied to anything, so you can link it or let it go. And execution rolls up into your OKR insights — so a slipping objective with nothing behind it can’t hide.
Today is Flo’s ranked plan. By OKR groups the work under each objective. Board is the kanban your team already knows. Same tasks, three lenses.
Your team comments, flags a blocker, or requests priority right on the task. Flo weighs those signals by who raised them and what kind they are — a manager’s flag moves a task, a long thread doesn’t — and it always tells you which signal changed your day.
QA can’t start until this is signed.
@Naledi this is critical for the board demo Thursday.
Raised to Urgent and moved to #1 — blocking KR2 and flagged by your manager.
Create, assign, link to an objective, comment, or reprioritise — just by asking. Flo does it as you, with every action logged and audited.
Link your work to your objectives and let Flo run the order of the day.
Start free