<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tiffany Oda on Medium]]></title>
        <description><![CDATA[Stories by Tiffany Oda on Medium]]></description>
        <link>https://medium.com/@tiffeoda?source=rss-24faf6bf40d3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*65lHNY1xZhxxhQI5_-gmIQ.jpeg</url>
            <title>Stories by Tiffany Oda on Medium</title>
            <link>https://medium.com/@tiffeoda?source=rss-24faf6bf40d3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:55:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tiffeoda/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Power Pair: Community & Customer Education]]></title>
            <link>https://medium.com/@tiffeoda/the-power-pair-community-customer-education-d131868dbad9?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d131868dbad9</guid>
            <category><![CDATA[customer-education]]></category>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[community-management]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Tue, 23 Jun 2026 14:56:01 GMT</pubDate>
            <atom:updated>2026-06-23T14:56:01.071Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ph6lYYNIru-cP6-JeFxQw.png" /></figure><p>I recently spoke at the Gainsight Pulse conference about the power pair dynamics of Community &amp; Customer Education working together. Co-presenting with my colleague, Head of Customer Education <a href="https://www.linkedin.com/in/jjanikis/">JJ Janikis</a>, we shared some examples of how we’ve built true collaboration between our teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z8c-88SCr_LEOw5YDZWaMg.jpeg" /><figcaption>JJ and I onstage talking about the power pair of community &amp; customer education.</figcaption></figure><h3>A squiggly org chart</h3><p>Before diving into some of the examples and how we collaborate, we shared a bit about how our two teams have had a squiggly org chart history. I’ve jokingly called it the “It’s complicated” Facebook relationship status. Over the last four years, Community and Customer Education have been in different orgs, same org different team, same team (the best era), back to same org different team. These circumstances were out of our direct control and were determine by various org restructuring, but throughout the squiggliness, JJ and I maintained our working cadence and supported our teams to continue open channels of communication, transparency and visibility into shared initiatives, and we never dropped out of rhythm of working together.</p><h3>5 Examples of the power pair</h3><h4>1. Learning → Advocacy</h4><p>We recognize that without learning the product, advocacy is simply not possible. I mean, you can’t be a fan of something you don’t know, right? As such, we’ve made sure to embed the Asana Academy as part of the process to become an Asana Ambassador. As a step to become an Ambassador, everyone has to complete two courses in the Academy: the Asana Foundations Skill Badge and an Asana Ambassador Orientation. This not only validates their product knowledge, but amplifies their credibility as an Ambassador and sets expectations of what it means to be in the program.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_24Gb2_YjyOhUFq64-F3dg.png" /><figcaption>In order to become an Asana Ambassador, everyone has to complete these courses in the Asana Academy.</figcaption></figure><h4>2. Certification Week</h4><p>Certification Week was an initiative in the community where Ambassadors shared their success stories and how being certified opened opportunities for them. Throughout the week, they shared anecdotes of immediately using learnings from courses at their companies, of getting interviews because they were Asana certified, and even how they were crowned as the “Asana Queen” by coworkers, tiara and all. This initiative not only drove program awareness and certification registrations, but also brought fun and personality to Asana through our certifications and skill badges. Lastly, community members who contributed to Certification Week received an exclusive badge for their Forum profiles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UXzJGvWcp6SySpWIDklUuw.png" /><figcaption>The Asana Queen sharing her story of getting certified, her fandom, and getting her peers to get certified.</figcaption></figure><h4>3. Communities of Practice</h4><p>Many of the Asana Ambassadors are the internal champions at their companies- the ones who hold office hours, who are the SMEs people turn to when they need help, and the ones who hold trainings for their companies. They’re the ones who are spearheading adoption across their organizations and building Communities of Practice. We recognized that education was a big piece of this, and created some ways to better bring education to the Ambassadors to bring to their internal communities.</p><ul><li>Forum + Live Trainings: We created dedicated forum threads for each training session held by the Education Team and invited attendees to join to continue the connection and discussion after the trainings were over. (Fun fact, this is actually how the Salesforce Success Community, now more famously known as the Trailblazer Community, began.)</li><li>Workshop Training Materials: We took our Asana on Tour content, which are 2-day long hands-on workshops, and packaged it in a way an Ambassador could take it and use it for their internal trainings. The content has everything from the decks, the talk tracks, and the workshop materials, making it super easy for them to take and use on their own. Adding to that, we give Ambassadors access to a swag site where they can purchase swag at-cost to handout goodies at their meetups and trainings.</li><li>Community of Practice Guide: Of course, we also recognized that just because they’re an Asana super user, it doesn’t mean they know how to build a community. As such, collaborated with a handful of Ambassadors who <em>had</em> built successful CoP at their organizations, and co-created a comprehensive Community of Practice Guide. It has helpful information on how to start a CoP, how to maintain it, and anecdotes and tips from people who have done it successfully. (This was personally a really fun project for me to work on with the Ambassadors, and I’m really proud of what we made.)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*wORt5U-wmR6BnHu5dRoKFA.png" /><figcaption>JJ and I sharing the stage with Asana Ambassadors talking about community and certifications at Work Innovation Summit.</figcaption></figure><h4>4. Credential Development</h4><p>We work together with the community on development of new skill badges and certifications offered in the Asana Academy. Asana Ambassadors have the opportunity to help build the content with us, get exclusive invitations to beta test and pilot new programs, and get early access. They absolutely love sharing their new credentials on LinkedIn before it launches to the public.</p><h4>5. Events</h4><p>As a last example, we work together on many events and often come together as one team for event activations. At Asana’s tentpole conference, Work Innovation Summit, together we’ve:</p><ul><li>Shared the stage with certified Ambassadors to talk about the importance of community and how getting certified has helped amplify their careers.</li><li>Owned a booth on the expo floor to talk about community and certification programs. We’d also have special swag to giveaway for Ambassadors and certified individuals who’d come say hi at our booth.</li><li>Staff the booth as one team. Team members on the Education Team were fluent in being able to talk about the community, and the Community Team was fluent in being able to talk about the certification program. One team, one dream.</li></ul><p>We also partner closely on Asana on Tours, which are the hands-on workshops that I mentioned above. The Community Team will run day-of event management and overall event support, and we’ll do the opening and closing talk track for the sessions, and the Education Team facilitates the sessions. We’ve got this process nailed down to perfection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*gQwssS4XUkkdfaJhDxKkwA.png" /><figcaption>Our shared booth at Work Innovation Summit.</figcaption></figure><h3>Conclusion</h3><p>Even though our teams have gone through various iterations of proximity on the org chart, our relationship has held steady. Through making sure we meet regularly, empowering our teams to collaborate, doing our annual planning together, and keeping communication lines open with proactive conversations and transparency, we’re able to deliver a more connected experience for our customers and amplify both the community and the education programs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*UbX4wy1KQpMrPpzrIzXMzg.jpeg" /><figcaption>Special shoutout to JJ for being such a great partner and stage buddy. We’ve now presented three times together. To many more!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d131868dbad9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Community Hot Takes! Community Council (Part 2)]]></title>
            <link>https://medium.com/@tiffeoda/6-community-hot-takes-community-council-part-2-d96ab34929b2?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d96ab34929b2</guid>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[community-manager]]></category>
            <category><![CDATA[community-engagement]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 17:11:00 GMT</pubDate>
            <atom:updated>2026-06-01T17:11:00.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*A7lDwhw_n0j6pEnvobKSmQ.jpeg" /><figcaption>The Orangerie, where our hot takes sessions took place.</figcaption></figure><p>If Part 1 of my Community Council recap was all about setting the stage, finding my footing, and soaking in the magic of being in a room full of people who <em>just get community</em>, Part 2 is where we get into the weeds a bit more.</p><p>During our time together, six of us stepped up to deliver quick-fire “hot takes”. Nothing super formal, but just a quick and spicy take on something community related. Slides were optional, but we all decided to make some. I attribute this to our community manager nature of being organized. 😆</p><p>Here is a glimpse into what my brilliant peers brought to the table (plus a little snippet of my own soapbox moment).</p><h3>1. The danger of the “one-size-fits-all” newsletter</h3><p><a href="https://www.linkedin.com/in/jlarsenparis/">Jennifer Larsen</a>, Senior Community Content Manager at Malt, talked us through a cautionary tale that should be required reading for anyone managing a global community. Her team ran an experiment with their community newsletter, consolidating the various languages spoken across the Benelux region into a single, unified version. The result? A year-long, agonizing downward slide in both click-through and open rates.</p><p><em>The takeaway:</em> Localization isn’t a nice-to-have; it’s a must-have. If you aren’t recognizing and tailoring content to the specific subsections and regional nuances of your community, they <em>will</em> tune you out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*p5rURck7zX2EHg0OlWvNMw.jpeg" /><figcaption>Jen and I bundled up ready for the bonfire and meteor shower at the chateau.</figcaption></figure><h3>2. Conversation design principles</h3><p><a href="https://www.linkedin.com/in/kaylauevans/">Kayla Uleah Evans</a>, Founder at Hauswarm, turned us all into conversation architects. She broke down how design affordances — literally how a space is built, whether that’s the physical orientation of round vs. rectangular tables or the structure of digital channels — dictate how people interact. She mapped out the three types of gatherings (exchanging, sustaining, and changing) and challenged us to think about the four types of change we can spark: affective, epistemic, cognitive, and power. Check out her <a href="https://hauswarm.substack.com/p/making-the-room-for-conversations?r=1qgdv6">Substack post</a> for more details.</p><p><em>The takeaway: </em>Communication is dictated by environment. To change the nature of the conversation, you have to intentionally change the design of the space (digital or physical) where it happens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ha0q7jC6TOzsdnOTnpB-kw.jpeg" /><figcaption>Kayla not only is hilarious and has a huge personality, but she’s finishing up her PhD in Human Centered Computing while also running her own business, Hauswarm.</figcaption></figure><h3>3. The art of multiplying yourself</h3><p><a href="https://www.linkedin.com/in/alla-zhdan/">Alla Zhdan</a>, Internal Community Lead at Svitla Systems, presented on how as community managers, we are famously chronically online and perpetually stretched thin. Alla’s talk was a masterclass in how to clone yourself (metaphorically, unfortunately) through community leaders. She reminded us that true community leaders are responsible, eager to validate ideas, results-driven, local, and incredibly cooperative. By empowering them to co-organize activities and act as your local eyes and ears, you don’t just scale your program — you give ownership back to the community.</p><p><em>The takeaway:</em> Stop trying to do it all alone. Scale your impact by turning passionate members into co-creators who bring local context and bridge the gap to your stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*qNAryA018bL4OdJxwStLdg.jpeg" /><figcaption>One thing I loved about Alla’s presentation, aside from the content itself, is she made her photos and backgrounds in the slides from the chateau and the grounds itself!</figcaption></figure><h3>4. Climbing “Cringe Mountain”</h3><p><a href="https://www.linkedin.com/in/kredcarroll/">Katie Carroll</a>, Director, Editorial &amp; Product Strategy at LinkedIn, talked about the terrifying but necessary journey of climbing “Cringe Mountain” — putting yourself out there and being real, earnest, and vulnerable in public to build your personal brand and establish your presence on LinkedIn. She broke down what type of content resonates: sharing your thinking processes (the messy “how,” not just the shiny “ta-da!”), unique POVs, strong hooks, and actual opinions.</p><p><em>The takeaway:</em> Authenticity requires a little bravery. To stand out and build a personal brand, you have to move past the fear of being perceived, deliver real value, and actively join the dialogue through comments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*TCZyHN0rjMUfKN7hRrFumQ.jpeg" /><figcaption>Katie captured the phrase perfectly, because I certainly cringe (or just close the tab) whenever I think about posting on LinkedIn, but her talk really motivated me to try and be more active, even if it’s just commenting on posts (which I learned is very important!).</figcaption></figure><h3>5. Expert webinars are out. Dirty kitchens are in.</h3><p><a href="https://www.linkedin.com/in/anamariadorgo/">Anamaria Dorgo</a>, Founder of L&amp;D Shakers and L&amp;D Manager, Communities &amp; Social Learning at Adyen, shared a concept I absolutely love: the value of showing the “dirty kitchen.” She noted that learning does not equal education. Glossy, over-rehearsed, expert-led webinars are losing their luster, and what people actually want is the unpolished, raw, messy middle. They want to see the thinking process, the mistakes, and the reality of how things get built.</p><p><em>The takeaway:</em> Perfection is boring and creates a barrier to connection. Lean into unpolished, raw formats and show the behind-the-scenes mess — that’s where the real value and engagement live.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*rxpONO3ItgjwR-7Kx-Mmgw.jpeg" /><figcaption>Anamaria and Jen hanging out in front of the chateau. Anamaria has built an amazing community for people in Learning &amp; Development. If you work in L&amp;D, I’d highly recommend checking out the <a href="https://soft-talos-bf8.notion.site/Welcome-to-L-D-Shakers-23972fa0a18f419a9abe1bd59cb174c0">L&amp;D Shakers</a> community.</figcaption></figure><h3>6. Wait. Don’t Automate.</h3><p>When it was my turn, I decided to bring it back to my roots in Community Operations. My hot take? A phrase I’ve been using for the last 8 or so years: <em>Wait. Don’t automate.</em> There is immense value in doing things manually for a bit before throwing automations at a problem. And now, in the AI era, I added a 2-element sanity check (Human Judgment Score &amp; Risk Score) to my framework to decide if a process should be automated, AI-assisted, or kept completely human.</p><p><em>The takeaway:</em> Don’t sacrifice trust for speed. Before rushing to automate or plug in AI, evaluate the relationship context and the potential blast radius if things go wrong — some things are meant to stay messy and human.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UEG7D8E2lTfILNFtZThuAQ.jpeg" /><figcaption>Our amazing onsite photographer, <a href="https://www.linkedin.com/in/sandra-s%C3%A1nchez-atienza/">Sandra Sánchez Atienza</a>, has captured maybe <em>the only photo of me smiling while presenting.</em></figcaption></figure><h3>Conclusion</h3><p>Looking back at the week, what made the Community Council so incredibly special was how entirely participant-centric it was. Instead of sitting through endless, passive slide decks, our days were anchored by thoughtfully crafted workshops and collaborative discussions. These “hot take” sessions provided a brilliantly low-barrier-to-entry way to share big ideas, which naturally spilled over into late-night convos and deep connections outside the formal agenda. It gave us the freedom to let our guards down, and dare I say, show each other our own “dirty kitchens.”</p><p>None of this magic would have been possible without the visionary behind it all, so I have to give a massive, heartfelt shoutout to <a href="https://www.linkedin.com/in/christina-hug/">Christina Hug</a> for bringing us together, curating this space, and orchestrating such an unforgettable experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*xe31QpHSBMkl1KJa4YYFaA.jpeg" /><figcaption>Christina taking the podium in the Orangerie. We were probably discussing the painting hidden behind the projector screen. What do you think the painting is of? (Find out what it is in Part 3).</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d96ab34929b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding intentionality, knowledge, and friendship at the Community Council (Part 1)]]></title>
            <link>https://medium.com/@tiffeoda/finding-intentionality-knowledge-and-friendship-at-the-community-council-part-1-ca2c9faa7208?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca2c9faa7208</guid>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[community-building]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Fri, 01 May 2026 21:27:43 GMT</pubDate>
            <atom:updated>2026-05-01T21:27:43.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z0RxjawXk4I--GCLYckhoA.jpeg" /></figure><p><em>This is part one of a three part series with takeaways and reflections from my time at </em><a href="https://www.communitycouncil.co/"><em>Community Council</em></a>, <em>a curated experience bringing together a group of 20 Founders and Executives of community-first businesses to exchange transformative ideas, tackle real challenges, and build meaningful relationships.</em></p><p><em>Part 1: The power of intentional experiences<br>Part 2: What I learned from my peers <br>Part 3: Community &amp; friendships</em></p><p>Before I jump into my takeaways from participating in the Community Council, I wanted to share some context on how it all started; it’s a pretty unique story, if you ask me.</p><p>It all started with an email titled, “<em>An Invitation to Normandy </em>🏰”. It was from someone who I didn’t know named Christina, inviting me to come to Normandy, France to stay in a chateau with 20 other senior leaders in community management. She said that she had been, “going down a rabbit hole of [my] Medium posts and have just been finding [herself] nodding along with every article,” and mentioned that she appreciated my step-by-step walkthroughs of complex community operations. After doing some internet stalking to make sure I wasn’t getting kidnapped, and excitedly sharing the email screenshot with all of my friends and family, I took the leap and replied, letting Christina know that I’m in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WvM22GOO0MpHVBxO" /></figure><p>I had no idea what to expect and was anxious about what was to come, but I was fully embracing this unique and unexpected opportunity. As the time to leave for France approached, I received a participant guide, full of helpful information about logistics, the chateau, and this note that gave me pause:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vOyZ_e6TtwsIL8ZfsSD_Bg.png" /><figcaption>Not being able to internet stalk the people I’d be living with for four days. 😬</figcaption></figure><p>The night before we were to meet at the bus stop that would be taking us to the chateau, Christina started a WhatsApp group with all the attendees. The messages of excitement started coming in. Rather than doing what I really wanted to do, which was to immediately stalk these people on LinkedIn, I followed due course and let the connection happen live.</p><p>We met at the bus stop and embarked for the 2.5 hour drive from Paris to Normandy. The bus was full of chatter; new acquaintances met, introductions, stories of how they found Community Council. Then we pulled up to the chateau, and saw a small group of people standing on the steps of the chateau welcoming us with waves and smiles. Council was in session.</p><p>I realize I could write an entire essay on my time at the chateau, but the truth is… I don’t want to share everything. A lot of the programming, the conversations, and general time there is something special that the group shared together, and I want to honor that and our time there, but there are some key observations, community learnings, and takeaways that I want to share with the world (or at least my humble number of followers) over the next few posts.</p><h3>The power of intentional experiences</h3><p>I was incredibly impressed by the number of thoughtful touches and considerations Christina put together for the Community Council. Just to list a few:</p><h4><strong>Personalized welcome baskets</strong></h4><p>Prior to attending, we filled out a participant survey. Amongst questions like dietary restrictions, topics we’re interested in discussing, etc., there were two questions I didn’t think much about at the time: our favorite pen ink color, and a small comfort item or snack that makes us feel at home. In the welcome basket? A pen with our favorite ink color, alongside two beautiful notebooks to write in. And I got a pin of my comfort snack item: spam musubi! There were also other thoughtful things like lavender oil to help with sleep since a lot of us traveled in internationally, cozy socks, some snacks, lotion, chapstick, a reusable water bottle (complete with soap and a sponge!), and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tUpYzaX-Zan5zdTopQuiWg.png" /><figcaption>Two simple questions in the participant survey that turned up later in unexpected ways.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/0*x9fDn0OMKkhPeK-g.jpg" /><figcaption>Such a thoughtful touch that made me “eeeeeeeee!” when I saw it.</figcaption></figure><h4><strong>Chateau ice breaker</strong></h4><p>Christina recognized that we not only needed to get to know one another, but get to know the space that we’d be calling home. With a preface of, “a lot of people can feel apprehensive about exploring the chateau and the grounds,” one of our first activities was a scavenger hunt to find places, get our bearings, while also getting to know one another while on our adventure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9eMRQtxlIZd8HN6OCfqjLA.png" /><figcaption>Our welcome scavenger hunt to get comfortable in the chateau and surrounding grounds.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GLNslcEhJe9kGuN97jTP6Q.png" /><figcaption>We may have taken a little unplanned detour through the forest on our chateau scavenger hunt. 📸 Photo credit: Sandra Sánchez Atienza</figcaption></figure><h4><strong>Matchmaking &amp; conversations</strong></h4><p>Every lunch, dinner, group conversation was intentionally designed. For example, lunches and dinners had assigned seating based on topics of interest, and we’d receive a few starter question prompts based off of what we had put in our participation survey. During our sessions, we’d also often get paired off, and groups were randomly assigned (often determined by a stack of cards). This ensured we’d have equal opportunities to meet with and work with everyone in the group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HJsOqK301NnNprXyMdqGvA.png" /><figcaption>📸 Photo credit: Sandra Sánchez Atienza</figcaption></figure><h4><strong>Evening reflections &amp; morning rituals</strong></h4><p>A pleasant surprise was at our doors at the end of each night. Each envelope contained an evening reflection, and another envelope to open in the morning with a morning ritual. It was a great way to end and start each day with a bit of pause and ponderance. Also, who doesn’t love a wax seal?!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cJ8jJlBprLKoOHo-YZ8SeA.png" /><figcaption>Special delivery, wax seal and all! 📸 Photo credit: Jen Larson</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mM7y5vwWV9LS82Hks9dgrw.png" /><figcaption>The evening reflections and morning ritual cards we’d receive daily.</figcaption></figure><ul><li><strong>Gratitude Corner: </strong>Right next to the stairs by the main foyer, there was a gratitude corner. Here we had to ability to write little notes of thanks that we could pass to anyone at the chateau throughout the week. They were also so kind as to provide us postcards in our welcome basket that we could use to write to loved ones, drop it in the outgoing mail basket, and they’d send out… to anywhere in the world. 🥹</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HH8VjCIG2jymCEn4Z_SoDQ.png" /><figcaption>Here is where we could write thank you cards to share with others throughout the week or send postcards to loved ones. 📸 Photo credit: Izzy Ahrbeck</figcaption></figure><p>There were so many other moments that made me feel so taken care of, moments of true surprise &amp; delight, and even feelings of childish whimsey and joy. Here are some others in shorter form, with a collage of photos at the end.</p><ul><li><strong>Culinary &amp; Dining: </strong>Chef Linda Sarris and Head of Operations Carmen Hernandez did a spectacular job keeping us fed and taken care of. From curated menus focusing on local ingredients to surprise chocolates and cocktails to special decorations on our lattes, their hospitality was incredibly thoughtful end-to-end.</li><li><strong>Mug personalization:</strong> Along with our reusable bottles/mugs, there was an adorable mug personalization station where we could customize our mugs with different charms and beads. It was a fun little arts and crafts section.</li><li><strong>Midnight snack &amp; sleep station:</strong> Every night on the table in the foyer, there would be midnight snacks and a basket full of sleep aids like melatonin, ear plugs, eye masks, and nasal trips. Just in case we needed it.</li><li><strong>Comfort cabinet: </strong>A collection of anything we’d need, from hair ties to personal hygiene products.</li><li><strong>Scavenger hunt:</strong> A scavenger hunt, with riddled clues and a surprise at the end. This one resulted in a lot of giggling and running like kids throughout the chateau.</li><li><strong>Yearbook letters:</strong> At the end of our stay, we had the option to write notes to the others. These were then put into envelopes and given to us as we departed, to be read at a later time. As an avid note writer, I absolutely loved the opportunity to do this for the people I had formed such strong bonds with over the week. And as the recipient, reading my notes left my cup filled, a tangible way of keeping these feelings and memories forever.</li><li><strong>Venue: </strong>Obviously, staying in a gorgeous chateau in Normandy, France is a gift in of itself, but there was intentionality behind it. Being in this environment made it easier for us to be present. The common areas welcomed conversations and comfort. The newness of staying at a venue we’ve never stayed at before primed us for the newness of the experience that was the Community Council. The beauty of the grounds opened our minds to sharing our experiences, our expertise, and our creativity with one another.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*it98158k7p5hPOTKAOtwDg.png" /></figure><h3>Conclusion</h3><p>I almost feel like I’m ‘spoiling’ these thoughtful moments of surprise for future Community Council participants, and I hope I’m not giving too much away. What I’m walking away with is a deep appreciation for the consideration and thoughtfulness Christina and her team brought to every detail. As a participant, I felt the intentionality behind every gesture; I felt truly valued and appreciated. Now, I want guests at my own future events to have that same experience. Attending the Community Council really opened my eyes to the importance of the participant experience. Whether I’m hosting a professional event for my company or a holiday party for friends and family, I know I’ll be looking for ways to recreate the feeling I had while at the chateau.</p><p>No Yoshi picture at the end of this one. The chateau is just way too beautiful to not share another photo of it. Thank you to Katie for letting me use her photo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*awhgzfSp1sIpAQvdIHBmEQ.png" /><figcaption>Missing frolicking in the fields already with my new community friends. 📸 Photo credit: Katie Carroll.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca2c9faa7208" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Made by the community, for the community]]></title>
            <link>https://medium.com/@tiffeoda/made-by-the-community-for-the-community-9b7fc5887a24?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b7fc5887a24</guid>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[community-engagement]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Thu, 02 Apr 2026 16:01:02 GMT</pubDate>
            <atom:updated>2026-04-02T16:01:02.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cZmO6t8Qr2Lm8J5Z7mbPzg.png" /></figure><p>The people in the Asana Ambassador program tend to fall into a few buckets:</p><ul><li>Team leads spearheading Asana adoption at their organizations</li><li>Admins who are responsible for setting up the Asana instance</li><li>People who generally love Asana and want to stay up to date on the product</li></ul><p>Across these groups, we see the same questions come up over and over again. “<em>How do I get my team to actually use Asana?</em>”, “<em>How do I train people without becoming full-time support?</em>”, “<em>How do I scale this beyond just me?</em>”</p><p>We had some solid resources — guides on rolling out Asana, training materials, and of course, resources in the community itself. However, there was a clear gap. We had no resources on how Ambassadors, the internal champions at their organizations, could create Communities of Practice to support their colleagues and improve adoption across their company.</p><p>So instead of creating something from scratch on my own, I decided to build a crowdsourced guide for creating and maintaining Communities of Practice. This resource would be exclusively available to Asana Ambassadors, made by Asana Ambassadors.</p><p>This article goes over my process and includes some highlights from the final product.</p><h3>Creating a crowdsourced guide: The process</h3><h4><strong>Step 1: Get the experts together</strong></h4><p>I put out a call for Ambassadors who had built successful CoPs at their organizations and invited them to join me for a virtual roundtable discussion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*YSOzmRKzmXMxOraBllfadw.png" /><figcaption>Putting a call out for Ambassadors who lead Communities of Practice at their organizations.</figcaption></figure><h4><strong>Step 2: Host the roundtable</strong></h4><p>I prepared a list of questions to jumpstart the conversation and shared them out with the group beforehand. This includes those who couldn’t make it live but wanted to participate async.</p><p>I also recorded the roundtable and used Zoom Companion so I’d be able to refer back to the information later. This would also allow me to focus on the conversation and be present, rather than having to divert my attention to taking notes.</p><h4><strong>Step 2a: Send appreciation</strong></h4><p>As a thank you, I sent participants a swag redemption link so they could grab something from our swag store.</p><p>I also got some appreciation back to me, which always reminds me of why I love working in community. One participant wrote me, “Thank you for organizing that! I really enjoyed learning from the others in the group.” Another wrote, “Really love all these opportunities to get involved as an Ambassador and community member.” And another wrote, “Thank you so much for the opportunity to support this project.” 😊</p><h4><strong>Step 3: Stitch it all together</strong></h4><p>I used AI to help synthesize the discussion, pulling out themes, organizing notes, and drafting the initial version of the guide. All in all, it probably saved me a few hours of listening to the meeting recording, sleuthing through the notes, and typing it all out. It also helped with formatting and making it look nice, of which I have no skills.</p><p>I now had a solid foundation, and it was time for validation with my community volunteers. I put the doc in a shareable Google Doc and invited everyone to join as Commenters, asking them to go through and make sure I captured everything. This wound up being a critical step — as a result of it, I got a few more screenshots, quotes, and additional input that we didn’t cover during the roundtable.</p><h4>Step 4: Publishing the guide, and more appreciation</h4><p>After reviewing and incorporating the comments from the group, I was ready to go. I added it to our Ambassador resources and created a mini promotion plan throughout the Ambassador spaces. I also made sure to credit the Ambassadors who were a part of the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*GXsUY1Xeg1zdaUcOE5Qn-Q.png" /></figure><p>Of course, then there was more appreciation! I wanted to give the Ambassadors an opportunity to brag about their participation in this. They were the true experts in bringing their experience building Communities of Practice, and even though the guide is exclusively available to Asana Ambassadors only, I wanted to give them a way to share their accomplishment on their social channels.</p><p>I made individual virtual thank you cards for them and sent it to them alongside some copy they could use to post on social. This way they also get to continue building their personal brand and establishing their expertise in a way that could benefit their careers as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*l8YySei-yzyar0qZDxUWrQ.png" /></figure><h3>The guide: a quick takeaway</h3><p>As much as I’d love to share the guide more publicly, this is a resource for Asana Ambassadors only. However, I can’t help but share a few tidbits:</p><ol><li>You aren’t the Asana police. Move from enforcing usage to creating a space where people <em>want</em> to learn.</li><li>Start small. Don’t try to launch something for your entire company off the bat. Start with one team, one workflow, one group of people who are already somewhat engaged.</li><li>Your job isn’t to have all the answers. Your job is to facilitate, connect, and make it easy for others to get involved.</li><li>Formats and programming can vary. Consider things like Slack/Teams channels, resource hubs, recurring office hours. The key is consistency.</li><li>Small content &gt; big trainings. People were generally more receptive to weekly tips, short feature callouts, quick examples from real teams, rather than big, polished training sessions.</li><li>If it’s not sustainable, it won’t work. You are building a CoP on top of your full-time job. Build systems, recruit co-leads, set realistic cadences, and find a rhythm that lasts.</li></ol><h3>Why I wrote about this: A conclusion</h3><p>This isn’t a typical post you’d find on The CommOps Gal, but I wanted to share it for a few reasons:</p><ul><li>This guide was a direct result of feedback that we heard from the community, as well as recognizing a gap in resources to help improve the value that folks would get from being a part of the community.</li><li>It was made by the community, for the community.</li><li>It was a great experience to collaborate and co-create directly with the community members.</li><li>Overall, I’m really proud of the final product and hope that it serves as a helpful resource for the Asana Ambassadors.</li><li>People are always looking for additional ways to use AI, and using AI to help synthesize the roundtable notes and put everything together truly saved me so much time.</li></ul><p>Have you ever co-created something with your community members? I’d love to hear about it! Feel free to share it in the comments below.</p><p>And as the normal thank you for reaching the end of this post, here is a recent photo of me and the Yoshster, enjoying a lovely SF day. It brings me joy because he decided to hang out in the weirdest half sit/stand pose. 😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W7zGWlmLkll5_jOEIjwECg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b7fc5887a24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI in Community: What we’re actually doing (and would like to do)]]></title>
            <link>https://medium.com/@tiffeoda/ai-in-community-what-were-actually-doing-and-would-like-to-do-ff2c0dd394ad?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff2c0dd394ad</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[community-operations]]></category>
            <category><![CDATA[community-management]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Mon, 09 Mar 2026 14:51:00 GMT</pubDate>
            <atom:updated>2026-03-09T14:51:00.603Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t3XGcyXECo2svsMz_UlUSw.png" /><figcaption>Made by AI.</figcaption></figure><p>Well, I didn’t make the one post a month goal. 😅 But you know what, that is okay. Hope everyone had a lovely February and March is treating you well so far. ❤️</p><p>I recently went to the Structure.Community Summit held by <a href="https://www.linkedin.com/in/billj/">Bill Johnston</a> here in San Francisco, bringing together ~30 senior community leaders to workshop ideas, hear from peers, and have in-depth discussions about community trends and topics. This summit’s focus was primarily on the use of AI in communities; it was thought provoking, and I walked away with some inspiration and additional ways to thoughtfully plug AI into our community processes. In this post, I’ll share a few examples of things that my team is doing with AI, as well as some things we aren’t doing yet that I’d love to try in the near future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AyWgYXfKa3tA76C9" /><figcaption>Lovely group photo at the Structure.Community Summit, courtesy of Bill Johnston and Alex Eckart.</figcaption></figure><p>Before I go into the content, I’d like to plug two books that my community friends have written. They were both at the summit and live and breathe community, and I think they have a lot of valuable insights to share with the world. I may or may not also be mentioned in the two books, which were firsts for me, and I’m excited to be a part of their works.</p><ul><li><a href="https://www.amazon.com/dp/B0FZ5M62MD/ref=cm_sw_r_ffobk_cp_ud_dp_3APT7HJ0F3D71RYNTR6T">The Community-First Advantage: How Modern Leaders Use Community to Drive Growth, Cut Costs and Compete in a Changing World</a>, by <a href="https://www.linkedin.com/in/christophercatania/">Chris Catania</a></li><li><em>(Coming out on April 1, 2026)</em> <a href="https://www.amazon.com/Community-Code-Strengthening-Go-Market-ebook/dp/B0GNJBXCPR/ref=sr_1_1?crid=2O19LGNGIUIH2&amp;dib=eyJ2IjoiMSJ9.C4ySvfmE08ecIEQxz_UA1Xh3AQK2D0NUTEJnDJ4O2JwtM3Ni-A4r3jBJ612J7px99AOf5hUD0J7x95CE1z6Dq43ci-v7464ilbN_BO8xxkesQ5gQsooKI_Oky3x19IB07DWNqtSXICoc6X7Zc1frAg2iGgCuhqxAA6Ac4_eG7319g7zHWRmuWe-uxllZYMoEMU1Jpjz5Yo8cXrDIz24xrTTn08TTm9ksXGjaeBFTpX4.0VRhDlujx8VKEf7DjqDT5hfL-HzotLWb3iKs7gyCFiA&amp;dib_tag=se&amp;keywords=community+code&amp;qid=1772393062&amp;s=digital-text&amp;sprefix=community+code%2Cdigital-text%2C172&amp;sr=1-1">The Community Code: Strengthening and Aligning Your Go-to-Market Through Community</a>, by <a href="https://www.linkedin.com/in/joshuazerkel/">Joshua Zerkel</a></li></ul><p>Lastly, quick caveat that most of what we do is in Asana, and so most of these use cases happen directly within Asana, using Asana AI. That being said, I think there are ways you could do similar work outside of Asana and I hope this still provides you some inspiration.</p><h3>Use Case #1: Content writing for across community surfaces</h3><p>By now I think most people who have familiarity with AI know it’s a great draft writer, taking together notes about tone and voice, what you want included, format, etc. and putting it together in a draft that can then be taken and finalized by a human. What we do takes it a little further.</p><p>I’m fortunate that community has established itself as a cross-functional (XFN) powerhouse at Asana. We work across the board with stakeholders in Product, CS, Support, and Marketing on a regular basis, and community is recognized as a true partner for these functions. Community milestone achieved, huzzah. As such, we receive about 30 requests a month from our XFN partners for various things — from event/webinar promotion, report requests, Ambassador speakers, early access and beta testing opportunities, upcoming product announcements, and more. Of these, many require copy to be written so we can share out the opportunities with the community members.</p><p>We have an <a href="https://asana.com/features/workflow-automation/forms">Asana Form</a> that we use for this, and one of the questions in the form asks for the category of the request. When the requester selects a particular option, in this case, “Share new, or cross-share existing content/campaign with the Community”, it triggers a few things in our workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*WzmWDdsDWMzni2AyDlruzg.png" /><figcaption>Requesters select what type of work they are asking to work with the community team on.</figcaption></figure><p>When this option is selected, there is form logic to show this question, asking where in the community they’d like their content shared:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*rhG9aKSqysQgcARyQrY28w.png" /><figcaption>There are a number of places in the community where we can share content.</figcaption></figure><p>When the form is submitted, we have automation set up that will automatically create subtasks, one for each of the boxes selected in the above screenshot. Then the AI magic begins. We have an <a href="https://asana.com/product/ai/ai-teammates">Asana AI Teammate</a> (who is lovingly named Falkor 🐉), who will take the information from the task, using notes of our tone, the channel of where the content is going to be posted, and write the suggested copy. We’ve even trained it to keep similar formatting, using html where we need to for Forum posts to center or use headers for sections, and kept considerations like how Slack posts need to be shorter than Forum posts that can be longer format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*P0giXDvIpa-rtKWfwtCbSA.png" /><figcaption>Falkor hard at work writing the draft for a Forum post.</figcaption></figure><p>Though it’s obviously important to keep a Human In The Loop (HITL) when it comes to anything regarding AI, using Falkor saves our team a significant amount of time. 🎉 Huge shoutout to <a href="https://www.linkedin.com/in/vanessa-s-m-neves/">Vanessa Neves</a> on my team who created Falkor.</p><h3>Use case #2: Monthly reporting</h3><p>This bit is very Asana-specific, so bear with me. The way Asana is set up is you can have <a href="https://asana.com/features/goals-reporting/portfolios">Portfolios</a>, which can house other Portfolios and Projects. Then you have Projects that house Tasks (and subtasks). A Task can also be multi-homed to sit in multiple Projects, as can a Project be multi-homed to multiple Portfolios. This essentially not only helps with organization, but if a Task is linked to a few different initiatives, multi-homing allows visibility and updates to multiple Projects by just updating a single Task.</p><p>For example, let’s use the first use case. If someone on the Events team asked the Community team to promote their event in the community, they could submit the form — this would create a Task that could then be multi-homed into a Community project (for us to track and write the copy, or have Falkor do it) <em>and</em> an Events project (so they can track where the different promotions channels). When we comment or mark this Task as complete, the Task shows completed on both the Community and the Events Projects.</p><p>The Community team has a number of Portfolios, Projects, etc. that we work in. All of these are multi-homed to one main Portfolio that houses everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*koGQovNYr81K0aIbrBruJQ.png" /><figcaption>A fairly redacted screenshot of our primary community team portfolio, or ‘the hub’, as we like to call it. Folder icons indicate Portfolios, whereas the other icons indicate Projects that have been multi-homed to this Hub Portfolio.</figcaption></figure><p>When the time comes for monthly reporting, we just ask Asana AI to draft our update. If we request it at the Hub portfolio level, it will pull all of the work held within it. We give it the sections and the framework that we want, include the start and end dates that we are looking for, and it pulls the main pieces of work and will auto-generate the summary for us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*Dts0izsnjQKMBl8ghXiq8g.png" /><figcaption>We use Asana AI to draft our monthly status updates, pulling all of the work included in the main Hub portfolio.</figcaption></figure><p>Transparently, though this process does help jumpstart a draft and surface the work that we accomplished throughout the month, the monthly status updates do still require significant manual work. A lot of our metrics and data live outside of Asana, like for example, in <a href="https://www.commonroom.io/">Common Room</a>, <a href="https://www.discourse.org/">Discourse</a> (our Community Forum), Salesforce, Tableau, amongst a few other locations, so we do still have to pull the numbers and then bring them into Asana for our status updates. Operationally, we don’t think it makes sense to work on integrations to bring these numbers into Asana; that’s not what the tool is for, so this will be something that remains manual, and that’s okay.</p><h3>Use case #3: Project organization via custom fields</h3><p>Within the Hub portfolio, one of the main Projects we have is our Roadmap. We keep all main tasks in here, from ideas for the backlog or the future, to recurring programs and events, to planned engagement initiatives, and even operational items. It’s my go-to source of truth for visibility on what the team is working on and to see what our current priorities are, and it also helps me with planning our roadmap for what is to come.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MvgPuAntzzgYeg2BcjdOkQ.png" /><figcaption>A (very) redacted form of our community roadmap. We use AI to help with filling out the custom fields.</figcaption></figure><p>As shown above, we use a few custom fields as columns — priority, program, operating principle, and FY27 big bets. These fields let me quickly analyze our work: Are we spending too much time on low-priority items? Are we contributing to Asana’s operating principles? Which big bets and community programs are our tasks tied to? That visibility drives better prioritization decisions, helps me keep my team’s scope aligned, and surfaces trends in how we’re spending our time. Nearly all of these tasks are multi-homed to other projects where more detailed work is happening.</p><p>Rather than having to manually fill out these custom fields for every task added to this project, we have smart workflows where AI will fill in the custom field based on the content in the task. Here is a screenshot of some of the rules we have running on this project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/1*rLiGXgHMD6q4jctoi4-diA.png" /><figcaption>A snippet of some of the rules that we have running on our Community Roadmap project.</figcaption></figure><p>Here is a screenshot of one of the rules listed above: “Categorize tasks by Operating Principle.” This uses Asana’s workflow builder, and states that whenever a task is added to the project, or if we run this rule manually, it will add the operating principle using AI. We then have written instructions for the AI where we further define the instructions, provide context and examples of what our operating principles are, and also provide it a course of action if the task does not meet any of the criteria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*1MnV66eqW8bo6mtZzlK_kg.png" /><figcaption>Asana’s workflow builder with instructions to assign an Operating Principle to a new task added to the Roadmap project using AI to deduce the relevant Operating Principle for the task.</figcaption></figure><p>We have similar workflows set up on most of our Projects, not only to fill out custom fields and help with classification, but to move Tasks to correct sections, to help rename Tasks for formatting consistency, to help summarize tasks, to set reminders for followups, and more. We use AI as a tool to run more efficiently and handle a lot of the smaller administrative tasks; believe me, the time adds up. Just like I say with other community operations automations, small + small = big. 🤓</p><h3>Thoughts for future AI opportunities</h3><p>As part of the Structure.Community summit, we had an exercise to identify future opportunities to use AI for our teams and our community. I won’t dive deeply into them since I haven’t worked on the feasibility of them or how I’d go about implementing them (yet), but I did want to share a few things that were mentioned I thought were very clever and would love to explore.</p><ul><li>Identify rising stars &amp; potential advocates through criteria like their engagement across community surfaces, sentiment, possibly even product usage, and send notifications for us community managers to reach out.</li><li>Amplify user-generated content across the community surfaces and social channels more broadly across the community and ecosystem as a whole.</li><li>Identify like-minded users based on criteria like level of product expertise, role/team, industry, conversation topics, and either make introductions or create a place for them to come and connect with one another.</li><li>Find trending conversations and topics throughout the community and sending notifications to relevant employees suggesting they get involved. (This could be for moderation to step in if conversations get too spicy, <em>or</em> it could be for something like flagging a productive conversation about a product or feedback with the respective product manager.)</li><li>Automated surprise &amp; delight and recognition.</li><li>Self-cleaning or updating community content, flagging, or deactivating outdated posts.</li></ul><h3>Conclusion</h3><p>I think a takeaway I had from the summit was optimism and excitement (aside from just feeling that happy feeling after seeing friends and being in-person at an event). I understand — it can be hard to be optimistic in a world where you’re constantly reading about mass layoffs because CEOs want to “rEpLaCe EvErYtHiNg wItH AI”. The job market (still) sucks, and even though I have seen community roles open up, I also have a lot of community friends still on the job hunt, or they’ve resorted to switching industries. But… in the conversations we had, it’s so clear to me that AI is a tool to help allow us (human community managers) make even better connections throughout our communities. It’s giving us more time to form those interpersonal relationships, to find potential opportunities for advocacy, to empower our community members, by taking care of all the transactional administrative work for us and supporting us in a lot of our day-to-day work. It’s not robots vs. humans. It’s robots + humans.</p><p>I’d love to hear other ways you and your community teams are using AI; feel free to throw it in the comments, or you can reach out to me at thecommopsgal@gmail.com. Also, in case you were curious, this article was 100% human written, with some minor edits for brevity and grammar by my friendly robot companion.</p><p>As a thank you for making it to the end, here is a picture of Yoshi — in his old age he’s developed a bit of cataracts and is partially blind, but he still loves to play catch, even if he misses the ball completely (like in this picture). We end up chasing a lot of our own balls these days, but if it’s still sparking joy for him, it’s still sparking joy for us too. ❤</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8zuB5pmsPYkRsVHtjgK4Vw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff2c0dd394ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we plan the year: An inside look at our annual planning]]></title>
            <link>https://medium.com/@tiffeoda/how-we-plan-the-year-an-inside-look-at-our-annual-planning-2d0d79064a9a?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d0d79064a9a</guid>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[annual-planning]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Mon, 05 Jan 2026 16:16:46 GMT</pubDate>
            <atom:updated>2026-01-07T17:02:07.218Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hG3LcboAfLeD3ryVET_YGw.png" /></figure><p>Wow! I cannot believe it’s been a year and a half since I last wrote here. To be honest, work has been a lot — nonstop organizational change, constant pivots, and a steady stream of parental leaves that’s left my team perpetually short-staffed. Outside of work, I needed time to not think about community. Add in everything going on in the world, and I mostly just wanted to shut my brain off. Buuut new year, new me. I’m back to doing my daily New York Times Wordles, brain exercises on Luminosity and Elevate, working out, and among all the other New Year’s Resolutions I have written down, one of them is to get back to working on this blog. I enjoyed being a bit quieter in the community industry with my head down doing the work, but — like Michael Jordan — I’m coming out of “retirement” and getting back on the court. I hope to do a monthly post. Feel free to keep me accountable if I start falling off.</p><p>My role has changed since my last post in July 2024 (wowza); I’m now Head of Community (milestone achieved!) and am not in the weeds with Community Operations as often, though obviously I’m still very involved. As a result, I’ll be writing about a broader range of community topics — from operations and ROI to leadership, programs, trends, and the occasional random musing. Heck, some might just be random musings, but <a href="https://www.youtube.com/watch?v=mIsnIt1p978&amp;list=RDmIsnIt1p978&amp;start_radio=1">it’s my <em>blog</em> and I’ll <em>write</em> <em>what</em> I want to</a>.</p><p>Okay, let’s get down to business… [to defeat <em>THE HUNS</em>] — I mean, it’s a new year. Even though our fiscal year doesn’t start until February 1st, we’ve been deep in annual planning, which brings me to today’s topic.</p><p><strong>Today’s topic: My Annual Planning Process</strong></p><p>There are a few notes to share just to start. This comes into play throughout the planning process.</p><ul><li>Since I started in May 2024, we’ve lost 3 people on the Community Team (which was already quite bare bones / keep the lights on) and have gotten 0 (I repeat, zero) backfills. Streamlining our processes, focusing on our high impact priorities, and being empowered to say “no” or “what is coming off our plate if we add xyz onto our plate” are going to be things we as a team will be practicing.</li><li>Our budget is flat YoY. It was also not much to begin with. (I’m sure this sounds familiar to a lot of you)</li></ul><p>I’ll probably share our actual annual plan in next month’s post (subject to change if another topic comes to mind), but for this one, I’ll write about the actual planning process. I hope that you can take this methodology and use what you find useful to do with your teams. 🙂</p><h3>Step 1: Individual retrospective (looking to the past)</h3><p>I asked each team member to individually reflect on the previous year — the work they did, programs they ran, how they worked with others on different teams, how they worked within the team, accomplishments, misses, the whole shebang, and focus on three categories: Start Doing, Keep Doing, and Stop Doing. (It’s helpful to create a slide template so everyone’s formats are consistent).</p><p>Once I had each team member’s contributions, I went through them, found trends, categorized them into groups, and created an aggregated slide. I then shared this with the team during a team meeting, and we used it as a stepping stone for the next step of the planning process.</p><p>Just to share, here were a few trends that I saw amongst the team retro:</p><p><strong>Keep doing:</strong></p><ul><li><strong>Team sprints</strong> — We run two-week sprints with kickoffs and a shared project to create visibility, encourage collaboration, maintain accountability, and keep an eye on bandwidth to prevent burnout.</li><li><strong>Product team cross-functional collaboration</strong> — we’e been working really closely with the Product team on things like community-generated product ideas and feedback, early access and beta tests, and also engagement initiatives for our Asana Ambassadors like monthly AMA’s with PMs. It’s not only been a huge hit with the Community, but the Product Managers have also thoroughly enjoyed getting closer to the community.</li></ul><p><strong>Stop doing:</strong></p><ul><li><strong>Fun engagement forum posts</strong> — We experimented with lighter, more playful topics, but they consistently underperformed. Given our members’ preference for product-focused content and our limited bandwidth, this work isn’t worth continuing at the capacity we were doing.</li><li><strong>Constant pivots and ad hoc work</strong> — We were pulled in many directions by requests and initiatives that didn’t always fit squarely within Community’s scope, which reduced our ability to focus on substantive community work.</li></ul><p><strong>Start doing:</strong></p><ul><li><strong>Team readouts</strong> — we do a lot, but we could be better at tooting our own horn. Being able to more strategically share readouts on accomplishments and what our upcoming priorities are to our cross-functional stakeholders.</li><li><strong>AI</strong> — we’re using AI to streamline some of our internal processes, but there is a lot of potential for additional automations and using our AI Teammate for better triaging, writing copy, and supporting our repetitive processes. Go community ops!</li></ul><h3>Step 2: Individual planning (looking ahead)</h3><p>Now that we were done with our retrospective and had a good baseline for what worked didn’t work well that we wanted to scrap and what did work well that we wanted to bring into the next year with us, it was time to plan for the future. The leadership team had published the company’s goals for 2026, and I asked the team to create their individual goals and plans, aligning them to how they roll-up to support the company’s priorities.</p><p>Importantly, part of this exercise was also listing out the things that they plan to take <em>off</em> their plates and stop doing. Again, a big theme for us this year is focusing on the high impact initiatives that align with company priorities, and trimming away the miscellaneous or busy work items that we spend our time doing. This may mean scaling back some of the “surprise and delight” and fun elements of community management, but given why members come to the community — product knowledge, updates, and real use cases — it’s a necessary tradeoff.</p><p>You may notice there is a lot of individual planning going on. My thought process behind this was I didn’t want other team member priorities, or my own thoughts, to bias their brainstorming processes. Each team member knows their AoR (area of responsibility), what programs or parts of programs they run, and what the priorities are. They also knew what the trends were from Step 1, and what they want to work on to continue developing their careers (from previous performance and career conversations that they’ve had with me). I wanted them to do thinking and planning on an individual level first, then come together as a team to put everything together.</p><h3>Step 3: Piecing it all together</h3><p>As a team, we put together our goals and plans for 2026. Each item has a DRI (directly responsible individual), though team members may support them or own specific parts. Taking everyone’s individual plans, we were able to roll up smaller items into bigger programs or initiatives, we were able to see general timing and ensure equally distributed work and bandwidth for each team member, and we always made sure what we had written down aligned with the company’s priorities. Additionally, we put together a slide of the things that we were going to slow down or stop doing, the reason behind it, and any potential impacts to KPIs by doing so.</p><h3>Step 4: Cross-functional sharing and buy-in</h3><p>Once we had our high level plan and goals tied to each, I shared them with my manager for any feedback. This is obviously an important step, especially for us to make sure she was okay with the things we noted we were going to slow down or stop doing. Also, this was a chance for us to reiterate the focus on high impact initiatives and what that would look like from a Community perspective. Lastly, it shed light on our current bandwidth and what would not be in scope for the year without additional support or headcount.</p><p>Once we got aligned with my manager, it was time to have conversations with our cross-functional partners. We know Community shouldn’t exist in a silo; we’re a highly collaborative function that works so widely throughout the organization. By sharing the plan, priorities, and goals with our cross-functional friends, we’re able to:</p><ul><li>Share timelines and identify collaboration opportunities</li><li>Flag where we’ll need cross-functional support</li><li>Clarify priorities and alignment</li><li>Be transparent about what we’re no longer supporting and why</li><li>Reinforce best practices for engaging with Community</li><li>Adjust our roadmap based on theirs, where it makes sense</li></ul><p>It’s also an opportunity for the cross-functional teams to share their plans with us, where we can find opportunities for community to support, when they might need to leverage the community for feedback or participation, and see if we have any shared goals we can work together to achieve. Generally, just having the transparency not only adds the visibility into what we’re working on, but increases trust, establishes better communication, and improves the partnership. I feel like lots of times community teams can get pushback from other teams when making an ask of them or needing their support on something; I know I’ve heard “that’s not really my job” in the past from people on other teams (not at Asana, of course). Sharing your plans and creating this sense of co-creation and collaboration helps prevent that kind of mentality later down the road. After all, the community helps them with their jobs just as much as their support helps the community.</p><h3>Step 5: Making a source of truth</h3><p>Whether you work out of a Google Doc, a slide deck, Asana, or something else, making a source of truth for your plans and roadmap is what I would consider the final step. Having a source of truth doesn’t mean it’s written in stone — plans will change. Its purpose is to provide clear, up-to-date visibility for the team and our stakeholders.</p><p>For my team, we use both Google Slides and Asana. Google Slides is the visual representation, if we need to share with leadership or XFN stakeholders, and it’s generally better to show for timelines and high level visibility. We use Asana for tracking ownership, dates, tasks involved, and generally for all of the work management. This is the basis for our projects, and we use the annual plan to create the more detailed roadmap that we work off of. We then make sure to look at the roadmap monthly to shift any items and make sure statuses are updated. This is also then included in our monthly reporting as we track progress for our KPIs throughout the year.</p><p>💡 If you want to learn a bit more about Roadmaps, <a href="https://medium.com/@tiffeoda/community-roadmap-from-brainstorm-to-execution-in-5-steps-e854eaedd904?source=user_profile_page---------6-------------24faf6bf40d3----------------------">here is an older post I wrote about building and executing the community roadmap</a>.</p><h3>Conclusion</h3><p>Depending on factors like your organization, team size, dependencies/blockers, and planning culture, your annual planning process may look different. We’re a global team with people located across many timezones, so we’re not able to do an in-person session or offsite to create this together, which is why there are several steps done asynchronously in the process. If you have the luxury of doing so, do a one-day planning session together! Or, if your company has more of a bottoms-up approach to planning, or you want to include XFN partners earlier on during the ideation process, there’s no right or wrong way to plan. This is what I’ve found works with my team within this company, but of course there is always iteration and room for improvement.</p><p>If you need any guidance on team planning, or want to do some roadmapping, feel free to reach out to me at <a href="/service/mailto:thecommopsgal@gmail.com">thecommopsgal@gmail.com</a>. I’d love to chat! And lastly, as a thank you for getting to the bottom of this post, here is a picture of Yoshi, who just celebrated his 13th birthday and is still going strong! For his birthday, he wanted to be an emu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*acF84kWT7z0HE3Qw1sXUPg.jpeg" /><figcaption>Yoshi pretending to be an emu.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d0d79064a9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conducting a Community Program Audit]]></title>
            <link>https://medium.com/@tiffeoda/conducting-a-community-program-audit-2cf84f671b99?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cf84f671b99</guid>
            <category><![CDATA[community-building]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[community-operations]]></category>
            <category><![CDATA[community-engagement]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Mon, 01 Jul 2024 14:47:23 GMT</pubDate>
            <atom:updated>2024-07-01T14:47:23.598Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aQnbjbngeXSl5f-dZ6zhUg.png" /></figure><blockquote>🔥 Template included! Be sure to check out the program audit deck template linked in this article.</blockquote><p>As many of you know, I recently started a new job, responsible for running one of our global community programs. Starting at a new company is a lot of work — aside from the general company onboarding, getting used to navigating your new tools, figuring out your team and how to best fit in and work with them, and being the ‘new kid at school’, you reach a tipping point where the onboarding slows down and the real work begins.</p><p>In this article, I share with you some of the things I did as I ramped up in my new role, as well as dive into how I did an audit of the community program I was tasked with leading.</p><h3>1. Get caffeinated with lots of coffee chats</h3><p>I’m obviously being facetious here with the section title, but having tons of conversations is so important. You not only get to introduce yourself across your company and your community, but you can find out really good historical context, feedback, and general thoughts about various parts of the team, the community, and the program.</p><ul><li>Introduce yourself to the community and share a calendar link (like <a href="https://calendly.com/">Calendly</a> or <a href="https://www.getclockwise.com/">Clockwise</a>) with a note that you’d love to meet and chat with members. Get to know them, when and why they joined the community, how they tend to engage, what they’ve liked, and what they haven’t liked so much.</li><li>Meet with your team members. Learn about their role, AoR (area of responsibility), working style, how they’ll interact with you and your AoR, their roadmap and priorities, and any context they have to share about the community and your program. Find out where their pain points are and also what types of things they’d like to work on but haven’t been able to do. Also ask them for a list of other people at the company you should meet with.</li><li>Have cross-functional meetings with people across the company. Follow the same conversation flow as mentioned in the above bullet point.</li></ul><p>Throughout this process, take lots of notes. Find key themes, jot down new ideas, collaboration opportunities, potential blockers or other things to look out for, initial impressions on priorities, etc.</p><h3>2. Dive into the community</h3><p>Get deep in the weeds of the community.</p><ul><li>Read posts, comments, and get acquainted with the different areas that members can engage.</li><li>Note any trending topics, subjects of conversation, common themes, and get a gauge of general sentiment.</li><li>Find frequent posters, learn who’s active in the community, recognize leaders within the community.</li><li>Go through the various processes your members would go through, whether it’s onboarding into the community, registering for an event, trying to find a resource, asking a question or posting a response, etc.</li><li>Observe. Over the first month or so, get familiar with the ins and outs of the community and have a solid picture of the lay of the land.</li></ul><p>Similarly to the coffee chats, take lots of notes and add to the themes and patterns you previously noted.</p><h3>3. Tech stack and data</h3><p>Time to activate the left side of your brain. Dig into the backend of your community — look inside your platforms and tools, see how they run, and also use the analytics to see how the community or your program is performing.</p><ul><li>Compare the existing data with the annual goals and determine how the program is performing.</li><li>Assess the platforms and ensure there is a comprehensive data flow throughout the tech stack. In other words, the data is not siloed in a platform, but rather, you can see the data across the platforms and thus the program.</li><li>Check for data integrity. Can the reports that you run be trusted, or are there asterisks and caveats to the numbers?</li><li>Are the reports and dashboards available to you relevant to the goals set in place? Is there a clear “so what” that you can deduce from the data, or any actionable insights you can gather?</li></ul><h3>4. Put together an audit finding presentation and roadmap</h3><p>The next thing I did was synthesize all of the information I gathered and put a deck together. In the deck, I report on the various areas of the program audit:</p><ul><li>What’s going well</li><li>What are areas of improvement opportunity</li><li>Goals check-in</li><li>Looking ahead themes</li><li>Proposed roadmap</li></ul><blockquote><strong>⭐️ I put together this </strong><a href="https://docs.google.com/presentation/d/1a5jvtIIudTcfTIvL2oAB7LDIjtVYKdhdlT_pJGKjQEE/edit?usp=sharing"><strong>program audit deck template</strong></a><strong> that you can copy or use as inspiration. ⭐</strong></blockquote><h3>5. Validate the audit deck with your team and cross-functional stakeholders</h3><p>Once you have the audit deck in a good place, it’s time to show it off and validate it with your team and key cross-functional stakeholders who you met with. Obviously, validate it with your manager and perhaps even skip-level manager too. Walk them through the deck, ask any clarifying questions you may have, and get their feedback. Is the audit aligned with their perceptions and context of the program? Are the look-forward themes and proposed roadmap in line with the rest of the team’s priorities, and does it make sense given the needs of the community?</p><p>You may go through a few revisions based on feedback you get from the team, but validation is an incredibly important step to make sure you don’t run your program in a silo, and to make sure the observations and notes you took throughout the process are accurate representations of the status of the program and the community.</p><h3>6. Re-visit the deck and update it on the regular</h3><p>I’m using this deck as a key resource for my team and pretty much always have the deck as an open tab in my browser. Here are a few examples where having it came in handy.</p><ul><li>Partnering with another team, something came up which resulted in separating one initiative on the roadmap into two parts and prioritizing a specific part before the remainder of the initiative. We updated this on the roadmap and added a note explaining why we made the change.</li><li>We had a fire occur which allowed us to flag a pressing issue in the community. As a result, we switched the timing of two initiatives, making it such that we focused on the pressing issue before the larger initiative we had previously prioritized first. We updated this on the roadmap and added a note explaining the change.</li><li>Due to team PTO, we realized one of the initiative’s timeline was not realistic, so we extended that initiative on the roadmap.</li><li>We had a new ask to support an upcoming event. Due to capacity constraints, we postponed one of the initiatives on the roadmap to accommodate this prioritized event. Again, we updated this on the roadmap and added a note explaining the change.</li><li>On a monthly basis, I’ll update the goals check-in slides so that at any point, people can go to the deck for a snapshot of how the program is performing relative to its goals. (Given I haven’t been at the company for multiple months yet, this is more of a “I will do” rather than a “I have done”).</li></ul><p>I’m six weeks in, and already the audit I conducted and the corresponding audit deck have become a source of truth for my team. It helps us stay organized, manage our bandwidth and capacity, and also has the context to understand why we may have made changes to the roadmap.</p><p>If you are auditing your community or a community program and looking for some help or guidance running the audit or putting together your findings, I’d love to chat. You can reach me at <a href="/service/mailto:thecommopsgal@gmail.com">thecommopsgal@gmail.com</a>. I’d also love to hear from you if you used my audit deck template in any way. And now, as a thanks for making it to the end, here is a picture of Yoshi writing this article for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J4GIBfcXY77lkXlAq7Tp6g.jpeg" /><figcaption>Yoshi, the CommOps Dog, hard at work. I pay him in treats and free rent.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cf84f671b99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 3: Scoping automation requirements]]></title>
            <link>https://medium.com/@tiffeoda/part-3-scoping-automation-requirements-77ff77c30f4c?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/77ff77c30f4c</guid>
            <category><![CDATA[community-operations]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[community-management]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Mon, 20 May 2024 15:02:16 GMT</pubDate>
            <atom:updated>2024-05-21T02:56:23.765Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g_ep9kzTSqlv_gYIxavtIw.png" /></figure><p>This is the third article in the series about automations -</p><ul><li>Part 1: <a href="https://medium.com/@tiffeoda/part-1-wait-dont-automate-gauging-when-automation-becomes-crucial-3dff64975893">Wait. Don’t automate! Gauging when automation becomes crucial</a></li><li>Part 2: <a href="https://medium.com/@tiffeoda/part-2-front-and-back-of-the-house-automation-considerations-619be5aaff08">Front and back of the house automation considerations</a></li><li><em>Coming up:</em> Automation project management</li><li><em>Coming up:</em> Automation implementation tips &amp; tricks</li></ul><p>Okay — you’ve identified a repetitive task or process that is sucking up you and your teammates’ time and has gotten to the point that it needs to be automated. That’s great! Let’s talk a bit about how to start scoping these automation requirements to make sure the automation that’s built fulfills all the needs and there are no surprises or curveballs once the automation is set up.</p><h3><strong>Why is scoping automation requirements important?</strong></h3><p>I can’t stress enough how important it is to be thoughtful about how you make your automations. Here are a few reasons why scoping everything is important:</p><ul><li>It ensures you’ve captured every scenario that a process can go through. There may be deviations, exception cases, or outliers to a process and you want to make sure the automation is set up handle each of those.</li><li>It helps determine tooling. Depending on the complexities of the automation and what is capable natively within the tools you’re using, you may need to do custom development or use an external tool.</li><li>It provides the documentation for your team, stakeholders, and, if you’re using custom development, your developers. This documentation should also be saved as a resource for future alterations to the automation, or in the event you leave the company, your successor is able to see how the automation is set up.</li></ul><h3>1. Document the manual process</h3><p>You’ve probably already spent significant time doing the process manually, and documenting the steps, the pre-requisites, the parallel paths, etc. is a key part in scoping out the automation. Just spend some time jotting down what you do whenever you go through the task. Also, if any other people also do this task, be sure to have them document the process as well, making note of where your processes are similar and where they may deviate from one another.</p><p>A process chart is oftentimes helpful for a visualization of the process steps, but also make sure to keep some space or have a place to document everything in writing. The more detail, the better!</p><h3>2. Determine variation points and variables</h3><p>As you’re going through the process manually, note instances that don’t fit the automation model. These variations or exceptions might cause errors (e.g. the subsequent action doesn’t happen) or incorrect actions (e.g. the wrong subsequent action is taken). Decide how the automation should handle these cases and how to fit the variations into one of your defined process paths.</p><p>As a side note, I find these outliers incredibly hard to think of without actually experiencing it first. It takes time to let a process continue manually and note exceptions as they arise. You never know what unique cases might occur.</p><h3>3. Align with your teammates and stakeholders</h3><p>If you have other teammates who work on parts of the process, it’s important to have them do the same exercise. You’ll want their documentation to find out if your processes are consistent to one another, and if they have any variation points that you may not have encountered. Additionally, if you have stakeholders, like from any cross-functional teams, it’s helpful to get their input as well. It’s best not to build automations in a silo, but make sure it is also aligned with your partnering teams’ processes.</p><p>While doing this step, it’s helpful to not only have their documentation, but walkthrough your documentation and findings as well. Get their input on the automation points you’ve scoped out to see if there are any other considerations you may not have thought about.</p><h3>4. Consolidate the documentation</h3><p>You’ve been monitoring and running the process manually for a while now, enough time to sufficiently capture the various scenarios, use cases, and exceptions that could potentially happen. You’ve gotten your teammates’ and stakeholders’ documentation and input, and feel aligned in the direction. Now, put it all together. Update your original documentation, including both the process chart and the written documentation and details.</p><p>As the community team’s operations person, you will most likely also have the insights into your tech stack and whether these automations will be able to run natively in the tools where the processes are taking place, or if you’ll need custom development or a third party in order to create the automation. It could be helpful to note this as well. Whether you have a developer helping you with your efforts, or you’re building this by yourself, noting where or how the process steps take place is important to include in your documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bm-9IJ5QxE1nqbGSDtPJpQ.png" /><figcaption>This is just a snippet of an example of what an automation process chart could look like. In this example, you can see decision points, what’s manual, and what’s automated.</figcaption></figure><h3>5. Team validation</h3><p>Validate you’ve captured everything in your documentation by doing a final validation session with your team and any relevant stakeholders. Schedule a meeting for the walkthrough, and walk them through the process end-to-end. Show the steps that will be manual versus automated, point out the input they’ve provided to you during step 3 above, and review the various exception cases and how the automation will handle those exceptions. Get a final sign-off that everyone is aligned and approves of how the automation will run.</p><p>As a personal tip, I highly recommend the team sign-off process, including from your manager. I’ve gone as far as to have an “approval” section at the bottom of the documentation with each person’s name and a checkbox stating they’ve read through and sign-off. Automation takes a lot of work to create and implement, and having this sign-off process can protect you from “… but should we do this instead” or “…can we add this to the process” which would add from scope creep or delay the project all together.</p><h3>Front of the house automations</h3><p>I wrote this article mainly focused on back of the house automations. Generally, scoping out requirements for front of the house automations will be the same, but there’s more dependency on your community members to go through the process and also have the opportunity to give feedback. Here are a few quick considerations:</p><ul><li>Use a user experience tool to track user behavior (e.g. Pendo, Appcues, Fullstory) to watch their behavior as they go through the process.</li><li>Non-invasive feedback forms or even a simple “How would you rate your experience” throughout the process.</li><li>Rely on a trusted group of members who can give more detailed input and feedback and be a sounding board.</li></ul><p>When it comes time to launch the automations, there are additional steps you should take for the front of the house. We’ll go over that more in the last post of the series, <em>Automation implementation tips &amp; tricks</em>.</p><h3>Next steps</h3><p>Now, it’s time for the work to start on building the automation! Whether you are working with a developer, your platform vendor, or are building it yourself, it’s important to have proper handoff from the requirements gathering stage, and included in this is managing the automation project. I’ll dive deeper into the next steps in the next blog post of the series, <em>Automation project management</em>.</p><p>Thanks for making it to the end of this post. It took me a little longer than planned due to starting my new job. Onboarding is no joke! 😅 Here is your Yoshi appreciation photo of him at the new park that opened up by our house, facing Oracle Park where the San Francisco Giants play.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rk2JIici2X2BoK9Rkmd9kQ.jpeg" /><figcaption>Yoshi enjoying the sunshine by the San Francisco Giants’ Oracle Park.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77ff77c30f4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 2: Front and back of the house automation considerations]]></title>
            <link>https://medium.com/@tiffeoda/part-2-front-and-back-of-the-house-automation-considerations-619be5aaff08?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/619be5aaff08</guid>
            <category><![CDATA[community-operations]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[operations]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Thu, 29 Feb 2024 16:02:17 GMT</pubDate>
            <atom:updated>2024-02-29T16:02:17.680Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*DRmuupdyI61gAsAYJ9vAww.jpeg" /></figure><p>This is the second article in the series about automations -</p><ul><li>Part 1: <a href="https://medium.com/@tiffeoda/part-1-wait-dont-automate-gauging-when-automation-becomes-crucial-3dff64975893">Wait. Don’t automate! Gauging when automation becomes crucial</a></li><li><em>Coming up:</em> Scoping automation requirements</li><li><em>Coming up:</em> Automation project management</li><li><em>Coming up:</em> Automation implementation tips &amp; tricks</li></ul><p>From interacting with community members to implementing a new tool, community operators have the unique ability to straddle the line in the community and live in both the back and front of the house. The same holds true for automations. Automations can be front-facing, something the community member directly gets to experience and benefit from, and they can also live behind the scenes, making processes for the community team more efficient and streamlined. In this article, I’ll discuss considerations as you build automations for both sides of the community.</p><h3>Front of the house automations</h3><p>Front of the house automations revolve around member-facing interactions and experiences. Whether it’s automated messages and notifications, to updates on statuses for things like event registrations, there are a handful of considerations to keep in mind.</p><ul><li><strong>Personalization</strong>. While automations can streamline processes, we never want to lose our personal touch when it comes to community building. Make sure to segment or properly identify the personas and the various routes or experiences they might have and build the automations to match that particular type of member’s experience and use case. You never want your community member to feel like a sheep being herded (I just spent a weekend on a farm with 🐑, so this is not <em>totally</em> random).</li><li><strong>Timeliness</strong>. Automated notifications, messages, and processes should be timely and relevant. You should set regular reminders to audit any front-facing automations to ensure they’re still up to date and make sense. Nothing shouts automated like, “Happy summer!” when it’s December. Also, be thoughtful of when an automation triggers — if it’s immediate, delayed, or based off of a previous step.</li><li><strong>User experience.</strong> You want to prioritize the member experience when designing front of the house automations. Whereas a backend automation can be strictly operational and maybe have its wonky elements to it (for example, an un-designed or plaintext button), you need to be thoughtful about providing that good frontend experience. To that end, it doesn’t hurt to get feedback through a quick pop-up survey asking how they’d rate their experience.</li><li><strong>Escalations</strong>. Sometimes, despite best efforts to audit and maintain them, automations break, or community members can get lost as they go through various processes. Make sure they have a way to surface an issue and reach out to the team if they need support or assistance. Also, make sure there are resources like knowledge base articles or info bubbles accessible to help them help themselves.</li></ul><h3>Back of the house automations</h3><p>Back of the house automations are for efficiency; they take care of repetitive, routed tasks so we don’t have to mindlessly click the same things over and over again and spend time doing something that’s not really worth our time.</p><ul><li><strong>Ownership</strong>. Even though the automation takes care of itself, for the most part, there should be a designated owner of the process. For example, if the task of reviewing user group leader applications is handled by a community coordinator, it should be that person’s job to monitor the automation, make sure it’s working as it should, and monitoring reports for any outliers or exception cases as the automation runs.</li><li><strong>Auditing and maintenance.</strong> Similarly to front-facing automations, make sure you are ‘going in for your 10,000 mile tune-up’ (that’s a 🚗 analogy) and keeping the automations up to date. Programs are always evolving, things are always being fine-tuned, and you want to make sure your automations are keeping up. Add it to your community ops roadmap so you can allocate time to regularly audit your automations, looking at things like the process steps, time delays, copy, exception cases, errors, and how frequently the automations are running.</li><li><strong>Tech stack</strong>. As you’re building automations, you may need to connect various tools or platforms in order for the automation to run. Make sure you’re documenting the automations — how they work, what they do, what steps are done in each of the tools, and also how the data flows. This is particularly important if you are working in tools owned by other teams and you (the community team) are not the main admin. Also try to minimize tech debt by clearing out automations irrelevant or outdated processes.</li><li><strong>Documentation.</strong> I know I mentioned this a little bit in my last bullet point, but I think it’s important to stress documenting <em>everything</em> in your automation, and this is something I will cover in parts three and four of this series. I recently had a former colleague reach out about an automation I had created that was still running for the community, asking about a configuration detail and why something was set up the way it was. It had been so long ago, I didn’t remember the particulars, and I hadn’t created documentation for it, leaving them in a bind now that the automation needed to be updated. Shame on me.</li></ul><h3>Conclusion</h3><p>Automations are amazing to help make things more efficient and run more smoothly, both from the front and back of the house perspective. However, there are various considerations and differences you should take into account when implementing these automations. Being thoughtful and intentional about how, where, what, and when you automate can greatly improve (or hurt) the member experience and your team’s efficiency.</p><p>And as a thank you for making it to the end with me, I give you Yoshi in a baking pan. He tasted delicious. Please ignore the mess in the background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fztUKpVE8mAgCHSaa1nLQQ.jpeg" /><figcaption>We, obviously, did not actually eat Yoshi. We were also recycling the pan and did not subsequently use it to make food.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=619be5aaff08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 1: Wait. Don’t automate! Gauging when automation becomes crucial]]></title>
            <link>https://medium.com/@tiffeoda/part-1-wait-dont-automate-gauging-when-automation-becomes-crucial-3dff64975893?source=rss-24faf6bf40d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dff64975893</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[community-operations]]></category>
            <category><![CDATA[operations]]></category>
            <dc:creator><![CDATA[Tiffany Oda]]></dc:creator>
            <pubDate>Mon, 05 Feb 2024 15:27:22 GMT</pubDate>
            <atom:updated>2024-02-05T15:27:22.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vf4tz1Xp0b3OKWmxwMUtcQ.png" /></figure><p>I was recently in a conversation with a founder who said the goal for their community was to make it, “completely self sustaining where all of the messages are automated [and they don’t need any community manager moderation].”</p><p>Aside from me making the 😦 face and thinking the 🤮 face at hearing it so blatantly said, unfortunately it wasn’t the first time I’ve heard automation being idolized in this way. Automation is sexy, and as communities grow, automation is necessary to keep up. However, there is a right time and place to automate, and if done too soon or too quickly, or in the wrong processes, it can be detrimental to not only your internal operations but also to your community members’ experiences.</p><p>In this article series, I’ll write about how to “Wait. Don’t automate!” Set yourself up for success when considering automation in your community by waiting before moving forward with implementing your automation. In this post, I’ll cover how to gauge when automation becomes crucial by forecasting the future time requirement for “<em>automate-able</em>” processes.</p><p>Also to be published in this series are:</p><ul><li>Front and back of the house automation considerations</li><li>Scoping automation requirements</li><li>Automation project management</li><li>Automation implementation tips &amp; tricks</li></ul><h3>What’s “automate-able”?</h3><p><em>I know, “automate-able” is not a real word. But it’s fun to say out loud. Try it!</em></p><p>The first to consider for automation is what kinds of things can be automated, and what things should stay manual with a human touch. As a guiding principal, I like to suggest:</p><p>⚙️ <strong>Automate process that are:</strong></p><ul><li>Repetitive: Done over and over again on a regular basis.</li><li>Multi-step: Have multiple steps that go through the same sequence.</li><li>Non-human touch: Don’t need personalization, customization, or relationship building.</li><li>No brainers: I like to think of it as the tasks you can do while watching TV and drinking a glass of wine because it’s so routine and doesn’t require you to think — you’re just clicking through and doing the motions.</li></ul><p>🫣 <strong>Don’t automate processes that are:</strong></p><ul><li>Rapport building: Relationships with members is mandatory in community management. If automating this process would diminish valuable ‘face time’ with members, don’t automate.</li><li>Complex: If there are a number of variables and exception cases for which a process can run, where human decision making determines the next steps.</li></ul><h3>Gauge when automation becomes crucial</h3><p>Even in my work today, there are manual tasks that I do, simply because we aren’t at a point we need to spend time to make an automation — the volume isn’t high enough. The same holds true at a startup like Talkbase, to working at Salesforce for the Trailblazer Community. (Did you know when I joined the team in 2017 there were <em>no</em> automations for community programs or processes?! Pretty crazy, right?) However, there will come a time when this changes, and it’s important to be able to forecast when the volume will reach capacity for the team’s bandwidth.</p><p>I use this method for being able to calculate <em>when</em> automation should be considered:</p><ul><li>What repeated processes does your team have that takes up bandwidth? What are you or your team members spending a lot of time doing?</li><li>How many times a week does this process take place?</li><li>How long does it take to do the process once?</li><li>Looking at your growth trajectory, how much <em>more</em> time would this same process take X amount of time in the future?</li></ul><p>I know this is a little vague, so let’s dive into this a bit deeper with an example. You have a user group program with an application process for members to apply to be a user group leader.</p><ul><li>You receive 20 applications a week.</li><li>Each application requires 10 minutes to review.</li><li>That means you are spending 200 minutes, or 3 hours and 15 minutes, a week reviewing applications.</li></ul><p>At this point, you can determine if this 3 hours and 15 minutes a week is worth you or your team member’s time. It could be that it’s already too much, in which case you could consider automation now. However, if it’s still manageable from a bandwidth perspective, you could take this one step further by looking at your growth trajectory and seeing when you’d need to reevaluate. To continue this example, let’s say that the user group program is growing by 5% every month, and you don’t want to spend more than 5 hours a week doing this task.</p><p>According to this model, as you can see, you’ll reach this capacity between Months 9 and 10. As such, you’ll want to start scoping out the automation so that it’s ready to go live by Month 9. Depending on the complexity of the automation, this may mean that you start working on the automation a few months prior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iTZKe9lkGlduBd_E7iZSxw.png" /><figcaption>With a 5% MOM growth, the current trajectory shows your team will reach the 5 hour a week limit of reviewing user group leader applications between Months 9 and 10.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsQ1mnGuN7bWqyBoLaZu-A.png" /><figcaption>This is a graphical visualization of the above graph, showing the red line (time to review) reaching capacity of 5 hours a week (yellow line) at the Month 9/10 mark.</figcaption></figure><h4>Keeping track of all of the potential automations</h4><p>If your community is established and reaching that exponential growth phase, or you’re coming to the time that automation is imminent, it can become overwhelming on how to keep track of these processes, timing things out, and planning when to start working on the automations. It’s a lot to keep track of! However, this is a great example of why having a dedicated community operations person on your team is important, the type of work they could do, and even the type of impact they can bring to your team. They would be able to work with the team and figure out potential processes to automate, figure out the bottleneck and potential timeline, and keep an eye on it on the community roadmap.</p><p>If you have some processes in mind that you want to think about automating, but you’re not sure if it’s the right time, I’d love to chat! Feel free to email me at thecommopsgal@gmail.com. Or, if you’re thinking about hiring a community operations person for your team but need a bit of help creating a business case for the headcount or some job descriptions for inspiration, email me!</p><p>Thanks for making it to the end, and I look forward to seeing you next time for part 2 of this series. And for my show of appreciation, here is a picture of Yoshi. He’s at my sister in law’s new condo and is being forced to wear sneakers to not scratch up the floors. Despite looking happy, believe me — he’s not. 🙃</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fFdz4JPbYnl95DriYaCx5A.jpeg" /><figcaption>Yoshi is not happy even though he looks happy. He hates the sneakers.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dff64975893" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>