• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Building a collaborative workplace
 

Building a collaborative workplace

on

  • 15,760 views

A presentation to the Victorian Public Sector Continuous Improvement Network (VPSCIN) on the 2 March 2009

A presentation to the Victorian Public Sector Continuous Improvement Network (VPSCIN) on the 2 March 2009

Statistics

Views

Total Views
15,760
Views on SlideShare
12,416
Embed Views
3,344

Actions

Likes
87
Downloads
0
Comments
1

14 Embeds 3,344

http://www.anecdote.com.au 3185
http://www.slideshare.net 50
http://www.anecdote.com 42
http://terrear.blogspot.com 38
http://www.linkedin.com 8
http://www.terrear.blogspot.com 6
http://translate.googleusercontent.com 4
http://www.google.ca 2
http://facebook.slideshare.com 2
http://zinclab.wordpress.com 2
http://static.slideshare.net 2
http://www.sbconsulting.kr 1
http://wiki.pwcinternal.com 1
http://www.lmodules.com 1
More...

Accessibility

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Building a collaborative workplace using stories from Shawn Callahan on Vimeo.

    <br /><object type="application/x-shockwave-flash" data="http://vimeo.com/moogaloop.swf?clip_id=3448097&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" width="350" height="288"><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=3448097&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1"></param><embed src="http://vimeo.com/moogaloop.swf?clip_id=3448097&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" width="350" height="288" type="application/x-shockwave-flash"></embed></object>
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • <br /> <br />
  • Within a month of joining IBM in 1999 I was off to Boston to learn about a new software product code named Raven. <br /> It eventually was called Lotus Discovery Server - auto expertise location <br /> On the flight home I wrote an internal memo for the product manager called “Some possible behavioural ramifications of LDS’s Knowledge Map” and earned my place on the Global Services team to design the product’s services roll out. <br /> It was the beginning of my interest in how you get people to collaborate and the role software has to play. It was all about fostering behaviour change. <br /> And that’s what today’s presentation is all about. <br /> <br /> <br /> <br /> Now, who has ever tried to lose weight? Show of hands. <br />
  • Everything I know about behaviour change in organisations I’ve learned from The Biggest Loser. <br /> Firstly we all know what to do. Eat less and exercise more. But it’s not easy. <br /> There are two questions we need to answer in the positive for ourselves before we change: <br /> Is it worth it? <br /> Can I do it? <br /> This is me at Xmas. So far I have lost 10kg. Here are my lessons. <br /> <br /> The same principles hold true for building a collaborative workplace but we need to start with one word. <br />
  • Everything I know about behaviour change in organisations I’ve learned from The Biggest Loser. <br /> Firstly we all know what to do. Eat less and exercise more. But it’s not easy. <br /> There are two questions we need to answer in the positive for ourselves before we change: <br /> Is it worth it? <br /> Can I do it? <br /> This is me at Xmas. So far I have lost 10kg. Here are my lessons. <br /> <br /> The same principles hold true for building a collaborative workplace but we need to start with one word. <br />
  • How do we know when we are collaborating? <br /> What are the specific behaviours? <br /> Now you can’t say ‘trust’ or ‘reciprocity’. They are values. <br /> Behaviours are something you can see happen and if you described them to someone else they could behave in the same way. <br /> Turn to your neighbours and identify three collaborative behaviours. Yell some out. <br /> This is the first step in effecting change. Identify vital behaviours. <br /> “Team members speak out with respect and good intent when they see a problem and their team mates hear them out to work out how to address the issue.” <br /> “Community of practice leaders meet regularly to design the upcoming events for the community.” <br />
  • Is it collaboration when you’re sent the yearly performance review spreadsheet and instructed to assess your staff’s performance? Absolutely not; it’s an act of co-ordination. Everyone is working separately to achieve the overall goal of conducting the performance reviews. Only a modicum of trust is required (trust in the system) to get the job done. <br /> So, is it collaboration when you meet with your team to work out the performance review process? Not quite. Here we are co-operating with our colleagues to deliver a task that we all know needs to be done. When we co-operate there is often a medium level of trust involved (trust in each other’s competencies and character), the value of the activity tends not to accrue directly to the participants co-operating and, in most cases, someone else is driving you to do it. [1] <br /> So what is collaboration then? It’s when a group of people come together, driven by mutual self–interest, to constructively explore new possibilities and create something that they couldn’t do on their own. Imagine you’re absolutely passionate about the role that performance reviews play in company effectiveness. You team up with two colleagues to re-conceptualise how performance reviews should be done for maximum impact. You trust each other implicitly and share all your good ideas in the effort to create an outstanding result. You and your colleagues share the recognition and praise equally for the innovative work. <br /> Given this definition of collaboration where are your organisation’s efforts weighted (show of hands) <br /> co-ordination? <br /> co-operation? <br /> collaboration? <br /> <br /> <br />
  • Show of hands, who is familiar with the Cynefin Framework? <br /> Briefly describe the framework. <br /> <br /> <br />
  • In April 2006 Cuu Huynh, 58 year old father of three, was tragically killed at the Fosters’ Abbotsford plant. <br /> Clinton McDonald, who heads up OH&S for the company, recognised that part of the problem was how OH&S was reported to the leadership team. They sent them too much information in a format that was complicated didn’t allow the key issues to pop out at them. <br /> The challenge was getting agreement with all the stakeholders to change the way they reported. <br /> So he created a collaboration between the engineers, scientists, business leaders and OH&S practitioners and over a period of about 6 weeks reformulated the report. <br /> Collaboration requires a convenor. <br /> When the job was done the collaboration was over. <br />
  • Now let’s think of your own workplace for a moment. <br /> You might have invested in the latest communication software (Notice how I don’t call it collaboration software ...) <br /> You have portals, discussion threads, project spaces, wikis, blogs, Sharepoint. <br /> But people are still taking credit for other’s good work. <br /> There is still duplication of effort. <br /> People compete with one another and sharing is avoided <br /> Everything has to go through the chain of command <br /> And so the technology is used haphardzardly. <br /> Tell the story of the NSW CIO <br /> So how do you make your organisation more collaborative? <br />
  • The people who represent the future are displaying behaviours which work. The first step is the find them then work out the vital behaviours. <br /> Don’t bemoan people not using your communication software -- it will just reinforce them not using it. <br /> RTA - no time for collaboration - too busy with the upgrade - how about we get together to share experiences. Yep, let’s do it. <br />
  • Not everyone <br />
  • Let me introduce you to Everett Rogers <br /> Everett Rogers gained his PhD in sociology in the 1960s and the first job he had was at the university in Iowa helping farmers adopt new strains of corn. <br />
  • Dr Rogers talked to many farmers but none were interested in the new strain of corn even though it promised to deliver far greater yields. <br /> Why? <br /> Because Dr Rogers was completely different to Iowa farmers. <br />
  • He spoke differently, dressed differently, were interested in different TV, books, films. The only thing he had in common was the English language. <br /> But he persisted until one day he found a hip farmer who wore Bermuda shorts and fancy sunglasses who was willing to give it a try. <br /> This innovator used the new strain of corn and had tremendous success. So Everett went back to the other farmers with the results. <br /> But the farmers were doubly sure they weren’t interested. This hipster dude was an insult to their culture. <br /> Everett dedicated his career to understanding this social conundrum. <br />
  • <br /> <br />
  • <br /> <br />
  • There are a number of ways to Influence them. <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • A cross section of employees were then invited to participate in confidential discussion groups (‘Anecdote Circles’), facilitated by the Advocates and held in Sydney and Melbourne, to see what stories people had that related to these themes. <br /> These Anecdote Circles provided us with rich, qualitative data that could never be found in a survey. The stories people told us gave us a picture of what is going on at Challenger. <br /> Sense-making <br /> The Advocates distilled everything that they heard and agreed on the most compelling stories for each theme. <br />
  • Initiatives included <br /> CoP for client service <br /> Capturing events on video <br /> Mentoring program <br /> MSC for client service stories <br />
  • Cheryl Schiltz had an operation - a hysterectomy. <br /> There was an infection and an antibiotic was used that affected her inner ear (vestibular apparatus). <br /> She lost her balance and felt she was falling all the time. Even when she fell down she felt like she was falling through the fall. This is the type of feeling you have in your worst nightmares. <br /> Paul Bach-Y-Rita is a neuroscientist who changed her life. <br />
  • Cheryl’s brain has created new pathways. <br /> We need to create new pathways in organisations. This requires practice and repetition. <br /> New sensory input. Practice. Repetitions to create habits. <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />
  • <br /> <br />

Building a collaborative workplace Building a collaborative workplace Presentation Transcript

  • Building a collaborative workplace with stories Tuesday, March 3, 2009
  • Tuesday, March 3, 2009
  • “Some possible behavioural ramifications of LDS’s Knowledge Map” Tuesday, March 3, 2009
  • We all know what to do, but we don’t do it Tuesday, March 3, 2009
  • We all know what to do, but we don’t do it Must be important Must have the skills Every trick in the book Goals Make exercise easy Record progress & tell people Put your gear where you will see it Tuesday, March 3, 2009
  • Collaboration? Tuesday, March 3, 2009
  • “I wonder if we could ...” Collaboration • Often requires specialisation on • Driven by mutual self interest • Requires high level of commitment on each side • Requires high levels of trust both sides • Creates new value • Value accrues to each party “We need to ...” Co-operation • Meets a business need; often • Value might accrue to one part or driven by a directive neither • Only requires medium level • Can succeed even if commitment is of trust uneven • Value often incremental “Get this done ...” Co-ordination • Often focused on one-time, short- • Driven by directive • Teamwork helps but not pivotal term goals • Trust not key to success • Value unlikely to accrue to people involved What is collaboration? Source: Economist Intelligence Unit Tuesday, March 3, 2009
  • When to collaborate Tuesday, March 3, 2009
  • Collaboration when needed Tuesday, March 3, 2009
  • Tuesday, March 3, 2009
  • “The future is already here; it’s just unevenly distributed.” — William Gibson Tuesday, March 3, 2009
  • Who do you change? Tuesday, March 3, 2009
  • Tuesday, March 3, 2009
  • Tuesday, March 3, 2009
  • Tuesday, March 3, 2009
  • Avoid like the plague Tuesday, March 3, 2009
  • Effort here Avoid like the plague Tuesday, March 3, 2009
  • Influence Pattersen et. al. (2008) Tuesday, March 3, 2009
  • So what is the role of stories in all this? Tuesday, March 3, 2009
  • Tuesday, March 3, 2009
  • Three journeys process Tuesday, March 3, 2009
  • Ist Journey What’s the story of the change? In the past we did this ... Then something changed ... Now we are doing this ... And we are aiming to achieve this ... Tuesday, March 3, 2009
  • Ist Journey What’s the story of the change? In the past we did this ... Then something changed ... Now we are doing this ... And we are aiming to achieve this ... Helping leaders find and retell their own stories “An organisation that values collaboration should be teeming with collaboration stories.” Tuesday, March 3, 2009
  • Collect and make sense of stories Design initiatives Second journey Tuesday, March 3, 2009
  • Implement Assess impact Adapt (3 monthly cycles) Third journey Tuesday, March 3, 2009
  • Cheryl’s Balance Problem Tuesday, March 3, 2009
  • Tuesday, March 3, 2009
  • So how do you build an even more collaborative workplace? Tuesday, March 3, 2009
  • Understand and spread the word about what you mean by collaboration Tuesday, March 3, 2009
  • Find your Gibson stories Tuesday, March 3, 2009
  • Focus on your influencers Tuesday, March 3, 2009
  • Embark on your three journeys Tuesday, March 3, 2009
  • Consistency Reinforcement Practice Tuesday, March 3, 2009
  • Tuesday, March 3, 2009
  • Questions? Shawn Callahan shawn@anecdote.com.au 0410 346 343 twitter: @unorder www.anecdote.com http://www.slideshare.net/ShawnCallahan Tuesday, March 3, 2009