<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Designing for Social Interaction</title>
	<atom:link href="http://boxesandarrows.com/designing-for-social-interaction/feed/" rel="self" type="application/rss+xml" />
	<link>http://boxesandarrows.com/designing-for-social-interaction/</link>
	<description>Boxes and Arrows is devoted to the practice, innovation, and discussion of design; including graphic design, interaction design, information architecture and the design of business.</description>
	<lastBuildDate>Wed, 15 May 2013 11:41:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: erova</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8037</link>
		<dc:creator>erova</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8037</guid>
		<description><![CDATA[There are huge opportunities to increase adoption and engagement in these strong, weak, and temporary ties.  Unfortunately, in many of the off-the-shelf social or collaboration platforms I&#039;ve seen (my experience is limited to enterprise social tools), the ability to recognize and target interactions based on how well people may know each other is a pipe dream. 

Um, check that: a pipe dream would suggest some of these providers are aware of the opportunities that exist in those relationships. In fact, I find many of these providers/vendors/etc expect us to be wowed just to be able to add *friends* or *colleagues* because Facebook and LinkedIn do it.   Hopefully as these products continue to mature and react to more innovative entrants into the market, we&#039;ll see greater functionality in reputation scoring and relationship management.  

Until then, without sounding like I&#039;m giving up, I feel like my hands are tied to the technology my clients have agreed to long before UX types like myself enter the picture.]]></description>
		<content:encoded><![CDATA[<p>There are huge opportunities to increase adoption and engagement in these strong, weak, and temporary ties.  Unfortunately, in many of the off-the-shelf social or collaboration platforms I&#8217;ve seen (my experience is limited to enterprise social tools), the ability to recognize and target interactions based on how well people may know each other is a pipe dream. </p>
<p>Um, check that: a pipe dream would suggest some of these providers are aware of the opportunities that exist in those relationships. In fact, I find many of these providers/vendors/etc expect us to be wowed just to be able to add *friends* or *colleagues* because Facebook and LinkedIn do it.   Hopefully as these products continue to mature and react to more innovative entrants into the market, we&#8217;ll see greater functionality in reputation scoring and relationship management.  </p>
<p>Until then, without sounding like I&#8217;m giving up, I feel like my hands are tied to the technology my clients have agreed to long before UX types like myself enter the picture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jasonux</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8038</link>
		<dc:creator>jasonux</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8038</guid>
		<description><![CDATA[good reading for designers as basic knowledge of design for society]]></description>
		<content:encoded><![CDATA[<p>good reading for designers as basic knowledge of design for society</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: padday</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8039</link>
		<dc:creator>padday</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8039</guid>
		<description><![CDATA[Thanks for the comments! 

@Chris

&quot;...the ability to recognize and target interactions based on how well people may know each other is a pipe dream.&quot;

I don&#039;t think it is a pipe dream. Many companies are working on building tools that extract social graph data and make that available to others. Many research studies have been conducted on Twitter users and usage by using their API to access their data about who is connected to whom.

&quot;I find many of these providers/vendors/etc expect us to be wowed just to be able to add *friends* or *colleagues* because Facebook and LinkedIn do it.&quot;

I think it is up to us to educate others about different kinds of relationships. We need to show people how having one big friends group doesn&#039;t reflect life offline, and presents as many problems as opportunities. It is up to us to push this and get people thinking about doing more than what exists today. You may be tied to a certain technology now, but we need to make sure that people are informed enough so that they might make different decisions next time.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the comments! </p>
<p>@Chris</p>
<p>&#8220;&#8230;the ability to recognize and target interactions based on how well people may know each other is a pipe dream.&#8221;</p>
<p>I don&#8217;t think it is a pipe dream. Many companies are working on building tools that extract social graph data and make that available to others. Many research studies have been conducted on Twitter users and usage by using their API to access their data about who is connected to whom.</p>
<p>&#8220;I find many of these providers/vendors/etc expect us to be wowed just to be able to add *friends* or *colleagues* because Facebook and LinkedIn do it.&#8221;</p>
<p>I think it is up to us to educate others about different kinds of relationships. We need to show people how having one big friends group doesn&#8217;t reflect life offline, and presents as many problems as opportunities. It is up to us to push this and get people thinking about doing more than what exists today. You may be tied to a certain technology now, but we need to make sure that people are informed enough so that they might make different decisions next time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sriyansa</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8040</link>
		<dc:creator>sriyansa</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8040</guid>
		<description><![CDATA[Awesome post with great insights Paul!

I think the single most critical point you have made here is to separate &quot;weak&quot; and &quot;temporary&quot; ties. The failure to realize this distinction lies at the heart of most critiques of any community driven endeavor. Traditional communities, that the word hark backs to, were people with weak ties. The internet communities are one of temporary ties.

What internet has really facilitated is the emergence of these temporary ties because the marginal cost of communicating with anyone new is close to zero. In earlier days, the cost of discovery itself was a significant barrier to entry for these communications to happen.

Again great post, and hope to read some more soon.]]></description>
		<content:encoded><![CDATA[<p>Awesome post with great insights Paul!</p>
<p>I think the single most critical point you have made here is to separate &#8220;weak&#8221; and &#8220;temporary&#8221; ties. The failure to realize this distinction lies at the heart of most critiques of any community driven endeavor. Traditional communities, that the word hark backs to, were people with weak ties. The internet communities are one of temporary ties.</p>
<p>What internet has really facilitated is the emergence of these temporary ties because the marginal cost of communicating with anyone new is close to zero. In earlier days, the cost of discovery itself was a significant barrier to entry for these communications to happen.</p>
<p>Again great post, and hope to read some more soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrbutler</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8041</link>
		<dc:creator>chrbutler</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8041</guid>
		<description><![CDATA[Paul,

I&#039;m very interested in this concept, and I think you&#039;re right about how different design and UI approaches are best suited for particular strengths of ties--particularly professional ones. 

I actually heard a program (Spark podcast) on this recently and began to think about the different types of connections I maintain online. Rather than thinking of them in terms of strength, I thought more about how frequency indicated value. I then mapped it out and found that I had a longer list of connections with whom I spoke every few months than those with whom I spoke several times a month (not including family, friends or co-workers). The people that were in the &quot;every few months&quot; group presented a lot of value to me, though! (They&#039;d probably fit within your category of temporary or specific need-based ties.) I wrote up a blog post on this and included a visualization of my connections map: http://www.newfangled.com/mapping_your_professional_network. As I pointed out there, the two to three people that had a significant impact on my career in the last year were in the infrequent group--something I wouldn&#039;t have realized without mapping it out.

The reputation points aspect of Boxes and Arrows commenting functionality is a perfect example of ways that UI can help to leverage and indicate the value of weak or need-based ties. I&#039;ve actually made a handful of long-term professional connections by participating in discussions attached to posts like yours with people I would probably never have encountered otherwise.

Chris]]></description>
		<content:encoded><![CDATA[<p>Paul,</p>
<p>I&#8217;m very interested in this concept, and I think you&#8217;re right about how different design and UI approaches are best suited for particular strengths of ties&#8211;particularly professional ones. </p>
<p>I actually heard a program (Spark podcast) on this recently and began to think about the different types of connections I maintain online. Rather than thinking of them in terms of strength, I thought more about how frequency indicated value. I then mapped it out and found that I had a longer list of connections with whom I spoke every few months than those with whom I spoke several times a month (not including family, friends or co-workers). The people that were in the &#8220;every few months&#8221; group presented a lot of value to me, though! (They&#8217;d probably fit within your category of temporary or specific need-based ties.) I wrote up a blog post on this and included a visualization of my connections map: <a href="http://www.newfangled.com/mapping_your_professional_network" rel="nofollow">http://www.newfangled.com/mapping_your_professional_network</a>. As I pointed out there, the two to three people that had a significant impact on my career in the last year were in the infrequent group&#8211;something I wouldn&#8217;t have realized without mapping it out.</p>
<p>The reputation points aspect of Boxes and Arrows commenting functionality is a perfect example of ways that UI can help to leverage and indicate the value of weak or need-based ties. I&#8217;ve actually made a handful of long-term professional connections by participating in discussions attached to posts like yours with people I would probably never have encountered otherwise.</p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: padday</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8042</link>
		<dc:creator>padday</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8042</guid>
		<description><![CDATA[Thanks again for the comments!

@Sriyansa Many people use weak ties to describe our interactions online with people we don&#039;t know. I&#039;m glad that my distinction of weak and temporary ties is useful for you, it has certainly helped me in my work. 

@Chris I think there is a great opportunity for us to rethink how we represent our relationships in our digital tools. Imagine if we replaced/supplemented our alphabetical lists with representations like you created in your exercise. We could learn a lot of new things.

The relationships between strength of tie and frequency of communication is an interesting one, and it comes up in research. There are people in many of our lives that we don&#039;t communicate with frequently, yet would turn to for support in an instant if we needed to. These are also the people that we meet, and despite not having seen each other in many months, it feels immediately natural. People describe it as immediately feeling &quot;like the old times&quot; and &quot;like you&#039;d just seen each other a few days ago&quot;. So frequency is a good signal for strength of tie, but it doesn&#039;t always show us the full picture.]]></description>
		<content:encoded><![CDATA[<p>Thanks again for the comments!</p>
<p>@Sriyansa Many people use weak ties to describe our interactions online with people we don&#8217;t know. I&#8217;m glad that my distinction of weak and temporary ties is useful for you, it has certainly helped me in my work. </p>
<p>@Chris I think there is a great opportunity for us to rethink how we represent our relationships in our digital tools. Imagine if we replaced/supplemented our alphabetical lists with representations like you created in your exercise. We could learn a lot of new things.</p>
<p>The relationships between strength of tie and frequency of communication is an interesting one, and it comes up in research. There are people in many of our lives that we don&#8217;t communicate with frequently, yet would turn to for support in an instant if we needed to. These are also the people that we meet, and despite not having seen each other in many months, it feels immediately natural. People describe it as immediately feeling &#8220;like the old times&#8221; and &#8220;like you&#8217;d just seen each other a few days ago&#8221;. So frequency is a good signal for strength of tie, but it doesn&#8217;t always show us the full picture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johnlabriola</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8043</link>
		<dc:creator>johnlabriola</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8043</guid>
		<description><![CDATA[Hey Paul,

Great piece, while I have read about thsi elsewhere, I think you did a good job consolidating some good data references and putting it in a language most people can understand. I sent it to a few stakeholders and other partners from a project I am working on.

I am the position of, as Chris Avore put it, addressing the pipe dream. About more than year ago my organization brought an out of the box social enterprise solution thinking it would address their needs. Well it kinda did, but not really. I was hired with some other people about 6 months ago to try to understand better our users. We learned a lot about their real life social interactions and are now starting to educating our business partners on social interaction design. For example we were talking about the subject of ties, and how we should enhance the strong ties (which we don&#039;t do at all) and build up the weak ones (which we kinda do a little).

Our problem now is that we must customize the enterprise tool or build extra custom components to do what we need. So in some ways I agree with Chris Avore, many enterprise companies are buying products and expecting amazing results. But that is not happening. If their smart they can get a good team int there to come in and straighten things out.

I think that it is up to us to educate the enterprises as well as the enterprise solution providers. I am hoping that the company that provider our software will look at what we&#039;re doing to learn how they can adopt their software. It may be a pipe dream, but I can at least hope.]]></description>
		<content:encoded><![CDATA[<p>Hey Paul,</p>
<p>Great piece, while I have read about thsi elsewhere, I think you did a good job consolidating some good data references and putting it in a language most people can understand. I sent it to a few stakeholders and other partners from a project I am working on.</p>
<p>I am the position of, as Chris Avore put it, addressing the pipe dream. About more than year ago my organization brought an out of the box social enterprise solution thinking it would address their needs. Well it kinda did, but not really. I was hired with some other people about 6 months ago to try to understand better our users. We learned a lot about their real life social interactions and are now starting to educating our business partners on social interaction design. For example we were talking about the subject of ties, and how we should enhance the strong ties (which we don&#8217;t do at all) and build up the weak ones (which we kinda do a little).</p>
<p>Our problem now is that we must customize the enterprise tool or build extra custom components to do what we need. So in some ways I agree with Chris Avore, many enterprise companies are buying products and expecting amazing results. But that is not happening. If their smart they can get a good team int there to come in and straighten things out.</p>
<p>I think that it is up to us to educate the enterprises as well as the enterprise solution providers. I am hoping that the company that provider our software will look at what we&#8217;re doing to learn how they can adopt their software. It may be a pipe dream, but I can at least hope.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrbutler</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8044</link>
		<dc:creator>chrbutler</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8044</guid>
		<description><![CDATA[Paul, 

I definitely agree--frequency is only one piece of the puzzle. In fact, just yesterday I received a phone call from someone I would have put in the very infrequent category and whom I&#039;d actually never spoken to directly before (only via email/Twitter so far). He wanted some advice and felt that a direct conversation was the best approach, even though our relationship had never included that kind of contact before. I was surprised by his call, and then as we got to talking a bit more, even more surprised by my feeling that talking to this person over the phone was so unusual--especially when 10-15 years ago phone would probably have been the primary contact method!

Chris]]></description>
		<content:encoded><![CDATA[<p>Paul, </p>
<p>I definitely agree&#8211;frequency is only one piece of the puzzle. In fact, just yesterday I received a phone call from someone I would have put in the very infrequent category and whom I&#8217;d actually never spoken to directly before (only via email/Twitter so far). He wanted some advice and felt that a direct conversation was the best approach, even though our relationship had never included that kind of contact before. I was surprised by his call, and then as we got to talking a bit more, even more surprised by my feeling that talking to this person over the phone was so unusual&#8211;especially when 10-15 years ago phone would probably have been the primary contact method!</p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steveportigal</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8045</link>
		<dc:creator>steveportigal</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8045</guid>
		<description><![CDATA[Great post, well explained and provocative. Reminds me that many years ago we did fieldwork with French mobile phone users and talked about technology and social connectivity. We got some very clear explanations about the difference between &quot;copains&quot; (i.e., buddies) and &quot;amis&quot; (friends), where an ami was for life and where one had far fewer amis than copains. Our French client had a lot of trouble understanding, then, our Japanese respondents who were (at that time, using Print Club, those small stickers) aggregating large numbers of shallow relationships they called &quot;friends.&quot; So you have the nomenclature issue, and you have the cultural issue. Even talking about it was tough, if the frame being illustrated didn&#039;t match the existing frame.]]></description>
		<content:encoded><![CDATA[<p>Great post, well explained and provocative. Reminds me that many years ago we did fieldwork with French mobile phone users and talked about technology and social connectivity. We got some very clear explanations about the difference between &#8220;copains&#8221; (i.e., buddies) and &#8220;amis&#8221; (friends), where an ami was for life and where one had far fewer amis than copains. Our French client had a lot of trouble understanding, then, our Japanese respondents who were (at that time, using Print Club, those small stickers) aggregating large numbers of shallow relationships they called &#8220;friends.&#8221; So you have the nomenclature issue, and you have the cultural issue. Even talking about it was tough, if the frame being illustrated didn&#8217;t match the existing frame.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kmerhi</title>
		<link>http://boxesandarrows.com/designing-for-social-interaction/#comment-8046</link>
		<dc:creator>kmerhi</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/designing-for-social-interaction/#comment-8046</guid>
		<description><![CDATA[Fantastic post! Thought provoking.

In the comment stream above, Chris Butler touched up on the frequency of communication as being another attribute of a relationship.  Steve Portigal mentions how difficult it is even to describe these relationships in simple terminology (Copains et Amis).

It is definitely helpful to look at individuals in our social networks as nodes and their relationships as bonds that can be described with a set of attribute; but this type of predicate logic may yield to undesirable results - Just like in the real world.  Example: the realization that the bonds of a particular relationship are stronger in one direction and weaker in the other.

How can we address these types of issues when designing online interactions. Do we simply rely on the individuals to &quot;attribute&quot; the type of relationship? Do we let the system provide hints on the state of that relationship? Food for thought, no doubt.

Thanks for sharing,
Khalid]]></description>
		<content:encoded><![CDATA[<p>Fantastic post! Thought provoking.</p>
<p>In the comment stream above, Chris Butler touched up on the frequency of communication as being another attribute of a relationship.  Steve Portigal mentions how difficult it is even to describe these relationships in simple terminology (Copains et Amis).</p>
<p>It is definitely helpful to look at individuals in our social networks as nodes and their relationships as bonds that can be described with a set of attribute; but this type of predicate logic may yield to undesirable results &#8211; Just like in the real world.  Example: the realization that the bonds of a particular relationship are stronger in one direction and weaker in the other.</p>
<p>How can we address these types of issues when designing online interactions. Do we simply rely on the individuals to &#8220;attribute&#8221; the type of relationship? Do we let the system provide hints on the state of that relationship? Food for thought, no doubt.</p>
<p>Thanks for sharing,<br />
Khalid</p>
]]></content:encoded>
	</item>
</channel>
</rss>
