In some of the many jobs I’ve done in my life, I found the most difficulty dealing with the response of, “That’s simple.” This statement was usually closely followed by a thoughtless assessment of how quickly it could get done/finished.
I know the truth.
Simple is never simple. Simple takes a long time to perfect. Okay, not perfect, but to make easy to do, see, explain. Simple is never simple.
Because if something is difficult or complex, a person sits down to do some work, they expect to have to delve deep into the research and plans and structures to find a way to get it done – properly.
If they think it’s simple, they leave it until the last minute (or few minutes/hours, or a day) and then discover there is quite a lot of work involved in the thing that appears simple on the surface.
Simple is never easy, it’s never fast, it’s never quick. It looks simple, but that’s like life. A good marriage may look easy, but is it?
How about a nice garden?
Or living in an uncluttered house?
Simple has so much subtext, that it should have a ‘Danger’ sign attached to it every time it’s used.
The next time someone says it, question the level of complexity as if it were the answer to ‘why’ that everyone finds at some stage.
Why isn’t simple simple?
Why is there subtext to everything?
Consider how we respond to the people close to us. They ask a question, but do we answer the question they ask, or do we analyse why it was asked, discover some sort of possible reason, and respond to our assessment rather than the question?
Don’t lie! Or if you think you’re not fibbing, really listen or analyse the next conversation you have with someone who asks you a question. Truly listen, even if it’s after the event.
“Wanna go to the beach?”
Analyse: Can I use this to get out of the work I/we should be doing around the house? Is it to get take-away on the way back? Is it to save money on air-con? Is it to make up after an argument?
“No, I need to [do this], but you go.” – an attempt at martyrdom, usually done to change the destination, or [some other agenda item].
Analyse: Laziness, too hot to get there, don’t want to waste money (this from the person who doesn’t cook, most likely), what argument? Finally, how can I use this to my advantage/get out of something else?
Or the work situation where the boss says, “I need that final piece of code tomorrow morning for the test bed.”
Analyse: the 80/20 rule. “Okay, I’ll finalise that before I leave today.” Read, assess, start – panic! “This isn’t what I expected! This will take all night.” and sure enough, when the sun rises, the job isn’t done, the manic look is in, sleepless and coffee create a caricature of a human being, and the simple bit of code isn’t complete …
Finding the simplest way to do something takes more effort than anything assessed as difficult or complex. We dismiss the concept of simple, somehow aligning simple with easy, but the truth will bite you, so beware the use of ‘simple’ or ‘that won’t take any effort, I’ll leave it until after I’ve done [the hard stuff].’
Can you see my face? The look of disbelief? That’s the look that comes from a lifetime of experience with the dichotomy of Simple to Complex.
Where did this little bit of brain-surge come from?
Rory, but I couldn’t reblog his Random Quote, so you should read it for yourself.
— * * * Yes, still editing, but I have a cover and a blurb, and the final straight is just around that bend …