Your SlideShare is downloading. ×
People, not process
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

People, not process

399
views

Published on

Published in: Design, Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
399
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. PEOPLE, NOT PROCESS Ian Fenn Twitter: @ifenn
  • 2. 16 JUNE 1989
  • 3. 1991
  • 4. 1997
  • 5. A SMALL TEAM๏ producer๏ assistant producer๏ production assistant๏ graphic designer๏ web developer๏ perl developer
  • 6. WE WORKED...๏ collaboratively๏ iteratively๏ job titles didn’t matter๏ documentation was light๏ we were user-centred
  • 7. FENN UX?
  • 8. WE WORKED...๏ collaboratively๏ iteratively๏ job titles didn’t matter๏ documentation was light
  • 9. LEAN UX?
  • 10. THERE IS NOTHING NEW UNDERTHE SUN BUT THERE ARE LOTS OFOLD THINGS WE DONT KNOW. Satirist Ambrose Bierce, The Devils Dictionary
  • 11. 2012
  • 12. “ARE YOU INTERESTED IN A UX ROLE?” I ASKED.
  • 13. “YES,” SHE SAID.
  • 14. “WHAT EXPERIENCE DO YOU HAVE?”
  • 15. “C, C#, C++, AND VISUAL BASIC”
  • 16. http://www.flickr.com/photos/76657755@N04/6881496274
  • 17. A DESIGNERSOLVESPROBLEMSWITHINA SET OFCONSTRAINTS.Mike Monteiro
  • 18. A DESIGNER SOLVES PROBLEMSTHEY OFTEN HAVE TO HELPIDENTIFY WITHIN A SET OF EVER-CHANGING CONSTRAINTS. Ian Fenn
  • 19. A DESIGNER SOLVES PROBLEMSTHEY OFTEN HAVE TO HELPIDENTIFY WITHIN A SET OF EVER-CHANGING CONSTRAINTS. WITHNO AUTHORITY. Ian Fenn
  • 20. 1. START WITH PEOPLE, NOT PROCESS.
  • 21. YOU GOT HIRED. WHY?
  • 22. ๏ enthusiasm๏ total confusion๏ disillusionment๏ search for the guilty๏ punishment of the innocent๏ reward and promotion of the non-participants
  • 23. UNFORTUNATELY FOR US, WE CARE
  • 24. 1. Be armed with knowledge http://www.flickr.com/photos/pedrobelleza/4705301278/
  • 25. 1. ARRIVE ARMED WITH KNOWLEDGE๏ Read the usual suspects - Jared Spool, Jakob Nielsen, Johnny Holland, Boxes and arrows, UX magazine...๏ Familiarise yourself with the high traffic websites that people visit - how are they shaping user behaviour?๏ Question everything around you. Why are things the way they are?๏ Is there a formal project brief? If so, ask for a copy in advance. Print it off. Scribble questions on it.
  • 26. 2. Arrive dressed for success. http://www.flickr.com/photos/littlebitmanky/424680015/
  • 27. 3. MEET THE PROJECT SPONSOR
  • 28. I keep six honest serving-men (They taught me all I knew);Their names are What and Why and WhenAnd How and Where and Who.- Rudyard Kipling in his "Just So Stories" (1902)
  • 29. ๏ Why are we doing this? (Business needs)๏ What do the users need? (User needs)๏ Where do they want it? (Environment/Device)๏ Who is doing it? (Team)๏ When do we have to get it done by? (Time available)๏ How will we measure success?
  • 30. THE VEHICLE WILL NOT START (THE PROBLEM)๏ Why? - The battery is dead. (first why)๏ Why? - The alternator is not functioning. (second why)๏ Why? - The alternator belt has broken. (third why)๏ Why? - The alternator belt was well beyond its useful service life and not replaced. (fourth why)๏ Why? - The vehicle was not maintained according to the recommended service schedule. (fifth why, a root cause) http://en.wikipedia.org/wiki/Five_whys
  • 31. ๏ What do they expect?๏ What’s in it for them?๏ What challenges do they face?๏ How will they know the project has been successful?๏ Who else should you meet?
  • 32. 4. MEET THE TEAM MEMBERS
  • 33. http://bit.ly/war-developers
  • 34. http://alextoul.posterous.com/the-war-between-developers-designers-project
  • 35. MEET TEAM MEMBERS๏ What’s their history?๏ How do they work?๏ What has been useful in the past?๏ What has annoyed them?๏ What are their expectations?๏ How do they like to communicate?
  • 36. PRODUCT MANAGERS๏ Some are ux-focused, others are business or technical๏ None of them will be short of an opinion๏ Support all of your work with evidence๏ Share it often
  • 37. PROJECT MANAGERS๏ Treat as you would a project sponsor๏ Be honest about timings and try to stick with them๏ Keep them informed๏ Ask them to coordinate feedback
  • 38. DEVELOPERS AND DESIGNERS๏ Involved them early on๏ Share your work or collaborate often๏ Understand their constraints
  • 39. DEALING WITH DIFFICULT PEOPLEDr. Rick Brinkman and Dr. Rick Kirschner (Hat tip to Giles Colborne for directing me to this book.)
  • 40. Task focusPassive Aggressive Relationship focus
  • 41. Task focus Whiner TankPassive Aggressive Think they Yes person know it all Relationship focus
  • 42. Task focus Whiner TankPassive Aggressive Think they Yes person know it all Relationship focus
  • 43. Task focus Get it right Get it donePassive Aggressive Get along Get appreciated Relationship focus
  • 44. CULTURAL ISSUES๏ Brits may be understated
  • 45. CULTURAL ISSUES๏ Japanese won’t want to say anything negative
  • 46. CULTURAL ISSUES๏ Chinese will be concerned about loss of face
  • 47. CULTURAL ISSUES๏ Indians will say ‘yes’, even if it’s a no.
  • 48. USEFUL PHRASES๏ ...... (Silence: Beg for forgiveness, not for permission.)๏ “Do you mind me asking - are you looking for solutions or do you just want to get things off your chest?”๏ “Which of the solutions you mentioned would you choose?”๏ “If we were going to meet the delivery date, how could we make that happen?”๏ “How could we find out...”
  • 49. ๏ know what you know๏ find out what you don’t know๏ ask what you need to know now๏ tell others what you now know
  • 50. WELL DONE.NOW YOU CAN THINK ABOUT PROCESS
  • 51. LAST NOVEMBER I RECEIVED AN EMAIL...
  • 52. 9.05 – YOURE GREETED IN THE LOBBY BY A UNICORN - YES, AUNICORN - TROTTING AROUND FOR A PROMOTIONAL PHOTO SHOOT. ITS JUST ANOTHER DAY AT THE OFFICE.
  • 53. 9.10 – GRAB AN ESPRESSO IN THE CAFE; IN THE QUEUE HAVE ACHAT WITH A FELLOW LEAD ABOUT LINE MANAGEMENT. YOUVERECENTLY CHANGED THE FORMAT OF YOUR BI-WEEKLY MEETINGS TO A MORE CASUAL LUNCH AND ITS WORKING BRILLIANTLY.
  • 54. 9.20 – YOUR MAIN CLIENT IS RUNNING AN AGILE PROCESS; IN YOURSCRUM YOU GIVE A SNAPSHOT OF WHAT YOU AND YOUR TEAM OF 4 ARE UP TO.
  • 55. 9.30 – RUN A WORKSHOP WITH KEY STAKEHOLDERS, THE CREATIVEAND TECH TEAMS (WE LIKE TO BLEND) TO SCAMP 2 ROUTES FOR AN IMPROVED PURCHASE PROCESS. OUR LEAD STRATEGIST KICKS THE WORKSHOP OFF WITH RESEARCH INSIGHTS.
  • 56. 11.00 – HOST A `BIG MAMA (OUR BI-WEEKLY TEAM KNOWLEDGE SHARE). TODAYS TOPIC: INSIGHTS FROM YOUR RECENT TRIP TO ADAPTIVE PATHS UX INTENSIVE.
  • 57. 12.00 – ATTEND ANOTHER WORKSHOP, THIS TIME FOR YOUR OTHER CLIENT, HOSTED BY THE CREATIVE DIRECTOR ON THE ACCOUNT. THE OBJECTIVE: SKETCH A FEW USER JOURNEYS TO SHOW HOWCONTENT CAN BE SHARED ACROSS A CAMPAIGN SITE, MOBILE AND TABLET DEVICES.
  • 58. 1.30 – PICK UP A FEW LUNCH BUDDIES FOR A WALK THROUGH THE LOCAL AREA AND A SANDWICH FROM A NEARBY CAFE.
  • 59. 2.30 – ATTEND A USER TESTING SESSION IN OUR IN-HOUSE LAB.
  • 60. 3.45 – MEET WITH YOUR TEAM TO GO THROUGH THE DETAIL OFNEW WIREFRAMES IN AXURE. RUN THE WIREFRAMES THROUGH THE PERSONAS AND STRESS-TEST THEM WITH EXPERIENCE PRINCIPLES.
  • 61. 5.15 – GET DEBRIEFED ON A PITCH YOULL BE HELPING OUT WITHNEXT WEEK. THE PROSPECT: A HIGH FASHION BRAND WHO WANT TO RE-ENERGISE THEIR ONLINE PRESENCE.
  • 62. 6.15 – WIND DOWN WITH A GAME OF TABLE TENNIS AND A BEER IN THE COMPANY BAR.
  • 63. NOTICE ANYTHING MISSING?
  • 64. 2. MAKE TIME TO THINK
  • 65. A TECHNIQUE FORPRODUCING IDEAS James Webb Young
  • 66. A TECHNIQUE FOR PRODUCING IDEAS๏ An idea is nothing more nor less than a new combination of old elements๏ The capacity to bring old elements into new combinations depends largely on the ability to see relationships
  • 67. A TECHNIQUE FOR PRODUCING IDEAS๏ First, gather raw materials - both the materials of your immediate problem and the materials from your rich store of general knowledge.๏ Second, work over those materials in your mind and try to identify patterns.
  • 68. A TECHNIQUE FOR PRODUCING IDEAS๏ Third, go for a walk in the park. This is the incubating stage, where you let something beside the conscious mind do the work of synthesis.๏ Fourth, an idea will be born, often when you least expect it.๏ Fifth, shape and develop an idea to practical usefulness.
  • 69. KING BED
  • 70. 3. SET YOUR IDEAS FREE
  • 71. BE PREPARED - FOR CHANGE
  • 72. THROUGHOUT THE PROCESS, QUESTION EVERYTHING.
  • 73. BE WILLING TO CHANGE TOOLSAND PROCESS IF YOU NEED TO.
  • 74. BE PREPARED TO BE WRONG
  • 75. HOW TO STAY SANE PHILIPPA PERRY
  • 76. SELF-OBSERVATION๏ What am I feeling now?๏ What am I thinking now?๏ What am I doing at this moment?๏ How am I breathing?
  • 77. ONE LAST THING...
  • 78. FIRST RULE OF CONSULTING:NO MATTER HOW MUCH YOUTRY, YOU CAN’T STOP PEOPLEFROM STICKING BEANS UP THEIRNOSE. Jared Spool - http://www.uie.com/brainsparks/2011/07/08/
  • 79. GOOD LUCK......AND THANK YOU. Twitter: @ifenn