Boost your digitalization: find the pains
As I walk around in numerous companies, one of the things that never ceases to amaze me is the number of people living out their lives in pretty poor jobs. Repetitive jobs, where they have lots of responsibility but little authority and where company processes, guidelines and rules dictate the way the work is to be done, with little to no freedom for the individual.
My typical response is something along the lines of “why the hell are you still in this job,” though expressed more politely. The typical answers I get are that things aren’t that bad, that there are good reasons why the job is structured as it is and that the individual has settled into the role. Of course, freedom is often defined as a cage where your wings don’t touch the boundaries, so perhaps I’m overly sensitive to being constrained and straight-jacketed into a boring, repetitive job.
We’ve all seen the cartoon by KC Green where the dog sits drinking coffee in a burning house claiming that “this is fine” and, while being lit on fire, claims that things will be OK. And we’ve all heard the story about the frog staying put in a pot with heating water until it dies. These being cautionary tales, the fact of the matter is that many people settle and simply accept reality as it is, no matter how poor the circumstances are.
My main concern is that so many of these jobs could be automated to the point that computers would take care of the majority of the drudgery and leave us humans to the more creative and unique tasks for which we’re primarily suited. Now, as a society, we’ve automated the last swaths of repeatable processes, so often the tasks not yet automated have some inherent difficulty that complicates automation. In my experience, there are at least three main drivers: inertia, regulation and forms of technical difficulty.
First, inertia is concerned with getting stuck in the past and continuing to do things a certain way because we’ve always done them that way. There’s a part of us that appreciates and recognizes the importance of traditions and easily abides by the rules dictated by these. This is difficult to change within the walls of companies, but even harder when these traditions cover an entire business ecosystem. A good example are shipping containers, which were invented as a concept before World War II, commercialized in the 1950s and still took decades to achieve broad adoption across the business ecosystem. This was despite the enormous reductions in transportation costs brought by these containers.
领英推荐
Second, regulation tends to freeze an industry in time based on what the best practice at the time of regulation happened to be. Although regulations are usually introduced with the best of intentions, in many cases they’re a good reminder of why the road to hell is paved with them. Many regulations demand human effort in a process, leading to high costs and, consequently, slow processes as companies seek to reduce costs by minimizing the human effort spent on following the regulations. Any innovations that would replace humans, reduce costs and accelerate the industry are blocked by regulation. An illustrative example is the banking industry where fintech startups are trying really hard to disrupt way too profitable incumbents only to be shot down by regulators when they start to become even a little successful.
The third reason blocking automation tends to be technical difficulty. Some part of the process requires human intellect as we don’t know how to automate it. This may include image recognition, interpreting video streams or processing natural language, to mention a few examples. The interesting thing is that AI has become incredibly good at these tasks and is more than likely to offer partial or even complete solutions.
The challenge is to be more like George Bernard Shaw’s unreasonable man and to continue to adjust the world to oneself. Rather than accepting the status quo, proactively search for pains. Once we find these, refuse to accept arguments claiming that this was tried before and failed. Instead, approach your work and the work in your organization with a Zen beginner’s mind, recognizing possibilities due to new technologies or other reasons and then acting on these. Don’t act as a jaded expert who has seen it all, but aim to see every day afresh. In the end, innovation is seeing what everybody has seen and thinking what nobody has thought.
Like what you read? Sign up for my newsletter at?[email protected] or follow me on janbosch.com/blog , LinkedIn (linkedin.com/in/janbosch ), Medium or Twitter (@JanBosch ).
Categories
Perception & Sensor Fusion @ Bosch | Automated Driving Alliance | PhD in Computer Vision & appl. Math
2 年Nice read, and if I may take it a bit farther: this is aligned with my observation that every job is slowly loosing its simple parts which is slowly splitting the available jobs into two categories: Creative-meaningful-well-paid and repetive-too-badly-paid-to-be-automized (yet). And the answer must comprise a revolution in education. Digital transformation eventually is a problem of a society transformation and not about replacing fax machines and giving everyone an iPad...
Next level industrial automation in The Netherlands and Italy
2 年Great way of thinking, fits nicely with my ‘I have to learn something new every day’ approach. When are you visiting Eindhoven or Milan again , Jan? We still have a catch up pending…
Software detective: software quality expert, experienced big data practitioner and performance specialist
2 年Hi Jan, nice piece. If you skip back to the 90s we were--as an industry--much better at this than we are now. The cause? The vast amounts of complexity that we heap on top of the business logic that the customer needs. The costs of building solid, secure, maintainable systems sky rocketed at the turn of the century. We were all full-stack developers in the 1990s. Business logic hasn't changed at all, but you wouldn't know it. What do you think about this?
Fractional CTO, Creator of AMMERSE, Author, Software Developer, prebonsai startup
2 年There are a number of reasons to not automate. I thought I would place some here for balance. Savings from automating a simple repetitive task could take years to be realised. I urge anyone to calculate the time it take to do with the time it will take to automate. A repetitive task has maintenance costs which typically involve your time, time is what you are trying to save. However, automating now relies on a tool, a set of tools, licenses, updates and general maintenance of the environment. EA is largely a role to repair, stabilise and change these sorts of things across an enterprise. There are also psychological benefits of repeatedly doing a task. Teaching others how to do it. The recovery time it provides your mind. The ability to think of other things while still remaining busy. (Think about problem solving while driving).
Cybersecurity for embedded products
2 年Great as always! But being one of those jaded experts, I would like to add a bit of nuance. I always encourage young colleagues to try things, even those that have failed in the past. But I also encourage them to understand why it failed in the past. Thus the part "... refuse to accept arguments claiming that this was tried before and failed" is well complemented with "but try to understand the reason it failed before and avoid making the same mistakes".