Developing People& Building Teams

For more than a decade, I held formal leadership responsibilities across technical support organizations supporting network management, secure file transfer, and messaging platforms.

My responsibilities included hiring, coaching, performance management, career development, resource planning, escalation leadership, compensation advocacy, and coordination across engineering, QA, product management, documentation, sales, and executive leadership.

My leadership journey began as a Team Lead before progressing into management responsibilities supporting multi-product technical organizations. Over time, I led teams supporting technologies including WhatsUp Gold, WS_FTP, MOVEit, and related products, helping engineers grow while balancing customer needs, business priorities, and organizational change.

While products, technologies, and organizational structures evolved over the years, one lesson remained constant: organizations scale through people.

Some of my proudest accomplishments are not products launched or projects completed, but the people who advanced into larger technical and leadership roles after joining my teams.

One of the most important lessons I learned as a manager was that talent is not always reflected in a résumé.

Throughout my leadership career, I frequently looked beyond traditional credentials and focused on qualities such as curiosity, accountability, communication skills, customer empathy, and problem-solving ability.

Several individuals who joined my teams from non-traditional backgrounds went on to build successful careers in technical support, quality assurance, software development, and leadership roles.

I learned early that hiring for potential often creates opportunities that hiring solely for experience can miss. Technical skills can be taught. Curiosity, integrity, and the desire to learn are much harder to develop.

As our teams evolved, I encouraged engineers to expand beyond a single product and develop expertise across multiple technologies.

At various points, our organizations supported WhatsUp Gold, WS_FTP, MOVEit, and other technologies across multiple teams. While organizational structures often favored specialization, I believed broader technical understanding created stronger engineers and more resilient organizations.

Cross-training improved collaboration, increased organizational flexibility, and created new career opportunities for team members capable of taking on larger responsibilities.

Many of the individuals who embraced that broader approach later advanced into QA, development, and other technical leadership positions.

Leadership is not only about accountability downward. It is also about advocacy upward.

One of the most memorable leadership lessons of my career occurred during a major organizational restructuring. Following a company reorganization, support responsibilities were divided across newly formed business units. While those organizations were still being established, my team continued supporting workloads that spanned multiple product groups.

When compensation decisions were later calculated according to divisional structures rather than actual team contributions, I believed the outcome did not accurately reflect the work my team had performed.

I advocated on behalf of my team because leadership requires more than managing performance. It requires ensuring that contributions are recognized fairly and that the people doing the work have someone willing to represent their interests.

Several months later, the team ultimately received the compensation recognition they had earned. More important than the outcome, however, was the principle behind it.

The experience reinforced a leadership lesson that has remained with me throughout my career: people remember whether their leaders stand with them when difficult decisions are made.

Over the course of my career, I helped teams navigate acquisitions, product integrations, organizational restructuring, global support expansion, and evolving operational models.

Examples included supporting the integration of MOVEit following acquisition, supporting the integration of Dorian technologies into the broader support ecosystem, coordinating geographically distributed support operations, and supporting customers across North America, Europe, Asia, Latin America, Africa, and Australia.

These experiences reinforced that the greatest challenge during organizational change is rarely technology itself. The challenge is helping people maintain clarity, trust, and alignment while change is taking place.

Much of my leadership experience existed at the intersection of customers, support, engineering, product management, and business operations.

Whether coordinating major customer escalations, supporting product integrations, helping teams navigate organizational transitions, or serving as a voice for customers within engineering discussions, my role often involved creating shared understanding between groups with different priorities and perspectives.

One example involved coordinating resources across support and engineering teams to address complex customer challenges where technical resolution required collaboration across organizational boundaries.

Looking back, a common thread throughout my career has been helping people move from ambiguity to alignment.

That philosophy continues to shape how I approach leadership, technology, customer engagement, and business challenges today.