Friday, 9 May 2008

Why Is It Hard To Work In Large Companies?

I've noticed that lately my motivation for work has dropped away a little.  We've recently had a new bundle of joy, Emily, who being the 3rd kiddo means home life is very much about keeping on top of the cleaning, playing with the kids, etc.  I'd previously wondered if this is partly the cause.

But Emily is now 8 months old, and I still feel a degree of apathy, so what is the cause?

I've come to suspect the more likely candidate is work.

You see, I used to work in a small(ish) software house with around 130 staff, I think I knew around 80 of these guys at the time I left.  Since leaving this, I've started in a company with 40'000 staff.  That's a lot of people, a lot of voices and opinions.

Now that I have perspective, I see that there was a really good community there.  People talked from time to time, people challenged things, we worked toward a common set of goals, delivery of a package to our customers and potential customers.

I think that now in such a large environment, these voices may be too small to be heard.  That means you don't get to meet others with the same goals as you or the same problems.  I put my apathy down to a lack of community in my workplace.

I think a lot of the best IT staff do their best work when they have a community to participate in because they are engaged with others and challenges at an ability level without fear of recrimination or career damage.  Simply put, you need to swim with the same fish to be part of the school.

What do I mean by a community?

I believe a community is a group of like minded people with common goals who want to help each other achieve their group goals for mutual benefit.  Sometimes it can be knowledge shared, contacts shared.  Sometimes it can be shared problem solving.

Now, work in a big company and that horrible factor of politics starts to play up.  It's hard to be sure if someone is trying to prove themselves to others, trying to shift out of the way of a bullet, and so on.  Too many people are in it for the money.

I think the community is one of the unspoken requirements for the best development to exist.  Without it, people's views are not challenged or questioned and people find it harder to seek to learn.

And that's quite sad I think...

I'm left pondering how you create a community when,

a) you don't have a project or budget or authority to create one

b) creating such a community would assume you all have clear goals, rarely the case in very large groups of people

c) the community needs members to take a small risk and offer help to their detriment (perhaps they need to use some of their own time to do something).

So my challenge is to understand how to create such a community in a larger organisation when the focus is only on projects, delivery and milestones.

I'm inspired by the material out there on agile methods.  It is clear to me that this approach works best for software development.

I feel at the moment that I have to sort out the community I work in before I can really get my learning back on track properly.

Does this strike a chord with you, and if so what do you think the right way is to tackle the problem?

6 comments:

LornaJane said...

This really strikes a chord and, having worked in the same smallish software house, I know exactly the spirit you mean.

I've worked in large companies and small, and I don't know that this can be solved in large companies. My solution is to work for a very small company, and love it :)

Mark Aitken said...

I wonder if one cause is developers from smaller companies usually are multi-skilled, they don't easily fit into a single skill role which large companies tend toward. Managers find it easier if staff stay in clearly defined roles which contributes to the problem.

Breaking this trend is hard because there are complex goals in larger organisations and unfortunately too many managers without a clear appreciateion of developers jobs allowing them to understand how to get more out of them by promoting development of a community.

I think the answer here is for the staff who are multi-skilled need to step up and deliver their knowledge to those in these skill silo traps.

Without these leading people, there can be no community and no sharing of experience and knowledge and things tick over. Nobody likes change...

Smaller companies find this happens more easily because people are multi-skilled and need to borrow knowledge from each other. However larger places employ single skill staff therefore the variety of skills is less requiring less of a community experience to work that model.

Anonymous said...

I think you've pretty much hit the nail on the head - that smallish software company's new large parent company have several technical specialists to carry out all the tasks that I do at a local level, with just me.

I think it would be possible for staff in large companies to have a sense of community - I used to work for a big software company that had quite a friendly outlook and people from all over the business would help each other out - lift sharing, recommending business, social nights out, etc...

I think it's probably either part of the ethos or not though. If it's there from the beginning, and reinforced by managers, it'll continue to grow with the company. Enforcing a sense of community on 40,000 people would be a pretty daunting task, and it would need the full support / instigation of the board I think. Even internal blogging or a skills swap board would help break down those barriers between teams I think.

Unknown said...

Ditto what my other esteemed ex-colleagues have said. You have no voice in a large software company. If you do actually manage to say something, it gets swallowed up in politics and bureaucracy.

There's little room for spontaneity either.

Maybe a resolution could be found in breaking the big company up into little virtual-companies (of say 100 people) - so that you get the benefits of the small-company ethos, along with the benefits of economies-of-scale that big companies have?

Unknown said...

Mark, I am catching up on your blog to know you better; even if I am currently taking a lot of your free time at work. ;)

I just want to react to this article with my personal experience:

I think my greatest disappointment in a big company (and I knew it would be the case, but I was still foolish enough to "have it a go"), is that you feel like a very small cog. And someday, or even worst, most days, it feels like if you are doing a great job, or if you are doing a really crappy one, it's impossible to tell the difference at the macro level: Big projects will still stumble through their deadlines, releases will still be deployed, and the company will plough its way forward.

Whether it is to success or failure seems to have very little to do with your actual personal achievements, and more because of market conditions, financial & industrial alliance at the highest level, or the latest clever marketing campaign of the Sales Department...

Th.

Anonymous said...

Hi Mark,

Happened upon your blog entry a wee while back when I was looking into this sort of area.

Rather than repeat myself, I'll just post a link to my own blog entry...
http://jamiemilne.wordpress.com/2009/07/18/community-spirit/

Need to catch up some time!

Jamie.