Your first 90 days as an HRIS Manager

Your first 90 days set the tone for everything that follows. Not because the business expects miracles. Because the business expects you to listen first, and judges the quality of your judgement by how well you do it. The HRIS leaders who get this right earn the right to reshape scope in month four. The ones who skip it spend year one cleaning up things they could have prevented.

A working timeline. Weeks 1-2: meet stakeholders, assess your team. Weeks 2-4: learn the tenant, map the inheritance. Weeks 3-6: ship one visible quick win. Weeks 5-8: fix the scope-creep problem you walked into. Weeks 7-12: align a 12-month roadmap and form the external partnerships you need. Below the surface, one thread runs through all of it: listening before leading.

Weeks 1-2 — Meet stakeholders, assess your team

Sit with leaders from HR, Finance, IT, Payroll, and the business. Ask two questions in every meeting. What do you need Workday to do better in the next 12 months? How will we measure success? Write down the answers verbatim. The alignment map you build from these conversations is the most useful document you will produce in year one.

Assess your own team in 1:1s. Four things to know before you make any structural decision. Who holds knowledge that exists nowhere else? Who is a quiet high performer getting zero recognition? Who is resistant to change versus just comfortable with the status quo? If a key person left tomorrow, what would break? Until you have answers to all four, do not change reporting lines.

A small tactic that helps new HRIS managers spot patterns earlier: keep structured notes from your first five to ten stakeholder meetings, then use AI to surface unwritten rules, political dynamics, and recurring themes across them. The important caveat: use an enterprise AI tool that meets your organisation's data security and confidentiality standards, not a public consumer LLM. Anonymise names where the analysis does not need them, and check the tool's input and output retention policy before pasting anything from a leadership 1:1. The point of the exercise is the pattern recognition, not the verbatim transcript, so a sanitised version of your notes does the job. Used this way, AI catches signals you would otherwise only see after month three. Used carelessly, it turns sensitive conversations into a compliance incident.

Weeks 2-4 — Learn the tenant, map the inheritance

Go under the hood before you touch anything. Walk through four areas with your team. Business Processes: run Hire, Change Job, Performance yourself end to end. Security: log in as employee, manager, HR partner, payroll, and check what each can actually see. Integrations: what is running, what is broken, what is held together by quarterly manual fixes. Data quality: run the key audit reports. You are not looking to fix things yet. You are looking for the shape of the mess.

Two questions most new managers forget to ask, both of which save you months. What was promised to this team that was never delivered? Where is Workday not the trusted source, and what shadow systems exist? These are the two questions where the team will test you within your first month. Payroll wants the integration they were promised two years ago. Finance is still running a master headcount in Excel because Workday "did not match" three years ago. The answers shape your roadmap whether you ask the questions or not. Better to know on day 14 than day 90.

What you inherit that nobody shows you

Every HRIS function comes with three layers of inheritance, and none of them appear in the onboarding deck. Undocumented customisations: config from years ago by someone who left. Cannot be changed without consequences nobody can predict. Broken promises: someone told a stakeholder team that a capability was coming. That was eighteen months ago. They are still waiting. They will test you. Shadow systems: Workday is technically the system of record. In practice, three departments keep their own version of the truth in spreadsheets.

Map all three before you commit to anything. The first promise you make in month one is the one you will be measured against in month six. Make it carefully.

Talk to end users from week 1, not week 3

The people using Workday every day know the real problems. Start with them in week 1, not week 3. And do not stop. One group almost everyone overlooks: the HR service centre. These are the people quietly fixing problems before management is aware they exist. Their inbox is the most honest dashboard of how Workday is actually performing.

Then work outward to HR business partners, managers, payroll specialists, and employees. Three questions. What works well? What is painful every month? What do you avoid because it takes too long or is confusing? Then ask the question most new managers never get to. What has been broken for so long that people have stopped mentioning it? Knowing where the buried landmines are before you start promising things is the difference between credibility in month three and a credibility recovery in month six.

Weeks 3-6 — Ship one visible quick win

You cannot earn the right to reset scope or present a roadmap without first proving you can deliver. Ship something small, visible, low-risk, in the first six weeks. A report that took two hours and now takes five minutes. A confusing process step that now has a clear guide. A broken integration that you owned and fixed. It does not matter how small. The team needs to see you can do the work, not just plan it.

The quick win also serves a second purpose. It teaches you the internal process for moving anything to production: the approval steps, the change-management board, the testing gates. Better to learn the internal machinery on something small than on the rebuild of a critical process.

Weeks 5-8 — Fix the scope-creep problem you walked into

Most HRIS teams become the "solve everything" team by default. Reset this early. Pick one responsibility that does not belong with HRIS and visibly change how it gets handled. Replace ad-hoc report requests with a catalogue plus office hours. Introduce an intake form for change requests. Distinguish "small change" from "project" so that nothing becomes a ticket by default.

Two things happen when you do this in month two. The business notices that your team has standards. Your team notices that you will protect their scope. Resetting boundaries after six months of bad scope is three times harder. Doing it now sets the operating model for the next two years.

Weeks 7-12 — Align a 12-month roadmap

By week 10 you have enough. Come back to leadership with a plan, not a list. A roadmap with clear outcomes, not 200 backlog items. The KPIs you will track against. The resources you need to deliver. This is the moment you shift from "new person learning the system" to "leader with a plan". The teams that skip this stay reactive for years. The ones that take it seriously become the teams leadership trusts with the next big bet.

A useful framing for the leadership conversation. You are not asking for approval of every backlog item. You are asking for alignment on outcomes and on the operating model that will deliver them. The detailed backlog lives in your team's planning, not in the steering committee.

External relationships you should not delay

Three relationships matter, and you should start building them in week four at the latest. Your Workday Account Executive. Share your roadmap. They can connect you to the right product teams, customer references, and roadmap signals. Build a real relationship, not just a contract conversation.

Your Customer Success Manager. Use them. Ask what other customers in your industry are doing. They are your internal Workday advocate, and they have data on what is working elsewhere that you cannot see from inside your own tenant.

Your implementation partner. You inherited this relationship. Evaluate it. Does the partner know your tenant well? Are they proactive about your roadmap or reactive to your tickets? Most importantly: does their capability match where you want to go next? Being loyal to the partner who got you live is fine. Staying with a partner who cannot take you where you need to go is a mistake.

Day 90 checkpoint — what you should have

By the end of 90 days, you should have. Proven you can deliver, not just plan. A clear picture of the tenant, the technical debt, and the shadow systems. End-user trust, because you listened before you acted. A map of the unwritten rules and political dynamics. A team that knows you will protect their scope. Leadership aligned on where you are going and why.

None of this is glamorous. All of it sets the tone for how the business sees HRIS for the next two years. The new managers who treat the first 90 days as a learning exercise rather than a delivery sprint end up delivering more, not less, by month nine.

What to avoid

Three traps that consume the first 90 days of inexperienced HRIS managers. Trying to fix everything in the first month: you do not have the context, the credibility, or the political capital. Pick one quick win and let the rest wait. Reorganising the team before you understand it: you will move out the wrong person within the first eight weeks if you do this. Wait until you have done your 1:1s and seen at least one cycle of real work. Presenting a 200-item backlog to leadership: backlogs are how HRIS teams demonstrate effort. Roadmaps are how they demonstrate leadership.