discoposse

Insights from the GC Chief Nerd - Part 2 of 2

Blog Post created by discoposse Expert on Dec 6, 2016

In the first part of this post (https://greencircle.vmturbo.com/people/discoposse/blog/2016/12/05/insights-from-the-gc-chief-nerd-part-1-of-2), I highlighted some general points that make up the important aspects of community within the role of a Technology Evangelist.

 

There are other points, but let's focus on the 6 that I've listed to begin with:

 

  1. Enabling collaboration with the technology community at large
  2. Bridging internal community-driven initiatives to the public space
  3. Listening and learning how the community consumes and drives technology
  4. Sharing inbound learnings with my engineering and overall team
  5. Bridging gaps across the entire IT ecosystem
  6. Breaking down barriers across all aspects of IT, business, and community by focusing on people, process, and technology in a holistic approach

 

How does this pertain to the honorary role as Chief Nerd within the GC Community?  This is where we learn exactly what my goals are to empower this fast-growing, open community.

 

Sharing to Encourage Learning and Engagement

 

When I speak at events and in webinars, or through written medium such as here in the GC, the goal is to encourage learning and engagement.  Speaking among the technology and business community is how we create successful communities. Otherwise, we would measure success of a content creator on word count alone. There is no value derived by simply creating a one-way push.  It's about collaboration.

 

Let's have a look at each point and how i map this to empowering the GC Community.

 

Enable collaboration with the technology community at large -  That is important because it also notes how we must extend beyond our internal groups to expand our learning.  This helps to avoid what we often speak to as "preaching to the choir".  It's also called the echo chamber, which risks only subscribing to central and narrow viewpoints.  Collaboration thrives on differing approaches and opinions.

 

Bridging internal community-driven initiatives to the public space - this highlights another strong need for any organization. By sharing the community-driven initiatives beyond the walls of the office (virtual or physical), we open up more chances to drive true collaborative relationships.  This encourages project and product growth.

 

Listening and learning how the community consumes and drives technology - this is straight out of the Gene Kim, Three Ways school of thought.  Amplified feedback loops require as much listening (if not more) as it does talking.

 

Sharing inbound learnings with my internal team - by ensuring that the amplified feedback loop is carried across the boundaries of events, Meetups, customer engagements, Twitter chats, and more, the value is felt both inside and outside as well.  Guiding development teams and product management with tangible feedback means that I've connected people to complete the feedback loop, and if I do my job right, those collaborations can continue directly without any nurturing needed by me.

 

Bridging gaps across the entire IT ecosystem - this is an important part of many methodologies, whether it be agile, DevOps, Lean, and others.  I've talked in the past about "You call it legacy, I call it production" and the proverbial long tail of IT as we cross chasms with new technologies.

 

We have to make sure that we enable new methodologies and technologies while bringing the people and processes forward.  This is the art of bridging the gap.  It's also a skills building expedition as we enable folks in our community to learn new things.  Bridging gaps means empowerment and mapping of paths from one point to another.  Making this an open, collaborative effort also means that we map the path for others to follow.

 

Breaking down barriers across all aspects of IT, business, and community by focusing on people, process, and technology in a holistic approach - this is the culmination of all of the above.  I've set it out on its own to highlight the fundamental goal.  This goes towards the focus on inclusion.  We have to take in all details, data, people, processes, and technology.

 

The collective of all of these pillars of community Is what you're watching play out here.  The GC Community thrives when we engage the community actively.  All of these points and the work that I'm building on are reusable for you in your current role wherever you are.  Community starts within ourselves, and extends to our team members, our entire organization, and beyond!

 

Welcome to the journey.  Community is a wonderful thing. It's made wonderful by you.  I just hope to be a steward of something special that enables and empowers you all through what we are doing here.

 

Thank you!

Eric Wright,

GC Chief Nerd

Powered by Community

Outcomes