The Crowded Boardroom: When the long tail collides with hierarchy – a true story.

A painting of a naval battle from the 1700. Many sailing ships can be seen fighting with cannons.

This not a random picture, it is how I envision the government, the Canadian federal government. Each ship is a department or agency. The ships have commanders with considerable authority. Communication at a distance is very bad, (they did it with flags, we do it today with email and private conversations). Groups of ships are supposed to work together and sometimes they do, but collaboration is difficult with many strong egos and conflicting agendas. The current administration wants the public service to be more efficient and outcome focused, something I can very much agree with, but have also heard before.

The goal of this post is to try and share some of the lessons from an extraordinary experience that I and many others were part of some time ago. The experience was leading the collaborative tools team that created GCpedia and GCconnex across the Government of Canada (2007-2010).

This part of my professional journey began with the 2000 tech bubble burst and the ride that preceded it ended. Looking for new consulting challenges I looked to government and found a world of opportunity for improvement.  Over the next few years, I undertook dozens of interesting projects in a variety of departments that eventually led to a three-year executive interchange appointment that changed my life, and I dare say, changed the Government of Canada.

When my interchange ended, I realized that this was a career highlight that would be difficult to surpass. So I wrote a paper about it.  The paper reflects on the origin story of what is certainly one of the most successful government collaboration platforms in existence. In the paper, I look at how the project managed to transcend cultural and institutional barriers to change. My hope is that as we embark on the next round of public service renewal the lessons of the past will help improve our odds at success.

Reading it today I am struck by a few things:

we need to adapt

The world has changed a lot in the almost two decades since GCpedia was launched, but government has not. A Westminster system that has its roots in the days of sail, is still challenged by the concept of collective instantaneous communication, whatever will we do to adapt to the age of AI?

Executives need to understand complexity

Large organizations of people are complex adaptive systems and not enough senior executives know what that means. In a complex adaptive system, neither use nor content can be fully anticipated, this has serious implications for how we think about management of information, technology, people, policy and services.

CHange is hard

Introducing change to an organization requires a willingness to manage by exception —the long tail does not easily fit in a boardroom (page 20). A senior central agency executive who is willing to risk manage and lightly “govern” can enable wide-spread innovation.

stealth works

Formal approval mechanisms cannot be expected to understand and preemptively approve the specifics of innovation. A small group with sufficient “policy cover” and lean governance can sometimes achieve good enough for next to nothing.

Conflict of interest is real

Governance and funding models are something we should be looking at and talking about to deal with our shared accountability issue (see the governance description starting on page 13). Existing models have inherent barriers and conflicts of interest that should be acknowledged and addressed if we hope to make collective progress.

I would be delighted to hear your thoughts.

Here is the  PDF 

Here is the presentation to accompany the paper.

The icons in this post come from Peter Stoyko’s brilliant systemviz codex. The header image of the sailing ships comes from Wikipedia Battle of the Saintes which took place in the Caribbean of all places.

More articles and stuff.

PROTECT THE DEVIANTS!

Two golden retriever dogs in a puddle as the sun sets.
Otis and Saul enjoying their deviance.

I was a “risky” hire.  Not quite cut from the same cloth. A slightly irregular education. A different sort of professional background. An advocate for better, maybe not anonymous enough…someone with an opinion.

The system, like any mature system, naturally tried to reject me. I failed exams for subjective reasons. Was disqualified based on narrow interpretations. Limited opportunities due to my background and maybe even gender and age.  In fact, I am pretty sure that if the HR System was a person I would have grounds for a complaint. Alas, the system is not a person and harassment only applies to people.

The people I have met are polite, concerned and friendly. Most of them want to do a good job.  Some of them have seen beyond the risk and helped me, and I thank you very much for that.

Now that I am in the system, I realize that I am a bit of a deviant for the same reasons that I was a risky hire.

https://gfycat.com/IdenticalThoseDarklingbeetle

If you imagine government organizations as living organisms and apply some biological logic, it is not hard to see how they would naturally try to reject anything foreign. And in some parts of government culture, I am definitely foreign.  Luckily in other parts of government culture, I fit right in, in fact, I am not as “deviant” as some!

Nevertheless, the places where I do fit in are generally bucking the system, or at least trying to hack it. Their directors and managers are committed to finding a way to do the right thing today, even when the rules are trying to force them to do the right thing for yesterday. It is not easy, they have to work hard, be persistent and continually challenge existing thinking. All before getting on with their mission. 

There is a point to this rant. In his seminal book on organizational culture, Organizational Culture and Leadership Paperback,  Edgar H. Schein talks about how people that first exhibit new traits become different than their co-workers. In most groups of people, this deviance from the norm results in marginalization—cultures by their nature seek the harmony of homogeneity.  Because of this human dynamic, if an organization wants to change it needs to protect the positive deviants from the forces that would see them banished.

The forces that marginalize deviants come in all shapes and sizes. Some are hidden in cognitive biases, others come out as classification, age, level, gender or discipline discrimination. Still, others manifest as well-intentioned policies and rules with narrow interpretations that result in prejudicial side effects.  Risk aversion plays a role here as well. Managers often equate risk with being challenged and the easiest way not to be challenged is to do things the way we have always done them. Deviants are risky by definition, even if they are positive, so the logical path is to get rid of them or not hire them in the first place. 

I think of myself as a positive deviant, and I know there are hundreds, if not thousands of public servants that feel the same way. If the public service is to remain relevant in a different world, it must be different and to be different it needs positive deviants, not former employees. 

Protect the positive deviants! 

The sausage and the salad

Over the last few years I have been trying to understand how open government can save democracy and help us deal with the big challenges in society today. Recently I have turned my attention to the policy making process as a big part of what government does.

Policy, according to Wikipedia is “a deliberate system of principles to guide decisions and achieve rational outcomes”.  Government does a lot of policy.  It creates laws, regulations and a whole series of policy instruments.  You could argue that government really only exists to create policy, and implement policy via services.  So policy is important.

Traditional government policy is like making sausage

Wikipedia 1200px-Kielbasa7.jpg
Various types of government policy produced in the traditional way.

To make sausage you grind up some meat, add some spices and maybe some filler. You stuff it in a tube of something using a special machine and package it up for cooking and consumption.  Once the sausage is made, it is pretty much impossible to change the recipe.

To make policy we grind up some knowledge, add some words and maybe some regulation. We get it approved by the department, the cabinet or the legislature in a process that takes years. Once approved, it is pretty difficult to change. Lessons from implementation are frequently lost as the policy does not get renewed for years.

The thing about sausage is that even though it might taste good, you never really know what goes into it.  Also too much of it is probably not good for your health.

Open policy making is like making a salad

Modern open policy produced with collective input and open to iterative improvement.

On the other hand, let’s think of a salad. Not only is it more colorful and diverse, you can instantly see all the ingredients. You can tell by looking at it whether it is fresh or not. Salads are versatile and easily changed. In fact, if you really want to you can still toss in some tasty sausage at the last minute.

Open policy making lets you know what went into the creation of government direction, you can easily see and examine the ingredients in the end product. In open policy making you can even offer up your own ingredients.  And salads are generally good for your health.

The world is changing and we need to adapt

We have spent centuries in government perfecting a convoluted sausage policy making process that depends heavily on expert advice and a bureaucratic understanding of the

Declining meat consumption in Canada as a metaphor for the changing policy landscape and rising demand for open policy making. 

public good.    But the world is changing. Meat consumption has been declining for decades and for government to stay relevant it must adapt.

I think we need more salads in our policy diet, what do you think?

Links and credits:

No one cares about open government

Open government is one of those terms that has different meanings depending upon your perspective.You might feel it is mostly about open data, or making information freely available, or you might think it is about engaging with constituents.

In 2014 and 2016 I had the opportunity to ask a lot of folks (mostly academics, civil society and public servants) why they thought open government was important. No one talked about open government as something inherently good, they talked about:

  • solving complex problems and creating social opportunity
  • fairness, objective knowledge and opportunity for positive change
  • understanding measuring, and connecting government
  • learning from the past and financial transparency
  • growing a healthy democracy
  • improving government
  • economic opportunity
  • citizen empowerment

They do care about Open Government they just don’t call it that.

p.s. For me, that healthy democracy item is flashing in my mind these days.

So what’s with the ducks?

 

Several different colors of rubber ducks. Could be a symbol of diversity or cooperation

Those of you that have been to my office know that I seem to have an obsession with ducks, particularly the bathtub kind. My collection of rubber, plastic, glass and paper ducks was mostly accumulated a few years ago when I was working to sell the concept of enterprise architecture. Many of the ducks in my collection are gifts from that period. This post explains the story behind the ducks.

Problem: How to communicate the benefits of Enterprise Architecture.

In the summer of 2007 the Enterprise Architecture and Standards Division, of CIOB TBS GC, faced a dilemma. Over the previous three years they had invested heavily in creating a robust and comprehensive approach to business transformation. Called BTEP for Business Transformation Enablement Program, this approach integrated business architecture and project management concepts into a disciplined method for horizontal change. After several successful implementations it had begun to attract attention and communications with potential adopters became important.

Unfortunately, the brilliant scientists that created the method responded to this interest using the sometimes arcane language of the discipline and simply overwhelmed business people with detailed descriptions of what they had done. A few like-minded individuals got the message and were enthusiastic, however, most business people simply didn’t get it.

In early 2008 the most senior levels of management in the Public Service began to ask questions around alignment. They wanted to know if projects they were being asked to fund were aligned, that is did they follow strategy, use compatible technology, comply with policy, and not duplicate one another? Alignment is a key goal for Enterprise Architecture and the division had been working on ways to measure (and create) alignment as part of its efforts to stimulate coherence. What interests our bosses, fascinates us, so naturally the division wanted to bring its alignment work to the forefront.

The division knew it had important knowledge and useful tools that could help. But they also had learned that selling Enterprise Architecture using the language of the discipline only worked with other architects. Strategically they understood that they needed to change their approach to communications and had hired myself as a senior communications person. I was a recent convert to the idea of Enterprise Architecture and was not steeped in the language of the discipline. Knowing the power of images and metaphor I stumbled upon the idea of ducks in a row and added it to the spider web, gear images, and railroad metaphors as things to try out.

Having previously worked in advertising, I sought to obtain a visual to go along with the words coherent government by design. In order to cut through the visual clutter and get noticed, the image had to be different than what people were used to seeing. The concept of ducks in a row seemed to resonate. The brightly colored ducks were nothing like the complex diagrams and charts that populated most of the decks in the division. There was no question they got attention.

We added the slide to an executive presentation the CIO was giving and while talking to the slide he associated the different color of each duck with the unique personalities of the departments in the federation that makes up the Government of Canada. The argument being that they did not have to give up their autonomy to move in the same direction.

The ducks turned out to be an excellent metaphor, not only because they communicate the central message of alignment, but because they are well suited to an extension into the physical world. The division even gave out rubber ducks as instant achievement awards. These ducks sit on desks and bookcases, as a means of drawing attention and reminding us of the importance of alignment.

As the program rolled out and ducks began to propagate, people started to give me ducks that they collected from their travels. I now have ducks from all around the world, drop by my office sometime and I will show you a few.

The book chapter can be found on the Enterprise Architecture Marketing page.

This post is an excerpt from the marketing communications chapter of Coherency Management: Architecting the Enterprise for  Alignment, Agility and Assurance Edited by: Gary Doucet, John Gøtze, Pallab Saha, and Scott Bernard

You can change culture now: 3 essential truths for public service leaders

stick man on stairs squareThe Canadian federal public service has been trying to change its culture for a few years with initiatives like Blueprint 2020 and the Innovation Hubs. Now we have a new federal leadership that wants to adopt a new and more collaborative approach to governing. One might wonder what is keeping us from our goal…

I am not a millennial, but I am a pretty hip, late baby boomer who has been part of the interweb since close to the beginning. My career has been a little eclectic and I have had the opportunity to observe and participate in a wide range of transformational activities. I am telling you this, because it is that experience that has provided the fodder for the observations that follow.

A few years ago I was deep into an analysis of how governments could realize the potential of collaboration and social technologies. As I was mulling over how to synthesise all of the data into a sound bite that could be easily consumed by a busy executive, I was also thinking about how it connected with what I had learned from working in advertising and teaching consumer behaviour. In a rare moment of clarity while waiting for a red light I scribbled down three truths that seem to me to be both obvious and profound.

1. Sharing is good

Sharing is the activity that fuels successful collaboration, knowledge management and communication, which in turn are fundamental to a “capable and high performing” organization. By sharing we become authentic to those around us, sharing preserves hard earned knowledge and makes us more productive, telling stories makes us real, and helps to build the common purpose which is so important to successful change.

Most of the major research firms agree that the biggest challenge organizations face in implementation of social technologies within the enterprise is creating a culture that supports information sharing. Having been involved with over a dozen enterprise collaboration efforts I can say that my personal experience supports those findings. Culture, as the saying goes eats strategy for breakfast, apparently it also eats technology, and probably has a taste for deliverology as well.

Many people don’t share because they are afraid of making a Career Limiting Move (CLM), while others, (kudos if you are one), consider sharing part of their responsibility. Unfortunately too many seem to equate sharing with a CLM, and ultimately we need to institutionalize ways of rewarding sharing and punishing information hoarding. Maybe we can make sharing part of management accountability accords, it is pretty easy to count contributions to sharing platforms like GCpedia and GCconnex…

2. Ego gets in the way

By ego I mean an unhealthy focus on self. We have all come across individuals that try and withhold information, and manipulate those around them for personal gain or promotion. When combined with a lack of emotional intelligence I believe this is one of the most destructive forces in the public service today. We need to get our self-worth from something other than the size of our empire, we need to get emotional and career points for collaborating. We need to recognize the common purpose, (serving Canadians anyone?), as more important than our personal gain. Not only is the, “I only do what is good for me” attitude, bad for the organization, its beginning to look like it may be bad for your career as well.

I have worked on enough horizontal files to have come across this issue more than once. No matter how you structure a collaboration, the people involved can always sabotage it. While researching the horizontal governance issue sometime in the early 2000’s, I came across an Auditor General’s report examining the lack of progress on the climate change file. Without much reading between the lines it was obvious that the real problem was that the primary departments involved could not find a way to collaborate, mostly because the Deputy Ministers did not like each other. Now I am not pointing fingers at the senior ranks, you see this kind of behaviour at all levels. I suppose we should not be surprised, given the competitive, individualistic socialization most of us have grown up with. But humanity’s greatest capacity is to learn, and I like to think that we can learn to work together despite personal differences—if we set aside our ego once in awhile in favour of the common goal.

3. You can’t communicate too much

“You can’t communicate too much”,  I posted this comment on twitter during  a conference  once and it quickly became one of the most re-tweeted updates, so it seems the sentiment hit a nerve.

Back in my advertising days we used to spend a lot of money on media buys and printing, and one of the worst things that could happen was for a print run or advertisement be published with a mistake. When it did happen it was an expensive and embarrassing lesson. After the first time we began to repeat instructions, in different languages if necessary, we would draw pictures, leave notes on the artwork, call the publisher, even attend press runs to make sure all was understood. Later in my career I worked with a Product Line Manager at a major telecom who told me that for an idea to get traction you had to say the same thing over and over again in as many different ways as you could think of —when you are sick of saying the same thing, it’s time to say it again— you can’t communicate too much.

In today’s information intense and dynamic workplace, trying to get the attention of information inundated executive ranks will take more than a little repetition. Going the other way, management can’t communicate too much with staff, especially during times of change. The mushroom school of management (keep them in the dark, and feed them sh*t), simply has no place in an agile and high performing organization— you can’t communicate too much.

In dynamic times, perfection is the enemy of communication, waiting for a complete and crafted message simply leads to speculation and fear, while communicating often and openly, even admitting you don’t know everything, leads to trust and understanding. Having a clear and common purpose is more important than knowing the details of how you are going to get there— you can’t communicate too much.

Conclusion

Changing the culture of something as big as the public service is a daunting task, sometimes compared to turning a supertanker. But the public service is not a ship, it is an organization made up of people, and it’s people who make the culture. The three truths that I have shared can and should be applied from the top down, but more importantly they can be applied by individuals regardless of rank, when you think about that, it means you have the power to change culture.

What are you going to do with that power?

Image Source: http://commons.wikimedia.org/wiki/File:Triskele-Symbol-spiral-five-thirds-turns.png

Editorial Note:

This post is adapted from one of two posts that was written for a GTEC 2013 blog series exploring what it means to be an Agile, Open, Collaborative and Mobile Government. The original post was entitled “Three truths to help you change the culture of the Public Service.” My focus in the series was on the Cultural, Organizational and Policy Infrastructure that provides the foundation for public service culture.

Good enough, is.

I have worked with government now for about 15 years and somewhere in that period I became infected with Public Service Renewal disease.  I call it that because that was I how I first learned to articulate it. But you could also call it Blueprint 2020, Destination 2020, Gov.20, Agile Government, Open Government or the current favorite, Digital Government.

One of the differences I have noticed between the federal government and other sectors of society is a preoccupation with obligation. The bureaucracy of government sees itself as obligated to meet a higher standard. Mistakes are rarely tolerated and staff routinely strive to achieve the impossible;  programs that will measurably create results with no risk.  The goal is laudable but consider for a moment how difficult it is to achieve societal goals that are actually measurable in a 4-8 year term. Society changes, but it does so in decades and in ways that economists struggle to understand much less measure. The other side of the equation is risk and as my mother used to say; ” nothing ventured, nothing gained”, venture implies risk so if you are unwilling to risk being wrong for fear of unfavorable media attention, or just because you want to create the perfect solution, you are doomed to an eternity of cost overruns and mediocre results.

Part of the problem is the way that accountability and reward are structured. Senior managers with performance pay are motivated to eliminate mistakes are frequently adopt a strategy of micro-managing. Because that is so unsustainable they quickly become overwhelmed with details.  When they are presented with an innovation that will take some additional effort, it is much easier to say no.

I started this post with the statement, “good enough, is”.   Early in my career, (decades ago now), I was working for the engineering group in a telecommunications firm, I was writing the project charter for a five-year multi-million dollar product transformation. Working with one of the executives articulating project principles, and he insisted that one of them should be  “Good enough, is”.  His rationale was that engineers were constantly almost finishing projects, and then thinking of better, more elegant solutions and restarting the entire effort. This constant pursuit of the very best was getting in the way of actually shipping a product. It struck me then as interesting, and worthy of consideration in realms beyond engineering and telecommunications.

Since those days I have come across the sentiment expressed in a number of ways, from “perfection is the enemy of good”, to perfection is a moving target, to the minimum viable product. Whatever you call it, I think it is worth reflecting on the question of whether you and your team are pursuing excellence at the expense of good enough. In these days of extreme demands and minimal resources, ask yourself is it worth the price?

Recently (2014) I have been encouraged by all the talk about bringing Agile processes into more aspects of government. But one thing that concerns me is I am not sure that folks understand that “good enough is” lies at the heart of the process.  I suspect that a few public servants with a passion for excellence, can pretty easily kill agile with good intentions.  We have to remember that agile is an iterative process. We need to build this into our thinking. Each iteration of a policy or service development cycle may be just good enough, but that is OK, because we can make it better in the next iteration. This leads to the next challenge which is making the iterations short enough, as in next quarter rather than in five years.

Kaizen

This is not to say I think the public service should under-achieve. The idea of “Good enough, is” should always be countered by the concept of Kaizen or continuous improvement. The dynamic tension is a healthy thing.

What do you think?

Note: This post originally appeared on the Government Executive Blog.

Three words for the season

This holiday season I would like to share a song with you from a band that my teenage son introduced to me to. It is certainly not a Christmas song, but I think the sentiment is one that is appropriate.

The song is called the Shen and it is track 4 from Infected Mushroom’s album Classical Mushroom, released by YoYo Records, in 2000. Infected Mushroom is an Israeli psytrance/electronica duo of producers Erez Eisen and Amit Duvdevani. The intelligible lyrics start around the 6:20 mark in the 8:34 minute long track. According to Metrolyrics.com the entire song consists of these words:

Patience, understanding and love;
Patience, understanding and love;
Patience, understanding and love;
Most of all you need love.

Patience, understanding and love,
that’s what I want for Christmas.

All the best to you and your loved ones,

Thom

If you like this type of music have a listen.

 
http://www.youtube.com/watch?v=p2BK48mIdZw

The song may or may not have something to do with the one time secret healing Technique of the Shun Shen Tao.  While preparing this post I came across this video where Grandmaster David Harris shares the “Shen” Technique in the art of Shun Shen Tao.  Interesting stuff.

The Importance of Open

Image

skycrop3Over the years I have had the chance to reflect upon lessons from quite a few successful and unsuccessful projects.  One of the more significant things that I have been lucky enough to be involved with is helping to bring the Government of Canada GC2.0 Tools (GCPedia and GCConnex) to life in 2007.  Since then, I have continued to work on enterprise collaboration and knowledge management efforts  including several environmental scans of best practices world-wide.

One of the more important insights I have gleaned from this research and experience is that when it comes to an enterprise collaborative solution, open is important.  According to McKinsey and others, achieving the potential of enterprise collaboration requires a culture of sharing, and sharing is a characteristic of open.

Open Door

Any solution that claims to be enterprise must be available and open to all employees, anything that imposes silos or mirrors existing hierarchies degrades the potential for emergence by limiting the number of participants. This is not to say that there cannot be private spaces, only that the creation of private spaces should require a business case if you are serious about open by default.

Open Information

Secondly, the information architecture needs to be open so that users can discover content and other users, both intentionally through search and serendipitously by accident, this enables the self-organization and relationship components of a complex adaptive system. Open information also means that you have to classify responsibly, declaring everything confidential is usually wrong and significantly decreases the value of the information assets.

Open Source

Using open source software is important because it allows a small internal team supported by a global volunteer network, to quickly adapt the technology to changing needs as they arise.

Outsourcing solutions means buying into someone else’s product roadmap and the cultural paradigm that goes with that roadmap. This might make sense in a mature market with global best practices like finance or human resource systems, but web-based collaboration is young, and governments are still learning what they need.

As government reinvents itself we cannot predict what will be required. Using open source software allows the organization to remain agile in a sustainable way. Keeping the expertise to develop and maintain low cost, light weight technology also serves the innovation agenda in ways that outsourcing never can.

Open Innovation

In the Government of Canada we are entering an era when outdated systems are being replaced by outsourced solutions. In many cases this is a good thing, but Enterprise Collaboration is one space where I believe this strategy would be a mistake. The reason is not technical but cultural. The GC2.0 Tools (GCpedia and GCconnex) should remain, low cost, open source, internally managed collaboration tools. Their very existence speaks to the innovation and skill of the public service. Attempting to replace what passionate public servants have collectively built with a third party solution clearly sends the wrong message.

@thomkearney

p.s. Writing this post, I am reminded of a favorite quote, “A mind is like a parachute, it only works when its open” – Frank Zappa, (according to the internet).

This post also appeared in the Canadian Government Executive Blog, November, 10, 2013.

Collaboration Tools the Shirky Ladder

This post originally appeared as part of the GTEC 2013 Blog4549099_HiRes

Collaboration is a word you hear a lot these days, and its one of GTEC13’s theme words.  In the Government of Canada (GC) Public Service context, the Chief Information Officer, Clerk of the Privy Council and the President of the Treasury board have all called for increased collaboration between departments in the service of Canadians.  A few years ago when I had the title Senior Director of “Collaborative Tools” I set out to understand the word better. The short form of the definition I came away with was that collaboration is a group of people coming together to solve a problem.

Of course, there is more to it than that.

Three Levels of Collaboration

One of the most cited books on the impact of the Internet on group dynamics is “Here Comes Everybody: The Power of Organizing Without Organizations” by Clay Shirky, 2008.  Shirky describes  three levels of collaboration:  sharing, cooperation and collective action. These levels exist on a ladder of increasing commitment, risk and reward.  Understanding the levels reveals important nuances in meaning that have significant impacts in making the most of collaboration tools.

1. Sharing is Easy

The first level is sharing. Sharing creates few demands on participants. All you have to do is make content available where others can find it. When I tweet a link or update my LinkedIn status I am sharing. Sharing is a happy by-product of working transparently, and can take very little effort but have a profound impact when a connection is made. My criteria for sharing is that the information be safe and potentially useful to others.  Sharing broadly, across departments, is important because it creates a critical mass of information connections that allows for serendipitous discovery and cost-effective re-use of information assets.  Sharing also sets the stage for the more advanced levels of collaboration by establishing some common knowledge and awareness of individual interests and experience.

Responsible sharing is the single most important thing each of us can do to realize the potential of our collective knowledge and begin the journey to a more collaborative culture.

2. Cooperating Means Change

Cooperating is the second level and it is harder than sharing because it means “changing your behavior to synchronize with others who are changing their behavior to synchronize with yours” (Shirky,2008).  When we agree to meet and make the effort to accommodate busy schedules we are cooperating at the simplest level. Co-creating a document is a more advanced form of cooperating. Cooperating creates community, because unlike sharing  you know the individuals you are cooperating with. There is a degree of shared risk and reward.  Conversational skills are important because we need to  understanding  both the shared goal and who is going to do what.  Cooperating means adhering to some mutually agreed upon standards while remaining flexible. Cooperating between departments in particular is a competency that we need to grow if we really want a more agile government.

3. Collective Action is Hard

Collective Action is the third and rarest level of collaboration. Collective Action is when a group of people truly commit themselves to a shared effort, it is an “all in” kind of thing with shared risk, reward and accountability. In an organizational context, (think Westminster silos), shared accountability can be extremely challenging because of the lack of enabling and enforcing mechanisms between departments.  All too often good intentions are lost in a tragedy of the commons as individuals become motivated by personal gain over collective good. Collective Action may be rare but it is a worthy aspirational goal for those that have mastered Sharing and Cooperation.

Different Tools for Different Levels

In the world of IT systems, vendors and advocates for particular solutions sometimes use the word of the day to help sell their product, and “collaboration solution” is a recent example.  When we view collaboration in the light of Shirky’s levels, it makes it easier to understand the value that different tools bring to the equation.

To share widely you need  open enterprise wide tools like GCpedia and GCconnex that can be accessed by everyone in the Public Service.  For formal cooperative projects you may require document  security and management work flows that proprietary  tools provide.  For collective action, we need changes to the mechanics of government before tools can hope to have much impact.

As the GC gears up for more horizontal collaboration, agility and mobility, it is important to remember that collaboration is not a tool—collaboration is an iterative social process. Collaboration is people, (you know the soft squishy things walking around in the office), working together, often in a very dynamic and ad hoc kind of way.

At its most basic, a collaboration tool’s job is to make it easier for a group of people to find each other and come together to solve a problem.  The design paradigm behind the tool can have a profound impact on the types of collaboration that are possible – some are oriented towards sharing, while others are more about control. A single enterprise collaboration solution may be neither practical or desirable, rather an ecosystem of tools, connected by standards, may be the only way to enable the full range of collaborative behaviours the future demands.

The First Step is Simple

Collaboration can be formal and structured or it can be organic and come together in an informal way. Collaboration can mean sharing, cooperating or collective action. Achieving the highest levels of collaboration is hard, but fortunately the first step is pretty easy, simply do what you learned in kindergarten and remember to share.

—————————

Shirky, C. (2008). Here comes everybody: The power of organizing without organizations. New York: Penguin Books.

Image credit: iStockphoto,  Illustration File #4549099, contributor Mightyisland

————————–

The Culture Table – Request for input

The purpose of this post is to share something I am working on in the hopes of receiving some feedback from people like you.

Back in April I wrote a post entitled “Hold your breath, it’s going to go deep”  about the fact that  I was presenting a paper at the World Social Science Forum in October,  well the deadline is approaching and I am now  trying to write the thing.  The paper is to examine the cultural and governance implications of horizontally enabling tools like GCpedia.  As part of that I would like to have a culture table that compares the two cultures with a focus on the divergent points of potential conflict.

To provide a frame for analysis of the conflicting cultures I have elected to use Schein’s three levels of organizational culture. The draft comparison follows.

Table 1: Points of Conflict

Levels of Culture

Gov2.0

Gov 1.0 (2007-2010)

Artefacts

Visible structures and processes

Observed Behaviour

Principle based guidelines

Loosely coupled networks

Communication based on need and interest (not hierarchy)

Collective learning

Constructive debate

Habitual knowledge sharing

Roles and Histories

Respect shown in disagreement

Prescriptive policy and web of rules

Departmental, Westminster system with legislated silos

Vertical communication patterns

Some cooperation amongst the willing

Territoriality

Established methods that have worked for decades

Respect shown by unquestioning agreement

Generic Job Descriptions

Espoused Beliefs and Values

Ideas, Goals, Values Aspirations

Ideologies

Rationalizations

Open by default

Trust and respect

Wisdom of the crowd

Experiment and learn

We is stronger than me

Authenticity

Design to “Fail fast”

Values and Ethics Code:

  • Respect for democracy
  • Respect for people
  • Integrity
  • Stewardship
  • Excellence

Share when ready

Non Partisan truth to power

Stay off the front page of the news

Design for “fail safe”

Basic Underlying Assumptions

Unconscious beliefs and values that determine behaviour, perception thought and feeling

Responsible autonomy is best

Deference to the most respected

Shared sense of purpose

Free information is powerful

Mistakes are learning opportunities

Beg forgiveness

Hierarchy is best

Deference to authority of the position

Entitlement to my job and benefits

What the boss wants

Information Is power

Mistakes are career limiting moves (that end up in the news)

Ask permission

Working for Canadians
(it’s a calling not a job)

This is just a draft and it is based on my perceptions.  What do you think, am I being unfair to the Gov 1.0 or too Pollyanna with the Gov 2.0?  Maybe something important is missing?

You can comment here, or you can comment on this Google doc version that I will be using as my working copy.

Thank you in advance, I look forward to your input. 

Thom

[polldaddy poll=7312241]

Would you attend a Chatham House party for Blueprint 2020?

UPDATE, August 1, 2013

A total of 36 people signed up for invitations. We are now coordinating times and such.
The next update will be a blog post after the event is held.

UPDATE, July 29, 2013

We have reached the magic number of 30 and are now preparing.
The list will close on Thursday, August 1 at noon.

See you soon!

Some blurry people celebrating Canada.

A few weeks ago I posted an idea on this blog about using the Chatham House rule as a way to get some frank and honest input into the Government of Canada’s Blueprint 2020 vision for the public service. I was afraid that some public servants might self censor in an attempt to avoid making a “career limiting move”.

Having barely survived producing the two PS Engage events, I am a little hesitant about jumping back into event management. However the idea generated some interest and as you know I am pretty passionate about making the Public Service better, so…

I have created a mailing list that you can join if you would like to attend a Chatham House event in support of Blueprint 2020.  You can sign up using this form. If more than 30 people sign up, I will organize and facilitate at least one event.  If others decide to organize events then I will let you know what I know via the mailing list.

That’s all for now, lets see what happens!

Three truths to help you change the culture of the Public Service

This is one of two posts for the GTEC 2013 blog series where we are exploring what it means to be an Agile, Open, Collaborative and Mobile Government. My focus will be on the Cultural, Organizational and Policy Infrastructure that provides the foundation for public service culture. This is a great time to be discussing these topics as the Clerk has recently announced the Blueprint 2020 initiative with a call to action for all Public Servants to participate in shaping the vision for the Public Service of the future.

Recently I was deep into an analysis of how Governments could realize the potential of collaboration and social technologies. As I was mulling over how to synthesise all of the data into a sound bite that could be easily consumed by a busy executive, I was also thinking about how it connected with what I had learned from working in advertising and teaching consumer behaviour. In a rare moment of clarity while waiting for a red light I scribbled down three truths that seem to me to be both obvious and profound.

1. Sharing is good

Sharing is the activity that fuels successful collaboration, knowledge management and communication, which in turn are fundamental to a “capable and high performing” organization. By sharing we become authentic to those around us, sharing preserves hard earned knowledge and makes us more productive, telling stories makes us real, and helps to build the common purpose which is so important to successful change.

Most of the major research firms agree that the biggest challenge organizations face in implementation of social technologies within the enterprise is creating a culture that supports information sharing. Having been involved with over a dozen enterprise collaboration efforts I can say that my personal experience supports those findings. Culture as the saying goes eats strategy for breakfast, apparently it also eats technology.

Right now, in the Public Service many people don’t share because they are afraid of making a Career Limiting Move (CLM), while others, (kudos if you are one), consider sharing part of their responsibility. Unfortunately too many seem to equate sharing with a CLM, and ultimately we need to institutionalize ways of rewarding sharing and punishing information hoarding. That kind of change will probably take decades, so maybe in the meantime maybe there is a need for some responsible anonymous input to Blueprint 2020? What do you say, should we throw a Blueprint 2020 Chatham House Party…err… Workshop?

2. Ego gets in the way

By ego I mean an unhealthy focus on self, we have all come across individuals that try and withhold information and manipulate those around them for personal gain or promotion. When combined with a lack of emotional intelligence I believe this is one of the most destructive forces in the public service today. We need to get our self-worth from something other than the size of our empire, we need to get emotional and career points for collaborating. We need to recognize the common purpose, (serving Canadians anyone?) as more important than our personal gain. Not only is the, “I only do what it good for me” attitude, bad for the organization, its beginning to look like it may be bad for your career as well.

I have worked on enough horizontal files to have come across this issue more than once. No matter how you structure a collaboration the people involved can always sabotage it. While researching the horizontal governance issue a few years ago I came across an Auditor General’s report examining the lack of progress on the climate change file. Without much reading between the lines it was obvious that the real problem was that the primary departments involved could not find a way to collaborate. Now I am not pointing fingers at the senior ranks, you see this kind of behaviour at all levels. I suppose we should not be surprised, given the competitive individualistic socialization most of us have grown up with, but human’s greatest capacity is to learn, and we can learn to work together and set aside personal differences if we set aside our ego once in a while in favour of the common goal.

3. You can’t communicate too much

“You can’t communicate too much”. I posted this comment on twitter during one of the conferences I attended recently and it quickly became one of the most re-tweeted updates, so it seems the sentiment hit a nerve.

Back in my advertising days we used to spend a lot of money on media buys and printing, and one of the worst things that could happen was for a print run or advertisement be published with a mistake. When it did happen it was an expensive and embarrassing lesson. After the first time we began to repeat instructions, in different languages if necessary, we would draw pictures, leave notes on the artwork, call the publisher, even attend press runs to make sure all was understood. Later in my career I worked with a Product Line Manager at a major telecom who told we that for an idea to get traction you had to say the same thing over and over again in as many different ways as you could think of —you can’t communicate too much.

In today’s information intense and dynamic workplace trying to get the attention of the information inundated executive ranks will take more than a little repetition. Going the other way, management can’t communicate too much with staff, especially during times of change. The mushroom school of management (keep them in the dark, and feed them sh*t), simply has no place in an agile and high performing organization.

In dynamic times, perfection is the enemy of communication, waiting for a complete and crafted message simply leads to speculation and fear, while communicating often and openly, even admitting you don’t know everything, leads to trust and understanding. Having a clear and common purpose is more important than knowing the details of how you are going to get there.

Conclusion

Changing the culture of something as big as the Public Service is a daunting task, I applaud the sentiment behind Blueprint 2020 and encourage everyone to get involved. But it is also important to remember that an organization is people, and an organization’s people are who make the culture. The three lessons that I have shared can and should be applied from the top down, but more importantly they can be applied by individuals regardless of rank, when you think about that, it this means you have the power to change culture.

A final note:

I am writing this on Father’s day, 2013 and as it happens this date is also the anniversary of my father’s passing at the age of 89. A child of the depression and a jet setter of the 60’s he lived his life with an ethos of “doing the best you can, with what you have”. In these uncertain times it is easy to blame others for inaction, but I say, do what you can, with what you have.

What do you say?

Image Source: http://commons.wikimedia.org/wiki/File:Triskele-Symbol-spiral-five-thirds-turns.png

“Dreams of a digital nirvana don’t come true, but all is not lost.”

https://nusum.wordpress.com/2013/06/07/reflections-of-a-participant-observer/746px-Tesla_colorado

When I was asked to write a post comparing technology and tools across time, I was intrigued because I believe that the tools and technology we choose shape the culture of our workplace.

Twenty pages of draft text later, I decided that the topic was more suitable for a book than a blog post. So instead, here are a few reflections on technology and collaboration from someone who has been around a bit.

Collaboration to me, means a group of people working together towards a common goal. Technology helps or hinders us in that collaboration by finding the people to collaborate with, in sharing stuff we are working on, in co-creating stuff and in measuring our progress towards a common goal.

The past

Before the existence of writing, collaboration was strictly a face-to-face affair and probably centred around survival. About 5000 years ago writing came along, and information could now be preserved and shared independent of a human to remember it. For the next 45 centuries written information was the domain of the elite.

When the printing press was invented, rooms full of scribes were gradually replaced with new technology – machines that could accurately reproduce information at an accelerated rate. Ideas could now spread further and faster than ever before. Collaboration over distance was possible although it took a long time. Information was very physical and real.

Around this time, Information geeks the world over began a quest for the ultimate classification system. Every great power had a great library.

More recently, the Cold War and quantum physics research produced the internet and the web. The “interweb” changed everything if you wanted it to. Information could now be in more than one place at once, and it could literally travel at the speed of light. Physical artifacts became digital—making it at once more accessible and more vulnerable. Everything became miscellaneous. Digital networks evolved into complex adaptive systems, and Digimon appeared in popular culture.

The web was a new frontier, unregulated and exciting, a new crop of 20 something techno wizards rose in business fame. Apple was born. The Cluetrain Manifesto was written and there was a boom in tech stocks. At the end of the millennium we panicked over a couple of missing digits (Y2K), and spent billions correcting the short sightedness of the previous decades.

In the GC, Government On-Line occurred and the Funding Fairy provided the means for departments to put their information on-line. Canada became a world leader, but the paper-based mentality that prevailed caused many to completely miss the opportunity presented by hyperlinks and digital logic, instead “brochure-ware” prevailed.

At the top of the hype curve, the tech bubble goes pop and we are reminded that gravity works. After the crash, the Web was reborn as Web 2.0 with user-created content and social networking taking centre stage. The Long Tail made its appearance and command and control hierarchies began to sense a threat, while the educated masses saw opportunity.

Government CIOs scrambled to keep the information plumbing from backing up while Amazon and Google raised the bar of citizen expectations for on-line service.

Tagging and folksonomies entered the vocabulary of information professionals, curating became something anyone could do. Librarians and archivists struggled to catalogue and preserve some of the exponential growth while the cognitive surplus emerged to build things like Wikipedia—making human knowledge more accessible than ever before. CIOs were either bewildered or excited at the possibilities.

GTEC played an important role by bringing together examples and people. It became an annual, milestone event. It was at GTEC 2007 that Ken Cochrane announced that the GC was going to build a “Collaborative Library” and it was at GTEC a year later that we launched GCPEDIA —bringing people and technology together.

Today

High speed wireless saturates the urban environment and ubiquitous network access is a reality. Digital natives experience continuous instant communication as part of everyday life while Government workplaces seem antiquated by comparison. The web and the collective forces that it enables are transforming all parts of connected society. Recorded information is produced at an accelerating rate.

Open source software matures and becomes a viable option for enterprise applications. Governments around the world join the Open Government Partnership, in Canada the Federal Government publishes the Open Government Action plan.

Holistic User Centred Design begins to challenge solutions approaches to designing technology. Humanists and engineers are learning to work together.

The digital divide becomes a social issue, web accessibility becomes law and massive resources are assembled to ensure all GC organizations become compliant.

Bureaucracies built to manage people, work and information over the last couple of hundred years are beginning to show their age. New groups emerge in the evolutionary sea of information we know as the internet. Powerful forces compete to control the new territory – Anonymous becomes an entity.

The GC invests heavily in GCDOCS, SharePoint and other technologies designed to manage/control documents. The idea of knowledge as a product of interconnected networks and not just documents takes shape. Social innovation tools appear in pockets. GCPEDIA, GCFORUMS, GCCONNEX and other grass roots tools struggle for institutional support while gaining users.

Examples of the power of social in communicating across silos and traditional boundaries accumulate. The idea of social networks in government becomes acceptable – as long as we call them “professional networks”.

Future – Sometime after tomorrow

There is no Web 3.0, but something else emerges— a diverse, complex adaptive system, no, a network of complex adaptive systems.

Control of information becomes less important, the cultural default is to share knowledge. Government is a platform and publicly funded data is routinely visualized by an army of professional and amateur big data analysts.
In the GC, Shared Services Canada provides reliable infrastructure, we share one email address across government, secure wireless is everywhere, non-government partners can easily and securely collaborate, the government cloud is a reality. Departmental CIOs become focused on transition and business improvement—information plumbing is rarely an issue. The government-wide technical architecture focuses on standards and interoperability, a diverse range of technologies and tools work together in relative harmony, vendors with “lock-in” strategies are shunned.

GC Ideas is in constant use, the GC App Store is the first place departments look when they need software. Government developers routinely contribute to open source projects. The Open Knowledge policy is promulgated across governments around the world. The Marvelous Mistakes page on GCPEDIA competes with the Fabulous Failures page for most valuable lessons. Risk aversion all but disappears in an organizational culture that embraces experimentation and sharing lessons learned.

Tablet computers are everywhere, briefing binders disappear. The Golden Tablet program maintains a knowledge connection with departing employees. The GC20 suite of tools is adequately funded.

Dreams of a digital nirvana don’t come true, but all is not lost. Networks of people who are comfortable connecting virtually emerge and disperse continuously. The definition of Public Service changes as the lines blur between indeterminate employees and partners. The GovCloud becomes a reality. Agility is an operational requirement, and government organizations re-invent themselves.

Leadership learns to work with the nebulous “crowd.” Connections are made and governance structures adapt to include interfaces to the crowd. The focus shifts from one of command and control towards engaging with self-identified stakeholders.

Serendipity becomes a business principle, the internet of things emerges, power

shifts to those who control the algorithms but a balance is maintained by the digital collective. The Virtual Government Network is an international network 200,000 members strong where new and innovative methods are shared. Public Servants feel more connected with each other, and with the publics they serve.

Global government becomes possible as a global consciousness emerges. The collective intelligence gets a handle on our wicked problems. Technology serves the three Ps of Profit, People and the Planet. Yes, life is good in my fantasy future.

Conclusion

The Government Organizations and leadership types we have today are a product of the technology and tools of the past. The challenge now is how to incorporate things like ubiquitous network access and dynamic peer networks into serving a self-organizing public.

In times like these it is important that executives demonstrate a willingness to experiment and learn. We are lucky these days to have a disruptor like @alexbenay in the CIO chair at the GC, but he is only

Collaboration is a popular word these days. But collaboration is not a technology or a tool. Collaboration is people working together towards a common goal. Collaboration is more about values than it is about tech. We should be discussing exactly what those values are, here are four that I can think of, what do you think?

Target slide

  • Open and continuous communication
  • Shared understanding of purpose/vision
  • Commitment to the greater good
  • Freedom from fear – respect and tolerance

New technology can open doors to new behaviour, but it is the people who share the value of collaboration who will deliver the outcomes.

Technology in and of itself will not save us. But if we take advantage of the opportunities it presents and if we shape the tools we choose to use in a way that reflects the values of collaboration then I believe anything is possible. What do you believe?

Thom Kearney can be found on the internet or in the crowd at GTEC.

This post originally appeared as part of the GTEC 2012 conference blog, I have updated it a little bit for 2017.

IMAGES

The Tesla image is public domain http://commons.wikimedia.org/wiki/File:Tesla_colorado.jpg

This media file is in the public domain in the United States. This applies to U.S. works where the copyright has expired, often because its firstpublicationoccurred prior to January 1, 1923. See this page for further explanation.

The Target Image is original, released by Strategy Guy Inc. under Creative Commons Attribution.

Potential

This was written and performed as slam poetry by my son for his grade 12 English class. I thought it was pretty insightful and ultimately a positive message. 

By Sam Kearney

We start off in life with the world at our fingertips,
with the words: “You can do anything” coming out of our parents very lips
And for years these words of motivation stick with you
fueling dreams of being celebrities, astronauts and rock stars too
The World seemed so big, so vast so full of adventure
Those in dentures would give us such a lecture
And so we believe with all our hearts and happy thoughts
That life is a happy place where only in movies are battles fought

But then comes adolescence, and with it comes the many doubts
For many once seemingly perfect family lives become full of arguments and shouts
You see atrocities every day on the television
at first these stories hurt you, on your heart they make an incision
But with this reality creates an invisible division
Your idea of the world has toppled like a house of cards
And with this destruction of an old understanding
sprouts a negative ideology against which we should guard

With this newfound negativity  come new thoughts and mindsets
we make bets with ourselves, putting money against us
We kill that old saying “You can do anything”
Thinking “I could never do this, i’m not good enough, i’m not good at anything”
When really these are just excuses to take the easy path
I mean if we’ve already given up then why put in the effort and try
It’s on that cheesy poster it’s simple math
“You miss 100% of the shots you don’t take” It’s true, in life you either take a shot, or sit and wait to die.

It’s what many of us do, we’re all addicted to it, an entire nation
strangled by what we joke about – procrastination
We need to release from the shackles, locked up by ourselves
Take OUR selves off of the shelves
Stop skimming on the top of the waters of life and delve
deep into the depths of it and discover our full potential
Unleash our inner thoughts and dreams and stop keeping them confidential.

Call for expressions of interest PS Engage 2012

PSengage image and logoDo you care about making the Public Service better?  Would you like to participate in the planning for PS Engage 2012? As you may recall PS Engage 2011 was our Public Service renewal conference last year with the theme of a Tapestry of People and Ideas.  Based on the overwhelming positive feedback and interest, we’re now gearing up for the 2012 event!

We’re currently developing this year’s theme but I expect it will have something to do with frugality and working across boundaries. There are a number of ways you can take part, some of which are listed below. If you are interested and have a little time to dedicate to a worthy and fun event, we would love to hear from you, simply reply to this message with your preferred coordinates and good times to meet, and we will arrange a virtual get together.

PS Engage 2012 Planning Committee Roles

These are the roles that have been identified, they may be performed by a single person or a small group. You can volunteer to lead or participate in any of these activities.

Sponsorship

Develop sponsorship package with communications, develop pricing and marketing strategy. Manage target list and sales funnel. Prepare and sign contracts. Make presentations. Arrange for sponsor material for web site, and day of distribution.

Program & Speakers

Articulate the theme, plan the daily program, arrange for speakers, take part in developing promotional material. Coordinate with speakers.  Create conference overview document and later versions as it evolves.

Communications

Develop promotional plan, create communications material, write and produce web site, design logo and promotional cards. Manage web cast and twitter feed.  Develop and produce posters, manage distribution. Evaluate web analytics, prepare and conduct post event evaluation.

Prepare and distribute regular emails. Manage list on SalesForce.

Floor Manager

Plan sponsor physical presence, manage floor space on the day of, coordinate with venue and suppliers.

Stage Manager

Work with Program group on content and manage stage the day of.

Logistics

Coordinate with speakers, make travel and accommodation arrangements, manage all vendor contracts, act as single point of contact. Arrange for meetings and take notes.

Volunteer Coordination

Manage volunteer list and assignments. Manage volunteer meetings.

Delegate Promotion and Sales

Work with communications on web site and other promotional material. Manage registrations.

Other

Whatever we have forgotten.


The bigger picture

PS Engage is a conference, PS Leader is an emerging non-profit organization with the mission:

To facilitate and advance collaboration, learning & innovation across all levels of government and geographies in support of connected, efficient, and open government.

If you think PS Leader is a good idea and would like to be part of the development of the organization drop us a line and we will invite you to the formation meeting.

PS Leader will engage in a number of activities in addition to PS Engage such as #GovChat , PS Leader Blog, Training, and the Virtual Government Network. If you are interested in participating in any of these specific initiatives, please let us know.

Thanks, we look forward to your interest and participation as these initiatives proceed.

Thom

Report from #PSE2011 – Five things you can do today

At the recent PS Engage Conference  I had the honour of channelling ideas from participants into 5 things you can do tomorrow. With the flip chart paper spread out in my office, here is my report:

1. Read the Social Media guidelinesannounced by the Minister and take advantage of whatever authority they give you. Hold your department accountable for applying the guidelines in an effective way.

2. Reach out to a colleague, it may be someone you know but have not spoken to lately, or it might be someone you know by reputation. Ask them what they are up to, tell them what you are doing. Just a quick 15 minute status check. You never know…

3. When you find a solution to a problem, SHARE IT!  Take the time to quickly document the problem and solution and put it in a place where others that might have that problem can find it. A good default location for Federal Public Servants is GCPedia,  but any place where those that need it will find it is good.

4. High Five!
When you see something good, even just a little good thing – celebrate it! Let the individuals involved know you noticed, and let others know who the good guys are.

5. Connect – access Federal Youth Network, govloop, linkedin, gcconnex, yammer, or whatever network is appropriate for you to extend your connections and learn new stuff.

6. Rewrite your job description. Hell, re-write your team’s job descriptions. Make learning and adaptability an important part of it.

7. Narrate your work. By keeping a log of your work as you do it, you are creating a recorded history that can be invaluable for those that come after you.  If you do it publicly though status reports to your network you are also contributing to 2, 3 and 5 above.

8. Add conferences like PS Engage to your learning plan. Make sure they are in your team’s learning plan. Make learning to learn a priority.

So there are eight ideas not five, what can I say? You are a productive bunch.

See you again soon.

Thom

Post PS Engage Activities

 A huge thank you to the delegates, sponsors and volunteers that make #PSE2011 such a success. We are getting asked when 2012 is going to happen, and hearing stories of enthusiastic teams returning to work full of the spirit of renewal, so I guess it was a success.The big question now is do we do it again? And if we do, what do we do differently?

To answer those questions we are going to need your help. Look for an invitation to join a PS Engage collective intelligence site hosted by Chaordix , Intersol and Rowanwood,  Assuming we can get it together in our spare time, we will be looking to get your opinion on the 2011 event as well as ideas for a 2012 event. Who knows? We might even extend the conversation around the Learning Circle Issues or the Tapestries of ideas that Jennifer created for us.  Or perhaps we can work on the Virtual Government Network concept if there is enough interest.  Maybe Delta Partners will get involved with a little of their awesome thought leadership. Whatever it is, it will be your opportunity to influence the future of PS Engage.

In the coming weeks and months we will be releasing material generated by the conference on the PS Leader Site. It is our intention to make the video, presentations, photographs and tapestries available. There is work  to make that happen and everyone at the moment there are clients to satisfy, so it may take a while.

PS Engage never would have happened without the fabulous cadre of volunteers that materialized. You know you are appreciated.

Speaking of volunteers, right now, web-savy volunteers are welcome to apply for positions helping out with the current activities. This includes things like posting material to the PS Leader blog and perhaps editing photos and preparing presentations for publication, creating descriptive posts to go with each item, text and image.

Eventually if we decide to do another event, we will be looking for folks ready to make a slightly larger commitment and join the planning committee. If you are interested in any of that, please let us know by joining the LinkedIn group.
Thanks again to everyone involved. You make it happen.
Thom

Weaving a tapestry of ideas and people

Update: For results from the 2011 and 2012 conferences please see the PS Engage Resources post.

As many of you know I am helping to put together a networking and learning event as part of the @PSLeader initiative started by Jeff Ashcroft, Jeff is the same guy that got me into doing the #GovChat series of twitter chats, it all started with a comment on a blog post here.

Anyway, when I was part of the Public Service I was involved in the first Collaborative Management day and was excited about it, basically I think the whole #w2p #goc3 thing is awesome. Sadly, now that I am Private Sector I can’t participate in the same way, so that got me to thinking and…

…a while ago, a group of us in the shadow public service were chatting and felt that it might be a good idea to create an event that builds on the #goc3 momentum for collaborative management.  Of course if we were going to do something it had to have value over and above what an internal conference could provide. The logic we came up with goes something like this:

If the focus of the Collaborative Management events is learning from others inside the Public Service, (and there’s  lots to learn), then  PS Engage distinguishes itself by emphasizing relevant ideas from outside the Government of Canada.  Strategically this makes sense because exposing yourself to ideas outside of your norm is an essential ingredient for innovation. So the focus for us became about bringing new and relevant ideas to the table.

When we started to reach out for speakers, the response was overwhelming with the likes of Mr. GovLoop, Steve Ressler and Ina Parvanova, Director of Public Affairs for the Mayo Clinic, among the luminaries  agreeing to share their stories with us.  Just recently, TBS President, Tony Clement’s office confirmed that he will be giving the opening address—for a conference focused on bringing lessons of change to Ottawa, I can’t think of a more relevant opening speaker.

Speaking of fiscal restraint, lets not panic about cut backs and such. To my way of thinking, financial pressure is a tremendous opportunity when it forces us to look for new ways of doing things. After all, necessity is the mother of invention, or at least that is what my mother used to say—so  come to PS Engage and help invent something great.

As a privately funded event we have to charge, the cost of bringing speaker’s in from out-of-town is significant, however we have managed to keep the price reasonable at $499.00.  Any profit from the event will go towards funding further exploration of the Virtual Government Network Concept.

Group discounts are available, (5 for the price of 4), and if you are student who really wants to go, tell me why you need to attend and how much you can afford, and I will see what we can do.

As an educator, it is great to be part of putting this together, and between the speakers and the networking opportunities I am pretty confident that the conference will be a high impact/low-cost learning event.  PS Engage, a tapestry of ideas and people, the perfect complement to Collaborative Management Day and a great way to get ready for change—what do you think?

Registration is open now, so get out your corporate credit card and go to www.psengage.org, if you need to put it in your learning plan you will find some learning objectives on the site to help you out with the words.

Hope to see you there, if you have any thoughts about this event or ideas for a future one, please share.

Thom

Of course you can follow along on twitter @psengage and #pse2011

Why do we collaborate?

As part of a presentation I am preparing for a public health  forum exploring enabling technologies, I have created a slide that I think summarizes why people collaborate. It was a bit of epiphany when it came to me so I thought I would share it in case it had value to you.

What I am proposing is  that there are essentially three reasons people collaborate, and these can be connected to  Maslow’s Hierarchy of Needs .

A slide showing Maslow's Hierarchy of needs and three motivations to collaborate.

I really should be working on something else at the moment, so here are very brief explanations for the three reasons:

1.  Get’er done!  No this is not just for rednecks, anyone with a specific deliverable or project to complete will collaborate if it helps them complete the work. This is your typical work oriented motivation. I align it with the lower part of Maslow’s Hierarchy because it usually related to work and earning money which is what we generally use to fulfill most of our lower level needs.

2. The second reason is essentially social combined with a belief that maybe many minds are more powerful than one. I align this with the middle of Maslow.

3. The final reason we collaborate has to do with Self Actualization, that nirvana state we presumably all strive for and which is often considered the underlying motivation for continued learning.

Well there you have it, what do you think? Does this ring true? Is it useful?

Letting go for high performance leadership

© Chris Lamphear, iStockphoto

In Gov 2.0 circles I often hear that organizational culture needs to change. If you think about that you will realize that people need to change. If you think about that you will realize that you have to change.  Last year I heard the story of a public servant leader who discovered that sometimes by letting go, you get better results. I think it is a good example of the transformation many of us need to consider for ourselves.

Two years ago, Angelina Munaretto took leadership of the Applying Leading Edge Technologies (ALET)  working group within the Canadian government. This horizontal, mostly voluntary group was established to explore ideas around the use of social media and Web 2.0 tools for the government communications community.

At the outset, the group was structured in a traditional way and using government hierarchy:  a  Project Manager, two sub-working groups with co-chairs, and an advisory committee. Work began on defining the deliverables, finding members for the working groups and then working towards meeting the needs of this  defined structure.

What nobody counted on, but in retrospect is not surprising, is the level of interest, passion and commitment exhibited by the entire government community in response to the global trend towards Web 2.0. All areas — not just communications, but programs, IM, IT and human resources — wanted to participate in some way. Those who were involved in applying the tools on a day-to-day basis started suggesting new projects that would help advance their programs, communications and use of Web 2.0 tools. The community grew into 150 people and 36 departments and agencies represented. Five departments seconded employees to work on deliverables for the community at no cost to the project.

Says Angelina: “We moved from being a community of practice who met to deliver pieces of work, to a group of professionals who wanted to make a difference.”

I know which one of those scenarios I would prefer, what about you?

Resources were needed and community members were stepping up to volunteer to help the ALET group meet the needs of the community. More people and more resources called for more management capacity, but there was simply no additional capacity. The working groups could no longer be managed within the traditional project structure. More management capacity was required but was simply unavailable. Angelina soon found herself in a position where a shift was required.

What this meant for Angelina was that she had to adjust her leadership style. No longer would she define tasks and delegate responsibilities  – she could suggest broad areas of work or needs that the community was articulating, but this was highly different.  When community leaders stepped up and offered their expertise and leadership, Angelina moved to providing secretariat support and broad guidance on the overall outcomes sought by ALET. Members of the group were given autonomy to shape the products they were producing.  It became less about leading the group towards the completion of a deliverable to more about facilitating the collaboration and contributing where help was needed . The deliverables were defined by the needs of those working on them, instead of the project leader. In personal terms, Angelina had to relax her expectation of control.  She also had to learn to trust people to do the right thing, sometimes with very little direction  – and learned when to offer help or check in to ensure that people had what was needed to complete a deliverable.

What she found was that when a group of people are motivated and given the autonomy to take direct action, the results can be impressive. What had started as a management team…led by Angelina became a relatively self-sufficient group that produced impressive results including an extensive research document which provided essential input into policy development, a social media toolkit and numerous guides to using a wide variety of social media. The most tangible result though was getting Departments to share key development documents for use of social media so that the community could re-use these for their own campaigns. The work that started with ALET planted the seeds for a vibrant communications community that continues to grow, share best practices and build guidelines to help others.

Angelina has now moved to Library and Archives Canada, where she is the Manager, Digital Engagement and Social Media. ALET continues to thrive under new leadership and the resource pages on GCPEDIA continue to be some of the most visited.

When I look at this case, I see a perfect example of intrinsic motivation as described by author Dan Pink, there is a wonderful RSA animate video that captures the essence of his message on You Tube. [youtube=http://www.youtube.com/watch?v=u6XAPnuFjJc]

The project, in spite of being run differently than a traditional government project, was highly successful – mostly due to Angelina’s ability to stop trying to control the project and instead to facilitate the collaboration and articulate the greater purpose. She gave the members of the working group the autonomy to make progress on something that would make a real difference.

In my mind, this shift is an example of what needs to happen with leaders across the public service; from a mentality of command-and-control to one of creating a collaborative culture. Angelina’s example demonstrates that when people are given the autonomy to work on something that motivates them and is in service to something larger, whole communities can benefit.  And really, isn’t that what being in the public service is all about?

I would like to thank Avra Gibbs Lamey, a communications professional and contributor to two of the sub-working groups under ALET, for co-authoring this post. Avra can be found on twitter  @gibbslamey.  Angelina can be found @AngelinaMunaret .

What is Public Service culture?

Oct. 2013 UPDATE:  You may also be interested in this post which delves a little deeper into the idea of public service culture and Gov 2.0.
———————

I am preparing to facilitate a workshop on overcoming cultural roadblocks to Web 2.0 at the Social Media in Government conference in Ottawa on Sept 27-03.  As part of the background for the discussion, I am trying to synthesize three things.

  1. A working definition of culture
  2. A description of the existing and emergent culture in Public Service (Federal, Provincial and Municipal)
  3. A description of a future culture that we can aspire to create within our sphere’s of influence.

We have had some twitter exchanges about #2 and to provide a little more detail for those that are interested, here are 4 early stage slides for your perusal and comment.

I look forward to exploring this area with you.

Also if you mention my name or code SPK you can save $400 on the conference.

To stimulate adoption, just say no.

This post originally appeared on the Senior Fellows and Friends blog in June, 2010.

Word No, underlined by red pencil

©iStockPhoto/Kanstantsin Shcharbinski

About mid way into the pilot phase of the open collaborative workplace project, we added Karl to the team.  This is the story of his adoption of a wiki approach to preparing a large document. Karl had joined the Canadian Revenue Agency , (CRA) 6 years before, coming from the Nortel Networks meltdown. He had a background in large-scale learning, development and management and he knew this web 2. stuff was probably a good thing, he just did not know exactly how. This is the story of his initiation to a wiki, specifically the MediWiki install known as GCPEDIA. It is a story you may be able to repeat.

One of Karl’s first tasks was to prepare a formal project charter that would begin the process of taking us from pilot to enterprise solution. As you can imagine preparing a project charter in a government central agency is a significant task. There was a prescribed outline to follow, four primary authors and an executive  level steering committee of 20 or so to be consulted. In addition to the immediate circle there were perhaps 100 or so interested parties.

After obtaining the requisite word processing template from the project management office, Karl came to me to discuss the approach for developing the charter. We had a tight deadline and I told Karl that we should use the wiki to create the document.

Two days later Karl showed up with a draft. As a word processing document. He was in a hurry he said and did not have time to learn how to use a new tool. He would put it on the wiki later he said.  I was keen to see the document, but refused to look at it, telling him to “do it on the wiki”.  Apparently he did not believe me because a day later he was back with another word processed document, this time printed!  I rejected it outright. He left in a bit of a huff, probably thinking I was being unreasonable.

After a few minutes of instruction he was working away in the new tool. Some copy and paste and a little formatting and he had a rough wiki version. Commenting that maybe that was not so bad he sent a link to the small group of original authors.

Over the next few days we all contributed to the document and Karl began to smile as the benefits of writing on the wiki became obvious. No  emails with attachments.  No confusion over what version was the most recent.  A consolidated revision history and immediate notification of changes. We worked on it when we could, in the early morning or late at night, from the office or from home, I even made an edit from my BlackBerry.

In a few days we had created a version that we were happy with as a first draft and invited the larger group of executives to take part. A couple of them did, and we also had comments from interested bystanders.  By the time we got to the committee meeting everyone had had their opportunity to contribute and the document was quickly approved.

Lessons:
Most people will naturally resist change, even when they know it good for them. If there is a familiar alternative they will use it, particularly when they are under pressure. By removing the familiar, users have no choice but to try the new way.

If it is possible to make your collaboration space the only way to do something important, make it so. It will force that critical first step.

What do you think?

Do you have any adoption stories you would like to share?

Thom’s Top Ten #g2e 2010 edition

Back in May I wrote about attending Gov 2.0 Expo, in that post I promised to share some of what I learned. In short, it was an intense three days, lots of great presentations, and more importantly dozens of interesting and insightful conversations.  Here is my report.

1.  Top quote

I thought this was a very mature statement.

” web 2.0 tools are not something we need to learn to use, but environments we need to learn to live in.” Jack Holt, Dept. of Defense

For other things I thought were cool at the time you can check out my twitter feed from the conference.

2. Thou shalt engage

There is a ton of civic and employee consultation going on south of the 49th parallel. It seemed like every second presentation was about some form of engagement, mostly using the tool made available by GSA to all agencies, a good example is GSA’s own consultation.

With all this activity going on I expect we will see some more lessons learned in the next few months at WebContent.gov, but two early conclusions appeared in my mind:

  1. A broad national conversation is difficult if not impossible and of limited value.
    There are simply too many voices. Maybe when semantic analysis improves it will be practical but for now focus is essential.
  2. Follow-up is critical. You need to know what you are planning on doing with the input,  be transparent about your intentions and follow through. Be sincere and prepare for the unexpected.  See this post from David Eaves for some perspective on what can happen.

David also had a wonderful keynote at the show about open data, baseball and government. You can watch it here.

For a Canadian perspective on engagement check out what the folks at Ottawa based Publivate are up to.

3. The big systems are coming

The early days of web 2.0 are rapidly coming to a close and I am seeing more and more big systems thinking entering the conversations. This is both good and bad. The good part is when the big systems are viewed as ecosystems with permeable barriers between components. The bad part is when those big systems encourage silos and are not designed to get better the more people use them.  I am not sure if this is an observation from #g2e or just a recent reflection, but there you go – beware of big systems that encourage silos.

4. You can still do a lot with a little

The City of Manor, pop 5,800 showed us how creative partnerships with innovative thinking could accomplish some really interesting things. The image that sticks with me is the bar code stickers on the side of city trucks. Check out the presentation.

5. We have begun to move from rhetoric to results

I think it was Gwynne Kostin at the General Services Administration, Office of New Media and Citizen Engagement, who said this to me and I felt the same. Compared to previous conferences , there was not quite so much enthusiastic arm waving going on. The mood was a little more serious, a little more thoughtful. I think these are the signs of a movement that is maturing.

6. Culture change is the elephant in the room

This thing called culture frequently comes up as something that needs to change. We talk about it a bit and then conveniently move on to something else.  What I almost never hear is the idea that culture is about people. For culture to change, people need to change.

Unfortunately that means you and I have to change.

I had breakfast with the amazing culture change artist Kitty Wooley (@kwooleyy) which led to a guest blog about how hard it can be to change, even when you want. You can read the post at the Senior Fellows and Friends blog .

As a former advertising guy, I am real interested in if, and how we can influence culture change.

7. Canada is seriously behind in some respects

I had the opportunity to chat a little with Senator Kate Lundy from Australia and learned about their Declaration of Open Government based on the three key principles of Informing, Engaging and Participating. Of course Obama has the Open Government Directive and I certainly heard the mantra of Transparency, Participation, Collaboration more than once.

I look forward to hearing something similar from our government….but I am not holding my breath.

8. But we might be ahead on the inside

Of the people I spoke with and certainly in the US and Australia there is nothing quite like the Canadian Government’s GCPEDIA.  For the most part silos persist and efforts to improve internal collaboration are just beginning with initiatives like FedSpace generating a fair bit of discussion on govloop.  Incidentally I had great chats with Emma Antunes who is on loan to FedSpace from NASA, and Mr. govloop himself, Steve Ressler.

9. We need a trusted GC url shortner

It seems like a small thing, but a trusted government URL shortened is essential for gov 2.0. The US version was launched at the show  http://go.usa.gov/.  I am pretty sure there is no official effort underway to do something similar in Canada, although I understand there is a page in GCPEDIA about it.  If anyone has an update, please let me know.

Oh yes, it needs to come with metrics. Lots of metrics.

10. People will engage for their reasons, not yours

Kathy Sierra gave a great short keynote on Creating Passionate Citizens that I would recommend you watch. Who knew that pets were a gateway drug to passion?  Video of Kathy’s talk at Gov 2.0 Expo.

There is lots of other video from the expo.

11. The more things change the more they stay the same

Web 2.0 technology is fun and amazing but when you get right down to it, social networks are about connecting people, and people connect (or not) depending on how well they communicate. There is noting new about that.

There is also nothing new about the power struggles going on all over the place. A disruption is underway and people are seeking advantage. What I think is different this time, is the potential for the “power of the masses” to be put to work on positive change.  Millions of people can now come together at very little cost. I am excited about what can happen, and worried that it won’t.

I have to stop now, there is more, lots more but now its your turn.

This post also appears on govloop

Hope is important…

Hope is important, it is what makes good things possible

I tweeted that as part of a response to something from @mgifford this morning and it sounded pretty good. So I thought I would put it here for all eternity.

I could probably talk about it some more in the context of organizational change or something, but I am too busy at the moment.

Maybe you would like to share why you think hope is important?

In whatever context you like.

Thank you

Cultural risk

I was recently asked to create an executive briefing that included a high level assessment of the risks associated with adopting social media in the Government. I segmented the risks by three areas; Policy, Legal and Cultural.  The cultural risks are what interest me at the moment and they relate to the internal culture of the organization. I found myself writing and rewriting these words:
Conflict occurs between hierarchical and network management philosophies when power based on information control is replaced by power based on reputation.
To complete the risk equation, I believe the likelihood and impact of this occurring depends on the degree to which key individuals try and maintain power structures based on information control.
I am wondering if the statement captures the essence of the risk ?
Can the risk of conflict in this situation be mitigated — perhaps it is inevitable, even necessary?
Thoughts?

Overwhelmed

Many of you will know that we had a  great time at the #w2p two weeks ago,  it was sort of an informal after party for my three year assignment in the Public Service. Well, tonite was the more  official transition party and between the two events I have to say I am a little overwhelmed.

It was a wonderful send-off with many words of encouragement and several presentations. I will be shopping for technology with my gift card soon, and enjoying the book, Keeper of the Flame, thanks to Sue Kemp for getting me a signed copy.  Special thanks also to Corinne Charette and Peter Bruce for taking the time out of their intense schedules to come by and share some very kind words.

Gary Doucet took a break from chasing his CCC in French to visit, you should know that his support was pivotal in the early days to providing the resources to move forward with GCPEDIA. Without his vision we would not be where we are today.

I was thanked for all the good work I have done and the accomplishments I achieved, but really I am the one that should be thankful. If it was not for the many, many wonderful, committed and passionate folks who supported the concept and wanted to do the right thing we could not have done what some said could not have been done. Some of you were at #w2p, some of you were there tonite, some of you are out there.

It is a remarkable accomplishment, bringing a horizontal social platform to a highly segmented federation but it is not mine, it is ours. It belongs to everyone that participates not just for themselves, but also for the greater good. You know who you are.

A few folks I need to mention include Jeff Braybrook, who along with Ken Cochrane and Chuck Henry are responsible for starting it all way back in 2007,  and Karl Ghiara who has been the backbone of the GCPEDIA team for the last 12 months and will be the go to guy for some time to come.  I should also say that I can’t think of a better candidate to take over the executive leadership than Marj Akerly from NRCan who will be moving to CIOB. Charles de Grasse could not make it, but those of you that use GCPEDIA or GCCONNEX should know that he is the guy that keeps the gremlins at bay.

I am proud to have been part of this effort and to see the Clerk of the Privy Council start using GCPEDIA this week.  I also think that the newly formed cluster of departments coming together to finance and take business ownership for GCPEDIA and other elements of the Open Collaborative Workplace is a prime example of the new attitude and spirit of collaboration we are seeing building across the system.

I could ramble on thanking people, but think I should probably call it a night. It has been a great ride, thank you all.

Now where did I leave that consulting shingle….

Thom

p.s. whoever took pictures, please post!

Persuasion presentation using Prezi

I thought I would share my first experience with Prezi , the zooming presentation editor. Last Sunday I create a presentation for the class in Persuasion that I am teaching. From download to packaging up on my USB took about five hours.  This is my report of the experience.

I first learned about Prezi through a twitter post by Nick Charney who you may know as someone that  schemes virtuously. I am writing the first draft of this post using Dragon speech to text software on my iPhone while stuck in traffic.

This particular course has a text book, and the process I followed was one of reviewing the chapters, identifying the relevant concepts and essentially throwing key words and images down on a single large canvas. Prezi makes it real easy to reduce, enlarge and rotate elements and I found the authoring process strangely liberating because I was not restricted by the normal linear presentation format.

Prezi allows you to select some pre-formatted styles which I found to include some very nice font selections. The ultra simple text editing is fast to use but unfortunately lacks any Spell Check which is a serious issue for creative spellers like yours truly.

After getting most of the content in place and sizing it to create a hierarchy of importance and some visual flow, it was time to create a path though the material. This was simple mater of clicking on objects, when I wanted to it was easy to move nodes from one object to the other, thus changing the order of the presentation.

A couple of run throughs in play mode and some adjustments to the path and sizing of objects, (to control the zoom effects) and I was ready to go.  The application allows you to share and present from the on-line version or you can create a downloadable non-editable executable that plays from the desktop. I saved a file to my memory stick and went to bed.

ADV1616 Students enjoying their Prezi

ADV1616 Students enjoying their Prezi

Next day I presented the Prezi twice and must say it was fun. Although my presentation was almost entirely text, the variety in sizes, font and zooming transitions made the presentation interesting and engaging. After each presentation I polled the class on their thoughts and universally they liked it.

And myself, I liked it too!

You can find the presentation on-line, (start by clicking on the picture of Aristotle).   This is a rather simple example, I know that Nick is using it to come up with something much more amazing…maybe even subversive.

Engagement anyone?

There is a lot of talk about employee engagement these days. In management circles we talk about strategies and best practices for achieving high levels of employee engagement. Perhaps this is in response to reports of a general malaise and historically high absenteeism, or maybe because we are finally waking up to the fact that we really do need to “do better with less” if we hope to leave the world a better place.

So what is this thing called engagement?

For me engagement is a personal thing, it is an organic network of relationships, messages and memes. It is about rallying around some of the common themes and goals in an organization. It is about giving permission to staff to take responsibility for finding new and better ways of doing their jobs.  It is about demanding intellectual accountability and value for every salary dollar we spend. It is about enabling staff to take small risks and implement ideas directly. Most importantly it is about trusting each other to do what we think is best. Accepting some risk and celebrating early failure.

Engagement isn’t something you can outsource. It comes from sincerity about working for improvement and a tolerance for many points of view.

So how do we improve engagement?

Attitude.

The #1 factor that will determine the success of an engagement effort is the attitude of the people involved. This means that:

  • Staff need to take on their leadership responsibility by speaking up and pushing their organizations to improve.
  • Middle Management needs to accept the fact that control is an illusion and be willing to trust their staff. And they need to define themselves in a away that does not require the control of information. They need to listen very carefully to those pushing for change.
  • Senior management needs to promote leadership at all levels and demonstrate that appropriate risk taking is acceptable.
  • We all need to be tolerant and listen to multiple points of view. Perhaps most importantly we need to approach the monumental tasks in front of us with a positive attitude.

Engagement isn’t something you design and build so much is it something that you cultivate in your relationships. Certainly we can design processes, polices and reward systems that create an environment that is engagement friendly, and we must continually work to reduce systematic barriers to engagement, but ultimately it comes down to the attitude of the people in the system.

And that starts with you and me.