It is becoming increasingly challenging for product development leaders to effectively lead as workplace demands continue to increase. The rate of change in technology, society, and business places immense pressure on leaders to ensure their groups move in the direction of their goals. What might have worked in the past no longer works.
Organizational surveys show that firms struggle with leadership. Product development leaders routinely complain of burnout and stress while their teams members complain of workplace dissatisfaction, resulting in organizational underperformance.
The lack of evidence-based leadership literature for product development leaders means that many leaders are left to figure things out with little guidance. They do not have a reliable resource that they can refer to when they face leadership challenges and, as a result, struggle during times of crisis and change. This book addresses this challenge by providing a theory-informed set of techniques for product development leaders. Becoming a Leader in Product Development provides an evidence-base set of practices for product development leaders. In doing so, it explores what leadership is and the leader's role in the leadership process, the impact of national culture and organizational culture on the leadership process, and the need for product development leaders to practice adaptive and servant leadership, followership, and self-care. The underlying theories for each topic are reviewed and then brought to life through stories and examples.
I became a leader quite unexpectedly. I vividly recall diving into numerous leadership books and gleaning insights from their stories. While these books sustained me for years, I eventually realized that some contained elements of survivorship bias. Too often, I found myself frustrated when outcomes didn't align with my expectations, and I couldn't pinpoint the reasons.
This book stands apart. It offers a comprehensive perspective on leadership, merging both theory and practical experience. Drawing from various theories, it presents them in a digestible manner. The book elucidates why certain strategies might not succeed. After reading it, I've gained a deeper understanding of past challenges.
Eb's personal anecdotes deeply resonated with me. I once advocated for Agile without fully understanding its nuanced assumptions. I've led teams in several countries without fully recognizing why a certain approach might not be universally effective. If you're in a leadership role now, I wholeheartedly recommend this book. In fact, it's the only leadership book I've recommended to my clients this year. It has profoundly influenced my perspective. The last two chapters underscore areas I had often missed in my career—don't miss them!