Technical Leadership Talks

The episode contains moderate substance about program design philosophy and curriculum rationale, but much of it consists of generalized claims about what leaders need (empathy, decision-making, finance literacy) without deep tactical or strategic insight. The specific industry pain point (engineers failing in management roles) is identified early, but the conversation rarely drills into how the program solves it beyond course titles and anecdotes.

“engineers are very, very good at solving problems or creating products. Uh, when it comes to the human side, engineers shy away”

“on the average it takes about seven years working for a company to really get promoted into high level management. And we want to shorten that time. Rather than seven, maybe it could be two years or three years”

The core insight - that engineers need emotional intelligence and soft skills training - is not novel; it reflects widely-acknowledged industry gaps that have been discussed in management literature for years. The emotional intelligence framework draws heavily from Goleman's well-known work. The program design itself (backwards from outcomes, industry advisory board input) mirrors standard curriculum development practice. No contrarian or first-principles arguments are presented.

“I ran into a book by Daniel Goldman on emotional intelligence that really hit me personally hard”

“we work backward. We created 10 courses in 2016”

Dr. Zoghi is a legitimate academic leader with 40+ years of engineering and management experience who founded and runs a significant program, giving him relevant practitioner credibility. However, his primary credential is as a university administrator/professor building an educational product, not as an operator who scaled teams or navigated complex business challenges in industry. He is somewhat removed from day-to-day technical leadership in a commercial setting.

“four days after 9, 11, I got my first management position. And after a couple years I noticed that I'm not really doing well”

“40 years of experience as an engineer, as an engineering professor, as a director, as a leader”

While the episode names the 12 companies involved in early design (petroleum, aerospace, software, consulting, auto), it provides almost no specific metrics, timelines beyond broad years (2015 - 2018), or concrete data validating program outcomes. One salary example ($30,000 raise, $200k+ salaries) is vague. Enrollment numbers (40, 45, 72) are given but no context on retention, job placement rates, or measurable leadership improvement. The anecdotes are touching but not evidence.

“12 companies and their frustration was they hired excellent engineer a lot from Texas A and M, but when they put them in management leadership position, either they fail or they don't do well”

“After I got my degree, I got a raise for 30,000”

The host asks straightforward, open-ended questions that allow the guest to deliver prepared answers, but there is minimal follow-up probing, pushback, or drilling into contradictions. When Dr. Zoghi claims the program shortens management readiness from 7 years to 2 - 3 years, the host does not ask for evidence. When he describes limiting enrollment to 40 - 45 to ensure quality, there's no challenge on the trade-off between exclusivity and impact. The conversation reads as a sympathetic program profile rather than critical inquiry.

“So can you take us back to the beginning and what inspired you to create the Master of Engineering Technical Management?”

“What were some of those skills?”