Timeline for How to evangelize DevOps and tools in a low acceptance environment?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2017 at 22:49 | comment | added | Jiri Klouda | On any job you need 30 days to learn the environment and 30 days to try to make your first mark and larger contribution. If you were not able to make a contribution by then, you won't have the reputation to bring larger change. If you did, you can try to push on the acceptance issue, if after another 30 days you still meet with sharp resistance, start escalating up the chain one step a week all the way to CEO. If the CEO does not care about transformation, nothing will change. Start lining up the interviews. | |
| Dec 15, 2017 at 22:33 | comment | added | 030 | @JiriKlouda How long will you give it a try? Imagine that someone joined a company last week and sees that there is a low acceptance environment, should one leave in one week? | |
| Dec 15, 2017 at 22:18 | answer | added | 030 | timeline score: 0 | |
| Dec 15, 2017 at 22:09 | comment | added | Jiri Klouda | I find out that the best reaction to low acceptance environment is leaving. When good people keep leaving, it becomes very convincing very quickly. | |
| Dec 15, 2017 at 21:38 | history | edited | 030 | CC BY-SA 3.0 |
edited title
|
| Sep 11, 2017 at 4:54 | vote | accept | Ta Mu | ||
| Sep 7, 2017 at 16:25 | answer | added | Stuart Ainsworth | timeline score: 9 | |
| Sep 7, 2017 at 8:18 | answer | added | 030 | timeline score: 4 | |
| Sep 7, 2017 at 5:25 | history | asked | Ta Mu | CC BY-SA 3.0 |