USER SUCCESS/ WOODSTREAM
Quick Wins and the Harder Work Behind Them
stream’s thinking about governance. It shifted the conversation from simply adding a tool to reexamining how deci- sions were made, tracked, and enforced across the program. Woodstream had been a tradition- ally run organization, with established processes that teams were comfortable with and reluctant to change. “We were set in our ways,” he reflects, acknowl- edging that the familiarity of legacy processes often made customization feel easier than reexamining how the business operated. SAP Cloud ALM, had it been in- troduced earlier, could have brought more structure during early design discussions, for reinforcing standard processes and documenting decisions more consistently. “We’re practically being alerted now if there’s a system misconfiguration or a trend in memory or disk utilization — and we’re addressing it ahead of time.” Today, the team plans to use features such as custom code analysis to evaluate existing enhancements and determine which ones truly add value, and which ones should be retired in favor of stand- ard capabilities. Woodstream’s journey also under- scored a key reality of running SAP Cloud ERP Private under RISE: respon- sibilities shift, but they do not disap- pear. Lightner notes that while SAP manages the underlying infrastructure, Woodstream continues to own sys- tem cleanup, configuration discipline, and day-to-day governance, and SAP Cloud ALM helps clarify when the team should act internally versus escalate to SAP or partners.
lished as the first operational use case. The impact, he says, was immediate. Certificate expirations were detected be- fore they caused outages. Alerts replaced surprises. Critical incidents dropped sharply. “Now, we’re being alerted im- mediately if there’s a system miscon- figuration or a trend in memory or disk utilization,” Lightner says. “We’re ad- dressing it ahead of time.” “That is because we have this single pane of glass view where we can jump in and quickly dive into system metrics and KPIs to see if there are any immedi- ate actions we need to take,” he adds. Beyond certificates, SAP Cloud ALM gave Woodstream something it had lacked since go-live: a dependable op- erational view of its SAP landscape. The Basis team could quickly see whether development, quality, and production systems were up, identify performance bottlenecks in SAP Fiori apps, and vali- date or refute user-reported outages with real data. Lightner says that visibility now ex- tends to executives as well, with reports showing uptime, performance trends, and how issues are addressed before they escalate. SAP Cloud ALM also delivered tangi- ble operational credibility at this stage. IT moved from reactive ticket handling to data-driven conversations with busi- ness and executive stakeholders, a shift that strengthened trust across the or- ganization. Lessons Learned: Timing Matters With the benefit of hindsight, Lightner is clear that SAP Cloud ALM’s greatest missed opportunity was timing. Hav- ing the solution in place before go-live would have provided clearer guidance during fit-to-standard activities and likely helped the team avoid some customizations that were later ques- tioned. “We have a decent number of customizations in our system that prob- ably weren’t needed,” he reflects. That realization also reshaped Wood-
Looking back, Lightner describes the initial rollout of SAP Cloud ALM as sur- prisingly straightforward. The immedi- ate payoff was also clear: faster visibility into incidents, fewer surprises, and a stronger ability to intervene before is- sues escalated. “The harder work,” he says, “had less to do with technology and more to do with ownership.” For years, operational issues, even those rooted in business processes, of- ten landed on IT’s plate. “We were very used to passing business issues off to IT,” Lightner recalls. “For example, if a sales order was created with a discrepancy — a customer discrepancy or a pricing dis- crepancy — it would often get passed to our IT team, and then we were the ones responsible for fixing it.” That mindset is now evolving. Teams are beginning to take greater respon- sibility not only for their transactions, but also for the processes behind them, and for understanding how proposed changes may affect other functions. This shift is gradual, but Cloud ALM is helping make it visible and manage- able by providing structure around how changes are documented, tested, and as- sessed across workstreams. For organizations preparing for SAP S/4HANA Cloud ERP Private or already live, Lightner’s advice is straightforward: do not wait. “Learn about SAP Cloud ALM early and implement it sooner than later,” he says. “It’s easy to set up, and the earlier you adopt it, the more value you’ll get — especially around documentation, governance, and complexity reduc- tion.” Woodstream’s journey shows that Cloud ALM does not have to be perfect or comprehensive on day one. Even a focused deployment can stabilize oper- ations, reduce risk, and create momen- tum. Over time, those tactical wins can evolve into strategic capabilities.
32
Made with FlippingBook - Share PDF online