It’s one thing to fix a bug; it’s another to watch someone’s face fall when your product makes their job harder. Your developers aren’t ignoring user frustration, they just rarely get to see it firsthand. Those moments of empathy can transform your team.
Feature specs and design mockups can describe what to build, but they can’t capture what it feels like for a customer to click the wrong button, get confused, or give up. When teams watch real users struggle, those technical “tickets” turn back into human problems that everyone feels compelled to solve.
At Uptech Studio, we’ve seen this shift transform projects. When our team observed teachers using early prototypes for SDES’s educational software, we realized that what made sense in a design review didn’t work in a real classroom. Similarly, while developing Prism Labs’ bodymapping SDK, seeing users stumble through scans helped the whole team—design, engineering, and product—collaborate on simpler, smarter fixes that dramatically improved success rates.
Regular user observation builds empathy and alignment. Developers start suggesting simpler solutions. Designers prioritize clarity over complexity. Product focuses on solving real pain points rather than adding more features. The result? A team that communicates better, builds faster, and creates products that actually work for the people using them.
Our partner KQED uses AppFollow to push all of our app ratings into a Slack channel so the entire team can immediately see them. It’s a good reminder that getting user feedback should be an “all of the above” strategy.
While qualitative observations are powerful, that doesn't mean you shouldn't also use tools that help manage and automate gathering user feedback.
Releasing software products (or just adding new features) without a regular habit of looking at data is like getting in a car, starting to drive and never looking at the road signs. Even if you have a destination in mind, how do you know when (or if) you'll ever get there? In this brown bag, we look at a couple of real-world examples of how we've worked with partners to answer critical questions with data.
At Uptech Studio, we regularly suggest simpler approaches that get you to the same outcome faster and cheaper—not because any single person had the perfect answer, but because our team collaborates from a shared concern and understanding of the user’s context. Looking for a partner who is deeply engaged with trying to understand your users? Reach out!
Thanks,
Matt New
Partner, Uptech Studio
