In the many years that I've worked in various businesses, technology has reinvented itself every so often. This forced IT leadership to look at how it ran its department, and it explored different management models along the way. Some worked, some didn't. But these have largely resulted in an 'agile' approach to creating technology solutions, and a workable management structure that, whilst OK for IT, sits rather uncomfortably alongside the business it is supposed to be part of.
What is equally apparent is that over the same extended period, and no doubt for many decades previously, those same businesses have not changed their management approach. They have resolutely kept to a functional, hierarchical organisational structure, with ability and time necessary pre-requisites in order for individuals to climb the career ladder. Oh, and add the need for a position to open up for the chance to be considered for promotion into it.
The accompanying management style was so firmly a part of how the company was run, that it was rarely even noticed, let alone questioned.
We kept our heads down, worked hard according to the rules we were explicitly made aware of (and some that we weren't), and accepted that one day we might, just might, become a manager and become part of that glorious command and control structure:
- The company has put me in charge, so I make the rules.
- It is important that you do what I say.
- I don't want you taking things into your own hands.
- If you don't hear from me, you are doing OK.
- Cross me, and I'll make your life a misery.
- If you break any rule or underperform, according to my judgement, then you'll be on a performance improvement plan from HR.
- Respect for me, and my manager, is the most important attribute you can demonstrate.
This style of management may have worked in ages past, or is a necessity in organisations like the Armed Forces, but in many working environments we have moved well beyond the industrial age and are firmly into the knowledge economy.
Executing perfectly may work for a while, but that doesn't make a company successful. Every organisation has to innovate as markets, consumers and technology evolves. Innovation is what keeps them in business, let alone keeps the revenue flowing. Strong performing, innovative companys are places where leaders lead, staff are empowered and customers become advocates.
You don't find that kind of positive office environment when corporate leadership energy is focused on keeping people in line, rather than helping them achieve their best working lives.
Autocratic managers are somewhat incredulous that those lower down the organisation chart should be given the chance to be self-directing, doubting that they could ever be as smart as they are. But they should be telling their staff to "think it through, make your decision, understand why you made it, and, if it turns our to be wrong, then you are more likely to get it right next time".
People grow by being allowed to experiment. Companies grow by allowing those people who are experimenting to work together to come up with something even better.
The old working ways are no longer effective. If your company insists on working like it did 30, 40 or 50 years ago, then you need to move on. If you are leading such a company, then you need to realise that command and control management needs to be replaced by trusting and inspiring your people. Getting the job done and bringing your team with you is what boosts your career.
Pragmatic steps to take
- Take time to engage your employees. In many legacy organisations, less than 20% of staff are fully-engaged, but a similar number are actively disengaged, and undoing the good work of others. The business case for employee engagement is clear. Engaging positively with your peers is a good personal growth tactic too.
- Move to a cross-functional organisational structure. The simplest way to avoid a command-and-control management style is to move to an organisational structure that ensures that staff and management focus on the customer. You will need to help some of your managers become servant-leaders, and you will need stop some of them trying to impose their will on people who now only report to them on a pay and rations basis, not for task execution.
- Don't measure your staff on things that don't matter. It is usually very apparent who the stars are, and, in a cross-functional, employee-engaged culture, your staff will let you know who they are. Similarly, the very few real underperformers or troublemakers can be discretely dealt with. Treat people like responsible adults and they will behave that way.
- Revise your Employee Handbook. Keep what is required by law, and what explains company values, but remove all of those arcane clauses that were remedies for something bad which happened once, a long time ago.
- Avoid Performance Improvement Plans. Start including your teams in problem solving and do so all of the time, making it part of the culture. Together work out why there was a disturbance, time-keeping problem or an operational slip-up, and come up with the answer together. Singling out individuals for censure chews up manager's time and reinforces a blame culture, neither of which is helpful.
- Change your recruitment policy. Stop hiring by keyword search and start having open conversations with plausible candidates. Look for attitude and potential as well as experience. Most people want to succeed and it is a failure of management if they don't acquire the skills to do so.
- Get everything out in the open. Talk about what matters at team meetings. Nothing is off-the-table. Discuss how things can be made better for employees and customers alike.
A trust and inspire culture is a win for everyone concerned. It leads to an agile business, which has a much greater chance of surviving the commercial jungle, and is an infinitely nicer place to spend a significant part of a life. Don't leave it much longer until you get your company to embrace it.
If you need help with this message, or with moving to this new culture, then Aston Beck would be pleased to help.Drop us a line
Some of the points raised in this post are explored further in these other articles: