June 2022 Newsletter

Our New Quarterly Newsletter Is Here!

Welcome to the AnswerHub quarterly newsletter! We are excited to send out this collection of articles, as our goal is to keep you informed about what we are doing in the market, what value our customers are getting from the use of the AnswerHub platform, and share best practices of building robust developer experiences and communities. Our mission at AnswerHub is to connect the world’s developer and technical teams one business at a time. We hope you enjoy this update, and we look forward to your feedback.

This quarter, we will overview the following:

  • Our new Slack Microsoft Teams two-way messaging integration
  • 9 Essential Questions to Ask When Planning a New Online Developer Community
  • The launch of our new blog page on AnswerHub.com where we share best practices and thought leadership
  • Our recent team gathering in North Carolina
  • Is “The Great Resignation” Turning Into “The Great Regret Nation”?

Thank you for your ongoing support and interest in AnswerHub! Please feel free to share this newsletter with anyone you think would find it interesting or useful!

The AnswerHub Team

9 Essential Questions to Ask When Planning a New Online Developer Community

A new online developer community should be planned and configured so that the structure, features, and operational practices align with its intended purpose and value. Whether planning a community from the start or optimizing an existing community, planning sets the foundation for success by defining the problems to be solved through the community, with consideration for the needs and preferences of the community members, as well as the objectives and measures of success for the business stakeholder; therefore configuring AnswerHub for success.

The first steps in planning the community are to collect all of the background information on the needs of your organization and the users of your community, and to gain a thorough understanding of the current culture and dynamic of the knowledge ecosystem to see how the community could best be implemented. To aid in this process, we recommend that you answer the following questions to help identify how users find answers today, who the producers and consumers are, and discover the baseline effort required to get an answer. Additionally, you will gain an understanding of how the community may wish to contribute, and the level of motivation to do so. The responses you receive can inform feature enablement, engagement tactics, promotion and communication plans, and potential early adopters.

1) When you have a technical question specific to your company related projects, what resources or approach do you most often use to find a solution?

  • Search internal knowledgebase or documentation
  • Email colleagues who you believe may know the answer
  • Ask your question on a chat channel or message an individual
  • Search the internet for similar scenarios
  • Contact your manager, scrum master, or project leader

2) Which is more often the case in situations where you have a technical quest?

  • You find or are guided to information that already exists
  • You ask your question and receive an answer and new documentation is created as a result

3) On average, how long does it take for you to find the solution to your question?

  • Not long – usually less than 5 mins
  • A little while – 30 mins to an hour
  • Longer than I would like – more than an hour, but less than 4 hours
  • Too long – more than 4 hours

4) How often do colleagues seek help from you directly via calls, emails, chats, or in-person visits?

  • Often – at least once a day
  • Sometimes – perhaps once a week
  • Not often – perhaps once a month

5) How often are you asked repeat questions?

  • All the time – at least once a day
  • Frequently – one or more times a week
  • Sometimes – several times a month
  • Seldom – I can’t recall a recent time

6) Would it be helpful if you had a place to publish or share your discoveries or to document processes to help the team?

  • Extremely – I don’t have a way to publish articles, but have a lot I could share.
  • Somewhat – There is a formal knowledgebase, but I’m not on the team that publishes articles.
  • Perhaps – I’d be willing to try, but am unsure exactly what I would publish.
  • Maybe – I really don’t have time for that.

7) Would it be helpful if you had a place to suggest ideas for improvement and to see, comment, and vote on the ideas of others?

  • Yes! Many of us have ideas that we share with our managers, but would like to get broader reactions.
  • Maybe – I have some ideas from time to time and would be willing to try.
  • Uncertain – We’ve tried something like this in the past, but it fizzled out.
  • Probably not – I’m very busy and am not sure I’d have the time.

8) What would increase your participation in an internal collaboration community?

  • Confidence that I would receive a useful answer quickly
  • If I could save time by avoiding repeat questions
  • If I could see who might have expertise relevant to my question
  • If I received recognition from colleagues (and even my manager) for the time I spent helping others
  • If my manager supported this as a core part of my job and not just something extra they want me to do
  • If I could have some ownership and control over the areas where I would be participating

9) Assuming a collaborative community was established that provided these opportunities, would you plan to actively participate and encourage others to join?

  • Yes, I would absolutely support this and would want to be involved in helping build it from the start!
  • Yes, I would participate and encourage others – this seems like something that could help us.
  • I would give it a try and if I found it helpful, I would probably recommend it to others.
  • I might try it and would like to hear from others if they find it valuable.
  • I’m not sure, I’d probably see how it goes and might try later.

For more tips and tricks on how to best build engagement for your community, please contact us!

Announcing New Microsoft Teams and Slack Two-Way Integration
Get More Out of the Tools You Already Have!

It is very likely that your development and technical teams are using Microsoft Teams or Slack every day – Why not make it easier to find answers to questions that are asked across the enterprise?

  • Reduce distractions, repeated questions, and corporate drag
  • Improve productivity and eliminate tool switching
  • Use AnswerHub to find answers more efficiently to questions posted
  • Get notified instantly when new questions & answers are available

Improve your experience with AnswerHub’s NEW Two-Way Integration

Watch the Microsoft Teams Integration Video
View or Download the Flyer
Watch the Slack Integration Video
View or Download the Flyer

Team Gathering in North Carolina

Last month for our Quarterly Kickoff, all our remote employees came into town from California and Chicago to Argentina, Uruguay and Portugal. We had a lot of great work sessions but also had a lot of fun with team dinners and even a Durham. Bulls game. It was such a fun week seeing everyone in person!

While the entire team was in town, we had the honor of working with an amazing organization Rise Against Hunger who puts together and sends meals to people in need. Recently they have sent meals to Haiti and currently to Ukraine. The AnswerHub team created and packaged 2,000 meals one afternoon during our quarterly kickoff week!

We Invite You to Visit Our Newly Redesigned Blog Page

AnswerHub prides itself on continually providing valuable information so you can get the most out of your community. Our recently redesigned blog page makes it easier than ever to find useful knowledge to create a community that meets your needs. What topics would you like to see addressed there? Contact us and let us know!

Is “The Great Resignation” Turning Into “The Great Regret Nation”?

“The Great Resignation” saw countless American workers leave their jobs, but more and more are regretting that decision. Alternatively, some who accepted employment had “buyer’s remorse” and jumped ship, as evidenced by the responses of about 72% of Millennial and Generation Z interviewees in a recent survey conducted by The Muse. Describing itself as “the go-to destination for the next gen workforce to research companies and careers”, The Muse boasts over 75 million yearly users, including both workers and organizations (which “use [the] platform to attract and hire talent by providing an authentic look at company culture, workplace, and values through the stories of their employees”).

The respondents shared that they were taken aback with the realization that their new positions – or the companies they went to work for – were “different” from what was communicated and discussed during pre-employment interviews.

CEO of The Muse, Kathryn Minshew, calls this “shift shock”, stating to FOX Business, “They’ll join a new company thinking it’s their dream job and then there’s a reality check.” She elaborated on the issue, explaining that sometimes job applicants simply don’t ask about important new-job considerations during the hiring process, and in other cases, recruiters or those conducting the interviews misrepresent the job in question or oversell the organization because they desperately need workers. She emphasized that, recently, job interviews have most often been over Zoom, and without an appointment at the company’s actual physical office, it is incredibly difficult for interviewees to evaluate the environment where they would potentially be working. Clearly, not getting what seems to be ‘advertised’ has moved from Instagram product ads into the workplace – and that is certainly contributing to more of the newly employed to say, “I’m gone!” rather than “I’m going to give it the ol’ college try!”.

Kathryn Minshew realizes the employment landscape has made a major shift, sharing, “It used to be that if you started a new job and didn’t like it, you needed to stay for one or two years to avoid a black mark on your resume, but we’ve seen this really interesting shift in perceptions.” 80% of the younger generation workers surveyed seem to agree, replying that leaving a job within 6 months of the start date is fine if the position is not what it was made out to be during the hiring process. 20% would resign within just 4 weeks if the job didn’t pan out the way they expected, while 41% would stick around 2-6 months. Almost half (48%) would jump ship and try for re-employment at a previous job.

“The Great Resignation” is a term brought about when millions of workers in the United States left their employment during the height of the COVID-19 pandemic. The new attitude of leaving a job in such an historically short time period could bring about a 2nd wave of the phenomenon. To avoid this, employers should be more forthright in what a job entails, as well as the corporate culture, as it will assist in finding the perfect fit, and keeping those workers on staff longer. Also, the workforce of younger generations has different values than those of the past, so meeting those will be useful in retaining employees. On this topic, Minshew opined, “People are much more likely to accept the good and the bad and to show up as engaged and productive if they have entered the situation with their eyes wide open.” When searching for developers to join your staff, you may want to give hefty consideration to new attitudes prevalent in the available workforce.