Stop Waiting for Title

9+ year enterprise IT veteran here. Learned hard: **title grants permission, not influence**. Influence built on competence, trust, consistency. Pattern observed: [earn trust] [through delivery] [then guide decisions].

Why Authority Falls Short

  • **Organizational reality**: Most tech decisions made before leaders enter room. Ground truth lives in Slack threads, RFCs, PR comments.
  • **Authority = compliance**: People follow. Influence = commitment. Difference shows in quality, speed, outcomes.
  • **Matrixed environments**: Cross-functional teams, dotted-line reporting, no direct reports? Influence mandatory.

    • Build Credibility Like Compound Interest

    **Become domain authority.** Pick area. Own it. Answer questions before asked. Document decisions. Share context freely.

    ```markdown

    # RFC: Migration Plan

    Context

    Current system latency spikes 3x under peak load...

    Decision

    Adopt event-driven architecture...

    Consequences

    Positive: Decouples services...

    Negative: Operational complexity increases...

    ```

    **Code reviews > meetings.** Thorough, respectful reviews teach. Set quality bar without gatekeeping.

    **Ship small wins.** Pattern: [identify pain point] [prototype fast] [demo working result]. Concrete demos beat slide decks.

    Create Pull, Not Push

  • **Align incentives**: Frame proposals around *their* goals. [Database team] cares about query performance? Show solution reduces load 40%.
  • **Build coalitions**: Pre-wire decisions. Talk stakeholders 1:1 before group meetings. Find co-authors.
  • **Embrace constraints**: Budget freeze? Timeline pressure? Constraints force creativity, build credibility when navigated well.

    • Navigate Politics Without Becoming Political

    | Do | Don't |

    |---|---|

    | Surface trade-offs transparently | Hide risks to look good |

    | Credit others publicly | Take credit for team wins |

    | Challenge ideas respectfully | Challenge people personally |

    | Admit knowledge gaps | Bluster through uncertainty |

    **Document everything.** Decisions drift. Requirements morph. Written record protects team, prevents hindsight bias.

    Practical Takeaway

    Start Monday: **Pick one upcoming decision. Map stakeholders. Understand one person's constraints. Propose solution addressing their win condition.** Influence compounds.

    Pattern: [small consistency] [over time] [builds unshakeable reputation]. Start.