• Enterprise Microblogging Use Cases: Help Reduce Your Inbox Clutter!

  microblogging

• WordPress 3.0: Multisite Domain Mapping Tutorial

  wp Multisite WordPress

• WordPress 3.0 Walkthrough: Getting Started with Multisite

  WordPress Multisite wp

• Costs and risks to consider when planning a move to the public cloud

  SOA case-studies cloud-computing cloud

• The Internet’s Library of Economic Statistics | timetric.com
  Online economic data series with a fancy interface
  data visualization statistics graph charts
• How The Guardian is pioneering data journalism with free tools » Nieman Journalism Lab

  data guardian.co.uk

• 7 Things That Blogging Does | Six Pixels of Separation – Marketing and Communications Blog – By Mitch Joel at Twist Image
  Blogging = Critical Thinking<br />
  Blogging = Ideation<br />
  Blogging = Tinkering<br />
  Blogging = Relationships<br />
  Blogging = Business<br />
  Blogging = Sharing<br />
  Blogging = Exhaust Valve
  blogging
• Quality Control—A WordPress Theme
  Turn a basic WordPress install into a simple and straight-forward ticketing system. Quality Control allows users to create tickets, assign statuses, milestones, categories, and tags. Other users can then interact with the tickets, updating their state, milestone, or any other property.
  wordpress bugtracker
• Local Council Spending Data: The Good, The Bad, and The Downright Obstructive

  council opendata

• What 108M Lines of Code Tell Us
  The Agile Executive highlights a CAST report into the technical debt of major enterprise applications.
  technicaldebt codequality
• Four roles for social media in workplace learning

  socialmedia organisations learning

• Moving Past Legacy Networking in a Virtualized Data Center
  Intel and VMWare sponsored whitepaper
  VMWare Intel networking cloud 10GbE
• Dilbert: The New Social Media Manager

  dilbert socialmedia

• Welcome to The Document Foundation!
  Fork of OpenOffice.org to maintain independence
  libreoffice openoffice opensource
• Domain-Driven Design Community

  development programming DDD

• Technical Debt a Perspective for Managers
  Good overview article, with some practical suggestions for paying down technical debt
  technical-debt agile programming development
• Domain-Driven Design in an Evolving Architecture

  architecture domaindrivendesign software

• 50 Great Web Alternatives to Desktop Software

  applications webtools software

 I am Synesthesia

 Add me to your network

• The Process of Database Refactoring: Strategies for Improving Database Quality

  refactoring database development agile

• The Enterprise Architecture Discipline: Scaling Agile Software Development

  agile architecture ea

• Encapsulating Database Access: An Agile "Best" Practice

  agile databases development architecture

• Agile/Lean Data Governance Best Practices

  agile lean data governance

• The Skillset of an Agile DBA

  dba agile agile_databases

• Agile Master Data Management (MDM)

  agile_databases agile

• Work Design Issues for HR in the Enterprise 2.0 Context

  enterprise2.0 Organisations HR

• Top 3 Business Benefits of (internal) Enterprise 2.0

  enterprise2.0

 I am Synesthesia

 Add me to your network

At an emotional level I feel pleased that a behaviour that I find natural (i.e. to dip into different work groups or areas of study and share ideas between them) and feel to be one of the more useful of my talents is shown to have measurable benefits. If anything it prompts the networker’s perennial question – “which groups haven’t I tapped into yet?”

In a similar vein, serendipitously this comes into view: Caves, Clusters, and Weak Ties: The Six Degrees World of Inventors on the way that researchers can bring in new ideas to a company through their weak ties with other technologists.

Reflection and Memory

Memory-wise I find the “little black book” with a few key phrases or bullet points essential to remember the flow of the day.

However I’m not keen to have a formal plenary “writing it down” session; partly so as to make best use of face-to-face time; partly because I find that writing a too-detailed set of notes tends to freeze the thinking at that point rather than allow the ideas to ferment and mature over time. Ian Glendinning strikes the right chord here for me.

I do think that a reflection period at the end of each session would be a good way to surface and anchor thoughts without over-formalising.

Developing the Ideas

The converse is also true – to continue the conversations amongst a geographically-dispersed group we are going to need to write it down on blogs, wikis, emails, IM etc. etc. – perhaps that is where we will begin to express a written emergence of our thinking?

I’m beginning to think that as well as having the “seed” themes (the 11 groupings from the window) to work with it would be very helpful to have some candidate “research questions” in each of those areas to focus our output. Each question should combine a focus for the thinking with a “how could we test this in real life?”. Food for a later set of posts?

Technology

Of course we already have one target output in terms of defining the right toolset (the [bliki]IntraBliki[/bliki]).

The overwhelming majority of issues discussed on the day were around people, interactions, emotions and the psychology of blogging in business – indeed as David Wilcox notes many of these issues are those that relate to any organisational change. However I think it would be dangerous to think that there are no technology challenges left at all. In my experience unless the technology hurdle is very very low then it becomes a great hook for people to hang their “resistance to change” issues on. Anu Gupta has picked up on this by referring to this Harvard Business School article

Don’t forget that we are, by definition, a self-selected group who have been prepared to deal with the technology to get our ideas “out there”. The use of social software in the workplace will only succeed (what’s more should only succeed) if it is successful in letting people do what they need to do more easily – a means not an end.

We noted that there were certain technological barriers to be overcome before the tools were sufficiently invisible to support a wide acceptance of corporate blogging / wiki etc.

I agreed to start some work to define the requirements of the ideal internal corporate blog / wiki tool so I’ve started writing some initial user requirements in the wiki. The root of the notes is at [wiki]IntraBliki[/wiki], please join in if you are interested.

Thanks to the excellent “light touch” facilitation from Lilia Efimova and Johnnie Moore we covered a range of topics technical, cultural, managerial, commercial and more… (there will be more posts over the next few days as I and others get on with our agreed actions!)

Some of the other people there: (apologies if I’ve left you off)

• Ian Glendinning
• David Wilcox
• Anu Gupta
• Riccardo Cambiassi
• Suw Charman
• Martin Roell
• Chris Macrae
• Ed Mitchell
• Louise Ferguson
• Lloyd Davis
• Desiree Gosby
• Omar Green
• Mark Brady
• Paul Goodison

Lee Bryant dropped in for lunch
and Matt Mower joined for dinner…

Disappointed that George Por couldn’t make it but I’m sure we will catch up again soon George!

For decades our common understanding of the organization of economic production has been that individuals order their productive activities in one of two ways: either as employees in firms, following the directions of managers, or as individuals in markets, following price signals. In this paper Yochai Benkler explain why we are beginning to see the emergence of a new, third mode of production, in the digitally networked environment, a mode he calls commons-based peer production. In the past three or four
years, public attention has focused on a fifteen-year old social-economic phenomenon in the software development world. This phenomenon, called free software or open source software, involves thousands or even tens of thousands of programmers contributing to large and small scale projects, where the central organizing principle is that the software remains free of most constraints on copying and use common to proprietary materials. No one “owns” the software in the traditional sense of being able to command how it is used or developed, or to control its disposition. The result has been the emergence of a vibrant, innovative and productive collaboration, whose participants are not organized in firms and do not choose their projects in response to price signals. This paper explains that while free software is highly visible, it is in fact only one example of a much broader social-economic phenomenon. Benkler suggest that we are seeing the broad and deep emergence of a new, third mode of production in the digitally networked environment. He calls this mode “commons-based peer production,” to distinguish it from the property- and contract-based modes of firms and markets. Its central characteristic is that groups of individuals successfully collaborate on largescale projects following a diverse cluster of motivational drives and social signals, rather than either market prices or managerial commands.

Benkler explain why this mode has systematic advantages over markets and managerial hierarchies when the object of production is information or culture, and where the physical capital necessary for that production— computers and communications capabilities—is widely distributed instead of concentrated. In particular, this mode of production is better than firms and markets for two reasons. First, it is better at identifying and assigning human capital to information and cultural production processes. In this regard, peer production has an advantage in what Benkler call “information opportunity cost.” That is, it loses less information about who the best person for a given job might be than either of the other two organizational modes. Second, there are substantial increasing returns, in terms of allocation efficiency, to allowing larger clusters of potential contributors to interact with large clusters of information resources in search of new projects and opportunities for collaboration. Removing property and contract as the organizing principles of collaboration substantially reduces transaction costs involved in allowing these large clusters of potential contributors to review and select which resources to work on, for which projects, and with which collaborators. This results in the potential for substantial allocation gains. The article concludes with an overview of how these models use a variety of technological and social strategies to overcome the collective action problems usually solved in managerial and market-based systems by property, contract, and managerial commands.

“Nearly everyone feels at odds with the organizations they work for at one time or another. Managers who are also parents struggle to succeed — and be there for their families — in companies that don’t offer flextime. Women and people of color want to open doors for others like themselves — without limiting their own career paths. Teachers want to motivate students and make their material relevant in schools or school districts that require strict adherence to curriculum. Environmentally conscious workers seek to act on their values and climb the executive ladder at firms more concerned with profits than pollution … I have spent more than a decade studying people like these, men and women who want to succeed in their organizations, yet want to live by their values, ideals, and identities, even if they are somehow at odds with the dominant culture of their organizations. Rather than assimilate away their differences or leave because of them, the people I studied take a middle road, constantly balancing between the pulls of conformity and rebellion, and many opt to use their difference as a fulcrum of learning and change. I call these individuals ‘tempered radicals.’ In my book Tempered Radicals: How People Use Difference to Inspire Change at Work [2001], I describe in detail how tempered radicals make organizational change. In this article, I focus on their importance as leaders.”