You have 4 summaries left

Software Engineering Daily

Engineering Insights with Christina Forney

Thu Jul 13 2023
Software EngineeringTeam EffectivenessLeadershipMetricsDeveloper SupportWorkplace ChallengesTransparencyCommunicationFuture Outlook

Description

As companies scale, measuring team effectiveness becomes difficult. Engineering leaders rely on gut feelings to make decisions. Uplevel uses machine learning and organizational science to generate actionable insights. The platform increases velocity, decreases burnout, and improves release planning. Increasing organization size and complexity obfuscates what's happening in software development teams. A study found that CTOs are often disconnected from their teams' roadblocks and implications of decisions. CTOs make strategic decisions without understanding negative impacts on teams. There is a disconnect between leadership's perception of important initiatives and developers' actual workloads. This disconnect leads to frustration and a negative reinforcing cycle. Developers feel a lack of support and reinforcement from leadership. Dora Metrics provide some clarity but are only a small piece of the puzzle. Developers want to be tracked and have data used for better decision-making, but they are not satisfied with the metrics currently used by leadership. Metrics that developers want leaders to consider include deep work time and potential burnout. The demand for software engineers is higher than the supply, leading to increased salaries and potentially more pressure on engineers to deliver. There may be a need for a solution to balance the increasing demands on software engineers while maintaining their well-being. R&D costs are some of the largest costs for organizations building software. Leadership and boards want to know if they are getting a return on investment from their engineering team. Spending excessive time in meetings takes away from value-creating exercises. Onboarding new developers and chat interruptions slow down an organization. Many organizations only get around 50-60% capacity out of their team due to overhead and meeting costs. Increasing the capacity of the team can lead to more productivity within working hours. High salaries don't necessarily mean maximum potential is being reached due to barriers and roadblocks in the way. A study revealed that most software engineers are willing to have transparency with their boss regarding their work habits. Surprisingly, not everyone prefers asynchronous communication, with roughly a third preferring synchronous communication and a third preferring a mix of both. Developers often feel disconnected from leadership decisions, with only 4% saying they know what the leadership is working on. Inconsistency in development processes and tools makes data collection difficult within organizations. Up Level provides transparency and visibility across engineering organizations to help leaders understand metrics and advocate for change. An example is identifying that too many hours are spent in meetings, leading to a policy change like 'no meeting Wednesdays' to improve focus. Engineering leaders can create transparency by showing the impact of meetings on engineers' focus time. Transparency and understanding the why behind policy decisions can lead to more buy-in and alignment. Data around code reviews, conflicts in merge requests, and development cycle times can inform decisions and generate endorsement for new policies. Teams based in different time zones may experience high waiting times for review, which can be addressed by shuffling teams to better align based on time zones. CTOs need to be better connected to what developers are doing, and developers want meaningful metrics and insights for decision-making. Relying on gut feelings without data leads to incomplete understanding and manual methods of gathering information. A product like Uplevel that improves workflows based on real-world data could increase support for async work. The amount of people supporting async workflows will increase. A product like Uplevel and the mission it is trying to achieve and fulfill should become a reality. Attrition numbers are growing in the software engineering field. Every company in the world is a software company, so we need to get better at being humane and treating ourselves with respect based on data. I hope and believe that this hypothesis could come true.

Insights

Measuring team effectiveness becomes difficult as companies scale

Engineering leaders rely on gut feelings, but Uplevel provides actionable insights using machine learning and organizational science.

Disconnect between leadership's perception and developers' actual workloads

CTOs often make strategic decisions without understanding negative impacts on teams, leading to frustration and a negative reinforcing cycle.

Developers want better support and data for decision-making

Dora Metrics provide some clarity, but developers are not satisfied with the current metrics used by leadership. They want deep work time and potential burnout to be considered.

Challenges in software engineering

R&D costs are high, excessive meetings take away from value-creating exercises, and organizations struggle to maximize team capacity. High salaries don't guarantee maximum potential due to barriers and roadblocks.

Disconnect between developers and leadership

Developers often feel disconnected from leadership decisions, and inconsistency in development processes makes data collection difficult. Up Level provides transparency and visibility to address these issues.

Improving workflows and communication

Transparency around the impact of meetings on engineers' focus time, understanding the why behind policy decisions, and using data to inform decisions can lead to better alignment and support for async work.

Future outlook

Support for async workflows will increase, Uplevel aims to fulfill its mission, attrition numbers are growing in the software engineering field, and companies need to treat themselves with respect based on data.

Chapters

  1. Measuring Team Effectiveness
  2. Disconnect Between Leadership and Developers
  3. Developers' Needs and Challenges
  4. Challenges in Software Engineering
  5. Disconnect Between Developers and Leadership
  6. Improving Workflows and Communication
  7. Future Outlook
Summary
Transcript

Measuring Team Effectiveness

00:00 - 08:50

  • As companies scale, measuring team effectiveness becomes difficult
  • Engineering leaders rely on gut feelings to make decisions
  • Uplevel uses machine learning and organizational science to generate actionable insights
  • The platform increases velocity, decreases burnout, and improves release planning

Disconnect Between Leadership and Developers

00:00 - 08:50

  • Increasing organization size and complexity obfuscates what's happening in software development teams
  • A study found that CTOs are often disconnected from their teams' roadblocks and implications of decisions
  • CTOs make strategic decisions without understanding negative impacts on teams
  • There is a disconnect between leadership's perception of important initiatives and developers' actual workloads
  • This disconnect leads to frustration and a negative reinforcing cycle

Developers' Needs and Challenges

08:29 - 17:08

  • Developers feel a lack of support and reinforcement from leadership.
  • Dora Metrics provide some clarity but are only a small piece of the puzzle.
  • Developers want to be tracked and have data used for better decision-making, but they are not satisfied with the metrics currently used by leadership.
  • Metrics that developers want leaders to consider include deep work time and potential burnout.
  • The demand for software engineers is higher than the supply, leading to increased salaries and potentially more pressure on engineers to deliver.
  • There may be a need for a solution to balance the increasing demands on software engineers while maintaining their well-being.

Challenges in Software Engineering

16:43 - 23:55

  • R&D costs are some of the largest costs for organizations building software
  • Leadership and boards want to know if they are getting a return on investment from their engineering team
  • Spending excessive time in meetings takes away from value-creating exercises
  • Onboarding new developers and chat interruptions slow down an organization
  • Many organizations only get around 50-60% capacity out of their team due to overhead and meeting costs
  • Increasing the capacity of the team can lead to more productivity within working hours
  • High salaries don't necessarily mean maximum potential is being reached due to barriers and roadblocks in the way
  • A study revealed that most software engineers are willing to have transparency with their boss regarding their work habits
  • Surprisingly, not everyone prefers asynchronous communication, with roughly a third preferring synchronous communication and a third preferring a mix of both

Disconnect Between Developers and Leadership

23:43 - 31:53

  • Developers often feel disconnected from leadership decisions, with only 4% saying they know what the leadership is working on.
  • Inconsistency in development processes and tools makes data collection difficult within organizations.
  • Up Level provides transparency and visibility across engineering organizations to help leaders understand metrics and advocate for change.
  • An example is identifying that too many hours are spent in meetings, leading to a policy change like 'no meeting Wednesdays' to improve focus.

Improving Workflows and Communication

31:26 - 39:16

  • Engineering leaders can create transparency by showing the impact of meetings on engineers' focus time.
  • Transparency and understanding the why behind policy decisions can lead to more buy-in and alignment.
  • Data around code reviews, conflicts in merge requests, and development cycle times can inform decisions and generate endorsement for new policies.
  • Teams based in different time zones may experience high waiting times for review, which can be addressed by shuffling teams to better align based on time zones.
  • CTOs need to be better connected to what developers are doing, and developers want meaningful metrics and insights for decision-making.
  • Relying on gut feelings without data leads to incomplete understanding and manual methods of gathering information.
  • A product like Uplevel that improves workflows based on real-world data could increase support for async work.

Future Outlook

38:51 - 39:51

  • The amount of people supporting async workflows will increase.
  • A product like Uplevel and the mission it is trying to achieve and fulfill should become a reality.
  • Attrition numbers are growing in the software engineering field.
  • Every company in the world is a software company, so we need to get better at being humane and treating ourselves with respect based on data.
  • I hope and believe that this hypothesis could come true.
1