Pripoveduj mi o času, ko si spremenil/spremenila stvari zunaj svoje ekipe.

Question

Accepted Answer

Na višji ravni vpliv presega meje ekipe. To preverja, ali lahko **poganijaš organizacijsko spremembo** skozi vpliv, gradnjo koalicij in vztrajnost — ne pa skozi oblast.

## Kako se lotiti

```text
1. Frame the problem in terms leadership cares about (cost, risk, velocity)
2. Build a coalition of allied teams and sponsors
3. Start with a pilot that proves value
4. Make adoption easy — tooling, docs, support
5. Measure and broadcast the wins
```

## Delujoči primer

```text
S: Each team built its own auth differently — inconsistent and a security risk.
T: I wanted a shared, secure auth standard across six teams, with no authority
   over any of them.
A: I quantified the duplicated effort and risk, got a staff sponsor, piloted a
   shared library with one willing team, then ran office hours and migration
   guides for the rest.
R: Five of six teams adopted it within two quarters; a class of auth bugs
   disappeared from incident reports.
```

## Dobro proti šibko

```text
✓ Coalition + pilot + easy adoption + metrics
✗ Mandating change by decree
✗ A great idea that never left a doc
```

## Zakaj je to pomembno

Organizacijska sprememba redko uspije z mandatom; širi se skozi dokaze, zaveznika in zagon.

Pilotni projekt tveganje zmanjša in daje skeptikom dokaze namesto obljub.

Ta vrsta vplivanja preko ekip je ključna razlika za senior in staff vloge.