Weekly team meetings taking away your lifeforce? Just try this.

Is this the scene at your work when another meeting is called?

Just because team meetings can be a soulless drain of vital lifeforce doesn’t mean they are not important.

For many people, the conditions for work being a satisfying experience is that we are ‘alone together’.  Oxymoron fans are digging it the most, but what I’m getting at is that most of us like some sort of autonomy/authority/control over what we do and how we do it, and at the same time, most of us need some sort of connection to other people to feel OK.

Work lets us do both.

And in most organisations, meetings are the primary forum in which we have the chance to form a connection as a group, meaning the chance to satisfy one of the fundamental conditions for work being OK.  Or better.

Which is why they are important.   And why it’s worth trying something new if your meetings are driving you into the gutter of existential despair.

So try lean coffee!

Lean coffee (which is a trademarked thing) is a ‘structured, but agenda-less meeting‘ in the words you’ll find on the website itself:  http://leancoffee.org/ .  Better yet, check out co-originator Jim Benson (he of personal kanban fame) talking about it for 3:37 on YouTube right here. Read more…

Eliminate change management

We all know the usual routine – management identifies the need for more productivity and/or quality or a new strategy, the necessary actions are identified (internally, externally or a combination of both), this necessitates change, so now we ‘change manage’.

And it works……at best…..sometimes.

What we’re really doing here is coercing people to like the change we’ve decided on.  We’re doing change to them.

What if instead we did change with them?

As Peter Block says,

when someone states ‘we need to get everyone on board‘, the answer is ‘what makes you think you’re in the boat?‘

Imagine if, instead of management calling in the external experts, it went the other way around and the frontline team approached management and said

‘We’re out of ideas.  But if you can find $50k for those improvement consultants we were speaking to last week, we reckon we can work with them and find about $200k per year savings back to the business‘.

Would this require ‘change management’? Read more…

New to management? Not sure what to actually do? Do this.

Lots of people become managers for the first time.  Then for training they’re sent to a course on ‘leadership’ which is actually about how to be a decent human in the world.  Which is useful.   But just like there’s more to being an aircraft captain than getting along with your crew, there’s more to being a boss than knowing how to get along with your people.

So here’s an email I sent to an experienced specialist who is a good operator who has recently become a manager.  They mentioned they would appreciate some advice on what to actually do. It’s the stuff I teach in tailored workshops and coach individuals and teams on. 

Hey there,

OK, this is the stuff that will get your team moving to where it needs to be:

1) Context & Planning – your job here is to make sure the team is clear on their mission Read more…

Developing a Strategy? Read This First

You’re in charge of ‘developing a strategy’.  Perhaps you’re a General Manager, where developing and delivering strategy (what work, why that, and why us) is the key part of the job.  Or maybe you’ve been assigned the task because you’ve put your hand up, or you’re an agitator, or someone wants to see what you can do.  Or perhaps you’ve been asked to bring together the ubiquitous ‘cross-functional team’.

So what do you do?

Convene! 

Strategies are developed by convening gatherings of people who want to be there, then having real conversations about possible futures.

They’re not developed by working through a process of identifying the current situation, by doing a SWOT, PESTL….whatever.  These things might be useful to identify things to talk about, but they come at a cost, which is the implication that the process will reveal the strategy.

It won’t, and here’s why.

Real strategy, as in strategy that actually happens, is created by people imagining what might be possible, then making the choice to create a new future.   Read more…

51% – the brilliantly simple concept to start creating real commitment

There’s an element that gets overlooked when you set up your organisation with the right number of levels (yes, there is a right number, but that’s a different post), and when you make sure that the people in the roles will be able to add value at the level that the role requires.  You get a natural feeling of release or ‘that feels better’ as some of the key conditions that create micromanagement or disconnection are now dealt with.

Couple in some training about what the unique value-add of each level is, and we’re well on the way toward an enterprise that can seriously get things done, both today’s work, and tomorrow’s.  If you’d like some research on this, and no less than 50 years’ worth is good enough for you, check out the work of Elliott Jaques.  We use it because it works.

But there’s a darker side.

In the process of defining ‘levels’, the human need for dominance rears it’s head.  I’m talking about the idea that “I’m at a higher ‘level’, therefore I know better than you”.  Don’t get me wrong, most times this isn’t evil, and comes through as genuine caring for ‘your’ people.  But the very act of assuming you know what’s best for someone else….how comfortable are you with being on the receiving end of that?

Yet, we need people who can think in longer timespans so we’re OK in the future.  And we need people who can make things work right now so we’re OK right now.  We need all of these things for a successful business.  Hierarchy is actually natural.

So what do we do?

What we do is move to the mindset described by Peter Block as Partnering not Parenting. Read more…

Self-organising doesn’t mean self-directed

“The thing about Scrum” I was saying to Melinda, one of my ex-colleagues and also one of the kindest and nicest people I’d ever worked with….”is that nearly all of it makes sense in a way that’s totally requisite.”

“Scrum?” she asked.

“Sorry, what I mean by Scrum is the software development method that’s based on principles of Agile.  The Agile stuff is about frequent checking in with the customer, that developers can sort themselves out, a whole approach that makes sure a team’s collective capability is used well.  What Scrum does is nicely define roles within a team under the Agile philosophy so that everyone knows what they’re doing.  That’s my potted overview anyway.”

“Isn’t that the stuff you teach with requisite?  That by clearly defining the role relationships in terms of who can ask who to start or stop things, people can be freed up from one of most common sources of conflict?”

“Yep, all the role relationships in a Scrum Team are a version of natural requisite role relationships.  No issue there.”

“So what’s the problem?” Read more…