We’d love to help. Head over to our repo and create an issue, and we’ll reply back when we discuss it on the show. DM us if you’d like to ask a question anonymously.
We’ll be tweeting new episodes, polls, questions, and show updates. Follow us and say hi!
This week, we talk about the tension between building what customers explicitly ask for versus building towards a team’s internal vision. In The Sidebar, we talk about the lack of public software critique: Why isn’t there an MKBHD equivalent for software design?
Around is a better way to video call. It’s designed specifically to make it easier to gather small groups together to collaborate in real time, without all the distracting and frustrating interfaces that comes with most video chat software. We love the small floating heads and emphasis on making it easy to work alongside the video call, rather than constantly having to app switch.
You can get started for free by signing up at Around.co!
The Sidebar is an exclusive weekly segment for our Patreon supporters. You can subscribe starting at $1 per month for access to bonus content going forward! Sign up at patreon.com/designdetails.
Curious to hear both of your thoughts on the decision making process of building features that you’re users explicitly ask for (i.e. edit button on Twitter) versus features that your team, whether it’s Design, Product, Engineering, feels are the right things to build based on the company’s priorities.
User research plays a large part, however, it’s something I’ve been struggling with lately. Especially as I’m working on new features that the company’s prioritizing, which is another process I’ve been removed from so far.