When I wrote ‘Design the Future’ about Design Thinking, it had a brief overview of the behavioural aspects of innovation – from an innovator’s and user’s perspective.
There was a mention of nudges (not sure I used the term though).
I have been of the (possibly obvious) view that, as companies get increasingly sneaky, especially when selling ill-health or stuff we don’t necessarily need, that despite how creative their marketing gets, customers too keep pace by becoming resistant to the nudges.
I also think the Ben Franklin Effect probably wears off, and that people aren’t exactly suckers to keep giving. Of course, it varies for people, their preferences, value trade-off, etc.
Unless business are sincerely trying to benefit or create a good habit in customers, I’ve personally never been a fan of exploitative nudges. Which is why, while some soft drink or fast food ads and initiatives are creative and impressive, you know it isn’t promoting something great in customers.
Two recent events seemed to be a sort of divine intervention to nudges and business practices that aren’t exactly in the best interest of customers.
First, Cristiano Ronaldo removing Coca-Cola bottles during a press conference at the Euros coinciding with a $4bn fall in the company’s share price. Nothing against the company in particular, but not a fan of global giants that proudly continue to promote ill-health.
The Second, email marketing. While useful to businesses including mine to spread the word, it also has become increasingly sneaky in that they closely track numerous user interactions. I recently got an email about an offer. Opened the email because the subject line was interesting, but immediately realized I didn’t need it. Instantly, the next mail appears, asking if there was something missing in the offer (previous mail). That was pushing it.
As per developments discussed at Worldwide Developers Conference (WWDC) that ended about a week ago, Apple will be putting more limitations on email marketing and in-app advertising. They’ll likely be preventing marketers from knowing when users have accessed their emails, among other features.
During a recent project with a company trying to create a positive habit in customers, the analytics team had a list of around 140 data points/actions on the app to track. I found some more to take the tally to 200. While the overarching service is beneficial to customers, I wasn’t overly proud of my contribution and faced the moral dilemma of whether we should track so much, or simply create a more effective user experience that might achieve the dual objective: one for the customer and one for the company.
Interesting how some businesses offer invasive tech to businesses, and other businesses offer defense against such tech in the form of new features on their products.
Late last year, the world (except probably Japan) would not have imagined that in a few months, they would not be able to see full faces in public. And yet, now most people are buying, and some people are making their own cool masks at home.
Over the last three months, I’ve on occasion thought about the design of masks. The N-95 mask (N in N-95 is for ‘Not resistant to oil’), has been recommended by some as being one of the better masks to defend against the Chinese virus.
In the world outside, we see everything from simple synthetic masks to the light blue surgical ones, fancy ones with respirators, and even handkerchiefs and dupattas being used as masks.
However, one problem with everyone wearing masks and makeshifts (kerchiefs, etc.), will be a possible deterioration of social fabric and societal behaviour. Because faces aren’t visible! It is possible that society as we know it could slowly tend to become a bit colder and indifferent. Because social connects aren’t quite the same when you can’t see a full face and a smile. On occasion, we don’t recognize known people because they are wearing a mask. And far more often than that, a ton of non-verbal communication, the grins and smiles, all get ‘masked’. The inability to see faces could affect the quality of communication and connect. This could affect us as individuals and as a world considerably over the coming months.
Let our masks not make us more cold and indifferent than we were.
The alternative: The only one I could think of, are Transparent masks.
Ashley Lawrence above, a college student studying education for the hearing impaired, designed this mask to help them lip read and follow expressions. Similarly, a few others around the world, a nurse included, have designed transparent masks in recent months. The current option of plastic for a mass market solution however, would be disastrous for the environment. In labs, there seem to be some natural alternatives like transparent wood. But at the moment, they might be far from ready for deployment.
Q: How can we design an affordable mask that (i) protects us from the virus, (ii) doesn’t harm the environment, and (iii) helps retain quality of social interactions and connect (by being transparent)?
This post about my 9-step version of the design thinking process has been long overdue. It is already explained in my book, ‘Design the Future’, but I also wanted to share it here for those interested.
The five-step Stanford design thinking process is arguably the most popular process out there. I have however, come across numerous different processes or versions. Ranging from the 15-step Darden process that I was taught, to oversimplifications and misleading three-step processes I have come across.
In my interactions with managers, business leaders and even students, I found that while many were familiar with the Stanford or some other design thinking process, they did not quite understand it well enough. For instance, ‘empathy’ came across to them as something that is ‘just done’. Similar to how many people assume hearing is the same as listening. And seeing empathy as a step in the process gave many the impression that like a switch, it had to be turned on and then off, as one moved to the next step.
So, in an effort to simplify the design thinking process so more people may use it, I created my own version of the design thinking process based on my understanding of design thinking and experiences practicing it. I took the Stanford model, and hopefully improved it.
You need to remember that any design thinking process is a broad guideline. It is not like a military obstacle course that one must complete in a defined sequence. You might find yourself looping through a few steps multiple times. Or in some cases, depending on what the information or insight presents, you might find yourself back at the beginning; starting again with renewed understanding of the challenge.
Sherlock Holmes, in the series ‘Elementary,’ once tells Watson, “The danger with rule books, Watson, is that they offer the illusion that leading a moral life is a simple undertaking, that the world exists in black and white. Welcome to the grays.”
At least when it comes to areas such as creativity and drawing inspiration, remember there can never be stringent rules or guidelines.
My 9-step version of the design thinking process:
My 9 Step version of the Design Thinking Process
Of the nine steps in the process, the first three are more underlying criteria than steps. Criteria that are critical to improving the chances of success on a project. Those three criteria are Humility, Empathy, and Intention. While these might seem obvious to the point of sounding stupid, they are often the most ignored aspects to a design-led process. More on that as we understand each step better.
After that come the more common steps of most design thinking processes. They are: Define – Empathize with Intent – Redefine – Ideate – Prototype – Test
Let’s look at the nine steps more closely:
Humility – The quality of having a modest or low view of one’s importance. Its relevance springs from the simple signal versus noise perspective. Our objectives as design thinkers is to maximize our understanding of user experiences and needs. Of those we want to innovate for, or whose problems or challenges we want to solve. That is the signal that is of utmost importance to us for innovating for them. Our views, opinions, and biases are the noise.
The moment you can bring yourself down to the level of a beginner or a learner, you put yourself in the backseat, and that’s when the end user or final beneficiary of your innovation will come into the limelight of your focus. Remember to start with humility.
Empathy – The ability to understand and share the feelings of another. Putting yourself in a live user-setting and observing and/ or interacting with users to get a better sense of what a problem or future opportunity might mean to them, how they deal with it, and so on. In conjunction with humility, it offers a good environment to capture user information.
Unlike what some methods might state, empathy (and humility as well as the next step, intention) are not steps in themselves. They should not be traits that you turn on and off depending on which stage of the design thinking process you are. It is also why, along with the intent, I have placed them at the base of the six-step process, to signify how the three traits always need to be ‘ON.’
Without being in a constant state of empathy, no real innovation is possible. And that will be the difference between a real design thinker or team creating an exceptional change, and people simply practicing it as a flavour of the times.
Intention – An intention is the larger thought and nudge to action for a change, that brings you to employ the design thinking process. You might wonder what the difference is, between humility, empathy, and intent.
As a business leader, humility will always help you spot customer or employee or other stakeholder needs and concerns. Empathy will let you better understand those needs and concerns. To get to the root causes of it. You might still choose not to do anything about it, because you don’t have the intention to. Contrarily, if you have the intention, but lack humility and empathy, it would mean that your objective or goal is not the right one.
Equipped with humility and empathy, but in the absence of any intent, a business leader will always spot improvement areas in his or her business. All they need then is to choose their intention – i.e., determine the direction of their effort, and get working on it.
Define – Here, we put the problem statement or opportunity statement in words. It is a starting point of sorts, to the primary design thinking process. Before interacting with user groups, this is a step where we broadly express what we think the problem or opportunity area might be. It could be how a client has described a problem, or, if we are helping a friend or industry colleague, it could be their description of the issue.
One key thing to remember with defining a problem or opportunity is to make it sound positive, irrespective of how grave or pointless the situation might seem. A lot of companies are prone to defining/ framing what hurts first. Their definition ends up being a problem statement which sounds grim. The disadvantage of doing this is that when you invite people to think of ideas, even as part of a brainstorming exercise, a grim-sounding problem statement stifles the thinking, and will hugely limit the number and quality of views that you receive.
On the contrary, if you turn your problem statement into an opportunity statement, people ideating will be in a positive mindset, and be more attuned to think of creative ideas. Try to notice the difference of mindsets the following two statements evoke. Read them more than once if necessary:
A Problem Statement: “How can we drastically reduce our after-sales service related expenses?”
An Opportunity Statement: “How can we redefine our service arm to be more relevant to customer needs, while not proving expensive for us?”
As Abraham Maslow once said, “if all you have is a hammer, everything looks like a nail.” Defining a challenge too negatively and very precisely might give you solutions that just create more problems of their own.
Empathize with intent – This is the fun phase, where you spend time observing actual users in their natural surroundings. See how they consume a product or service. How they interact. And you must do this in the subtlest way possible, even when you are interviewing or interacting with them. Especially if the process is delicate or embarrassing for the end-user, or if the user is introverted or are in some way intimidated by you and your team’s presence.
One important thing to remember in this phase is to be subjective with the empathy, but objective with what they share with you. If you have a subjective mindset when trying to find learnings, you might tend to get lost in a problem. And depending on the type of assignment, it might leave you either in disbelief, or maybe even depressed or an emotional wreck, depending on the kind of problem you are working to solve, as users expose you to severe difficulties or bitter experiences.
Instead, empathize with users as they walk you through their journey, experiences, feelings, and thoughts. But look at it from behind a glass wall when taking notes or drawing inspiration or conclusions from it. That way, your focus is not diverted by problems but instead stays focused on noting down those problems and possible thoughts, reasons, etc., that might spring to mind. The focus will help you then work towards getting rid of the problem, as opposed to being overwhelmed by it.
Redefine – After gathering user insights, we revisit our original definition with what we have learned. After enough information has been collected in the earlier stage, the team debriefs. The information is shared amongst team members without contaminating it with their inferences. That way, each member gets a clear sense of how things presently are.
Often, when tasked with solving a problem for someone, even when we have little or no information to go with, we are eager to get started with identifying potential solutions right-away. You might have seen this tendency in yourself and others (I tend to, from time to time), where someone mentions a problem, and without stopping to understand more, you start rattling possible causes or solutions.
That happens when we go with our definition of someone else’s problem. Which is why, after an initial definition, once we get a better understanding of it from actual people facing the problem (in the ’empathize with intent’ stage), we redefine the challenge more accurately, based on what we have learnt.
Ideate – This is the stage where designers would take the information they have gathered and use it as inputs that they put through a choice of design thinking tools. Tools including the brainstorming or versions of it, to contra-logic, worst-idea, brain-writing, trigger questions, changing perspectives, etc., and then use anchors, forced combinations and connections to come up with numerous ideas. The more ideas, the better, and the crazier the ideas; even better!
Prototype – Prototyping an innovative solution is akin to shaping a solution using two pairs of hands – your design team’s, and your users’. In the previous stage, you would have identified some potential ideas and possible directions regarding a solution. This is where you need end users to help you figure out what works for them, and what does not.
The objective of this stage is to be able to move rapidly towards a final solution, with minimum investment (as far as possible) on experiments towards refining potential solutions. The moment each prototype becomes too expensive and complicated, there is a tendency to either convince yourself and your team that it is a great solution (because of the effort that went into it. It is a cognitive bias called the IKEA effect).
Another possibility is that if you encounter a roadblock at this stage, your team or the top management might get easily demotivated and consider it a colossal failure, solely because your team spent a fortune building a prototype that user groups did not like or approve of.
Instead, make the most basic and low-cost but effective prototypes possible. Use anything from sheets of paper for story-boarding, to card paper or cardboard, Styrofoam and other craft supplies to work toward a final solution. Your objective with each prototype, is to test no more than one factor or variable you need clarity on. Test too many criteria, and the learning becomes unclear.
At workshops I conduct, I sometimes take my old letterheads for participants to use for discussions, sketching, or to make things out of.
It is only when everyone finds using anything lying around them as potential material for prototypes, is when prototyping will become far more prevalent. The same goes for ideating. If the materials you use are too fancy, you or your team might use it as an excuse to delay prototyping, or even ideating.
Which is also why, while a lot of design thinking workshops use post-its and put up pictures of it, few participants continue to use post-its to implement some of the tools they learnt. Because buying post-its is expensive and sometimes inconvenient. If you can’t make do with stuff already at your desk or around, the action gets delayed till you buy those supplies. Take this from someone who uses toothpaste or soap to write on the bathroom wall so that a potential idea does not disappear with the flowing water.
Test – Once you’ve completed the prototyping phase, you move on to testing. The significant difference between the two is that while prototyping was far greyer and also, the prototypes were far less expensive but required a slight stretch of the imagination by the user, the testing phase is that much more advanced, as it is that very close to the final product or service.
And unlike checking one feature at a time in the prototyping phase, here you are testing the product or service in its entirety, towards ironing out any features or poor service extensions that exist, by letting your users directly interact with the solution.
The first rule to keep in mind in the testing phase too is that your product or service is not final or finalized yet! There would still be some assumptions that your team would need to test. For instance, it is one thing to prototype with sketches or storyboards or even pretend mobile interfaces. Quite another to have end users interact with your store layout or theme park or mobile application.
Which is why we have the testing phase, where your team would help build almost-final solutions to test them in the hands of a closed group of stakeholders. It is great to have a select list of people who will evaluate your creation. That increases the focus and feedback capturing. And what you will be testing, are any assumptions that were earlier not tested, or that sprung up along the way with the increase in clarity.
It isn’t possible to overstate the amount of valuable, even critical insights that can be gained in the testing phase.
Testing is followed by eventually launching the product, service or change – once all assumptions and user hesitations have been factored in.
After you’ve gained more realistic insights from real users who interacted with your prototypes and brought you very close to a final solution that you by way of prototypes and then running exercises with them in the testing phase, you are finally onto an almost ready and well-refined answer.
Ideally, even after launch, the journey should be looked at like it is the making of a TV series. You’ve launched season 1 or 2, and it is doing well. But you need to check-in now and then as to how viewers are reacting and engaging with it. The bigger question in your mind always is, is there enough traction to demand a season 3, and if yes, would there be any significant changes needed (replacing actors, etc.) or is the show no longer relevant to its audiences. In which case, you then need to figure out what next. That way you are not going in blind with season 3, to later find out it lost its audience midway through the previous season itself.
One should remember that there is no perfect product, service, experience or solution to user needs or problems. And there are no runaway results promised by design thinking, the way some firms guarantee the ability to create viral videos. But yes, you always have a far greater chance of arriving at a product or service that people want or need by using design thinking, than by merely guessing or troubleshooting your way through.
Common problems startups face – A Design thinking outlook
I have been directly associated with startups since 2006. That’s when I started my career as a member of a venture capital investment team. All the way to my recent years consulting them and young businesses, I have heard a multitude of problems that startups face. Problems that can largely be categorized under two main causes.
The first one of course, being investments. The second, being the lack of traction, or growth in business.
With regard the problem of funds, you could further break it up in to funds you must have, and funds that are good to have.
Literally all of us are, more often than not, influenced by awe-inspiring startup stories. About those startups in the world that seem to be on a blistering growth path. With people and funds literally queuing up for an opportunity to invest in them.
Watched the movie ‘The Incredible Hulk’? The Hulk and the Abomination in that are like those few startups that receive disproportionately high amounts of funding.
Everyone is not like them. And even in their case, of the two, only Hulk was relatively stable with the superpower. The Abomination, as the name goes, became that way because of his lust for super-strength to beat the Hulk.
Similarly, even if all startups could be funded like that, or like Uber and PayTM and Zomato and others have been, there is no guarantee they will succeed. Because making a business stable takes managing a lot more variables than merely the investment one.
Which brings us back to the other alternative – funds you must have.
This is the basic minimum investment that you would need to get your startup rolling. It isn’t too tough to calculate it. Just make sure you have sufficient buffer. And keep checking those levels so you don’t realize it’s bad only once you’re broke. The advantage of this mindset, is that even if external investments never come, your startup will be built on a solid foundation and a sound business model. That, as opposed to one of hyper-experimenting, as is sometimes the case with super-funded startups. Take the case of TinyOwl hiring and almost immediately firing hundreds of enthusiastic freshers back in the day. Or Ola paying USD 31.7 million for FoodPanda a year and a half ago, only to fire a lot of the staff and suspend its operations recently.
While such news pieces might be good to hear, they are often not something to be proud of.
A bootstrapped startup will have its share of proud moments too. And they will be far more grounded and not the kind that could be easily taken away, unlike the case with some over-funded ventures.
Now let’s look at the other main problem area of startups. The lack of traction or growth.
In my book, Design the Future, I mention what is to me, a wonderful example from both an investment angle and a strategic one that depended solely on the understanding of customer needs.
One portfolio company whose growth my boss and I used to oversee, was in the car rental space. Around 2009, it was on its way to be the largest player in India, right on the heels of Meru. Meru was then leading the pack in terms of size of fleet.
However, what was interesting, was that Meru’s business had been built largely on debt. Ours had been built on equity. Which meant we were profitable sooner, and could scale much faster. Meru had just turned profitable around 2009-10, if I remember correctly.
And back then, our portfolio company was already onto the model of partnered fleet. That is what Uber is all about now. Our company was collaborating with small tourist vehicle operators to add their fleet and drivers to their own, in a revenue-sharing model.
Now think about this. A company founded in 2006, which was already employing a model that we in recent times popularly know of as Uber, what as of today, has a market capitalization of USD 69 Billion! And Uber was founded only in March of 2009 (conceptualized in 2008).
So what prevented our portfolio company from being the one valued at USD 69 billion?
In hindsight, a lack of better understanding of the stakeholders in the ecosystem, is my guess.
Our portfolio company and other players back then were perhaps used to a certain customer price level and profitability that they enjoyed in a tried-and-tested pan-India market.
However, perhaps we failed to see that we could considerably reduce the margins and incentivize the partner ecosystem, in an effort to gain massive scale.
And with customers, it is only in very select areas that if we offer something at a lower price, they won’t take it. But certainly not with transport.
So, Uber carpeted several countries with the initial attractive pricing, and more than encouraging partner revenue-sharing and incentives.
And companies like ours, that didn’t think huge enough, shrunk into insignificance in that particular space at least, which they had ruled for some years till then.
Putting investments and a better understanding of the stakeholder ecosystem together, it is not necessary that every business and every idea has to be Uber-sized!
You can as well remain small, exclusive and yet thriving in a small or select few areas or geographies, if that is your business vision. Or, as is the case with Uber, you can be the most recognized brand in ground transport.
What is most important, is to first decide where on that spectrum you want to be. Then you need to find out (not in meeting rooms, but by spending time with stakeholders), what their likes and dislikes are. What drives them, what their profit expectations are? And how flexible are they on pricing; or, is there a better way you can offer them what you do? Something that might completely be poles apart from how you offer it right now.
Scenarios in the startup ecosystem are limitless. And so are the possibilities.
Originally written for NODD app and posted here: link
***
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.
One of the fundamental ingredients of an impactful innovation or successful design thinking exercise, is empathy. The ability to understand and share the feelings of another.
Often, in our enthusiasm to create something someone (a customer segment, employees, or even society), or to solve a problem for them, we tend to knowingly or unknowingly speed up the process. We skip the part of trying to understand the problem or the cause of it. Or the unexpressed need. We create, and we expect (or at least hope for) delight from those receiving our innovations or solutions.
This simple image I came across online gives great context to our urgency to solve problems or innovate. An infant is too young to realize or even see clearly, the flaw in this. If a simple flaw like this could be missed by most of us, what else might we be missing? How little effort are we taking to look at business innovation or problem-solving from the right ‘context’?
Small efforts in understanding customer needs, go a long way. Apart from feeling appreciated and important, customers help us get closer to innovative solutions they are willing to pay for. The least we can do is look at their needs and problems from their perspective.
*
If you run or manage a business, and innovation, strategy, problem-solving, customer experience or ideation are areas of interest, there are a few ways I can help. More about it here.
My book, ‘Design the Future’ is available as an Ebook on Amazon & Kobo, and as paperbacks across leading online bookstores including Amazon &Flipkart. Look forward to your review on Amazon once you’ve read it.
***
Look forward to your views. For similar topics that encourage reflection and discussion, follow or subscribe (top right of the page). You can also connect with me onLinkedIn and onTwitter.
Ava and Dr. Jimmy Patell, dear friends of mine, were extremely kind to gift me a poem that they wrote about my book on design thinking, Design the Future.
The poem itself is more priceless to me than the book. Really humbling.
Here it is.
Design the Future, what does it portend What does it say, what message does it send Does it help Managers in their work place Or a simple layman in his home space
How can the processes that evolve A family’s day to day problems solve Or is it just solely business tools Being espoused in some management schools
Well to clear the mystery of it all Shrutin Shetty has taken a call And made things clear by writing a book That may well become the subject’s handbook
Friends, it may help giving the book a read It may assist you in your hour of need Solve the problem before others do And get credit that is due to you.
– Ava and Jimmy
If you haven’t picked up my book yet, you can use the code JIMAVA herefor a 25% off on the paperback. Paperbacks are also available across leading online bookstores worldwide, and ebooks on Amazon and Kobo. If you do buy the book, would appreciate a review on Amazon once you’ve read it.
***
Look forward to your views. And if you liked this post, do follow or subscribe to my blog (top right of the page) for similar topics that encourage reflection and discussion. You can also connect with me on LinkedIn and on Twitter.
Here’s a thought regarding upbringing. Views welcome; and especially so if you have kids and your parents either stay with you, or you visit each other often.
You know how curious for information kids are. And parents often ask them to say or sing something they have learnt, in front of family or in the presence of guests? As a parent, try to think of the reason why you do this.
“What is your intent behind requesting your kid to say or sing something in front of the family and/or guests?”
Is it more for amusement (and possibly family bonding) or to show-off your child’ progress, or something else?
And in case it is for ‘something else’, what is that something?
Similarly, ask your parents the same questions. Especially if your parents aren’t all that literate (or if you have grandparents, ask them as well).
What’s the thought/ point behind this?
Back in the day, grandparents or parents didn’t always have access to the best of education. In such instances, they would often request their kid to say something they had learnt. Especially in the presence of visiting family or friends. Is it possible that was less for amusement, and more as a matter of pride or accomplishment?
Nowadays parents have obviously received a good education (in most cases). They usually know know more than their kid does (be it something as basic as English, etc.). In such cases, is requesting your kid to say something in the presence of others more for amusement, and less out of pride or humility that the elders might have felt?
How does this matter?
Is it possible that in the past, those kids would sense the the humility and pride, and in present times, would sense the amusement? And would the reactions of kids be different given what they sense? And does that influence their actions? For instance, would that feeling of humility or pride they saw in their elders push them to strive harder? And in more recent times, do kids see themselves as being entertainment for elders, and therefore sometimes tend to strive to please or entertain instead?
While earlier generations were overly concerned about “what society will think” regarding different aspects of their professional and personal lives, are the current and younger generations very different? Aren’t the younger generations also overly dependent on social acknowledgement, attention and approval, even though it might be for contexts different from those of earlier generations?
*
My book on design thinking titled ‘Design the Future‘ is out. If innovation, design thinking, problem-solving, human behaviour or ideation are areas of interest, am sure you will enjoy this book.
You can order your paperback copy via Amazon, Flipkart & Infibeam.
Would be great if you could leave a review on Amazon once you’ve read the book.
***
Look forward to your views. And if you liked this post, do follow or subscribe to my blog (top right of the page) for similar topics that encourage reflection and discussion. You can also connect with me on LinkedIn and on Twitter.
Hi! As some of you might already know, my book on design thinking, titled ‘Design the Future’ is out!
Despite design thinking being several decades old, we are seeing increasing relevance in its application in our fast-paced lives today. I’ve read incredible books on the subject in the years I’ve been practicing it. However, I still find confusion & uncertainty among some of those who have been practicing it, as well as those merely trying to learn it.
‘Design the Future’ is an effort to reduce grey areas by building a stronger foundation. It covers the fundamentals, examples from around the world, and my observations, notes and learning of design thinking & human behavior.
If innovation, design thinking, problem-solving, human behavior or ideation are areas of interest, I’m sure you will enjoy reading this book.
If you do read the book, I’d be grateful if you can leave me a review on Amazon.
You can reach me at ‘shrutin [at] ateamstrategy [dot] in’ with your views, or if you’d like me to answer any questions or doubts you might have.
Hope you enjoy reading the book & find it useful in supplementing your design thinking skills.
***
Look forward to your views. And if you liked this post, do follow or subscribe to my blog (top right of the page) for similar topics that encourage reflection and discussion. You can also connect with me on LinkedIn and on Twitter.
I recently conducted an interactive session on Design Thinking at a leading investment bank. It might be easy to assume that applications of design thinking at an investment bank are limited. It is quite the opposite though. And the applicable scope of design thinking just seems to grow bigger with each passing day. The team was also kind enough to present me with a thoughtful gift at the end of the session. A Gucci tie.
Now, once you’re in the design thinking fold, you are always processing and assessing products and services. As you might have noticed, the tip of the tie is a little crumpled. If I was the manufacturer of ties that retailed at anything between $60-240 or more, I would have been concerned about the experience a customer goes through of opening the packaging and seeing the product as well.
The tie came in a tall box which was in a slightly taller paper bag, fastened with an embossed ribbon. When you hold the bag upright however, the tie drops inside thanks to that often-neglected phenomena called gravity. This causes creases at the tip of the tie. Now while many might tell you it is ok to iron a tie, it is not something I’d recommended you did often. And certainly not something you would want to do with a brand new tie.
While there might be several ways to package it in a way that leaves an impression with the customer, it isn’t something I’ll spend time thinking of right now. The easy way for Gucci to solve this problem, would be by merely placing a card paper insert which is fixed to the sides of the box. It would hold the tie in place at the top, like a clothes hanger. That way, the tip of the tie would never touch the bottom of the box when held upright.
Little things go a long way in improving how customers interact with your product. And how they remember it.
***
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.
A close friend recently shared this article titled ‘Why Design Thinking will fail’, written in 2013 by Jeffrey Tjendra. Jeffrey is a designer entrepreneur and strategist. Among some of us friends, there was were points of disagreement on the article. Jeffrey does seem to have a good understanding of design thinking. This post, however, is an effort towards taking a closer look at each point mentioned there. And to see if it makes sense or not. All of this, with my limited but growing knowledge of design thinking.
Before I begin, here’s a quote by Mara Wilson. While her quote describes storytelling, I believe it offers a more far reaching explanation. With products and services too, for instance. She said, “The more specific you get, the more universal it is. (It’s a special alchemy of storytelling).” – Mara Wilson
Back to the article, here goes:
Misperception of Meaning – I’ll agree, it can be misleading to some. I use either ‘human-centered’ or ‘user-centered’ design thinking in an attempt to bring a little more clarity, especially when interacting with people I believe might misinterpret the meaning.
Loss of Meaning – Can’t do much about that. A lot of effective methodologies often see phases of hype and a lot of randomness being packaged and sold in its name. But as the dust settles, only the real stuff and an increased respect remains.
Misunderstanding and Not Accepting Creative Elements – True. However, any company or more specifically, a management that has ever worked on any form of creativity or innovation, knows how boring, full of trials and iterations, full of mess and uncertainty it can be. Look at your kid’s school projects for instance. If it isn’t too simple, it is bound to take a lot of ‘random’, before it starts to make sense. Anyone who doesn’t understand that, will surely not use design thinking. And that’s alright.
Lack of Business Elements – Coming from a management and finance background, with experience in strategy and marketing, I tend to build those critical business aspects to a design thinking project. And that is especially why the design thinking team needs to have a wide-enough assortment of skillsets. Using only UI/UX people or ethnographers or psychologists is not going to do the trick.
Language and Perspective Barriers – There have been worse instances of communication gaps. For instance, if you have heard the almost unbelievable and heroic story of the Gimli Glider. An obvious technical specification got so conveniently ignored, that it put at risk, 69 occupants aboard a Boeing 767. Read the fascinating story! So, it just boils down to the intention and seriousness of the parties involved. Nothing is foolproof or idiot-proof. But a lot of change and innovation can be brought about with the right intentions. And no amount of left-brain learning and practice can fix unpredictable situations either. Because a lot of left-brain thinkers often learn a process from end to end. Any deviation could potentially leave them baffled. Creative thinking, on the other hand, helps one focus on the fundamentals. On understanding the building blocks more and more. And then, irrespective of situations or deviations to them, there is often more clarity as the building blocks can be used to better understand complexity. And it’s often easier to communicate fundamental building blocks across language barriers, as opposed to communicating complexity to begin with.
Missing Future – Even design thinking veterans like IDEO have made mistakes, overestimating future demand of tech products. A strong problem or opportunity statement (which is open to being updated when you learn more about the end-user) helps reduce the risk. As does an unbiased and strong mechanism to interact with, and observe and understand needs, behaviours and desires of end-users, and capture that information towards building a solution.
Wrong Implementation of Process – Which is why a lot of products and ingredients come with ‘Instructions to Use’. If an ingredient needs to be mixed and cooked, simply sprinkling it will not help.
Poor Direction Scoping – This is where an intention and objective to start with, matters. There are billions of people, billions of problems and billions more opportunities. Which one or ones do you want to target. That’s what you pursue. Ignore everything else.
Co-creation at the End of Process – all I’ll say is, phone sex doesn’t help create babies.
Misconception of Approach to Creativity – This is true. Some people would tend to follow the design thinking process like it is a treasure map, when in fact, it is navigating your way through hostile jungle. Your senses need to be on alert all the time. Any input can change a lot of initial assumptions. That lions don’t climb trees. Or that chimps tend to rely on third party to help resolve disputes.
Wishful Thinking for Culture of Innovation – Completely agree here. Which is why, a startup whose founders have the right values and give importance to innovation, can build it better into their culture, as opposed to trying to inject it into a global behemoth that has a century of history.
The End Process is not the End – true – design teams, just like any other specialty teams, need to walk the talk. Leaving projects with solution advice that is abstract to clients, won’t serve anyone’s purpose. A lot of large consulting firms were infamous for doing this back in the day. Leaving clients many million dollars poorer, and with a big “report” that the client was clueless what to do with.
Risk of Stagnancy – As Zig Ziglar said, “People often say that motivation doesn’t last. Well, neither does bathing – that’s why we recommend it daily.”
Thoughts?
***
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.
My book on design thinking titled ‘Design the Future‘ is out. If innovation, design thinking, problem-solving, human behaviour or ideation are areas of interest, am sure you will enjoy this book.
