Leadership and execution

Time to improve: making room to test automation

A team needed to prove automation's potential before receiving dedicated resources. An internal reassignment made the first test possible.

No one was going to give me a person to work on automation. So I reassigned someone from my own team.

In a commercial function I led, we knew parts of the routine could be automated. The challenge was finding capacity to test what could free up time later. Without someone to run the proof of concept, there was no evidence. Without evidence, there were no additional resources.

This is another chicken-and-egg problem in corporate life: improvement needs initial capacity before demonstrating the benefit that could justify a larger structure.

The first decision was resource allocation

I reassigned a leader to the project and promoted an inside salesperson. She ran a proof of concept with an external implementer, using a real process.

The promoted salesperson took over leadership and retained some accounts, helping preserve the operation during the change. Capacity for the test came from a decision within the existing team.

That choice had a cost and a risk. If the test failed, I would have taken a leader out of the routine without demonstrating the potential benefit.

From proof to expansion

The proof of concept worked. As the program developed, robotic process automation, or RPA, reached around twenty bots in sales. Only afterward did a dedicated IT person join, enabling expansion into other areas.

That sequence matters. The twenty bots belonged to the program's development, rather than being the result of the first test alone. The proof of concept demonstrated potential; continuity required further decisions.

At Danaher, I learned the term Dynamic Resource Allocation. As applied in this account, it means moving people and time toward a priority before results appear, using available capacity to demonstrate value and seek conditions for implementation and scale.

Three questions before requesting more resources

Before requesting additional capacity for an improvement, I ask myself:

  1. Which real process could demonstrate the benefit?
  2. Who steps out of the routine, and what do we stop doing to make room for the test?
  3. What result would convince the person responsible for approving the next stage?

The second question is particularly important. A proof of concept needs room in someone's workload. Recognizing what will be redistributed makes the cost of the choice clearer.

A first step does not replace resources for scale

This case does not imply that every initiative should start without additional investment. Some require infrastructure, skills or conditions the team does not yet have.

Here, there was an opportunity to test with reassigned internal capacity and external support. We chose to make that first commitment to demonstrate the potential. Expansion came later, with a different structure.

Waiting for spare time can keep a team trapped in the routine it wants to improve. The path I found was to select a process, create room for a test and make explicit what that decision required of the operation.

A personal account by Leandro Oliveira.

Leandro Oliveira

Executive with experience in B2B sales, marketing, services and operations. Shares lessons from his professional career across different sales rhythms and markets.

Ready to develop your commercial operation?

Let us discuss the decisions, processes and capabilities that need to evolve.

Contact ProduBiz