Toward a socio-technical pattern language
•Download as PPT, PDF•
1 like•761 views
The document discusses how socio-technical patterns and pattern languages can help align people, processes, and technology in complex systems design. It outlines the case for considering human factors, describes some proposed socio-technical patterns, and argues that representing knowledge as patterns can provide more actionable guidance for designers compared to typical research publications. Challenges include developing comprehensive socio-technical pattern languages and methods for applying patterns during design.
![Outline ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (18)
Similar to Toward a socio-technical pattern language
Similar to Toward a socio-technical pattern language (20)
More from John Thomas
More from John Thomas (20)
Recently uploaded
Recently uploaded (20)
Toward a socio-technical pattern language
- 1. Toward a Socio-Technical Pattern Language How do we help design teams align people, process, and technology? John Thomas, IBM Research Madeira, Portugal, 29 July 2003
- 7. Potential Forms of Knowledge Known, Predictable, Unchanging, Simple Unknown, Unpredictable, Changing, Complex Algorithms, Formulae, Programs, Machines Patterns Guidelines Heuristics, Principles, Properties Case Studies Stories Ethical values and fluid intelligence
- 8. How can we help the designer DESIGN?
- 22. Reality Check
- 23. Reality Check
- 24. Who Speaks for Wolf? Visual by www.PDIimages.com
- 26. Support Conversation at the Borders
Editor's Notes
- There are a host of empirical studies illustrating that merely throwing new technology at a problem is unlikely to result in any very substantive benefit. The ROI on HCI varies but is much higher than the typical IRR for businesses.
- Nonetheless, applications continue to be developed today which have glaring problems, the solutions to which, have in some cases been known for decades. There are several main reasons for this gap between what we could do to make systems really useful to our customers and what the industry all too often settles for. These include trying to “add on” HCI as some kind of interface paint after the system functionality has been designed, a lack of HCI expertise on product development teams, a rush to market that bypasses the time taken to understand the customer’s situation, organizational anomalies in how products are priced and success is measured. In many cases, however, the fundamental problem is that the work taken to support the user properly is