I’ve already blogged about the Key Note from Chris Leone that kicked off the HCM Cloud Centre of Excellence Customer Summit. If you haven’t seen it, check it out here. The main themes for the summit were AI and Redwood. The ‘Jump Into Redwood Session’ with Laura Froehlich and Todd Wall was extremely interesting and a good follow up to the key note on the first day.
Having recently completed my Prosci Certified Change Practioner qualification, I was delighted when the session kicked off with ‘Why Change’. I think this question is often skipped because it’s a mandated change from Oracle, but as there are so many benefits to moving to Redwood, it’s a really important question. It’s true that change can be scary and users and organisations can be reluctant to do so, but there are so many advantages when you embrace that change.
One of the key benefits is the integration of AI. It’s so fundamental to the way businesses anticipate operating, a number of customers have added objectives to their team to incorporate AI into their daily work. Oracle are making it so much easier to achieve this goal by embedding AI and AI Agents into the Redwood applications. Whilst not everyone wants to use AI, Oracle have incorporated in such a way it can appease both those who do and those who don’t want to use AI. For those who don’t want to use it, it is delivered switched off. For those that do, a quick change to the page in VB Studio, involving ticking a box and publishing it and you have AI embedded in the particular page. It really is that easy! It should be noted that AI functionality is not available to all users, it depends on the server / region the organisation is in. Those in the UK Government Cage cannot access it at present, but it will be available in 2025.
When talking to customers about the new features being delivered in a particular quarterly release, they often only apply to the Redwood versions of the pages. So, if you want the latest functionality, switching to Redwood is your only option. The final key benefit is the improved performance Redwood brings. This wasn’t just a ‘lift and shift’ project to create the Redwood pages, they were completely rewritten from scratch in a new toolset.
One of the stand out parts of the session was the 5 myths about Redwood. Some I’ve heard before and some I haven’t, but I thought they were interesting and I wanted to share them with you. The first one about the profile options being automatically switched on when reaching the the quarterly update uptake date is actually a complex one. Whilst the quarterly release date is when it is mandatory to have made the move, it’s not actually delivered switched on. If you raise an SR after the uptake date, the analyst will advise you to move to the Redwood page, as the non-Redwood pages are out of support. One key announcement during this session was that in 25B, Learn will be delivered switched on in Redwood and in 25C, Timecards will be delivered with Redwood switched on. Whilst this isn’t on the uptake date, it’s 2-3 quarters later, it does mean that at some point Redwood will be automatically switched on for all organisations.
The second myth is around the product not being ready yet and therefore there is no point in starting work on testing and personalising pages. Whilst new features are constantly being released in Redwood, the uptake date is just that, the date you should have made the move for that module, it’s not a date to start making the move. The third myth is that it’s a massive and complex reimplementation. The move is only complex if the organisation chooses to make it such. It is possible to switch on the Redwood pages, make the appropriate security changes, migrate personalisations (using the Personalisation Helper Tool), test and deploy. If you wish to make it more complex by revisiting features that weren’t previously implemented or fundamentally change your existing configuration, this is when it becomes a reimplementation.
The fourth myth is that Redwood is optional. It really isn’t, if you wish to continue being in support, you must make the move. As announced on the session, eventually Oracle will force Redwood on users by delivering it switched on. It’s better to do it early so you’ve got time to test and update users as once it’s automatically applied, it will be too late. The final myth is not one I’ve come across, but that organisations are going to wait until ERP and SCM is available in Redwood, before moving HCM over. It might be because I’ve been regularly discussing the disparity between the timelines of ERP and HCM in terms of Redwood, that I haven’t heard this discussion before. With regards to SCM, Self Service Procurement is mandatory in Redwood from 25C, so this is on a similar timeline to HCM anyway.
The final item I want to share from the session is the Redwood Adoption Checklist. This is really helpful to remind us all of the steps involved in moving to Redwood. If you’re anything like me, you’ll love ticking items off the list!
Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines
K8 Mead 