HN840: How to Make a Technology Buying Decision

The episode features Ethan Banks and Drew Conroy-Murray interviewing Sean Morgan about making effective technology buying decisions in networking. Morgan transitions the conversation from the typical engineer-focused approach (specifications, throughput, protocols, APIs) to a broader business perspective that encompasses organizational alignment and financial justification.

Morgan argues that the most critical aspect of technology buying decisions is ensuring IT functions align with broader business objectives. Engineers must understand the revenue impact of their infrastructure decisions—what happens to the business if specific systems fail, which internal clients depend on those systems, and how technology unlocks future opportunities. This requires engineers to spend time with stakeholders to understand business needs rather than acting as gatekeepers.

The discussion addresses vendor messaging and product features. Morgan notes that while vendors often highlight incremental improvements, their insights about future industry direction can be valuable if filtered appropriately. She emphasizes understanding true costs across hardware, software, and human resources before evaluating vendor claims about savings. For example, if a vendor claims 90% reduction in troubleshooting costs but the organization only spends two hours monthly on troubleshooting, the claim is obviously false.

On ROI calculations, Morgan stresses the importance of first establishing credibility by demonstrating understanding of business objectives. ROI must include human element costs and opportunity costs—what else could employees do if freed from troubleshooting or maintenance tasks. Revenue enablement is more valuable than cost reduction, particularly when IT enables new business initiatives. However, enterprises often lack clear visibility into their total IT spending due to fragmented budgets across operations, capital expenditures, marketing, and manufacturing.

The conversation explores the challenge of justifying incremental technology upgrades when existing infrastructure functions adequately. Morgan notes that opening of the 6 GHz band represents a true inflection point, but most networking improvements are incremental. The Wi-Fi market operates on roughly five-to-seven-year replacement cycles driven by end-of-life rather than revolutionary capabilities.

Both speakers emphasize proof-of-concept testing before adoption, noting that new products often have untested corner cases and unexpected interactions with specific customer environments. Vendors aren't being deliberately deceptive; they simply cannot foresee all use cases and configurations. Strong vendor relationships matter because partnerships help address issues when they arise. The discussion concludes with Morgan reflecting on how her shift from engineering leadership to market analysis gave her perspective on industry patterns and the value of professional networks for problem-solving.