Ready to put scrappy feedback gathering into practice? Start a free ProdPad trial and centralize every scrap of input in minutes<\/p>\n <\/div>\n
Here\u2019s the thing most people miss: this scrappy approach isn\u2019t only useful for two founders in a cafe trying to find product market fit<\/a>. It\u2019s just as essential for big, well-resourced companies. In fact, the bigger the company, the more likely it is that the early-stage feedback muscle has atrophied. Teams get lost in dashboards, surveys, and process. Everyone assumes someone else is talking to customers. And before you know it, you\u2019re making product decisions in a vacuum.<\/p>\n\n\n\n That\u2019s why I argue that scrappy feedback gathering is not just an early-stage survival tactic. It\u2019s a discipline that every product team, no matter the size of their company, needs to embrace.<\/strong><\/p>\n\n\n\n Early on, scrappiness is baked into survival. If you don\u2019t get customer feedback, you fail. But in larger companies, the danger is subtler. Everyone has a role, a process, and a job description. \u201cStay in your lane\u201d becomes the norm. And that often means no one is responsible for doing the unglamorous but vital work of just picking up the phone or jumping into a Slack channel to ask a customer, \u201cHow\u2019s this really working for you?\u201d<\/p>\n\n\n\n The irony is that big companies have more users and more data than startups could dream of. But more data does not mean more insight. Data tells you what<\/em> is happening. Only scrappy feedback tells you why<\/em>.<\/p>\n\n\n\n Think about how many product flops you\u2019ve seen from giant companies<\/a>. They had the resources. They had the metrics. What they lacked was the scrappy truth-finding that would have revealed customer indifference or confusion before launch.<\/p>\n\n\n\n So whether you\u2019re at a startup fighting for traction or at an enterprise trying to stay relevant, the principle is the same: get out of the building<\/strong>. As Steve Blank put it<\/a>, there are no facts inside your building. There are only opinions. The facts are out there with your customers.<\/p>\n\n\n\n Scrappiness is not chaos. It\u2019s deliberate, lightweight, and customer-focused. Here are some practical ways to put it into action, whether you\u2019re two people in a garage or a product team at a global company.<\/p>\n\n\n\n Don\u2019t wait for feedback to trickle in. Reach out. Cold email prospects, send quick polls in Slack groups, or drop into LinkedIn communities where your users hang out. In my role here at ProdPad, I\u2019ve reached out to product managers on Twitter and LinkedIn and simply asked, \u201cWhat\u2019s frustrating you about your roadmap process?\u201d Those short exchanges gave me insights that shaped features years down the line.<\/p>\n\n\n\n For larger teams, this might mean encouraging PMs to shadow support calls, join a sales demo, or run an informal chat with a handful of customers every month. It\u2019s not about launching a research study. It\u2019s about staying curious.<\/p>\n\n\n Watch our on\u2011demand session on how to set up a lightweight product idea intake process that won’t drown you.<\/p>\n <\/div>\n Startups are famous for this, but big companies should do it too. Airbnb\u2019s founders once flew to New York to photograph listings for their early hosts. That move doubled their revenue almost overnight<\/a>. Scrappy, unscalable work pays dividends because it gives you raw exposure to your users.<\/p>\n\n\n\n They weren\u2019t the only ones. Dropbox validated its product before it even existed<\/a> with nothing more than a demo video. Drew Houston put together a simple screencast showing how Dropbox would<\/em> work, then posted it on Hacker News. The blunt comments, critiques, and demands from early adopters weren\u2019t always pretty, but they confirmed the idea was worth building.<\/p>\n\n\n Zappos did something similar in e-commerce. Nick Swinmurn tested whether people would buy shoes online<\/a> by posting photos of shoes from local stores, then personally going back to purchase them at retail whenever someone placed an order. Customers gave very direct feedback about trust, shipping speed, and the buying experience. That uncomfortable early-stage feedback highlighted the barriers Zappos would need to overcome to scale.<\/p>\n\n\n\n Slack\u2019s early days also hinged on uncomfortable truth-seeking. Originally built as an internal tool, Stewart Butterfield handed it out to other startups and begged for brutal honesty<\/a>. Instead of praise, he wanted to know what didn\u2019t<\/em> work. That feedback\u2014complaints about onboarding, confusion over channels, quirks in notifications\u2014was what shaped Slack into a product people loved.<\/p>\n\n\n\n The pattern is clear: companies that grow don\u2019t just embrace praise. They deliberately invite critique. That\u2019s what doing things that don\u2019t scale really means: being willing to ask for the raw truth before you\u2019re ready for it.<\/p>\n\n\n\n In a big org, that could mean personally onboarding the next five enterprise customers instead of delegating it. Or sitting down to read every comment from a survey rather than waiting for a report. Scrappy means hands-on.<\/p>\n\n\n\n If you have users, embed feedback opportunities everywhere. An in-app widget, a feedback link in your email signature, or even a pinned message in your customer Slack channel. ProdPad has tools for this because I learned the hard way that if you make feedback hard to give, you won\u2019t get it<\/a>. Lower the barrier and you\u2019ll be surprised how often people will tell you what you need to know.<\/p>\n\n\n\n Not every conversation has to be a formal 45-minute interview. Sometimes the gold comes from five minutes at the end of a support call, or a quick DM after a webinar: \u201cWhat did you think of this?\u201d In 2025, you have more channels than ever. Use them. A Discord server, a LinkedIn poll, a one-question Typeform. The smaller the ask, the easier it is for people to respond.<\/p>\n\n\n\n Buffer is a classic example here. Joel Gascoigne validated his idea with a landing page<\/a>. Visitors who clicked \u201cPlans & Pricing\u201d saw a message that said, \u201cWe\u2019re not quite ready yet. Leave your email.\u201d That tiny test, essentially a micro feedback experiment, gave him unfiltered responses and a list of people eager to try the product.<\/p>\n\n\n\n Glossier followed a similar path, but with community. Founder Emily Weiss didn\u2019t start with a product. She started with Into the Gloss<\/em>, a beauty blog where she asked readers blunt questions about their routines and frustrations<\/a>. Sometimes the answers were contradictory. Sometimes they were critical of existing beauty brands. But it was that messy, uncomfortable early-stage feedback that became the foundation for Glossier\u2019s brand: transparent, relatable, and community-driven.<\/p>\n\n\n\n These examples show that micro feedback doesn\u2019t have to be polished or expensive. Sometimes a simple landing page, blog, or direct question surfaces more insight than a year\u2019s worth of surveys.<\/p>\n\n\n\n Collecting feedback is only step one. If you don\u2019t capture and process it, you\u2019ll just have a pile of sticky notes that no one ever looks at again.<\/p>\n\n\n\n Here\u2019s how to make it useful:<\/p>\n\n\n\n See an expert turn raw feedback into themes and decisions.<\/p>\n <\/div>\n Why scrappy feedback matters at scale<\/h2>\n\n\n\n
Scrappy tactics to gather early-stage feedback<\/h2>\n\n\n\n
Be proactive, not reactive<\/h3>\n\n\n\n
Do things that don\u2019t scale<\/h3>\n\n\n\n
![\"Dropbox\u2019s](\"https:\/\/www.prodpad.com\/wp-content\/uploads\/2025\/08\/Dropbox-Original-MVP-Explainer-Video-0-50-screenshot.png\")
Be everywhere your users are<\/h3>\n\n\n\n
Try \u201cmicro feedback\u201d<\/h3>\n\n\n\n
Making early-stage feedback actionable<\/h2>\n\n\n\n
\n
![\"The](\"https:\/\/www.prodpad.com\/wp-content\/uploads\/2023\/07\/ProdPad-Prioritization-Framework-eBook-1024x240.png\")
<\/a><\/figure>\n\n\n\n