Trillion

"We need more consultants" is the reflex when a SAP programme slips. It's usually the wrong call. Most delays we see trace back to governance, not headcount: unclear decision rights, slow approvals, scope that drifts unchecked. Here's how to fix it without adding a single person to the programme. ➡️ Full breakdown on the blog: https://lnkd.in/e6mjwzw7 #SAP #SAPTransformation #SAPProgrammeDelivery #CIO

The 2027 ECC deadline isn’t moving, and many S/4HANA programmes are already operating against tight delivery timelines. Do you have a clear view of where your S/4HANA programme stands? We’ve prepared a short readiness check to help you: → Assess your readiness level → Identify delivery risks and capability gaps → Receive tailored insights to strengthen your transition plan It covers 11 focused questions across resourcing, delivery structure, technical complexity and change readiness. 📌 Take the assessment in under 3 minutes: https://lnkd.in/eNXUk7qQ #Trillion #SAP #S4HANA

Every SAP programme we've worked on has a plan. Not every one stays on it. The difference rarely comes down to planning quality. It comes down to what happens when the plan meets reality: a dependency shifts, a data issue surfaces late, or a decision needs sign-off faster than the governance cycle allows. The programmes that stay on track are the ones where decisions get made at the pace the programme needs, not the pace the organisation is used to. That means clear ownership, fast escalation and a willingness to cut scope early rather than compress timelines later. None of that shows up on a Gantt chart. All of it decides whether the go-live date holds. What's the biggest threat to your programme's timeline right now? #S4HANA #SAP #SAPTransformation #DigitalTransformation

Every time a SAP programme starts slipping, we hear the same reflex: "let's bring in more consultants." Nine times out of ten, that's the wrong diagnosis. Look at the delays we've actually seen close up, and the pattern's rarely a skills gap. It's a governance one: no one owns the decision, approvals sit in an inbox for two weeks, scope keeps drifting because nobody's pushing back. Add headcount to a programme like that and you just get more people waiting on the same stuck decisions. We've written up what actually causes SAP programme delays, and how to fix it without adding a single consultant. Full breakdown here: https://lnkd.in/e6mjwzw7 #S4HANA #SAP #SAPTransformation #DigitalTransformation #CIO

AI doesn't replace capability. It exposes the gaps in it. That's what Harry Gordon and Andy Brown, an independent SAP Programme Director, unpacked in a conversation on SAP in the AI Era: what AI is actually doing on live SAP programmes, not what it's supposed to do. Andy's team brought in an AI-assisted delivery tool to design, build and test faster, with an expert architect in the loop. Projection: half the timeline, half the cost. By week four of an eight-week plan, they weren't halfway through the work. The tool had gone to people who didn't understand the development lifecycle, and the delivery plan hadn't been thought through. They stopped, rebuilt the approach, and got back on track. Still on course to hit that eight-week target. One of five takeaways from the conversation. Want to read more? Find the full blog in the comments below. #S4HANA #SAP #SAPTransformation

We keep seeing the same mistake from SAP leaders: treating S/4HANA as an IT delivery problem. It isn't one. The technology decisions are the easy part. Data models, integration patterns, cutover windows, all solvable with the right team. What's harder, and what actually determines whether a transformation lands, is who owns the decisions that shape the future operating model. Too often, that sits with IT and the programme office, while the leaders who should be setting the direction only get pulled in once something's gone wrong. A transformation of this scale is a leadership call, not a technical one. Get that right first, and the technology decisions become considerably easier. Where does ownership sit on your programme right now? #S4HANA #SAP #SAPTransformation

"We've done Fit-to-Standard, so we're ready." We hear this a lot. It's not quite right. A signed-off workshop is a milestone. It's not the same as being ready to migrate. Here are the four gaps that quietly derail S/4HANA programmes that think they're further along than they are. ➡️ Full breakdown on the blog: https://lnkd.in/eYGCegD7 #S4HANA #SAP #SAPTransformation #DigitalTransformation

GRC still gets treated as the thing you sort out once the SAP programme is basically done. That's exactly why it derails so many of them. Segregation of duties, access risk, audit controls: these decisions shape how the whole system is built. Bolt them on after go-live and you're not tidying up, you're rebuilding. We've seen programmes hit their go-live date and then lose months to remediation because GRC was never designed in, just checked at the end. Build it into the programme from day one and it stops being a blocker. Leave it until the end and it becomes the reason the programme slips. Where does GRC sit on your current SAP programme: designed in, or bolted on? #SAPGRC #S4HANA #SAP #SAPTransformation #CIO

Treasury sits at the sharp end of every SAP finance transformation. That's the thread running through Edition 04 of The Trillion Take. This month, Ollie Cavendish's take was joined by two treasury leaders writing in their own words: Maria Belen Marrades Casuscelli (Head of Treasury, Panasonic) and Anna Maria Tyszko (Associate Manager Treasury & ERP Project Lead, Pandora). Three companies. Three roles. Same argument each time: leadership is proven by delivery, not by visibility. Swipe through the themes, then read the piece in full. 📩 Edition 04: https://lnkd.in/edUDWuWG #S4HANA #SAP #SAPTransformation

Every SAP Programme Director says the same thing once Fit-to-Standard is signed off: "we're ready." A signed-off workshop tells you the design is agreed. It doesn't tell you whether your data's clean enough to migrate, whether the business has capacity to absorb the change, or whether your integration scope is actually understood rather than marked "TBC." Ready means your data, your people and your integration scope can actually absorb the change, not just that the design's been agreed. Full breakdown here: https://lnkd.in/eYGCegD7 #S4HANA #SAPTransformation #SAPReadiness #CIO