Log on:
Powered by Elgg

Azra Ahmed :: Feeds

December 12, 2015


December 11, 2015


December 10, 2015


December 09, 2015


December 08, 2015


December 07, 2015


December 05, 2015

Links for 2015-12-04 [del.icio.us]


December 04, 2015

Links for 2015-12-03 [del.icio.us]


December 03, 2015


December 02, 2015


December 01, 2015


November 30, 2015


November 29, 2015

Links for 2015-11-28 [del.icio.us]

  • Storytelling That Moves People
  • Ira Glass on Storytelling, part 1 of 4 - YouTube
  • Ira Glass on Storytelling, part 2 of 4 - YouTube
  • Ira Glass on Storytelling, part 4 of 4 - YouTube
  • Ira Glass on Storytelling, part 3 of 4 - YouTube
  • Summary of the book Story by Robert McKee
    McKee does have his "10 commandments:" Thou shalt not take the crisis or climax out of the PROTAGONIST'S hands. The anti-"deus ex machina" commandment. Thou shalt not make life easy for the protagonist. Nothing progresses in a story except through conflict. Thou shalt not use FALSE mystery or cheap surprise. Don't conceal anything important the protagonist knows. Keep us in step with the hero. We know what he or she knows. Thou shalt respect your audience. The anti-hack commandment. Thou shaLT know your world as God knows this one. The pro-research commandment. THOU SHALT NOT COMPLICATE WHEN COMPLEXITY IS BETTER. Don't multiply the complications on one level. Use all three: intrapersonal, interpersonal, extra personal. THOU SHALT SEEK THE END OF THE LINE. The negation of negation, taking characters to the farthest reaches and depth of conflict imaginable within the story's own realm of probability. THOU SHALT NOT WRITE ON THE NOSE. Put a subtext under every text. THOU SHALT NOT GIVE EXPOSITION STRICTLY FOR EXPOSITION'S SAKE. Dramatize it. Convert exposition to ammunition. Use it to turn the ending of a scene, to further the conflict. THOU SHALT REWRITE.


November 28, 2015


November 27, 2015


November 26, 2015


November 25, 2015


November 24, 2015

It's high time for designers to get out of the way of design thinking

Design at IBM

A prospective client sent me a link to this in-depth article on IBM's design thinking revolution, where Phil Gilbert, IBM's General Manager of Design, has hired over 1000 designers into the firm, and pushed for over 8000 of its managers and staff to get 'trained' in design thinking. They have even created specific design centres across the firm, with design offices in most of its key locations, such as the one above. The goal is nothing short of beginning IBM's next phase of transformation, one of many in its 100+ year history.

However, all is not rosy. Despite achieving a monumental success relative to the status quo, 8000 'recognised' design thinkers in a corporation of over 370,000 souls is barely a dent in terms of changing practice. If NoTosh were to effect change in only 2% of the teachers with whom we work, we'd have packed up our bags long ago.

I'm not sure hiring 1000 designers in and of itself is the answer to any organisation trying to instil a different way of viewing the world. Here's why.

Since design thinking really began to be a thing, back in the early 60s, the designer him or herself has consistently been at the centre of the design process. Even though we talk of 'user-centred design', the actual ideation and production of a solution, and in many cases the synthesis and definition of the problem to be solve, too, are all tasks undertaken by skilled 'designers', rather than the people in the organisation who have the scope, brand, or 'permission' to play in that space. Once the designers leave the project, so does the design thinking. 

There is a reason d.school sees its executive courses filled with repeat customers and firms like IDEO continue to thrive - they are resolving challenges in specific examples of services or products, but not necessarily transforming the firms and organisations who had the budget and desire to solve a problem in that specific area. Solving a problem costs money. Solving a problem and teaching the client how to do it again and again costs more than just money. That might be the greatest challenge of all.

It's not just a gut feel or my word for it either. There is ample research showing this phenomenon of 'designer at centre' of the process, and the negative effects it has on finished products and services (Brown & Katz, 2011; Leifer, Plattner & Meinel, 2013).

Where the IBM story gets interesting is the number of times the word 'study' is used: four times. Those who want to think differently have to work hard at it, and look out of their existing ecosystem to see how. But the words 'teach' or 'show' or 'share'...? 0 appearances in this article, and many like it.

As long as organisations 'buy in' design expertise, it is in the designers' interest not to teach or to show. After all, where will the next gig come from? And are all designers clear on how they can work and teach their craft to the client? In our firm, we're not only well-practiced at thinking differently, both creatively and critically, but we're also beautifully amateur in so many of the industrial domains in which we choose to play. We are not experts in automotives, fashion, television or web startups. But we are expert teachers. And, with that, we are inherently sharers and showers.

It is that nuance that will help design move from the ranks of bearded, checked-shirt, boating shoe cool kids, and into any organisation that wants to effect perpetual and significant change in the way it views the world around it. If you want to outthink the limits of what's possible, the first step might be to put learning at the heart of everything you do

References:
Brown, T., & Katz, B. (2011). Change by design. Journal Of Product Innovation Management, 28(3), 381-383.
Leifer, L., Plattner, H., & Meinel, C. (2013). Design thinking research: Building innovation eco-systems.

 



November 21, 2015

Links for 2015-11-20 [del.icio.us]


November 20, 2015


November 19, 2015


November 18, 2015


November 16, 2015


November 13, 2015


<< Back Next >>