Showing posts with label Productivity. Show all posts
Showing posts with label Productivity. Show all posts

Wednesday, 2 May 2007

Empowerment - Nobel or Patronising?

Empowerment goes to the heart of good governance, good democracy and good business. Being a leader is not about getting someone to do a task but making them want to so they do it without asking.

Lisa Haneberg has something different to say about that:

Saying you want to create a work environment where people do their best work and then failing to collaborate with employees (notice I did not say empower, which is generally a fake term and patronizing) about projects and decisions that affect their work - that's management on the cheap.


Apparently empowering people is 'patronizing'. Having experience in politics, I know this to be far from the case.

She does however touch on an issue that many free thinkers and leaders forget; that not everyone shares our vision. I have seen many people lose their control with employees, who are often earning the minimum wage, for not going above the call of duty.

You must not forget that whilst you have invested everything into a project; belief, time and money all for a greater spiritual or financial return, those you have brought in won't have. After all, why should you work your butt off for a low wage, or if viewed differently, low Return On Investment? Empowerment, a term used often in politics, is superficially thought about meaning 'how' to get people active and involved.

If you dig deeper, it is however about something different; the 'why' should people get involved.

Solve this latter question and the former will follow suit. As entrepreneurs, team leaders and blue sky dreamers, you must think about the 'why'.


  • Why should people believe in your idea as much as you do?
  • Why should people work their buts off for you?
  • Why should people work harder the ruder you are?


If you can empower people, you can do one of the key things required of you as leader and rainmaker; motivate. Help people share you vision by focusing on the why, and the how and if's will follow.

Tuesday, 1 May 2007

Leading, Not Managing

Leading a team can be hard work. My father always said that when leading a team you had to be able to do what they did, and take on the extra responsibilities that come with leading a team in 'extra time'.

As a child and then teenager, this marred with my own views of being a leader that came from watching many macho films. I had always wanted to be an officer in the British Army, and was well suited to it. Not incredibly intelligent, but active, fit, a desire for action with a smattering of backbone and dislike for the mundane and average meant I was well suited to it. The only reason I did not sign up was due to having grown a conscience - would I be happy with fighting other peoples wars?

This article is not and debate on the merits and place of an army in a democratic society. But leading at the time did seem to me like doing what others could do, but for longer, better, and harder.

As someone who wanted to be an officer I believed you had to lead from the front. That meant being able to run faster, lift more weight, work for longer and just do more work better.

That all holds true, and went some way to gaining a lot of respect from older colleagues in the cadets.

However leading is more than just doing more work. It is more than managing. It is about people. Leading and managing often get confused. In the article manager or leader the distinction is made clear.

Selection of those who work with and around you is important. Unfortunately there will always be people who are happy to live the nine to five, work to live not live to work live life style. You need to make sure you can get the best possible team around you.

However once that is done, are you doing the best you can to keep people motivated? Getting bogged down in the nitty gritty of programming, something that is enjoyable and invigorating, could be detracting from your true responsibilities.

Your job may not be about running faster, but making sure other people do.

Wednesday, 25 April 2007

Can you think positively?

Jeff Atwood wrote an excellent article that resonated with my own experiences on what separates a good programmer from a mediocre one. His advice was to take a step back from the programming itself, and broaden your skill set; not through learning more languages but learning more about the user, the industry and the business as a whole.

Atwood quotes Bill gates from the book Programmers At Work rings so true;


Does accumulating experience through the years necessarily make programming easier?

Bill Gates: No. I think after the first three or four years, it's pretty cast in concrete whether you're a good programmer or not.


It was clear, I hate to say, who the good and the bad programmers were on my Masters. Now why was it? Naturally, and rather immodestly, I counted myself on the side of the fence that shepherd the good programmers. But why?


  • Was I that intelligent, other and above others? No.
  • Did I have more experience then they? No
  • Did i have access to more/better study materials? No


I went through many similar questions, before finally finding the answer: I was patient and willing to learn.

Because I always assumed I would learn to programme, and programme well (which I still am doing - you never do stop learning), any time I came across problems I was able to surmount them while others stumbled, lost confidence, and eventually gave up.

Boris Veldhuijzen van Zanten wrote an interesting article looking at and comparing the thinking patterns of successful and unsuccessful entrepreneurs.

The attitude of the failing businessman matched exactly those of my failing classmates, who would focus on short term problems and not the final goal.

When I trained to do a static parachute line jump, pretty much everyone on the course were motorbike riders, including the trainer. When it was explained to us how to avoid not ending up swinging from a tree, the analogy of two motorcycles riders was used.

They are both going round a bend with a tree on the outside corner, the first looking at the tree he wants to miss, the other looking at the point on the road where he wants to come out of the corner. Which one hits the tree?

My fellow masters students who kept focusing on the hurdles, without keeping their eye at the end of the track, were the ones who fell.

Is the way you think, your attitude, the real barrier to your progress?

Friday, 30 March 2007

Table Of Contents

In the voice of usefull information it is I write this post.

Programming is the name of the game. However there are often those nigley jobs that have to be done. Those secondary, even tertiary tasks that are small, unlikable and unavoidable.

It is in this manner that I hope to make the lifes of everyone who has to write a report that bit easier.

The contents section at the beginning of any report is always best left done to the end. Before i knew this feature of Word, I hated doing this. Every section removal, chapter addition or page change would lead to a slog to the contents section to make sure that everything else matched.

Alas it was pointed out, as is now to you, that Microsoft Word has a nifty feature of generating Table of Contents automatically for you.

Here's how you do it.

Step 1 Go through your document and give each chapter heading you want to appear in the contents a style format h1. Thats right, select the text and go to styles. From there just chose h1.

Step 2: Now inside every chapter, if there is important bits that you also want to appear in the contents, select it and style it with the h2 format.

Step 3: At the page you want to insert the table, choose Insert > Reference > Index and Tables. Click on the Table of Contents tab and then click OK.

Step 4: Edit it to your hearts desire. If you had made changes to the document and the contents is not reflecting this, press F9 for options on updating and editing it.

There you have it. My first usefull information post. I had to give in a report today and this was most useful. Now for you rascals who don't know this get back to work and give me ten lines.

'Insert > Reference > Index and Tables'
'Insert > Reference > Index and Tables'
'Insert > Reference ......'