# Attention *The answer that feels responsible* --- Most of a senior job is deciding where things go rather than doing them yourself: where the money goes, where your own hours go, and where your few load-bearing people spend their time. In each of the three, there's an answer that feels responsible, and it's usually the expensive one. ## Spend capital on the structure, not the magic Most of the AI cases I've been asked to back die on the two dullest questions: what is the actual problem, and how will we know it worked. The ones worth backing are rarely the exciting ones. A faster first draft of a document saves real minutes, but it doesn't move revenue or cost by itself, and it's easy to wave through as if it did. This decade the proposals say AI; last decade they said cloud, and before that e-business. The two dull questions don't change. What pays is the boring structural work: reworking the workflow underneath, and getting the data and systems into a state the tools can use. An agent doesn't see a business the way an org chart does - it doesn't care who reports to whom, it sees the work and the data. In most mid-size businesses the real bill is codifying what the place already knows, and that's the one people flinch at while the trade press fills with claims that someone else got the magic for free. The numbers usually dip while you're doing it, too, because data quality drops the moment you start looking at it honestly. Backing the visible magic feels responsible; the structural work is where the money should go, and riding out the dip it causes is what your nerve is for. ## Give away the work you are best at You reach a senior seat partly by being good at something, so there will always be work you could do better than whoever you hand it to. The books say delegate; in a mid-size business that is only half right, because sometimes the quickest thing is to do it yourself, and being too grand for the spreadsheet is its own kind of failure. But the work you are best at is the stuff that ends up stuck to you, and holding it feels responsible too: nobody else will do it as well, and you can prove that every time you check. Handing it over means watching it done worse than you would do it, and the reflex is to grab it back. I did exactly that with one piece of work and spent the better part of a year as the bottleneck on it. Do that twice and the person you gave it to has learned it was never really theirs. Better to let it run at eighty per cent under someone whose job it now is. The one person who can't afford to hold it is you. ## Protect your best people from the urgent The scarcest thing you allocate is the attention of the handful of people everything routes through, not your own time - and they are always the ones the next fire wants too. Left alone, the urgent wins every time, because the fire is loud and has someone standing behind it, while the important work is quiet and easy to keep putting off. So stand in front of those people and take the requests yourself: some turn out not to need them at all, and the rest can wait or go in a batch. A key person's queue fills faster than they can clear it - problems take longer to fix than they took to arrive - so it only grows unless someone guards it on purpose. Sooner or later, though, the request that arrives isn't one you can quietly absorb. Someone senior wants one of your people by name, for a fire that's burning now, and the person they want is carrying something of yours that matters. Feeding the fire is the answer that feels responsible, and the instinct to simply defend is the next most tempting one. Both skip the actual work. Start by taking the urgency seriously. Someone asking for another director's key person knows what they're asking and is in enough pain to ask anyway; the request itself is evidence. Then notice what a request for a named person actually is: an answer somebody has already chosen. You're being handed a solution with the problem still inside it. Get some space between the two. Play the problem back until they agree you've understood it - before that, any alternative you offer lands as wriggling out of helping; after it, alternatives become contributions to something you're both looking at. Then widen the options, with their original request inside the list as a candidate rather than the thing under attack. What widens it is naming the constraints and asking which ones flex: how long they've actually got, what standard the answer has to meet, whether a serviceable answer now beats a complete one later. And your own programme's constraints go into the same exercise, in the same conversation, because if only their side gets examined you'll win these encounters on process rather than merits, and you won't notice you're doing it. Do that and you get one of four outcomes. An answer falls out that's better than the one proposed. Or several credible options appear, and the routes that don't need your person get a fair hearing for the first time. Or you conclude the person really is the only feasible answer, in which case the trade-off gets made explicitly rather than absorbed quietly, which is the process working. Or you refuse, and let it escalate to whoever adjudicates, with something behind your no. That last one has to stay available. A process whose outcomes never include no is a process for making yes feel collaborative. If you do hand the person over, your own programme now has a problem: operating without them for a while. It deserves the same treatment you just gave the other one. Go back to the team, explain what was decided and why, and give them the authority to move something - a date, a deliverable, a standard. A team that's been told what was traded knows which constraint they're allowed to flex. Skip that, and the lesson the people carrying your strategic work take away is that their programme is negotiable and nobody explained why. And guarding it means letting a real fire burn sometimes, with a name on it and someone asking why you didn't help. The failure, when it comes, is only ever obvious afterwards: a run of weeks where the urgent got all the good hours, and the important thing hasn't moved at all. ---