Culture Development

Delivering Impactful Product Changes

Product people often overcomplicate things, struggle to justify decisions, and focus on incremental improvements that don't drive revenue. Smart product people know how to make tradeoffs, involve customers for validation, and understand the competitive landscape. When considering “small,” incremental features, it is important to ask if they will make a difference and if they will eliminate a major pain point. Impactful features may not be created in a single product cycle and customers may not know what they want until it is shown to them. Taking risks to achieve goals requires courage and it is important to not overthink or over-complicate product roadmaps. Little details should not be dismissed as they can make a big difference.

Becoming the Type of Leader That You Would Want to Follow

This article is about the lessons learned by an introverted IT professional who was unexpectedly placed in a leadership role. Through research, mentors, and data-monitoring software, the individual was able to learn how to build a team, manage people, and resolve conflicts. They also learned the importance of transparency and the value of reading industry blogs for problem-solving.

Ten quotes from Adam Grant relevant while dealing with layoff

This passage discusses the importance of knowing when to abandon treasured tools and parts of identity, the evolution of self-esteem in a career, how to take feedback, how anger can be a mirror for seeing core values more clearly, how to make big career decisions, how to support people who are down, and how to seek advice.

Measuring Impact: A Guide for Engineering Leaders

This article explores the importance of measuring the impact of individual engineers in a team and discusses the challenges faced in doing so. Measuring impact helps in recognizing high performers, identifying areas for improvement, and making informed decisions regarding promotions and career advancement. However, measuring impact can be subjective and difficult to quantify, and different levels of experience and seniority may require different metrics. To measure impact effectively, clear metrics and goals need to be established, growth profiles and frameworks should be revisited, and the context of the work being done should be considered. Ultimately, measuring impact contributes to the overall success of the team and the company.

Building Communities of Practice

This article discusses the problem of communication breakdown as a company grows, and the actions taken to address it. A Community of Practice was created to connect people working on similar problems, and Confluence was used as a tool to enhance collaboration. The concept spread to other departments, and people grouped around different niches in the software development department. The article also highlights the importance of having a community lead to fuel enthusiasm, and the need to create a safe environment for people to share their presentations.

Deciding if Management Is Right for You

After taking a year to reflect on the decision to move into a management role, the author decided to start small and test their skills in guiding others. They mentored a few engineers and then took on an initiative to unify the architecture of their organization. This was a successful endeavor and gave the author the confidence to decide that they could be a good manager. The author emphasizes the importance of being a good leader in engineering, such as being humble, creating an environment where everyone can thrive, and making the team feel like they can rely on you.