engineering-partnership-optimization

Establishing a high-trust partnership with engineering is the difference between shipping a product that works and dealing with constant "over-engineering" or system rewrite requests. This skill focuses on increasing technical empathy, sharing credit, and involving engineers in the creative process to prevent the "creative outlet" trap where engineers build unnecessary technical complexity because they feel excluded from business decisions.

The Partnership Framework

1. Eliminate the "Telephone" Protocol

Avoid acting as a bottleneck or a filter that adds no value. Being a "middleman" wastes time and introduces translation errors.

• Identify the Level: If a stakeholder asks a question requiring deep technical detail, do not try to relay the answer back and forth.
• Connect Directly: Bring the engineer into the Slack channel or meeting briefly.
• Provide Context, Not Just Tasks: When connecting them, your job is to set the business context so the engineer knows why they are answering the question, then step back.
• Trigger for Action: If you find yourself saying "Let me get back to you" more than twice on the same technical topic, connect the parties directly.

2. Practice Technical Empathy

Engineers are annoyed when PMs act like details don't matter. Successful engineering is entirely about details.

• Validate Complexity: Even if you don't understand the specific code, acknowledge that the "small thing" might have massive architectural ramifications.
• Ask Probing Questions: Instead of "Why is this taking so long?", ask:
  • "What are the major technical challenges with implementing this?"
  • "Are there hidden dependencies in the old system that we haven't accounted for?"
  • "What part of this lift is the most fragile?"
• Listen to the "Boring" Stuff: Be patient when engineers explain details. It shows you value the craft, which builds the credit you'll need when you eventually have to ask for a shortcut.