Owning Your Work: Action Items, Priorities and Handover

An action item is real when it carries one owner, one date and one described finished thing. Two owners means none. Under pressure, the order runs: first what somebody else is blocked on, then what carries a hard outside date, then what is largest. A handover is one sheet: what is still open, what somebody else is holding, what comes next, and where the file sits.

The three conventions above look like housekeeping. Housekeeping is not what they are. Look at where work on a desk actually goes wrong. Work very rarely goes wrong because a person could not do the thing they were asked to do. Work goes wrong at the joins: between two people who each thought the other had it, between a task and a date nobody wrote down, and between the person who left on Friday and the person who arrived on Monday. Every one of these conventions is about a join. None of them is about being better at the work, and all of them are about the work surviving contact with other people.

One assignment runs through this guide, the same one running through the surrounding subjects. The Kavery research desk sits inside Kavery Capital Services Private Limited, an invented lender. Sharada Iyer, seven months into the role, produced a piece of work on Meenakshi Tubes Private Limited, a borrower whose working capital line was up for renewal. Prakash Nadar reviewed it. Latha Menon chaired the meeting on 12 March where it was taken through in front of six people, and the decision of 12 March was that the line falls from Rs 40,00,000 to Rs 25,00,000, reviewed again in 90 days. The machinery that ran after the meeting ended is what matters, and it would have run the same way whatever the borrower manufactures.

One more thing shapes all three conventions: none of the moves below needs rank. Advice elsewhere tells an analyst to protect their time, push back, or decline the third thing handed over on a Tuesday. Advice like that assumes a person who is allowed to decline. Somebody in their first month is usually not that person, and the honest position is that they should not be. Every move set out here meets a harder test: it can be made by somebody with no authority, no team and nobody who owes them a favour, on a Tuesday afternoon.

What makes an action item real rather than a note of intent?

An action itemA recorded commitment that something specific will exist by a specific day, carried by a specific person. It is the smallest unit of work that other people can rely on. is not a task and it is not a reminder. An action item is a promise recorded in front of witnesses, and it becomes real the moment it carries three fields. One ownerThe single named person accountable for the item. Not the team, not the desk, not whoever is free. One name.. One date. One described finished thingWhat will exist in the world when the item is done, described so that anybody can look at it and say yes, that exists, or no, it does not.. Miss any one of the three and the item will not be done, and the failure has a signature that can be spotted in four seconds.

The three fields are not a template, they are three different questions, and each one is missing from real meeting notes for a different reason. The owner is missing because naming one person feels like singling them out. The date is missing because nobody in the room wanted to commit to one. The finished thing is missing because the item was written down while somebody was still talking, and what got captured was the topic rather than the output. Three different social pressures, one identical result on the day.

The check runs on any set of notes just received: not to correct anybody, and not out loud. The check is simply a count of how many items carry all three fields. On most notes it is under half, and the ones that are complete are the ones that got done. The correlation is not a coincidence and it is not about discipline. An item with three fields can be checked by anybody at a glance, and an item that can be checked by anybody at a glance tends to get done by somebody.

Why does an item with two owners get done by nobody?

A desk cannot do anything. Neither can a team, a workstream or the research side. Only people do things, and the moment an item names something other than one person, who is doing it has been left open in a document that looks closed. The two owner version is worth being precise about: it is not the same mistake as the no owner version, and it feels considerably safer.

Here is the mechanism, and it is not about people being lazy. Two names on one item creates two people who each hold a reasonable belief that the other has started. Each belief is reasonable because neither has been contradicted. Nobody is avoiding the work. Both of them would do it happily if asked. The item generated no signal in either direction, and silence reads as coverage to both of them. Shared ownership does not divide the work between two people, it divides the certainty, and half of a certainty is not a commitment.

Think about a household with two adults and one gas cylinder booking. If both are responsible for booking it, the booking gets missed at least once, and neither person did anything wrong. The evening it runs out, both say the same sentence: they thought the other one had done it. Nobody in that household is careless. The arrangement was careless. Move the same thing to a desk with a credit committee date on it and the consequence is larger, but the mechanism has not changed at all.

There are two clean fixes and both take one line. Splitting the item into two items with one owner each is right when the work genuinely has two halves. Naming one owner and one helper, with the owner named first and the word helping written down, is right when the work is one thing that two people will touch. Either way exactly one person knows the date is theirs, so the item now generates a signal.

Why does the finished thing have to be described rather than named?

People argue with the third field. Writing it feels like being asked to add words about something everybody in the room already understood. The room did understand it. The room will not remember it. Three weeks later the item says review the concentration point, and four people have four different pictures of what would satisfy that, all of them defensible.

The test is mechanical, and it runs on any item in a second. The question about the item is this: on the date, what will exist that is not there now. If the answer is a sentence about a thing, the item is written. If the answer is a sentence about an activity, it is not. Look into, review, think about, follow up on and discuss with all describe activities, and an activity can be performed for two minutes or two days and both count as having happened. An artefact either exists on the date or it does not, so describe the artefact rather than the effort. No conversation is needed to establish which.

Compare the two versions of the same item. Look into the floor, by 12 April. Against: a note by 12 April saying whether the desk's own 11 per cent operating margin floor, an internal policy and not a rule of lending, was applied to the other borrowers reviewed on the same cycle, and where it was not. The second one is twenty six words longer and it removes every possible disagreement about whether it was done. The longer version also does something quieter and more useful: it tells the person doing it when they are allowed to stop.

How to Prioritise Finance Work Under Time Pressure: What Goes First When Everything Is Due?

PrioritisationDeciding the order to do things in when there is not enough time to do them all now. It is a question about order, never about which ones get dropped. gets taught badly because it is usually taught as choosing what not to do. For most people that choice is not on offer. Four things are due, all four came from somebody entitled to hand them over, and all four are going to be done. The only real question is the order, and the order is decided by three tests run strictly in sequence.

Test one. Is somebody else stopped until this is done? Not inconvenienced, stopped. If a colleague cannot start their own work until a two minute reply arrives, that two minute reply outranks the half day task carrying the analyst's own name. Anything blockingSomebody else cannot proceed until the analyst's part is done. Their work is sitting still, and the time is being spent whether it is noticed or not. somebody goes first. A delay on a blocking item is not one delay but two, the analyst's plus somebody else's, and it keeps multiplying while the analyst works on something else. Blocking items are usually small, and small things feel postponable. Test one therefore reverses the order instinct would have chosen more reliably than any other test.

Prioritisation When Work Cannot Be Declined: What Are the Second and Third Tests?

Test two. Is there a date set outside this desk? A committee that sits on a fixed day, a renewal that falls due, a customer meeting already in a diary, or a promise made out loud in a room in front of six people. The working test for a hard dateA date fixed by somebody outside the work, which cannot be moved by asking. The opposite is a date set by the analyst or the reviewer, which usually can. is simple: can this date be moved by asking politely? If yes, it is a soft date and it belongs behind the hard ones. If no, it is hard. Where two things both clear this test, the earlier date goes first. Nowhere else in the sequence is the obvious answer also the right one.

Test three. Which of the rest is largest? Start the largest of the remainder. Size is not urgency. The largest item is simply the one most likely to run past the estimate of it, and today is the only day on which running over can still be discovered early enough to tell somebody. The effect in the common case is worth seeing. A big frightening task that blocks nobody and has no outside date loses the first two tests and ends up last anyway. Last is exactly where it belongs, and exactly where dread would never have put it. Size is the tie break between things that have already survived the first two tests, and it is never the way into the list.

Here is the order the three tests produced on one real morning of this assignment, 21 March, the day after the meeting. Five things were on the list. The order the last column produced is almost the reverse of the order the list would suggest, so read that column before the others.

The two minute item went first and the item that felt like the real work went fourth. Test three did one job at the bottom of that list and only one: between the two items with no date and nobody blocked, the larger went first. If the second borrower file turns out to be three days rather than one, the useful moment to know is Wednesday and not the following week. The twenty minute redaction, waited for by nobody at all, went last and stayed undone until after the leave, and that was the correct outcome rather than a failure.

What happens when two priorities conflict and nobody is reachable?

Now the case the ladder does not settle. Two people have each handed over something, both said today, and both of them are unreachable. The clash is not rare and it is not a sign that anything has gone wrong. The clash happens because neither of them knows what the other asked for, and there is no reason they should.

Waiting feels neutral and safe, so most people wait. Waiting is neither neutral nor safe. Waiting is a decision to do nothing, taken on behalf of two people who did not agree to it, and at the end of the wait the original conflict is still there and there is less time. Waiting is not the absence of a decision, it is the one decision in the set that nobody asked for and nobody would have chosen.

The move that works instead costs nothing and needs no standing at all. Both instructions are written down in the words they were given in, an order is picked, and one short message goes to both people saying which order is being taken, why in one line, and by when they can say otherwise. Then the work starts. If somebody objects before the hour named, the order switches and almost nothing is lost: only two hours have gone into the first item rather than five. If nobody objects, there is a written record that the question was asked, and the work has been going on the whole time.

Why is this not an escalation in the ordinary sense? Because it asks nobody to decide anything. The message does not put two people in a room to sort out their competing claims. A junior analyst has no power to arrange that meeting and no standing to request it. The message hands each of them a decision they can make in three seconds by themselves, and it makes not replying the cheapest correct option for both. Asking nobody to decide anything is why the move works for somebody in their first month, and it is also why it keeps working later.

What Goes in a Handover, and How Long Should One Take to Write?

A handoverA short written note that lets somebody else pick the work up while its owner is away, without needing to speak to them. is one sheet with four parts, and it takes about half an hour. If it is taking half a day, something is wrong, and the wrong thing is almost never the note. Every part of the note is a pointer, and a pointer only stays short when the thing it points at can be opened by somebody else with nobody standing next to them.

The reason a handover can be half an hour rather than half a day is that every one of its four parts points at something instead of describing it, and pointing only works if the file at the other end can be entered by a stranger. The whole of the return on how a workbook is built and how a source log is kept arrives here, three weeks after the file was opened on 3 March, in a form nobody was thinking about at the time.

Which part of a handover is the one that always goes missing?

The second one. Waiting on somebody else disappears from almost every handover note ever written, and the reason is structural rather than careless. Open work sits on the writer's own list, so it is visible. Part three, what comes next, is in the writer's head, so it is visible. Where the file sits is in front of them. But the thing requested from somebody on 21 March is not on the writer's desk at all. The request sits on theirs. Nothing in the writer's own working day is a reminder of it, precisely because they are not the one waiting.

The cost lands entirely on the person covering. The covering person spends three days on the work, the document arrives, and they have no idea it was requested, what it was requested for, or that it was already chased once. Or worse, it does not arrive at all and nobody chases it: the only person who knew a chase was due is away. The second part carries four things every time: what was asked for, who was asked, the date of the request, and what should happen if it has not arrived by a stated day.

What did all of this look like on one assignment?

The meeting of 12 March produced four action items. Each carried one named owner and one date. Two of them were Sharada Iyer's, and both closed on their dates. Closing them mattered more than it sounds: the leave started on 24 March, and an item left open across five days of absence stops being an item and becomes somebody else's problem.

Four items, four dates, and only three owners between them: two of the four sat with the same person. Notice what is not in that table. The 90 day review agreed on 12 March falls on 10 June, and it is not an action item. The review is a line in the decision record with a date and no name against it. A date in a record is a reminder; it becomes an item the day somebody's name goes beside it, and until then it is held by whoever happens to reread the record. The gap is real, and it is worth seeing that even a well run meeting leaves one.

Then 24 March, and five days of leave. The handover note ran to one sheet and took under thirty minutes to write: what is open, what is waiting on somebody else, what comes next, and where the workpaper sits. The colleague picking it up had not been in the room on 12 March and had never touched the Meenakshi Tubes Private Limited file at all.

The handover worked for a reason that had almost nothing to do with the note. The workbook it pointed at was one file with a checks tab at the front, built between 3 March and 11 March, and it could be entered cold. Entering the file cold is a measured property rather than a claim: a different person on the desk, with no conversation with anybody who did the original work, rebuilt the 10.8 per cent operating margin out of that workpaper in 25 minutes. The thirty minute handover and the twenty five minute cold rebuild are the same property of the same file measured twice. A handover rests on the file conventions rather than on the writing of the note.

How does work get handed back rather than a problem?

Handing back is the mirror of the handover and it is the one people get wrong most often, usually at the end of a piece of work when they are tired of it. The distinction is between returning three threads open and returning three threads either closed or explicitly named as open with a date and a person against each. Closing what was openedFinishing every thread started, or, where it cannot be finished, naming it as open with who has it and by when, so that nothing quietly stops existing. is the whole of it. Plenty of threads genuinely cannot be closed by the person who opened them, so the second half of that definition matters as much as the first.

The whole difference between the two columns is four lines of writing, and it decides whether the person receiving the work starts with it or starts by investigating it. There is a version of this that is worth building into how any piece of work is finished: before it goes back, every thread opened during the work is listed, and each one is put in one of two states. Done, with where it landed. Or open, with who holds it and by when. No thread is allowed to be in a third state, and the third state is the one that quietly consumes other people's weeks.

What does owning a piece of work mean without authority?

One sentence most people never get told is worth reading twice. Ownership and authority are two different things, and the second one is not required for the first. A person can be entirely accountable for something they cannot make happen by themselves. The split sounds unfair for about a minute, and then it stops sounding unfair once what ownership actually consists of in that situation becomes clear. The list is short and very doable.

The standard case runs like this. An item depends on a reply from somebody two levels above the analyst, and the reply has not come. The reply cannot be compelled. The reply cannot be escalated in the way the word usually means. Whose problem is the item? The analyst's, still, and the reason is not moral, it is practical: the analyst is the only person who can see that it is going to be late. Everybody else finds out on the date.

So what does owning it look like on Tuesday, when the date is Friday and the reply has not come? Owning it looks like one sentence sent on Tuesday to the person expecting the item: the item is at risk because I am waiting on a reply I asked for on the 18th, here is what I will deliver on Friday if it does not come, and here is what changes if it does. Ownership without authority is a duty to say what will happen before it happens, and that duty is fully dischargeable by somebody with no standing whatsoever. A person who does that twice becomes the person nobody has to check on, and that is worth more inside a desk than being right about anything.

Who else runs on action items, and what do they do with them?

None of this is a research desk convention. Any group of people does the same when work has to cross between them. Seeing the same three fields in three other places is what stops them feeling like paperwork.

A credit officer at a lender keeps a diary of review dates, and every single line in it has a name against it. When a line falls due and the name is a team, the review does not happen, and the first anybody knows is when the borrower's position has moved and nobody looked. The missed review is the same defect as the one in the block above, at a scale where it costs money. The cost is also why a lender's covenant monitoring list is one of the most rigidly single-owner documents in any financial institution.

An audit senior runs an open items list across the whole engagement, and it has exactly the three fields on it: the point, the person, the date. The reason auditors are unromantic about this is that an engagement has a hard external date at the end of it and forty threads running into that date, and the only thing that makes forty threads survivable is that each one is somebody's. Ask anybody who has closed an audit what the last two weeks consist of, and the honest answer is chasing items that were written without one of the three fields six weeks earlier.

And the household version, the one that makes it stick. A wedding has perhaps forty things to be arranged and several people arranging them. The ones that get missed are never the difficult ones. The difficult ones have somebody's name on them because they were obviously going to be hard. The missed item is always the small one everybody assumed somebody else had picked up, discovered on the morning of the event, when it is both trivial and unfixable. Every group of people that has ever missed something small and obvious has missed it in exactly this way. The three fields are a convention about people rather than about work.

The Kavery research desk, Kavery Capital Services Private Limited, Meenakshi Tubes Private Limited, Sharada Iyer, Prakash Nadar and Latha Menon are invented.
Educational material. Not advice on any investment, tax, budget or market position.