The Problem

No title. No direct reports. Yet your team needs to change direction. How?

Authority fails in matrixed orgs. Titles stop at org-chart boundaries. Technical influence works everywhere.

What Influence Looks Like

**Influence** = decisions shift because of your input, not your rank.

Not persuasion. Not politics. Credibility compounds.

Five Moves That Work

1. Ship Visible Work

Code speaks. Ship clean, well-tributed PRs. Document decisions in RFCs. Link outcomes to business metrics.

  • Before: "Maybe we should move to event-driven"
  • After: "We migrated order-processing to Kafka. P99 latency dropped 40%. Here's the writeup."

    • Evidence beats opinion.

    2. Write Down Decisions

    Verbal alignment evaporates. Written decisions stick.

    Use lightweight RFCs or ADRs. Two pages max:

  • Context
  • Options considered
  • Decision + rationale
  • Open questions

    • Write for the engineer six months later who asks "why?"

    3. Lend Expertise Freely

    Pair with adjacent teams. Answer questions in Slack without ego. Debug their staging environment.

    Reciprocity builds faster than requests. When your proposal lands, allies already exist.

    4. Frame Ideas Around Their Goals

    Stop: "We should adopt Terraform."

    Start: "Platform team needs deployment time under 15 minutes. Terraform cuts that to 8."

    Same technology. Different framing. One ignores their OKRs. One aligns with them.

    5. Disagree, Then Commit

    Challenge in meetings:

  • "This approach works for current scale. Concerned about 10x traffic."
  • Present data, not feelings.

    • Then support the final decision. Publicly. Completely.

    Stakeholders remember who pushed back constructively. Trust compounds.

    What Not To Do

  • **Don't CC executives** to win arguments. Burns bridges.
  • **Don't gatekeep knowledge.** Share playbooks. Hoarding creates dependency, not influence.
  • **Don't claim credit for team work.** Attribute precisely. Humility scales.

    • The Pattern

    Observe → Document → Share → Align → Repeat.

    Influence is a loop, not a moment.

    Takeaway

    Pick one practice. Today. Write an RFC for your next non-trivial decision. Share it unprompted with one adjacent team.

    Influence starts with the first artifact.