Cross-Team Influence in Engineering: Lead Without Authority

Cross-team influence is one of the clearest signs that an engineer is moving beyond local execution.

You do not need to manage people to lead important technical work. You need to create enough clarity and trust that other teams choose to move with you.

Start with shared pain

Cross-team work fails when it sounds like one team’s preference.

Find the shared pain:

• repeated incidents
• duplicated work
• slow releases
• unclear ownership
• inconsistent APIs
• poor observability
• support load
• customer-facing reliability problems

People align faster when the problem is real for them too.

Make the proposal easy to evaluate

A good cross-team proposal explains:

• the problem
• who is affected
• options considered
• recommended direction
• impact on each team
• rollout plan
• ownership model
• risks and mitigations

Do not ask teams to trust a vague idea.

Talk to teams before the review

Influence starts before the meeting.

Meet with the teams most affected. Ask:

• What concern would block this?
• What constraint am I missing?
• What would make this easier to adopt?
• What timeline is realistic?
• What risk should be visible to leadership?

This turns resistance into input.

Give credit generously

Cross-team influence is not about owning every idea.

Give public credit when other teams improve the plan. This builds trust and makes adoption easier.

People are more likely to support a direction when they feel respected in the process.

Use decision records

After alignment, write the decision down.

Include:

• what was decided
• why it was chosen
• what alternatives were rejected
• who is responsible
• what happens next
• when the decision should be revisited

This prevents the same debate from restarting every two weeks.

Promotion evidence

Cross-team influence is valuable promotion evidence.

Track:

• teams aligned
• decisions unblocked
• risks reduced
• adoption achieved
• business or operational impact
• standards created
• repeated problems eliminated

This is especially important for Staff Engineer and Principal Engineer paths.

If you want help building this skill, start with technical leadership coaching and the Staff Engineer mentor page.