Again thank you so much Eddie it's great learning a lot. I'll email you if I get stuck again, but this has been really helpful looking at the analytics. You're a wealth of information, sure appreciate it.
Case Study: Engineering a Global Social Media Ecosystem for Philip Kim From "Spreadsheet Stagnation" to a High-Velocity, Volunteer-Led Digital Engine Client Overview
| Category | Strategic Detail |
|---|---|
| Client Name | Philip Kim (International Non-Profit Leader) |
| Industry | Non-Profit / Global Advocacy / Community Engagement |
| The Challenge | |
| The Solution | |
| Certifications | |
| The Impact | |
| The Tech | |
| The Results & ROI |
https://youtu.be/bUqqy5Wj900?si=rGojzu_BKKch1wjl
<aside> 📸
Client: Philip Kim
Organization: Community Arts Foundation (CAF) – an international nonprofit with significant volunteer network
Geographic Base: Los Angeles, California (with international audience reach)
Organizational Structure: Six volunteer administrators managing distinct social media accounts across multiple platforms
Current Platforms: TikTok, Instagram, Twitter, Blue Sky, Weibo, Red Book, YouTube, WeChat; plus website news and events section
Current Pain Point: Organization had developed a basic Excel spreadsheet tracking when content should post across platforms and which volunteers were responsible for each channel, but lacked strategic planning framework. Content was being created and posted reactively rather than being planned in advance, built up toward events, executed during events, and leveraged afterward. With numerous events happening continuously, the social media approach felt overwhelming and inefficient—each event received only single post rather than integrated multi-week campaign strategy.
Desired Outcome: Establish systematic approach to planning social media content two weeks in advance per event, build content calendars that span pre-event promotion through day-of coverage to post-event follow-up, create sustainable framework for coordinating six volunteer administrators across multiple platforms without requiring new software tools if possible, develop understanding of which content types and posting times actually drove engagement and reach for their specific audience
Current Resources: Google Workspace with Google Calendar, Google Chat, Google Drive, and Google Tasks already integrated across the organization; existing volunteer team familiar with these tools; open to exploring scheduling software but preferring solutions that integrate with existing infrastructure
Technical Knowledge: Nonprofit administrator with data literacy and analytical curiosity—comfortable examining Instagram insights and interpreting engagement patterns, but lacking frameworks for translating analytics into content strategy decisions
</aside>
<aside> ⚠️
</aside>
<aside>
Philip Kim initiated the consultation by positioning what appeared to be a software selection problem but was actually a strategic infrastructure problem. The organization had grown organically, developing multiple social media accounts across eight platforms as different volunteers brought their own platform preferences or as organizational priorities shifted. Rather than having a deliberate multi-channel strategy, they had accumulated channels—each one existing but none of them operating within a coherent framework that connected planning to execution to measurement.
The immediate friction was operational. The Excel spreadsheet tracked which volunteer managed which platform and when content should theoretically post, but the spreadsheet didn't actually drive the posting. Volunteers still needed manual coordination. The volunteer network, while generous with their time, couldn't be expected to maintain perfect synchronization without clear communication and advance warning. Meanwhile, events kept arriving—CAF apparently hosted them continuously—and each event received basic coverage rather than strategic amplification. There was no pre-event buzz building, no multi-post content sequence, no post-event momentum capture. Just posting when the event happened and moving on.
The software question emerged from this operational reality. Philip asked whether there was a scheduling tool that would improve their process, and mentioned they already used Google Workspace as their organizational infrastructure. This seemed like a simple tooling question, but it masked deeper uncertainty about what they actually needed. Did they need a sophisticated scheduler? Did they need to integrate scheduling with Google Calendar? Should they invest in learning new software, or could their existing Google tools be leveraged more effectively?
The analytical challenge was equally pressing. Philip had started examining Instagram insights, discovering patterns that surprised him but didn't yet translate into decision-making. The data showed their audience engaged most heavily at 6 a.m. to 9 a.m. Pacific time (with Sunday morning being the peak slot), with shocking concentration in a specific timezone pattern suggesting either international audience or significant East Coast USA reach. More striking was the engagement distribution: reels generated dramatically more engagement than stories or traditional posts, yet when looking at the account visually, stories appeared more prominent. The insights contradicted intuition, which meant the analytics weren't yet informing strategy—they were just creating confusion.
Beyond the operational and analytical layers lay the frequency question. How often should they post? The volunteer team had limited bandwidth. Posting more frequently meant asking volunteers to commit more time. But less frequent posting meant missing opportunity to reach an international audience operating across multiple time zones. How did they determine the right frequency given their content creation capacity?
</aside>
<aside> đź’ˇ
</aside>
<aside>
I delivered a comprehensive 60-minute strategy consultation addressing scheduling software landscape, live analytics interpretation, content planning frameworks, and sustainable team coordination approaches. Rather than prescribing a specific tool, the consultation evaluated what CAF actually needed against their existing infrastructure and volunteer capacity.
The consultation began by mapping the social media scheduling landscape, not to sell software but to clarify what different tools do and what tradeoffs they require. Philip needed understanding the distinction between what different platforms offer and whether a tool was actually the missing piece.
The main scheduling platforms discussed included Content Studio, Hootsuite, Buffer, and Feedhype. Each operates on different commercial models and offers distinct capabilities. Content Studio offers comprehensive multi-platform scheduling with editorial calendar views, team collaboration features, and the ability to compose content directly within the platform for immediate posting or future scheduling across Facebook, Instagram, TikTok, LinkedIn, and other major platforms. Hootsuite provides similar scheduling with strong analytics integration. Buffer offers lifetime deal options (occasionally available) at very low price points if purchased during promotion windows. Feedhype operates on low-cost subscription models with generous team member allowances.
The key distinction that emerged was that these tools aggregate expensive API access across thousands of users, allowing individual organizations to schedule content far in advance. When posting directly to Facebook, for example, users are limited to scheduling roughly 30 days in advance because that's how Facebook's API constraints work. But scheduling tools store content on their own servers and send it to platforms according to schedule, allowing users to plan months ahead. This technical distinction explained both why these tools exist and what they actually do—they're not magical; they're solving a real infrastructure problem created by platform API limitations.
However, the consultation also revealed a critical insight for CAF's situation: they didn't actually need advanced scheduling in the traditional sense. The organization has six volunteer administrators managing different accounts. If the core constraint is coordinating those six people to post consistently, the scheduling tool isn't solving the real problem. The real problem is communication and planning visibility.
This realization led to the strategic recommendation that ran counter to typical consulting advice. Rather than adopting new software, Philip should optimize what the organization already uses and knows. Google Workspace provides Google Calendar (where the organization already plans), Google Chat (their internal communication), Google Drive (their file storage), and Google Tasks (their task management). These tools already have adoption. The team understands them. There's no learning curve.
The proposed approach leveraged Google Calendar as the planning nucleus. Instead of creating a separate planning system in a scheduling tool, all event planning happens on the calendar the organization already uses. For each event, the calendar becomes the hub for the social media strategy around that event. Calendar entries can include notes about pre-event content, day-of coverage strategy, and post-event follow-up plan. Google Tasks can be created from the calendar entries, automatically assigned to the volunteer responsible for each platform. Google Chat becomes the coordination channel where updates and final content links are shared.
The advantage of this approach is profound: it creates a single source of truth using tools the team already knows. There's no training required. The only behavioral change is deliberate planning two weeks in advance instead of day-of scrambling. The coordination happens in the communication channels the organization already uses daily.
To illustrate this approach, I walked through how a Notion calendar could serve a similar planning function if they wanted more sophisticated templating. Notion has calendar views, board views, gallery views, and table views—allowing different team members to see the same planning information in their preferred format. Notion allows unlimited invitations to team members, so all six volunteers could be given access to the social media planning board. A database entry for each event could include fields for event name, date, platforms, pre-event content requirements, day-of posting plan, post-event strategy, and assigned volunteer. The beauty of Notion for this use case is flexibility—the team could evolve the template as they learn what information matters most for their workflow.
However, given that the organization already uses Google Workspace and has limited appetite for learning new tools (Philip explicitly stated this preference), Google Calendar with enhanced documentation and Google Tasks with clear assignments accomplished the same strategic goal with lower friction.
The consulting approach shifted when Philip shared his Instagram insights data. Rather than discussing abstract best practices, we examined his actual data and reverse-engineered strategic implications.
The most striking finding was that their audience engages most heavily from 6 a.m. to 9 a.m. Pacific time, with Sunday morning as the peak slot across all days. This pattern suggests either significant international audience (given the early morning engagement) or concentrated East Coast USA reach (where 6-9 a.m. PT equals 9 a.m.–noon ET). The dramatic drop-off at 9 p.m., counter to typical social media usage patterns where evening scrolling is common, further suggested their audience operates on a different schedule than the general social media population.
Rather than asking Philip to trust a generic "post at peak times" rule, we examined what that actually means for CAF. If the audience is genuinely most engaged in morning hours (whether due to international time zones or East Coast concentration), posting at 6 a.m. PT maximizes visibility to their core engaged segment. But this also raises a question: is 6 a.m. PT realistic for volunteer posting? Probably not. Scheduling tools solve this problem—volunteers can create content during business hours, and the tool posts it at optimal times automatically.
The reels versus stories distinction was equally revealing. Philip was surprised that reels generated 26,000 reaches (primarily unfollowed audience) while stories barely registered. This isn't a surprise when you understand how Instagram's algorithm works. Stories are pushed only to followers of the account, creating a limited reach ceiling. Reels are pushed to explore pages and recommendations, allowing them to reach non-followers at scale. Instagram has prioritized reels over stories because the platform competes with TikTok and YouTube Shorts—reels use the same 9:16 vertical video format as those competitors, while stories use 4:3. The platform's algorithm reflects that strategic priority.
This insight directly informed content strategy: reels should be a priority content type for CAF, especially if they want to grow beyond their existing 10,000 followers. The data showed reels reaching unfollowed audiences effectively, which is exactly how new audiences discover accounts. Stories remain valuable for audience retention and engagement with existing followers, but shouldn't consume volunteer capacity if reels drive better reach.
The engagement data by content type—likes, comments, shares, saves—provided further direction. Some content drives interaction (likes and comments) while other content drives reach (shares and saves from non-followers). Understanding the difference allowed Philip to segment strategy: content designed to build community among existing followers has different requirements than content designed to reach new audiences.
Philip raised the frequency question directly: how often should they post given volunteer capacity constraints? The answer required moving past the idea that "more is always better" and instead connecting frequency to content quality and organizational capacity.
The principle is straightforward: social media operates more like a video game than a publishing platform. You can win by paying money (advertising) or by paying with time (organic reach through high frequency). But if you're not running paid campaigns and you lack unlimited volunteer capacity, frequency becomes a constraint variable you optimize around quality rather than the other way around.
The golden rule in social media engagement is that platforms push content to roughly 10% of a creator's audience initially, then expand based on engagement. For CAF with 10,000 followers on Instagram, this means a post reaches roughly 1,000 followers first. If those 1,000 people engage positively, the algorithm pushes to additional followers and non-followers. If engagement is poor, the algorithm stops expanding the reach.
This means the relevant question isn't "how often can we post?" but rather "how often can we post good content?" If volunteers can reliably produce quality content daily, daily posting makes sense. If they struggle to produce quality content more than three times weekly, three times weekly is the right frequency. Posting mediocre content seven times daily damages reach more than posting excellent content twice weekly—poor engagement signals to the algorithm to reduce expansion, limiting reach more aggressively than lower posting frequency would.
Given that CAF has six volunteer administrators and numerous events, the realistic frequency depends on event distribution. If the organization can commit to high-quality content production around events (pre-event building, day-of coverage, post-event follow-up), that creates a sustainable rhythm. During slow event periods, the frequency might drop. During high-event periods, frequency increases. This isn't a failure of consistency; it's intelligent capacity management.
The conversation also addressed the unusual platform mix CAF uses. Eight platforms across TikTok (English-language short video), Instagram (image and video with Western audience), Twitter/Blue Sky (text-based with engagement-focused community), Weibo and Red Book (Chinese-language platforms), YouTube (long-form video), and WeChat (Chinese messaging and content app) suggests CAF serves multiple geographic and linguistic communities.
This isn't a platform proliferation problem if each platform serves a distinct audience. Weibo and Red Book reach Chinese audiences; WeChat reaches Chinese diaspora communities. YouTube reaches audiences interested in long-form content. TikTok reaches younger audiences across regions. The complexity is real, but it's tied to mission rather than poor planning.
However, the eight-platform approach does explain why Excel spreadsheet tracking felt overwhelming. Managing that many platforms with six volunteers requires systematic clarity about which volunteer owns which platform, what content variations matter (language, format, optimal posting time by platform), and how information flows from planning to execution. This is where either a scheduling tool (which handles multi-platform distribution automatically) or a detailed Notion planning system (which documents the multi-platform requirements clearly) becomes valuable.
The consultation didn't recommend consolidating to fewer platforms. Instead, it recommended documenting the platform strategy clearly—why each platform exists, who the target audience is, what content types work best on each platform, and how frequently to post to each. Once documented, coordination becomes manageable.
Toward the end of the consultation, we discussed a content generation approach that solves the perpetual "what should we post?" problem without requiring constant creative effort. Rather than treating each post as a discrete creative challenge, think of content as answers to frequently asked questions the audience has about the organization, its mission, and how to engage with it.
For CAF, the questions might be foundational: What is the Community Arts Foundation? What kinds of programs do we run? How do I volunteer? How do I attend events? What makes our approach different from other arts organizations? How do I support the organization financially? But questions also go deeper into specific concerns: What should I expect at my first event? How accessible are our programs? Do we have programs for children? Do we have programs for seniors? What's the cost of participation?
These questions emerge from actual audience interactions (comments, DMs, emails) but also from stepping into the audience's perspective. Someone discovering CAF for the first time has different questions than a regular volunteer. Someone from a specific geographic region might ask different questions than someone from the broader community. These repeated questions represent content in high demand—they're asked frequently, so they're worth answering repeatedly in different formats.
By maintaining a questions list and converting frequently asked questions into content (blog posts, videos, social media graphics, reels), the organization creates content that serves audience needs rather than pushing information the organization thinks is important. This shifts social media from broadcast to service.
</aside>
<aside>
</aside>