February 2024 Summaries

Creating an effective survey involves more than simply crafting questions and seeking responses; it requires careful consideration of design elements to ensure the collection of meaningful data. Despite the simplicity often associated with well-constructed surveys, many fall short due to issues such as non-responsiveness, noise, and lack of actionable results. The process of responding involves complex cognitive stages—comprehension, retrieval, judgment, and response—each introducing potential biases. To mitigate these issues, survey questions should be clear, contextually anchored, and free from ambiguity, avoiding jargon and compound questions. Rating scales, such as the Likert scale, should be linear and balanced to accurately capture respondents' opinions without introducing confusion from mixed dimensions or uneven intervals. Ultimately, the goal is to enhance survey quality and user experience while ensuring reliability and validity through real response data and statistical analysis, thereby making the findings more accurate and actionable.

Engineering managers are increasingly focused on optimizing team productivity, especially in the wake of widespread tech industry layoffs since 2022. Common productivity bottlenecks include workflow inefficiencies, unclear priorities and excessive work-in-progress (WIP), burdensome "keeping the lights on" (KTLO) tasks, manual work, and external decision-making. To address these issues, teams should streamline workflow processes, set clear priorities and WIP limits, reduce KTLO through prioritization and automation, and move decision-making closer to the team. Empowering teams and fostering a culture of continuous improvement and experimentation are essential for sustainable productivity gains. Avoiding fallacies such as over-reliance on detailed upfront planning, simply increasing headcount, or assuming more processes will enhance speed is crucial. Instead, focus on outcomes over outputs and engage stakeholders to support productivity initiatives. This approach aligns with the principles in Donald G. Reinertsen's "The Principles of Product Development Flow" and is supported by tools like Swarmia, which provide visibility and solutions for resolving bottlenecks.