The Mortal Risk of Riding Shotgun in an Autonomous Vehicle
We live in strange times. And in interesting and amusing times.
A recent article I read, spoke about how most automotive manufacturers are misleading (or are confused themselves), when they claim to offer autonomous driving features in their vehicles.
Their mindset seems hugely flawed, if not shocking. Article here
Don Norman could have a field day ripping this mindset apart.
I have heard numerous stories since when I was a teen. Of people falling off to sleep while driving to or from work in the US. It never made sense to me. However, in the years since, I have seen and personally known fatigue while driving.
I worked in Pune in the manufacturing sector for a year and half. Work largely involved workday trips to relatively far off industrial sectors and every other weekend trips back home, I was mostly driving alone.
Then there were outstation trips, where I would leave early one morning, pick up one or two colleagues, and drive to another city, attend meetings at companies spread across a large industrial sector. The next few days would involve more meetings all day, before either driving back to Pune. Or driving to the next city for an encore. In all, over 33,000 km in under 18 months.
What auto manufacturers apparently offer with autonomous driving, is different versions of driving systems that take care of driving for you. It could be identifying and staying within lanes, measuring vehicular distance and safe braking, and using GPS to drive you to your destination.
You would assume you could completely disconnect and do your thing, as your car takes you places. However, auto manufacturers still expect you to be as alert as if you were driving, in case a sudden manual intervention is needed.
That expectation of theirs is absurd at best.
Humans are either engaged or not. Or as my Statistics professor would often quote the popular idiom, ‘she’s either pregnant or not, there is no somewhat pregnant’.
If you have someone drive a car, you can hope they are awake and alert. And yet there’s no guarantee, proof being the numerous accidents that occur due to distracted driving.
But the moment you are not driving, your brain switches off, or switches to something else. Unless you are a professional rally car navigator, or in the armed forces.
On most long distance drives, be it with friends, family or work colleagues, the person in the passenger seat eventually nods off, and I’m almost certain it is not because of the company.
So, expecting someone not to drive, but have the alertness and rapid response times of someone who is, is asking for a lot!
Of course, the biggest reason for this expectation is not so much the flaws in technology, but rather human behaviour again. Many autonomous vehicle accidents are due to unanticipated human errors – be it pedestrians or other human-driven vehicles.
So the effort should be on improving that unpredictability in erratic human driving, before rolling out technology that could potentially cause fatal harm to customers who come with a very different expectation of the technology than what the manufacturer offers them.
Look at the quality revolution and process improvement. They took industry by storm several decades ago. And their impact on our machines and automated processes is unquestionable. But are we humans more efficient today, or are we far more distracted and poor managers of our time than we were? Phones, entertainment and noise to blame.
Maybe manufacturers are explaining the gaps in tech to customers before the purchase. Maybe even spelling out the risks and precautions to them. But there’s only so much you can change human behaviour in short periods of time.
And finally, it was amusing how this potentially life-threatening flaw got reported. The article was titled, “..a UX risk!” Why dilute a crucial message? It’s a f@€k!^¢ risk to life! Far more than a risk to the customer experience. Can’t have a bad experience if you’re dead. Why not highlight that?
If you own, manage or work at a company, and are grappling with a complex challenge or are in need of innovation for growth, get in touch. More here.
And you might find my book, ‘Design the Future’ interesting. It demystifies the mindset of Design Thinking. Ebook’s on Amazon, and paperbacks at leading online bookstores including Amazon & Flipkart.
There has been the occasional debate between two schools of thought:
You need to ask the customer what he/she wants; and,
The customer doesn’t know what he/she wants until we show them (remember ol Steve Jobs?)
A bulk of the views I’ve come across so far lie on the side of ‘ask the customer’. However, it isn’t often that you find companies that build sound offerings and experiences that delight customers. And when questioned, a lot of them agree that no one really asked the customer. The huge divide between logical sounding answers on innovation, and contradicting real-life actions.
In fact, it all depends on how much improvement you want.
If you only need an incremental edge over competitors, your company’s efforts too will be similar – marginal targets, marginal budgets, marginal efforts. This might include a superficial but fancy-sounding customer survey, or just a few managers in the meeting room thinking of ways to tweak the existing product. In all, uninspiring intent, uninspiring effort, uninspiring results.
However, if what your business needs is a leap in growth, you need radically new offerings. That’s where customer inputs come in. From personal experience, I’ve come to realize that customers themselves often may not know or be able to hint at what might be a final solution going forward. But your interactions with your customers will be the only thing that will spark of that genius idea for an innovative new solution. Nothing else can trigger that. No research reports or internal ‘brainstorming’ can. But it is the customer who will help you get there. And the whole journey isn’t like a surgical missile strike or a silver bullet or an instant mix; but more like clay pottery.
You start with a meaningless mass of possibilities, spin them around, try things, make corrections, keep spinning, more tries, more corrections, till finally you have something wonderful shaping out. Something previously unthought of. Something incredible.
Look forward to your views. And if you liked this one, consider following/subscribing to my blog (top right of the page). You can also connect with me on LinkedIn and on Twitter.
Design Thinking is a relatively new concept in many countries including India. It is, however, already some decades old now. And having been practicing it for a few years now, I often get asked what it is about. And for examples of its applications.
For starters, design thinking is a mindset. One that uses empathy and a set of tools to innovate and pursue complex opportunities or solve complex problems. It aims at better understanding the needs of the end-user, or identifying the root cause of a problem, before beginning to innovate. And that always requires empathy, without which, we often settle for one of the first few logical seeming solutions that come to mind.
Like many management and quality initiatives of yester-years, design thinking too is currently receiving its share of a superficial hype. With time however, I believe the hype will pass; leaving people with a better understanding and more sincere appreciation for the power of design thinking.
Ordinarily, in a traditional problem-solving process, more constraints would almost lead to a dead-end or teams giving up. Such complex projects are where design thinking works best.
“Recognizing the need is the primary condition for design.” –Charles Eames
About a year ago, I had undertaken a design thinking exercise for the paediatric oncology department of one of Asia’s leading cancer hospitals. Sharing an overview of the same here, in case some of you are wondering what design thinking is all about. For me, design thinking is simply a humble means to achieve a goal.
Client: Paediatric Oncology Ward of one of Asia’s leading cancer hospitals
Objective: Improving the overall paediatric patient experience
I was at the hospital with two of my associates, to meet the expert medical oncologist regarding a project the associates and I were collaborating on. During interactions, the doctor expressed that patient feedback regarding the treatment has been positive. He and his colleagues, however, were always keen on knowing how they could further improve the patient experience. And given that the hospital offered free/heavily subsidized treatment to the poor, this was a humbling gesture. I offered to work on it.
The task involved interacting with patient families, doctors, administrative and support staff. It was necessary to get a good understanding of each stakeholder group and interactions between groups, in this bustling ecosystem.
Over the next 2 months, I spent several hours a day or entire days, speaking with paediatric patient families. I broad-based the sample to include new admissions, patients currently undergoing treatment, and those there for checkups 1-3 years after successful treatments. The wonderful administrative staff helped identify patients in different segments, as well as introduce me to some of them, to make for a more comfortable interaction.
Doctors had already provided considerable information from their perspective. I then spoke with administrative and support staff across the hospital. From admissions, to inquiry and even 3rd party social service representatives.
Initial Observations & Findings:
Based on information gleaned, and using Design Thinking and other tools*, here were some findings:
Patients/ patient families:
90% of patients came from outside the city, 80% from outside the state
Nearly all patient families spoke one or more of 6-8 different languages
Wait-times to meet a doctor, were significant – between 2 – 6 hours or more
A slight delay in patient arrival could mean making another trip the following day
At least 2 family members accompanied each patient. It meant putting their normal lives on hold. It meant treatments that lasted between a few months to over a year or more
Was well-intentioned, but mildly stressed and curt in responses to patient families
The staff dealt with hundreds of patients and family members on a regular basis
Some staff, on average, answered a request for direction to a particular building/room once every 2-4 minutes. Same was the case with some others about when their turn to meet a doctor would come, etc.
Some staff members were aware of their curt disposition. However, they admitted that in the region a bulk of the patients came from, they were accustomed to speaking in a curt manner. I too realized the same based on my observations and interactions with some of them. It was an amusing dilemma, the innate intention to be more polite, but an audience that might complicate your work if you yielded. A solution I proposed, aimed at solving that problem from the staff point of view
The funding enabled treatment to be completely or partially subsidized for the poor
Doctors had requested that solutions be cost-effective, if they were to be considered for implementing
Initial Verdict from Patients/ Patient families:
The overall feedback regarding the existing patient experience at the hospital was stellar. This included quality of process, staff, doctors, etc. However, I soon realized that this view was biased. Biased by gratitude for a hospital that covers all or a large part of their medical expenses.
I was back to the beginning. How do you improve patient experience when their treatment is paid for?
Back to trying to identify the opportunity:
I split the problem areas into three:
Long wait times for paediatric patients to see a doctor
Duplicate room number problem
Multiple inquiries to staff for directions to a room/ward
Increased stress levels of staff
How can an already good patient experience be made better?
Without burdening the hospital resources?
Again, using Design Thinking tools, I came up with initially unidentified problem areas. I also stumbled upon a promising solution for improving the patient experience.
Cutting to the chase:
My recommendations were as follows:
Split patients into morning and afternoon batches to make for easier sequencing and much shorter waits
Unique naming and numbering of rooms/wards (using words that cut across at least the 6-8 languages)
Colour coding of important rooms across buildings, with colour-coded stripes on the wall, to help patients ‘follow the coloured line’ (ideally with the colour names being identifiable across languages)
Colour coding would significantly bring down the number of times staff got asked for directions. (Patient families would be able to direct others. Colour/line/name-for-room would help overcome language barriers). It would reduce staff stress levels and making them more productive and happy
And most importantly, Customer Experience:
Proposed Tie-ups with companies (nearby to start with) for low-to-medium skill jobs that were individual-independent. One that anyone could turn up to do it. That would ensure work continuity while not limiting patient treatment schedules
Thought behind it: What was clear, was a free/almost-free treatment, and capable and polite doctors and staff. What design thinking helped me identify, is how family members put their lives on hold as their child underwent treatment. Earning some money while they were in the city, would help them buy small joys. It would help reduce the horrors of the disease and side-effects of the treatment on their child. That’s the only thing doctors and staff could not give
This would not burden hospital finances
I also proposed an alternate strategy option: where patients would pay a very nominal fee for services (from their salaries/stipends). This could bring new-found respect for the institution. The institution could also perhaps extend treatment to a few more patients with the same funds
Please note that coloured stripes and naming of rooms isn’t part of design thinking. What is, is identifying underlying issues such as staff stress and its causative factors. So is identifying possible areas to delight a customer in an otherwise perfect seeming environment.
“The goal of a designer is to listen, observe, understand, sympathize, empathize, synthesize, and glean insights that enable him or her to ‘make the invisible visible.’ –Hillman Curtis
Key learnings from this assignment:
Customers might not always articulate what they want
Be aware of tendencies where the ecosystem might bias a customer’s viewpoint
Often, solving or even addressing one problem area could have benefits across multiple areas
Anyone can learn and practice design thinking. It does, however, need a lot of Empathy and Involvement from you. It also requires an unwavering commitment towards customers, employees and innovation. And it is especially for those who are comfortable grappling with lots of ambiguity, and can stay true to the larger objective.
Got questions on design thinking, or how it might help your company innovate and grow? Comment below, or get in touch with me via LinkedIn or Twitter (links below).
“Only those who attempt the absurd will achieve the impossible.” –M.C. Escher
Look forward to your views. And if you liked this post, do follow/subscribe to my blog (top right of the page). You can also connect with me on LinkedIn and on Twitter.
* tools including (but not limited to) observation, interviewing techniques, design briefs, contra-logic, changing perspectives, forced connections, etc.
Several years back, I used to work in the ever so famous BPO (Business Process Outsourcing) Industry in one of India’s IT hotbeds, Bangalore. My job involved providing technical assistance to North American customers of our pretty impressive all-in-one printer range.
There was a time I wondered if the monotony could leave me permanently depressed. Or worse, brain-damaged. But right then, I received an email from my boss. He was forwarding an email from a customer I had assisted a few days before. The customer had needed print cartridges urgently. For some reason unknown to most of us, it took about 3-4 days after placing an order, for the cartridges to actually reach the customer. (And in case you wondered, ‘no, the cartridges weren’t shipped from India).
While this was a free delivery, there was a 1-day shipping for some charge. I was aware that in some special cases, I could request a senior colleague to waive off the charges on the 1-day fee, but it was not a luxury I’d like to take for granted. So I promised the customer a 3-4 day delivery period and that I would try to have the cartridges delivered earlier if possible.
Coming back to the email the customer had sent, it read something on the lines of – I would like to thank XYZ for the quick shipping of my print cartridges. He said it would take 3-4 days, but when it arrived the next day, I was thrilled. He has done what we in the customer service industry call ‘under-promising and over-delivering’, the surest way to win a customer… and a little more to that effect.
That was my first lesson in customer service; ok maybe not the first, but certainly the one with the most impact. It has been a while since that corporate ‘high’, and since those technical support days, but that feedback has stayed on with me. While I’m no ‘pro’ at customer service, I do understand its ever-increasing importance in any business, and I constantly try to figure ways of improving the customer’s experience.
And I have found many an Indian BPO employee, or for that matter, even your average sales or service staff at any retail outlet or business centre, bubbling with enthusiasm to cater to the customer’s every demand. And while this is a great thing for customers, there are 2 key ingredients missing in many cases. Those being Planning and Communicating. A simple equation of their effect on customer experience would look something like:
Customer Experience = Communicating (Planning+Commitment+Delivering on Commitment)
Most of us are great at committing, but tend to fall a little short when it is time to deliver on the commitment. And this causes unnecessary customer dissatisfaction.
In our endeavor to give the customer that little bit ‘extra’, we often miscalculate delivery or commitment deadlines. And this ends up causing the exact opposite of the effect we had planned for.
If we were to take into account all possible influencing factors (Planning) and build it into a commitment or delivery deadline, and perhaps even throw in a little buffer if we have a gut feel about possible delay, we would be giving the customer a more realistic picture. And of course, nothing beats plain old ‘Communication’. It is extremely important that we communicate with the customer. Even a call or message updating them the moment you see a deadline getting stretched, does wonders. You cannot imagine how much customers appreciate that phone call informing them of a delay. It beats them arriving at your doorstep on D-day only to be asked to come the following week.
To my customer. I may not have the answer, but I’ll find it. I may not have the time, but I’ll make it. -Unknown
Then of course, nothing beats delivering on a commitment or deadline.!
Look forward to your views. And if you liked this one, consider following/subscribing to my blog (top right of the page). You can also connect with me on LinkedIn and on Twitter.