Explaining to a colleague why you did not use the tool for this one

The question has changed direction

For a while the question was why you were using these tools. Now it is increasingly why you did not, and it arrives in ordinary forms: this took three days, could it not have been done in an afternoon, is there a reason we are still doing this by hand.

The question is usually reasonable and it is often asked by somebody with a legitimate interest in the answer. What makes it awkward is that the person answering rarely has a prepared reason, having made the decision on judgement, in the moment, for reasons that were obvious to them and are now hard to articulate.

An unarticulated reason under mild pressure tends to collapse into either defensiveness or a shrug, and neither of those is the reason you actually had.

Preference is a weak defence, consequence is a strong one

Saying that you prefer to write it yourself, or that the output feels wrong, may be entirely true and it will not persuade anyone. It sounds like taste, and taste loses arguments about time.

The stronger form names what would have gone wrong. The material could not leave the organisation. The check would have cost more than the work. The document commits us to a position and I need to be able to say why every line is there. This is a small enough job that the setup and verification exceed the saving.

Each of those is a claim about the situation rather than about you, and each is arguable on its merits, which is what you want. If the colleague can show that the check would have been cheap after all, you have learned something rather than won something.

Be specific about the part you kept

Most of these conversations are made harder by an implied all-or-nothing framing, where the choice is between doing the job by hand and handing it over. In practice the interesting answer is usually a division: the research was assisted, the argument was not; the transcription was automated, the interpretation was not.

Describing that division does two things. It shows the decision was considered rather than reflexive, and it moves the discussion to the specific step where you drew the line, which is where any disagreement actually lives.

It also protects you from a genuine error, which is refusing help on a whole task because one part of it needed judgement. That happens, and it is the mirror image of the mistake the question is worried about.

Where you can, describe the division in terms of what each part contributed rather than what it cost. Saying that the background reading was assisted and took an hour instead of a day, while the recommendation was written from scratch because it commits the team to something, is an answer that satisfies both halves of the question at once.

Some of the pressure is real and should be taken seriously

It is worth entertaining the possibility that you are wrong. Habits harden, and a method chosen four years ago for good reasons may be slower than the alternative now without your having noticed, particularly if you have not tried the alternative recently.

A fair response to being asked is to try it once, deliberately, on a real task, and to measure the whole thing rather than the fast part. That either produces a better answer or gives you a much stronger version of the one you had.

What should not happen is a change of method under social pressure without a test, which is how organisations end up with processes nobody can defend in either direction.

Where the answer is simply no

Some refusals do not need to be justified by efficiency, because efficiency was never the criterion. Material that cannot be sent anywhere. Work where the process is what the client is paying for. Situations where a person has to be accountable for a judgement and cannot delegate the reasoning behind it. A message to somebody that would mean nothing if it had been drafted.

In those cases the useful sentence is a description of the constraint rather than an argument about capability, and it usually ends the discussion, because the constraint is one the colleague also has to work under.

Having those cases written down in advance — the short list of what does not go through the process here, and why — turns an uncomfortable conversation into a reference to an agreed position. That is worth more than any individual defence you improvise on the day.