Introduction
Reading Impact Networks has obliged me to reflect deeply on what a staff network is. The book is about human service-oriented networks and networking practice in general, rather than a deep dive into staff networks.
We use the term staff network without really defining the term. What is a network? How do the words staff and network go together here? Is what has been created really a network? If not, am I okay with that?
Below I want to reflect on what I took from the book, including revisiting my own time as a staff network chair in the context of thinking about whether it was really a network. But first I want to think about ways to imagine what a network might be
What is a network?
We are familiar with the idea of road and rail networks, and electricity networks. Elements are interconnected and purposeful activity flows through them.
We now understand that forests are networks of trees and other plants joined together beneath the soil as their roots and fungi create a mutually sustaining web – the wood-wide web. Suzanne Simard’s Finding the Mother Tree: Uncovering the Wisdom and Intelligence of the Forest is an especially inspiring book on this theme.
Networks are the foundation of who we are and what we do. They are based on relationships grounded in trust and mutual regard. On an organic level they are the basis for ecologies. On a systems level they are the foundation of effective complex communities.
Essentially, when 2 people come together we have the germ of a network. What purpose it has and how effective it will be in achieving that purpose is what we need to think about next.
Creating intentional purpose driven networks that are effective in attaining their objectives is what Impact Networks is about.
A Disability Employee Network
When what is now called the DCJ DEN [Department of Communities and Justice Disability Employee Network] was created in 2010 it was a network in the sense that staff with disability came together 4 times a year to provide input to the department’s HR team on issues impacting staff with disability. At some meetings there might be 6 or 8 HR representatives present.
There were around 20 staff with disability from across the state who had volunteered to join the DEN, and who came together only at the meetings. This was a time before virtual meetings were usual. The meetings started around 9:30 and continued to 15:30 -16:00. Back then the DEN was essentially controlled by HR. It was a consultative network.
I changed that in 2016 when I unexpectedly became DEN Chair. Member numbers had crashed because of a departmental restructure that saw a lot of staff leave and we merged with another department which brought in new staff with disability, but who were unaware of the DEN.
My immediate task was to rebuild the membership. That happened well enough, but I was still thinking in the same old way – the 4 meeting a year were the focus of activity. Things changed in 2018 when I was introduced to the idea of Networkology by Kate Nash, CEO of PurpleSpace. My immediate realization was that there was a ‘science’ behind this – and that we (staff with disability) could drive it what the network did.
Over the following 18 months we built (or contributed to the building of) a network comprising:
- 15 colleagues with disability from across the state, and with a variety of disabilities. This was the Guidance and Action Team (GAT). The GAT had 4 full day meetings a year when we consulted with invited staff from key business areas. We also had running conversations via email that seemed to be daily. The GAT became the heart of the network.
- A supporting alliance of leaders was created. It included the Secretary, the Deputy Secretary Corporate Services, another Deputy Secretary who was the DEN’s Executive Champion, another senior executive (who subsequently became the Executive Champion following another restructure), and the Inclusion & Diversity Manager. The DEN had nothing to do with setting this up – other than establishing that we could be trusted. More about this later.
- We grew the number of network champions from 1 to over 30 over 12 months. While some were immediately active, others were well-intended but in need of guidance. For a time, the Executive Champion at the time worked to craft a champions network but that work ended when they left the role. There was a great untapped potential there.
- We encouraged staff without disability to sign up as allies. At one stage the number of champions and allies exceeded the number of DEN members with disability. Being an ally could be cover for people with invisible disabilities to be safely engaged with the DEN.
- I created relationships with the CEOs of PurpleSpace and the Australian Network on Disability and an independent accessibility consultant.
- I also reached out to the Executive District Directors, nearly all of whom were responsive and supportive of the DEN in regional areas.
- We set up program of roundtables where volunteer staff with disability told their stories to colleagues and executives under managed circumstances. The roundtables were run by a DEN member who had offered to take on this additional workload.
- I set up and oversaw consultations between staff with sensory disabilities and IT staff on tech accessibility concerns.
- We initiated or participated in forums where I and several other DEN members talked about the lived experience of being a person with disability in the workplace.
Creating linkages was one thing and maintaining them was another. I emailed monthly reports to all members and had a separate monthly Champions’ update. I also worked with Officer of the Secretary to ensure there were regular messages from the Secretary in support of the DEN going out to all staff. New DEN members received a welcome email from the Secretary. I later discovered that this was an extraordinarily powerful thing.
Looking back, what we worked to create was a genuine network. The Big Idea I took from the concept of Networkology was that what was needed was energy that was focused and steady. Meeting 4 times a year with occasional consults in between fitted the purpose of the department, which was in control. But it didn’t suit our purpose. We had to be politely but persistently impatient. We wanted things to change, so we took the initiative to get moving. Our approach was collaborative, so we had the essential attributes of a network – interconnection and energy. We were impactful. We were trusted.
We had the essential elements of a genuinely impactful staff network in place:
- The GAT and an engaged membership
- A strong relationship with our Inclusion & Diversity team
- A strong relationship with our executive leaders.
- A growing number of engaged Champions.
Key features of an effective network
The title of Impact Networks makes it clear that the book about effective networking. Making an impact is important to me. Why get involved in doing something that doesn’t deliver a positive outcome for the people in whose interests I have decided to act? Here are some things I jotted down while listening to the audiobook.
- Relationships are the heart of networks.
- Without good relationships effective collaboration is not possible.
- Relationships must be trust-based. Without trust, networks cannot function.
- Networks are not hierarchical.
- Develop a deep and nuanced understanding of the cause of the problem/challenge being responded to.
- Driving systems change – is a goal but should be envisioned in terms of “pockets of possibility”. For example, disability inclusion might be a universal goal, but a disability staff network can effectively work only within its organizational context. If it does that right, then the impact might travel to a beyond the organization. But if fails to have that local impact there will be no enduring change for the better. We work to create the possibility of positive change.
Impact Networks has excellent advice on how to structure and run a network that can be scaled down to staff networks. Here I want to focus the idea of networks rather than a ‘how to’.
Building relationships and growing trust
There is nothing more vital to a network than trust-grounded relationships. I reached out to one of the executives in point 2 above to get some deeper insight.
In most cases there’s a power imbalance to be addressed. If there is a mistrust of executives that imbalance is exacerbated. It is impossible to establish a relationship of trust if the regard is not mutual.
Executive sponsors and champions have an opportunity to actively engage in connecting with network leads and to have exploratory conversations. This can go a long way toward mutual trust building.
The message I’d convey to staff network leads is that if you want executive leaders to support your network, establish a relationship that can confirm your credibility and earn their trust. Regardless of who initiates the relationship, it should not be about one-one connections. It is better to meet with sponsors and champions along with other members of the network leadership group. A discussion facilitator should be identified ahead of time. Initially this would best be an executive – just to address any status anxiety that might be triggered in network members. Besides, executives may naturally want to take on this role. An agenda would be a good thing to have too.
Trust is always earned, never demanded. Sound leadership always wants evidence of, or a compelling case for, a value proposition. Whether its private or public money evidence of, or a compelling argument for, a return on investment is expected, if not required.
Trust is built on more than sentiment. A staff network might be a good cause, but its ability to deliver desired/agreed outcomes is the ground upon which trust is established. Hence this is the basis upon which investments in the network continue to be made.
A group-based interaction has the chance of creating a shared sense of community with a common commitment the network’s purpose. We need to remember that relationships are not purely transactional. This can be a difficult thing to adjust to for network members accustomed to interactions that are not only predominantly transactional but also carry an acute awareness of power imbalances.
In the context of executives and senior leaders [as sponsors and champions] being members of the organization’s leadership in-group there’s much to be said for them taking the lead in establishing relationships with network leads – if building that relationship seems to be slow in happening.
The org wide web
Large organizations are ecologies. They are like forests. Their cultures are key factors in determining how healthy they are. Staff networks can take on the role of ‘forest carers’, looking out for the culture, shaping it towards inclusion, fairness and kindness. But this should be an active and equal partnership with inclusion professionals and executive leadership. Indeed, with anyone who wants to participate.
It is important to understand staff networks as intentional dynamic systems that arise from within a complex organizational environment to influence behaviour in favour of a shared sense of wellbeing. They are not apart from that environment, but an expression of it.
Organizations tend to be bureaucratic and hierarchical for necessary or habitual reasons. But the organization’s culture is neither bureaucratic nor hierarchical. That’s where staff networks sit. Our vision for the DEN was that membership embraced sponsors, champions, allies and staff with disability. All were invited to meetings as participants.
What we created wasn’t perfect, but it did create a sense of what was possible and converted many possibilities to actualities.
Conclusion
All staff networks are ERGs, but not all ERGs are staff networks. Regardless, all ERGs engage in networking to some degree. Below I will refer to what staff networks do as ‘active networking’.
ERGs must decide whether they are active networks or whether networking is just a strategy. If they are active networks, becoming familiar with Networkology is essential – and Impact Networks is a very well-crafted tool. I also highly recommend PurpleSpace, but that’s a membership-based org. You will probably have to get your organization to pay the membership fee.
If the response is that your ERG is not a network, I’d suggest revisiting your ERG’s mission in the context of the problem you are responding to. It’s not that I am implying a criticism. It’s just that ruling out being an active network is a huge methodological commitment to make. Maybe read Impact Networks to be sure the best choice has been made.
The thing about networking, as I learned, is that you can do it sub-optimally and not be aware that you could do far better. I was fortunate that I had an epiphany in May 2018. I could have been a passionate trier fated to be marginally impactful were it not for the discovery of Networkology. I see on the net that the name has been colonized by an IT org. That’s a pity. It should have been left alone as way of knowing how to do networking very well.