Improving Communication Between Engineers and Product Managers: Insights from Nicholas C. Zakas

Software engineers are frequently perceived as difficult to communicate with, a view echoed by many senior developers, including frontend expert Nicholas C. Zakas, who admits his own communication shortcomings and emphasizes that effective collaboration requires mutual understanding of engineers' daily work and emotional states.

Zakas, formerly Yahoo's front‑end lead and now at Box, reflects on his dissatisfaction stemming from being treated merely as a code executor rather than a creator, highlighting the frustration when product direction is pre‑defined and engineers are excluded from the creative process.

He illustrates common pitfalls through a house‑building analogy: product managers often push to start without clear plans, set deadlines before requirements are defined, and later demand changes that render earlier work obsolete, leaving engineers to guess and assume, sometimes incorrectly.

Key problems identified include vague or late requirements, contradictory specifications, small changes that cause large rework, and last‑minute major revisions under tight deadlines, all of which erode engineers' motivation and sense of ownership.

Zakas proposes four actionable recommendations: (1) involve engineers early to deepen their understanding of requirements; (2) minimize interruptions, especially during focused coding periods; (3) create space for engineers to make technical decisions and trust their judgment; and (4) provide timely gratitude and feedback to show respect and reinforce positive collaboration.

By applying these practices, teams can avoid the “garage‑first” scenario where engineers build isolated components only to discover later that the overall product vision has dramatically changed, ultimately leading to more efficient development and higher morale.

Source: Lagou.