Collaboration is a participation sport. To make it all work, everyone needs to change their behavior. And if you want your new technology tools to drive the process forward, you need to practice using them – every chance you get.
Distributed teams, working out of the office, are becoming the norm. Much has been written about building effective remote teams – but are they truly engaged remote teams? Here are five things high-powered teams (and their leaders) must do to succeed (no technology required).
Many enterprises find it difficult to sustain active collaboration environments that match the fervor of their internet-based inspirations. In this article, we look at three root cause challenges, and how the right Leadership moves can deal with the challenges and realize the benefits.
Three good stories from the past week - great for me, since I am hearing feedback and "remixing" for things published here on this blog. But good, because they are nice examples of people taking ideas and tweaking them to fit their particular situation: Phil saw my presentation earlier this year on IT Strategy, and latched on to the bridge between the tactical "run the business" (RTB) work (for IT, operational support tasks), and the strategic "enhance the business" projects…
A true-life story of collaboration in action; social media done right, with plenty of lessons learned. Because coffee!
When introducing collaboration tools to an organization - creating the corporate intranet, defining project sites in Sharepoint, etc. - there are multiple skills you must master - well, at least get better at. You need to capture the ideas and communicate the data such that your target reader understands what you are trying to convey - but you also have to help them locate it in the first place. Three personas you'll need to adopt, three sets of skills to…
This post started off as an excuse to experiment with Google Docs, and this really neat feature I discovered - embedding a spreadsheet in a web page as a sharing method. However, it struck me as a potential way to cost justify the time, effort, and expense of implementing collaboration systems with the Most Cynical Among Us. We've all been in large meetings, with tens of people from the project team, along with the expensive consultants, sitting around a table…
An Enterprise 2.0 dream scenario: implementing a complex project across multiple sites, in two different time zones, with a large team (well over 100). The team was reasonably savvy with collaboration tools; core team members were quite comfortable with Instant Messaging, and we have been relying on SharePoint for many months. A centralized, coordinated document repository; a single source, very public bugs/issues list - the foundation was in place for some time, so our "go-live weekend" experience was pleasantly predictable…
Introducing buzzword-compliant technology like a wiki, or integrated collaboration spaces like SharePoint, will typically go well with a motivated audience like your internal IT department. But if you really want to understand how this stuff works, try it with "real people" - line employees in sales and marketing, operations, and finance. Sure, you've heard complaints from these folks (they have better PCs at home, the SAP/Oracle UI is brutal compared to Amazon and AT&T U-Verse, and why can't they just…
Last month, Vinson wrote about the use of wikis in school projects, and it reminded me to dust off some notes I took from a conversation with my daughter Sean MacLennan, late last year. It was a history project about World War II, and the class was asked to compose their reports on a wiki. Sean is a pretty good writer, and she likes to write, so I was interested in her thoughts on the wiki as a medium, and…