惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
GbyAI
GbyAI
F
Fortinet All Blogs
Y
Y Combinator Blog
I
InfoQ
Microsoft Azure Blog
Microsoft Azure Blog
C
Cyber Attacks, Cyber Crime and Cyber Security
Vercel News
Vercel News
T
The Blog of Author Tim Ferriss
P
Proofpoint News Feed
S
Schneier on Security
NISL@THU
NISL@THU
The Hacker News
The Hacker News
Simon Willison's Weblog
Simon Willison's Weblog
The GitHub Blog
The GitHub Blog
MyScale Blog
MyScale Blog
Cisco Talos Blog
Cisco Talos Blog
F
Full Disclosure
P
Palo Alto Networks Blog
T
The Exploit Database - CXSecurity.com
Know Your Adversary
Know Your Adversary
A
About on SuperTechFans
The Cloudflare Blog
T
Threat Research - Cisco Blogs
M
MIT News - Artificial intelligence
宝玉的分享
宝玉的分享
雷峰网
雷峰网
Hugging Face - Blog
Hugging Face - Blog
博客园 - 三生石上(FineUI控件)
D
DataBreaches.Net
Martin Fowler
Martin Fowler
H
Help Net Security
B
Blog RSS Feed
B
Blog
爱范儿
爱范儿
V
V2EX
I
Intezer
L
LangChain Blog
WordPress大学
WordPress大学
小众软件
小众软件
美团技术团队
Latest news
Latest news
H
Hackread – Cybersecurity News, Data Breaches, AI and More
T
Tor Project blog
L
Lohrmann on Cybersecurity
Cyberwarzone
Cyberwarzone
Last Week in AI
Last Week in AI
Project Zero
Project Zero
C
Cybersecurity and Infrastructure Security Agency CISA
V
Visual Studio Blog

Buttondown's blog

Email could have been X.400 times better The physicists who convinced Fermilab to send Brazil's emails Better in-app previews Analytics 3.0 Subscriber ID variables Comments! Send latest premium action Automation filtering Free API subscribers Surveys in automations Reply to replies Labels for RSS feeds How Jeremy Singer-Vine curates curious datasets for readers 2023 (and what's next) Email vs web content Sort by engagement Better gift subscriptions How Andy Dehnart built a career reviewing television New email template Email-based automations Opt-in reply tracking Automatic alt text More social network integrations Sort by metadata Overlarge image warnings Automation tag actions Pause emails mid-flight Search tags and automations Gift via automations Subscriber-driving emails Programmatic webhooks Email page views Tag statistics Discord webhook formatting Automatic subscriber cleanup RSS subscriber count Weekly subscriber reports More list columns Customizable list views How Max Voltar turned a side gig into a trusted keyboard resource How Nick Disabato runs two newsletters from one design consultancy Made-for-you share images Automation improvements End-of-email surveys Filter by date Survey-triggered automations More automation functionality New webhooks How France Insider built a news service with paid subscribers Email as primary key How John Willshire unites two businesses in one newsletter Confirmation reminders Email churned subscribers Email-to-draft Subscriber metadata columns ChatGPT integration Faster web archives Referral program Better search results TikTok embeds Subscriber timeline Spotify embeds Improved RSS-to-email Subscribe page OG image New analytics page Google Tag Manager Even more subscriber types Integrating Duda with Buttondown Linktree integration guide Advanced and enterprise plans Framer integration guide API requests page Team collaboration In-email surveys Better CSS settings Better RSS automation fetching! Editor toolbar improvements Smart filters Faster emails page RSS automations Faster email analytics Zapier error codes Image accessibility checks Tags vs newsletters OG image picker Image editor improvements API bulk actions Improved OpenAPI spec Mastodon support Better subscriber filtering Better subscriber validation Hotkey support! Programmatic access to analytics Stronger bulk actions Faster archive page Custom canonical URLs Email slug and metadata Improved writing interface Generating a Typescript router in Django Filter emails by source
How we interview customers at Buttondown
nickd · 2025-12-17 · via Buttondown's blog

As Buttondown has grown, we’ve experienced many of the typical growing pains that you’d come to expect. In particular, new customers may not fit our original customer profile, which was, for a long time, other techies like us who cared about independent software and wanted a tool that did one thing well.

If that doesn’t describe you, fair, and we’d like to figure out who you all really are and what you need. That’s where interviewing comes in.

We don’t know our customers

Admitting we don’t know our customers is a bit of a risk. You may view it as a red flag: why support us if we’re clueless about it?

But in reality, no business truly knows their customer. We think it’s a strength for us to admit that we don’t know our customers. So many businesses view their customers as an “unknown unknown”, and they succeed based on luck or guesswork.

We know we can do better. By learning what drives you, we can build the best Buttondown for everyone.

Every single customer comes to Buttondown with their own hopes & motivations. Some of them have never started a newsletter before. Others have used a spreadsheet for years and want something a little more fit for purpose. No matter your perspective, we want to know it and adapt to it.

How we interview

Every month or so, we gather a list of Buttondown users that fits a specific theme. One month we might interview veterans & power users; another month, we might ask new customers what’s holding them back from onboarding. We get a list of emails and ask them if they might have time for a half-hour call. We offer a gift card for their time, because we need to provide some form of incentive.

What we ask on that call depends on who we know we’re talking to, and what direction we find the conversation going in. We can do our best to narrow down the criteria by which we recruit new people to talk to, but at the end of the day we really have no idea who’s going to show up on the other end of the call.

As for how to guide the interview, the unfortunate answer is to spend 20 years interviewing customers before you’re asked to do it for Buttondown. Interviewing only works when you’re experienced enough to interview people specifically for design insights. It’s not enough to ask what’s broken, or what pains they felt before coming in the door. You need to listen & reflect back what the participant is saying, because you never know what will come through.

Some big things I find myself doing are:

  • Create immediate familiarity & comfort. I tell all participants that we’re looking specifically for feedback that helps us grow as a business, and that I have a direct line to the CEO (true) and they cannot hurt my feelings (false, but it gets a laugh).
  • Be actively listening to the customer’s response in order to guide your next question. “You said X there. Can you expand on that?” is a classic.
  • Create enough silence that the customer keeps talking. That’s often where the truth comes out.
  • Provide space at the end for them to ramble free-form. Every time you ask if there’s anything else they’d like to add, they say “oh, no…” and then add five things.

But the real answer is to practice by interviewing people often.

Making sense of it

I take handwritten notes on every call. Then I record & transcribe every call, and then I write up summaries of my notes. At the end of the summary, I write up some takeaways and fill our bug tracker with projects & bugs to fix. We discuss as a team, and we do it all again.

We’ll never fully understand our customers, but through interviewing we can understand more & more, and learn how to make a Buttondown that works for everyone.