Five Sketches™ at STC Vancouver
I’m presenting on repurposing the core competencies that relate to ideation and design, at the April 2009 Society for Technical Communication session, in Vancouver, Canada. The presentation is titled: Ideation and design with Jerome Ryckborst.
During this session, I’ll talk about how technical communicators have skill sets that make them valuable outside the “traditional” domain of technical communication. I’ll tell them the story of how I ventured into software designer with developers.
It’s a full hour—lots of slides. See you there!
P.S. I’m a pretty engaging presenter, so don’t let the fact that (today) I’m a boring blogger mislead you. I believe what Seth Godin says about presentations.
Update
The slides are on SlideShare.
April 17th, 2009 | Tags: core competencies, event, Five Sketches™, Jerome Ryckborst, Society for Technical Communication, STC Canada westcoast | Category: What I am doing |
2 comments
Jerome on Twitter
Jerome on LinkedIn
Jerome on Technorati
Jerome on Delicious
Sadly, I had class the night of the event so I didn’t attend. However, I was able to check your presentation. Thank you very much for posting it.
Comments from a Technical Communicator with background in negotiation and conflict resolution:
Harvard mathematician Howard Raiffa called negotiation the science and art of collaborative decision making; my former employers and mentors called it the art of collaborative solution design. Interestingly, Five Skethes™ identifies and addresses the same concerns negotiation does: crafting the problem appropriately, diffusing the tendency to defend one’s idea, promoting cooperation, co-creating possible solutions, dealing with divergent ideas, managing conflict, and agreeing. Since negotiation and conflict resolution is supported by literally thousands of empirical studies, I would say that Five Sketches has way more scientific support than you like to admit.
The classical orange conflict, illustrates this overlapping nicely: two kids are quarrelling over the last orange in the house. As the parent, if you define the problem as “there is one orange for two kids who want it badly”, you will probably split the orange in half. But what if the boy wants to make orange juice and the girl wants it to make orange peel candy? The very definition of the problem can constrain creativity and hinder agreements.
There are more overlapping areas, but for now you got me interested in usability research!
Looking forward for an opportunity to talk,
Tak Ishikawa
I think user interfaces really should be designed by someone who has user experience design knowledge, not developers. Developers should focus on the quality of the codes. Asking developer to design UI is just like asking them to writer help.