- The Well Built Solutions Newsletter
- Posts
- šš The case for the Review & Recommend project
šš The case for the Review & Recommend project
Read time: 6 minutes (Email newsletter originally sent July 2025)
Hey there! Ceci hereā¦
In Workday, progress usually means new.
New modules. New fixes. New releases.
But sometimes, the smartest move is to just stop ā
Breathe š§š»āāļø
And figure out whatās actually going on in that module š§
You know the one weāre talking aboutāthe module with the ticket queue from your worst nightmares.
The one no one wants to touch because no one really understands how it works š«£
You didnāt break it. But you did inherit it. And now you and your team are left trying to make it make sense.
In todayās newsletter, weāre advocating for the most unsexy of Workday projects: The Review & Recommend (R&R).
And why engaging this project might be the most strategic choice you make with your Service Partner all year.
Looking for Workday support in 2026? Join Well Builtās project waitlist š¤
š” What exactly is a Review & Recommend project?
You might hear them called āOptimizationsā or āTransformationsā, but we prefer to call them what they areāReview & Recommends. The name is honest, straightforward, and sets the right expectations from the start.
Because in this kind of project⦠no configuration gets done š±
Crazy, I know. You might be thinking āSCAM!ā
And, unfortunately, in some cases, thatās probably true (more on this below).
But done right, R&Rās can change the course of your organizationās Workday roadmap and radically improve your day-to-day Workday experience.
Hereās why...
A Review & Recommend is a thoughtful, structured deep-dive into a specific moduleās current state.
The goal is to comprehensively uncover:
 š Whatās working well
š Whatās lacking, missing, or simply unaligned to your business needs, and 
š What changes will make the most meaningful impact on your organization so you can move forward with confidence 
Think of it like a wellness check! The final deliverable is a full report of your chosen module, complete with a recommended action plan.
In todayās Workday landscape, these projects are more important than ever.
As the ecosystem matures, more organizations are years past go-live. Teams are operating in tenants shaped by quick fixes, shifting hands, and little to no documentation.
An R&R gives you a chance to pause, take a clear-eyed look at where things stand, and move forward with purpose.
š Is an R&R project for you?
If your team has repeat sentiments like:
- Should it really be this hard? 
- We donāt know what we donāt know⦠
- Whyās this thing always on fire? 
- Whatāre the best practices? 
- Itās just the way weāve always done it⦠
Then yesāa Review & Recommend project is probably exactly what you need.
Instead of treading water in the stormy seas of a frankensteined module, get yourself to dry land. Take inventory. Chart a course. Then, steer the ship.
A well-run R&R gives you all the information you need before investing more time and money into new (and potentially disjointed) configuration.
But not all R&Rs deliver on that promise.
š¬ Why R&R projects fail
Unfortunately, a lot of organizations walk away from their first R&R project disappointed.
Firms tend to treat these projects like filler work. They assign a lone resource with no clear methodology or support and ask them to āfigure it outā.
I know, because I was that Workday consultant.
In my first year, I was handed an R&R well before anyone wouldāve called me āseasonedā. Thankfully, I had a background in strategy consulting and built my own approach from scratch. The project turned out great, but I had to totally wing it.
Without consistent structure, the project becomes a gambleāthe process and deliverables are completely up to the imagination, skill level, and ambition of the consultant, which can vary drastically.
Hereās an exampleā¦
At the beginning of this year, we were chatting with a prospective (now current!) client of ours.
They were interested in an R&R of their Payroll module, but felt apprehensive. They had spent a nice chunk of their budget on this type of project before for their Absence module.
And, the final deliverable?
One. Single. PowerPoint Slide š³
They were left wondering:
- Was everything in the module truly looked at? 
- How do we action on this? 
They asked for clarity and got a shrug. A bad R&R still leaves you in the dark!
(We delivered a stellar project they were thrilled with, and got them that long-awaited clarity, ICYWW. š)
But it doesnāt have to be that way. If you decide to invest in one of these projects, make sure you know what āgoodā actually looks like.
š©š»āš³ The ingredients of a good R&R
A solid R&R starts with structure and ends with clarity.
If the firm you work with canāt explain their approach up frontāor if everything feels vague from the startāthatās a red flag š©
Hereās what to look for in a good R&R:
ā A clear scope
Every component of the module should be listed out. That includes:
- Module-specific configuration 
- Business processes 
- Security 
- Reporting 
- Touchpoints to other modules 
Nothing should be left to guesswork. The scope serves as your checklist to ensure you get a comprehensive review.
ā A defined timeline and phases
You should know:
- How long the project will take 
- What the major phases are 
- The participation thatās expected from your team at each step 
- When youāll receive deliverables 
Donāt accept black-box timelines. Hereās an example of our timelineā¦

Well Builtās Review & Recommend project timeline with phases.
ā Tempered expectations
Be wary of big promises. Your module might not be in that bad of shape after all! (Another reason we donāt like to call these projects āTransformationsā.)
Sometimes, the workaround you hate is revealed as the best option when stacked against the alternatives.
A successful R&R doesnāt guarantee youāll uncover 100 mind-blowing issuesāit guarantees clarity and peace of mind.
ā Recommended and validated findings
A good R&R doesnāt just point out problemsāit also highlights whatās working well. That way, your team knows what not to touch, and what can serve as a model for future configuration. We learn just as much from well built config as we do from addressing whatās not!
ā A detailed report of the findings
You should receive clear documentation of the WHAT and WHY behind every finding (not just a bulleted list).
The report should be written in plain language, include helpful screenshots, and be easy for your team to read without needing to call the consultant to explain it.
ā A tailored action plan
The recommended findings should be assessed and prioritized based on:
- Impact 
- Level of effort 
- Urgency 
Together, they should form a proposed action plan that fits your orgās capacity, skill level, and roadmap.
ā Trust in the process (and the people)
Even with all this structure, itās important to name the obviousāthis project is inherently a little subjective. Different consultants might surface different findings, and thatās okay.
What matters most is that the review follows a clear methodology and delivers a supported analysis with actionable workānot fluff.
If these expectations seem high, itās because⦠well, they are!
We hold ourselves to them. And we believe the quality of work you tolerate is the quality youāll keep getting. Just like hiring the right in-house team, you want to hire the right partner.
Letās make thoughtful, well-documented R&Rs the normānot the exception.
š§ Clarity isnāt sexy. Itās Strategic.
Review & Recommend projects arenāt flashy. They donāt end with a shiny new module or a fancy dashboard.
But what they do deliver is something most teams are sorely missing: clarity.
Weāve led a number of R&Rs now, and each time our method sharpens.
But make no mistakeādone right, these projects are a ton of work. Itās detailed analysis, painstaking documentation, and thoughtful prioritization.
We hopeāespecially for organizations deep in the throngs of postāgo-live muckāthat this newsletter sparks a shift! One that raises the bar for R&Rs and prioritizes clarity as a deliverable.
As always, thank you for being a reader!
Weāre celebrating you and your pursuit of a Well Built Workday š„³
Until next time!
Ceci & Mia
Co-Founders of Well Built Solutions
P.S. Loving the newsletter? Leave us a testimonial here š„°

Say hi š on LinkedIn ā @ceciblomberg, @miaeisenhandler
š Learn more about Well Built Library | Book a call | See a sample
ā¶ļø Watch the replay from the first-ever Well Built Webinar
š¤ Want to partner? Get on Well Builtās project waitlist here

Reply