Yes, I do suggest improvements, and it's how I got promoted to my current role as a manufacturing project manager (Yes, ugh, project manager. At least I'm technical).

I think the approach matters a lot. Nobody appreciates some corporate jagoff like me coming in and saying that everything is being done wrong and I have a better way. The people who engage in a given process every day are the experts in that process. Regardless of what I think could be improved, they have to buy in and agree that the changes I proposed are actually useful, which they won't do unless they feel some ownership over or stake in the change.

If I have ideas on how to improve, I start by asking about the current process and why things are done that way. It's easy as an outsider to think that there are opportunities to improve something, especially when I don't have a lot of insight into that process.

Sometimes, the answer to why we do things in a certain manner is "we've always done it that way," which indicates to me that either:

1. The opportunity is ripe for improvement, or
2. Somebody already went through this process and found the optimal way to do it.

The second option doesn't necessarily mean there isn't room for improvement, as technology and capabilities evolve over time, but it may not be worth further exploration.

Often times, in asking those questions, I learn about some nuance or technicality that totally invalidates my idea or changes how I would approach it. Sometimes we accept inferior ways of doing things because they make something else more efficient or easy.

It's important to pick your battles when proposing improvements. Not everything will bring the same degree of cost savings, efficiencies, or whatever other benefits to the table. Choose the ones that will have the biggest impact with the least amount of effort/cost to implement, and you have a formula for success.