I have definitely experienced effective small org -> ineffective large org.
Lots of make work, "lawyers don't get paid to simplify". Growing from small to large company you can end up with a lot of bureaucrats that tell you things like "this policy is what big cos do", but is really entrenching their position and keeping them employed. Creates adversarial relationship between devs and IT/ops/sec.
They don't have it easy, because one leak or bad PR due to data and they're shot into space.
Best to move to small effective teams, move fast, and show value. Often by currying favour of C/SVP you can get barriers removed fast and get things done.
Ecosystem is large, so find your niche.
Seen entire teams destroyed by well meaning PMs and other idealists implementing a "system" leading to dev/project slowdown and even abandon. Adding a couple check boxes to a JIRA process seems simple, but every choice is multiplied by the number of developers you have. You can see this in places that implement scrum poorly.
Overly complex security policies, JIRA check pointing, and constant meetings can grind you up. A lot of it is mistrust of employees, or employees also don't have enough context to do what they need to do.
It is also entirely possible that I am a particular type, attracted to small/medium fast movers, and then I get tired of battling security/ops/managers for access to systems/data I need to do work, or the new sets of flaming hoops to jump through to do completely mundane tasks.
Lots of make work, "lawyers don't get paid to simplify". Growing from small to large company you can end up with a lot of bureaucrats that tell you things like "this policy is what big cos do", but is really entrenching their position and keeping them employed. Creates adversarial relationship between devs and IT/ops/sec.
They don't have it easy, because one leak or bad PR due to data and they're shot into space.
Best to move to small effective teams, move fast, and show value. Often by currying favour of C/SVP you can get barriers removed fast and get things done.
Ecosystem is large, so find your niche.
Seen entire teams destroyed by well meaning PMs and other idealists implementing a "system" leading to dev/project slowdown and even abandon. Adding a couple check boxes to a JIRA process seems simple, but every choice is multiplied by the number of developers you have. You can see this in places that implement scrum poorly.
I'm reminded of this slide: https://speakerdeck.com/holman/how-github-uses-github-to-bui...
Overly complex security policies, JIRA check pointing, and constant meetings can grind you up. A lot of it is mistrust of employees, or employees also don't have enough context to do what they need to do.
It is also entirely possible that I am a particular type, attracted to small/medium fast movers, and then I get tired of battling security/ops/managers for access to systems/data I need to do work, or the new sets of flaming hoops to jump through to do completely mundane tasks.
You can always roll the dice! Bonne chance!