One surface, three views: how Horizon plans your work

Most tools pick a shape for your work and make you live inside it. A board app turns everything into columns. A calendar app turns everything into dates. A sprint tool turns everything into a two week march. Each one is right some of the time and wrong the rest of it, so you end up with three apps, three copies of the same tasks, and a standing tax of keeping them in sync.

Horizon is our answer to that. It is one planning surface with three views: Sprint, Calendar, and Kanban. They are not three products stitched together. They are three lenses on the exact same tasks. Move a task in one, and it has moved everywhere, because there is only ever one task. The view you are looking at is a choice about how to see your work today, not a place you have to copy it to.

Why a view is not a container

The core idea is small and it changes everything: a view is a way of reading your tasks, not a bucket that owns them. Your tasks live in projects. Horizon reads them and arranges them by the thing that matters for the question you are asking. When you want to know what to do this cycle, you read them as a sprint. When you want to know what lands on which day, you read them as a calendar. When you want to know what stage each piece is at, you read them as a board. Same data, three questions, no duplication.

Horizon remembers the view you left in, so it opens where your head already is. Switching is one click, and nothing is lost in the switch because there was nothing to move.

Sprint: what to finish this cycle

Sprint is the view for committing to a slice of work and finishing it. It runs on whole calendar weeks: every sprint starts on a Sunday and ends on a Saturday, so the grid always reads Sunday through Saturday with no ragged edges. You set the length, from one to four weeks, and the cadence just repeats. Tasks carry story points, so the header can show you committed against done, and a velocity bar builds up a picture of what your weeks actually hold rather than what you hoped they would.

Sprints also have the three moments that make the ritual worth keeping: a goal you write at the start, a review at the end, and a short retro. When a cycle closes with work still open, the carryover step moves it forward on purpose instead of letting it quietly rot at the bottom of a list. The point is not ceremony for its own sake. It is a clean start and a clean finish, every week.

Calendar: what lands on which day

Calendar is the view for time. It lays your tasks out on a full month grid by due date, so deadlines stop being a list you scroll and become a shape you can see. Drag a task to a different day to reschedule it. Click a day to add work straight into it. It answers the question a sprint cannot: not what to finish this cycle, but what is actually due on Thursday, and whether next week is quietly on fire.

Kanban: what stage each piece is at

Kanban is the view for flow. One board for the workspace, with columns you name and reorder to match how work actually moves: Backlog, To Do, In Progress, whatever review stages you run, and a terminal Log. Drag a card across, or move it from the task drawer. The Log column is special. It is tied to completion and it does not move, because finishing is the one column that should always mean the same thing. Watching cards pile up in the Log is the point of the whole product in miniature: proof of what you did, not just a tidier pile of what is left.

One surface, so the tool disappears

When the three views share one set of tasks, the overhead that usually comes with planning just is not there. Nothing to reconcile, no second system of record, no Sunday night spent copying cards between tools. You plan the cycle in Sprint, sanity check the dates in Calendar, push the work across in Kanban, and it is all the same tasks the whole time. The best planning tool is the one you stop noticing, because it never asks you to maintain it.

Horizon is part of the Squad plan, alongside Project Blueprint and the full Didi suite. If a sprint sounds like more process than you want, start in Calendar or Kanban and never open Sprint at all. The views are there to serve the work, not the other way around.