The Quiet Proposal

For three weeks, Eva had kept a document called “Small improvements” on her laptop, opening it late in the evening and closing it again before anyone could notice. It contained a plan to reduce the time her team spent answering the same customer questions. She had shown it to nobody, partly because she was new and partly because the plan, in her own judgement, was still unfinished.

During a team meeting, her manager mentioned that several customers had complained about slow replies. Eva nearly raised her hand, then decided to wait until she had better figures, a decision that she would later describe as sensible and cowardly in equal parts. By the end of the meeting, two colleagues had suggested hiring more staff, and the conversation had moved on.

That afternoon, Eva asked her colleague Tom to read the document. He liked the idea of a shared answer library, but he noticed something that she had overlooked: the plan did not say who would keep the information up to date, so within a month the library would be as unreliable as the replies it was meant to replace. Together they added a simple weekly review, and for the first time the plan felt like something that could survive contact with a real team.

Eva sent the proposal to her manager the following morning. Instead of claiming that it would solve everything, she suggested testing it with one type of question for two weeks, and she named the information they would collect in order to decide whether the trial had been worthwhile. It was a modest request, and she suspected that its modesty was exactly what made it difficult to refuse.

The manager agreed to the trial and asked Tom to help. Some answers still needed individual attention, but routine replies became easier to find almost at once. Eva realised that sharing an unfinished idea with the right person had improved it more than another week of working alone would have, and she deleted the word “unfinished” from the title of the file.