Back to Knowledge Base
    CasesMay 5, 2024

    Case: Automotive HR & SAP SuccessFactors

    A highly visible project spanning many years for an automotive giant, integrating HR systems across 10+ countries.

    Case: Automotive HR & SAP SuccessFactors

    Complex and high-stakes. That describes this project perfectly.

    A global SuccessFactors integration for an automotive giant. Multiple years. High visibility across the organisation.

    HR teams from 10+ countries were working together. Migrating personal data. Adopting new user flows. Training people on the new system. And building an integration layer because the old local systems weren't going away immediately.

    For the team I worked with, this meant constant work, confusion, and risk.

    The session

    A RiskStorming session was clearly needed. We sat together physically, shuffled topics around the room, but logged everything in RiskStormingOnline so we could track risks as they developed.

    Some of the risks we covered:

    • Error and update emails from the integration being unclear or impossible to act on
    • Data getting out of sync without the team knowing
    • Special characters breaking because of encoding differences
    • Uncertainty about access to the third party test environment: when, and for how long
    • Limitations on logs, historical data, and what happens when time and throughput hit their limits
    • The nightmare scenario: the third party sends an empty table or re-formatted data that wipes out everything

    What we did about it

    For each risk, we talked through mitigation strategies. Sometimes that meant building logging and alerts on our side. Sometimes it meant requesting other parties set up processes well ahead of time.

    The point was having these conversations early. Documenting them. Tracking progress as a team.