<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
		xmlns:content="http://purl.org/rss/1.0/modules/content/"
		xmlns:wfw="http://wellformedweb.org/CommentAPI/"
		xmlns:dc="http://purl.org/dc/elements/1.1/"
		xmlns:atom="http://www.w3.org/2005/Atom"
		xmlns:sy="http://purl.org/rss/1.0/modules/syndication/">
<channel>
<title>Communal Osmosis</title>
<atom:link href="http://www.communalosmosis.com/" rel="self" type="application/rss+xml" />
<link>http://www.communalosmosis.com/index.php?option=com_lyftenbloggie&amp;task=feed&amp;type=rss&amp;Itemid=1</link>
<description>Spreading and sharing whats working in software</description>
<pubDate>2010-11-28 20:24:05</pubDate>
<language>English (United Kingdom)</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<item>
<title>Wandering Thoughts and Self-Reflection</title>
<link>/index.php?option=com_lyftenbloggie&amp;amp;view=entry&amp;amp;year=2010&amp;amp;month=11&amp;amp;day=28&amp;amp;id=27:wandering-thoughts-and-self-reflection&amp;amp;Itemid=1</link>
<comments>/index.php?option=com_lyftenbloggie&amp;amp;view=entry&amp;amp;year=2010&amp;amp;month=11&amp;amp;day=28&amp;amp;id=27:wandering-thoughts-and-self-reflection&amp;amp;Itemid=1#comment</comments>
<dc:creator>Joel Tosi</dc:creator>
<category><![CDATA[Uncategorized]]></category>
<description>I was sitting in a technology conference session recently and, rather quickly, started focusing more on the presenter than the content (perhaps because the content was less than stellar).  Either way, this sta</description>
<content:encoded><p style="margin-bottom: 0in;">I was sitting in a technology conference session recently and, rather quickly, started focusing more on the presenter than the content (perhaps because the content was less than stellar).  Either way, this started me thinking how much easier it is to find faults than fix our own.<img src="http:www.communalosmosis.comimagesstorieslemonade.jpg" border="0" style="float: right;" ><p>
<p style="margin-bottom: 0in;">This may seem obvious, but just think about it – even in positions of inferiority (in a session to learn or discovering how to create a product) – it is more natural for us to find faults in others or a process than actively work on resolving our own or helping others to improve.<p>
<p style="margin-bottom: 0in;">I see this most commonly with teams that are looking to create more collaborative environments – the transparency to some becomes quite scary.  And so they lash out.  Developers will attack testers - ‘Their job is to find bugs.’  ‘They don’t automate enough.’  Business sponsors will question development motives - ‘They just pad their estimates so I know its not real.’<p>
<p style="margin-bottom: 0in;">When I work with teams where I see this, I try and stress getting people talking and understanding each other on a personal level.  From there, I stress simple, obvious facts – no one is here trying to sabotage a project  everyone is trying to contribute as much as they can.  If we can start from that common understanding, and honestly believe it, then we are taking the first step towards creating an environment that is high with personal safety as well as honest, constructive feedback.  Without that as a basis, any gains we make as a team will be on fragile ground.<p>
<p>Quite often, the role of a coach feels like a counselor or a psychiatrist – and part of it really is.  Our job, as leaders is to foster an environment were people can become more not only become team reflective, but also honestly self-reflective.<p></content:encoded>
<pubDate>Sun, 28 Nov 2010 20:24:05 -0600</pubDate>
<guid isPermaLink="false">/index.php?option=com_lyftenbloggie&amp;amp;view=entry&amp;amp;year=2010&amp;amp;month=11&amp;amp;day=28&amp;amp;id=27:wandering-thoughts-and-self-reflection&amp;amp;Itemid=1</guid>
<wfw:commentRss>http://www.communalosmosis.com/index.php?option=com_lyftenbloggie&amp;amp;task=feed&amp;amp;type=rss2&amp;amp;id=27&amp;amp;Itemid=1</wfw:commentRss>
</item>
<item>
<title>Who wants to be an Evangelist</title>
<link>/index.php?option=com_lyftenbloggie&amp;amp;view=entry&amp;amp;year=2010&amp;amp;month=10&amp;amp;day=26&amp;amp;id=26:who-wants-to-be-an-evangelist&amp;amp;Itemid=1</link>
<comments>/index.php?option=com_lyftenbloggie&amp;amp;view=entry&amp;amp;year=2010&amp;amp;month=10&amp;amp;day=26&amp;amp;id=26:who-wants-to-be-an-evangelist&amp;amp;Itemid=1#comment</comments>
<dc:creator>Joel Tosi</dc:creator>
<category><![CDATA[Product]]></category>
<description>I consider myself lucky to have a varying group of individuals that I have met over the years with whom I can speak rather frankly ab</description>
<content:encoded><p><img src="http:www.communalosmosis.comimagesstoriesbakkersnl.jpg" border="0" width="175" align="right" >I consider myself lucky to have a varying group of individuals that I have met over the years with whom I can speak rather frankly about products - not just delivery but discovery.  I have seen an interesting pattern evolving - people want evangelists.  Gone are the days where it was enough to be a solid developer, great requirements writer, or an effective manager.  The times - they are a changing - and that is a really good thing.<p>
<p>I was speaking with a colleague a few weeks back who was working on somewhat of a startup and was using outsourced development.  He asked me a seemingly loaded question - 'How come the developers only care about me telling them exactly what I want, then they hide off and come back with something I don't need?' 'Well,' I responded, 'you are working with the wrong developers.'  By nature, the outsourced model is designed to remove any collaboration and focus strictly on savings based upon contractual obligations.  Perhaps a better name would be 'sunkcosting'.<p>
<p>The above scenario isn't limited to just outsourced development or startups.  I see this scenario wherever there is a separation of delivery team from product - whether it be created by the company or by the individuals.<p>
<p>Take this as another example - a buddy of mine works at a pretty hip, larger 'entertainment' software company.  He calls me up one morning fuming. 'Joel, all the developers cared about was getting home.  The launch was busted and they just said they would fix it Monday.  WTF?'<p>
<p>The above scenario has other issues - finding out a launch is broke when you roll it out probably has a root cause further down the stack - but the sentiments are still the same.  People on that product team weren't passionate about the product.  Had they been, there is no way that they would have left their product to rot and aggravate customers until someone rolls out of bed to look at it.  More than likely, with a passionate and engaged team, the product either wouldn't have rolled out or the problems would have been flushed out sooner simply by the team banging so much on the product they are creating.<p>
<p><img src="http:www.communalosmosis.comimagesstoriesmessage.jpg" border="0" width="175" align="left" >What can  should you do about this?  Simple - be excited about something and work on it.  There are two types of people at work - those that are excited and want to do  make something better; those that are complacent and would rather not be bothered.  Be excited and passionate, it is far more rewarding.  If you are on the hiring side - look for people with passion and drive.  Skills can easily be taught, complacency is something that will cost you ten-fold to try and remove.<p>
<p>Short feedback loops are not only great for the quality of a product, but they are also great for looking at the dynamics of a team.  Use your team to its fullest - get everyone engaged with the product.  Make them evangelists.<p>
<p> <p></content:encoded>
<pubDate>Tue, 26 Oct 2010 07:07:59 -0500</pubDate>
<guid isPermaLink="false">/index.php?option=com_lyftenbloggie&amp;amp;view=entry&amp;amp;year=2010&amp;amp;month=10&amp;amp;day=26&amp;amp;id=26:who-wants-to-be-an-evangelist&amp;amp;Itemid=1</guid>
<wfw:commentRss>http://www.communalosmosis.com/index.php?option=com_lyftenbloggie&amp;amp;task=feed&amp;amp;type=rss2&amp;amp;id=26&amp;amp;Itemid=1</wfw:commentRss>
</item>
</channel>
</rss>

