Ispričajte mi o vremenu kada ste pokrenuli promjenu izvan svoje tima.

Question

Accepted Answer

Na seniorskoй razini, utjecaj prelazi granice tima. Ovo testira je li **sposoban pokrenuti organizacijsku promjenu** kroz utjecaj, izgradnju koalicija i ustrajnost — ne kroz autoritet.

## Kako to pristupiti

```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
```

## Radni primjer

```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.
```

## Dobar vs slab

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

## Zašto je to važno

Promjena na razini cijele organizacije rijetko uspijeva naredbom; ona se širi kroz dokaze, saveznike i zamah.

Pilotni projekt smanjuje rizik promjene i skepticima daje dokaze umjesto obećanja.

Ovakav utjecaj across timova je glavna razlika za seniorske i staff uloge.