[ynniv]

You might be wrong in thinking that your "faster" way is better. Given no details I can't really elaborate, but a fresh perspective often omits important subtleties that management values.

For instance: paper forms becoming web forms / database tables. Great for 99% of enterprise situations, but there is a loss of flexibility in edge cases. You can't write notes in the margins, or enter "invalid" but actually correct data.

Adoption will be seen differently by different people - those who have seen no edge cases (aka you) see the common case become substantially more efficient. Those who have more experience (aka management) might see the frailty of the new system and worry that important business will be lost.

So, people who value their time (doctors, lawyers, etc) still use older systems (often paper) that are more mature and flexible. Heck, I find myself (a "Millennial" early adopter) moving towards free text systems as I run into random inflexibility.

[OliverSmith]

exactly... inflexibility to change an old process because of 1% or less of the use cases could be justified or not. If a new process makes 99% of things take 10% of the time and 1% of things take 1000% of the time, you still win. I would argue that edge cases should rarely be a reason to hold up improving a process.

[abstractbill]

...except that those 1% might be incredibly critical to the business. Perhaps if you break them, the fallout will be bad enough to kill the company.

Whether or not you should try a new process is entirely a function of what kind of company you're in, not what generation the various players grew up in. If you're in a startup, you should definitely try any new process you can think of that might give you an edge. If the company is basically milking a cash-cow, be incredibly risk-averse when thinking about "making things better".