Timeline for Should I propose a big change as a newcomer?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2013 at 10:22 | comment | added | lortabac | +1 for the cautious approach. My particular case turned out to be a simple lack of time to organize a meeting between the 2 managers. Now the issue is solved, but your points are still valid in general. | |
| Apr 3, 2013 at 17:02 | comment | added | user5305 | You are making a lot of assumptions based only off of your experiences, this isnt always true. | |
| Apr 3, 2013 at 16:04 | comment | added | Telastyn | @rhysw - Do you really think the other department's boss didn't already talk to the OP's boss about it? I've seen this a half dozen times. One backwards department head rebuffs attempts at improvement as change for change's sake, or due to political spite, or due to simple ignorance of the impact the backwardsness causes. Since the direct tact failed, the other department head is trying to subvert the change into the department. Having the OP bring this up directly or calously would quickly destroy that process. | |
| Apr 3, 2013 at 15:55 | comment | added | user5305 | Which is precisely why it doesnt hurt to bring it to his boss's attention. If it can solve the problem, the boss will push it, if it cant, the boss will tell him it wont work and explain why. Best case scenario, you solved a problem, worse case scenario you learned something new about the system and why your solution wont work. I dont see any downsides | |
| Apr 3, 2013 at 15:52 | comment | added | Telastyn | @RhysW - Poppycock. If the new guy goes in and pushes for improvements without knowing the problem he is fixing, or the political landscape he could easily set people against the improvements. Improvements only benefit the company if they're enacted. | |
| Apr 3, 2013 at 15:08 | comment | added | user5305 | Waiting until a problem arises can be costly when a deployment breaks and costs a few hundred million to a customer due to their lack of service. There is never any harm in discussing improvements pre-problem | |
| Apr 3, 2013 at 12:58 | history | answered | Telastyn | CC BY-SA 3.0 |