An engineer's recognition for understanding the product marked the author’s transition into effective product counsel. By prioritizing curiosity, they engaged with the SaaS product deeply—experimenting, questioning, and shadowing customer support. This immersive approach revealed user frustrations and helped align legal advice with real needs. Moreover, the author learned essential technical concepts to communicate better with engineers, acknowledging that while expertise in coding isn’t necessary, grasping the basics can significantly enhance collaboration and trust, ultimately enabling the legal team to contribute more effectively to product development.
The first time an engineer told me, "You actually get it," I felt like I'd earned a badge of honor. That comment didn't come out of nowhere.
When I started working with a SaaS team, I insisted on using the product myself. I clicked every button, broke features intentionally, and asked why certain decisions were made.
I'm not a developer, but understanding the fundamentals helps me give practical advice. I can suggest feasible solutions and avoid asking for changes that would derail the team's efforts.
Spend time using the product and listening to its users. The insights you gain will make your advice sharper and more relevant.
Collection
[
|
...
]