The Courtesy Copy

Adrian's emails were models of courtesy. He thanked colleagues for their efforts, acknowledged competing priorities and copied everyone who might later need to know what had happened. When a project slipped behind schedule, his messages provided an immaculate record of his concern.

At the quarterly review, his manager praised his documentation and asked why the same problems kept returning. Adrian explained that he had raised them repeatedly.

"I can see that," she said. "What happened after you raised them?"

He regarded the question as unfair. Other teams controlled the decisions. He could not be expected to do their work as well as his own. Nevertheless, he opened the email trail that evening and read it without focusing on the dates.

He found warnings addressed to groups, requests that named no decision-maker and summaries that made disagreement look like progress. His language was so carefully balanced that it rarely required anyone to respond.

The next morning, he sent a shorter message. It identified two options, explained the consequence of delaying and asked a named colleague to choose by Friday. He offered to join a call if either option was impractical.

The reply was not especially polite. It contained objections that his earlier messages had somehow avoided. By lunchtime, however, they had agreed on a revised approach.

Adrian kept documenting decisions. He simply became less satisfied when the only thing a message achieved was proving that he had sent it. The archive was still useful; it was no longer a substitute for a conversation.