Smarter Community Management: From Prompts to Practice

Inspired by Hilary Gridley’s Making AI a Habit, I’ve started using AI tools like ChatGPT and Gemini to explore ideas on community management and work through different angels before putting them into practice. Like with any tool, AI works best when paired with critical thinking – much like trying on four shirts in a dressing room and walking out with the one that fits.

In each post, I’ll share which tool(s) I used, my preference, and the actual prompts that guided me. I’ll always refine the AI’s output so that it’s helpful and actionable.

Essentially, this series is my AI personal toolkit for community management. So let’s get started!

Stakeholders vs. Partners: Key Differences for Community Managers

It’s important to understand the difference between a stakeholder and a partner since each role has their own level of involvement, commitment, and engagement. This allows you to develop your relationships with each role appropriately through appropriate communication, decision-making, and strategic alignment.

Internal stakeholders are teams who are interested in your community because it affects them in some way. They want to know about your community’s outcomes and may give resources or share their opinions, but they don’t get involved in the day-to-day activities. These are teams you keep informed about your community metrics and other outcomes. Example: Sales

Internal partners are teams that are just as interested in your community as stakeholders, but these teams roll up their sleeves and work closely with you on shared objectives. These are teams that you directly collaborate with on projects and goals. Example: Product and Support

Knowing the difference between an internal stakeholder and partner gives you the ability to manage your expectations and build stronger relationships by understanding the level of

  • Communication and engagement – Partners will be more collaborative and involved while stakeholders will prefer a high-level summary.
  • Resource management – Partners are involved with your projects with shared goals which requires more resources while maintaining the level of support from stakeholders who aren’t as directly involved requires less.
  • Strategic planning – Partners will be more influential when you’re setting goals and project initiatives while stakeholders have a more indirect influence

The difference between a good and great community manager is recognizing the nuances between internal stakeholders and partners. Knowing how to approach each group using the right communication strategies, along with resource expectations and weaving them into your strategic plans not only builds stronger relationships, but also significantly contributes to your community’s success.


Try This

  1. Label each team in your organization as a stakeholder or partner.
  2. Identify your level of communication, engagement, and their involvement.
    • How often will you give updates?
    • What will you share with them? If metrics, which would be most beneficial and why?
    • What is their level of involvement and expectations?
  3. What are their goals and initiatives, how do they align with yours and vice versa.

Renewing my Thought Follower Pledge in 2024

In January 2022, I shared that I am a proud thought follower and had planned to summarize podcasts and articles to share them here. Little did I know that 2 months later, tragedy would strike and I’d be laying my fiancé, our hopes, and planned future together to rest. With the help of friends, family, Zuora co-workers, and other communities who rallied around me, I’m back!

The industry has changed since 2022 and so, my thought followership tales will focus on these 3 topics:

  1. ChatGPT Tips – getting the most from generative AI chatbots
  2. Community Management Math – allow me to dispel the mystique
  3. Communities Across the Lifespan – helping all ages find their tribe

And as with most tales there are side stories so you may see some other topics as well.

Let’s continue!

Thought follower…and proud of it!

So many people want to be thought leaders – but what’s the point of leading if no one is following?

There are so many influential and brilliant community managers creating amazing content – books, articles, webinars, videos – that I’d like to start highlighting them as a thought follower. Author Todd Henry said in his article Forget Thought Leaders – We Need more “Thought Followers”

[Thought Followers]…are people who immerse themselves in the brilliant, challenging thoughts of others, commune with great minds, and then follow their own thoughts wherever they might lead. They have a disciplined Study Plan that challenges them to think about important problems and allows them to stretch their thoughts and explore uncomfortable places.

They aren’t afraid to humbly submit to the great insights of others and consider their implications to their own work. They are fiercely curious. They love process. They set aside time to savor great writing. They understand that brilliant ideas are excavated and assembled, not self-generated.

And this is what I plan to do starting in 2022 whether it’s listening to a podcast, reading a book or article, or watching a webinar or conference session. I’ll summarize each with my top 3 takeaways followed by my action items. I hope to follow my summary posts with my results as well!

So here’s to the Thought Followers! Let’s begin…

Advice for a New Community Manager

Two people having coffee

My winning submission from Khoros’ Community Manager Appreciation Day 2020 Contest.

Most community managers are on a team of one (as I am) so my advice focuses around that – especially when Community is new to one’s organization:

  1. Don’t overwhelm yourself with tasks. Select up to 3 initiatives to focus on for that particular quarter or fiscal year. Is it growth? engagement? Your calendar and any task manager software are your friends!
  2. Become familiar with your new organization and how it fits with your community. Go to your intranet, make a list of all of the departments and create bullet points on how they could contribute and benefit your community – tactically and strategically. This list will help you promote community internally and find allies that will help make your job easier.
  3. Have an open-door policy to talk about Community. Find active community members (internal and external) and call them up to learn how they use community and what could be better. This information provides incredible insight into user behavior
  4. Welcome new internal team members, introduce yourself and the Community’s value to their department. Newly hired folks need a buddy…so why not have it be you? Not only will you be their lifeline within the company, you can show them the value of Community. Similarly, newly hired folks want to be recognized and seen by their managers. Share how the Community would benefit their careers within your org (i.e. Give them something they can share on LinkedIn!)
  5. Always think strategically. Connect with internal team members who are influential in making decisions and would encourage their department to participate more in the community. Take them to coffee or lunch to understand their current work struggles and leverage that information to demonstrate how your community will help make their jobs easier.
  6. (Last but not least) Take that vacation…and enjoy it! Don’t feel guilty if you need to take a day off or a vacation. Come up with a process where you can casually check emails (or train a back-up) while you’re on vacation. You will be more influential and valuable when you’re refreshed and well-rested.

SDX Here I Come!

SDX in Portland Banner

I’ve been asked to give a workshop at the upcoming Support Driven Expo (SDX) in Portland this July 21-22!

My topic will be “5 Tips to Increase Employee Participation in Your Community” and I’m pretty excited to share some of my ideas and how I’ve improved participation within Zuora.

Takeaway
Tools and strategies that will help thaw employee inactivity and turn your community into one that is vibrant and have users wanting more.

Description
You know the saying “Build it. They will they come.” How true is this for online support communities where internal teams hold a wealth of product knowledge, but they aren’t sharing it with your community users? If your users aren’t getting the answers they need from the Community, your Community will become a ghost town.

In this interactive workshop, Zuora Community Manager Lana Lee will share strategies that motivated Zuora employees how to leverage the Community for their teams while, at the same time, helping customers with their questions.

My First Podcast on Community Signal

Iphone on Sofa

Community Signal LogoI’ve always enjoyed listening to other people talk at conferences about community management and never thought that I’d be asked to actually be on a podcast…but then it happened!

Out of the blue, I received a Twitter DM from Patrick O’Keefe from Community Signal which is a bi-weekly podcast for community professionals.

I’ve heard of this podcast before and always thought that the guests were people who had done amazing things so I was definitely surprised when Patrick asked me to be a guest on his show.  I was super excited about it, but also nervous because I didn’t think I had anything interesting to say.

To gauge whether or not he had a show, Patrick sent me a questionnaire and I answered it as detailed as I could because I wanted to be picked.  He wrote back saying “We definitely have a show!” and we setup a time to chat.

Without giving away too much of my episode, we talked how I discovered Community Management and titled my show From Civil Engineer to Community Manager.

So without further ado, here’s my podcast episode.  I hope you like it!

 

 

FAQs: Your Community's Best Friend

There’s nothing more annoying than fielding the same question…over and over again.  When I was going through my Lithium training, the instructor said that the rule of thumb was that for every person who has a question, you can assume that 25 people have that same question.

That’s where FAQs in your Community help – especially with deflected tickets.  When I was a Meetup forum moderator, I kept a cheat sheet of FAQs so that I could copy and paste the answer.

For the Zuora Community, nearly all of the questions are technical; customers usually search Google for their answer, which is why it’s crucial to have FAQs for error messages, security issues, “how tos” and so forth.

Customer Solutions Articles (CSAs)

Since we’re on Lithium, we have our support agents write what we call “Customer Solutions Articles” based on questions asked in their Zendesk tickets.  They post the question as the original post, followed by the reply in the subsequent post.  Then they mark the reply as an accepted solution.  Right now, we don’t showcase our accepted solutions (I know, I know….I’ve logged that request with our IT team), but when we do, those will show up.

CSA Tracking

Each CSA is given a “Customer Solutions Article” label so that I can track the number of label views.

Quality Controlled CSAs

In our first year, we used to have a Q&A process, but that took forever to get something posted so the community would get, at most 5 CSAs posted a month, if the agents didn’t have many fires to put out.  The number of views were around 1000 page views/month and the “Customer Solutions Article” label was consistently #1 – not bad for a brand new community!

The problem with this process was that there was a lot of back and forth – checking, editing, rechecking – such that the CSA queue was getting longer and longer and it wasn’t a priority.

Enter…the Kraken!

At the beginning of our 2nd year, the CSA queue got to ~60 pending articles waiting to be quality-checked.  So we said “Screw it…let’s just get the articles out there for our customers!” There were some folks who were hesitant on letting incorrect information float around the Community, but my opinion was that it’ll create a great discussion; any engagement is good engagement to a Community Manager, right? 🙂

So, we released the Kraken…

Liam Neeson Release the Kraken

Did all hell break loose?  No!  Our CSA views skyrocketed to around 4000 views/month!

One can easily assume that a percentage of those views resulted in a deflected ticket as many customers didn’t ask additional questions in the CSAs.  We also had very few corrections.

Wait…it gets better!

Requiring CSAs Upon Ticket Closure Results in Metrics of Gold!

If agents posting CSAs at-will increased the article views 4x as much, we should require agents to write a CSA (if it makes sense) before they’re allowed to close a Zendesk ticket.  Sounds evil, right?

We followed this process for a few months (no more than 2 quarters) and the Community was overflowing with CSAs.  Imagine how many tickets an agent sees a week and translate those tickets into CSAs.  It was awesome and the metrics supported it.

One month prior to this requirement, CSA labels were seeing an average of 4000 page views/month. The month after, CSAs skyrocketed to 7000 page views/month.

While these numbers are impressive, we found that agents were getting burnt out and a little sloppy writing their CSAs, so we went back to posting articles at-will.  Still, our CSA metrics hang out around the upper 7000 page views/month.

FAQs are Your Best Friend

It takes time to build up a FAQ, but the payoff is well worth the effort.  Our agents were reporting that customers were asking fewer lower-hanging fruit type of questions, which made their job more interesting and customers were getting their questions answered.

Start out with 10 FAQs and built it up from there.  Remember that browsers will crawl your site when people Google their questions so keep SEO in mind.