The Planner
A calendar view of scheduled work — day and week layouts, drag-and-drop rescheduling, and Olga's scheduling proposals.
Phase 1
The Planner is a calendar-like view where users see their scheduled work laid out by day and hour — a personal calendar, but for the work RunOlga is helping them do. It is where priority-to-task decomposition becomes a real week: approved tasks land here with specific days and times.
Views
| View | What it shows |
|---|---|
| Day | One day with all the hours laid out |
| Week | The default — 5 or 7 days at once |
Month view is not in Phase 1; it arrives in Phase 2 — see Scope & roadmap.
What appears in the Planner
- Priority-derived tasks — colored to match the Priority they belong to
- Standalone tasks — not tied to any Priority, shown in a neutral color
- Meetings — pulse meetings, quarterly reviews, and other scheduled meetings
- Regularly scheduled work — anything recurring
How you use it
- Drag and drop tasks to reschedule them
- Click a task to see details or edit it
- Ask Olga to move a task or reschedule the week
- Watch for overload warnings when a day has too much work scheduled
- Switch to another user's Planner — if your permissions allow it
Rescheduling here and in To-Dos stays in sync — they are two views of the same tasks.
What Olga does in the Planner
- Proposes the schedule. When a Priority is broken into tasks, Olga proposes what day and time each task should happen.
- Spreads work sensibly across the week instead of piling it all on one day.
- Warns when a day looks unrealistic — "Wednesday has 11 hours scheduled — that's too much."
- Suggests rearranging when new work arrives — as a proposal, at decomposition time or when you ask. The proactive version, where she rearranges on her own initiative from capacity analysis, is Phase 2.
- Yields to you. Users override her by dragging tasks or asking her to reschedule. Nothing moves without your action or confirmation.
It has to feel instant
Dragging a task gives immediate visual feedback — the change appears on screen before it is saved to the database. A Planner that hesitates on every drag would not survive weekly use; snappiness here is a requirement, not a polish item.
Roadmap