10 reasons your people are just like so over your scaling

We recently sent out a survey about scaling organisations and 83 of you responded. Thanks very much to all those who took part! This is a great response and it made us realise we really hit a nerve in our community with this question. If you missed out the first time, you still can still contribute to our results over here.

We asked:

Have you ever left an organisation because of the changes that have come with scaling?

tumblr_nnslm6b4xa1spaqz2o1_400
twinpeaksgifs.tumblr.com

  • 54% of people we asked answered yes.
  • 61.4% of people also said their preferred organisational size is different from the organisation they currently work in.

From this result, we have concluded that half of your employees may leave if your company scales. For example, if you have a company of 100 people that you want to grow to 200 people, you may need to hire ~150 people to get there. Perhaps you could invest that extra energy, time and money into building and supporting your company culture?

This week at Agile Manchester, Minimum Viable Book co-author Emily gave a buzzfeed-style lightening talk with 10 of the most commonly held responses to our survey.

We’ll be publishing the context and the full results of our survey in a new edition of the Minimum Viable Book soon, but in the mean time, here are 10 reasons why your people are like so over your scaling. I hope you enjoy them – and the painstakingly chosen gifs :).

1. They focused on managing spreadsheets rather than meaningful work

giphy-13
tumblr.com

People dislike the overhead of meetings and bureaucracy, and these are common features of larger organisations. Most people hate spreadsheets. They just want to do meaningful work rather than waste time reporting on their work.

2. The organisation became more ‘corporate’ as it grew which didn’t suit me

giphy-11
tumblr.com

People like the family feeling, knowing everyone and the ease of collaboration that comes with smaller organisations.

3. Lack of managerial experience leading to a lack of support

giphy-3
gifbay.com

Fast-growing organisations were thought to have less support for their staff as management were also learning how to deal with the growth themselves. On the flip side, larger companies can offer better benefits to their people as they have more resources available.

4. Mediocre people were hired. It became a game of paying the bills, not taking risks


reddit.com

People felt growth sometimes led to rapid hiring and were frustrated that people they didn’t respect were hired. Money was seen as the focus instead of making interesting things. The flip side in the client services sector is that smaller organisations don’t have the clout to attract the bigger clients, which can lead to fewer options for personal career development.

5. People feeling like they are working against each other rather than with each other. Silos.

giphy-7reddit.com

Smaller organisations generally have flatter structures and less hierarchy, which was seen as a bonus. Smaller, however, can also mean over-worked people.

6. Being pulled in two directions by two (back-stabbing) bosses

cuzimmathug.tumblr.com

Smaller organisations were thought to have less politics. Although it was also suggested that a small conflict in a small company could affect the whole team more dramatically.

7. Big companies = generally more bureaucracy, sign-off points and politics which can make it harder to do something

giphy-15brooklynbookgirl.tumblr.com

HR functions were cited a few times as an indicator of bureaucracy and the inability to ‘just get things done’. HR did not get good press in the answers in general (sorry HR people).

8. Loss of focus and control

giphy-2
reddit.com

Smaller organisations were said to have a clearer shared vision. Larger companies find it harder to keep everyone aligned.

9. The loss of original culture, and a new obsession on the bottom line

giphy-6
reddit.com

Our survey tells us culture was a big factor as companies grew. People felt the culture changed in large-scaling companies and was not what they originally signed up for, while the focus shifted from people to money. In much smaller organisations however, our respondents felt they were likely to meet less people, so they had a higher probability of not liking the people they work with.

10. The company became less focused, more chaotic and lazy

giphy-12
reddit.com

If there isn’t good leadership and alignment, it appeared to be easier to hide. People said they get lazy and get away with it.

How our research has evolved

We have been researching the minimum viable book for a year now and in that time our approach has changed and evolved. We have changed too. Our research has fuelled our learning and being flexible has allowed us to explore avenues that we didn’t expect.

When we started on this journey we raised a fear about research, the fear was:

“It’s not researched enough / there’s not enough data”

And our mitigation was:

“We will conduct multiple workshops and surveys per chapter”

So we set about planning workshops in a number of locations: London, Bristol, Berlin and Austin Texas. We brainstormed some starter topics and asked our readers what they wanted to know most about. While we were away, we planned interviews with interesting people in the spare time around the workshops so we could dig a little deeper into our topics.

What we found was that while the workshops were a great way to meet people and set us going, the bit that has really got us excited were the interviews.

We threw our net quite wide. The criteria for people we wanted to talk to was simple: people who make things or get things done. This led us to meet hackers, coders, makers, curators, inventors, educators, business owners as well as agile and lean practitioners. We found that some of the most interesting conversations happened in the most unexpected places.

Our interview style has always been fairly laid back and this hasn’t changed, we find a quiet spot and let the conversation flow. Initially we used the interview chapters as a starting point, but now we usually kick-off by asking people for their back stories, then gently guide the conversation towards some of the common themes we have found throughout our journey.

We see the value in remaining flexible and allowing for emerging ideas and topics – it’s really helped us along the way. Even as we approach our Beta deadline in a few months, we aren’t expecting our approach to stay the same. And we’ll welcome all those changes.
As Eve from Make ATX said in one of our interviews:

“Accept what you are doing might not always turn out the way you want it to, but who knows, it might turn into something better.”

Emily & Amy

Photo by: marcwathieu

The Results of our first Chapter theme Poll

Thanks so much to everyone who took time to fill in our poll about chapters, we had over 50 of you respond.

The poll is now closed and the top four themes, as voted by you, are:

  1. What can go wrong and when not to use Agile: The warning signs and when Agile doesn’t fit.
  2. Agile UX and design: How can UX and design fit with agile development? It does, we promise.
  3. Agile at scale: Implementing Agile to manage a chunky programme, portfolio or organisation.
  4. Planning, tracking and reporting: Waterfall isn’t the only way to get the governance processes your Stakeholders need. We’ll explore what you can do to measure progress, gauge insights and how to constantly learn as you go.

For us, this means that our first workshops will focus on the top 4 themes.

That doesn’t mean we won’t include other themes, but these are what you (the users) have told us are the most important.

The full results are as follows:

I don’t want to read this I don’t mind either way I’d like to read this I’d really like to read this I’d really, really like to read this Average
What can go wrong 0 2 9 20 19 4.12
Agile UX and design 0 4 9 21 15 3.96
Agile at scale 1 8 9 12 19 3.82
Planning, tracking and reporting 0 3 14 20 10 3.79
How to sell agile 4 8 8 11 20 3.69
Agile characters 2 8 15 18 5 3.33
Agile Everywhere 5 12 10 14 9 3.2
Getting started with agile 5 7 18 14 6 3.18
All the methodologies 3 11 16 14 4 3.1
Why people do agile? 1 13 20 9 5 3.08

 

In our next post we will announce the workshops.

Polling Station image by STML