LinkedIn UX groups, data and questions

Doesn’t it seem like there are a lot of user experience groups on LinkedIn? I’ve joined a few of them in hopes of staying up-to-date on topics, but after joining a couple groups, I quickly realized there were many more possible groups, and they all started looking pretty similar to me.

Why would I join this group versus that one?

Some are tied to specific organizations, like the Information Architecture Institute, the Interaction Design Association, or the Usability Professionals Association. Or like the Boxes and Arrows group, related to a specific industry publication. If you are a member of such an organization, joining the matching LinkedIn group probably makes sense in some way.

Some are focused on narrower subjects, like the Agile Experience group or mobileUX. If you have a narrower interest and find a group that fits, perfect.

Some differentiate by being localized. The UPA Israel, for instance, or London User Experience Professionals. Cadius is a group for UX people who speak Spanish. I think that’s fantastic.

But then we have all those other groups that ooze together, subject-wise. I’ll bet each has its own creation story, but at this point, the differentiation is slim.

Don’t these top 5 UX LinkedIn groups sound similar?

  1. User Experience
  2. Interaction Design Association
  3. UX Professionals
  4. UX Professionals Network
  5. User Experience Group

The second item is the group for members of IxDA, but the rest are simply professional groups for UX people. I’ll bet if you mixed together all the content and members of those groups you would first see a lot of repetition in members and topics, and second, I’ll bet you couldn’t separate them back into their original groups without a key. What does that say about these groups?

Some data on these groups

For what it’s worth, I’ll post some data I harvested while trawling LinkedIn this afternoon. (Why did I do this? Am I mad? No, but I’ve been sick all weekend, and in my addled state, cataloging some LinkedIn groups was the most obvious thing to do.)

The following data is merely what I found this afternoon. It is not comprehensive.

Chart showing membership rates of about 40 user experience groups on LinkedIn.

Chart showing membership rates of about 40 user experience groups on LinkedIn as of March 11, 2012.

Want a little more information? You can download an Excel spreadsheet I used while gathering this information. The worksheet includes columns for ID, Title, Membership, Parent Group, Created date, Type (e.g., Professional Group), Owner, Coverage (e.g., Earth, Greater London, UK, etc.), Language (didn’t fill that in), and Organization (e.g., IxDA).

Here’s the Excel file: User Experience (UX) groups on LinkedIn, March 2012 (.xslx)

Too many groups!

In closing, I think it would be easier and less time consuming to stay up-to-date in the field if there weren’t so many overlapping groups. What if some of these groups merged? Would people get too upset about that?

(Now for more tea and expectorants.)

UX and Project Mangement cross-over article from Interactions magazine

A Taxonomy of Models Used in the Design Process by Joanne Mendel in the Jan + Feb 2012 edition of Interactions magazine is pretty interesting.

At Covenant Eyes we’re continually in the churn of Agile development, and integrating user experience work can be challenging. We’re figuring it out, and have definitely made some breakthroughs, but this article has provided another perspective that is helping me think about timing of user experience work within the loose phases of work that a typical project runs through.

It isn’t a stretch to layer the phases of Discovery, Reframe, Envision, and Create over a project’s lifecycle, and so tying different models for design work in each phase provides an opportunity to reflect on how we’re doing with matching up appropriate design work.

I’m asking my team and our project managers to read through it, and perhaps we’ll get a chance to discuss it together and consider if we can use some of the ideas to do better work.

IxDA Lansing kickoff featured speaker Dan Klyn

Last night was the inaugural event for IxDA (Interaction Design Association) Lansing, and information architect Dan Klyn presented “The Nature of Information Architecture.”

Presentation overview

Dan’s presentation was both informative and controversial. He provided some nice background on the naming of the field of information architecture, citing Richard Saul Wurman phrasings at the 1976 AIA convention in Philadelphia and then Wurman’s book “Information Architects.”

Dan also proposed a way of considering what information architecture is through a target diagram, from core to outside as:

  1. Ontology (the study of being)
  2. Taxonomy (the science of order or arrangement)
  3. Choreography (writing/describing circular dance)

I like this description of IA. I do feel it gets to the heart of the work, and I can immediately consider certain areas of my own job in this light. Of course there are plenty of other descriptions of IA from Wurman, Rosenfeld, Morville, and others, but as I bring them to mind, they seem to be more focused on describing IA to outsiders whereas this one speaks to those of us already  in the field.

I wouldn’t, for instance, walk up to a client and say, “I’m concerned with the ontology of your system.” But I can talk with other information architects about questions of ontology, and they will likely bring their own experiences to bear.

After discussing this model for IA and how it circles the concept of understanding, Dan shared two ways to answer the question “How do we know when IA is good?”

  • performance (need to measure change in performance from a benchmark)
  • propriety (how appropriate to the context is the IA solution)

When discussing this question of quality of IA, the point was made that a functional, adequate solution is artless. It is insufficient. We’ve all used a website or service that we end up getting irritated with, and could comment afterward “Well at least it worked.” Good IA goes beyond sheer performance to fulfill propriety as well.

Isn’t naming always controversial?

The controversial part of Dan’s presentation is in the naming of things. The gist of my issue is that I felt Dan was saying that strategic-level IA work—the work that involves not just end-users but is concerned with larger business concerns—is beyond the scope of user experience work. (I really hope I’m not misrepresenting Dan’s meaning.)

My experience as a UX professional (note that I used to refer to myself as an information architect) says that UX begins with understanding both user and business needs, and is best done when exploring the strategic-level in order to frame the tactical work.

That said, I will say that with all the work demanded of UX in my job, I regret that I haven’t had the time to devote to a more traditional strategic IA-based analysis of our systems.

Dan made the point that this strategic work, though done by a smaller group, has greater leverage than choosing which style of form field to use. He is right, of course. I just think that that work is still to be done under the UX umbrella.

Thanks Dan for the talk, and Chris Bachelder for bringing it together

All-in-all, I’m really glad I had this opportunity to take part in Dan Klyn’s presentation. It was well-done and thought-provoking. Dan has shared his slides for “The Nature of Information Architecture.”

IxDA Lansing is the first Michigan group of the Interaction Design Association, and was initiated by Chris Bachelder of Techsmith Corp. I, for one, am grateful to have a Lansing-based group to advance UX events. Thanks Chris!