For a long time, the industry treated design like a relay race. The Product Manager (PM) would run the first leg, defining the “requirements.” They’d then pass the baton to the UI Designer, who would make those requirements look beautiful in Figma. Finally, the baton went to the Engineer, who would try to make those pixels move on a screen. The problem? Information gets lost at every handoff. By the time the designer gets the baton, they are often solving for the  solution  rather than the  problem . Product Thinking  is about breaking the relay race. It’s about being in the room when the requirements are being born. It’s about realizing that if you don’t understand why a feature exists, you can’t possibly design the right interface for it. You might pick the perfect typeface, but you’re essentially writing a beautiful poem in a language the user doesn’t speak.…