A cross-functional team from Modus Create teamed up with the healthtech company to co-develop the GitHub PoC. The approach was intentionally collaborative and designed not just to showcase GitHub’s capabilities, but to build internal buy-in across all business units.

1. Building consensus with working sessions

Instead of running traditional discovery meetings, the team took a more hands-on approach, embedding with each business unit one at a time. These were working sessions, not status calls. The goal was to see each team’s setup in action, understand their day-to-day workflows, and uncover what was really happening under the hood.

This rotating rhythm helped us understand the nuances of each business unit’s environment and provided real-time migration guidance tailored to their setup. 

2. Migration and re-engineering CI/CD workflows

Each business unit selected 2–3 repositories for the PoC. Our team then guided their migration to GitHub, along with associated commit histories, comments, and pull requests where needed.

But this wasn’t just a lift-and-shift operation. CI/CD pipelines were re-engineered in GitHub Actions, often replacing complex workflows originally built in Jenkins or GitLab CI/CD. These pipelines weren’t demos but mirrored real production logic. To validate them, developers ran typical change scenarios end-to-end, confirming that the new pipelines held up to everyday use.

3. Enabling GitHub Advanced Security (GHAS)

Working closely with GitHub’s team, we activated GHAS on the selected repositories. This allowed internal stakeholders to see how security features, like secret scanning, code scanning, and dependency reviews, could be centrally configured and enforced across teams.

This step was a critical part of the PoC. It validated GitHub’s ability to meet the company's enterprise-wide security and compliance requirements without adding custom tooling or operational overhead. Just as importantly, it demonstrated how consistent policies could be rolled out across all business units, no matter where teams were starting from.

4. Addressing resistance with transparency

One business unit wasn’t convinced. Heavily invested in GitLab, that business unit flagged valid concerns, including feature gaps, migration complexity, and disruption to familiar workflows.

We didn’t dismiss the feedback. Instead, we leaned in. The team conducted a side-by-side feasibility analysis, acknowledged where GitHub fell short, and proposed workarounds when needed, never forcing alignment, always prioritizing trust. 

5. Driving stickiness with GitHub Copilot

Our Training and Enablement team partnered with key stakeholders to design hands-on sessions aligned with both business goals and budget. Drawing on our experience scaling enablement across large teams, we delivered targeted 101 (beginner) and 201 (intermediate) workshops. We then followed up with an ROI session to help teams translate their performance, usage, and priorities into actionable metrics.