The A-Ruminations team discuss Healthy Tension.
Category Archives: Approaches
014 Convenience Vs Strength
The A-Ruminations team discuss the idea of Convenience Vs Strength.
What we give Up and Why?
012 Numbers
The A-Ruminations team discuss decisions, biology and all that it implies.
010 Value In Value – Reflection and Purpose
The A-Ruminations team discuss the Value In Value focusing upon Reflection and Purpose.
008 Spanner In The Works
The A-Ruminations team discuss the Utility of “Spanners In The Works” and analyse the advantages and pitfalls they bring.
007 Collaboration
The A-Ruminations team discuss and analyse Collaboration and what it means.
006 The Five Whys
Tobbe and Kim Discuss “The Five Whys” and the assumptions we make about them.
005 It’s Not Who You Know, It’s How You Know Who You Know
Kim, Tobbe and Steve discuss – It’s not Who You Know It’s How you Know Who You Know.
Positives and pitfalls of Social Networking, Company perceptions and Honest Relationships.
004 Autonomy and Agency
Kim and Tobbe discuss the better term of Agency over Autonomy.
OBSERVATIONS IN HOW THINGS GO 2
As a society based in the post Industrial revolution, where productivity and maximising profit rule the landscape and dictate our daily lives. We strive for “Efficiency” in our work lives and even our daily lives and many of us never really think about what we’re doing and the costs of our search for better, faster, more!
Efficiency vs Expediency.
Years ago I was developing a database, the demands placed upon the database were simplistic and basic. In essence it was a list, used to check the availability and validity of numbers. The idea was to wash a random bucket of numbers to see if they fit the criteria set by the customer. These numbers could have easily simply occupied a simplistic table format and been fine. The customer would have been happy and content yet, I found the basic minimal number of columns, data points inappropriate for the customers future needs.
Yes, I opted for Efficiency over Expediency. The reason was I have a scientific background and we never throw anything out, especially data. The data is only as good as your mindfulness and awareness while collecting it. Many a scientific study has suffered and been less important because basic and minor data was not collected during the experiment. In science I would never disregard any data which may be needed later. Anticipating future data needs and possible uses, is key to Efficiency.
So I was predisposed to put myself in the customers shoes and try and anticipate possible future data requirements. The upshot of this was that for very little extra effort, an extra few columns and a few extra lines of code; the customer could benefit from future data mining and analysis.
The effort required to develop the database was the same !
So why do we choose Expediency over actual Efficiency ?
The daily activity of trying to finish our work items steers us towards Rapid Solutions which seem Efficient; yet this very Expediency often costs many times more with rework, rebuilds and even the complete redevelopment when parameters shift as future needs become apparent.
The old saying “A stitch in time, saves nine” springs to mind. The mindfulness and mending of a small tear prevents the need for major reworking and effort.
So next time, ask yourself is this done for Expediency or actual Efficiency, and hopefully we can get a head of the curve and put our future efforts into better things than Rework.
The way I see this is that most of us try to do the best we can but a few remind me of the Ferreters of old who would let go any pregnant female rabbits so they would get work next year, to reduce the rabbit population.
Expediency has become our efficiency.