Now-Next-Later

Drawing a roadmap on a calendar creates one specific problem: this quarter's column and the fourth quarter's column look equally solid. The near column holds work that's half built with people on it, and the far column holds work nobody has examined yet, but on the chart they're both just a box.

Pagedeck lived through it. A permissions overhaul sat in the Q4 column, and Sofia told a customer close to signing that it would arrive in October. She wasn't wrong to say it — that's what the chart said. The trouble was that nobody had looked at the item closely at any point. Work actually started the following March, and in between Sofia had to walk the same customer through a revised story three separate times.

Deleting the dates fixes that and leaves everyone who relied on the roadmap unable to read anything. Now-Next-Later keeps order and certainty and drops the calendar. Splitting work into what's being built, what comes after it, and what's only being looked into means far fewer conversations that begin with asking when the far column lands. The column name is already the answer.

Three columns, the items inside them, and a few fields attached to each item. Getting the meaning of the columns right is what makes the rest work.

1. Now — work with people actively building it. The number of items here never exceeds the number of teams that can move at once. Two teams and five items means three of them are not actually being built by anyone.
2. Next — work that starts as soon as a Now slot frees up. Usually the problem is settled and the solution is not.
3. Later — not work that's been agreed to, but work that's been agreed to look into. Items here disappearing entirely after some research is the normal outcome, and that disappearance is the column earning its keep.

Each item carries four fields.

1. A name and the problem it solves. Next to "permissions" sits "an admin can't open a single document to an outside partner." With the problem written down, the item can be swapped out when a cheaper solution appears.
2. What should be different once it's done, and the number that will show it.
3. Confidence. This field is the heart of the format, because even inside the Later column some items have a settled direction and others are still a coin flip.
4. An owner and a current state. Three states are enough: not looked at, being looked at, being built.

The rules for moving between columns belong in the document too. Promoting an item from Later to Next requires a line describing what was learned in between. Without that line, items get promoted in the order of whoever asked loudest. A milestone, a checkpoint for confirming progress, is attached only to items in the Now column; pinning one to work that hasn't started turns it into a date commitment by another route.

The product manager (PM) writes it and updates it with the build team roughly once a month. A PM is the role that decides what gets built and why, and owns it through release. The fixed cadence exists because items go stale on their own. Touch it once a quarter and the Now column still lists finished work, and anyone who opens that document once won't open it again.

Four audiences read it, and each looks at a different column.

1. The build team reads Next, so it can research what's coming while finishing what's in Now.
2. Sales and customer success read it for what they're allowed to put a time on. The rule is simple: only Now gets a timeframe, and everything else gets described by its column name.
3. Leadership reads the whole Now column, since where the company is spending its people this month is entirely contained in it.
4. When a version goes out publicly, Later is usually cut. It carries the least certainty and so gets misread most badly outside the building.

Having four audiences is also where the format most often breaks. Every stakeholder wants a different level of precision, so somebody is always asking for a date. Write a date in for one of them and within two months every column has dates in it.

"That one's in Later. It's not something we've agreed to do, it's something we've agreed to look at."

The request wasn't rejected, but it isn't a commitment either.

"There are five items in Now and we have two teams. Three of those belong in Next."

The column holds more than the staffing allows, so the document no longer describes reality.

"Tell the customer it's in Next. We can't give a date yet."

Confirming the rule that the column, not the person, decides what timeframe can be spoken aloud.

Pagedeck has used this format since the permissions incident. Mia reworks the three columns in the first week of each month and writes three lines at the top explaining what moved and why. Sofia checks only the Now column before a customer meeting, and Grace copies the Now column straight into the board deck. Later never leaves the company.

What disappeared after the switch wasn't the question about dates. It was the explanation owed when a date slipped. The questions still arrive, but the answer is fixed by the column name instead of being negotiated again each time.

The most common misreading treats the columns as units of time — Now is this quarter, Next is the following one, Later is after that. The names point at time, so the assumption is natural. What the columns actually separate, though, is certainty. An item in Next might start in six months, or next month if the current work finishes early. Read them as time and the document becomes a calendar with renamed columns, which brings back the exact problem it was meant to remove.

The second mistake is reading the absence of dates as commitment avoidance, a view that's especially common in sales. The opposite is closer to true. The Now column is a stronger commitment than any cell in a dated roadmap, because people are already on it and will still be on it next week. In exchange, the format promises nothing at all about Later. It trades away the total volume of commitments to raise the reliability of the ones that remain, and without seeing that trade the document just looks evasive.