cross-functional-leadership

Facilitate alignment between engineering and other functions (product, design, stakeholders).

Work with product to negotiate achievable scope when capacity is constrained.

Convert technical constraints and risks into business impact language.

Facilitate alignment sessions when teams have different visions or priorities. Use before major initiatives or when resolving cross-functional conflict.

Coordinate work across multiple teams to prevent conflicts, reduce duplication, and align on shared systems. Use when scaling beyond single team or managing dependencies.

Create design-to-engineering handoff processes that minimize rework and ensure designs are implementable. Use when coordinating with design teams or establishing design-engineering collaboration.

Negotiate scope defensively when timelines are tight or requirements are vague. Use when facing unrealistic deadlines or unclear feature requests.

Communicate technical progress, tradeoffs, and risks to non-engineers in language they understand. Use in status updates, executive presentations, or crisis communication.

Build collaborative relationships with product managers where engineers shape strategy and product makes informed decisions about technical tradeoffs. Use when coordinating feature prioritization or platform decisions.

Translate business/user requirements into technical specifications that engineers can build against. Use when clarifying ambiguous requirements or discovering hidden technical constraints.