Tuesday, October 15, 2013

I don't own my team

If you know me you know that I strongly believe that the language we use shapes our thoughts. I hate the dehumanizing use of resources when we mean people, or use of 'the business' when referring to people outside of IT.

The new phrase that I'm trying to eradicate from my language is 'my team'.

Since moving back into a team lead role I've started using this phrase again and it's been making me feel increasingly uncomfortable. It does so in two regards. Firstly, it's possessive as if I own the team. Secondly, it makes me feel that I'm solely responsible for the team and their output.

In conversations with other team members, I've switched the my to an our. When talking to people outside of the team, I'm starting to refer to my own team by the team name. I also noticed that  have been referring to other teams by team leader name. This needs to stop too.

By using our I feel like we're all in it together rather than me being above the team or owning them.

Monday, August 5, 2013

Missing feedback loop. How can I serve a team member better?

In one-to-one meetings with my managers, past and present, I've asked about things I could do better. I've just realised that I've never asked the people I manage the same thing. How could I serve them better?

Some people might see this as weakness, but I see it as the opposite. If I'm not getting feedback other than top down, I'm missing a critical piece.

This shouldn't be an annual thing either, but a continual process of improvement both ways.

Of course this is going to require trust, which has to be built over time, but it's not going to stop me taking the first step.

Friday, August 2, 2013

The absurdity of 'the business'

I've often heard software development departments refer to other parts of the organisation as 'the business'. Not only is that wording divisive, but it's also completely absurd. I've often heard the same departments that we call 'the business', also calling other parts of the organisation 'the business'. We're all the business; we're not a lesser or greater part; we're all in it together

Wednesday, May 1, 2013

Software development career treadmill

In my last post I outlined many of the reasons why software developers are a good model for career resilience. It was based on the fact that we have to be resilient due to how quickly technology and trends move.

Several times in the past, I've been asked what one thing would I tell people considering a career in software development. I always give the same piece of advice; be prepared to continually learn.

There are downsides to this continual learning cycle though; I've dubbed this the software development treadmill. This treadmill keeps on going at a slightly uncomfortable pace and doesn't relent no matter how tired you get. This continuous pace requires you to have a passion for software development. Without that passion, it's been my experience, you'll washout or stagnate into a career deadend. Passion is critical because it will help keep you motivated to continually learn and practice, most often in your spare time.

Even those who do continually learn and practice aren't guaranteed to always be on top of new technology and trends. This is mainly because there are so many things that you could spend your time on. You end up having to pick and choose based on what interests you and your guess at where the industry is going. Sometimes you'll hitch your cart to the wrong horse and will have to leave that deadend; then scramble to catch up with what the market is actually doing.

For developers in the west, there's also the constant fear of being outsourced. This adds an extra pressure to keep up.

Eventually even lifelong learners can get tired of this unrelenting pace of change. Traditionally developers would move up into management, where their development skills don't have to be as sharp. That said, I've noticed that with the advent of self-organising teams and flatter hierarchies, there's less of a need for management and therefore less opportunities for promotion; these positions were limited before anyway. As a result we're staying in development jobs for a lot longer. This presents additional challenges. As you get older your family commitments generally increase. This means that you have less time to learn and practice on your own time.

Finally there's an unspoken darkside of being an older developer and that's that it's seen as a young person's game. There's a myth in the industry that young people are far more creative. If you want to have a long career in software development you'll need to be on top of your game.

Has this been your experience as a software developer? I'd love to know either way.

Monday, April 22, 2013

Software developers are a model for career resilience

Since the official end of the Great Recession, the private sector has pretty much rebounded. The Dow Jones has recently hit all-time highs and some companies are now posting record profits. Despite this, unemployment has remained stubbornly high. In the US there are three unemployed people for every job opening. We've also seen old business models are being disrupted and companies that can't adapt are closing their doors.

With this in mind, people are now having to become more creative and adaptable with their careers. You can no longer rely on a company to help you design a career path. It's up to you now.

In a recent conversation it struck me that software developers are naturally career resilient and, in my opinion, serve as a good model for others.

So why are we more resilient? Because we have to be.

Our field is always in a state of flux. Programming languages, frameworks and technologies go in and out of fashion. It's very easy to get caught out by focusing on one language and suddenly finding that the industry has moved on; leaving you behind. This is hard to come back from. If you don't continually keep on top of new technologies and learn new skills, you'll stagnate and be stuck.

Another reason you can get stuck is due to skill related pay. When you have a skill that's in demand you get paid a premium for that. When the market moves and you don't, you can struggle finding a new job that pays as much as the previous because that skill is no longer in demand. This might not be completely obvious until you try to make a move.

Another wrinkle is that technology choice can be geographical. For example, working in London in the late nineties - early 2000s most web application shops used Perl. When I moved to Houston there were very few companies that were looking for Perl developers. I ended up finding a job at one of the few Perl shops in Houston, but the local industry moved to .NET so I did the same.

Software development contractors are even more resilient than their fulltime counterparts.They are able to shift from position to position; only looking for the next position a week or so before the current one ends.

How resilient is your career?

For more information about increasing your career resilience, I recommend reading the following article by Michele Martin:

Career Resilience: The Four Patterns that Should Guide All Your Career Moves

Friday, February 22, 2013

New name, new focus

Those that have been reading my Scrum+ blog for a while might have noticed that the name has recently changed. This is because my main focus is now around building better places to work and my blog posts were starting to be only on that topic. Thanks to everyone that has visited over the last few years and I hope you'll continue to read as I post about this new focus area. Thanks to +Michele Martin for the name suggestion as well as others that contributed to the renaming effort.

Let's break our dependence on being told what to do

The 20th century model of work was one of hierarchy, one where your superiors you told you what to do.

Many people are still stuck in this mindset. It's easy to do. When you're not being told what to do you feel uncomfortable and unsure what to do. I've fallen into this at times in the past too.

The problem is, if you are dependant on being told what to do, you become less creative, adaptable and resilient. If you find yourself in an uncertain situation, you're more likely to fall back on things you've done in the past rather than looking for something new.

Right now, the future of work is uncertain. We're currently going through a time of rapid technological innovation. Organisations are able to do more with less people. Companies that don't innovate are going out of business as new ones disrupt legacy business models. This amongst other things, is causing unemployment to rise. Hundreds of people are competing for a handful of jobs.

As existing jobs are automated we're going to need to find new problems to solve, which means people to be able to think for themselves.

I believe that we should create organisations that have a culture of innovation, where all employees can use their own creativity and ingenuity to solve problems. Not only will this help companies become more adaptable and resilient, but by doing this we can help people break the dependency on being told what to do. This in turn, will help them find their own ideas to tackle and ways to thrive in this uncertain future.