Working Productively With a Tech Lead Who Challenges Every Proposal

You are a product manager at Google, and your team's tech lead argues the opposite side of nearly every plan or decision you bring forward. How would you deal with this? ```hint Find the motive first The right response depends on why the challenges keep coming and what they actually cost the team. Decide what you would look at before treating this as a problem to fix rather than a habit to put to work. ``` ### Clarifying Questions - Is the pushback slowing delivery or hurting team morale, or is it mainly uncomfortable for me? - Does the tech lead challenge only my proposals, or also those of engineers, designers and leadership? - Have the challenges caught real problems, such as missed risks or gaps in requirements? - How are decisions split on this team, for example product scope and priorities with me and the technical approach with the tech lead? ### What a Strong Answer Covers - Diagnosing why the tech lead pushes back and whether it helps or hurts the team before acting - A direct, private conversation that assumes good intent, describes the impact and agrees how to work together - Channeling the challenges into structure, such as pre-mortems, written trade-offs and clear decision rights - Knowing when to close a debate and commit, and when escalation is justified - A real example from the candidate's past, told with situation, task, action and result ### Follow-up Questions - You talked to the tech lead, but decisions still get reopened and the team is missing dates. What do you do next? - The tech lead challenges your plan in front of senior leadership during a launch review. How do you respond in the room and afterwards? - How would your approach change if you had just joined and the tech lead had been on the team for years?