Lessons from a bottleneck
Critical troubles due to extreme dependency
I recently spent some time studying about graphs and it was during one such session that I came across the concept of a super node:
In graph theory and network science, a “super node” is a vertex with a disproportionately high number of incident edges.
The problem with super nodes is that when it disappears from the network, the system is in a chaotic position and functionality performance rate decreases.
I quickly drew analogy of this to the countless past team collaborative works I have had while working in a team. I wish to explore two such instances.
Super node can never leave peacefully
When I was working in the content team, my boss Ms. Nikita Mallya would work round the clock to ensure the team generated high quality work. When asked if she needs help, she said she cannot risk closing her eyes for a moment as she would miss some error due to the incompetence of the rest.
Don’t get the wrong impression about her. She has extensively worked to nurture of every team member and through her mentoring, numerous other students, including myself, have immensely developed our ability to effectively communicate in words.
But her obligation in time became her duty that she cherished and the system is highly decentralized and stable. As a result, she lost the freedom to explore other avenues other than content writing — something she came to accept. You see, by the very fundamental design, a super node needs to be there because the output quality demands so.
Super nodes leave others carefree
I had the opportunity to organize a conference last weekend — MEC.conf, the developer conference. Months of preparation resulted in the success of this program indeed, yet there are lessons to be learned on closer examination.
Devdutt was highly driven to work and he was leading the planning phase to a great extend. Due to his extensive participation, his peers did not give much attention as it was taken care of.
However, Devdutt left the discussions when exams were nearing as he was concerned about his performance for the same — understandably. The down part was that now that the super node was gone, others did not know what to do as they did not pay attention to details previously.
When decisions had to be made, no one was willing to be decisive as everyone felt they were not as worthy as the super node to make the call — a phenomenon that cost us time and energy. All this could have been avoided if the unintended effect of over participation in the initial phase did not cause the rest to give less importance to the matter.
The super node problem occurs when the system is highly centralized. What we need is delegation of authority — empowerment of the members thus creating a second base of safety in the absence of the apparent super node.
