A boomerang hire with a specific mandate
Progress Software announced on August 18 that Bridget Collins is returning to the company, where she started her career decades ago as a software engineer, this time as chief information officer. She arrives from Rapid7, where she held the title of chief information and business transformation officer, and before that held CIO or transformation roles at Cerence and Nuance Communications, two companies built around conversational and generative AI before the industry called it that. CEO Yogesh Gupta framed the hire around scale: Collins's job is to lead IT strategy, cybersecurity, and AI adoption as Progress absorbs recent acquisitions and expands its own AI footprint.
The detail worth sitting with is what Progress actually sells. The Burlington, Massachusetts company builds enterprise software for managing the data, content, workflows, security, and governance that sit underneath AI initiatives, exactly the category every enterprise buyer is currently trying to figure out how to budget for. Putting a career CIO with three prior stops running technology and transformation for AI-adjacent companies in charge of Progress's own internal AI adoption reads as a deliberate choice, not a coincidence. The company appears to have decided its internal IT organization needs to double as a credible proof point for what it sells.
Why the internal reference case matters to buyers
Enterprise software buyers have gotten sharper about asking vendors uncomfortable questions: if your product manages AI governance, how does your own company govern the AI it uses internally? Most vendors struggle to answer well, because the internal IT organization and the product organization tend to operate on different timelines and different budgets. Collins's public comment on taking the job, that Progress has established itself as delivering the context and control organizations need for AI, reads like someone who already understands that this is the question she has been hired to answer credibly rather than rhetorically.
For a CIO evaluating governance or data management vendors, this is a useful signal to look for elsewhere in the market: does the vendor's own IT leadership carry real operating experience in the category, or is the internal deployment a marketing afterthought bolted onto a sales pitch. Collins's background running IT at a cybersecurity company and two AI-native firms means she has almost certainly made the same build-versus-buy and vendor-versus-internal-tooling calls that Progress's customers face right now, and that lived experience is a more credible signal of product fit than any published case study.
The integration work hiding behind the AI headline
Progress has spent the past several years acquiring companies to broaden its data and application platform, and each acquisition brings its own IT stack, security posture, and data governance conventions that need to be reconciled before AI initiatives can run cleanly across the combined company. Collins's transformation-officer background, not just her CIO title, is the relevant qualification here, since technology integration after M&A is a distinct discipline from either pure IT operations or pure product strategy.
This dual mandate, AI governance plus acquisition integration, is a heavier lift than either responsibility alone, and it explains why Progress went outside for a candidate with a documented track record in both rather than promoting internally or splitting the role. For any technology leader managing a company built partly through acquisition, the lesson is that AI adoption and integration debt are not separate workstreams competing for budget, they are the same problem viewed from two angles, and they need one accountable owner.
The talent pattern behind the hire
Collins's career path, from software engineer to CIO across a cybersecurity firm and two conversational-AI companies, is becoming a recognizable profile: technology executives who built their governance credentials before AI governance was a formal budget line are increasingly the ones landing CIO seats at companies whose entire pitch depends on governance credibility. That is a narrower and more specific hiring criterion than simply having run IT before, and it means the talent pool for this kind of role is smaller than the volume of open postings might suggest.
For enterprise tech leaders building out their own AI governance function, the practical implication concerns where to look for talent. If your organization needs someone who can both run internal IT and speak credibly about how AI governance functions in production, the strongest candidates are the ones with prior experience at companies where governance was the product itself, not just a compliance checkbox layered on top of engineering. Progress just demonstrated what that hiring thesis looks like when a public company acts on it deliberately.
What this means for your next IT leadership hire
The broader lesson for enterprise buyers extends past Progress's own customers. As more software vendors position themselves around AI governance, data control, and security, the credibility of the pitch increasingly rests on whether the vendor's internal technology leadership has actually lived the problem, not just marketed a solution to it. Collins's hire gives Progress a genuine answer to that question, and competitors selling into the same category should expect to be measured against it.
If you are staffing a CIO or head-of-IT role at a company navigating its own AI rollout, weigh candidates the same way Progress evidently did: prioritize operating experience in AI-adjacent environments and demonstrated transformation work over generic IT management credentials. The gap between a CIO who has theoretically studied AI governance and one who has actually built it under real operational pressure is exactly the gap Collins is being paid to close.
