Tasks is now a work desk: four views, one board

PRODUCT UPDATE · FROM THE ANALYST DESK. Most procurement teams do not lose renewals because they lacked data. They lose them because a piece of work sat in a place nobody looked at during the eleven weeks that mattered. The chase email to legal, the security questionnaire that needed a second reviewer, the note to ask the SAM manager whether those 340 seats are actually assigned. None of it is hard. All of it is easy to drop. We have rebuilt Tasks from a single board into a work desk with four views of the same underlying runway, a file for every task, and keyboard control that keeps your hands off the mouse.

The named problem: your runway lives in three places and none of them agree

Here is the shape of the problem as most buy side teams experience it. The renewal calendar knows the dates. The contract record knows the terms. The actual work of getting from here to a signed agreement lives somewhere else entirely, usually a spreadsheet a category manager built in 2022, a Kanban board in a general purpose tool that nobody outside procurement can read, and a thread of emails where the real decisions were made.

The cost is not dramatic. It is quiet and cumulative. A questionnaire response sits unowned for nine days because two people each assumed the other had it. A notice window closes while the task to send notice is still in a column called Later. We have written before about how the auto renewal clause turns an unworked task into a twelve month commitment, and the mechanism is almost always the same: the work existed, but not in a place where its absence was visible.

A board fixes visibility for the person looking at the board. It does not fix the other three questions a working team asks every day. What is mine, right now, in the order I should touch it. What is the state of the entire runway when I need to scan it in one pass. And who is carrying what, including the work that nobody has picked up.

One board, four views, and a masthead that states the position

The desk opens with a masthead that states where the work stands rather than decorating it. Below the masthead is a band with four views. They are not four tools. They are four readings of the same board, so a card moved in one appears moved in all of them.

Board is the drag and drop view you already know, kept intact for the weekly stand up and for anyone who thinks in columns. My day strips the board down to every active task assigned to you, arranged in landing order, with one click to complete and one click to defer. It is deliberately narrow. It answers a single question and then gets out of the way. Ledger is the table: the whole runway, sortable, scannable, built for the pass you make on a Monday morning when you want to see everything at once rather than everything that is yours. The bench shows load by owner, who carries what, and underneath it a pick up tray of unowned work that any team member can claim with a click.

The pick up tray is the piece we expect to change behaviour most. Unowned work is the single most reliable predictor of a missed window, and in a column based board it hides in plain sight because a card without an avatar looks identical to a card with one at a glance. Pulling it into its own tray makes the absence of an owner the visible fact, not a detail.

Every task has a file, and the file is shareable

Click any task in any of the four views and its file opens. This is the substantive change, and it is the one that matters most for people outside procurement. The file is a panel where status, due date, owner and notes all edit in place. No modal chain, no separate edit mode, no round trip to a different screen to change a date.

It is also shareable. That single property removes a category of work most buyers do not think of as work: the translation layer. Today, when legal asks what you need from them on the Salesforce renewal, you write a paragraph describing a card. With a file you send a link, and legal sees the status, the date, the owner and the notes without an account tour or a screenshot. The same applies to the finance partner who wants to know whether the diligence step is done before they release the budget line.

This connects directly to how we think about the rest of the desk. The renewal calendar tells you when. The playbook tells you what position to take, and the kickoff interview turns a blank dashboard into a set of concrete first moves. Tasks is where those moves become work with a name against them and a date they are due.

Keys, and why a two second saving compounds

Keys 1 to 4 switch views. Forward slash searches. N starts a new task. That is the whole scheme, and it is intentionally small enough to learn once and never look up again.

The argument for keyboard control is not that a category manager cannot find a menu. It is frequency. A buyer working four live renewals touches this desk twenty or thirty times a day. Pressing N to capture a task while still on a supplier call is the difference between the task existing and the task being something you meant to write down afterwards. Capture friction is the reason runways go stale, not laziness.

The four view band also has an audience effect worth naming. The Ledger is the view you put on the screen in a governance meeting, because a table of owners and dates is legible to a CFO in a way a column board is not. That is the same instinct behind presenting the next four quarters straight from the calendar: show the working system rather than a slide about the working system.

What changes for a procurement buyer

Honest limits

Four things this release does not do, stated plainly so you can plan around them.

First, it is not a project management tool and we are not trying to make it one. There are no dependencies, no critical path, no Gantt view, no sub tasks. If your renewal genuinely requires a dependency graph, and a small number of large migrations do, you will still run that elsewhere and use Tasks for the procurement work stream. We think that is the right boundary. A tool that models everything usually models nothing well.

Second, the four views are readings of one board, which means they inherit the board's assumptions. If your team has not agreed what a column means, adding a Ledger table does not create that agreement. It just displays the disagreement in a second format. Spend twenty minutes agreeing your stages before you roll this out to a wider group.

Third, the pick up tray only works if people look at it. Making unowned work visible is a necessary condition, not a sufficient one. If your operating rhythm has no moment where someone checks the tray, orphaned tasks will still age. We would suggest attaching it to an existing meeting rather than creating a new one.

Fourth, shareable task files are shareable within your tenant's permission model. They are not public links you can send to a vendor. That is a deliberate constraint. The notes field on a renewal task frequently contains your walk away position, and no interface convenience is worth putting that a single forward away from the other side of the table.

One more limit worth naming. This release improves how you carry work. It does not tell you what the work should be. That still comes from the calendar, the playbook and the benchmark. What it does is close the gap between deciding on a move and the move actually having an owner and a date, which in our experience is where more renewal value leaks than in the negotiation itself.