Press "Enter" to skip to content

Metrics Mastery: Communicating Engineering Value in the Boardroom

It’s time for some big ideas to take us into the weekend.

Taryn Plumb on Venture Beat discusses the evolving authentication methods in 2024 and beyond due to the password identity crisis. The article highlights the weaknesses of traditional usernames and passwords, the importance of multi-factor authentication (MFA), the emergence of zero trust systems, the concept of just-in-time (JIT) access, the use of passkeys as an alternative to passwords, and the potential of biometrics as the ultimate credential. The article emphasizes the need for more robust authentication methods to enhance cybersecurity.

Also, in Venture Beat, Ori Keren dives into metrics for CTOs in the Board room.   How does one showcase the business value of engineering by aligning resources to high-impact projects and demonstrating operational efficiency? Metrics such as cycle time, lead time, merge frequency, business impact, full-time equivalent, and estimated cost can help communicate this value to non-technical leaders. Engineering leaders can gain the same appreciation as sales by providing meaningful metrics and secure the necessary financial support.

I also noted a piece from Mike Masnick in TechDirt, who criticizes the FTC for its lack of understanding in copyright issues related to AI. The FTC’s argument that fair use is anti-competitive is refuted, as fair use promotes competition and prevents monopolies. Copyright experts also question the FTC’s suggestion that AI training could violate Section 5 and diminish the value of creators’ works. Despite criticism, the FTC continues to endorse the idea of licensing all training data and expresses concerns about style mimicry. The FTC’s approach is seen as one-sided and endorsing anti-competitive copyright monopolies, contradicting its mission to encourage competition.

Finally, I want to ponder two perspectives.  Axios reports on how companies are navigating the challenges of diversity, equity, and inclusion (DEI) efforts as these terms become weaponized. Attacks against DEI are expected to intensify in the coming year, but many employers recognize the importance of maintaining a diverse workforce for attracting and retaining talent. DEI funding and staffing have faced challenges, and businesses are shifting their focus away from the term towards well-being and inclusion efforts.

Because according to a report from the British Computer Society (BCS), it will take 283 years for female representation in IT to reach parity with the tech workforce in the UK. The BCS also found that progress towards gender equality in IT jobs has stalled, with the proportion of women tech workers remaining at 20% in 2022. The report calls for a radical rethink to attract more women and girls to tech careers and create a more inclusive tech culture.

Why do we care?

I included Masnick’s opinion to highlight a counterpoint to my own and because businesses using AI should stay informed about evolving copyright laws and fair use doctrines. Legal advice and compliance teams should be involved in AI project planning.

I’ve long not cared about buzzwords – so if DEI is a buzzword, ok.   Focus on the business outcomes.    Like Mark Cuban, I believe efforts should be centered on practical measures that enhance employee well-being and ensure a diverse workforce because it’s good for business.  And there’s reason to do so – besides wanting to engage customers, IT companies need more workers.    IT companies and educational institutions should collaborate to create initiatives and programs encouraging women and girls to pursue tech careers. This includes mentorship, scholarships, and creating inclusive workplace cultures.

Finally, I wanted to include some metrics to consider. If you’re going to act as a virtual CTO, you should refine your metrics to demonstrate the business impact of your work. Training in business communication and analytics can help technical leaders articulate their contributions in terms that resonate with non-technical stakeholders.