Experienced tech entrepreneur & CTO with a 15 year+ track record of working in the CRM analytics industry. Skilled in building and leading engineering & data science teams, statistical modeling, machine learning and the Apache Spark/Python stack. Engineering professional with a Doctor of Philosophy (Ph.D.) focused in Marketing & Statistics from The University of Kiel.

My Mentoring Topics

  • Founding, funding and growing B2B-Software startups
  • Building and scaling teams from 0-50 people
  • Leading and recruiting people in knowlege-based industries where culture, purpose and intrisic motivation is all that matters and people demand is 10x the supply.
R.
3.May 2023

I recently had a mentoring session with Dennis Proppe, and it was a phenomenal experience! Dennis is a highly knowledgeable tech entrepreneur and CTO with a wealth of experience in the analytics industry. His extensive background in building and leading engineering & data science teams, as well as his expertise in statistical modeling and machine learning, was evident throughout our conversation. Dennis' experience in founding, funding, and growing B2B-Software startups provided invaluable insights that have significantly impacted my professional journey. His ability to break down complex concepts into digestible pieces made it easy to understand and apply his advice to my own situation. Additionally, Dennis shared his expertise in building and scaling engineering teams, which was extremely helpful in guiding me through the hiring process. His emphasis on the importance of culture, purpose, and intrinsic motivation in knowledge-based industries resonated deeply with me and offered a fresh perspective on recruitment and leadership. Dennis is not only an expert in his field but also a genuinely caring and supportive mentor. He took the time to listen to my concerns and provided thoughtful, personalized advice that went above and beyond my expectations. His ability to communicate complex ideas clearly and effectively made our session both engaging and highly informative. I highly recommend Dennis Proppe as a mentor for anyone looking to grow professionally and gain valuable insights into the world of B2B-Software startups, engineering team management, and leadership in knowledge-based industries. Dennis' experience, expertise, and supportive nature make him a top-tier mentor who can help take your career to the next level.

A.
31.October 2022

Thank you so much for that inspiring session. Now I got more confidence in our decisions and the way we choose.

A.
2.August 2022

It was really nice to talk with Dennis, he gave me a lot of important feedbacks and ideas. Definitely recommend!

A.
29.March 2022

Dennis was really helpful, being able to break down the many questions I had into the core issues to tackle and providing me with actionable suggestions for next steps. Will definitely reach back out to continue learning from his expertise when the time comes.

M.
11.February 2022

The session with Dennis was incredible helpful. I felt from the beginning, that I'm not only talking with an experienced founder that understands me and my goals, but also really cares about helping me. During our session, Dennis provided very helpful insights and ideas, that will save me many months if not years. In particular his founder, technical, and product expertise has been very helpful. 10 / 10 - recommend highly talking with Dennis. @Dennis - Thank you again for your time.

M.
28.September 2021

Dennis is a great Mentor In terms of support and validating the ideas! I really enjoyed talking with him and for sure I will follow up with him in the next steps! He also offered me some useful resources and points to keep in mind. Thank you very much for being a good mentor:)

Radical Candor: Fully Revised & Updated Edition - Be a Kick-Ass Boss Without Losing Your Humanity
Kim Scott

Key Facts or Insights from "Radical Candor" Radical Candor is a management philosophy that advocates for direct, clear, and empathetic communication between managers and their teams. It is built on two fundamental principles: "Care Personally" and "Challenge Directly". The book provides a comprehensive framework that helps managers to improve their leadership skills and promote a healthy workplace culture. Scott breaks down management styles into four quadrants: Radical Candor, Obnoxious Aggression, Manipulative Insincerity, and Ruinous Empathy. "Radical Candor" advises managers to have difficult conversations with their employees, offering constructive criticism without being insensitive. The book emphasizes the importance of building strong relationships with team members to promote trust and openness. Scott also highlights the significance of listening to feedback from employees and using it to improve management practices. She suggests that managers should delegate tasks effectively to promote growth and development in their team members. Scott provides practical tools and techniques to implement the principles of Radical Candor in real-life situations. The book is based on Scott's extensive experience in leadership roles at various renowned tech companies, including Google and Apple. It calls for managers to maintain their humanity while being effective leaders, hence the subtitle: "Be a Kick-Ass Boss Without Losing Your Humanity". In-Depth Summary and Analysis of "Radical Candor" "Radical Candor" by Kim Scott is a revolutionary guide that offers valuable insights into effective leadership and management. It provides a comprehensive framework based on two fundamental principles: "Care Personally" and "Challenge Directly", both of which are crucial for building strong relationships, promoting a healthy workplace culture, and improving overall team performance. In her book, Scott categorizes management styles into four quadrants: Radical Candor, Obnoxious Aggression, Manipulative Insincerity, and Ruinous Empathy. Radical Candor is the most desirable of the four as it incorporates both caring personally and challenging directly. It encourages managers to be honest and direct with their feedback, while also showing genuine care for their team members. On the other hand, Obnoxious Aggression, Manipulative Insincerity, and Ruinous Empathy are all flawed management practices that could potentially hamper team morale and productivity. Radical Candor emphasizes the importance of having difficult conversations with employees. It encourages managers to provide constructive criticism without being insensitive or harsh. Such feedback, when delivered appropriately, can help employees improve their performance and contribute more effectively to the team's goals. Building strong relationships with team members is another significant aspect highlighted in the book. When managers care personally about their employees, it fosters a sense of trust and openness within the team. This, in turn, promotes better communication, collaboration, and overall team dynamics. Listening to feedback from employees is another crucial aspect discussed in the book. Scott emphasizes that managers should not only provide feedback but also be open to receiving it. This two-way communication allows for continual improvement and adaptation in management practices. The book also offers insights into effective delegation, advising managers to delegate tasks that promote growth and development in their team members. This not only helps to build skills within the team but also shows employees that their managers have confidence in their abilities. Scott provides practical tools and techniques to implement Radical Candor principles in real-life situations. These include methods for giving and receiving feedback, holding effective meetings, and resolving conflicts, among others. The concepts and ideas in "Radical Candor" are deeply rooted in Scott's extensive experience in leadership roles at renowned tech companies, including Google and Apple. Her practical examples and anecdotal evidence add credibility to her arguments and make the book a valuable resource for managers at all levels. Finally, a key message from the book is for managers to maintain their humanity while being effective leaders. It's possible to be a "kick-ass boss" without losing your empathy, compassion, and respect for others. This balance is the essence of Radical Candor and a cornerstone of effective leadership.

View
Inspired
Marty Cagan

Key Insights from "Inspired" The importance of deep customer understanding in product development. The concept of Risks and Opportunity Assessment Process (ROAD) in product planning. The role of Product Discovery in creating successful products. The value of using prototypes in product design and testing. The significance of Product Manager in an organization. The application of Agile principles in product development. The difference between product delivery and product discovery. How to create a compelling product vision and strategy. The importance of validated learning in the product development process. Understanding the role of technology and design in product development. The importance of strong leadership in fostering a successful product team. In-depth Analysis of "Inspired" "Inspired" is a seminal work by Marty Cagan that provides a comprehensive guide on how to create technology products customers love. It is based on Cagan's extensive experience in the tech industry, having worked with some of the most successful companies in Silicon Valley. The first key insight from the book is the importance of deep customer understanding. Cagan emphasizes that successful product development starts with understanding customers' needs, desires, and problems. This involves conducting user research, customer interviews, and surveys, among other methods. This approach aligns with the principles of human-centered design, a design philosophy that focuses on understanding and addressing the needs and experiences of users. Cagan introduces the concept of Risks and Opportunity Assessment Process (ROAD), a strategic tool for product planning. It helps businesses identify potential risks and opportunities in their product development process and make informed decisions. Product Discovery is another essential concept in the book. It involves exploring and validating product ideas before development begins. Cagan suggests using prototypes during this stage to visualize and test product concepts. This aligns with the Lean Startup approach, which values quick experimentation and validated learning. The author also emphasizes the role of the Product Manager in an organization. According to Cagan, Product Managers should be "product CEOs," owning the product vision, strategy, and roadmap. They should lead cross-functional teams, work closely with customers, and make crucial product decisions. Cagan's approach to product development is rooted in Agile principles. He advocates for iterative development, continuous improvement, and close collaboration between development teams and stakeholders. He also distinguishes between product delivery and product discovery, arguing that while Agile methods are excellent for delivery, different methods are needed for discovery. The author also provides guidance on creating a compelling product vision and strategy. A strong vision and strategy can guide decision-making, motivate the team, and communicate the product's value proposition to stakeholders. Cagan underscores the importance of validated learning, a concept borrowed from Lean Startup methodology. This involves testing assumptions and learning from customers' feedback to improve the product iteratively. Moreover, Cagan discusses the role of technology and design in product development. He emphasizes the need for product teams to leverage emerging technologies and prioritize user experience in their product design. Lastly, Cagan stresses the importance of strong leadership in fostering a successful product team. He believes that leaders should empower their teams, cultivate a culture of innovation, and ensure alignment with the organization's vision and strategy. In conclusion, "Inspired" is a comprehensive guide that offers practical insights and strategies on product development. It embodies a deep understanding of the importance of the customer, emphasizes the value of discovery and validation, and promotes a culture of innovation and agile principles. All these elements are crucial in the rapidly changing world of technology product development.

View
Become an Effective Software Engineering Manager
Dr. James Stanier

Key Insights from "Become an Effective Software Engineering Manager" Transitioning from individual contributor to manager: The book provides a comprehensive guideline on how software engineers can transition into effective management roles, emphasizing the need for a shift in mindset and skillset. Managerial responsibilities: The book outlines the various roles a manager plays in a software engineering team, which includes project management, team building, conflict resolution, and strategic planning. Effective communication: The importance of clear, concise, and effective communication in management is stressed throughout the book. Managing team dynamics: The book provides insights into understanding and managing the complexities of team dynamics in a software engineering environment. Performance management: The book provides a framework for setting expectations, measuring performance, and providing feedback to team members. Leadership development: The book emphasizes the importance of continuous learning, self-reflection, and development for a software engineering manager. Career growth: The book provides guidance on how to navigate career growth in management within the technology industry, including advice on networking, mentorship, and personal branding. Building a positive work culture: The book encourages engineering managers to foster a positive work environment that promotes diversity, inclusion, and collaboration. Implementing Agile methodologies: The book discusses the application of Agile practices in managing software engineering teams and projects. Strategic decision making: The book provides tools and techniques for strategic decision making, including risk assessment, prioritization, and long-term planning. Understanding and navigating organizational structures: The book offers insights into navigating and understanding the complexities of organizational structures in a software engineering context. Detailed Summary and Analysis "Become an Effective Software Engineering Manager" by Dr. James Stanier is a comprehensive guide for software engineers aiming to transition into managerial roles. The book provides a clear path for this transition, emphasizing the need for a significant shift in mindset and skillset. The author argues that the technical skills that make one a good software engineer do not necessarily translate into effective management. This is a significant insight that resonates with my experience in academia, where I have seen many technically proficient individuals struggle with managing others. The book outlines the variety of roles a manager plays in a software engineering team. These roles include project manager, team builder, conflict mediator, and strategic planner. The author clearly defines these roles and provides practical advice on how to fulfill them effectively. This multi-faceted approach to management is a crucial aspect of modern software engineering management, where the role can no longer be reduced to simple project management. Effective communication is another key topic in the book, which I believe is fundamental to any managerial role. The author provides clear strategies for communicating with different stakeholders, including team members, senior management, and clients. He emphasizes the importance of clarity, brevity, and empathy in communication, which aligns with my experience in managing academic teams. Another significant aspect of the book is its focus on managing team dynamics. The author provides valuable insights into understanding and managing the complexities of team dynamics in a software engineering environment. He discusses topics such as fostering collaboration, resolving conflicts, and managing performance. I find this section particularly useful as it aligns with the modern view of management as a role that facilitates team success rather than controlling individual tasks. The book also provides a comprehensive framework for performance management. The author discusses setting expectations, measuring performance, and providing feedback. These are crucial aspects of managing a software engineering team, where performance can often be quantified but should also include qualitative aspects such as teamwork and creativity. Dr. Stanier places a strong emphasis on leadership development, arguing that an effective software engineering manager must be committed to continuous learning and self-reflection. This aligns with my experience in academia, where the most effective leaders are those who are open to learning and adapting. The book also provides guidance on navigating career growth in management within the technology industry. The author discusses networking, mentorship, and personal branding, providing practical advice on how to advance in a managerial career. The author also encourages engineering managers to foster a positive work culture that promotes diversity, inclusion, and collaboration. This is a crucial aspect of modern management, and it aligns with my experience in academia, where a positive and inclusive culture can greatly enhance team performance and satisfaction. The application of Agile methodologies is another key topic in the book. The author discusses how Agile practices can be applied in managing software engineering teams and projects. This is a crucial aspect of modern software engineering management, as Agile methodologies have been shown to enhance productivity and satisfaction among software engineering teams. The book also provides tools and techniques for strategic decision making, including risk assessment, prioritization, and long-term planning. These tools can be invaluable for software engineering managers, who often need to make strategic decisions that can have significant impacts on their teams and projects. Finally, the book offers insights into navigating and understanding the complexities of organizational structures in a software engineering context. The author discusses different organizational structures and provides advice on how to navigate them effectively. This is a crucial aspect of management, as understanding the organizational context can greatly enhance a manager's effectiveness. In conclusion, "Become an Effective Software Engineering Manager" provides a comprehensive and practical guide for software engineers aiming to transition into managerial roles. The book covers a wide range of topics, from communication and team dynamics to performance management and strategic decision making. It provides valuable insights and practical advice, making it an invaluable resource for aspiring software engineering managers.

View
The Five Dysfunctions of a Team - A Leadership Fable
Patrick M. Lencioni

Key Facts and Insights: The fundamental premise of the book is that teams often fail due to five common dysfunctions, which are: Absence of Trust, Fear of Conflict, Lack of Commitment, Avoidance of Accountability, and Inattention to Results. The book uses a business fable approach to convey the message, following a fictional company and its new CEO who identifies and resolves these five dysfunctions. The first dysfunction, Absence of Trust, is rooted in the team members’ unwillingness to be vulnerable and open with each other. This leads to a lack of trust and a fear of making mistakes. The second dysfunction, Fear of Conflict, arises from the team's inability to engage in unfiltered, passionate debate about things that matter, leading to inferior decision-making. Lack of Commitment is the third dysfunction, where team members, due to lack of clarity or buy-in, fail to fully commit to decisions, causing ambiguity about direction and priorities. Next is the Avoidance of Accountability, where team members hesitate to call out peers on their actions and behaviors that can potentially harm the team. The final dysfunction is Inattention to Results, where team members put their individual needs (such as ego, career development, or recognition) above the collective goals of the team. Through the fable, Lencioni provides practical advice for overcoming these dysfunctions. He suggests building trust through vulnerability, encouraging constructive conflict, gaining commitment through clarity and buy-in, holding team members accountable, and focusing on collective results. The book is not just about identifying the dysfunctions but also provides a model and actionable steps to overcome these dysfunctions and build a cohesive and effective team. At the heart of the book lies the idea that success in any team is dependent on overcoming these dysfunctions and working together towards a common goal. An In-Depth Summary and Analysis: "The Five Dysfunctions of a Team - A Leadership Fable" by Patrick M. Lencioni is an insightful book that unveils the reasons why teams often fail and offers practical advice on how to overcome these issues. Lencioni uses a business fable, a unique approach that combines storytelling with business principles, to illustrate his points and make the book relatable and engaging. The first dysfunction, Absence of Trust, is linked to the unwillingness of team members to be vulnerable and open with each other. This lack of transparency creates a culture of fear, where team members are afraid to make mistakes or take risks. As a long-standing academic in this field, I've seen how this lack of trust can paralyze a team, stifling creativity and innovation. Overcoming this dysfunction requires creating a safe environment where individuals feel comfortable expressing their thoughts, ideas, and potential misgivings. The second dysfunction, Fear of Conflict, stems from the team's inability to engage in meaningful, passionate debate about things that matter. This fear of conflict often leads to artificial harmony, where team members pretend to agree even when they have differing opinions. This avoidance of conflict can result in poor decision-making, as not all perspectives are considered. I believe that constructive conflict is a crucial component of a high-performing team. Encouraging open, honest debate ensures that all viewpoints are heard and considered, leading to better, more informed decisions. Lack of Commitment is the third dysfunction, where team members don't fully commit to decisions due to lack of clarity or buy-in. This lack of commitment can lead to ambiguity about the team's direction and priorities. In my experience, clear communication and the inclusion of all team members in the decision-making process can help overcome this dysfunction. The fourth dysfunction, Avoidance of Accountability, occurs when team members hesitate to call out peers on their actions and behaviors that could potentially harm the team. This avoidance often stems from a desire to maintain personal relationships and avoid conflict. However, holding each other accountable is crucial for maintaining high standards and achieving the team's collective goals. The final dysfunction, Inattention to Results, happens when team members prioritize their individual needs above the collective goals of the team. This can lead to a lack of focus on the desired results and a failure to achieve the team's objectives. Focusing on collective results and rewarding team success rather than individual achievements can help overcome this dysfunction. In conclusion, "The Five Dysfunctions of a Team - A Leadership Fable" is an insightful book that provides practical advice on overcoming common team dysfunctions. It highlights the importance of trust, constructive conflict, commitment, accountability, and a focus on results in creating a successful team. As a professor with years of experience in this field, I can attest to the effectiveness of Lencioni's methodology in transforming dysfunctional teams into high-performing ones. This book is an essential read for anyone looking to build or improve their team.

View