I have a tendency to treat coming up with content ideas as a solo sport.
I’m used to sitting with my thoughts, combined with a post format I saw that I loved and want to recreate. And when I’m stuck, I scroll through my bookmarks with hundreds of post ideas for something to remix.
I’ve been fortunate that that system works time and time again for me — but it’s not the only way to create.
So, a few weeks ago, instead of forcing it, I tried something different that I should be doing way more often: I asked my community.
Not in a vague, “what should I post about?” way — but with a specific, open-ended question. And what followed was a flood of thoughtful, deeply relatable replies — the kind that made me realize that the best content ideas aren’t buried in your own brain. They’re hiding in your comment section.
In this post, I’ll share how I ran this mini experiment, the types of responses it sparked, and how I turned those replies into content that resonated — a self-sustaining flywheel. I’ll also break down how you can try it — whether you’re running a brand account, building your personal presence, or just feeling stuck on what to post next.
The experiment: Building content with, not just for, my communityI framed the whole thing as a lightweight experiment — one post, one question, one goal: to see what would happen if I handed the mic over to my audience.
In many ways, it functioned like a mini AMA — an open door to ask anything without the pressure of needing the “perfect” question. But it also went beyond that. This wasn’t just a Q&A — it became a content loop. The questions turned into posts, the posts sparked new conversations, and suddenly, my content strategy was rooted in real-time dialogue with the people I’m trying to reach.
It was an honest attempt to flip the script: to treat the comment section as the discovery, not the aftermath of a post.
Here’s what I posted:
“What’s a challenge, moment, or question you’ve faced related to personal branding or career growth that you’d love to see me unpack in a post?”
The most important factor in the success of this post is that it wasn’t me fishing for easy engagement. And it worked.
I heard from freelancers, strategists, job seekers, creators, and community managers — each with their own angle on what they were navigating. Some wanted help simplifying how they explain what they do. Others asked about balancing personal and company brands, or how to know when it’s time to pivot your content focus.
And somehow, every response sparked fresh ideas.
That was the moment it clicked: When you ask a question rooted in your content pillars, you don’t just get random replies — you get ready-made posts, straight from the people you’re trying to reach.
What my community askedThe responses covered more ground than I expected. In fact, although I was going to post more questions, I have so much content that I’m covered for several weeks from now, so I ended up only doing the one post.
Some questions were tactical:
Others were more personal:
Nothing felt too out there for me to answer — even the question about which came first? The chicken or the egg? I pick chicken every time by the way.
It reminded me that your audience’s questions are rarely brand new — but they’re new challenges to them. And your perspective is new to them too. You don’t need to have an expert reply ready. You just need to listen, then share what you’ve figured out so far.
In many ways, the responses allowed me to write about things I might’ve otherwise skipped — not because they weren’t important, but because I thought they were too obvious. Turns out, “obvious” is often exactly what people need.
How I turned responses into postsThe real magic of this experiment wasn’t just in the replies — it was in what came next.
Every comment was a spark. Some turned into full reflections. Others became frameworks or jumping-off points for conversations I’d been meaning to have anyway. The best part? I didn’t have to guess if they’d resonate. I already knew they struck a chord — because someone asked for them.
Here’s how a few responses became real posts:
Each post also credited the person (or people) who asked, creating a loop: someone felt seen, I created something useful, and others chimed in with even more to add.
When I looked back, I realized this format works specifically because it’s collaborative. It helps me write posts that don’t just reflect my own thinking — they reflect what people actually want to explore through my experience. And that gets them to engage.
Best practices for turning community insights into contentYou don’t need a big audience or a viral post to try this. You just need a clear theme and a willingness to listen.
Here’s a simple way to crowdsource content ideas from your own community:
Even if you don’t turn a comment into content immediately, save it. I keep a backlog of questions and post ideas in Buffer, tagged by pillar and format, so I always have something to come back to when inspiration runs low.
This experiment worked well because it started with a clear question and a willing community — but it’s not the only way to find ideas rooted in what your audience cares about.
If you’re looking to expand beyond your own comment section, here are a few other ways to surface content opportunities through community conversations:
This whole experiment started as a way to get unstuck. I wanted new ideas. What I got was a reminder: Content creation doesn’t have to be solitary.
The people who follow your work often have the exact questions you’re equipped to answer — you just have to invite them into the process.
Since trying this approach, I’ve been thinking of content less as a broadcast and more as a dialogue. The post is the first line. The comments are the second. What you create next is the response.
It’s not about handing over your content strategy — it’s about expanding the room where ideas happen.
So next time you feel stuck, try this:
Try it yourself — post your own community-sourced question this week and tag us @buffer if you do. We’d love to see what your audience comes up with.
All Rights Reserved. Copyright , Central Coast Communications, Inc.