Jonathan Berry
Jonathan Berry
Role : Founder and Director
Organization : Camrose Employee Engagement

  Sort by : Title Sort  Date 

The Government’s Big Society idea: it could be more cunning than you think
posted by Jonathan Berry  on July 19, 2010

Is the "Big Society" really a way to build voters' commitment to the governing coalition? As everyone in my profession knows, the way to engage employees in an organization is to seek their opinion on how to change it. You normally get some good ideas back, but the other huge value is that people who have had a say in designing their organization are far more committed to making it work. They become more productive and innovative and develop better relationships with their clients. So does this logic extend to neighbourhoods and communities?


Let’s Make This Interesting
posted by Jonathan Berry  on July 13, 2010

 
Who wants a bet? It’s not a fair bet so you don’t have to pay me anything when I win.
 
The bet is this: that underwork is a far broader and more consequential problem than overwork. To win the bet, you have to support your case with evidence that compares the levels and impact of overwork with those of underwork in any major economy. (I told you it was unfair).
Overwork is a badge of honour. Even when you are working 80 hours a week, there is still a profound sense of pride in your contribution, in your employer’s need for you and your irreplaceability.
 


Guilt or Shame?
posted by Jonathan Berry  on August 12, 2010

Do you take an interest in your company's culture? Are you given to saying things like, "if only we had a culture of open communication", or "we must develop a culture of quality"? If so, you probably feel the promise is lurking out there that you could design your culture so that everyone in your business would just know how to behave without having to be told.

But how? You want so many things from your culture (gazing into my crystal ball, I see that you want quality, integrity, openness, respect, putting the customer first and meritocracy), so how do you design a culture that does all of these things? It's not software after all - you can't just keep bundling in new features.

Easy. For most businesses, all you have to do is move from a guilt culture to a shame culture.

Most people in western companies work in a guilt culture. In a guilt culture, when Bob in marketing makes a mess of things, it's Bob's fault. Bob takes the reprimands and works through the weekend to fix it. In a shame culture, all of Bob's colleagues are equally shamed or tainted by Bob's errors and they all stay late to fix them.

The shame culture may strike you as unfair, but think of the behaviours it drives. Nobody wants to let the team down, so you do your own work with greater enthusiasm. And when you've finished your work, you see who else in the team needs help. Nobody in the team is allowed to produce inferior work and productivity levels rise as a result.

And how do you move from guilt to shame? By observing one principle: reward or reprimand the team, not the individual. This won't feel natural at first for anyone brought up in the Christian tradition, in which guilt plays such an important role. (Islam places greater emphasis on shame, but I assume you're not reading this for religious instruction).

The shame culture's not for everyone of course. The more your business relies on individual contributors, the closer you should stick to guilt. Imagine the offices of a newspaper in which anxious colleagues read over the journalists' shoulders suggesting alternative wording. But if you value teamwork, go for shame.

  Showing 1-3 of 3