(Originally first published on July 4, 2014 at https://www.linkedin.com/pulse/20140702070019-9377042-don-t-get-confused-ucd-vs-ucsd/ )
Also, this article is a part of the title UX Simplified: Models & Methodologies by Samir Dash (ISBN: 978-1-3115-9110-4 / ASIN: B00LPQ22O0 ). Available at Amazon: http://www.amazon.com/dp/B00LPQ22O0/
In my last posts I discussed about Usability Design and User-Centered Design (UCD) and User-Centered Systems Design (UCSD). But many confuse between these two. So in the following I am trying to differentiate these two:
UCD vs UCSD
UCD is differs from the UCSD in the following areas:
- Goal: The goal of UCSD is more on the process than the user so as to make the final product/system more usable. UCD rather focuses more on “users” of the product and not the design process. More focus is spent on understanding the user and their need.
- Process vs. Techniques Set: UCSD is about system development where as UCD is mostly a set of tecniques and process sets to be used with in UCSD
- Perception: The DNA of UCSD is about changing the mindset of the professionals in the development process so that the designing aspect of usability can be put into practice freely and with higher priority. The UCD process is not about the changing perception about the priority of the design in the whole process.
- Broadness: UCSD covers the whole process that includes the areas which are even not part of “designing” whereas UCD can be seen as a subset of UCSD focusing of the “design process sets”.
UCD Models and Process
There 3 different models that support UCD in varying degrees and follow the ISO standard Human-Centred Design for interactive systems:
- Cooperative Design: This involves designers and users on an equal footing.
- Participatory Design (PD): Inspired by Cooperative Design, focusing on the participation of users
- Contextual Design: “Customer-Centered Design” in the actual context, including some ideas from Participatory Design.
All these UCD models involve more or less a set of activities grouped into the following steps mentioned below:
- Planning: in this stage the UCD process is planned and if needed customized. It involves understanding the business needs and setting up the goals and objectives of the UX activities. Also forming the right team for the UX needs and if needed hiring specialties fall into this step.
- User data collection and analysis: This step involves data collection through different applicable methodologies such as user interviews, developing personas, conducting scenarios , user-cases and user stories analysis, setting up measurable goals.
- Designing and Prototyping : This involves activities like card sorting, conducting IA, wire framing and developing prototyping.
- Content writing: this involves content refinement and writing for web and similar activities.
- Usability testing: This involves is a set of activities of conducting tests and heuristic evaluations and reporting to allow refinement to the product. However Usability Testing can have its set of steps involving similar activities such as planning , Team forming, testing , review and data analysis and reporting.
All these are similar to most of the steps that fall under Usability Design as UCD can be seen as a subset of process with in Usability Design.
So many processes: What is where?
After going through multi relation models in all these processes and sub process discussed in this post and the previously discussed posts, it might be little confusing to visual all the overlapping and dependable process sets. So here is a simple representation diagram that roughly shows the overlapping relations:
(c) 2013-14, Samir Dash