<?xml version="1.0"?>
<!-- RSS generated by Radio UserLand v8.0.8 on Mon, 18 Aug 2003 10:43:11 GMT -->
<rss version="2.0">
	<channel>
		<title>rodcorp: rodcorp: Projects and teams</title>
		<link>http://radio.weblogs.com/0105728/categories/projectsAndTeams/</link>
		<description>Project management, team management</description>
		<copyright>Copyright 2003 rodcorp</copyright>
		<lastBuildDate>Mon, 18 Aug 2003 10:43:11 GMT</lastBuildDate>
		<docs>http://backend.userland.com/rss</docs>
		<generator>Radio UserLand v8.0.8</generator>
		<managingEditor>rodmcl@yahoo.com</managingEditor>
		<webMaster>rodmcl@yahoo.com</webMaster>
		<category domain="http://www.weblogs.com/rssUpdates/changes.xml">rssUpdates</category> 
		<skipHours>
			<hour>2</hour>
			<hour>3</hour>
			<hour>4</hour>
			<hour>5</hour>
			<hour>6</hour>
			<hour>1</hour>
			<hour>20</hour>
			<hour>9</hour>
			</skipHours>
		<cloud domain="radio.xmlstoragesystem.com" port="80" path="/RPC2" registerProcedure="xmlStorageSystem.rssPleaseNotify" protocol="xml-rpc"/>
		<ttl>60</ttl>
		<item>
			<title>Rodcorp is moving home</title>
			<link>http://rodcorp.typepad.com/rodcorp/</link>
			<description>New home is &lt;a href=&quot;http://rodcorp.typepad.com/rodcorp/&quot;&gt;chez Typepad&lt;/a&gt;.</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/08/18.html#a494</guid>
			<pubDate>Mon, 18 Aug 2003 10:41:17 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=494&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F08%2F18.html%23a494</comments>
			</item>
		<item>
			<title>Ross Mayfield: interruption &apos;taxes&apos; in IM, email, phonecalls</title>
			<link>http://radio.weblogs.com/0114726/2002/12/31.html#a171</link>
			<description>includes good stats for Peopleware fans. As you&apos;d expect, generally an inverse relationship between how personal and &apos;intense&apos; the type of interruption is (phonecall, email etc) and time-to-recover-from-interruption, except that IM (which has more presence than email) may extract a lower interruption tax. Another reason to use it in the office?</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/08/13.html#a492</guid>
			<pubDate>Wed, 13 Aug 2003 10:59:28 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=492&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F08%2F13.html%23a492</comments>
			</item>
		<item>
			<title>Businesses: managing real-time communications critical</title>
			<link>http://ross.typepad.com/blog/2003/08/information_bat.html</link>
			<description>Businesses: managing real-time communications is as important as managing real-time processes. Put another way: PR is increasingly an internal exercise because external PR just happens, leaks out of the company via your employees. So, Ross says, trust your employees, teach them and empower them. Trust being the key verb here. (cf Cluetrain of course, and Semler/Semco.) </description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/08/13.html#a491</guid>
			<pubDate>Wed, 13 Aug 2003 10:55:05 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=491&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F08%2F13.html%23a491</comments>
			</item>
		<item>
			<title>Designers: selling down not up</title>
			<link>http://www.eleganthack.com/archives/003407.html#003407</link>
			<description>Politics considered helpful in the selling-your-design game.
&lt;blockquote&gt;
The title itself -- Make It Bigger-- refers to Paula&apos;s endless battle to help clients be able to see the design clearly, and accept it without the layers of hierarchy pissing on it (my words, not hers). By end running the hierarchy and then selling down rather than up, she is able to avoid watered-down design arriving for final approval.
&lt;/blockquote&gt;</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/08/13.html#a490</guid>
			<pubDate>Wed, 13 Aug 2003 10:49:04 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=490&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F08%2F13.html%23a490</comments>
			</item>
		<item>
			<title>Agile development = being ready to ship at any time?</title>
			<link>http://www.darrenhobbs.com/archives/000465.html</link>
			<description>Darren Hobbs sez that agile means being ready to ship (literally, shrinkwrap and shelve up) whatever work you&apos;ve done at any point throughout the project. Guards against the risk of the project being cancelled, though arguably if something is ready to go at all times &lt;em&gt;and&lt;/em&gt; that thing meets some of the project goals, the project probably won&apos;t get whacked. Also: possible risk of not making sufficient progress in fear of breaking the product?
&lt;br /&gt;
&lt;br /&gt;
Looking at &quot;agile&quot; as it relates to the team rather than the project itself, the other &quot;thing&quot; that is ready to ship when a project is whacked is the team, what it has learned (individually and collectively), and its willingness/interest in going on to the next project and doing good. Not that these are necessarily all positive values: disillusionment and fear of failure are big risks in teams that have had projects cancelled.
&lt;br /&gt;
&lt;br /&gt;
See also the &lt;a href=&quot;http://www.agilealliance.org&quot;&gt;Agile Alliance&lt;/a&gt;, and its &lt;a href=&quot;http://www.agilemanifesto.org/&quot;&gt;manifesto&lt;/a&gt;:
&lt;blockquote&gt;
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Individuals and interactions&lt;/em&gt; over processes and tools
&lt;br /&gt;
&lt;em&gt;Working software&lt;/em&gt; over comprehensive documentation
&lt;br /&gt;
&lt;em&gt;Customer collaboration&lt;/em&gt; over contract negotiation
&lt;br /&gt;
&lt;em&gt;Responding to change&lt;/em&gt; over following a plan
&lt;br /&gt;
&lt;br /&gt;
That is, while there is value in the items on the right, we value the items on the left more. 
&lt;/blockquote&gt;
Worth reading.</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/08/08.html#a485</guid>
			<pubDate>Fri, 08 Aug 2003 15:54:56 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=485&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F08%2F08.html%23a485</comments>
			</item>
		<item>
			<title>AIGA: Understanding The Future Of Mobile Devices</title>
			<link>http://radio.weblogs.com/0105728/stories/2003/08/07/understandingTheFutureOfMobileDevices.html</link>
			<description>Notes taken at this event, ably led by Nico MacDonald.</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/08/07.html#a481</guid>
			<pubDate>Thu, 07 Aug 2003 18:34:39 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=481&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F08%2F07.html%23a481</comments>
			</item>
		<item>
			<title>WIP: Lament: music for printer and five voices</title>
			<link>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/30.html#a469</link>
			<description>I walked into the open-plan office upstairs and heard the girls mournfully talking about how the new printer was no good. I asked whether it was slow, or had poor print quality. No: they didn&amp;#146;t like the newly upgraded printer&amp;#146;s song, which was mechanical and annoying. The old printer&amp;#146;s noise had been repetitive but musical, so they used to sing along with it when it did a large run of flow charts. I asked them what the old printer song had been like, and one of them started humming it to me. Gradually the others joined in until there were about five of them humming it, in remembrance.</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/30.html#a469</guid>
			<pubDate>Wed, 30 Jul 2003 20:50:37 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=469&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F30.html%23a469</comments>
			</item>
		<item>
			<title>Books read in 2002, 2003</title>
			<link>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/30.html#a468</link>
			<description>Rodcorp&apos;s books read in &lt;a href=&quot;http://www.rodcorp.com/stories/2003/07/30/rodcorpsBooksIn2003.html&quot;&gt;2003&lt;/a&gt; (now you know what we&apos;ve been doing instead of working) and &lt;a href=&quot;http://www.rodcorp.com/stories/2003/03/20/rodcorpsBooksIn2002.html&quot;&gt;2002&lt;/a&gt;.</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/30.html#a468</guid>
			<pubDate>Wed, 30 Jul 2003 20:45:23 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=468&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F30.html%23a468</comments>
			</item>
		<item>
			<title>The Origins of Things: Sketches, Models, Prototypes</title>
			<link>http://www.amazon.com/exec/obidos/ASIN/9056623184</link>
			<description>&lt;blockquote&gt;
illuminates the process by which designers transform their often groundbreaking ideas into functional, manufacturable products. Drawings, cardboard models stuck together with tape and ultramodern computer animations are more significant here than the finished products, for they illuminate the designer&apos;s process in a way that the finished product--unless it is a deconstructive design object!--does not
&lt;/blockquote&gt;
&lt;a href=&quot;http://www.amazon.co.uk/exec/obidos/ASIN/9056623184&quot;&gt;Buy in UK&lt;/a&gt;. Incidentally, &lt;a href=&quot;http://www.amazon.co.uk/exec/obidos/external-search/202-3127684-8116665?mode=books&amp;keyword=The+Origins+of+Things&amp;tag=365com&amp;Go.x=3&amp;Go.y=11&amp;Go=Go&quot;&gt;some interesting looking related books here too&lt;/a&gt;.
&lt;br /&gt;
[via &lt;a href=&quot;http://www.machinelake.com/archives/000960.html#000960&quot;&gt;MachineLake&lt;/a&gt;]
</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/21.html#a456</guid>
			<pubDate>Mon, 21 Jul 2003 20:07:12 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=456&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F21.html%23a456</comments>
			</item>
		<item>
			<title>Cabinets of Curiosity: desktops of designers</title>
			<link>http://www.metropolismag.com/html/content_0703/cab/index.html</link>
			<description>&amp;quot;For designers who collect, the cluttered workspace is a library of inspiration&amp;quot;. The desks of designers Rob Cristofaro, 
Maira Kalman, Scott Stowell and Milton Glaser.
&lt;br /&gt;
[via &lt;a href=&quot;http://www.machinelake.com/archives.html&quot;&gt;MachineLake&lt;/a&gt;, itself via &lt;a href=&quot;http://www.manamplified.org/&quot;&gt;manAmplified&lt;/a&gt;]
</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/21.html#a455</guid>
			<pubDate>Mon, 21 Jul 2003 20:06:44 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=455&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F21.html%23a455</comments>
			</item>
		<item>
			<title>Bike courier culture, alley cat racing</title>
			<link>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/21.html#a454</link>
			<description>This weekend we met a bunch of bike couriers at a barbecue. Interesting people, with a strong sub-culture - sub in the sense that non-couriers know very little about what they are like, how couriering works etc. Unsurprisingly, most of them are mad about bikes, and it&apos;s a way to earn a crust. So there was much talk of the Tour de France. They knew only one person who&apos;d gone on from couriering to &apos;proper&apos; road racing. There are 600-1000 couriers working London at any one time, and they do about 70-80 miles a day in town, mostly within the Circle line area, though they may travel further west to Notting Hill, and further east to the Docklands. This bunch had a strong sense of identity and shared culture/community. Some have expensively tricked-out rides, some something seemingly more standard (the playoffs between lightness/efficiency, reliability and cost being the key equations couriers run in choosing the tools of their trade), with single/no brakes and single gears common.
&lt;br /&gt;
&lt;br /&gt;
About 50+ of the London couriers are into &quot;alley cat racing&quot;: illegal checkpoint-to-checkpoint race where the racers only know the next checkpoint. Ie: orienteering on a bike, in (and often against) the traffic. AC Racing was imported from US couriers in the mid-90s. Last night they showed a video made by film students by mounting a camera on one of the alley cat racers. 8 minutes of crazy, often-dangerous riding through traffic and people; ends with the cyclist getting hit by a truck when he attempted to zoom across a red-light and straight across the traffic going both ways (he&apos;d successfully done this a few times already in the film). He wasn&apos;t hurt too badly, but the bike probably was. &quot;Oh well, that&apos;s racing&quot;, he concludes.
&lt;br /&gt;
&lt;br /&gt;
Even though you don&apos;t quite get a sense of the true speed on film, it was fantastic, and reminiscent of several other illegal car or motorbike films (Claude Lelouch&apos;s infamous C&apos;etait un Rendezvous, the Getaway in Stockholm films, Black Prince Peripherique).
&lt;br /&gt;
&lt;br /&gt;
Couriers, alley cat racing, etc:
&lt;ul&gt;
&lt;li&gt;
some somewhat dark &lt;a href=&quot;http://www.dccourier.com/video/&quot;&gt;alley cat video at DC Courier&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&quot;http://www.google.com/search?q=alley%20cat%20race&quot;&gt;Google for &apos;alley cat race&apos;&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
Travis Culley&apos;s &lt;a href=&quot;http://www.amazon.co.uk/exec/obidos/ASIN/0375760245&quot;&gt;The Immortal Class: Bike Messengers and the Cult of Human Power&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&quot;http://www.londonmessengers.org/&quot;&gt;London Bicycle Messenger Association&lt;/a&gt; (who also have a print(?) newsletter called &lt;a href=&quot;http://www.londonmessengers.org/mt.html&quot;&gt;Moving Target&lt;/a&gt;)
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&quot;http://www.bikereader.com/BikeReader/BikeReader.html&quot;&gt;bikereader.com&lt;/a&gt;: a rider&apos;s digest of essays, humour etc
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&quot;http://www.massbike.org/info/movies.htm&quot;&gt;various bike movies&lt;/a&gt; (list), &lt;a href=&quot;http://www.bicyclecam.com/index.htm&quot;&gt;BicycleCam&lt;/a&gt; (races filmed from the bike)
&lt;/li&gt;
&lt;/ul&gt;
Other films:
&lt;ul&gt;
&lt;li&gt;
&lt;a href=&quot;http://enjoyment.independent.co.uk/film/features/story.jsp?story=382314&quot;&gt;Claude Lelouch&apos;s infamous C&apos;etait un Rendezvous&lt;/a&gt;, a 9-minute 1973 short film in which he races his Ferrari through an empty night-time Paris. &lt;a href=&quot;http://s73322911.oneandoneshop.co.uk/site/moreinforend.html&quot;&gt;Buy Rendezvous here&lt;/a&gt;. (Lelouch also did a Tour de France film, &lt;a href=&quot;http://www.amazon.co.uk/exec/obidos/ASIN/B00004CVGP&quot;&gt;Pour Un Maillot Jaune&lt;/a&gt;)
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&quot;http://books.motortraders.net/books/item.asp?code=1589&quot;&gt;Black Prince Peripherique&lt;/a&gt;, in which a Kawasaki is raced round the 35km Paris peripherique in morning traffic. You can also &lt;a href=&quot;http://www.amazon.co.uk/exec/obidos/ASIN/B00006SKX6&quot;&gt;buy Periperique here&lt;/a&gt;.
&lt;/li&gt;
&lt;li&gt;
the &lt;a href=&quot;http://www.getawayinstockholm.com/main.html&quot;&gt;Getaway in Stockholm films&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
(Update: &lt;a href=&quot;http://www.exo.org.uk&quot;&gt;Struan&lt;/a&gt; correctly reminds us that alley cat racing perpetuates the image of &apos;cyclists as arrogant, self-righteous grumps with only limited respect for the law&apos;. Which, together with the rest of us non-courier cyclists going through red lights, really doesn&apos;t help. Perhaps the racing is symptomatic of a bike culture that sees itself as *against* motor traffic. Alley cat racing isn&apos;t safe or particularly clever, but we have to admit it was quite exciting to watch.)</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/21.html#a454</guid>
			<pubDate>Mon, 21 Jul 2003 19:35:01 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=454&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F21.html%23a454</comments>
			</item>
		<item>
			<title>IDEO: Give email a timeline</title>
			<link>
http://www.technologyreview.com/articles/wo_brown062503.asp</link>
			<description>Tim Brown, CEO of IDEO, interviews with Master of Design MIT Tech Review (free reg reqd). Two interesting nuggets: first a slightly confusing vision of email + blog-like timeline = good way to organise (confusing to us anyway: we&apos;re not sure how this is significantly different from sorting emails by Received):
&lt;blockquote&gt;
There&apos;s something about e-mail that demands a reply, demands a response. But when you&apos;re getting thousands of these things, it becomes an impossibility to respond to everything. So we&apos;ve got to shift the etiquette, and maybe make e-mail more like publishing: that is, you send something out and you might get one percent response. I think that the paradigm of e-mail as letters, as objects, is inappropriate. I&apos;m waiting for a shift to the timeline, rather than the object, as the organizing principle.  If you think about a blog for instance, that&apos;s a timeline. And it&apos;s a really good way of organizing huge amounts of information, because we&apos;re quite good at sequencing. We&apos;re quite good at remembering when things happen. That has meaning for us. But imagine creating an individual document around every one of those individual blog entries and just having them there on your desktop or in a folder. It would be completely meaningless to you. And that&apos;s how we treat e-mail now. But imagine keeping e-mail a bit more like a blog. Then suddenly, you&apos;ve got instant messaging qualities and e-mail qualities happening at the same time.  So I&apos;m guessing that we&apos;ll start to see that sort of timeline become more and more important. Because I think it&apos;s the way that we as human beings tend to organize massive amounts of data.
&lt;/blockquote&gt;
And here&apos;s the well-known IDEO formulation of design as an often-*subtractive* process:
&lt;blockquote&gt;
The naive view of designing is that it&apos;s purely an additive process, about adding more and more and more. Actually, design is a funnel-shaped thing. It becomes an editing process: What is appropriate? What can be stripped away? So design is a holistic way of thinking. It&apos;s about being able to create the whole of something, and in such a way that somebody who&amp;#146;s using that product, whether for the first time or the tenth time, understands it can interact with it as seamlessly as possible
&lt;/blockquote&gt;</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/21.html#a453</guid>
			<pubDate>Mon, 21 Jul 2003 19:33:06 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=453&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F21.html%23a453</comments>
			</item>
		<item>
			<title>Three sets of cards to help your head make connections faster</title>
			<link>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/18.html#a452</link>
			<description>&lt;ol&gt;
&lt;li&gt;
Brian Eno and Peter Schmidt&apos;s &lt;a href=&quot;http://www.enoshop.co.uk/index.php?product_id=8&quot;&gt;Oblique Strategies&lt;/a&gt;: One hundred worthwhile dilemmas, &amp;quot;each of which is a suggestion of a course of action or thinking to assist in creative situations&amp;quot;
&lt;/li&gt;
&lt;li&gt;
Charles and Ray Eames&apos; &lt;a href=&quot;http://www.eamesoffice.com/catalog/category.php?category=168&quot;&gt;House of Cards&lt;/a&gt;: Comes in five flavours. &amp;quot;The images are of what Eameses called &apos;good stuff&apos;, chosen to celebrate &apos;familiar and nostalgic objects from the animal, vegetable, and mineral kingdoms&apos;. The six slots on each card enable the player to interlock the cards so as to build structures of myriad shapes and sizes&amp;quot;
&lt;/li&gt;
&lt;li&gt;
IDEO&apos;s new &lt;a href=&quot;http://www.stoutbooks.com/cgi-bin/stoutbooks.cgi/61457.html&quot;&gt;Method Cards&lt;/a&gt;: &amp;quot;Each card describes one method and includes a brief story about how and when to use it. This is not a &apos;how to&apos; guide. It&apos;s a design tool meant to help you explore new approaches and develop your own. Use the deck to take a new view, to inspire creativity, to communicate with your team, or to turn a corner&amp;quot;
&lt;/li&gt;
&lt;/ol&gt;</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/18.html#a452</guid>
			<pubDate>Fri, 18 Jul 2003 08:32:53 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=452&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F18.html%23a452</comments>
			</item>
		<item>
			<title>Ricardo Semler: a company should trust its destiny to its employees</title>
			<link>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/17.html#a446</link>
			<description>From Ricardo Semler&apos;s Maverick!, the story of his anti-Taylorist experiment at Semco. 
&lt;blockquote&gt;
To survive in modern times, a company must have an organizational structure that accepts changes as its basic premise, lets tribal customs thrive, and fosters a power that is derived from respect, not rules. In other words, the successful companies will be the ones that put quality of life first. Do this and the rest - quality of product, productivity of workers, profits for all - will follow.
&lt;br /&gt;
At Semco we did away with strictures that dictate the &apos;hows&apos; and created fertile soil for differences. We gave people an opportunity to test, question and disagree. We let them determine their own training and their own futures. We let them come or go as they wanted, work at home if they wanted, set their own salaries, choose their own bosses.
&lt;br /&gt;
[...]
&lt;br /&gt;
&lt;br /&gt;
At the heart of our bold experiment is a truth so simple it would be silly if wasn&apos;t so rarely recognized: &lt;strong&gt;A company should trust its destiny to its employees&lt;/strong&gt;.
&lt;br /&gt;
[...]
&lt;br /&gt;
&lt;br /&gt;
Semco is an invitation [to] forget socialism, capitalism, just-in-time deliveries, salary surveys, and the rest of it, and to concentrate on building organizations that accomplish that most difficult of challenges: to make people look forward to coming to work in the morning.
&lt;/blockquote&gt;
It&apos;s an invitation many companies could usefully consider.
&lt;br /&gt;
&lt;br /&gt;
Semler books:
&lt;ul&gt;
&lt;li&gt;
Maverick: &lt;a href=&quot;http://www.google.com/search?q=Semler%20Maverick&quot;&gt;google&lt;/a&gt;, &lt;a href=&quot;http://allconsuming.net/item.cgi?isbn=0446670553&quot;&gt;Allconsuming&lt;/a&gt;, &lt;a href=&quot;http://www.amazon.co.uk/exec/obidos/ASIN/0712678867&quot;&gt;Amazon.co.uk&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
The Seven-Day Weekend: &lt;a href=&quot;http://www.google.com/search?q=Semler%20Seven-Day&quot;&gt;google&lt;/a&gt;, &lt;a href=&quot;http://www.amazon.co.uk/exec/obidos/ASIN/0712677909&quot;&gt;Amazon.co.uk&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/17.html#a446</guid>
			<pubDate>Thu, 17 Jul 2003 13:05:46 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=446&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F17.html%23a446</comments>
			</item>
		<item>
			<title>Kevin Kelly Recomendo has good mapping tools etc</title>
			<link>http://www.kk.org/recomendo/</link>
			<description>&lt;ul&gt;
&lt;li&gt;
&lt;a href=&quot;http://www.kk.org/recomendo/archives/000053.php&quot;&gt;Diagrammatic chart of world history&lt;/a&gt;: Displays with utmost intelligence 50 centuries of civilization, as revealed in the complex rise and fall of ancient powers. Not as linear as the (out of print) &lt;a href=&quot;http://www.amazon.com/exec/obidos/ASIN/0528834266&quot;&gt;histomap&lt;/a&gt; (some interesting &lt;a href=&quot;http://www.ralph-abraham.org/articles/MS%2396.Algebra/index.figures.html&quot;&gt;writing/maths histomaps here&lt;/a&gt;)
&lt;li&gt;
&lt;a href=&quot;http://www.kk.org/recomendo/archives/000073.php&quot;&gt;Offroute&lt;/a&gt;: custom topographic maps
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&quot;http://www.kk.org/recomendo/archives/000045.php&quot;&gt;world map wallpaper&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&quot;http://www.kk.org/recomendo/archives/000052.php&quot;&gt;The Tiny Book of Tiny Houses&lt;/a&gt;: &amp;quot;Each very tiny house -- or should we say each shack and shed -- is photographed and sufficiently rendered in orthogonal view that one could construct it, or at least borrow designs from it [...] George Berhard Shaw designed [his] hut himself as a tiny office built on a central steel-pole frame so that it could be manually rotated to follow the arc of the sun&amp;quot; (&lt;a href=&quot;http://www.amazon.co.uk/exec/obidos/ASIN/1579121519&quot;&gt;something similar at Amazon.co.uk&lt;/a&gt;, &lt;a href=&quot;http://allconsuming.net/item.cgi?isbn=0879515104&quot;&gt;Allconsuming&lt;/a&gt;) 
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&quot;http://www.kk.org/recomendo/archives/000068.php#more&quot;&gt;Ancient Civilisations&lt;/a&gt;: the best one-volume survey of earlier civilizations he&apos;s found (&lt;a href=&quot;http://www.amazon.co.uk/exec/obidos/ASIN/0673997693/&quot;&gt;Amazon.co.uk&lt;/a&gt;, &lt;a href=&quot;http://allconsuming.net/item.cgi?isbn=0130484849&quot;&gt;Allconsuming&lt;/a&gt;)
&lt;/li&gt;
&lt;li&gt;
and... &lt;a href=&quot;http://www.kk.org/tools/&quot;&gt;Tools are the revolution&lt;/a&gt;: pdfs of pages from the Recomendo-inspired Whole Earth issue
&lt;/li&gt;
&lt;/ul&gt;</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/16.html#a443</guid>
			<pubDate>Wed, 16 Jul 2003 13:31:48 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=443&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F16.html%23a443</comments>
			</item>
		<item>
			<title>Redundancy in software and structural engineering</title>
			<link>http://kstar.dyndns.org:8080/blog/030630.html</link>
			<description>Kurt Starsinic: &quot;Redundancy&quot; as it&apos;s usually practiced in software design is compared to the same in structural engineering, and found wanting.
&lt;br /&gt;
[via Searls]</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/07/02.html#a439</guid>
			<pubDate>Wed, 02 Jul 2003 16:38:46 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=439&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F07%2F02.html%23a439</comments>
			</item>
		<item>
			<title>Unintrusive, delay-friendly: How IM augments conversations</title>
			<link>http://sylloge.textbox.org/article/31/</link>
			<description>Instant messaging&apos;s mostly-synchronous nature mean that &amp;quot;it is OK to not answer an IM until you are ready&amp;#151;a pause of 30 seconds is perfectly acceptable where it wouldn&amp;#146;t be in voice (and the answerer doesn&amp;#146;t even have to hold the question in their mind while doing something else, but can refer back to it later)&amp;quot;. Stewart Butterfield&apos;s office uses it to communicate across geographically distant teams (where presence is a useful feature), but &amp;quot;even in the office here, we often use them when we are only few feet away: to ask quick questions without breaking other peoples&amp;#146; concentration&amp;quot;.</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/06/18.html#a436</guid>
			<pubDate>Wed, 18 Jun 2003 10:11:04 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=436&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F06%2F18.html%23a436</comments>
			</item>
		<item>
			<title>Terry Bell: The right hand of Frank Gehry</title>
			<link>http://www.calendarlive.com/galleriesandmuseums/cl-ca-reynolds25may25.story</link>
			<description>LA Times feature on the managing architect/project manager who makes Gehry&apos;s buildings happen. Architect as project manager rather than visionary. 
&lt;blockquote&gt;
Apart from &quot;knowing how to build stuff,&quot; says Gehry, the key to Bell&apos;s role is &quot;knowing how to keep a crew of workmen together, and earning a certain amount of respect for his position, because the construction guys always try to diss the architect.&quot; In another sense, Gehry continues, Bell&apos;s job is &quot;like being the conductor: You&apos;ve got the score. Now, how do you do it?&quot;
&lt;/blockquote&gt;
[via ?]</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/06/18.html#a433</guid>
			<pubDate>Wed, 18 Jun 2003 01:34:06 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=433&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F06%2F18.html%23a433</comments>
			</item>
		<item>
			<title>Program management: responsibility without authority key to MS success</title>
			<link>http://www.sellsbrothers.com/spout/#myFirstMonthAtMs</link>
			<description>Chris Sells explains that program managers have to persuade, cajole, sell &amp;quot;doing the right thing&amp;quot; to others at Microsoft. Management by buy-in (as opposed to management buy-in). Responsibility without authority is is designed into the role, and is seen as a key differentiator for MS.
&lt;blockquote&gt;
The PM&apos;s job is wake up in the morning and think to him/herself, &quot;What&apos;s the right thing to do today?&quot; The range of things that fall into this category is far too wide to even give you the bounds, but essentially it&apos;s whatever someone else isn&apos;t already doing (or isn&apos;t doing to their satisfaction : ). Once they identify the right thing to do, they can attempt to take &quot;ownership&quot; of making it happen (your boss gets a say in how you spend your time).
&lt;br/ &gt;
&lt;br/ &gt;
Once ownership is acquired, that&apos;s when things get interesting. PMs have all kinds of responsibility, but no authority. While this kind of position is generally one to avoid in the world of corporate politics, the internal product cycle training video I watched a couple of weeks ago points out that &quot;responsibly without authority&quot; is by design. Instead of ruling by fiat, PMs have to wander around the company finding folks that are involved with what they&apos;re doing to get their &quot;buy in&quot; and their help. The way to do that is through old-fashion politics, i.e. gathering consensus, persuasion, trading favors, brow-beating, table thumping, complaining up your own management chain, complaining up your opponent&apos;s management chain, etc. It&apos;s not just a popularity contest, although being liked certainly helps. It&apos;s also about your reputation, as established by your technical chops and your ability to produce, among other things.
&lt;/blockquote&gt;</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/06/10.html#a424</guid>
			<pubDate>Tue, 10 Jun 2003 10:16:35 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=424&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F06%2F10.html%23a424</comments>
			</item>
		<item>
			<title>Blogging as inhibitor (Gibson) or catalyst (Doctorow) for writing</title>
			<link>http://www.williamgibsonbooks.com/archive/2003_04_13_archive.asp</link>
			<description>William Gibson says he&apos;s stopping blogging so that he can write. In an &lt;a href=&quot;http://radio.weblogs.com/0103966/stories/2003/04/25/inventorOfCyberspaceStepsBackToThePresent.html&quot;&gt;interview with Karlin Lillington for the Irish Times&lt;/a&gt; WG said: &amp;quot;If I expose things that interest or obsess me as I go along, there&apos;d be no need to write the book. The sinews of narrative would never grow.&amp;quot;. And on his own blog &lt;a href=&quot;http://www.williamgibsonbooks.com/archive/2003_04_13_archive.asp&quot;&gt;he warned readers he&apos;d stop&lt;/a&gt; once it was time to start the next book:
&lt;blockquote&gt;
One thing that was immediately clear to me, from the first blog, is that this is not an activity, for me, that can coexist with the writing of a novel. In some way I only dimly apprehend, it requires too much of the same bandwidth (yet never engages anything like the total *available* bandwidth).
But, definitely, the ecology of novelization and the ecology of blogging couldn&apos;t coexist, for me.
&lt;/blockquote&gt;
On the other hand, Cory Doctorow says he blogs so that he can write: &lt;a href=&quot;http://boingboing.net/2003_03_01_archive.html#90638792&quot;&gt;&amp;quot;I&apos;ve been using this blog to keep track of stuff that needs to work its way into my novels for years now&amp;quot;&lt;/a&gt;, and notes that the same seems true for Rucker, Sterling, Warren Ellis and others too.
&lt;br /&gt;
&lt;br /&gt;
What is it (the author? the subject matter? the writing method?) that makes blogging a writing-inhibitor for one author and a writing-catalyst for another?</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/04/28.html#a419</guid>
			<pubDate>Sun, 27 Apr 2003 23:59:30 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=419&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F04%2F28.html%23a419</comments>
			</item>
		<item>
			<title>Chris Sells: My first week at Microsoft</title>
			<link>http://www.sellsbrothers.com/spout/#myFirstWeekAtMs</link>
			<description>&amp;quot;I learned that the internal resources for MS employees are unbelievable. I could work their my whole life and never take advantage of all of them&amp;quot;
&lt;br /&gt;
[via Scoble]
&lt;br /&gt;
Kind of related: review of an Interviewing-at-Microsoft book, &lt;a href=&quot;http://books.slashdot.org/books/03/04/22/224224.shtml?tid=109&amp;tid=127&amp;tid=98&quot;&gt;How Would You Move Mount Fuji?&lt;/a&gt;, and onwards from there, Malcolm Gladwell asks &lt;a href=&quot;http://www.gladwell.com/2000/2000_05_29_a_interview.htm&quot;&gt;What do job interviews really tell us?&lt;/a&gt;. </description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/04/27.html#a417</guid>
			<pubDate>Sun, 27 Apr 2003 22:50:20 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=417&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F04%2F27.html%23a417</comments>
			</item>
		<item>
			<title>Vodafone sees user experience as the battlefield, Microsoft as the competition </title>
			<link>http://www.mobitopia.com/20030408.html#193035</link>
			<description>&lt;blockquote&gt;
Microsoft is our main competitor as much of the strategic position will be in controlling the user experience more than the network. Under this point of view we see a serious danger as we could be marginalised as ISPs have been.
&lt;/blockquote&gt;
Judging from the experience of using Vodafone Live! over GPRS, there is much work to be done.</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/04/27.html#a413</guid>
			<pubDate>Sun, 27 Apr 2003 12:39:03 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=413&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F04%2F27.html%23a413</comments>
			</item>
		<item>
			<title>Most significant technological revolution in TV has by far been the remote TV control</title>
			<link>http://www.calendarlive.com/tv/cl-ca-baker13apr13,0,2459991.story</link>
			<description>&lt;blockquote&gt;
Ever notice, for example, that network series rarely have theme songs like in the old days? Thank the remote. Notice that there are no commercials between the end of one network show and the beginning of the next one? Thank the remote. Notice (if you&apos;re old enough) that the commercials themselves are more sophisticated and less annoying than the ones the TV blared in the &apos;70s? Thank the remote. Notice those endless headlines crawling across the bottom of your screen? Thank the remote. Notice (ladies) that you can tell a lot about a guy&apos;s control issues by watching an evening of TV with him? Thank the remote.
&lt;br /&gt;
[...]
&lt;br /&gt;
&quot;For all the whiz-bang predictions of what interactive TV is going to bring ... the most significant technological revolution in TV has by far been the remote TV control,&quot; said Robert Thompson, director of Syracuse University&apos;s Center for the Study of Popular Television. &quot;It made passivity even better.&quot;
&lt;br /&gt;
[...]
&lt;br /&gt;
The technology that&apos;s let you surf through this war was rooted in another one, World War I, when Germany used radio signals to guide a motorboat packed with explosives. 
&lt;/blockquote&gt;
[via gizmodo]</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/04/27.html#a412</guid>
			<pubDate>Sun, 27 Apr 2003 12:37:45 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=412&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F04%2F27.html%23a412</comments>
			</item>
		<item>
			<title>Doctorow on Shirky at ETCON2003: A Group Is Its Own Worst Enemy</title>
			<link>http://craphound.com/shirkyetcon2003.txt</link>
			<description>Notes from Clay Shirky&apos;s talk at ETCON 2003.
&lt;blockquote&gt;
If you&apos;re going to design a piece of social software, design for:
&lt;br /&gt;
* All groups have a Constitution: formally instantiated in code, informally instantiated in social norms
&lt;br /&gt;
* Handles for the user that matters. Anonymity doesn&apos;t work well for large groups, neither does weak pseudonymity. The world&apos;s best reputation system is in the emotional center of the brain. Almost all reputation systems are trivial or bad or both. Some people cheat on their wives but not at cards. eBay has done us all a disservice: non-iterated atomic transactions are the opposite of social situations. A good repuatation system just needs to let me know who you are. There has to be a penalty for switching handles.
&lt;br /&gt;
* A way for good works to be identified -- member since, Karma, etc. A music sharing group that FedExes 180 GB HDDs back and forth gives new members the username, $SPONSOR&apos;S_UID_MEMBERNAME
&lt;br /&gt;
* There needs to be a cost to participate: moderators have to be around for a while. It needs to be hard to do somethings on the system: otherwise the core group won&apos;t be able to defend itself. This is anti-ease-of-use, but only for individuals, but the user of social software is the GROUP, not the USER.
&lt;br /&gt;
* Spare the group from scale: conversations require dense, two-way conversations. Metcalfe&apos;s law is a drag. The value of a group is inverse to its size: you&apos;ll give a kidney to a smaller group than you&apos;d give a kiss to. MeFi shuts off new users when it gets too big.
&lt;br /&gt;
People who use your software have rights, even if you own the software.
&lt;/blockquote&gt;</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/04/27.html#a411</guid>
			<pubDate>Sun, 27 Apr 2003 12:37:10 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=411&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F04%2F27.html%23a411</comments>
			</item>
		<item>
			<title>Ricardo Semler on peopleware: Idleness is good</title>
			<link>http://www.guardian.co.uk/g2/story/0,3604,938216,00.html</link>
			<description>Ricardo Semler&apos;s methods at Semco may seem nutty (you can choose you own salary and manager, everyone can see the company financial accounts), but apparently they work.
&lt;blockquote&gt;
Semco&apos;s staff work in small, autonomous units of about a dozen (the size, says Semler, of a close family group). They make the decisions, choose their leaders, set objectives and decide who they need and what they should be paid: someone who wants too much pay for what they are doing might be frozen out by the group. &quot;From a distance it can sound like a workers&apos; paradise,&quot; says Semler, &quot;but the system is pretty unforgiving, because if you put your salary too high, and people don&apos;t put you on the list as someone they need for the next six months, you&apos;re in more trouble than you would be at General Motors.
&lt;br /&gt;
&lt;br /&gt;
There is little bureaucratic control beyond financial accountability; almost everything depends on peer pressure. &quot;We have a higher trust in human nature,&quot; says Semler, &quot;but we&apos;re also convinced that peer control is fabulous as long as there is a common interest. If someone&apos;s interested, the sort of corporate corruption you see elsewhere can never happen. It can only happen in places where people really don&apos;t care, where they&apos;re doing their nine-to-five thing, and the chief executive knows he&apos;s under the sword of Damocles so might as well make as much as he can. If he has that attitude, a lot of other people think the same way, so that system is doomed.&quot; 
&lt;/blockquote&gt;
As XP is to coding, Semler&apos;s methods are to peopleware: they seem arse-about-face. And we suspect that without embracing the culture 100%, it&apos;s hard to get the benefits.
&lt;br /&gt;
&lt;br /&gt;
The Guardian&apos;s article pulls a quote out as its headline (Idleness is good), but the core idea is that Trusting People Is Good, and trust is something sorely lacking in many workplaces these days. The next step is probably to ask customers to name a fair price they want to pay for services, and accept it (or for customers to ask their suppliers to do a fair amount of work for a budget of X). Perhaps Semco do this already.
&lt;br /&gt;
&lt;br /&gt;
Awesome stuff.
&lt;br /&gt;
&lt;br /&gt;
Related: 
&lt;ul&gt;
&lt;li&gt;
&lt;a href=&quot;http://www.t-bird.edu/about_us/lib_research/case_series/cases_1998/ricardo_semler.htm&quot;&gt;Thunderbird&apos;s case study on Semler and Semco&lt;/a&gt; has a more in-depth overview of how Semco&apos;s participative management culture works (Thunderbird: &amp;quot;The American Graduate School of International Management&amp;quot;)
&lt;/li&gt;
&lt;li&gt;
At Ideo, team-leaders make a pitch to fellow employees about the kind of work direction they want to take their team in, and the employees get to choose which team to join.
&lt;/li&gt;
&lt;/ul&gt;</description>
			<guid>http://radio.weblogs.com/0105728/categories/projectsAndTeams/2003/04/18.html#a406</guid>
			<pubDate>Fri, 18 Apr 2003 00:19:52 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=105728&amp;amp;p=406&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0105728%2F2003%2F04%2F18.html%23a406</comments>
			</item>
		</channel>
	</rss>
