Every job looks easy from the outside
The word “easy” usually means the speaker has not seen the details. Sometimes it means the specialist has stopped looking for a simpler way.
“Easy” is a word that’s used to describe other people’s jobs.
The line comes from Rework, the book Jason Fried and David Heinemeier Hansson of 37signals published in 2010. The observation behind it is familiar to anyone who has worked in a team. A request arrives framed as small: “just add a button”, “it’s only a quick email to the list”, “can you knock out a logo this afternoon”. The person asking is sincere. They cannot see the database change behind the button, the legal review behind the email or the three rounds of revisions behind the logo.
Psychologists have a related name for this. Daniel Kahneman and Amos Tversky described the planning fallacy in 1979: people underestimate how long their own tasks will take. With other people’s tasks the error grows, because the estimate is made without any of the details that would slow it down. The less someone knows about a job, the more it resembles its description, and descriptions are always short.
In a young company the cost shows up in two places. Founders who have never done sales tend to assume a good product sells itself, and they budget accordingly. Founders who have never run support assume it can be handled in spare hours. Both find out otherwise when the work lands on them. Managers who call a task easy also send a message to the person doing it: that any difficulty they report is an excuse. People stop reporting problems, and estimates get worse.
The fix Fried’s company favored is to have people do a little of each other’s work. At 37signals everyone, including programmers and designers, took turns answering customer email. Someone who has spent a day in support stops calling support easy, and usually starts building fewer features that generate tickets.
The line has a blind spot. Specialists can also overstate how hard their work is, sometimes to protect their time and sometimes because they are attached to a complicated method. An outsider who asks why a task takes two weeks occasionally finds that it should take two days. A good answer to “this should be easy” is an explanation of why it is not, and a good response to “this is hard” is to ask what makes it so. Both sides learn more than they would from either word alone.
The practical habit is to replace the word with a question. “How long do you think this will take, and what could make it longer?” invites the person who knows the details to share them, which is the only way anyone else learns how easy the job really is.