<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" gd:etag="W/&quot;CkEESX4-eyp7ImA9WhBbEEw.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534</id><updated>2013-05-08T12:56:48.053+02:00</updated><category term="google+" /><category term="control" /><category term="multitasking" /><category term="seth godin" /><category term="news" /><category term="enterprise 2.0" /><category term="collaboration" /><category term="free" /><category term="measurement" /><category term="stickiness" /><category term="robot" /><category term="customer" /><category term="strategy" /><category term="privacy" /><category term="analytics" /><category term="algorithms" /><category term="paperless" /><category term="posterous" /><category term="linkedin" /><category term="social learning" /><category term="virtual world" /><category term="sustainability" /><category term="social bookmarking" /><category term="push" /><category term="ted talks" /><category term="rss" /><category term="video" /><category term="email" /><category term="social media in de praktijk" /><category term="serendipity" /><category term="cluetrain manifesto" /><category term="slack" /><category term="requirements management" /><category term="davenport" /><category term="website design" /><category term="top task management" /><category term="mobileweb" /><category term="workplace" /><category term="work" /><category term="extranet" /><category term="liveblogging" /><category term="arie de geus" /><category term="trailfire" /><category term="engagement" /><category term="IBM" /><category term="facebook" /><category term="HRM" /><category term="reading" /><category term="visualization" /><category term="socialnow" /><category term="gigaom" /><category term="information overload" /><category term="lego" /><category term="whiteboard" /><category term="workshop" /><category term="williams" /><category term="downtime" /><category term="userinteraction" /><category term="success" /><category term="outliers" /><category term="information" /><category term="hierarchy" /><category term="policy" /><category term="definition" /><category term="intra13" /><category term="government" /><category term="jacob morgan" /><category term="turkle" /><category term="philosophy" /><category term="b2b" /><category term="techtalks" /><category term="literacy" /><category term="networking" /><category term="wordpress" /><category term="congres intranet" /><category term="dunbar" /><category term="interview" /><category term="feedreader" /><category term="mobile intranet" /><category term="content manager" /><category term="welcome" /><category term="epaper" /><category term="lindastone" /><category term="information auditing" /><category term="innovation" /><category term="telecommuting" /><category term="b2c" /><category term="marketing" /><category term="design" /><category term="socmedprak" /><category term="governance" /><category term="web 2.0 summit" /><category term="intra12" /><category term="benchmarking" /><category term="epic" /><category term="project" /><category term="information abundance" /><category term="blogging" /><category term="the information" /><category term="google" /><category term="congres webredactie" /><category term="feeds" /><category term="technorati" /><category term="education" /><category term="technology" /><category term="podcast" /><category term="information architecture" /><category term="social software" /><category term="chaos theory" /><category term="unilever" /><category term="ibf" /><category term="customers" /><category term="requirements engineering" /><category term="christmas" /><category term="tumblr" /><category term="social sites" /><category term="inspiration" /><category term="leadership" /><category term="creativity" /><category term="human resources" /><category term="personal knowledge management" /><category term="language technology" /><category term="blog action day" /><category term="sharepoint" /><category term="jane mcconnell" /><category term="gamification" /><category term="asking" /><category term="water" /><category term="content management" /><category term="dialogue" /><category term="what technology wants" /><category term="opensource" /><category term="predictionmarket" /><category term="survey" /><category term="best practice" /><category term="gleick" /><category term="mckinsey" /><category term="voice" /><category term="services" /><category term="productivity" /><category term="future of work" /><category term="mindstorms" /><category term="roi" /><category term="learning" /><category term="adoption" /><category term="paper" /><category term="the tipping point" /><category term="navigation" /><category term="mary meeker" /><category term="frankwatching" /><category term="deployment" /><category term="macrowikinomics" /><category term="newspaper" /><category term="implementation" /><category term="indexing" /><category term="meeting" /><category term="accountant" /><category term="millenials" /><category term="fashion" /><category term="question" /><category term="telework" /><category term="publishing" /><category term="peter senge" /><category term="Darwin Engine" /><category term="wikipedia" /><category term="knowledge worker" /><category term="copywriting" /><category term="alcatel" /><category term="epidemics" /><category term="consultant" /><category term="wonder" /><category term="twitter" /><category term="compliance" /><category term="content marketing" /><category term="social media" /><category term="erp" /><category term="numbers" /><category term="entopic" /><category term="writing" /><category term="foursquare" /><category term="management" /><category term="filtering" /><category term="human" /><category term="scheduling" /><category term="mobile" /><category term="hnw" /><category term="hagel" /><category term="socioprise" /><category term="finance" /><category term="html5" /><category term="web" /><category term="leatherman" /><category term="document management" /><category term="gladwell" /><category term="jive" /><category term="generation y" /><category term="global digital workplace report" /><category term="comic" /><category term="hyves" /><category term="guest lecture" /><category term="printing" /><category term="microblogging" /><category term="salesforce" /><category term="big data" /><category term="presentation" /><category term="trends" /><category term="km" /><category term="pkm" /><category term="digital literacy" /><category term="location" /><category term="congres sharepoint" /><category term="iphone" /><category term="physical world" /><category term="intelligence" /><category term="michael sampson" /><category term="masscollaboration" /><category term="web 2.0" /><category term="sales" /><category term="cluetrain" /><category term="archiving" /><category term="realtime" /><category term="nba-vrc" /><category term="HR" /><category term="knowledge sharing" /><category term="consultancy" /><category term="the living company" /><category term="making it all work" /><category term="review" /><category term="web 3.0" /><category term="guideline" /><category term="laptop" /><category term="james robertson" /><category term="Rowling" /><category term="future" /><category term="web editor" /><category term="corporation" /><category term="swarm" /><category term="business" /><category term="gerry mcgovern" /><category term="knowledge management" /><category term="Google Reader" /><category term="bad" /><category term="security" /><category term="storytelling" /><category term="semantic web" /><category term="tapscott" /><category term="commenting" /><category term="ted" /><category term="role" /><category term="eddy vaassen" /><category term="cloud" /><category term="net generation" /><category term="kennismanagement" /><category term="the netherlands" /><category term="e20s" /><category term="enterprise 2.0 summit" /><category term="semanticweb" /><category term="i-fetch" /><category term="android" /><category term="social networks" /><category term="open innovation" /><category term="people" /><category term="digital native" /><category term="transparency" /><category term="conversation" /><category term="scanning" /><category term="concepts" /><category term="market" /><category term="we" /><category term="expertise" /><category term="fun" /><category term="plm" /><category term="requirements" /><category term="crowdsourcing" /><category term="journalism" /><category term="filter bubble" /><category term="mind" /><category term="yahoo" /><category term="wiki" /><category term="attention" /><category term="trust" /><category term="document engineering" /><category term="social business" /><category term="organization" /><category term="persuasion" /><category term="apple" /><category term="user adoption" /><category term="tablet" /><category term="reputation" /><category term="nrc" /><category term="IT" /><category term="change" /><category term="ipad" /><category term="map" /><category term="thiememeulenhoff" /><category term="benchmark" /><category term="knowledge mapping" /><category term="environment" /><category term="conference" /><category term="crm" /><category term="complexity" /><category term="press" /><category term="forum" /><category term="Lotus" /><category term="paperdigital" /><category term="schulz" /><category term="power of pull" /><category term="2012" /><category term="instagram" /><category term="social networking" /><category term="metrics" /><category term="natural language search" /><category term="Potter" /><category term="internet" /><category term="the fifth discipline" /><category term="open" /><category term="knowledge work" /><category term="file" /><category term="recruitment" /><category term="intranet" /><category term="digital workplace" /><category term="prediction" /><category term="millennial" /><category term="pull" /><category term="product lifecycle management" /><category term="database" /><category term="thinking" /><category term="car" /><category term="it flower" /><category term="sharing" /><category term="gtd" /><category term="influencing" /><category term="idea" /><category term="wrong" /><category term="vision" /><category term="office" /><category term="birthday" /><category term="seely brown" /><category term="vacation" /><category term="process" /><category term="steptwo" /><category term="culture" /><category term="social intranet" /><category term="streaming" /><category term="expertise location" /><category term="BPM" /><category term="communication" /><category term="communities" /><category term="monitoring" /><category term="audit" /><category term="dutchopen" /><category term="instant messaging" /><category term="book" /><category term="blog" /><category term="senge" /><category term="social now" /><category term="life" /><category term="listening" /><category term="mindmapping" /><category term="digitalization" /><category term="passion" /><category term="secretary" /><category term="economics" /><category term="enterprise content management" /><category term="blogger" /><category term="information management" /><category term="thoughtleader" /><category term="oce" /><category term="natural language" /><category term="structure" /><category term="search" /><category term="microsoft" /><category term="slideshare" /><category term="bookmarking" /><category term="model" /><category term="failure" /><category term="thinkplace" /><category term="data" /><category term="controlling" /><category term="wikinomics" /><category term="accounting" /><title>infoarch</title><subtitle type="html">About my experiences
as a senior consultant intranet/social media</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://info-architecture.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>915</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/Infoarch" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="infoarch" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;Ak8ESX05cCp7ImA9WhBUE0Q.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-7926766091201389847</id><published>2013-05-01T11:00:00.000+02:00</published><updated>2013-05-01T11:00:08.328+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-01T11:00:08.328+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="personal knowledge management" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge management" /><category scheme="http://www.blogger.com/atom/ns#" term="digital literacy" /><category scheme="http://www.blogger.com/atom/ns#" term="literacy" /><title>How to help others become digitally literate?</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-OQ1VKKNgAOg/UXmbceL53II/AAAAAAAAPow/NWU4_zra4Ik/s1600/photo+(3).JPG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="149" src="http://2.bp.blogspot.com/-OQ1VKKNgAOg/UXmbceL53II/AAAAAAAAPow/NWU4_zra4Ik/s200/photo+(3).JPG" width="200" /&gt;&lt;/a&gt;&lt;/div&gt;
In my previous post I asked my readers how they help other’s understand the potential of new ways of working? How can we teach and show others what digital literacy is?&lt;br /&gt;&lt;br /&gt;I wanted to share one idea I use to teach others to work out loud. What I always try to do is relate to the primary processes of the organization or, even better, to the primary work processes of the person I’m helping. He/she is working in a certain way and used to that. For instance, he uses email to send around documents and get feedback on them. Or he sends out an email to a group of people to get ideas about a certain topic. Starting there I ask that person what he/she likes about working that way. And what he/she dislikes about it. Then I ask how he/she thinks the dislikes could be solved. My experience is: most people don’t think they can be solved. They just cope with the issues and carry on. If this is the case, I show them how I do the same job with a certain tool. I tell them why I work in that way and why I like to work that way. And I stop there. In most cases they say: I didn’t know there were tools like that, could you help me get/use them as well? In some cases they continue to work they way the way. And that’s OK. I can’t force them to work in another way. I just hope they remember there is another way and try it some other time.&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=-wcy0khiMhc:p8_Jp6vykao:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=-wcy0khiMhc:p8_Jp6vykao:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=-wcy0khiMhc:p8_Jp6vykao:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=-wcy0khiMhc:p8_Jp6vykao:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=-wcy0khiMhc:p8_Jp6vykao:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=-wcy0khiMhc:p8_Jp6vykao:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=-wcy0khiMhc:p8_Jp6vykao:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=-wcy0khiMhc:p8_Jp6vykao:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=-wcy0khiMhc:p8_Jp6vykao:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/7926766091201389847?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/7926766091201389847?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/05/how-to-help-others-become-digitally.html" title="How to help others become digitally literate?" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-OQ1VKKNgAOg/UXmbceL53II/AAAAAAAAPow/NWU4_zra4Ik/s72-c/photo+(3).JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;DkUEQXk8eyp7ImA9WhBUEk8.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-7530749244996012193</id><published>2013-04-29T10:30:00.000+02:00</published><updated>2013-04-29T10:30:00.773+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-04-29T10:30:00.773+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="pkm" /><category scheme="http://www.blogger.com/atom/ns#" term="filtering" /><category scheme="http://www.blogger.com/atom/ns#" term="personal knowledge management" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge management" /><category scheme="http://www.blogger.com/atom/ns#" term="digital literacy" /><category scheme="http://www.blogger.com/atom/ns#" term="literacy" /><title>Digital Illiteracy</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-laVAJVqMI2w/UXmalkYkH2I/AAAAAAAAPok/8SLeLNuEddE/s1600/photo+(2).JPG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="149" src="http://2.bp.blogspot.com/-laVAJVqMI2w/UXmalkYkH2I/AAAAAAAAPok/8SLeLNuEddE/s200/photo+(2).JPG" width="200" /&gt;&lt;/a&gt;&lt;/div&gt;
Some time ago my friend &lt;a href="http://twitter.com/anadatagirl"&gt;Ana Silva&lt;/a&gt; wrote a&lt;a href="https://artlifework.wordpress.com/2013/02/02/the-importance-of-digital-literacy-in-social-tools-adoption/"&gt;n interesting post about a very important topic: digital literacy&lt;/a&gt;. Please read her post (and the comments). The main point of her post is that we should not assume people get the internet or get social media and will start working out in the open by themselves. Some do, but many need to be helped. We have to teach them, step-by-step, to be digitally literate. This is hard work.&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I’ve written about this topic quite a bit as well using a different term: &lt;a href="http://info-architecture.blogspot.nl/search/label/knowledge%20management"&gt;‘personal knowledge management’&lt;/a&gt;. How do we become more productive working out in the open and using the new (and old) social concepts and tools?&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
As I wrote in a comment on Ana’s post, this is not a small issue. Recently the Dutch newspaper I read (&lt;a href="http://nrc.nl/"&gt;nrc.nl&lt;/a&gt;) ran an extra section of the newspaper about ‘searching in a smarter way on the internet’ (Dutch: Slimmer zoeken op internet’). Very interesting stuff with all kinds of tips &amp;amp; tricks to improve the way you use the internet. But what struck me is the economic implication of digital illiteracy. The University of Twente published a study “Ctrl Alt Delete” and they found that 5.3% of our work time is lost due to digital illiteracy. That’s 10 billion euro’s per year in The Netherlands alone! That’s a lot of money. And there’s a lot of work to do.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NkHkpGMN7ws:4DxUKP_h__o:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NkHkpGMN7ws:4DxUKP_h__o:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NkHkpGMN7ws:4DxUKP_h__o:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=NkHkpGMN7ws:4DxUKP_h__o:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NkHkpGMN7ws:4DxUKP_h__o:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=NkHkpGMN7ws:4DxUKP_h__o:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NkHkpGMN7ws:4DxUKP_h__o:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NkHkpGMN7ws:4DxUKP_h__o:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=NkHkpGMN7ws:4DxUKP_h__o:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/7530749244996012193?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/7530749244996012193?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/04/digital-illiteracy.html" title="Digital Illiteracy" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-laVAJVqMI2w/UXmalkYkH2I/AAAAAAAAPok/8SLeLNuEddE/s72-c/photo+(2).JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;D08EQ3gzeSp7ImA9WhBVGUo.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-2267576251227088840</id><published>2013-04-26T13:30:00.000+02:00</published><updated>2013-04-26T13:30:02.681+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-04-26T13:30:02.681+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="socialnow" /><category scheme="http://www.blogger.com/atom/ns#" term="gamification" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge work" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise 2.0" /><category scheme="http://www.blogger.com/atom/ns#" term="social business" /><title>Talks about gamification, money and the future of work #socialnow</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://3.bp.blogspot.com/-PEWXAYiKNP0/UXmXV6rlu-I/AAAAAAAAPoU/A22d1Xt93S0/s1600/photo+(1).JPG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://3.bp.blogspot.com/-PEWXAYiKNP0/UXmXV6rlu-I/AAAAAAAAPoU/A22d1Xt93S0/s200/photo+(1).JPG" width="149" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;o:OfficeDocumentSettings&gt;
  &lt;o:AllowPNG/&gt;
 &lt;/o:OfficeDocumentSettings&gt;
&lt;/xml&gt;&lt;![endif]--&gt;

&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;w:WordDocument&gt;
  &lt;w:View&gt;Normal&lt;/w:View&gt;
  &lt;w:Zoom&gt;0&lt;/w:Zoom&gt;
  &lt;w:TrackMoves/&gt;
  &lt;w:TrackFormatting/&gt;
  &lt;w:PunctuationKerning/&gt;
  &lt;w:ValidateAgainstSchemas/&gt;
  &lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
  &lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
  &lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
  &lt;w:DoNotPromoteQF/&gt;
  &lt;w:LidThemeOther&gt;EN-US&lt;/w:LidThemeOther&gt;
  &lt;w:LidThemeAsian&gt;JA&lt;/w:LidThemeAsian&gt;
  &lt;w:LidThemeComplexScript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;
  &lt;w:Compatibility&gt;
   &lt;w:BreakWrappedTables/&gt;
   &lt;w:SnapToGridInCell/&gt;
   &lt;w:WrapTextWithPunct/&gt;
   &lt;w:UseAsianBreakRules/&gt;
   &lt;w:DontGrowAutofit/&gt;
   &lt;w:SplitPgBreakAndParaMark/&gt;
   &lt;w:EnableOpenTypeKerning/&gt;
   &lt;w:DontFlipMirrorIndents/&gt;
   &lt;w:OverrideTableStyleHps/&gt;
   &lt;w:UseFELayout/&gt;
  &lt;/w:Compatibility&gt;
  &lt;m:mathPr&gt;
   &lt;m:mathFont m:val="Cambria Math"/&gt;
   &lt;m:brkBin m:val="before"/&gt;
   &lt;m:brkBinSub m:val="&amp;#45;-"/&gt;
   &lt;m:smallFrac m:val="off"/&gt;
   &lt;m:dispDef/&gt;
   &lt;m:lMargin m:val="0"/&gt;
   &lt;m:rMargin m:val="0"/&gt;
   &lt;m:defJc m:val="centerGroup"/&gt;
   &lt;m:wrapIndent m:val="1440"/&gt;
   &lt;m:intLim m:val="subSup"/&gt;
   &lt;m:naryLim m:val="undOvr"/&gt;
  &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="276"&gt;
  &lt;w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/&gt;
  &lt;w:LsdException Locked="false" QFormat="true" Name="heading 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 7"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 8"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 9"/&gt;
  &lt;w:LsdException Locked="false" Priority="0" Name="header"/&gt;
  &lt;w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/&gt;
  &lt;w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/&gt;
  &lt;w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/&gt;
  &lt;w:LsdException Locked="false" Priority="0" Name="Body Text"/&gt;
  &lt;w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/&gt;
  &lt;w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/&gt;
  &lt;w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/&gt;
  &lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/&gt;
  &lt;w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/&gt;
  &lt;w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/&gt;
  &lt;w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/&gt;
  &lt;w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/&gt;
  &lt;w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/&gt;
  &lt;w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/&gt;
  &lt;w:LsdException Locked="false" Priority="37" Name="Bibliography"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/&gt;
 &lt;/w:LatentStyles&gt;
&lt;/xml&gt;&lt;![endif]--&gt;

&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
 /* Style Definitions */
table.MsoNormalTable
 {mso-style-name:"Table Normal";
 mso-tstyle-rowband-size:0;
 mso-tstyle-colband-size:0;
 mso-style-noshow:yes;
 mso-style-priority:99;
 mso-style-parent:"";
 mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
 mso-para-margin:0cm;
 mso-para-margin-bottom:.0001pt;
 mso-pagination:widow-orphan;
 font-size:12.0pt;
 font-family:Cambria;
 mso-ascii-font-family:Cambria;
 mso-ascii-theme-font:minor-latin;
 mso-hansi-font-family:Cambria;
 mso-hansi-theme-font:minor-latin;}
&lt;/style&gt;
&lt;![endif]--&gt;



&lt;!--StartFragment--&gt;

&lt;br /&gt;
This is my final post about the &lt;a href="http://socialnow.org/"&gt;SocialNow conference 2013&lt;/a&gt;. In this post I’d like to share some highlights from four talks. Two were about gamification, one was about money and one about the future of work.&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;Gamification&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
The presentations about gamification by &lt;a href="http://twitter.com/daverage"&gt;Andrzej Marczewski&lt;/a&gt; (of Cap Gemini) and &lt;a href="http://twitter.com/carvalhop"&gt;Paulo de Carvalho&lt;/a&gt; (of Vodafone) were very interesting. I really enjoyed how these presentations were placed back-to-back. Andrzey gave &lt;a href="http://www.slideshare.net/daverage/social-now-extended"&gt;a general but very good introduction to gamification&lt;/a&gt;. He talked about the what, why and how. I really enjoyed how he also talked about cheating and gamification.&lt;/div&gt;
&lt;div&gt;
Paulo talked about his experiences with gamification inside Vodafone. He gave a detailled overview of how they applied gamification to certain business processes and how they deeply thought about the right metrics and incentives for the game to be useful.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Costs&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://twitter.com/ananeves"&gt;Ana Neves&lt;/a&gt; gave a short presentation about the cost of social tools in the enterprise. Don't focus on the license fees only. The Total Cost of Ownership for Social tools is just as important as for other tools. Even een free internal tool is never really free. And make sure you pay attention to adoption costs as well. I liked how Ana also addressed the cost of not implementing social tools inside your organization.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Future of work&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://twitter.com/stoweboyd"&gt;Stowe Boyd&lt;/a&gt; gave the closing keynote at the conference about the future of work in a social world. He made some really interesting remarks about the shift from collaboration to cooperation. I was planning on sharing my notes about this talk, but just saw &lt;a href="http://artlifework.wordpress.com/2013/04/25/stowe-boyd-on-why-the-future-of-work-is-cooperative/"&gt;Ana Silva has a good blogpost summarizing Stowe's talk&lt;/a&gt;. So, please go ahead and read her post!&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;Concluding&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
The SocialNow conference was very interesting. I thought is was even better than last year. This was due to a great panel (&lt;a href="http://twitter.com/anadatagirl"&gt;Ana Silva&lt;/a&gt;, &lt;a href="http://twitter.com/philahill"&gt;Phil Hill&lt;/a&gt; and &lt;a href="http://twitter.com/pedrocustodio"&gt;Pedro Custodio&lt;/a&gt;). They did a great job asking questions to the vendors and opening up the discussion with the rest of the participants. The participants had great questions as well. It was a true learning experience for this reason. There were deep and fundamental discussions about all aspects of internal social design, features, implementation, adoption, etc. Great stuff!&lt;/div&gt;
&lt;div&gt;
Furthermore I see some disappointment in the field. People have been at the break of the Enterprise 2.0 field are evaluating the past year's and wondering what the future of the enterprise 2.0 and social business market and practice will look like.&lt;br /&gt;Most organizations doing internal social hardly every have one platform with all the functionality. Because the SocialNow conference is built around vendor presentations, I'm wondering how we can bring this fragmented (and more realistic?) world in the conference. Could it be that some vendors should team up and do a presentation together?&lt;/div&gt;
&lt;div&gt;
And once again we see innovation happens on the edges. Some vendors 'simply' copy the good social tools on the internet and make internal versions of them. But there are also vendors that think differently and challenge the status quo of tools and... business.&lt;br /&gt;&lt;br /&gt;&lt;!--EndFragment--&gt;&lt;/div&gt;
&lt;div&gt;
I really enjoyed SocialNow and hope to meet you there next year!&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=TMXAcqAmdZM:7GV-aa9nt-g:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=TMXAcqAmdZM:7GV-aa9nt-g:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=TMXAcqAmdZM:7GV-aa9nt-g:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=TMXAcqAmdZM:7GV-aa9nt-g:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=TMXAcqAmdZM:7GV-aa9nt-g:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=TMXAcqAmdZM:7GV-aa9nt-g:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=TMXAcqAmdZM:7GV-aa9nt-g:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=TMXAcqAmdZM:7GV-aa9nt-g:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=TMXAcqAmdZM:7GV-aa9nt-g:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/2267576251227088840?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/2267576251227088840?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/04/talks-about-gamification-money-and.html" title="Talks about gamification, money and the future of work #socialnow" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-PEWXAYiKNP0/UXmXV6rlu-I/AAAAAAAAPoU/A22d1Xt93S0/s72-c/photo+(1).JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;CUUESX04eip7ImA9WhBVGUs.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-7858137022619420252</id><published>2013-04-26T10:00:00.000+02:00</published><updated>2013-04-26T10:00:08.332+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-04-26T10:00:08.332+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="socialnow" /><category scheme="http://www.blogger.com/atom/ns#" term="technology" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise 2.0" /><category scheme="http://www.blogger.com/atom/ns#" term="social business" /><title>Enterprise 2.0 tool vendors at SocialNow #socialnow </title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-UZjIOLp3FiY/UXmQl-waplI/AAAAAAAAPoE/iukP4P-5IYo/s1600/photo.JPG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://4.bp.blogspot.com/-UZjIOLp3FiY/UXmQl-waplI/AAAAAAAAPoE/iukP4P-5IYo/s200/photo.JPG" width="149" /&gt;&lt;/a&gt;&lt;/div&gt;
Now for some highlights from the vendor presentations in my second post about the &lt;a href="http://socialnow.org/"&gt;SocialNow&lt;/a&gt; conference.&amp;nbsp;&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://twitter.com/foulders"&gt;Foulders&lt;/a&gt; has not been launched yet, but presented their concept and tool at the conference. They want to start where the users are: their email inbox. And most people have multiple inboxes. So they provide a super dashboard over all your inboxes and help you organize the tasks that come out of your email. They use language technology to help the user quickly and efficiently organize emails in tasks and folders.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;a href="https://podio.com/"&gt;Podio&lt;/a&gt;&amp;nbsp;was at the conference for the second year. I didn’t hear anything new with respect to the product. There will be a big update to the product in the very near future. Podio is still an impressive product that wants to help us overcome email and make spreadsheets better. Spreadsheets can easily be turned into open and smart Podio apps to improve collaboration and communication around them.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Another new tool to SocialNow is &lt;a href="http://wordpress.org/"&gt;Wordpress&lt;/a&gt; with the &lt;a href="http://p2theme.com/"&gt;P2&lt;/a&gt; extension. Wordpress isn’t a new tool, of course. It’s an impressive and widely used platform. The P2 extension makes it very easy for organizations to set up an internal social networking, microblogging and document sharing platform. I really like Wordpress with P2, but I’m biased, because we have developed intranets based on Wordpress and P2.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://xwiki.org/"&gt;Xwiki&lt;/a&gt; was at SocialNow for the second time. Xwiki is also, like Wordpress, an open-source platform. I saw some new things in Xwiki that I hadn’t seen before. One, you can drag-and-drop documents to wiki and it has a document viewer so you can view the document without having to open it, this also works for video.&lt;/div&gt;
&lt;div&gt;
Secondly, they add ‘track changes’ and commenting features to wiki’s. So it shows edits and comments in the way you see them in MS Word for instance. As an owner of the page you can accept and reject changes.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://evernote.com/business/"&gt;Evernote for Business&lt;/a&gt; presented their concept. If you know Evernote, you know Evernote for business. The pricing is pretty steep: 10 euro per user per month. They focus on small and medium-sized businesses. I like they way they clearly said who the product if for and who it isn’t for and what kind of things work in Evernote and don’t. For instance, for task management they pointed to other kinds of tools.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://sharepoint.microsoft.com/"&gt;Sharepoint&lt;/a&gt; revisited SocialNow, but with a different approach. Last year, Microsoft had just acquired Yammer, but it was unclear what this would mean for the Sharepoint platform. Now it (slowly) is becoming clear. This year’s presentation was ‘only’ about &lt;a href="http://www.yammer.com/"&gt;Yammer&lt;/a&gt; and hardly talked about Sharepoint. Newsgator was not mentioned at all. It was said that Yammer will be the social layer for Sharepoint. And they are working on integrating Yammer with  Sharepoint Online and Office365.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://spreadd.com/invites/"&gt;Spreadd&lt;/a&gt; was at SocialNow and clearly improved it’s user interface. I like the bold way they address modern knowledge worker issues. Do users really search for stuff or would they like to get things pushed to them, do users really maintain their profile or should it be done automatically? Spreadd integrates all the services employees use and publishes the information that changes to an activity stream (taking the security controls into account). Spreadd has not officially launched but is being tested by a large organization.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://www.zyncro.com/"&gt;Zyncro&lt;/a&gt; is an interesting internal social networking platform with all the features you would an internal social platform has. I didn’t see any new features compared to last year. But the language detection and translation functionality is impressive and smart. I’m going to look into Zyncro more deeply in the near future.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://www.yoolink.fr/"&gt;Yoolink&lt;/a&gt; was a new vendor at SocialNow. They are a French internal social network vendor. They also have a mobile version and support SSO. Interestingly they also provide a collaborative whiteboard, so employees can share drawings and make them together.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
The vendor presentations are the core of SocialNow. All-in-all I think the state of internal social technology is impressive. I like the way some are really trying to innovate on the edges while others try to provide Facebook- and Twitter-like functionality inside the organization. I do wonder though how some position themselves with respect to other vendors. For instance, Yoolink  and Zyncro are interesting platforms, but how do they compare from Jive and Sharepoint/Yammer? Is it price, company size, features? Zyncro for one acknowledge they currently are fit for mid-sized and smaller companies. And Yoolink says they do not (want to) compete with Jive.&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
One thing that continues to surprise me in vendor presentations is how many struggle to really relate to the situation of the customer. In this case Cablinc. Many mention the situation of Cablinc in the first part of the presentation and slide to a regular presentation marketing the product and features. And furthermore, the vendors hardly tell Cablinc what value they will be getting from using the platform. I know the presentations have to be short, but still.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=P-L2Rga51ec:HnYCpFJRN-I:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=P-L2Rga51ec:HnYCpFJRN-I:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=P-L2Rga51ec:HnYCpFJRN-I:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=P-L2Rga51ec:HnYCpFJRN-I:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=P-L2Rga51ec:HnYCpFJRN-I:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=P-L2Rga51ec:HnYCpFJRN-I:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=P-L2Rga51ec:HnYCpFJRN-I:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=P-L2Rga51ec:HnYCpFJRN-I:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=P-L2Rga51ec:HnYCpFJRN-I:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/7858137022619420252?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/7858137022619420252?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/04/enterprise-20-tool-vendors-at-socialnow.html" title="Enterprise 2.0 tool vendors at SocialNow #socialnow " /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-UZjIOLp3FiY/UXmQl-waplI/AAAAAAAAPoE/iukP4P-5IYo/s72-c/photo.JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;CkANQ3w9eyp7ImA9WhBVGU8.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-3109117983578961305</id><published>2013-04-25T22:13:00.001+02:00</published><updated>2013-04-25T22:13:12.263+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-04-25T22:13:12.263+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="socialnow" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise 2.0" /><category scheme="http://www.blogger.com/atom/ns#" term="adoption" /><category scheme="http://www.blogger.com/atom/ns#" term="social business" /><title>Notes and learnings from the SocialNow conference 2013 #socialnow </title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-dwRlEWCv7y8/UXmOR3rmizI/AAAAAAAAPn0/v_SlB2GuqQ8/s1600/photo.JPG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://4.bp.blogspot.com/-dwRlEWCv7y8/UXmOR3rmizI/AAAAAAAAPn0/v_SlB2GuqQ8/s200/photo.JPG" width="149" /&gt;&lt;/a&gt;&lt;/div&gt;
The 2nd edition of &lt;a href="http://socialnow.org/"&gt;the SocialNow conference&lt;/a&gt; was held in the beautiful city of Lisbon. &lt;a href="http://info-architecture.blogspot.nl/2012/07/chosing-right-social-tool-reflecting-on.html"&gt;As you may remember&lt;/a&gt; SocialNow is a unique conference. The conference is organized by &lt;a href="http://twitter.com/ananeves"&gt;Ana Neves&lt;/a&gt; of &lt;a href="http://knowman.pt/"&gt;KnowMan&lt;/a&gt;. The conference is about helping organizations compare and choose internal social tools. Several Enterprise 2.0 tool vendors have to present their tool relating to the situation of a &lt;a href="http://socialnow.org/cablinc/"&gt;fictitious company&lt;/a&gt; and its issues with collaborative project work and topic-based knowledge sharing. The program is complemented with keynotes from leading experts in the field. I really enjoyed this edition of SocialNow and thought it was even better than last year. I’ll share my notes and learnings from the conference in several posts. This is post nr 1. BTW: You can find a Storify by Paul Corney of &lt;a href="http://storify.com/PaulJCorney/social-now-2013-lisboa-a-unique-event-where-compan?utm_content=storify-pingback&amp;amp;awesm=sfy.co_hI1Y&amp;amp;utm_campaign=&amp;amp;utm_source=t.co&amp;amp;utm_medium=sfy.co-twitter"&gt;day 1&lt;/a&gt; and &lt;a href="http://storify.com/PaulJCorney/socialnow-lisboa-day-two"&gt;day 2&lt;/a&gt; here.&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;Challenges&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
&lt;a href="http://twitter.com/absolutesubzero"&gt;Emanuele Quintarelli&lt;/a&gt;&amp;nbsp;kicked off the conference with a talk about the challenges of the social enterprise. As with many experts in the fields his talk was not "happy clappy". Internal social media and enterprise 2.0 has been around for some time now and the results are not all that positive. Even though several extensive reports by for instance McKinsey and Gartner show internal social can offer considerable affordances for organizations, Emanuele wonders what this really means for organizations trying to move forward with internal social. Do these studies really help them make their first or next steps?&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Emanuele shares some facts and figures of what is really happening in organizations. Like:&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;28% of the knowledge workers actually use collaborative tools monthly.&lt;/li&gt;
&lt;li&gt;Gen x is the largest group of users not Gen Y.&lt;/li&gt;
&lt;li&gt;64% of the organizations are not measuring anything w.r.t. internal social.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div&gt;
So, it looks more like a ghost city than a lively community. 50% of the social initiatives fail… By why do they fail?&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Emanuele goes on to list several reasons why Enterprise 2.0 implementations fail. Primary reason is lack of purpose and support of the implementation with community management. Another reason is a lack of focus on people and the way they work. Emanuele stresses we should also pay attention to the negative things humans do like hoarding knowledge.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
OK, but how should we start or proceed? (I bundled some of the points Emanuele listed separately.)&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;Focus on people and communities. Connect to communities as living organisms. Community management is very important. It’s like an iceberg: not much is visible, lots is behind the scenes. It’s building relationships, back-channeling, planning, etc. Co-design is the single most critical factor to success. And respect fear people (can) have. “Change is not death, fear of change is death.”&lt;/li&gt;
&lt;li&gt;Focus on change (management), helping people to work better. ‘Technology changes, humans don’t’. But is this is really true? Adoption is not the end goal, but important. Success is about the majority, not the early adopters.&lt;/li&gt;
&lt;li&gt;Start from the business. Embed social in the flow. How do the social enterprise initiatives relate to business? Define goals.&lt;/li&gt;
&lt;li&gt;Try, fail, evolve. Work in pilots!&lt;/li&gt;
&lt;li&gt;The social enterprise is more about meaning than money. Think about how you reward employee for participating.&lt;/li&gt;
&lt;/ul&gt;
One last thing, says Emanuele: be human and have fun!&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=EdntJn0Or4o:wDb7Hfz9-4o:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=EdntJn0Or4o:wDb7Hfz9-4o:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=EdntJn0Or4o:wDb7Hfz9-4o:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=EdntJn0Or4o:wDb7Hfz9-4o:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=EdntJn0Or4o:wDb7Hfz9-4o:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=EdntJn0Or4o:wDb7Hfz9-4o:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=EdntJn0Or4o:wDb7Hfz9-4o:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=EdntJn0Or4o:wDb7Hfz9-4o:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=EdntJn0Or4o:wDb7Hfz9-4o:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/3109117983578961305?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/3109117983578961305?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/04/notes-and-learnings-from-socialnow.html" title="Notes and learnings from the SocialNow conference 2013 #socialnow " /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-dwRlEWCv7y8/UXmOR3rmizI/AAAAAAAAPn0/v_SlB2GuqQ8/s72-c/photo.JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;D08FQno8eCp7ImA9WhBVEUU.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-5903428356391738575</id><published>2013-04-17T10:03:00.001+02:00</published><updated>2013-04-17T10:03:33.470+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-04-17T10:03:33.470+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="location" /><category scheme="http://www.blogger.com/atom/ns#" term="foursquare" /><category scheme="http://www.blogger.com/atom/ns#" term="crm" /><title>Should Foursquare head into the CRM-market?</title><content type="html">&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-sDCelBscNSA/UW5XQsljFII/AAAAAAAAPmw/A3IDAzndMkY/s1600/foursquare.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://2.bp.blogspot.com/-sDCelBscNSA/UW5XQsljFII/AAAAAAAAPmw/A3IDAzndMkY/s200/foursquare.png" width="200" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Some time ago I &lt;a href="http://info-architecture.blogspot.nl/2011/07/foursquare-useless-for-now.html"&gt;wrote about the usefulness of Foursquare&lt;/a&gt;. At
that time I shared I use Foursquare for fun, but it’s not really useful to me.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Just recently something popped up that does show Foursquare is useful to me. Part of my work is to visit customers and potential
customers. Some of the customers aren’t ready to do business with us at the
time I visit them and ask me to come back later. So, after some time, I visit
them again. Of course the company I work for has a CRM tool, but it’s a pain to
go to that system before you visit the customer to check when you were there
the last time and what you discussed. I usually just look up my notes stored
somewhere on my iPad.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
But it is useful to know when I was there the last time.
When I arrive at a customer I check in to &lt;a href="http://www.foursquare.com/"&gt;Foursquare&lt;/a&gt;. And what does it say?
‘Welcome back! Last time you were here was in &amp;lt;date&amp;gt;.’ The interesting
thing is the conversation with the customer almost always starts with: ‘Good to
have you back, when was the last time we met?’ Foursquare helps me answer that
question.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Which makes me wonder. Isn’t Foursquare a great CRM tool?
Isn’t Foursquare the perfect place to store (and share?) information about
customers? Currently this is not possible in Foursquare. You can share a tip,
which is public. Not good for customer data. But if you could, Foursquare could
not only say ‘welcome back’, but also tell you what you discussed the last time
you were there.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Does this make sense? Curious to hear your thoughts.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;!--EndFragment--&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=J9ytBKEuKx4:vOCxIVfVC9M:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=J9ytBKEuKx4:vOCxIVfVC9M:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=J9ytBKEuKx4:vOCxIVfVC9M:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=J9ytBKEuKx4:vOCxIVfVC9M:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=J9ytBKEuKx4:vOCxIVfVC9M:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=J9ytBKEuKx4:vOCxIVfVC9M:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=J9ytBKEuKx4:vOCxIVfVC9M:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=J9ytBKEuKx4:vOCxIVfVC9M:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=J9ytBKEuKx4:vOCxIVfVC9M:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/5903428356391738575?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/5903428356391738575?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/04/should-foursquare-head-into-crm-market.html" title="Should Foursquare head into the CRM-market?" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-sDCelBscNSA/UW5XQsljFII/AAAAAAAAPmw/A3IDAzndMkY/s72-c/foursquare.png" height="72" width="72" /></entry><entry gd:etag="W/&quot;DUIGQHs6eyp7ImA9WhBQFkw.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-4643446270782214379</id><published>2013-03-18T15:38:00.003+01:00</published><updated>2013-03-18T15:38:41.513+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-18T15:38:41.513+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="social networking" /><category scheme="http://www.blogger.com/atom/ns#" term="social intranet" /><category scheme="http://www.blogger.com/atom/ns#" term="productivity" /><category scheme="http://www.blogger.com/atom/ns#" term="email" /><category scheme="http://www.blogger.com/atom/ns#" term="social networks" /><title>A World without Email by @elsua #intra13</title><content type="html">&lt;a href="http://2.bp.blogspot.com/-cewi92PI1Kc/UUcKauqm-5I/AAAAAAAAOX0/keHr4MS-Pp4/s1600/photo+(2).JPG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="149" src="http://2.bp.blogspot.com/-cewi92PI1Kc/UUcKauqm-5I/AAAAAAAAOX0/keHr4MS-Pp4/s200/photo+(2).JPG" width="200" /&gt;&lt;/a&gt;We started out the workshop with sharing who we are and how we cope with email. Surprisingly most says they cope with email quite well and don't experience email as a huge issue. But all would like to use email in a better way and get others to do so as well. All participants have some kind of collaboration tool inside their firewall (not saying it's used well or not).&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://twitter.com/elsua"&gt;Luis Suarez&lt;/a&gt; finds many high-level manager balk when they hear the word 'social', so he uses 'open' more. He stresses that email is a great way to share information. Which is true, says Luis. But you must add: in a silo. And his 'war' on email is not about killing email but repurposing it.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://elsua.net/"&gt;Luis&lt;/a&gt; asks why colleagues of the partipants are reluctant to use (internal) social/open tools:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;time&lt;/li&gt;
&lt;li&gt;no big value&lt;/li&gt;
&lt;li&gt;loss of control&lt;/li&gt;
&lt;li&gt;relevance of information&lt;/li&gt;
&lt;li&gt;convenience&lt;/li&gt;
&lt;li&gt;availability&lt;/li&gt;
&lt;li&gt;security&lt;/li&gt;
&lt;li&gt;resources&lt;/li&gt;
&lt;li&gt;governance&lt;/li&gt;
&lt;li&gt;no fame&lt;/li&gt;
&lt;li&gt;what's in it for me?&lt;/li&gt;
&lt;li&gt;over-sharing&lt;/li&gt;
&lt;li&gt;extra tool&lt;/li&gt;
&lt;li&gt;not business critical&lt;/li&gt;
&lt;li&gt;etc.&lt;/li&gt;
&lt;/ul&gt;
So, why do people send email? The participants came up with the following list:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;thank you's&lt;/li&gt;
&lt;li&gt;cover you butt&lt;/li&gt;
&lt;li&gt;to do's&lt;/li&gt;
&lt;li&gt;attachment&lt;/li&gt;
&lt;li&gt;meetings&lt;/li&gt;
&lt;li&gt;reminders&lt;/li&gt;
&lt;li&gt;answers to questions&lt;/li&gt;
&lt;li&gt;notifications&lt;/li&gt;
&lt;li&gt;follow-up&lt;/li&gt;
&lt;li&gt;bacn (notifications from social networks)&lt;/li&gt;
&lt;/ul&gt;
So, how can we get ourselves and others to stop doing the above with email and shifting it to open/social tools. First, spend 5 minutes of your time educating someone how to use a file sharing tool (to stop sending around attachments). Thank people on their social profile instead of sending a thank you-email. Thank them publicly. Move status reports to blogs or wiki's. Move your to-do's in email to a public space or public task management tool telling others you're working on it, also allowing others to collaborate with you. Wiki's are great to share the agenda of meetings and the minutes, instead of emailing them. For gathering feedback, use fora or blogs. Ask question on social platforms so others can chip in and you'll be defined by the potential pool of experts.&lt;br /&gt;
What are the benefits of doing this in open/social platforms? We didn't have a lot of time to go into this. Luis advises us to define these benefits personally and show what how this helps us in our own work.&lt;br /&gt;
&lt;br /&gt;
Luis wraps up his workshop with two tips that lead to 80% less email:&lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;apply the above-mentioned use cases&lt;/li&gt;
&lt;li&gt;stop responding to email today&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=4GBm8_P_5sA:WpA5O1oiuG0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=4GBm8_P_5sA:WpA5O1oiuG0:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=4GBm8_P_5sA:WpA5O1oiuG0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=4GBm8_P_5sA:WpA5O1oiuG0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=4GBm8_P_5sA:WpA5O1oiuG0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=4GBm8_P_5sA:WpA5O1oiuG0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=4GBm8_P_5sA:WpA5O1oiuG0:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=4GBm8_P_5sA:WpA5O1oiuG0:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=4GBm8_P_5sA:WpA5O1oiuG0:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4643446270782214379?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4643446270782214379?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/03/a-world-without-email-by-elsua-intra13.html" title="A World without Email by @elsua #intra13" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-cewi92PI1Kc/UUcKauqm-5I/AAAAAAAAOX0/keHr4MS-Pp4/s72-c/photo+(2).JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;DkEAR3k5eip7ImA9WhBQFk0.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-283174572760326798</id><published>2013-03-18T12:04:00.000+01:00</published><updated>2013-03-18T12:04:06.722+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-18T12:04:06.722+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="congres intranet" /><category scheme="http://www.blogger.com/atom/ns#" term="intra13" /><category scheme="http://www.blogger.com/atom/ns#" term="intranet" /><category scheme="http://www.blogger.com/atom/ns#" term="digital workplace" /><title>Intranet as digital workplace by @markmorrell #intra13 </title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-2sgcczNiKJ4/UUbZw-0JcrI/AAAAAAAAOXg/RisVcgC5auc/s1600/photo+(1).JPG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="149" src="http://1.bp.blogspot.com/-2sgcczNiKJ4/UUbZw-0JcrI/AAAAAAAAOXg/RisVcgC5auc/s200/photo+(1).JPG" width="200" /&gt;&lt;/a&gt;&lt;/div&gt;
First of all we should be clear what a digital workplace is. Mark’s definition of a digital workplace is: work is something you do not a place you go to. In a digital workplace you can:&lt;br /&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;work from any location or while mobile&amp;nbsp;&lt;/li&gt;
&lt;li&gt;have the same or similar online experience&lt;/li&gt;
&lt;li&gt;collaborate, search, and complete tasks online&amp;nbsp;&lt;/li&gt;
&lt;li&gt;choose what tools you can use to do this&amp;nbsp;&lt;/li&gt;
&lt;li&gt;feel comfortable whenever you are using&amp;nbsp;&lt;/li&gt;
&lt;li&gt;feel comfortable whenever you are using it&amp;nbsp;&lt;/li&gt;
&lt;li&gt;be confident you can use it when you need to&lt;/li&gt;
&lt;li&gt;have a better work/life balance&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
The real difference between the intranet and the digital workplace is that you can get work done with a digital workplace. It's not just a content and publication platform, but a place where you can get work done. It's collaborative, it's task-focused.&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
So, how do you develop a digital workplace strategy? Mark shares several points with us:&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;it should align with your other strategies&lt;/li&gt;
&lt;li&gt;is wider than an intranet strategy&lt;/li&gt;
&lt;li&gt;is for the short, medium, and long term&lt;/li&gt;
&lt;li&gt;has a governance framework (Mark: 'everything should be managed')&lt;/li&gt;
&lt;li&gt;people who will create, support, and make it happen ('this is the hardest part', says Mark)&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
What steps can be made to work towards the digital workplace:&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;develop a proposal for a digital workplace&lt;/li&gt;
&lt;li&gt;show the benefits to be gained&lt;/li&gt;
&lt;li&gt;get it approved...... and funded!&lt;/li&gt;
&lt;li&gt;have a steering group (focus on strategy, not implementation with them)&lt;/li&gt;
&lt;li&gt;agree on roles and responsibilities&lt;/li&gt;
&lt;li&gt;have standards, training, guidance (e.g. with vid- or podcasts)&lt;/li&gt;
&lt;li&gt;coordinate IT, HR and property management&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
During the workshop the participants worked on these steps and shared their approaches.&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
Mark &lt;a href="http://intranet-pioneer.com/"&gt;blogs quite a lot about the benefits of digital workplace strategy&lt;/a&gt;. He shared some benefits during the workshop, such as:&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;shared performance objectives reduce risk of conflicting priorities&lt;/li&gt;
&lt;li&gt;help decide top priorities to implement&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
Benefits of digital workplace are:&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;BT employees took fewer sick days and were 20% more productive&lt;/li&gt;
&lt;li&gt;a study by the Emerald group at BT showed their work-life balance improved, even though they worked longer hours&lt;/li&gt;
&lt;li&gt;the BT Agile Worker program save 6000 pounds per worker&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
Mark also pointed to reports from other companies about the benefits they are getting from the digital workplace.&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NBe8ry20XUg:hWhk3D3lbq0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NBe8ry20XUg:hWhk3D3lbq0:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NBe8ry20XUg:hWhk3D3lbq0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=NBe8ry20XUg:hWhk3D3lbq0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NBe8ry20XUg:hWhk3D3lbq0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=NBe8ry20XUg:hWhk3D3lbq0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NBe8ry20XUg:hWhk3D3lbq0:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=NBe8ry20XUg:hWhk3D3lbq0:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=NBe8ry20XUg:hWhk3D3lbq0:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/283174572760326798?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/283174572760326798?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/03/intranet-as-digital-workplace-by.html" title="Intranet as digital workplace by @markmorrell #intra13 " /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-2sgcczNiKJ4/UUbZw-0JcrI/AAAAAAAAOXg/RisVcgC5auc/s72-c/photo+(1).JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;D08NQnczeSp7ImA9WhBQE0k.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-2620683383016197427</id><published>2013-03-15T12:09:00.002+01:00</published><updated>2013-03-15T12:11:33.981+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-15T12:11:33.981+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="dutchopen" /><category scheme="http://www.blogger.com/atom/ns#" term="creativity" /><category scheme="http://www.blogger.com/atom/ns#" term="serendipity" /><category scheme="http://www.blogger.com/atom/ns#" term="kennismanagement" /><category scheme="http://www.blogger.com/atom/ns#" term="km" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge management" /><title>Innovatie in de 4de dimensie, de 4 ruimtes van KM door @pauliske #4ruimtes</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-PaTsK2LuL-4/UUL9tackvXI/AAAAAAAAOQ4/3meUxAOUJ1g/s1600/photo+2.JPG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://2.bp.blogspot.com/-PaTsK2LuL-4/UUL9tackvXI/AAAAAAAAOQ4/3meUxAOUJ1g/s200/photo+2.JPG" width="150" /&gt;&lt;/a&gt;&lt;/div&gt;
Volgende spreker is &lt;a href="http://twitter.com/pauliske"&gt;Paul Iske&lt;/a&gt; over 'Innovatie in de 4de dimensie, de 4 ruimtes van kennismanagement'.&lt;br /&gt;
Net als de vorige spreker Pierre benadrukt Paul dat de wereld wordt steeds complexer. Hoe blijf je bestaan in de wereld? Hoe pak je een rol in deze wereld?&lt;br /&gt;
Het vraagt om Agility. Paul laat een leuk voorbeeld van agility zien aan de hand van &lt;a href="http://www.youtube.com/watch?v=0qF01mJ6KSM"&gt;dit filmpje&lt;/a&gt;.&lt;br /&gt;
Veel organisaties komen snel terecht in routines. Routines zijn een deel van leren; je kunt zo dingen sneller leren doen. Maar het kan ook beperken. Je mist dingen als je niet de moeite neemt om even buiten je routines te kijken.&lt;br /&gt;
In deze tijd wordt er van ons gevraagd om de snelheid van ons leren te verhogen. Want we leven in een tijd waarin de snelheid van het leren, sneller gaat dan de verandering.&lt;br /&gt;
Innovatie is dan het proces om (bestaande) kennis toe te passen in een markt/omgeving.&lt;br /&gt;
Een omgeving bestaat uit 4 ruimtes:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;social space&lt;/li&gt;
&lt;li&gt;virtual space&lt;/li&gt;
&lt;li&gt;physical space&lt;/li&gt;
&lt;li&gt;process space&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
Het klimaat is ook belangrijk voor innovatie. &lt;a href="http://twitter.com/leadbeaterch"&gt;Leadbeater&lt;/a&gt; heeft 9 condities benoemd voor creativiteit, leiderschap en innovatie:&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;diversiteit&lt;/li&gt;
&lt;li&gt;selectie&lt;/li&gt;
&lt;li&gt;imbedding&lt;/li&gt;
&lt;li&gt;co-evolutie&lt;/li&gt;
&lt;li&gt;ontleren&lt;/li&gt;
&lt;li&gt;verstoring&lt;/li&gt;
&lt;li&gt;eenvoud&lt;/li&gt;
&lt;li&gt;verspilling&lt;/li&gt;
&lt;li&gt;timing&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
Er is geen schaarste aan kennis. Het gaat erom wat je met die kennis &lt;i&gt;doet&lt;/i&gt;. Als je aan mensen vraagt welk deel van hun kennis ze gebruiken (op het werk) dan blijkt dat het bijzonder klein is. Het hoeft geen 100% te zijn, maar wat meer zou veel opleveren.&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
Belangrijk bij innovatie is samenwerken vanuit verschillende perspectieven. Samen kijken naar een probleem op verschillende manieren. Uit onderzoek blijkt dat op deze manieren doorbraken worden gerealiseerd. (Heet ook wel 'open innovatie' of 'collaboratieve innovatie'.)&lt;/div&gt;
&lt;div&gt;
Maar je kunt nog een stap daarvoor innoveren. Dan weet je eigenlijk helemaal niet wat je wilt, maar door partijen bij elkaar te zeggen kun je 'combinatorisch innoveren'. Op basis van serendipity komen mensen/organisaties tot combinaties die vermarkt kunnen worden. De basis vraag is dan: Wat zouden wij samen kunnen doen?&lt;/div&gt;
&lt;div&gt;
We zijn hier ook mee aan de slag gegaan aan het einde van de keynote: gewoon met je buurman kijken of er raakvlakken zijn om samen te werken.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=y89RguwOGuE:spZaPYk25yI:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=y89RguwOGuE:spZaPYk25yI:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=y89RguwOGuE:spZaPYk25yI:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=y89RguwOGuE:spZaPYk25yI:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=y89RguwOGuE:spZaPYk25yI:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=y89RguwOGuE:spZaPYk25yI:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=y89RguwOGuE:spZaPYk25yI:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=y89RguwOGuE:spZaPYk25yI:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=y89RguwOGuE:spZaPYk25yI:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/2620683383016197427?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/2620683383016197427?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/03/innovatie-in-de-4de-dimensie-de-4.html" title="Innovatie in de 4de dimensie, de 4 ruimtes van KM door @pauliske #4ruimtes" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-PaTsK2LuL-4/UUL9tackvXI/AAAAAAAAOQ4/3meUxAOUJ1g/s72-c/photo+2.JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;Dk8DSH08eip7ImA9WhBQE0k.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-7020335230841883676</id><published>2013-03-15T11:10:00.005+01:00</published><updated>2013-03-15T11:54:39.372+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-15T11:54:39.372+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="dutchopen" /><category scheme="http://www.blogger.com/atom/ns#" term="kennismanagement" /><category scheme="http://www.blogger.com/atom/ns#" term="km" /><category scheme="http://www.blogger.com/atom/ns#" term="management" /><category scheme="http://www.blogger.com/atom/ns#" term="congres sharepoint" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge management" /><title>Ontwerpen van organisaties door Pierre van Amelsvoort #4ruimtes </title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://3.bp.blogspot.com/-V8OhOELrObY/UUL944QyGWI/AAAAAAAAORA/NOaq_H3WkDA/s1600/photo+1.JPG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://3.bp.blogspot.com/-V8OhOELrObY/UUL944QyGWI/AAAAAAAAORA/NOaq_H3WkDA/s200/photo+1.JPG" width="150" /&gt;&lt;/a&gt;&lt;/div&gt;
Vandaag ben ik bij het lustrum congres van de DutchOpen KM. Het DutchOpen KM en een netwerk van kennismanagement ervaringsdeskundigen die regelmatig bij elkaar komen. Het netwerk bestaat 10 jaar en het leek ons goed om dit te vieren met een congres over de ‘4 ruimtes van kennis management’. Ik zal mijn notes van de dag delen in een aantal blogposts. Ik schrijf live, dus let graag niet teveel op de zinsbouw en typo’s.&lt;br /&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Eerste keynote spreker is &lt;a href="http://www.linkedin.com/pub/pierre-van-amelsvoort/1a/4a5/a84"&gt;Pierre van Amelsvoort&lt;/a&gt;. Zijn keynote gaat over ‘Ontwerpen van organisaties’.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Pierre neemt ons mee in de veranderende wereld van organisaties. We bewegen van de focus op efficiency naar kwaliteit, flexibiliteit, innovativiteit en nu service/duurzaamheid. Dit is niet en-en-en. Dit wil niet zeggen dat jouw organisatie alle deze stappen moet zetten.&lt;br /&gt;
Belangrijk om naar organisaties te kijken vanuit het begrip 'regimes'.&lt;br /&gt;
Een grote ziekte in organisaties is het opknippen van organisaties in functies/fragmenten. En dat groot perse beter zou zijn.&lt;br /&gt;
Volgorde van organiseren is P &amp;gt; B &amp;gt; S: proces, besturen en systemen.&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;
Betrokkenheid van medewerker bepaalt kwaliteit van het werk, weten we al lang. Maar wat doen we daarmee?&lt;br /&gt;
Pierre’s antwoord is: organiseren met mate en zorg voor ruimte voor diversiteit en coleur local. &lt;a href="https://twitter.com/search?q=%234ruimtes&amp;amp;src=hash"&gt;&lt;/a&gt;Zoekt naar de menselijke maat van samenwerking. Dat heeft volgens Pierre ook met de grote van organisaties en groepen binnen organisaties te maken:&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;8-12 mensen is een goed team, kleiner dan dat heb je onvoldoende diversiteit&amp;nbsp;&lt;/li&gt;
&lt;li&gt;40-50 mensen in je hoofd hebben voor een community.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
Hierarchie is goed, om richting te geven aan mensen. Maar hierarchie moet altijd wat toevoegen, vooral het tijdsperspectief. De functie van hierarchie is het nemen van beslissen, niet administreren. &lt;br /&gt;
&lt;br /&gt;
Het is belangrijk om meer te organiseren op basis van vertrouwen. &lt;br /&gt;
&lt;br /&gt;
Bij veranderingen in organisaties moet je sturen op mensen, cultuur, structuur en systemen. Vooral bij vaste, bureaucratische regimes naar een flexible regime, moet het ‘disruptive’ gebeuren. &lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=90tIek7jmM4:URCYh8HBib8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=90tIek7jmM4:URCYh8HBib8:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=90tIek7jmM4:URCYh8HBib8:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=90tIek7jmM4:URCYh8HBib8:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=90tIek7jmM4:URCYh8HBib8:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=90tIek7jmM4:URCYh8HBib8:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=90tIek7jmM4:URCYh8HBib8:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=90tIek7jmM4:URCYh8HBib8:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=90tIek7jmM4:URCYh8HBib8:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/7020335230841883676?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/7020335230841883676?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/03/ontwerpen-van-organisaties-door-pierre.html" title="Ontwerpen van organisaties door Pierre van Amelsvoort #4ruimtes " /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-V8OhOELrObY/UUL944QyGWI/AAAAAAAAORA/NOaq_H3WkDA/s72-c/photo+1.JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;CkEAQX88cCp7ImA9WhBQEEw.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-4249124069316501421</id><published>2013-03-11T15:04:00.000+01:00</published><updated>2013-03-11T15:04:00.178+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-11T15:04:00.178+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="commenting" /><category scheme="http://www.blogger.com/atom/ns#" term="comic" /><category scheme="http://www.blogger.com/atom/ns#" term="communication" /><category scheme="http://www.blogger.com/atom/ns#" term="conversation" /><title>Comment therapy</title><content type="html">&lt;div class="separator" style="clear: both; text-align: left;"&gt;
No comment... :-)&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-xo4gtVXDEsw/UTn9xiNbTxI/AAAAAAAAOB8/YrZ3Xkstpr8/s1600/F35084D7-8BDF-4D64-B153-762E2AA2E360.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="282" src="http://1.bp.blogspot.com/-xo4gtVXDEsw/UTn9xiNbTxI/AAAAAAAAOB8/YrZ3Xkstpr8/s320/F35084D7-8BDF-4D64-B153-762E2AA2E360.JPG" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=RcgmT3Y_PBE:Zr96Wu9RMjw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=RcgmT3Y_PBE:Zr96Wu9RMjw:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=RcgmT3Y_PBE:Zr96Wu9RMjw:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=RcgmT3Y_PBE:Zr96Wu9RMjw:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=RcgmT3Y_PBE:Zr96Wu9RMjw:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=RcgmT3Y_PBE:Zr96Wu9RMjw:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=RcgmT3Y_PBE:Zr96Wu9RMjw:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=RcgmT3Y_PBE:Zr96Wu9RMjw:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=RcgmT3Y_PBE:Zr96Wu9RMjw:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4249124069316501421?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4249124069316501421?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/03/comment-therapy.html" title="Comment therapy" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-xo4gtVXDEsw/UTn9xiNbTxI/AAAAAAAAOB8/YrZ3Xkstpr8/s72-c/F35084D7-8BDF-4D64-B153-762E2AA2E360.JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;Dk4GQ3gyeCp7ImA9WhBRF0g.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-4152546956295737118</id><published>2013-03-08T16:02:00.000+01:00</published><updated>2013-03-08T16:02:02.690+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-08T16:02:02.690+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="telework" /><category scheme="http://www.blogger.com/atom/ns#" term="digital workplace" /><category scheme="http://www.blogger.com/atom/ns#" term="yahoo" /><category scheme="http://www.blogger.com/atom/ns#" term="google" /><category scheme="http://www.blogger.com/atom/ns#" term="telecommuting" /><title>Is working from home always better?</title><content type="html">There's been lots of talk in the blogosphere about Marissa Mayers decision to tell Yahoo! employees to stop working from home. Hey, even Yahoo! employees were/are discussing it on the web.&lt;br /&gt;
James Robertson &lt;a href="http://www.steptwo.com.au/columntwo/no-working-from-home-yahoo-in-the-spotlight-but-google-has-got-off-lightly/"&gt;wrote up a nice post&lt;/a&gt; about this decision and also pointed to the fact that Google seems to be like-minded to Yahoo! when it comes to working from home. Also interesting is what he says about the implications of this kind of news for 'the digital workplace'.&lt;br /&gt;
&lt;br /&gt;
One of the things I like about the discussion is that we have to rethink why we like/dislike working from home. And that's one of the things I miss in the discussion about tele-work. Of course commenters rightly wonder what this Yahoo! statement means with respect to trusting employees to decide for themselves where they can get their work done.&lt;br /&gt;
However, isn't it also OK to discuss what the pro's and con's of tele-work are. Is working from home always the best way to go?&lt;br /&gt;
In my experience with working from home, some types of work are great to do from home and some are great to do in the train or at the office. I know from talks with others that my experiences relate to many. For instance I find it very hard to write reports and read longer documents and books at the office. There are simply too many disruptions there. I know this does not go for everybody. But isn't this something to discuss. Along with things we personally have to get done, there are also joint task we have to get done together. How are we going to get that done when working from home and/or the office?&lt;br /&gt;
As &lt;a href="http://twitter.com/markmorrell"&gt;Mark Morrell&lt;/a&gt; says in a comment to the above-mentioned post (I'm rephrasing him a bit): in the end it comes down to trusting employees to decide when and where they can get things done. Sometimes this is at home, sometimes this is at work. True. My point is: we decide this for ourselves &lt;i&gt;and&lt;/i&gt; we decide about this together with colleagues.&lt;br /&gt;
&lt;br /&gt;
I'm curious what your thoughts are on this topic. Please share them as a comment.&lt;br /&gt;
&lt;br /&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iXW7DO2KyMk:zGMK_fp5hCA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iXW7DO2KyMk:zGMK_fp5hCA:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iXW7DO2KyMk:zGMK_fp5hCA:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=iXW7DO2KyMk:zGMK_fp5hCA:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iXW7DO2KyMk:zGMK_fp5hCA:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=iXW7DO2KyMk:zGMK_fp5hCA:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iXW7DO2KyMk:zGMK_fp5hCA:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iXW7DO2KyMk:zGMK_fp5hCA:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=iXW7DO2KyMk:zGMK_fp5hCA:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4152546956295737118?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4152546956295737118?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/03/is-working-from-home-always-better.html" title="Is working from home always better?" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author></entry><entry gd:etag="W/&quot;DkQHRno5fSp7ImA9WhBSFEs.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-6847922871950207699</id><published>2013-02-21T17:32:00.001+01:00</published><updated>2013-02-21T17:32:17.425+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-02-21T17:32:17.425+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="gamification" /><category scheme="http://www.blogger.com/atom/ns#" term="congres intranet" /><category scheme="http://www.blogger.com/atom/ns#" term="social intranet" /><category scheme="http://www.blogger.com/atom/ns#" term="intra13" /><category scheme="http://www.blogger.com/atom/ns#" term="intranet" /><category scheme="http://www.blogger.com/atom/ns#" term="digital workplace" /><title>Reasons to come to the Intranet Conference 2013 #intra13</title><content type="html">&lt;a href="http://1.bp.blogspot.com/--YOE47TVDWk/USZJ8DzXXkI/AAAAAAAANP4/XS3nFDy52eo/s1600/photo.JPG" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://1.bp.blogspot.com/--YOE47TVDWk/USZJ8DzXXkI/AAAAAAAANP4/XS3nFDy52eo/s200/photo.JPG" width="150" /&gt;&lt;/a&gt;&lt;br /&gt;
On March 18 and 19, 2013 the next edition of &lt;a href="http://english.congresintranet.nl/english/"&gt;the Dutch Intranet Conference &lt;/a&gt;will be held. We hope to meet you there! But let me give you some idea of the program and main topic of the conference.&lt;br /&gt;&lt;br /&gt;In the intranet space lots of discussion is about choosing the right technology and selecting and providing the right features for your organization. Also, we talk about intranet governance. What is the right governance model for my organization? How can we keep our intranet interesting and vibrant? &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Soft skills &lt;/b&gt;&lt;br /&gt;What I hardly hear is the skills intranet-related people need to do intranet right? What skills does an intranet manager or owner need? For this reason we thought we’d focus the keynotes on this topic: the skills of the intranet manager and more specifically, the knowledge worker. Because that’s what most modern intranets are for: to support knowledge workers in their daily work. &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Keynotes &lt;/b&gt;&lt;br /&gt;We invited 3 keynote speakers to give their view on this topic. These are: &lt;br /&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="http://twitter.com/euan"&gt;Euan Semple&lt;/a&gt;: The internet has tremendous influence on organizations. Subsequently this also changes the way we look at intranets. Euan will share what he thinks is changing in organzations and what it means for intranets.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://twitter.com/elsua"&gt;Luis Suarez&lt;/a&gt;: What skills does the modern intranet manager need to do his/her work? And what skills does the knowledge worker (the intranet manager’s customer) need to work in a productive way? Luis will share his vision and experiences on this topic and give practical tips to improve the way we work and subsequently improve the intranet.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://twitter.com/stevenvbe"&gt;Steven van Bellegem&lt;/a&gt;: The intranet can be seen as a conversation between the business and technology. How do we make these two connect? The intranet itself can be seen as a conversation platform. How do intranet managers create interesting and relevant conversations? And why are conversations so important inside the company? Those are some of the questions Steven will address in his keynote.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
In all these talks we hope the conference participants will get practical insights for their daily work, which they can act on. We think we have chosen excellent keynote speakers from which we all can learn. &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Breakouts: BYOD, mobile, gamification, and more &lt;/b&gt;&lt;br /&gt;On the conference day there will also be 3 rounds of breakouts with 10+ topics to choose from. These breakouts won’t be focused on the soft side of intranet only. We set up a nice mix of more traditional and more modern intranet topics. Just to mention two modern topics: the Rabobank will be talking about how Bring-Your-Own-Device works in practice and what it means for intranet. And a large telecom company will be sharing how they use gamification on their intranet to increase engagement. &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Pre-conference workshops &lt;/b&gt;&lt;br /&gt;The day before the conference we have 4 pre-conference workshops about topics that are pretty hot. &lt;a href="http://twitter.com/markmorrell"&gt;Mark Morrell&lt;/a&gt; will give a workshop about the digital workplace and Sharepoint intranets. Luis Suarez will talk about his (and your) battle against email. And Euan Semple’s workshop is about getting hands-on with social intranet. &lt;br /&gt;&lt;br /&gt;&lt;b&gt;You’re invited!&lt;/b&gt;&lt;br /&gt;The company I work for, &lt;a href="http://www.entopic.com/"&gt;Entopic&lt;/a&gt;, has organized this conference for several years now. We’re proud to say it has become the largest intranet conference in the world.  Of course most of the participants come from Holland and Belgium. But, over the years more and more participants from other countries have joined us as well. So, we’d love to welcome you all to this conference. Not only the keynotes, but also the pre-conference workshop and several breakouts will be in English.&lt;div&gt;
&lt;br /&gt;  I hope this give you some idea of what &lt;a href="http://www.congresintranet.nl/"&gt;this year’s conference&lt;/a&gt; is about. If you have any questions, please leave a comment and I’ll get back to you soon.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=2LxPG7hlP0w:BktxlAw9t10:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=2LxPG7hlP0w:BktxlAw9t10:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=2LxPG7hlP0w:BktxlAw9t10:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=2LxPG7hlP0w:BktxlAw9t10:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=2LxPG7hlP0w:BktxlAw9t10:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=2LxPG7hlP0w:BktxlAw9t10:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=2LxPG7hlP0w:BktxlAw9t10:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=2LxPG7hlP0w:BktxlAw9t10:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=2LxPG7hlP0w:BktxlAw9t10:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6847922871950207699?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6847922871950207699?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/02/reasons-to-come-to-intranet-conference.html" title="Reasons to come to the Intranet Conference 2013 #intra13" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/--YOE47TVDWk/USZJ8DzXXkI/AAAAAAAANP4/XS3nFDy52eo/s72-c/photo.JPG" height="72" width="72" /></entry><entry gd:etag="W/&quot;DkUNRnc7cSp7ImA9WhBTGUg.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-4893951222661310528</id><published>2013-02-15T19:51:00.003+01:00</published><updated>2013-02-15T19:51:37.909+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-02-15T19:51:37.909+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="knowledge work" /><category scheme="http://www.blogger.com/atom/ns#" term="productivity" /><category scheme="http://www.blogger.com/atom/ns#" term="slack" /><category scheme="http://www.blogger.com/atom/ns#" term="blogging" /><title>Under pressure</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-QyjKby0Ixts/UR6C8llKY_I/AAAAAAAANFQ/70FmWwBGkD4/s1600/pressure.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://1.bp.blogspot.com/-QyjKby0Ixts/UR6C8llKY_I/AAAAAAAANFQ/70FmWwBGkD4/s200/pressure.jpg" width="196" /&gt;&lt;/a&gt;&lt;/div&gt;
How do you feel when you’re under pressure? Can you get things done then? Can you think? I was wondering how you cope with pressure, because I’ve been very busy lately. So busy, I hardly have time to blog (and tweet)… Which is not good.&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
In the past I’ve written about &lt;a href="http://info-architecture.blogspot.nl/2010/06/slack-day.html"&gt;how important slack&lt;/a&gt; is for work in general and specifically for social stuff, like blogging. We need time to reflect and think things over. Time is needed to write things down and publish blogposts about what we do and think. What I find is that when slack leaves my time schedule, I have a hard time keeping up blogging. However important I find blogging, it’s one of the first things I stop doing. So, how important to me is it really, I wonder? Should it be part of my weekly time schedule?&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
However, on the more positive side, &amp;nbsp;you may know, I use the &lt;a href="http://info-architecture.blogspot.nl/2009/12/workshop-productive-knowledge-work.html"&gt;‘Getting Things Done’ methodology&lt;/a&gt; to stay efficient and effective. I’ve been under pressure many times, but I never let go of GTD. It really helps me plan my tasks, get my tasks completed on time and define realistic deadlines with myself and clients.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
So, is that the way to go? Should I just ‘manage’ blogging in the same way then? It would be interesting to hear how you plan your social stuff.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=br57XFmQs9M:aslLzOeHKmE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=br57XFmQs9M:aslLzOeHKmE:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=br57XFmQs9M:aslLzOeHKmE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=br57XFmQs9M:aslLzOeHKmE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=br57XFmQs9M:aslLzOeHKmE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=br57XFmQs9M:aslLzOeHKmE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=br57XFmQs9M:aslLzOeHKmE:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=br57XFmQs9M:aslLzOeHKmE:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=br57XFmQs9M:aslLzOeHKmE:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4893951222661310528?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4893951222661310528?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/02/under-pressure.html" title="Under pressure" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-QyjKby0Ixts/UR6C8llKY_I/AAAAAAAANFQ/70FmWwBGkD4/s72-c/pressure.jpg" height="72" width="72" /></entry><entry gd:etag="W/&quot;C0cESHo_fSp7ImA9WhNbGEs.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-1763298523538451349</id><published>2013-01-22T14:23:00.002+01:00</published><updated>2013-01-22T14:23:29.445+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-01-22T14:23:29.445+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="blogger" /><category scheme="http://www.blogger.com/atom/ns#" term="sharing" /><category scheme="http://www.blogger.com/atom/ns#" term="blogging" /><title>6 years of blogging</title><content type="html">Wow, time flies when you're having fun, right? I was planning to blog about my blog's 6th birthday, but simply forgot because of some interesting (and more important?) work I had to do.&lt;br /&gt;
Six years ago I decided to start blogging! I remember the first time I clicked on 'Publish'. Man, was I anxious/curious/scared what would happen next. Actually, I still feel those sensations every time I blog. It is &lt;i&gt;scary&lt;/i&gt;&amp;nbsp;to share your ideas publicly and have them read, reviewed and scrutinized out in the open. But, in my experience, it has also always been great fun. I met lots of new people via my blog, I learned &amp;nbsp;a lot from all the interactions on and around my blog, and it's a great way to structure my thoughts.&lt;br /&gt;
So, expect me to continue blogging in 2013! Last year the number of posts I published went down. You decide if that's good or bad. And if it says something about the quality of the posts. A big reason for less posts is the job I have. I've been &lt;i&gt;very&lt;/i&gt;&amp;nbsp;busy (and I'm happy to say so in these economic times). But I do plan to blog more. I want to blurt out more short thoughts and experiences I have. Of course I hope you, my dear readers, will enjoy them. Looking forward to hear from you!&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=a4GufeoTWOA:kxNe3m5JwbE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=a4GufeoTWOA:kxNe3m5JwbE:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=a4GufeoTWOA:kxNe3m5JwbE:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=a4GufeoTWOA:kxNe3m5JwbE:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=a4GufeoTWOA:kxNe3m5JwbE:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=a4GufeoTWOA:kxNe3m5JwbE:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=a4GufeoTWOA:kxNe3m5JwbE:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=a4GufeoTWOA:kxNe3m5JwbE:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=a4GufeoTWOA:kxNe3m5JwbE:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/1763298523538451349?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/1763298523538451349?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2013/01/6-years-of-blogging.html" title="6 years of blogging" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author></entry><entry gd:etag="W/&quot;CEYAQ308eip7ImA9WhNVGUg.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-4613107145865460777</id><published>2012-12-31T12:09:00.000+01:00</published><updated>2012-12-31T12:09:02.372+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-31T12:09:02.372+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="facebook" /><category scheme="http://www.blogger.com/atom/ns#" term="internet" /><category scheme="http://www.blogger.com/atom/ns#" term="iphone" /><category scheme="http://www.blogger.com/atom/ns#" term="apple" /><category scheme="http://www.blogger.com/atom/ns#" term="strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="mobile" /><category scheme="http://www.blogger.com/atom/ns#" term="mary meeker" /><category scheme="http://www.blogger.com/atom/ns#" term="trends" /><category scheme="http://www.blogger.com/atom/ns#" term="mobileweb" /><category scheme="http://www.blogger.com/atom/ns#" term="google" /><category scheme="http://www.blogger.com/atom/ns#" term="android" /><category scheme="http://www.blogger.com/atom/ns#" term="microsoft" /><category scheme="http://www.blogger.com/atom/ns#" term="ipad" /><category scheme="http://www.blogger.com/atom/ns#" term="paperdigital" /><title>My notes from the Internet Trends 2012 Update</title><content type="html">I find Mary Meeker's reports on internet trends very interesting. They're packed with interesting data and insights. I've been &lt;a href="http://info-architecture.blogspot.nl/2011/11/internet-trends-2011-and-on.html"&gt;following her work&lt;/a&gt; closely. She recently published an updated overview of 2012 and I thought I'd share my highlights with you at the end of this year.&lt;br /&gt;
&lt;br /&gt;
sheet 9: stunning slide showing shipment of iPads, iPhones and iPods over 10 years compared. This slides is old(er), but it just underlines the interesting times we live in&lt;br /&gt;
sheet 10: You thought the ramp up of Apple products is huge, well Android ramp up is 6 times that of iPhone&lt;br /&gt;
sheet 12: 30% of US adults own a tablet, less than 3 years ago that was 3%&lt;br /&gt;
sheet 17: mobile advertising is growing rapidly; $0.7 billion in 2008, $19 billion in 2012&lt;br /&gt;
sheet 18: 24% of online shopping was done via tablets on Black Saturday, versus 6% 2 years ago&lt;br /&gt;
sheet 20: we are in the midst of a &lt;b&gt;huge change powered by new devices&amp;nbsp;+ connectivity&amp;nbsp;+ UI&amp;nbsp;+ beauty&lt;/b&gt;. Meeker highlights the effects for the pc, photography, phone, knowledge, navigation, news, note taking, content organization, magazines, cash registers, lending money, idea building/funding, recruiting, product design, etc. market (and we are still in "spring training", Meeker says [sheet 58])&lt;br /&gt;
sheet 24: very interesting overview of the market share of Microsoft compared to others. Used to be 96% and is now just 35%.&lt;br /&gt;
sheet 61: I like how Meeker digs deeper into the consequences of the internet by addressing what it means for our space, time and money and how we balance these&lt;br /&gt;
sheet 77: Meeker mentions markets that still can be opened, such as the time spent in cars and watching TV, education and healthcare.&lt;br /&gt;
&lt;br /&gt;
And here's her complete slidedeck:&lt;br /&gt;
&lt;br /&gt;
&lt;iframe allowfullscreen="allowfullscreen" frameborder="0" height="356" marginheight="0" marginwidth="0" mozallowfullscreen="mozallowfullscreen" scrolling="no" src="http://www.slideshare.net/slideshow/embed_code/15474339?rel=0" style="border-width: 1px 1px 0; border: 1px solid #CCC; margin-bottom: 5px;" webkitallowfullscreen="webkitallowfullscreen" width="427"&gt; &lt;/iframe&gt; &lt;br /&gt;
&lt;div style="margin-bottom: 5px;"&gt;
&lt;strong&gt; &lt;a href="http://www.slideshare.net/kleinerperkins/2012-kpcb-internet-trends-yearend-update" target="_blank" title="2012 KPCB Internet Trends Year-End Update"&gt;2012 KPCB Internet Trends Year-End Update&lt;/a&gt; &lt;/strong&gt; from &lt;strong&gt;&lt;a href="http://www.slideshare.net/kleinerperkins" target="_blank"&gt;Kleiner Perkins Caufield &amp;amp; Byers&lt;/a&gt;&lt;/strong&gt; &lt;/div&gt;
&lt;br /&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=WBg3jdv9TE8:2RZClaobnX4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=WBg3jdv9TE8:2RZClaobnX4:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=WBg3jdv9TE8:2RZClaobnX4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=WBg3jdv9TE8:2RZClaobnX4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=WBg3jdv9TE8:2RZClaobnX4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=WBg3jdv9TE8:2RZClaobnX4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=WBg3jdv9TE8:2RZClaobnX4:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=WBg3jdv9TE8:2RZClaobnX4:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=WBg3jdv9TE8:2RZClaobnX4:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4613107145865460777?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4613107145865460777?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/12/my-notes-from-internet-trends-2012.html" title="My notes from the Internet Trends 2012 Update" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author></entry><entry gd:etag="W/&quot;A08NQ34_fSp7ImA9WhNVF00.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-4305466190164153855</id><published>2012-12-28T16:42:00.003+01:00</published><updated>2012-12-28T16:51:32.045+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-28T16:51:32.045+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="web 2.0" /><category scheme="http://www.blogger.com/atom/ns#" term="sharing" /><category scheme="http://www.blogger.com/atom/ns#" term="social media" /><category scheme="http://www.blogger.com/atom/ns#" term="open" /><category scheme="http://www.blogger.com/atom/ns#" term="internet" /><category scheme="http://www.blogger.com/atom/ns#" term="trends" /><category scheme="http://www.blogger.com/atom/ns#" term="rss" /><title>Is our web slipping away?</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-Q-q9hxRRg20/UN25cSq2vcI/AAAAAAAALf4/vLzi82cD5Ac/s1600/lostfound.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://2.bp.blogspot.com/-Q-q9hxRRg20/UN25cSq2vcI/AAAAAAAALf4/vLzi82cD5Ac/s200/lostfound.jpg" width="200" /&gt;&lt;/a&gt;&lt;/div&gt;
Sometimes I read a post that really gets me thinking. Anil Dashes' &lt;a href="http://dashes.com/anil/2012/12/the-web-we-lost.html"&gt;recent post 'The web we lost'&lt;/a&gt; did it this time. I think reading the full post is well worth your time if you're interested in where the web is headed. Two fragments from the post triggered me the most:&lt;br /&gt;
&lt;blockquote class="tr_bq"&gt;
We've lost key features that we used to rely on, and worse, we've abandoned core values that used to be fundamental to the web world. To the credit of today's social networks, they've brought in hundreds of millions of new participants to these networks, and they've certainly made a small number of people rich.&lt;br /&gt;
&lt;br /&gt;
But they haven't shown the web itself the respect and care it deserves, as a medium which has enabled them to succeed. And they've now narrowed the possibilites of the web for an entire generation of users who don't realize how much more innovative and meaningful their experience could be.&lt;br /&gt;
&lt;br /&gt;
(...)&amp;nbsp;&lt;/blockquote&gt;
&lt;blockquote class="tr_bq"&gt;
The first step to disabusing them of this notion is for the people creating the next generation of social applications to learn a little bit of history, to know your shit, whether that's about &lt;a href="http://dashes.com/anil/2010/04/ten-years-of-twitter-ads.html"&gt;Twitter's business model&lt;/a&gt; or &lt;a href="http://dashes.com/anil/2012/04/why-you-cant-trust-tech-press-to-teach-you-about-the-tech-industry.html"&gt;Google's social features&lt;/a&gt; or anything else. We have to know what's been tried and failed, what good ideas were simply ahead of their time, and what opportunities have been lost in the current generation of dominant social networks.&lt;/blockquote&gt;
One of the things I really like about the web is that I know what it was like before the web was there and became so important in our lives. I can also remember the first steps 'web 2.0' brought us and how thrilled I was (and still am) about the next version of the web. After years in the internet and intranet version of the new web, I too am wondering if we're loosing it. I understand Dashes points to business models and what existing services are doing (building walls, cutting off integration opportunities based on RSS, etc.) as reasons for loosing the web. However, I wonder if we should ask even more fundamental questions. Web 2.0 and social media was about refinding our voice. More and more I see the services that helped us refind our voice are becoming less human (walling their garden, changing privacy settings, etc.). They're going against important statements from &lt;a href="http://www.cluetrain.com/"&gt;The Cluetrain Manifesto&lt;/a&gt;. And I see less and less people blogging and starting deep conversations (although I must say this is one of the reasons I love &lt;a href="https://plus.google.com/103105513170293090755/posts"&gt;Google+&lt;/a&gt;). Monetization of services has become more important than the core values of the new web.&lt;br /&gt;
&lt;br /&gt;
Or aren't we loosing it, but are we just getting started? Is it that the early adopters have to slow down and understand that the majority is just starting to understand the concepts and tools of the new web?&lt;br /&gt;
&lt;br /&gt;
Just when I wondered if Dashes would share his ideas about &lt;i&gt;rebuilding&lt;/i&gt; the web we lost, &lt;a href="http://dashes.com/anil/2012/12/rebuilding-the-web-we-lost.html"&gt;he posted his ideas&lt;/a&gt;. They are good ideas, even though they're focused on technology, design, funding, business models and the like. These could be good starting point, but as I just mentioned, I wonder if this cuts deep enough to really bring back the web we lost.&amp;nbsp;What do you think?&lt;br /&gt;
&lt;br /&gt;
UPDATE (5 minutes after publishing this post): My friend Ana Silva &lt;a href="http://artlifework.wordpress.com/2012/12/16/thinking-about-the-social-web/"&gt;recently blogged about this topic as well&lt;/a&gt;, pointing to Dashes' post and other related posts.&lt;br /&gt;
&lt;br /&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iUyh5TNuIVs:7SBYBcsRnw4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iUyh5TNuIVs:7SBYBcsRnw4:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iUyh5TNuIVs:7SBYBcsRnw4:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=iUyh5TNuIVs:7SBYBcsRnw4:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iUyh5TNuIVs:7SBYBcsRnw4:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=iUyh5TNuIVs:7SBYBcsRnw4:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iUyh5TNuIVs:7SBYBcsRnw4:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=iUyh5TNuIVs:7SBYBcsRnw4:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=iUyh5TNuIVs:7SBYBcsRnw4:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4305466190164153855?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4305466190164153855?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/12/is-our-web-slipping-away.html" title="Is our web slipping away?" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-Q-q9hxRRg20/UN25cSq2vcI/AAAAAAAALf4/vLzi82cD5Ac/s72-c/lostfound.jpg" height="72" width="72" /></entry><entry gd:etag="W/&quot;DkMMRnc-eyp7ImA9WhNVFk8.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-6121116872889378933</id><published>2012-12-27T17:08:00.001+01:00</published><updated>2012-12-27T17:08:07.953+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-27T17:08:07.953+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="education" /><category scheme="http://www.blogger.com/atom/ns#" term="social media" /><category scheme="http://www.blogger.com/atom/ns#" term="trends" /><category scheme="http://www.blogger.com/atom/ns#" term="guest lecture" /><title>Social Students?</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-HE0puYaqP7o/UNxyQgzqVjI/AAAAAAAALdI/YRTN-QSe2DE/s1600/Student.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="150" src="http://2.bp.blogspot.com/-HE0puYaqP7o/UNxyQgzqVjI/AAAAAAAALdI/YRTN-QSe2DE/s200/Student.jpg" width="200" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;a href="http://info-architecture.blogspot.nl/2012/10/re-which-social-media-do-millenials-use.html" target="_blank"&gt;What social tools are young people using&lt;/a&gt;? As a (internal) social media advisor for several companies I'm very interested in the answer to this question. So, when I get a change to talk for students, I'm honored, but also very curious what they will tell me.&lt;br /&gt;
&lt;br /&gt;
Recently I was asked to guest lecture for students at the &lt;a href="http://www.ru.nl/" target="_blank"&gt;Radboud University of Nijmegen&lt;/a&gt;. It's the university I went to years ago. I was asked to share my experience with using social media concepts and tools inside organizations. I basically used &lt;a href="http://www.slideshare.net/driessen/use-and-need-for-internal-social-media-concepts-and-tools" target="_blank"&gt;a shorter version&lt;/a&gt; of &lt;a href="http://www.slideshare.net/driessen/gastcollege-han-over-enterprise-20" target="_blank"&gt;the slides I use for my guest lectures for a college&lt;/a&gt;, but spent more time on the conceptual, philosophical if you will, side of 'social'.&lt;br /&gt;
I also asked them which social tools they use and why they use them. What did they say? Here's what I learned (there were 40+ students attending my lecture):&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;None use Google+. Why? Nobody/none of their friends is there.&lt;/li&gt;
&lt;li&gt;All except 3 use Facebook. The 3 that didn't use FB, just didn't see the value of using the service.&lt;/li&gt;
&lt;li&gt;None of the students blog. Some said they didn't because they thought nobody is interested in what they have to say. Some said they wanted to but didn't have time.&lt;/li&gt;
&lt;li&gt;There are no Hyves users in this class (Hyves is a Dutch social network).&lt;/li&gt;
&lt;li&gt;75% uses Twitter. Most use it to consume information, not publish/share it.&lt;/li&gt;
&lt;li&gt;They know Foursquare but don't use it.&lt;/li&gt;
&lt;li&gt;All have a LinkedIn account, but don't use it. It's for after their student-life.&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
Interesting, I find. It's pretty different from &lt;a href="http://info-architecture.blogspot.nl/2012/10/re-which-social-media-do-millenials-use.html" target="_blank"&gt;the usage pattern I collected while lecturing at a college&lt;/a&gt;. To me the most worrying answer is the one about blogging. At college and university hardly anybody blogs. I usually point to my blog and tell them what it brought and brings me. I hope that inspires them...&lt;/div&gt;
&lt;div&gt;
What's worrying to me is the reason why they don't blog: because they conclude what they think and would share is not interesting to others. And these students will be paid to think in the future. Wouldn't it be great if these young people would share their thoughts with us? I think so and hope they will in the future. The big question is: &lt;a href="http://info-architecture.blogspot.nl/2012/12/why-do-we-share.html" target="_blank"&gt;how do we get them to share&lt;/a&gt;?&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=OJUkrMAQlb0:6nsHxQaZvBo:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=OJUkrMAQlb0:6nsHxQaZvBo:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=OJUkrMAQlb0:6nsHxQaZvBo:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=OJUkrMAQlb0:6nsHxQaZvBo:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=OJUkrMAQlb0:6nsHxQaZvBo:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=OJUkrMAQlb0:6nsHxQaZvBo:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=OJUkrMAQlb0:6nsHxQaZvBo:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=OJUkrMAQlb0:6nsHxQaZvBo:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=OJUkrMAQlb0:6nsHxQaZvBo:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6121116872889378933?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6121116872889378933?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/12/social-students.html" title="Social Students?" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-HE0puYaqP7o/UNxyQgzqVjI/AAAAAAAALdI/YRTN-QSe2DE/s72-c/Student.jpg" height="72" width="72" /></entry><entry gd:etag="W/&quot;DkYCQX08eSp7ImA9WhNVFkw.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-4051384076355642291</id><published>2012-12-27T14:16:00.000+01:00</published><updated>2012-12-27T14:16:00.371+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-27T14:16:00.371+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="social networking" /><category scheme="http://www.blogger.com/atom/ns#" term="productivity" /><category scheme="http://www.blogger.com/atom/ns#" term="sharing" /><category scheme="http://www.blogger.com/atom/ns#" term="social media" /><category scheme="http://www.blogger.com/atom/ns#" term="email" /><title>Emailing with @elsua?</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-npvS8Dmf6tM/UNMrp5Vv7_I/AAAAAAAALVs/Qc8EURDHi1s/s1600/noemail.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://2.bp.blogspot.com/-npvS8Dmf6tM/UNMrp5Vv7_I/AAAAAAAALVs/Qc8EURDHi1s/s200/noemail.png" width="200" /&gt;&lt;/a&gt;&lt;/div&gt;
You all know &lt;a class="g-profile" href="http://plus.google.com/101335707221917520541" target="_blank"&gt;+Luis Suarez&lt;/a&gt;, right? The guy from IBM, that live on the Canary Islands and has &lt;a href="http://www.elsua.net/tag/a-world-without-email/" target="_blank"&gt;declared war on email&lt;/a&gt;. Well recently I wanted to get in touch with him to discuss an opportunity that popped up. Contacting him is easy, right? He’s all over social media. Just DM him &lt;a href="http://twitter.com/elsua" target="_blank"&gt;on Twitter&lt;/a&gt;, send a message via &lt;a href="https://plus.google.com/u/0/101335707221917520541/posts" target="_blank"&gt;Google+&lt;/a&gt; or Facebook. LinkedIn will do as well. I thought I’d share how it went. Did I seduce Luis to hand over his email address to me?&amp;nbsp;&lt;div&gt;
&lt;br /&gt;But what to do if you want to send him a longer piece of text? Do you request for his email address? I was tempted to but refrained to ask  because I knew I would be whipped by him. ;-) So I reached out to him via Twitter (direct message) and asked if we could call sometime soon. That was possible and we had a chat. But, still, I had to send him more information about the opportunity, about 10-15 lines of text. And I’m not going to chop this into 140 character messages. LinkedIn could work, but feels like email. I’m not connected to Luis in Facebook, so I couldn’t message him there either. So I left it up to him. And what did he choose? We had a one-on-one conversation in Google+. Which worked fine. There is no limitation to message link there. Although attachments can’t be sent, a link to it works as well. &lt;br /&gt;&lt;br /&gt;This does make me wonder: this one-on-one conversation is basically email in a social network. The shift of email-like communication to social networks is evident and understandable. But does it really make sense to move this kind of conversation there? Isn’t this the sweet spot of email and basically it’s best use case. To use it for one-on-one confidential conversation? I could think of two good reasons to move these kind of conversations to social nets: &lt;br /&gt;&lt;ol&gt;
&lt;li&gt;When we think the conversation might me opened up to a larger group later on. When the conversation has been held in the network where this group is, it can easily be shared with them.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;When social networks instead of email is de central hub of the knowledge worker. For most people this is not the case yet (just relate to what application you open first in the morning when you start working…).&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
So, what do you think? Are there other reasons to communicate one-on-one in social media instead of email? And how would you have interacted with Luis if you wanted something from him? &lt;br /&gt;&lt;br /&gt;By the way, Luis will be at the &lt;a href="http://www.congresintranet.nl/" target="_blank"&gt;2013 Intranet Conference&lt;/a&gt;&amp;nbsp;(the company I work for is the organizer). He’ll be sharing his thoughts on the skills of the knowledge worker in a keynote and in a pre-conference workshop he’ll be talking about ‘a world without email’. You can register &lt;a href="http://aanmelden.congresintranet.nl/" target="_blank"&gt;here&lt;/a&gt;!&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=qqef31BHX90:ioYfVmibwS0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=qqef31BHX90:ioYfVmibwS0:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=qqef31BHX90:ioYfVmibwS0:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=qqef31BHX90:ioYfVmibwS0:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=qqef31BHX90:ioYfVmibwS0:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=qqef31BHX90:ioYfVmibwS0:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=qqef31BHX90:ioYfVmibwS0:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=qqef31BHX90:ioYfVmibwS0:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=qqef31BHX90:ioYfVmibwS0:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4051384076355642291?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4051384076355642291?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/12/emailing-with-elsua.html" title="Emailing with @elsua?" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-npvS8Dmf6tM/UNMrp5Vv7_I/AAAAAAAALVs/Qc8EURDHi1s/s72-c/noemail.png" height="72" width="72" /></entry><entry gd:etag="W/&quot;D0ICQXoyfSp7ImA9WhNVE0g.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-6909724406057086205</id><published>2012-12-24T14:26:00.000+01:00</published><updated>2012-12-24T14:26:00.495+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-24T14:26:00.495+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="blog" /><category scheme="http://www.blogger.com/atom/ns#" term="blogging" /><title>Looking forward </title><content type="html">It’s that time of the year again when we look back and evaluate the year that has passed by so quickly. And lots like to make predictions for the year to come. I don’t want to share my predictions and my ponderings on the previous year. It has been an exciting year for me though. Many interesting projects, many interesting interactions with colleagues, customers and you. I moved from being a senior consultant to manager, visited interesting conferences, had discussions about and changes to the company I work for, etc. I’m just happy to have a great job, in times when many are looking for a job.&lt;br /&gt;&lt;br /&gt;I would like to thank you for the previous year. For reading my blog, thinking about things I’ve shared with you and the interactions we’ve had here and elsewhere. I’m looking forward to 2013 and hope you are to. &lt;br /&gt;&lt;br /&gt;&lt;b&gt;I wish you and all your loved ones happy holidays!&lt;/b&gt;&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=d4nuurrnjXs:O9GXkuz3TXQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=d4nuurrnjXs:O9GXkuz3TXQ:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=d4nuurrnjXs:O9GXkuz3TXQ:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=d4nuurrnjXs:O9GXkuz3TXQ:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=d4nuurrnjXs:O9GXkuz3TXQ:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=d4nuurrnjXs:O9GXkuz3TXQ:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=d4nuurrnjXs:O9GXkuz3TXQ:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=d4nuurrnjXs:O9GXkuz3TXQ:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=d4nuurrnjXs:O9GXkuz3TXQ:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6909724406057086205?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6909724406057086205?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/12/looking-forward.html" title="Looking forward " /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author></entry><entry gd:etag="W/&quot;DEEEQXg-cSp7ImA9WhNVEEQ.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-274087890743348773</id><published>2012-12-21T14:30:00.000+01:00</published><updated>2012-12-21T14:30:00.659+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-21T14:30:00.659+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="location" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge mapping" /><category scheme="http://www.blogger.com/atom/ns#" term="expertise location" /><title>I’ve seen the future and (part of) it’s Qbengo</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-mSiC9FJOgrM/UNMwhXGvj8I/AAAAAAAALWQ/iNDWYHggvNA/s1600/photo+(1).PNG" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://4.bp.blogspot.com/-mSiC9FJOgrM/UNMwhXGvj8I/AAAAAAAALWQ/iNDWYHggvNA/s200/photo+(1).PNG" width="133" /&gt;&lt;/a&gt;&lt;/div&gt;
In the past I’ve written quite a bit about &lt;a href="http://info-architecture.blogspot.nl/search/label/expertise%20location" target="_blank"&gt;expertise location and knowledge mapping&lt;/a&gt;. Expertise location is about supporting people to find people with certain expertise they’re looking for. In larger and multi-nationals organizations this is a big issue. One aspect about expertise location is also finding out where the person is. This can be a static location (e.g. the person works in room 3, building 4). This is difficult enough, but it can be done as I wrote some time ago.&lt;br /&gt;&lt;br /&gt;However, the workforce is more mobile than ever. Less and less employees have a fixed space they’re working in daily. They work in several rooms in an office during the week, they work from home, in the car, etc. Supporting expertise location in this context is even harder. In theory it can be done. I wrote about this as well. But I never saw a company actually connect the dots and make it work. Until recently. &lt;br /&gt;&lt;br /&gt;I had the pleasure to visit &lt;a href="http://www.qbengo.com/home" target="_blank"&gt;Qbengo&lt;/a&gt;. Qbengo is currently focused on connecting people at larger conferences. You’ve been there: a large conference with many booths. You have specific questions and would like to have them answered, but finding your way to the right person and/or booth, is hard. Furthermore, you don’t want to walk by all the booths, because that takes too much of your time. &lt;br /&gt;&lt;br /&gt;Qbengo has developed technology to support this process. They can quickly map out a conference location: the conference rooms, lunch area, booths, etc. By downloading there app you get access to these conference maps. But you can also register and connect with people and vendors there. When you set up a meeting with Qbengo you are subsequently helped to find that person or booth with turn-by-turn navigation inside the conference location. The cool thing is this also works in 3D. And this was exactly &lt;a href="http://info-architecture.blogspot.nl/2010/07/location-for-business-3d-required.html" target="_blank"&gt;one of the issues I pointed to some time ago&lt;/a&gt;. For (expertise) maps inside organizations to work, you would need 3D-mapping technology, because most offices are multi-layered. &lt;br /&gt;&lt;br /&gt;Qbengo is a start-up and a start-up needs focus. But you can easily see where I think they should and could go, right? Yep, expertise location for organizations. They have all the elements to make this work. This is (part of) our future and I think this is very exciting.&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=X8b3ImLa9wI:5In3GwfWO_U:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=X8b3ImLa9wI:5In3GwfWO_U:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=X8b3ImLa9wI:5In3GwfWO_U:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=X8b3ImLa9wI:5In3GwfWO_U:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=X8b3ImLa9wI:5In3GwfWO_U:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=X8b3ImLa9wI:5In3GwfWO_U:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=X8b3ImLa9wI:5In3GwfWO_U:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=X8b3ImLa9wI:5In3GwfWO_U:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=X8b3ImLa9wI:5In3GwfWO_U:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/274087890743348773?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/274087890743348773?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/12/ive-seen-future-and-part-of-its-qbengo.html" title="I’ve seen the future and (part of) it’s Qbengo" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-mSiC9FJOgrM/UNMwhXGvj8I/AAAAAAAALWQ/iNDWYHggvNA/s72-c/photo+(1).PNG" height="72" width="72" /></entry><entry gd:etag="W/&quot;DEcHQHc7eSp7ImA9WhNVEEw.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-6828024571851976038</id><published>2012-12-20T16:07:00.000+01:00</published><updated>2012-12-20T16:07:11.901+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-20T16:07:11.901+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="trust" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge sharing" /><category scheme="http://www.blogger.com/atom/ns#" term="sharing" /><category scheme="http://www.blogger.com/atom/ns#" term="reputation" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge management" /><title>Why do we share?</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-JFBPP8py1iY/UNMpgcji0aI/AAAAAAAALVI/FN2Y5WIPXJ8/s1600/Sharing.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" height="200" src="http://1.bp.blogspot.com/-JFBPP8py1iY/UNMpgcji0aI/AAAAAAAALVI/FN2Y5WIPXJ8/s200/Sharing.jpg" width="181" /&gt;&lt;/a&gt;&lt;/div&gt;
Maybe a better question is: why do I share? I was wondering about this while reading &lt;a href="http://plus.google.com/109479022314471643787"&gt;+Oscar Berg&lt;/a&gt;’s post ‘&lt;a href="http://www.thecontenteconomy.com/2012/09/why-do-people-share.html" target="_blank"&gt;Why do people share?&lt;/a&gt;’.&lt;br /&gt;Oscar makes several interesting statements about sharing in his post. Like this one: &lt;br /&gt;&lt;blockquote class="tr_bq"&gt;
The act of sharing something tells our colleagues something about us and that we think and care about what they might be interested in. If what we share is relevant and valuable to them, they will understand that we have really tried to understand what their needs and interests are. Their trust in us grows.  &lt;/blockquote&gt;
And, citing from &lt;a href="http://sloanreview.mit.edu/the-magazine/2010-winter/51213/how-reputation-affects-knowledge-sharing-among-colleagues/" target="_blank"&gt;an MIT Sloan article about reputation and knowledge sharing&lt;/a&gt;:&lt;br /&gt;&lt;blockquote class="tr_bq"&gt;
Reputation also plays a role where rules or systems are unable to spur sharing. Because critical information is often held privately by individuals, workers often can choose to share or withhold such information in their interactions with colleagues without fear of sanction. That leaves reputation as a key motivator in any decision to share or withhold information.&lt;/blockquote&gt;
Oscar also relates to the influence of culture on sharing. Furthermore, referring to another article, the content of what you share also depends on whether you’ll share it. People share content that will bring them ‘emotional communion’ and not all content is fit for that. &lt;br /&gt;&lt;br /&gt; And at the end of his post he points to &lt;a href="http://www.nancydixonblog.com/2009/03/the-incentive-question-or-why-people-share-knowledge.html" target="_blank"&gt;a post by Nancy Dixon&lt;/a&gt; in which see distinguishes two types of knowledge sharing. One is, in my own words, work-related, the other relation-related. Examples of the first are reports. Experiences are examples of the second. More interestingly, both types of sharing have different motivations. Only the second kind of sharing was done for personal benefit. &lt;br /&gt;&lt;br /&gt;Interesting stuff, I think. I’ve been &lt;a href="http://www.diigo.com/user/driessen/sharing" target="_blank"&gt;collecting articles about knowledge sharing&lt;/a&gt;&amp;nbsp;and &lt;a href="http://info-architecture.blogspot.nl/search/label/sharing" target="_blank"&gt;blogging about his topic&lt;/a&gt; for some time as well. It’s not an easy topic. And the above provide interesting insights, but only scratch the surface of this topic. &lt;br /&gt;&lt;br /&gt;At the end of Oscar’s post I was wondering what motivates Oscar to share. I can’t talk for Oscar, of course, but I will share why I share. To me there is one big reason to share information and knowledge (as far as I know them now): &lt;br /&gt; Share to learn: I share what I know and see with others because I want to learn. By wording my knowledge in text or speech in itself, helps me to learn. But I also hope to learn from the response I get from the person I’m addressing or that has asked me the question. I hardly withhold information from people. I will if I think that person does not respect me or will use the information in a wrong way. &lt;br /&gt;&lt;br /&gt;I think I can unpack this general reason and distill underlying reasons from it. These are: &lt;br /&gt;&lt;ol&gt;
&lt;li&gt;Share to show-off: to me there is definitely a show-off element to knowledge sharing. It’s not the most important one, but I do share to show what I know, read, bump into, etc.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Share to listen: an important part of learning to me is listening. So I enjoy what others are sharing, because it helps me learn. It also triggers me to share by posting things I find interesting and asking questions.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Share to remember: sharing information is also a way for me to capture things I find interesting. So I bookmark a link, tweet a link or statement, etc. In this way I’ve stored it for later use.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Share to be more effective: I share to learn and this helps me become more productive. Asking a question in my (digital) network, helps me find (partial) answers more quickly. Once I’ve written about something on my blog, I can refer to it later on. This makes more productive in the long run.&lt;/li&gt;
&lt;/ol&gt;
So, these are the reason for me to share. Do they make sense? What are your reasons to share?&lt;br /&gt;&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=PdG1TF2hG4Q:QFDxsnMZgss:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=PdG1TF2hG4Q:QFDxsnMZgss:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=PdG1TF2hG4Q:QFDxsnMZgss:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=PdG1TF2hG4Q:QFDxsnMZgss:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=PdG1TF2hG4Q:QFDxsnMZgss:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=PdG1TF2hG4Q:QFDxsnMZgss:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=PdG1TF2hG4Q:QFDxsnMZgss:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=PdG1TF2hG4Q:QFDxsnMZgss:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=PdG1TF2hG4Q:QFDxsnMZgss:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6828024571851976038?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6828024571851976038?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/12/why-do-we-share.html" title="Why do we share?" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-JFBPP8py1iY/UNMpgcji0aI/AAAAAAAALVI/FN2Y5WIPXJ8/s72-c/Sharing.jpg" height="72" width="72" /></entry><entry gd:etag="W/&quot;CUQERno9fSp7ImA9WhNXF0U.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-4749994514368469621</id><published>2012-11-27T14:00:00.000+01:00</published><updated>2012-12-06T09:41:47.465+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-06T09:41:47.465+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="trust" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge work" /><category scheme="http://www.blogger.com/atom/ns#" term="productivity" /><title>Satisfying Knowledge Worker Values</title><content type="html">&lt;blockquote class="tr_bq"&gt;
Bribing the knowledge workers on whom these industries [of the Information Revolution] depend will therefore simply not work. The key knowledge workers in these businesses will surely continue to expect to share financially in the fruits of their labor. But the financial fruits are likely to take much longer to ripen, if they ripen at all. And then, probably within ten years or so, running a business with (short-term) "shareholder value" as its first—if not its only—goal and justification will have become counterproductive. Increasingly, performance in these new knowledge-based industries will come to depend on running the institution so as to attract, hold, and motivate knowledge workers. When this can no longer be done by satisfying knowledge workers' greed, as we are now trying to do, it will have to be done by satisfying their values, and by giving them social recognition and social power. It will have to be done by turning them from subordinates into fellow executives, and from employees, however well paid, into partners.&lt;/blockquote&gt;
&lt;div&gt;
This was written in 1999 by Peter Drucker (&lt;i&gt;&lt;a href="http://www.theatlantic.com/magazine/archive/1999/10/beyond-the-information-revolution/304658/" target="_blank"&gt;Beyond the Information Revolution&lt;/a&gt;&lt;/i&gt;). We still have long way to go...&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=8VTAaBg6d2o:PdeyMukWUno:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=8VTAaBg6d2o:PdeyMukWUno:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=8VTAaBg6d2o:PdeyMukWUno:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=8VTAaBg6d2o:PdeyMukWUno:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=8VTAaBg6d2o:PdeyMukWUno:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=8VTAaBg6d2o:PdeyMukWUno:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=8VTAaBg6d2o:PdeyMukWUno:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=8VTAaBg6d2o:PdeyMukWUno:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=8VTAaBg6d2o:PdeyMukWUno:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4749994514368469621?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/4749994514368469621?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/11/satisfying-knowledge-worker-values.html" title="Satisfying Knowledge Worker Values" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author></entry><entry gd:etag="W/&quot;Dk8FQ30yfip7ImA9WhNQGU4.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-1450107048529829818</id><published>2012-11-26T14:00:00.000+01:00</published><updated>2012-11-26T14:00:12.396+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-11-26T14:00:12.396+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="trust" /><category scheme="http://www.blogger.com/atom/ns#" term="productivity" /><category scheme="http://www.blogger.com/atom/ns#" term="knowledge worker" /><category scheme="http://www.blogger.com/atom/ns#" term="information overload" /><category scheme="http://www.blogger.com/atom/ns#" term="email" /><title>What's the real issue with Information Overload?</title><content type="html">What's the real problem underlying information overload? Nathan Zeldes has been finding answers to this question for years. Recently he wrote a &lt;a href="http://www.nathanzeldes.com/blog/2012/09/the-dark-side-of-information-overload/" target="_blank"&gt;must-read post&lt;/a&gt; on the answers he found. There are all kinds of reasons we keep on using email in an unproductive way. But the underlying issue, according to Zeldes, is &lt;b&gt;mistrust&lt;/b&gt;. To solve the information overload problem within organizations we need to address this "dark side" of overload. If we don't we'll never structurally solve the problem. Address this dark side and change the underlying culture, Zeldes advises.&lt;br /&gt;
&lt;br /&gt;
I agree this is a way to fundamentally root out mistrust. But what if this is not possible? What if the company just doesn't see the problem and therefore does not want to spend time on this extermination process?&lt;br /&gt;
I think every person can start by settting an example. Be counter-cultural! Show how the way you use email is more effective and productive. It's the long bottom-up approach, but this road empowers you, instead of waiting and complaining until "the rest of the company" gets it and starts the "improve trust program".&lt;br /&gt;
&lt;br /&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=UO_quhjnpAE:ASH4e9f6hds:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=UO_quhjnpAE:ASH4e9f6hds:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=UO_quhjnpAE:ASH4e9f6hds:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=UO_quhjnpAE:ASH4e9f6hds:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=UO_quhjnpAE:ASH4e9f6hds:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=UO_quhjnpAE:ASH4e9f6hds:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=UO_quhjnpAE:ASH4e9f6hds:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=UO_quhjnpAE:ASH4e9f6hds:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=UO_quhjnpAE:ASH4e9f6hds:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/1450107048529829818?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/1450107048529829818?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/11/whats-real-issue-with-information.html" title="What's the real issue with Information Overload?" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author></entry><entry gd:etag="W/&quot;CEANQnw8eip7ImA9WhNQFkU.&quot;"><id>tag:blogger.com,1999:blog-312551883381829534.post-6338619168254866797</id><published>2012-11-23T15:59:00.004+01:00</published><updated>2012-11-23T15:59:53.272+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-11-23T15:59:53.272+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="social networking" /><category scheme="http://www.blogger.com/atom/ns#" term="social media" /><category scheme="http://www.blogger.com/atom/ns#" term="email" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise 2.0" /><category scheme="http://www.blogger.com/atom/ns#" term="social business" /><title>Email integrated with Social Software</title><content type="html">&lt;a href="http://twitter.com/chieftech"&gt;James Dellow&lt;/a&gt; has a &lt;a href="http://chieftech.com.au/post/is-email-really-the-nemesis-of-better-collaboration-software"&gt;nice post&lt;/a&gt; researching the history of email and why email is so successful. More importantly he wonders what this means for social tools and their success. He concludes his post with the following:&lt;br /&gt;&lt;blockquote class="tr_bq"&gt;
Enterprise social software can also learn some important lessons from email:&lt;ul&gt;
&lt;li&gt;We need interoperability between enterprise social systems.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;Users prefer standardised interfaces.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;It needs to be cost effective to own and operate.&lt;/li&gt;
&lt;/ul&gt;
Far from being a nemesis, email and enterprise social software are more likely to form a strong symbiotic relationship.&lt;/blockquote&gt;
I've been thinkings and &lt;a href="http://info-architecture.blogspot.nl/search/label/email" target="_blank"&gt;blogging&lt;/a&gt; about this topic quite a bit as well. I did research and product concept development on document management tools in the past. One of the things we said back then is: integrate document management into email. I think this principle still applies. I also think the killer social tools will be deeply integrated into/with email. For that reason I think Google+ has a good chance of winning the social game. People want one spot to do a lot of different things. They &lt;a href="http://dl.acm.org/citation.cfm?id=383305" target="_blank"&gt;live in their inbox&lt;/a&gt;. To me the holy grail is to have a platform from which you can easily share content to email, to social nets, etc. Don't worry this will lead to less email, not more.&lt;br /&gt;&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=Tfl1vDkHrf8:eoWWeJFvMJM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=Tfl1vDkHrf8:eoWWeJFvMJM:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=Tfl1vDkHrf8:eoWWeJFvMJM:F7zBnMyn0Lo"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=Tfl1vDkHrf8:eoWWeJFvMJM:F7zBnMyn0Lo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=Tfl1vDkHrf8:eoWWeJFvMJM:V_sGLiPBpWU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=Tfl1vDkHrf8:eoWWeJFvMJM:V_sGLiPBpWU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=Tfl1vDkHrf8:eoWWeJFvMJM:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/Infoarch?a=Tfl1vDkHrf8:eoWWeJFvMJM:gIN9vFwOqvQ"&gt;&lt;img src="http://feeds.feedburner.com/~ff/Infoarch?i=Tfl1vDkHrf8:eoWWeJFvMJM:gIN9vFwOqvQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6338619168254866797?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/312551883381829534/posts/default/6338619168254866797?v=2" /><link rel="alternate" type="text/html" href="http://info-architecture.blogspot.com/2012/11/email-integrated-with-social-software.html" title="Email integrated with Social Software" /><author><name>Samuel Driessen</name><uri>https://plus.google.com/103105513170293090755</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh3.googleusercontent.com/-UVG3KOnylxw/AAAAAAAAAAI/AAAAAAAAOIc/HSNZsL0XBgU/s512-c/photo.jpg" /></author></entry></feed>
