I’ve thought about applying product thinking to non-product team work for many years, even during my time as a lawyer.
In his Harvard Business Review article Bring Product Thinking to Non-Product Teams, John Gothelf articulates the approach.
For example, instead of HR viewing its ultimate goal as launching the system, Gothelf suggests that the team think about the ultimate customer outcome and test and iterate to ensure customer success.
I’ve worked on developing digital products for the past 15 years. At a high level, I’ve come to define product thinking as follows:
• Defining the ultimate customer and goal.
• Defining the the tactics that advance the project to the ultimate goal.
• Measuring continually to test success or failure.
• Ongoing communication and iteration to ensure alignment.
As an attorney previously, I employed product thinking, instinctively, with legal arguments and client advice. I’d ask:
• What is the conclusion (or goal)?
• What are the logical steps (or tactics) necessary to reach the conclusion?
• What is the optimal way to construct and lay out assertions in support of the conclusion?
• How do facts and law come together (like customer input and data) to aid in iteration?
How does an attorney make the transition from law to product development?… Read the rest and share