Definition: Communicating with and influencing more senior people in an organisation, including reporting back how the team is responding to decisions and initiatives.So what? Leaders can only act on what they can see. Reporting the patterns and reactions a manager observes helps senior people make more informed decisions and change course when needed.Example: Sharing a leadership initiative with the team, gauging their reaction, and relaying that feedback to leadership so they understand its impact.

Definition: Leading an engineering team by bringing together people, processes, and tools, while advocating quality engineering principles to the wider organisation and acting as a two way channel between the team and leadership.So what? In a quality engineering context, the role combines people leadership with the quality engineer's mindset: empowering and protecting the team, managing what information flows in each direction, and feeding back to leadership how decisions are landing.Example: Deciding whether an update is shared as a group announcement or handled one to one, depending on how sensitive or disruptive it is likely to be.

Bug bashes enhance collaboration, provide diverse perspectives on your product, and help build and reinforce quality culture. A bug bash usually looks something like this: You invite a cross-functional team: testers, developers, product owners, designers, stakeholders. Maybe it's just your product team, or perhaps you want to invite some folks who don't usually attend your team meetings, like legal or marketing. Make sure to invite some folks who haven't yet used the product (or haven't yet tried new features). You set out some guidelines for how to test the product. Just as at a social party, you need to be a good host, and setting out clear guidelines and expectations is part of that. Make it fun! Gamify testing (some tips below).  For a few hours or maybe even a few sessions of a couple of hours, the team focuses on testing the product, following the guidelines you laid out.  Make sure to include break times. Snacks and drinks are always welcome, too. 

Definition: An approach that steps back from a single feature or task to understand how it fits into the wider product, its dependencies and downstream systems, and the people involved.So what? Applied to engineering management, the same questioning mindset used in testing helps map how work connects across products, teams, and individual growth paths, rather than viewing any part in isolation.Example: When testing a feature, mapping its downstream systems, dependencies, and third party connections, and considering how it will behave once deployed to production.