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! 

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.

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.

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.

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

Simple password rules…

This is a bit of a rant after a wasted evening.

Recently I attempted to create an account at an educational institution that shall remain unnamed.  (I am associated with four similar institutions and they all take different approaches to creating user accounts.)  This one I found particularly interesting when it came to creating passwords. The following are the rules for creating a password that were presented after my first unsuccessful attempt. I particularly like numbers 4 and 5.

    1. Must be between 6 and 8 characters long.
    2. Must not match anything in your account information, (i.e. 3 consecutive characters from login name, fullname…)
    3. Must not have more than 3 repeated characters (For example, aaaa).
    4. Must not match certain patterns (i.e. license plate number).
    5. Must not fall into any of the above categories, when reversed, pluralized, or truncated.
    6. Must not contain the characters ‘&@#{}’.
    7. Must contain at least 4 unique characters.
    8. The first 6 characters must contain at least 2 alphabetic and at least 1 digit (0 – 9) or 1 special punctuation character.

      Now is it just me, or do these sound like someone is getting carried away?  My banking password instructions are not that complex! Don’t get me wrong, I understand the need for strong passwords but this kind of thing makes me crazy.  Surely developers can find a reasonable compromise between security and usability?

      Oh yes, I never did access my account, I now await a response from tech support,  I wonder what the cumulative cost of these rules is to the institution in terms of support calls?