What steps or processes do you use to identify improvements that will genuinely make an impact at your company? Do you keep up with new tools and look for ways to introduce them, or do you start with a specific problem and then find the right tool or process to address it? I feel like this is an area I'm missing in my career, and it may be holding me back from moving up. I'd appreciate practical advice on how to spot worthwhile opportunities and show their value.
4 Answers
Begin with a real use case, not a tool trend. Find the biggest sources of wasted time, cost, or risk, then support them with data such as deployment frequency, lead time, failure rates, recovery time, ticket volume, or time spent on manual work. Value-stream mapping can help expose unnecessary handoffs and long waits. Once the problem is clear, choose the simplest reliable solution, whether that is a process change, automation, or a new platform.
Start by talking to the people doing the work and keep track of recurring pain points. Look for things that slow delivery, create confusing handoffs, or make routine tasks unnecessarily difficult. One-off complaints may not mean much, but problems that come up repeatedly over several weeks are usually worth investigating. Often the best improvement is better coordination or a simpler process rather than a new tool.
There are plenty of high-impact improvements that are not flashy: reducing merge queues, speeding up frequently run jobs, turning repetitive support requests into self-service, fixing recurring incident causes, improving secret management, and reducing noisy alerts. Review post-incident actions and toil logs for ideas. Also check whether tools you already pay for have features that could replace manual steps or extra add-ons.
The small fixes can be easy to overlook because they quickly become the new normal. Record the baseline first—how long the process took, how many tickets it generated, or how often it failed—so you can demonstrate the impact later.
A practical approach is to choose one recurring problem, build a small proof of concept, and measure the result before asking to expand it. Prioritize improvements that reduce business risk, save meaningful time or money, improve security, or make delivery more predictable. Companies are usually more receptive when the proposal is tied to a clear problem and measurable outcome rather than enthusiasm for a particular technology.
Exactly. A bit of listening and relationship-building can uncover more useful improvements than chasing whatever technology is currently popular.