Wednesday, April 29, 2009

Failures, Hardships, and Success

It's a sad fact that while we are ready to speak about our points of success, most of us do not acknowledge nor really mention the failures and hardships that were endured to take us from a certain point in our lives to another. These points in our lives not only define, but evolve our strength of character by learning fortitude, patience, perseverance, realize our determination, and ultimately reinforce our passion which compels us to move forward and manifest our goals.

Then why are we so afraid to speak about them when mentioning these doesn't make us any less. In fact, on the contrary, haven't they taught us more than first-time success ever could? Relating these experiences offers valuable kernels of insight to another who may be enduring similar trials and tribulations along their own journey. So cheers to the failures and hardships that push us to become more - May we fail often enough to remain humble, grow wiser, and may these always be remembered fondly! :) And thank you to Edison for not only giving us the electric light bulb, but for teaching us that even failing holds its own seeds of success!

"Many of the great achievements of the world were accomplished by tired and discouraged men who kept on working"

Genius? Nothing! Sticking to it is the genius! ... I've failed my way to success."
--Thomas Edison


On that note, here are some articles regarding mistakes, hardships, and failures...along with the explanation as to why they are wonderful. Enjoy!

I Hope You Fail: Why Failure is Good


The Greatest Mistake of All Time

Fail Your Way To Success! Why Failure Is So Wonderful!

How Have You Failed Your Way to Success Lately?


Why Failure is Good for You


Reasons for Why Failure is Good

Saturday, April 25, 2009

Gates vs. Jobs



Continuing on that note - also humorous (Elvis reference was icing on the cake)




Wednesday, April 22, 2009

R.I.P. Innovation?


I came across a very interesting short BCG article (thanks to a friend) which mentioned some very interesting statistics about satisfaction regarding the end results of R&D led products - but does that mean that these "innovative" products sell better or make the people involved (executives, share holders, etc) happier? Does it significantly increase margins along with sales?

Click here to read article (and as always, I'll include some of it on here)

---- BEGIN ARTICLE POST----
BCG-Businessweek Innovation Practice

For most companies, innovation is the key to driving growth, shareholder value, and competitive advantage in today's global economy. But even at the best companies, up to a third of all innovation initiatives are draining valuable resources.

According to the most recent BCG-BusinessWeek innovation survey only 46 percent of senior management are satisfied with their return on innovation spending while 63 percent of chief financial officers are still unhappy with their innovation results. Innovation remains a top priority for 66 percent of respondents, and 67 percent are planning to increase their investment in innovation.

The problem these companies face isn't a lack of ideas—most of them have more than enough. It's that companies don't have a disciplined process for turning those ideas into cash. An effective innovation-to-cash process (ITC) is the foundation of successful innovation, which we define as profitable innovation.

---- END ARTICLE POST----

I can't deny that the numbers reported were a little surprising to me but then again, not really so much as I would expect. Infact, it actually reminded me of Nussbaum's "Innovation is Dead" post back from the last day of 2008 - something which I did partially see myself agreeing with but accepting such a statement proclaiming the death of innovation is also going a little too far). In any case, I think all of this presents something that us glossy-eyed idealistic developers (designers, technical professionals, etc.) may need to take a few steps back and reconsider how to optimize for better results because balancing the two (profits and R&D-based innovation) can be quite the juggling act.

There is often an all-too familiar battle between the execs and the creative development teams when it comes to decisions regarding how a product ought to be executed. It is one where the decision is ultimately made by the execs with creatives to rethink, defend the necessity, and articulate their points better in terms of business but of course, it still provides no assurance it will be fruitful.

So is there a better way to adapt the innovation-to-cash process so it promotes revenue, increases margins, and won't crush the creative, innovative spirit? Or has true innovation died as Nussbaum suggested, and been replaced by minute cosmetic modifications to a product/service?

Tuesday, April 21, 2009

Design is the Problem - and the Solution?


With so many books on my list that I wanted to read, finding the time along with a steady concentration is no easy feat. However, I recently came to learn about how a former design college professor's book - Design is the Problem was released. I was extremely excited to purchase it and pour through its pages right away because I remember thinking that Nathan was a different sort of designer (and design instructor) altogether with what seemed like a more expansive train of thought of how design could be applied in a more profound manner. He challenged the thought of limiting the application of our design techniques to products or even services alone - but to rethink and apply them to entire systems instead with special thought to its life cycle along with its collective impact.

It was this class taught by Nathan along with another great design professor, Ian MacColl, that we as a class researched and addressed the issues of modern day air travel. By the end of the semester, it resulted in the inception of a fictitious airline brand: Ascend, our perception of what an ideal modern-day airline should be. Following our research, we students proceeded to individually design products/services that fit into specific parts of an air travel experience. I personally thoroughly enjoyed this course and it resulted in what today is one of my favorite pieces from my student career - Ascend Enlightenment. (For more information about my Ascend Enlightenment project, you can visit my portfolio here - and for more information about Ascend airlines along with the other student projects, you can visit our college website here)

Anyway, back to his book - so I am only 40 pages in so far, but am already excited about reading ahead. Nathan is once again challenging the 'designer' within all of us to rethink and reapply our creative, problem-solving potential towards entire experiences and systems - even older established systems such as the economy. Though he is not the only one to ask this question (find another compelling example here), it is an interesting, refreshing notion to say the least. One that pushes the boundaries of how and where design is applied.

Actually, this specific design philosophy deeply resonates with my own thoughts about design which has been a struggle because as a designer, I do question myself at times about where my efforts lead to: simply to contribute yet another product to the sea of commodities that are deemed obsolete the moment they hit the shelves? To promote a lifestyle where consumers are persuaded to believe that they need to buy something and replace an older one which could be working just as well? And all for what? To 'keep up with the trends' or be considered 'out of touch?' Therein lies the challenge of rethinking everything and do more than simply creating something superficial and short-lived.
[/rant]

By the way, if any of you are interested, you can find more about his book here and if you do happen to read it, I would certainly like to know what your afterthoughts were. I will come back to update once I myself have finished the book.

Monday, April 20, 2009

"Wow, People are Stupid"


How many times have you heard of people (ie: designers, marketers, developers, etc.) condescendingly utter "Wow, people are stupid" or other remarks to a similar effect when something that they've helped develop with all of its bells and whistles goes awry....and is lost upon the end users?

I can't remember how many times I've had this conversation within my own circle of friends - especially with one of my good friends who apart from being a proficient programmer, has related his own share of insightful encounters with his clients. Clients who take the liberty of presuming, overestimating the effectiveness of what they choose to deliver to their users without any solid backing, and completely discount considering any suggestions made by anyone else - even if they happen come from the very professional programmer they've hired, who should be noted as having extensive experience in developing interactive platforms. In many circumstances, the same self-assured clients come back shortly thereafter to request revisions once they receive frustration-filled feedback from their end users - the very ones which could have been avoided had they paused to consider the suggestions made earlier.

While this is not uncommon and there is not too much that is wrong apart from the presumptuous attitude that clients may project, the problem is that it doesn't end there. The problem is when they come back with revisions and pin the entire blame on the end users being incompetent. That is is where it really makes one raise an eyebrow - and with all due respect for clients along with client satisfaction- it begs the question:
"Honestly, is it really entirely the end user's fault?"

At what point does one ask themselves "If so many users are having a hard time using this - are they all stupid? Should I pause for a few moments and take a few steps back to re-evaluate what's going on to discover what elements are causing that disconnect to take place at all?"

Essentially what it boils down to is the client clearly has a "vision" in mind along with the presumption that their vision is what their end users will want, will use, and behave a certain way with. But then those end users do something unexpected which the client had not accounted for - leading to frustration on the end user's part along with the client who must now consider a revision. However, by no means does it make the end user stupid. Only that perhaps alternatives ought to be considered which will permit the client to assess and anticipate their end users better, and figure out how this information can be leveraged with their own vision.

Now say a developer sees this problem occurring, however, the authority to make those decisions lie with someone else. How does the developer then go about persuading their client to reconsider that approach in view of the potential consequences later down the line, especially if that client is not willing to acknowledge the developer's experience, potential consequences, or any of the case studies they've presented? Is 'let them learn the hard way' the only option left at that point? Does that not risk making it harder for the client to recapture that market share because the end user's perception of the client's product has now become tainted as being one that is frustrating to use?

Anyway, on a similar note, below are some interesting articles I recently visited that relate to the topic of clients, under/overestimating the user, and so forth. Some of them are old, but the message they carry was still relevant:

Call them Clients? No, They are Business Partners! by Design Sojourn

End Users Are Not Stupid... by Lee Drake

The Gnome Journal on End Users (old, but not only are the points still completely relevant, they bring up an exceptional point of why satisfying customers is a priority because a satisfied end user becomes a good advocate for the product/service. In other words, more $$$)

An older thread regarding Kodak, software downloads, and frustrated users which I found to be an interesting read

And as always, if there are any additional examples you think are relevant, please send them on over! :)

Saturday, April 18, 2009

Products Without Social/Cultural Context = Epic Fail(ures)

I have been going back and forth about writing on this subject for the past few months but I couldn’t put it off anymore. Especially not after seeing examples where well-established, respectable companies wanting to capitalize on emerging markets by globalizing their products have made seemingly naive assumptions about users elsewhere in the world. The result? Products failed to sell in these different consumer markets due to the fact that the company's presumptions were sorely misplaced. The products were essentially out of context at a social and/or cultural level, therefore, inappropriately for the user markets they aimed to capture.

Sure, many of us would assume that larger corporations, with their vast experience and resources, would have sophisticated research techniques in place. R&D facilities within their subsidiaries would understand the local user's needs, translate them into areas of opportunities, and introduce products that not only address those needs but could easily be incorporated into their lifestyles. We would expect that someone may already have asked questions like "Is this product going to meet the needs of the consumers in Asia the same as it will meet the needs of the consumers in America? Yes? No? What are the differences and similarities?”

But just like in our assuming so, these companies too made a grave mistake in presuming that their products would sell just as well in new emerging markets just as they may have elsewhere. They assumed their products would sell like pancakes – but unfortunately, forgot to ask the simple question “Do my users even eat pancakes? More importantly – do they top them with maple syrup and whipped butter, and eat them using the same fork/knife utensils like users elsewhere do?”

While given the the fact that trying to "please everyone" can be suicidal, it should not be taken as a convenient excuse in failing to have a deeper understanding of the consumer market one is going to be introducing products to. Wouldn't a wiser approach then consist of sending out 'cultural probes' before deciding which features can be realistically incorporated, even if it is at an incremental level? At least then, instead of looking like a company that had been gravely misinformed or clueless, they can at least be able to state with conviction that they made an informed decision: "We were aware of X and Y, but due to Z, we deliberately chose to go this specific route and only incorporate features D and F into the product for the time being."

I'm interested in hearing thoughts that others would like to share regarding this matter. Below, there's a list of some examples along with their referenced articles and article highlights which may provide some ammo in jumpstarting the discussion.

Apple's iPhone, an Indian Flop, Prepares for China
by Mehul Srivastava in Businessweek
Apple, often considered a shining advocate for design and how it brings value in delivering a cool, edgy product that users love, too is guilty of having made the presumption that users elsewhere in the world would share the same enthusiasm – only to be proven wrong despite two years after its launch of iPhone in the Indian market and possibly again in China. Let's briefly go over a few points as to why this happened:
  • Price Point: Three iPhones equals one car.
    "The iPhone is also priced far beyond the reach of even many middle-class Indian consumers. Even though iSuppli, the El Segundo (Calif.) market research company, estimates iPhones cost less than $175 to build, both Apple and Airtel stuck to the approximately $700 price for the phone in India, vs. $199 with a two-year AT&T (T) contract in the U.S. In India, then, three iPhones equal one Nano, the $2,000 car that Tata Motors (TTM) launched in India just two weeks ago. An Apple spokesperson in London, Bethan Lloyd, said in an e-mail that pricing and tariff issues are decided by local partners, not Apple. Apple declined to make executives available for an interview."

  • Phone Plan: Prepaid/Pay as you Go vs. Contract.
    "For Airtel and Vodafone, subsidizing the phone has not been an option. The vast majority of Indian users have prepaid accounts, and even with the few regular contracts out there, high-end users generate just about $30 a month in call and data charges. Add to that the fact that the iPhone is easily unlocked and used on rival networks, and the carriers decided the AT&T model in the U.S. just wouldn't work in India. (In Europe, where iPhone sales have been lukewarm, many carriers reached the same conclusion.) "

  • Competition & Pricing are simply the beginning. Indians just use their phones differently.
    "According to Sanjay Gupta, the chief marketing officer of Airtel's mobile business, Indians just use their phones differently. With spotty data coverage and slow download speeds on non-3G networks, the iPhone just doesn't dazzle the way it does in the U.S. Also, Indian customers like to forward text messages; Nearly 70% of them do that at least once a day, says Gupta. Until recently, the iPhone didn't allow users to do that. "It's a big functionality issue," says Gupta. 'The device is being judged as a phone, not as a data device.' "

  • Local partners have different goals.
    "Another difficulty for Apple in India: Local partners don't necessarily have the same goal of selling lots of iPhones. Airtel, for instance, doesn't seem to mind that Indian consumers haven't embraced the gadget, since associating with Apple has helped the carrier in other ways, says Gupta. "For us, it allowed an association with iPhone as a brand," he says. 'And that's definitely made us happy.' "
With the points mentioned above, it is difficult to fathom whether Apple had asked themselves these questions before launching the iPhone and gone ahead with the launch anyway despite the consequences. Perhaps Apple wasn't arrogant in assuming that the momentum of hype the iPhone had gathered would be enough to push it into these emerging markets. Perhaps Apple deliberately took a more Microsoftesque approach where the product is released despite its shortcomings, feedback is gathered from users - both pleased and disappointed, lessons are learned, and then relevant modifications are integrated within future product generations as opposed to allotting money/time/resources beforehand and missing out on on capitalizing with the current version of the product altogether.


The Washing Machine that ate my Sari/Lungi
by Apala Chavan, Douglas Gorney, Beena Prabhu, Sarit Arora in Interactions Magazine
Whirlpool Corporation designed a single, stripped-down washing-machine platform for emerging markets. Dubbed the “World Washer,” it was launched in countries like Brazil, Mexico, China, and India with slight feature and cosmetic styling modifications to reflect local tastes of each market. Whirlpool was able to understand a few cultural elements such as in China, for instance, washing machines sat in the living room and were like a status symbol. Then despite having these cultural insights, why did the washing machine end up doing so well everywhere else but in India, especially South India? Only after noticing how abysmal the sales were in South India, Whirlpool dispatched a team to figure out what went wrong and here is what they learned:
  • Re-labeling the “Delicate” cycle as “Sari Cycle” was not enough.
    "They finally realized what was going into the machines-traditional South Indian clothing such as lungis, dupattas, mundus, angavestrams… and, of course, saris. Little more than sheets of very fine cotton or silk, six to nine yards long, the garments were getting caught, entangled, and shredded in the millimeter-wide gap between the machine’s agitator and drum."

  • Shooting one’s self in the foot with generalizations.
    "Because its designers did not broadly, deeply, and fundamentally understand specific target markets, the World Washer failed to live up to its name. The basic mistake Whirlpool made-in a variant of not understanding its target market-was to assume that needs are the same across emerging markets. The World Washer had been given a single, generalized, emerging-market reference point by designers with limited understanding and direct experience of the customs and modes of dress in South India. They did not ask the right questions of target users-if they talked to them at all. So critical details, like the thickness and dimensions of the clothes that would be washed, went unnoticed."

  • A single millimeter changed an entire business model
    "That single millimeter forced Whirlpool to completely restructure their business model and abandon their joint venture, in addition to designing a new washing machine for India. It took the company years to recoup their losses and regain significant market share in the subcontinent."
Despite having region-specific cultural insights which were integrated into overall cosmetic styling and features, the actual effectiveness of those functions in context with what they would be washing clearly hadn’t been tested. The good news is that Whirlpool fared much better in the long run when it came to catering the needs of their region-specific consumers though it proved to be an uphill battle to recapture certain markets and for people to regain that trust within their brand. In fact, their incident prompted other multinational companies to literally go the distance in understanding their users at a deeper level for successful product-localization.


Additional Examples
A few additional examples of why culturally/socially-sound contexts are not just limited to product features, but permeates through to relevant price points that reflect the spending behaviors within emerging markets as opposed to mature developed markets.
  • One India? No. Many Indias. (Markets & Submarkets)
    "While navigating the Scylla and Charybdis of design for more than one developing economy, designers also need to remember that segments within markets differ. Rama Bijapurkar, author of Winning in the Indian Market, has discussed that there are many Indias. “What confounds people about India is that everything you say about it, the opposite is also true. There are five-star hotels and abject poverty. That reality has forced corporations to reinvent their pricing-strategy formulas in emerging markets-and often to re-reinvent them. Newly affluent consumers in emerging markets are an attractive niche, but overall standards of living remain lower than in the West, gaps between the rich and the very poor notwithstanding. Even high-end shoppers have different spending behaviors than in developed markets. Marketers and product designers cannot ignore affordability.”

  • Proctor & Gamble Diapers: Premium < Affordability.
    "When Procter & Gamble introduced disposable diapers into the Brazilian market, it went in with its top-end model, which failed to sell. Only after offering a less-sophisticated diaper, half the price of the top-end version, was the company able to grow the market."

  • Good bye, Levi Strauss, we found cheaper jeans with similar/better quality.
    "With its booming economy and particularly price-sensitive market, India has taught some of the most prominent multinationals just how elusive the upper end of emerging markets can be. Levi Strauss brought its American jeans to India in 1995, not only designed but also priced as is-$65. They were considered exorbitant, especially compared with generic jeans that seemed to offer equivalent quality. After three miserable years of rampant counterfeiting and flat sales, Levi had to change its pricing and design strategy."

  • Affordability without compromising on Product Quality or Performance Reliability.
    "Affordability is a double-edged sword, however. Lo barato sale caro, goes the saying in Latin America-”what is cheap ends up being expensive.” If not designed with sensitivity to the market, low-cost products may strike target users as low-quality compromises and detract from the company’s brand appeal. That appeal, regardless of price, is in the confidence it inspires. With limited incomes, “emerging consumers” are more cautious than their counterparts in the West; they would rather pay more for quality than risk product failure. The relative financial loss from an underperforming product would be far more serious."

  • Tone down on the ‘Featuritis’
    "For users in emerging markets, streamlining or eliminating complex features, without reducing core quality, results in a more attractive and affordable product-particularly when features are added with careful consideration of the market context. ‘Getting the right product at the right price is the biggest challenge,’ says FutureBrands CEO Santosh Desai. ‘The usual approach is to strip the product of features until a semblance of affordability is attained. The trouble is that the emerging consumer, for whom every act of discretionary consumption is an act of sacrificing something essential, is looking to be seduced rather than patronized.’ For that reason, mobile phones loaded with games, music, and other extra features appealing to the U.S.A.’s youth-driven market have not succeeded in emerging markets. Feature creep, driven by the seemingly limitless appetite of developed markets for add-ons and customization, has no place in emerging market design."
Got any more examples that you think would be good to share? Please forward them on over!

Wednesday, April 15, 2009

'A Reason to Cry'-chief. (I crack myself up)

This was too awesome to not post. Taken from I New Idea.

Yes, these are actually sold for$28 a piece. $95 for custom stock cry-chiefs.


Saturday, April 11, 2009

Wednesday, April 8, 2009