Mark Olson was right about big ops
Jan. 28th, 2013 09:12 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
As many people who have ever stood still for five minutes within my earshot know, I believe that organizations pass through phase transitions as they grow, with the major inflection points being at 10, 50, 250, 1250, and I speculate 2x5^n for any integer n. The two major ways that I model this are organizational fanout, wherein the maximum number of reports is 10 and the best achievable indirect reporting efficiency is 50%; and communications modes, which relate to Dunbar's number and the limits of human comprehension. Communications mode shifts each have a different description and there is enough material that I will probably eventually write a book about them, so I won't describe them here.
A consequence of this, as again many of my readers will have heard me say already, is that as organizations approach one of these inflection points from below, they begin to adapt to keep their communications and control structures working. They optimize for output from individual contributors at the expense of encouraging teamwork and delegation to keep their headcount from rising. They put infrastructure in place to smooth the existing, but fraying, means of communication. There are countless such knobs and I'm sure my book will include descriptions of many of them.
But for the organization to successfully pass through a transition point, all of these knobs, having been turned all the way up, will have to be turned all the way in the other direction. The organization suddenly needs entirely new communications infrastructure. Organizational cohesion will have to be replaced by unit cohesion. Delegation and teamwork suddenly takes priority over individual output. Schedules and timelines will suddenly be driven from different points as communications modes shift1. And so on.
Note, importantly, that it is not enough to recognize an optimization as being specific to the lower approach to the phase transition. To turn the knobs the other way, you have to know what the other way is. You can't just rip the knob off.
Big Ops is a knob. We use it in volunteer organizations of 249 people to keep the singly-indirected, centralized communications flowing. When the organization reaches 251 people it begins to drop information -- sometimes critical information.
Boskone recognized this as a problem and tried to solve it by ripping the knob off, with predictable results. Arisia seems to have found the other end of the knob, because the Ops desk at Arisia 2013 was positively boring. Information was flowing around it, and getting where it needed to go. We threw so many replacement options at the problem that it is hard to say which one is the other end of the knob, but I think one thing that really helped was having so many people still reading their email at con, so that information could reach, for instance, hotel liaisons directly from the departments that needed to reach them, without Ops having to get involved.
We do still need an Ops desk. They will still need to be prepared to deal with the kinds of big-Ops activities that used to happen there. But if this year is indicative, Big Ops is withering away.
1. more on this in another post, because it is a brand new discovery for me.
A consequence of this, as again many of my readers will have heard me say already, is that as organizations approach one of these inflection points from below, they begin to adapt to keep their communications and control structures working. They optimize for output from individual contributors at the expense of encouraging teamwork and delegation to keep their headcount from rising. They put infrastructure in place to smooth the existing, but fraying, means of communication. There are countless such knobs and I'm sure my book will include descriptions of many of them.
But for the organization to successfully pass through a transition point, all of these knobs, having been turned all the way up, will have to be turned all the way in the other direction. The organization suddenly needs entirely new communications infrastructure. Organizational cohesion will have to be replaced by unit cohesion. Delegation and teamwork suddenly takes priority over individual output. Schedules and timelines will suddenly be driven from different points as communications modes shift1. And so on.
Note, importantly, that it is not enough to recognize an optimization as being specific to the lower approach to the phase transition. To turn the knobs the other way, you have to know what the other way is. You can't just rip the knob off.
Big Ops is a knob. We use it in volunteer organizations of 249 people to keep the singly-indirected, centralized communications flowing. When the organization reaches 251 people it begins to drop information -- sometimes critical information.
Boskone recognized this as a problem and tried to solve it by ripping the knob off, with predictable results. Arisia seems to have found the other end of the knob, because the Ops desk at Arisia 2013 was positively boring. Information was flowing around it, and getting where it needed to go. We threw so many replacement options at the problem that it is hard to say which one is the other end of the knob, but I think one thing that really helped was having so many people still reading their email at con, so that information could reach, for instance, hotel liaisons directly from the departments that needed to reach them, without Ops having to get involved.
We do still need an Ops desk. They will still need to be prepared to deal with the kinds of big-Ops activities that used to happen there. But if this year is indicative, Big Ops is withering away.
1. more on this in another post, because it is a brand new discovery for me.
no subject
Date: 2013-01-28 03:59 pm (UTC)Also, I personally think communication in a group starts dropping off below 10 - maybe around 6 or 8 people. but that may just be me rather than a universal.
no subject
Date: 2013-01-28 04:31 pm (UTC)Boskone could have replaced Big Ops with the Voodoo Message Board and given staff instructions to check it every hour. That our Voodoo Message Board is electronic and in our pants is not the innovation.
no subject
Date: 2013-01-28 04:45 pm (UTC)Huh?
Date: 2013-01-28 04:35 pm (UTC)(I do understand, I think, what Ops and DevOps are in an Internet company -- just as a point of reference.)
*shrug*
Mostly just FYI, in case you didn't realize who might be included/excluded by your word choice.
Re: Huh?
Date: 2013-01-28 04:45 pm (UTC)Re: Huh?
Date: 2013-01-31 07:10 am (UTC)This phrase also jumps out at me:
"I think we completely misunderstood the problem."
Re: Huh?
Date: 2013-01-28 04:59 pm (UTC)What Ops does at Arisia shifts a little bit from year to year. But for the last several years the notion has been that if you're a staffer with a need or a question, you came to ops. I agree that things were more decentralized this year, and it's an interesting analysis.
In general (with some exceptions of course) things were calmer this year, so that may have just been a case of boring = good when it comes to con operations.
email not for everyone
Date: 2013-01-28 05:27 pm (UTC)I do think there were some interesting trends this year. Use of cell phones rather than radios for Div Heads.
However, I think communication this year was very disjointed and disappointing. Many people didn't get the memo on the sign policy and staff still used things other than blue tape and put things in elevators. Late checkout was a hairball. The pre-con "newsletters" were often a day late with incomplete information.
I.E. I really don't think this year was any better than past years - it was just "different".
IMO, we need to do a better job of subscribing staff (or at least Area Heads to Staff-Announce or a new Area-Heads mailing list and sending information there. I also don't mean sending meeting minutes there. I mean one item at a time. When some people get a two page message summarizing a meeting, they just don't read it. The sign policy should have been sent to staff-announce. A reminder about only blue tape should have been sent to staff-announce. Information about late checkout should have been sent to staff-announce. As separate messages. And lack of information about Massage Den was a total mess. After I found out about it 24 hours late, I had to leave a meeting and make about 6 phone calls to inform my direct staff. I could go on.
-$.02
Re: email not for everyone
Date: 2013-01-28 06:49 pm (UTC)Re: Big Ops
Date: 2013-01-29 03:39 am (UTC)Re: Big Ops
Date: 2013-01-29 04:21 am (UTC)Changes in size affect Arisia more indirectly, through changes in budget, which allow us to do fancier things. For Arisia these things often cost volunteer time as well, and the real reason we want to grow our organization is so that we will be able to do all of the awesome things we can now afford. Does FRFF also add more things as they find they can afford them? Or do they do a similar number of more expensive things, in the form of getting in more expensive acts than they could have afforded before? Spending more money per timeslot wouldn't have a lot of staffing impact.
Re: Big Ops
Date: 2013-01-30 02:56 pm (UTC)