Bookmarks for March 20th from 15:28 to 17:53

Social business pinboard links for March 20th, syndicated automagically:

  • The Hard Science of Teamwork – Alex "Sandy" Pentland – Harvard Business Review – patterns as a way of making sense of group behaviour (and I'd say emergent phenomena galore)

    "People should feel empowered by the idea of a science of team building, The idea that we can transmute the guess work of putting a team together into a rigorous methodology, and then continuously improve teams is exciting. Nothing will be more powerful, I believe, in eventually changing how organizations work."

  • The Architecture of a Social Business : Enterprise Irregulars – Elements of a Social Business Architecture
    – Social Media Platforms
    – External Social Business Services
    – Service Delivery
    – Social Foundation
    – Systems of Engagement
    – Systems of Record

Upcoming: Coworking Week vom 13. bis 19.9 – WikiWednesday integriert?

Noch mehr Termine – die Coworking-Week findet in der Woche vom 13.9. bis 19.9. in Stuttgart statt. Dabei soll das Thema Coworking “einer breiteren Öffentlichkeit” vorgestellt werden. Gesucht sind weiterhin kreative Ideen und Vorschläge was in dieser Woche passieren könnte.

Eine der Ideen die beim letzten WikiWednesday entstanden sind, ist es die Coworking-Week zu nutzen um am 15.9 den nächsten WikiWednesday Stuttgart (wieder im Coworking Space Stuttgart) zu organisieren. Die thematische  “Verwandschaft” ist ja gegeben, stellt sich noch a) die Frage welche spannenden thematischen Schwerpunkte wir in der Überlappung diskutieren wollen und b) ob sich überhaupt eine Mehrheit für diesen Termin findet? Für a) sind Ideen und kreative Vorschläge gefragt, entweder hier oder (noch) in der Koordinationswave – dort kann auch der Terminvorschlag weiter besprochen und dann koordiniert werden.

Teams’ knowledge use and performance (under stress)

Just a short note – check out  Heidi Gardner’s Harvard Business School working paper Feeling the heat: The effects of performance pressure on teams’ knowledge use and performance (pdf)

Why do some teams fail to use their members’ knowledge effectively, even after they have correctly identified each other’s expertise? This paper identifies performance pressure as a critical barrier to effective knowledge utilization. Performance pressure creates threat rigidity effects in teams, meaning that they default to using the expertise of high-status members while becoming less effective at using team members with deep client knowledge. Using a multimethod field study across two professional service firms to refine and test the proposed model, I  lso find that only the use of client-specific expertise (not the expertise of high-status members) enhances client-rated performance. This paper thus reveals a paradox affecting teams’ use of members’ knowledge: the more important the project, the less effective the team. This paper contributes to the emerging literature linking team-level expertise utilization (instead of just recognition) with performance outcomes and also adds a novel, team-level perspective to the literature on inter-firm relations.

This is close to being an organizational collaboration pathology – huh? Now, it’s clear that having some slack time to build up social capital is essential (for building up trust and more – we’re talking of forming, norming, storming phases in teams) while in reality teams don’t always get that time (it’s a fast-paced multi-project world after all).

But putting on the heat on teams with an overblown performance focus seems to aggravate effects we know by the name of group think (and the related fall-back to well-established patterns when the going gets rough). And group norms kill creativity:

Unfortunately groups only rarely foment great ideas because people in them are powerfully shaped by group norms: the unwritten rules which describe how individuals in a group ‘are’ and how they ‘ought’ to behave. Norms influence what people believe is right and wrong just as surely as real laws, but with none of the permanence or transparency of written regulations…the unwritten rules of the group, therefore, determined what its members considered creative. In effect groups had redefined creativity as conformity.

Now what role may social software play in this situation? I agree that just mimicking Xing or LinkedIn in the hope of supporting and facilitation intra-company knowledge networks is bound to fail (and more, it’s following a flawed paradigm, social networks in companies should be understood as emergent properties of this complex social system we call organization). Designing the knowledge environments (and tools) for smart and action-oriented workers tasked with creative jobs is not easy (and very dependent of actual context too), letting the connections between interdependent teams simply emerge is a challenge. Just think of the various relations we entertain to people not in our actual company network (freelancers, alumni, competitors and complementors, partners, …), these are complex systems too:

Confluence-Visualization-547x400