# Chris Goumas

Chris Goumas writes about managing Workday HRIS teams and systems, with a focus on practical delivery challenges for small and mid-market organizations. Chris Goumas's posts cover team capacity, system maintenance, AI adoption, and how to test new tools safely.

- Profile: https://b2binfluencer.marketing/creators/chris-goumas/
- LinkedIn: https://www.linkedin.com/in/chrisgoumas
- Topics: artificial-intelligence, hr
- Based on 23 dated posts, latest 2026-10-08

## Summary

Chris Goumas is most useful for practical Workday HRIS operations, team capacity, and grounded AI adoption for mid-market teams.

- Best for: A Workday-focused HR technology consultancy seeking thought leadership on HRIS delivery and AI agent adoption.
- Not for: A competing HCM platform arguing mid-market companies should replace Workday.
- Check first: Ask for recent LinkedIn audience data and results for comparable posts, including roles, seniority, and company size.

### Takeaways

- Approving time off and covering the work are two different decisions.
- Faster ticket closure can hide declining team capability.
- Run a narrow AI pilot instead of waiting for data to be ready.

## Main ideas

- **Approving time off and covering the work are two different decisions**: Goumas argues that teams called "small and mighty" often run on heroics that hide key-person risk. Executives read long hours as commitment, but a team that catches every ball inches from the floor is one absence, resignation, or bad release window away from an outage nobody budgeted for. Goumas's fixes are deliberate rather than motivational: one owner and one backup for the things that cannot wait two weeks, a one-page runbook, a locked intake process, and a partner already cleared through security and procurement before an emergency. Hustle is not a plan, and heroics are a poor measure of whether a system is healthy.
- **Faster ticket closure can hide declining team capability**: Goumas frames AI adoption around four separate risks, each with a different response. Never-skilling is when a person never learned a skill because AI did the task for them. Deskilling is when someone had the skill and reliance let it fade. Mis-skilling is when an AI error gets learned as fact. Automation bias is when someone trusts a plausible answer because checking it takes time. A scorecard built only on faster ticket closure can count declining capability as success, Goumas argues; rewarding the analyst who catches a bad recommendation matters more than rewarding speed.
- **Run a narrow AI pilot instead of waiting for data to be "ready"**: Goumas says client conversations changed their position. They had been in the camp that wanted the data foundation fixed before anything was built on top of it. Their objection is that "get the data ready" gives a small team no definition of done: how much, which records, for what purpose, and what counts as ready are all left open. Goumas proposes the reverse in some situations: a controlled pilot with one narrow use case, a small group of testers, approved sources, people who can verify answers, and no automated changes. The pilot then produces specific, traceable problems the team can fix.
- **Agents inherit your tenant, so someone has to own the consequences**: Goumas argues that AI agents show up inside your Workday tenant on the release schedule whether you ask for them or not, inheriting your security model, business processes, and approvals. That inheritance is both the advantage and the risk: if security groups are a mess, an agent inherits the mess and moves faster than any person could. They ask who checks what agents actually do and say the workforce consequences of AI belong to HR, not an IT tech-stack review. On adding outside agent platforms, Goumas puts the burden of proof on the added platform: use delivered capability first, and be clear that eligible external-agent calls can count against your Workday API entitlement, so paying another vendor does not cover the Workday consumption.
- **Most Workday tenants have outgrown their operating model, not broken**: Goumas says the honest diagnosis is usually that a tenant was architected for the company that launched it and nobody resourced the operating model to evolve. Job architecture goes untouched since go-live, security roles get patched on top of patches, business processes still describe a company that has since had layoffs, reorgs, or acquisitions, and data quality slips quietly. Their prescription is a reset in sequence: audit job architecture, clean up security roles, rebuild business processes, fix data quality at the source, then build the four or five reporting hubs and KPIs leadership will actually use. Foundation first, new SKUs second, adoption metrics third. Goumas is skeptical of adding modules to a base that was never maintained.
- **The platform is moving faster than mid-market teams can absorb**: Goumas argues that Workday's platform expansion and the headcount available to absorb it are diverging. Large enterprises can assign dedicated Extend teams, integration architects, and data engineers, while mid-market and smaller companies may have one studio integrations person already buried in EIBs, release testing, and a ticket backlog. Goumas calls that difference a canyon rather than a skills gap, and warns that it widens with each release. Their advice to a mid-market HRIS director is not to chase the whole platform: understand what Workday Build is, catalog the current state, pick one small use case, be honest about the bottleneck, and watch the Flex Credits consumption model because it changes the budget math.
- **When choosing an AMS partner, hourly rate is not the cost**: Goumas argues that shopping managed services by hourly rate is a trap: the cheap rate often comes with junior consultants who take longer, unfamiliar assignments where someone learns your configuration on your billable time, and pod rotation that makes you explain your setup every time. They say to measure total billable hours to resolution, real experience in your specific modules, how long the team stays together, and whether the same people can carry their knowledge into project work with no ramp-up. In Goumas's framing, the best model is the same senior consultants on your modules, because the learning stays with your team and your budget absorbs the result rather than the hours.

## Work to read

- [Are you an HRIS One & Only?](https://www.linkedin.com/posts/chrisgoumas_are-you-an-hris-one-only-they-are-rare-activity-7498373688204058624-NIc6)
- [Your HRIS team closed MORE tickets and became LESS capable](https://www.linkedin.com/posts/chrisgoumas_your-hris-team-closed-more-tickets-and-became-activity-7511410849669066753-0uWQ)
- [You left the Workday HRIS team out of the planning meeting](https://www.linkedin.com/posts/chrisgoumas_you-left-the-workday-hris-team-out-of-the-activity-7509228995436056576-DIvB)
- [Hey Dir HRIS...your Workday AMS partner quoted you $169/hour](https://www.linkedin.com/posts/chrisgoumas_hey-dir-hrisyour-workday-ams-partner-activity-7493300276548784129-6vnC)
- [Workday Data quality - Forget it. Jump straight to Agent & AI testing](https://www.linkedin.com/posts/chrisgoumas_workday-data-quality-forget-it-jump-straight-activity-7508211655915327489-FPyf)
- [I got stumped this week by the simplest Workday question](https://www.linkedin.com/posts/chrisgoumas_i-got-stumped-this-week-by-the-simplest-workday-activity-7430699547254775808-iTD5)
- [Workday - KEEP or KILL?](https://www.linkedin.com/posts/chrisgoumas_workday-keep-or-kill-should-we-go-activity-7458649113010626560-ys7k)

## Brand relationships

- **Workday** (mention)

## Partnerships

No partnership or sponsorship offer appears in Chris Goumas’s posts. Their public posts offer vendor-agnostic analysis of Workday HRIS operations, not branded placements or published ad formats; none carries a sponsorship disclosure, rate card, media kit or partner offer. Commercial references describe how Workday AMS and staff-augmentation firms operate — junior versus senior consultants, pod rotation, billed hours to resolution, knowledge transfer, pre-vetting a partner through security and procurement, and no-retainer ad hoc support — and read as first-hand commentary on the consulting market, not an offer. One post invites readers to “compare notes” on a Workday reset, a conversational prompt rather than a published service or partnership route. Buyers planning a paid thought-leadership partnership should confirm terms directly with Goumas; the posts do not verify a format, deliverable or rate.

## Alternatives

- Seena Mojahedi: A Workday consultancy focused on tenant health may find Mojahedi’s post on governance after a cleanup and his breakdown of issues beneath AI-ready data a closer fit. Examples such as conflicting reports, unexplained configuration and integrations that no longer serve the business give diagnostic conversations a concrete starting point. The governance story also makes the case for protecting time to keep fixes from eroding.
- David Blonski: Choose Blonski’s perspective for a campaign making the case for replacing legacy enterprise software rather than improving a Workday environment. His posts argue that separate, domain-specific AI stacks create cost and complexity, and frame AI as a way to reduce operational friction without reducing the workforce.
- Ahikam Kaufman: For finance leaders, Kaufman’s posts offer a relevant angle on AI-agent economics and governance. His questions about changing direction after deployment focus on dependencies, portability and where financial logic and audit history reside. His post on token costs connects model choice and agent activity to controls, traceability and ongoing operating costs.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/