Hard-won lessons from a decade of Adaptive Planning implementations — where projects stall, why they stall, and what separates the engagements that deliver lasting value from the ones that leave clients holding the bag.
After ten years implementing Workday Adaptive Planning, certain patterns become impossible to ignore. The technology is rarely the hard part. The difficulty lives in how projects are scoped, how clients are prepared, who owns the work, and what happens after go-live. Below are the lessons that have shaped how I approach delivery — and the places where, time and again, well-intentioned projects lose momentum.
Scoping Sets the Tone — and It’s Usually Broken
Adaptive Planning rarely earns more than a page in the SOW
On most large systems integrator engagements, Adaptive Planning is lucky to occupy a single page in a forty-page statement of work. It is treated as an afterthought. The consultant is then left to unpack what can realistically be delivered while reconciling the half-truths handed down from sales or technical leaders who scoped the deal years earlier. That gap erodes trust on both sides — with the client and with the consultant — during a negotiation that should never have been necessary had the SOW been complete from the start.
Put plainly: if I had to deliver some of these projects exactly as the SOW described, I’d owe my client team a Lexus. The scope and the reality are often that far apart.
Clients Can’t Envision What They Can’t See
Embed early, before the design hardens
Until clients see their own data in the system, they struggle to picture how the project comes together. Wherever possible, embed Adaptive Planning consultants alongside the client during the chart-of-accounts conversation. Once the financial data model and Workday build are in place, the ship has sailed — and so has the appetite to change anything.
Accept that clients won’t take the e-learning — and plan around it
In my entire career, I have seen a full client team complete the Workday Adaptive training before implementation exactly once. So let’s be realistic. Build knowledge transfer into delivery early, not at the midpoint or the tail end. A handful of topics reliably trip clients up: levels; the difference between sheets and reports and how to interact with each; version management; and sheet types — standard, cube, and modeled — and when to use which. The sooner these are addressed, the less confusion surfaces later.
Governance and Ownership Decide the Outcome
Settle data governance before the build begins
Encourage clients to establish workflows and data governance up front. You want to begin the build without spending billable time navigating the politics of data ownership or reverse-engineering complex business cases that have no documented workflow behind them.
Adaptive Planning belongs to Finance — with IT as a partner
Adaptive Planning is purpose-built software designed to be managed by Finance. That can be a hard truth for legacy IT teams entrenched in an IT-first posture. An IT-first approach tends to under-invest in the communication and model-configuration depth the project actually needs, while over-indexing on tactical requests — single sign-on, user setup, security. Those tasks matter, but they are not on the critical path to the heavier work of model design. Lose that lead time and you will most likely slip the go-live.
The most successful projects I’ve seen run on dual ownership: a Functional Administrator paired with IT. IT owns the deeper technical work — integrations, SSO, initial setup. The Functional Administrator handles user settings, troubleshoots integration failures such as mapping issues, manages versions, and adds cube accounts. Projects run IT-first, by contrast, tend to accumulate pain points.
Rethinking How the Work Actually Gets Done
Cadence should serve momentum, not the calendar
The default of one or two standing meetings a week is fine for scheduling and poor for momentum. Where you can, stagger the rhythm: a heavier first week — perhaps two two-hour working sessions — followed by a lighter week with a single short check-in. Spend less time in meetings and give both sides room to move the work forward. This is admittedly difficult for SIs juggling staffing across many projects at once.
And a candid note on sourcing: offshoring complex finance-modeling configuration rarely works well. Charging a multiple of a smaller SI’s rate for inexperienced “Workday-certified” consultants does the client a disservice.
Hypercare, Reimagined
Don’t balance the financials on the client’s back
Do not — and I mean do not — plug a project’s financials by parking an offshore resource in charge of hypercare. Do better with documentation, and hand the client genuine ownership of their new investment. Too much of the training material I see from SIs looks like the 1990s called and want it back. Do better: embed video, use tools that produce clearer illustrations, and prepare detailed checklists that let the client truly own their instance. Many firms promise a “two-in-a-box” model and fail to deliver it, because it’s simply easier for consultants to do the work themselves — which leaves the client holding the bag.
Use the Right Tool for the Right Job
Don’t force Adaptive Planning to be the ERP
As a degreed — and reformed — accountant, I say this with affection for my accountant friends: planning projects led by accountants often get too far into the weeds. Yes, the tool can be configured to do almost anything. The question is at what cost. Weigh the user experience and decide whether the juice is worth the squeeze before chasing every detail.
Let the ERP drive the granular actuals and plan at a higher altitude. There are several sound methodologies for balancing finance and operational views within Adaptive Planning, but the fundamental truth holds: the organization wants to see the bigger picture, not hyperfocus on details that, more often than not, don’t move the needle.
The throughline across all ten years is simple: technology delivers value only when scope is honest, ownership is shared, clients are prepared, and the handoff is real. Get those right, and Adaptive Planning does exactly what it was built to do.
