The Value of the Non-Expert

-

Early in my career, I was invited to sit in on a meeting with enterprise architects and senior engineers to discuss an integration between a legacy content management system and a new distribution platform. I was there as the (fairly junior) project manager, not the technical authority in the room. The conversation quickly became highly specialized: API contracts, data schemas, caching layers, and system latency thresholds. It was clear I wasn’t the deepest technical expert at the table, and for the first part of the discussion, I mostly listened and felt a little lost.

What I began to notice, however, was that while the technical details were sound, the group was implicitly optimizing for architectural elegance rather than delivery timing. No one was explicitly mapping the proposed solution against the external deadline tied to a partner launch. I asked a clarifying question that went something like this (I may have actually rambled a bit): “If we implemented the simpler, interim integration first, would it satisfy the partner requirements for phase one, even if it’s not the long-term architecture?” That shifted the energy in the room. The engineers acknowledged that a phased approach was technically feasible; it just hadn’t been the direction they were debating.

By reframing the conversation around business constraints rather than technical perfection, I was able to contribute meaningfully without pretending to be the expert. The teams aligned on a two-phase plan. First, deliver a stable, limited integration to meet the launch date, then refactor toward the more scalable architecture in the next release. That experience reinforced for me that being the “non-expert” doesn’t mean being silent. Sometimes the most valuable contribution is connecting deep expertise back to the larger objective the team is trying to achieve. 

Popular posts from this blog

The Dual Faces of Technology: Enhancing and Replacing Jobs

-
Image
Automation has been on my mind a lot lately, more immediately due to a book I read , but also because of the looming reality of artificial intelligence. To understand what's involved, making the distinction between replacing technologies and enabling technologies is crucial. As we traverse the timeline of the 20th century, we observe how each type of technology has distinctly influenced employment. Automated technologies have transformed industries by replacing manual labor with machines. Consider the automated switchboards introduced in the early 20th century. Previously, telephone operators manually connected calls using physical connectors on a switchboard. With the advent of automated switchboards in the 1920s and 1930s, many of these jobs were eliminated as calls were routed through electromechanical systems. Similarly, in agriculture, the introduction of mechanical harvesters like the combine harvester in the 1930s drastically reduced the need for manual labor. These machine...
Read more

The Technology Trap: Capital, Labor and Power in the Age of Automation (Book Review)

-
Image
In his compelling book, " The Technology Trap: Capital, Labor, and Power in the Age of Automation ," Carl Benedikt Frey offers a sweeping examination of the historical and ongoing impact of mechanization and automation on society. Starting with the onset of the first Industrial Revolution, Frey deftly navigates through the evolution of technology up to the modern age of artificial intelligence, presenting a nuanced view of how technological innovations have reshaped labor markets and power dynamics. Frey categorizes technological innovations into two types: enabling technologies, like the typewriter, which enhance worker productivity without displacing the labor force, and replacing technologies, such as robotic machinery in factories, which eliminate certain job roles altogether. This distinction forms the backbone of Frey’s analysis, as he explores the varying implications of each type of technology on different segments of the workforce. The book traces a historical patter...
Read more

Deputy Product Owners

-
Image
"The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner." - The Scrum Guide There are a lot of ways in which my approach to Scrum differs from what's in the official guide, and since that document refers to Scrum as 'immutable,' let's just call what I do 'Notscrum™.' In Scrum, there is only one product owner per team. That person is the sole person responsible for the product backlog, and the person who advocates for the work to be done. In Notscrum there is one product owner, but there can be multiple deputy product owners. Here's how it works. When my program at Viacom was first forming I met with the then-director of the Library & Archive group and learned that while he set the priorities on work done, the archivists were organized in three distinct areas with a team lead ...
Read more