Work carried
through to use.

The situation

A global pharmaceutical enterprise was piloting an AI-powered scientific-literature platform before deciding on a wider rollout. The pilot involved 60 power users, nine client workstreams and six internal teams. The product had to meet the client’s workflows while working within licensed-content constraints.

My responsibility

I ran the implementation process: onboarding, the delivery plan, requirements coordination, phased rollout, training and stakeholder communication. My role was to connect the client’s needs with the people responsible for the product and its delivery.

I structured the pilot around incremental delivery and feedback. Demonstrations, workshops, Q&A and train-the-trainer sessions gave the client opportunities to work with the platform as it developed.

Partway through the pilot, the AI capability was falling short of expectations. I brought the client’s requirements into a shared conversation with product, the business unit and engineering. We clarified what could be delivered within the licensed-content constraint and the launch window, then shortened the QA and demonstration cycle so the client could assess working software.

What changed

The pilot met its success criteria and progressed to a global launch for 20,000 users in July 2026. The implementation approach, tracking framework and presentation materials became reusable assets for colleagues.

The 20,000 figure describes the scope of the launch, not a measured active-user count. My contribution was implementation and cross-functional delivery, rather than model development.

The situation

Following a twelve-month technical account review, a multinational enterprise needed to consolidate three large software accounts into one setup. The work involved approximately 30 stakeholders, different regional requirements, interpreters and multiple time zones.

This was as much a coordination problem as a configuration task. Different groups needed their requirements understood, and decisions had to hold across the whole implementation.

My responsibility

I led the consolidation, coordinating requirements alignment, configuration decisions, quality assurance and client sign-off. I worked with the stakeholders involved to establish who needed to contribute to a decision and who needed to approve it.

I kept decisions and actions visible, coordinated communication across time zones, and worked through conflicting regional requirements with the relevant groups. The aim was to give everyone a shared understanding of the configuration and what remained to be done.

The earlier account review provided the groundwork for the integration. It connected a detailed understanding of the existing setup to the practical decisions needed to bring the three accounts together.

What changed

The three accounts were consolidated into a single, fully working account. Stakeholders signed off and the project closed with no outstanding issues.

The useful lesson was practical: complex implementations need clear decision ownership and sustained follow-through alongside the technical work. Keeping those visible helped the different groups move through the consolidation together.

The situation

A global chemical company needed a content-management solution that fitted its internal workflows. The work extended from understanding those requirements to launching the platform and preparing an operations team to run it.

The project spanned 36 months. A working implementation had to include the people, knowledge and handover needed to sustain it after launch.

My responsibility

I carried the implementation through requirements scoping, system and workflow design, configuration, testing, training, launch, quality assurance and handover.

I worked with the client to translate its requirements into a practical configuration and delivery sequence. Testing and client feedback were part of the implementation, so the team could check that the solution matched the workflows it needed to support.

Training covered both users and administrators. Those audiences needed different levels of understanding: one to work with the platform, the other to support and maintain its operation. The handover connected that training with the documentation and knowledge the operational team would need.

What changed

The system was delivered, launched and handed over. The client’s operations team ran the platform independently after handover.

For this project, that was the meaningful endpoint: the software was in use and the team responsible for it could take the work forward. The implementation covered the transition into operational ownership as well as the technical launch.