
Sign up to save your podcasts
Or
After hundreds of interviews with tech innovators I have concluded they are all trying to accomplish the same thing: tell how they can help get the word out that they may have a slice of the solution for federal information technology. One of the best ways to “get the word out” is through a community of interest.
During the interview today, Derek Weeks details his success in forming a community around Development Operations, or DevOps. In fact, he has published a book detailing that wildly successful endeavor: Unfair Mindshare LINK
One of the keys is to listen to problems and gaining a deeper understanding of the challenges in remedying complex tech concerns in the federal government. The community is called DevOpsDay https://devopsdays.org/
Derek and a colleague started with an idea to have a couple of hundred developers have access to each other in an informal meeting. It became so popular that it has blossomed into a group of 30,000.
Some key takeaways
·Start with a user-lead experience. There is no use in guessing what topics will be of interest to the community. Reach out personally to dig deep into current issues and concerns.
·Give without expectation. User generated content is closest to the problems than anything from the marketing department. Content from sponsors as well as from members should be shared willingly.
·1,000-hour rule. There is a commitment of at least 1,000 hours a year to accomplish a successful community. This is not a “set it and forget it” initiative. Careful nurturing and growth of the community needs a real effort.
·Localize community relationships. We have seen meetups all over the world. One way to get the word out is to contact like-minded professionals. A problem in Sao Paulo, Brazil could be the exact concern in Kigali, Rwanda.
·Sustaining the relationship is as crucial as beginning it. Derek gives specific tips on maintaining the relationship over the long haul.
The success of community building tells us more about software developers than anything else. Aggressive pitches will be discounted. Generic email blasts are outdated.
Digital natives appreciate authentic experiences. This means that a community leader does not look at a member of a community as a “prospect” but as a “person.”
= = =
Want to leverage you next podcast appearance? www.podscorecard.com
Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/
Want to listen to other episodes? www.Federaltechpodcast.com
5
55 ratings
After hundreds of interviews with tech innovators I have concluded they are all trying to accomplish the same thing: tell how they can help get the word out that they may have a slice of the solution for federal information technology. One of the best ways to “get the word out” is through a community of interest.
During the interview today, Derek Weeks details his success in forming a community around Development Operations, or DevOps. In fact, he has published a book detailing that wildly successful endeavor: Unfair Mindshare LINK
One of the keys is to listen to problems and gaining a deeper understanding of the challenges in remedying complex tech concerns in the federal government. The community is called DevOpsDay https://devopsdays.org/
Derek and a colleague started with an idea to have a couple of hundred developers have access to each other in an informal meeting. It became so popular that it has blossomed into a group of 30,000.
Some key takeaways
·Start with a user-lead experience. There is no use in guessing what topics will be of interest to the community. Reach out personally to dig deep into current issues and concerns.
·Give without expectation. User generated content is closest to the problems than anything from the marketing department. Content from sponsors as well as from members should be shared willingly.
·1,000-hour rule. There is a commitment of at least 1,000 hours a year to accomplish a successful community. This is not a “set it and forget it” initiative. Careful nurturing and growth of the community needs a real effort.
·Localize community relationships. We have seen meetups all over the world. One way to get the word out is to contact like-minded professionals. A problem in Sao Paulo, Brazil could be the exact concern in Kigali, Rwanda.
·Sustaining the relationship is as crucial as beginning it. Derek gives specific tips on maintaining the relationship over the long haul.
The success of community building tells us more about software developers than anything else. Aggressive pitches will be discounted. Generic email blasts are outdated.
Digital natives appreciate authentic experiences. This means that a community leader does not look at a member of a community as a “prospect” but as a “person.”
= = =
Want to leverage you next podcast appearance? www.podscorecard.com
Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/
Want to listen to other episodes? www.Federaltechpodcast.com
1,462 Listeners
7 Listeners
7 Listeners