Most people already own a calendar and a to-do list, and I do not think another of either would help them much.

The calendar is for things that happen at a time: meetings, flights, the dentist, the client call that starts at 14:00 because other people have made the unfortunate decision to exist in time too. The to-do list is for things you intend to do: send the note, fix the invoice title, read the document, remember the thing before it escapes and becomes a vague discomfort during dinner. Both are useful. Neither quite fits the way my week actually works.

Most of my work sits between the two. It matters, but it does not always have an hour attached. A task can belong to this week without belonging to 10:30 on Wednesday, and an idea can be worth keeping before it is firm enough to be a task at all. Some of the work has edges already; some is still uncut material. Slate is built for that gap.

Calendars are good at time

A calendar knows when the train leaves and when the call starts, and at fixed commitments it is very good. The trouble starts when I ask it to carry work that does not behave like an appointment. If I put “write proposal” from 9:00 to 10:30 on Tuesday, the calendar believes me. It draws a rectangle and the future looks handled. Then Tuesday comes, the call before it runs over, a new message changes what the proposal needs, and the rectangle stops describing the day even though the work itself has not changed.

That is why I stopped making my calendar carry ordinary work. It is excellent at external commitments and much worse at the half-defined, flexible, human mess of a week.

To-do lists are good at intent

A to-do list has the opposite strength. It accepts almost anything: “follow up with Mira,” “fix onboarding note,” “maybe revisit pricing page,” “think about Mark.” It asks few questions, which is exactly what capture needs.

After a while, though, the list becomes a drawer with no bottom. It keeps intentions alive and decides almost nothing about which ones deserve the week, so people start adding due dates.

Most task due dates are guesses wearing formal clothes

A date field looks responsible, like the adult in the room. But most of the due dates I have put on tasks were guesses, not deadlines.

“Wednesday” usually meant: I hope the week has room for this by then. The app treated that hope as a promise, so when Wednesday arrived and the task was still undone, it had a word for me: overdue.

That word is too heavy for what happened. I was not late for a flight or a tax filing. I guessed wrong about my own week, which is one of the most ordinary things a person can do. So instead of the week giving you something to build on, you open it and get handed a small, steady sense of having already failed. That is a strange thing for a planning tool to manufacture before nine in the morning.

Placement is the plan

Slate takes a simpler position: if a task belongs on Wednesday, put it on Wednesday. It does not turn into a fake deadline or an event, and it does not get a block of time. You are marking the place where you intend to meet the work. That is your weekly slate.

Not everything deserves a day yet

The other half of Slate is the Idea Backlog, which I built because I kept needing a place for work that mattered before it was ready. Corporate work produces a lot of this. Some tasks arrive clean: send the follow-up, book the appointment. Others arrive as “figure out the client feedback” or “do something about the onboarding notes,” things that matter but are not yet tasks. Forcing them into Tuesday does not make them clearer; it just makes Tuesday worse.

The Backlog is where those items wait without disappearing. It will hold a phrase, a rough task, a named list, a possible errand, a decision you are not ready to make. Used honestly it is less a junk drawer than the uncut pile beside a workbench. Some of what sits there is ready for the week; the rest needs more cutting first.

Planning is not scheduling

Scheduling is what you do once the constraints are known. Planning is what you do while they are still arriving, and that second thing is what Slate is built around.

Most of my week is not knowable on Monday. A client will clarify the wrong thing, or a small task will expose three hidden dependencies. Meetings generate new work, and the item that looked important on Friday can look faintly ridiculous by Tuesday afternoon.

A planning surface has to leave room for all that. Work moves from rough material to weekly commitment, a backlog item sits until it earns a day, and Wednesday gets to change without the whole system making you feel bad about it. Slate sits in the space the two older tools leave open.