Standardisation in the Enterprise

In enterprises there is often a strong desire to standardise. The reasoning is simple: if we are all doing things the same way, using the same technology, then we can simplify our operations, benefit from economies of scale and make our people more fungible. So by extension, not standardising means duplicated effort, resources and expenditure. But are things really this clear cut? Perhaps we should begin by thinking about the meaning of the word standardisation and understanding the alternatives. »

Remote pair programming

During a previous job I spent a lot of time working with delivery teams on other continents, helping them develop software. I was lucky enough to visit them on several occassions for a week at a time, and whilst I was there made lots of progress working with the on-site developers. Unfortunatley I was not able to stay on-site for the duration of the project and so needed to find other ways of collaborating with the teams remotely from back in the UK. »

Socratic questions

In my last blog post, I looked at situational leadership and how different influencing styles and techniques can be effective in different contexts with people at different levels of maturity. ‘Push’ (directive) influencing techniques are more focused on “telling” whereas ‘Pull’ (non-directive) techniques tend to involve the use of questions and reflection to guide. One particular technique involving the use of questions to influence in this way is Socratic questioning. »

Leadership styles

Traditionally people used to think leadership was an inherent quality and that individuals have their own distinct leadership style. In practice, each style has its own strengths and weaknesses, situations where it excels and others where it is less effective. Therefore, whilst it is natural to have a preferred style that one feels most comfortable with, a good leader should be able to adapt their style depending upon the situation or context, the team or individual being influenced and the task at hand. »

Extending Go programs with plugins

I am really enjoying programming in Google’s Go language (Golang for search engines) but very occasionally come across things that aren’t really possible, or considered idiomatic, in Go. Go is a very opinionated language which is a good thing as it keeps the language and tool chain very simple but also means if you need to do something unusual, it can sometimes feel like you are fighting the language. One example of this is developing plugins. »