For me, it seems to be the constant attempts of management trying to fit “digital” into the same workflows, management systems and expectations as older, traditional work.
Every senior manager I’ve had who hasn’t been from a tech background (which has been a lot), has expected both the work and the workers to behave exactly like every other traditional, non-digital, department. This is just wrong. Not only is the work different, the process of the work is different and the output is different. For me, this manifests most starkly by people expecting concrete timelines for mostly unknown work and then getting upset when that’s either inevitably incorrect or they don’t get an answer they want. I don’t think I’ve ever been given enough time to properly scope work in order to provide a timeframe because scoping is seen as “not beneficial” work. If the company doesn’t get any financial benefit from the work, it doesn’t count.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For me, it seems to be the constant attempts of management trying to fit “digital” into the same workflows, management systems and expectations as older, traditional work.
Every senior manager I’ve had who hasn’t been from a tech background (which has been a lot), has expected both the work and the workers to behave exactly like every other traditional, non-digital, department. This is just wrong. Not only is the work different, the process of the work is different and the output is different. For me, this manifests most starkly by people expecting concrete timelines for mostly unknown work and then getting upset when that’s either inevitably incorrect or they don’t get an answer they want. I don’t think I’ve ever been given enough time to properly scope work in order to provide a timeframe because scoping is seen as “not beneficial” work. If the company doesn’t get any financial benefit from the work, it doesn’t count.