The Secret to Building Incredible Products that People Love
Great chefs write great code. Why? Because they taste before they serve. They're testing flavors and textures at every opportunity, constantly slipping into the shoes of their customers and improving their product. But I didn't realize until embarrassingly recently that “customer” can be a very loose term. In fact, so can “product”. Of course, obsessing over the customer experience will help you design a better UI for your website. But that same customer obsession can be applied to your team’s onboarding process, code reviews, GraphQL schema, and much more. Everything you create that gets consumed fits this formula. Product = function ➡️ customer = caller. Product = scrum ticket ➡️ customer = engineer. Product = analytics dashboard ➡️ customer = on-call support. Take a slide deck, for example. What ingredients would tailor it to your customer's liking? Will they be wolfing it down hastily between meetings, or consuming it slowly like a three-course meal? Should it be presented elegantly like a filet on white tablecloth, or casually like a burger through the car window? At it's core, this metaphor tells a heartwarming story: the lifeblood of creation is empathy. Taste the food before you put it on the plate. And if your tastebuds can't be trusted, find a good sous chef! P.S. This simple trick will get you at least 50% of the way toward building something truly exceptional. The other 50% requires incorporating feedback from – you guessed it – your actual customers. 😉 Which dish will you be taste testing on this week's menu? Comment below so we can all learn together. 👇 #softwareengineering #programming #coding