(If your browser is having difficulties displaying the video, it can be viewed directly on YouTube here)
Oracle have set an ambitious timeline for clients to have adopted Redwood in HCM by 25C, August-October 2025. The biggest change for many clients and partners will be in getting to grips with Visual Builder Studio customisation; a big jump for those familiar with HCM Design Studio, as the terminology and release best practice is very different from what we are used to.
Join us as we translate this new world into something digestible and in layman terms. We give context to these changes, show best practices, and outline our key learnings so far.
Agenda
- Backdrop of Redwood
- Roadmap and Strategy for a redwood project
- Identifying your project team
- Personalisation Helper tool and Redwood compatible features
- VBS Terminology
- VBS Best Practice
- Namos’ Lessons Learned
Speakers Bio
Danielle Evans – HCM Consultant at Namos Solutions, Danielle specialises in Core and Common Features, and has taken a lead in the first implementation incorporating Redwood into the design and build.
She comes with a background in client-side systems management having managed a systems team in Higher Education Institutions; during those years she led the HCM in-house function during a multi-pillar implementation at the point of hypercare and established a strong post-implementation support model.
Danielle has a deep understanding of the challenges and benefits of Oracle HCM implementations in public sector from both sides of the experience (client and consulting) and approaches projects with sympathy and understanding of the client’s needs.
