He’s an amazing guy; his ideas on “minimally invasive education” and “child-driven education” are fabulous; what’s more important is that he’s put his ideas into practice and shared the results with us. I had the privilege of watching him at TED Global at Oxford in 2010 (thank you Chris, thank you Bruno), and one phrase he used has stayed forever in my memory.
Teachers who can be replaced by computers should be replaced by computers
I may be paraphrasing him, but that’s the gist of what he said. That sentence, along with John Seely Brown’s deceptively simple question (How long does a five-year-old take to become a six-year-old? One year), have influenced quite a lot of my recent thinking on education. But that’s not what this post is about. Or maybe it is. Sometimes I get the feeling the answer to everything is learn, learn, learn. Learning is living. The willingness to learn fuels life.
When I first came across the concept of outsourcing I was mystified. The received wisdom was that we should only outsource operations that had well-defined and mature processes, standardised and repeatable. And a part of me was asking “Why? Surely those are the very processes that are prime candidates for automation? Why would we want to apply the sledgehammer power of human brains to such mundane things?”. I remained mystified as I watched the BPO market mushroom. Paraphrasing Sugata Mitra, I felt that processes that can be replaced by computers should be replaced by computers. And I could not understand why this didn’t happen.
Those were the days, eh? Times when we had regular, standardised, repeatable processes. Times when we knew when, where and how locked-in customers would consume products and services in a predictable, stable manner. Times when listening to the customer was easy because there was nothing they could say and nowhere they could say it. And even if they did say something, it was easy not to listen.
Today it’s a whole different ball game. And for some time now I’ve been stressing the importance of “designing for loss of control” as companies spend more and more time trying to fit square pegs into round holes, as engagement with the customer migrates and mutates away from standardisable processes; companies nowadays seem to spend more time “handling exceptions” than executing the unexceptional.
Which brings me to the point of this post.
Systems can ask for permission. Only humans can ask for forgiveness.
You can come up with rules for how people should do things, and come up with tables of authorities and permissions and what-have-you. Much of the time, all you’ve done is lay out a rulebase that can be automated. And perhaps should be automated. But maybe it’s too late for that. Today, we’re seeing a shift from process to pattern, a shift from rule to principle, a shift from hierarchical to networked, a shift from centralised to edge-based. No more repeatable processes. Values-based activity. With domain experts dotted throughout the organisation, engaging with customers who expect the people they’re dealing with to be empowered to deal.
Customers know all this.
Customers know that exception handling is now the norm. And they expect everyone to know this.
People in customer service will have to learn to improvise. Be creative. We’ve all heard tales about the helpdesk from hell of the type “My computer freezes every time I touch any key” “Well don’t touch any key then!”. That’s not going to work any more.
An aside. I was looking for recipes for jhal muri, street food from Calcutta. Extra-spicy puffed rice with dollops of mustard oil and lashings of fresh green chillies. And I found this site, which I loved. In fact the stimulus for writing this post came from reading the recipe. The author makes the point that there is no such thing as a recipe for the dish; just a set of ingredients that can be varied at will to suit tastes.
And I thought to myself, that’s how customer service will look in time to come. A set of “ingredients”, the things a company can do or make or provide, loosely coupled by the values and principles the company adheres to. A “cook” who puts those ingredients together, on order, to suit what the customer wants.
Creativity in customer service? Perish the thought.
But I’m being serious. It is possible that unless customer service gets creative, it will be the company that perishes, not the thought.
Which brings me to my final point. For this creativity to exist, we should look to the masters of improvisation, in music, drama, art. Before they could improvise, they had to have real in-depth knowledge of the domain, a feel for the space, an intuitive sense of what they do. [Maybe there's a reason for knowledge workers to be called knowledge workers? Hmmm.] Before they could improvise, they had to understand the technical capabilities and constraints of the instruments they played, the tools they used. Intuition, coupled with technical skill, underpinned by experience.
Or at least it used to be hard.
Now, with enterprise social networks, it’s become a whole lot easier. If they’re designed well, you’re able to able to propagate the principles and values consistently, develop both the tacit as well as the explicit knowledge needed, share and enhance experience, make it easier for people to build their intuition and their skillbase, grow their confidence via active feedback loops. All done in an environment where you can record and look back in order to learn and improve. [Of course this can be used to apportion blame as well, but that's not a sustainable strategy]. That’s why I joined Salesforce just over a year ago, I was fascinated by what could be done with Chatter, how enterprises would be able to transform themselves.
Look around you. See if the culture of work you’re in is about permission or forgiveness. It’s a good yardstick for figuring out whether you’ve really grasped this new world we’re all entering.