Workday's new product head hopes he can make you like Workday

Over the last 20 years, Millions of people connect with families. they didn't know they had. whose face looks like mine. see someone else eyes look like mine So what happens to all the genetic data for all those Americans if the company goes away? That's this week on Explain It To Me. New episodes every Sunday, wherever you get your podcasts.

Hello and welcome to Decoder. I'm Eli Patel, Editor-in-Chief of The Verge, and Decoder is my show about big ideas and other problems. Today I'm talking with Garrett Kazmaier, the brand new President of Product and Technology at Enterprise Software Company Workday. Dakota listeners probably know the name Workday. A lot of companies use its platform to run HR and finance, which the suits have started bundling up into a phrase they call human capital management.

I invite you to have whatever feelings about that you want. Anyhow, if you've been applying to jobs lately, you have almost certainly run into Workday. And you are almost certainly frustrated with it. I mean, I'll just say this from the jump. It's rare that enterprise software executives come on this show. because it's a guarantee I will ask them why everyone hates enterprise software and what they're doing to fix it. Workday is no exception.

Last year, Business Insider published an article literally titled, Everybody Hates Work Tech. Now, Garrett's new on the job, maybe a little bit braver than most, and to his credit, he came on Decoder and he took the heat. We spent a lot of time talking about what enterprise software really is, what it does. and why all of these tools have a reputation for being so deeply frustrating for so many people.

As you'll hear, the heart of this conversation is the major tension that exists between the idea that software is a tool that accomplishes some work and the idea that using a software tool is the work itself. and making that even more complex.

Everyone experiences software like Workday in totally different ways across a company. I mean, just think about it. For most people at work, Workday is just a database or a series of forms that are required to fill out to file expenses or log a performance review. For the people who actually work in HR and finance, using Workday is a huge part of their actual job. It might be their only job. And then for the C-suite, who make a lot of decisions using data generated by tools like Workday,

They might never actually use the software at all. Instead, just looking at reports other people generate from the information in the database. This is tricky stuff, and as most companies manage those tensions and balance those trade-offs, well, user experience falls to the bottom of the list. Which is why most of this software is so bad. You will not be totally surprised to hear that Garrett's solutions to a lot of these issues is to use AI. After all, Workday now calls itself an AI platform.

So I really wanted to know what role Garrett thinks AI will play at work, and if simply letting an AI fill out all those forms for people might make things better, or alternatively just result in bad data all through the database. And I really wanted to know how comfortable he was letting AI make decisions about finance and HR, because AI systems can have a lot of bias built into them. That's something lots of companies, including Workday, have already faced lawsuits.

Look, I told you, there's a reason enterprise software executives don't often come on the show. So credit to Garrett for sticking in there. I think you'll like this one. Okay, Garrett Kazmaier, Workday's President of Product and Technology. Here we go. Derek Casemire, you're the president of Product and Technology at Workday. Welcome to Decoder.

Thank you for having me, Eli. Excited to be here. I'm excited to talk to you for a variety of reasons. One, enterprise software executives don't often want to come on a show because I just asked them about the nature of enterprise software. So you're very brave. Thank you for coming on. And then second, you're the new guy. You just started in March. So you don't have to defend all the stuff that other people did. You can just be honest about it.

Exactly. And maybe your chest don't invite so many of enterprise executives. So I don't know. Maybe I can lure some more in. My threat is always that we all just use the software together live. But it's an audio podcast. Don't worry. We're not going to do that today. Workday is one of those pieces of software that maybe everybody encounters in the course of their career. You apply to a job. Workday is the interface. You're at a job. It's your finance system.

Human capital management is, I think, what we call it now. We're doing our performance reviews. How do you think about Workday? What is it? Yeah, you know, it's that incredible system that helps organizations, you know, on the one side, you know, manage their people and manage their money, which is great, you know, well, two of the most important assets our corporation is built upon.

But I think more importantly, like what you have said, when you think about everyday work experience, it's the systems that everyone touches, everyone interacts with.

And I think it makes a huge difference in having a great work experience and ultimately a great personal development and building a great career. So yeah, it's a system of work and it's very exciting to be here. There's a lot of... companies that want to describe themselves as the backbone of how you might do we had web service companies come on, Squarespace, come on and say, we're the operating system for small businesses, right?

book the class or you book the auto mechanic and then we'll do the billing and finance. Workday is also expressed like that in some way, right? You've got people, you've got money, they're moving through your system, they're spending the money, you're tracking what the people are doing and if they're performing well. Do you want the big picture of we're running the entire business in Workday? I think that's kind of an archaic way to think about systems and people.

because enterprise software is an ecosystem. Organizations are large and touch many domains, and people and money is important, but there is also customer, right? There is service. There are so many things, right? There are so many things that makes a company. There are so many things that make a work experience.

I'd argue that, you know, back in the old days, right, when you look into the legacy enterprise software systems, right, that they had this idea of that perfectly walled garden and, hey, there's going to be one door, you know, you enter in the morning and you're going to stay in that door. We're going to give you what that system has to offer. And that's it, right? And I think today's reality is that

It is not reflective of what makes a great enterprise software stack. You have a multitude of vendors offering different capabilities and you have to compose them together. reflect you know what really is important to your company and then secondly and i think it also It's about the work experience, right? You know, from people bringing in their own devices to they bringing in their own AI models, you know, more often than other, their own AI coding experiences. Meaning that...

They also have way more agency about the systems they use and the systems they expect to use, right? So you have collaboration and productivity, and that's something very specialized. enterprise systems for all sorts of purposes and I actually think it's about an intelligent ecosystem and being part of, I would describe it as an enterprise software fabric if you will. It is really important that vendors like Workday work with other vendors in the industry.

build that system so that customers can use them in orchestration without having that kind of ridiculous idea, right? You get everything from Bonnet and you have to be happy with that. I mean, how would that work?

I mean, you have a long career in enterprise software, but that is a trend across every enterprise business product that I've ever encountered, where you start with one part of the business, and then the line of our news is we want to be the operator. We want to take everything. And it sounds like you're just totally against it.

I think I'm totally for a vibrant software ecosystem. And if you think about it, I think it starts with an operating system. I think that's a great metaphor, but it also... It's also something that I think we have to evolve, right? You know, back in the old days when we said operating system, it was this monolithic piece and everything had to run on it. And then came along that and suddenly, well, what you had on your operating system...

was not the only thing that you could use when you were on your device, right? Because you could access web services and online services and suddenly... I would say, when you say operating system, what is the operating system? You might say... well, it's a specific software platform and only the things that run on it are allowed, right? And I would say, well, you know, I guess the operating system today is the browser and everything that, you know.

relies on HTTP as part of my operating system ecosystem. And in the AI world, you might say, It's an operating system that is defined by MCP, Modern Context Protocol, and we have an orchestration of agents. I do think, you know, operating systems are important because they define actually how... an ecosystem works they define standards and they define um very important shared interest you know security being one of them right um so those are all things that

no one would want to give up upon. But I don't think there are single source, single vendor, monolithic pieces anymore that just create one experience. I would say it's a dated way of thinking about enterprise software, actually. There's a real push and pull here, and there's a reason I'm starting in this kind of esoteric space.

I think a lot about what work is. Like, what are we all doing? And in the age where, you know, there's a big push and pull between remote work and in-office work and what those experiences are. So much of our jobs just every day is using software. You and I are talking right now through a piece of software called Riverside that is like quite cranky, but like on one very basic level, my job is just using Riverside.

And the things I can do at my job are limited in some ways by Riverside. They're enabled in huge ways by the software existing. And you see that with every kind of enterprise software. Workday, there are enormous numbers of HR and finance professionals who show up to work every day, and what they do is they use Workday.

in one way or another. There's executives who receive reports from Workday, and their job is just evaluating the information Workday has compiled for them and then making some decisions. How do you see the role of the software there? Because what it looks like and how it works and what it's for is all pretty dependent on the fact that some people's jobs are just using the software.

it's an interesting way to think about a job right because when you just said right when you said it's my job to use riverside i actually thought Maybe that's not true. Maybe your job is asking powerful questions and talk to many people and creating a show that engages listeners. And Riverside, the software piece that you have just mentioned, that is just something that allows you to do your job really well. I think the same applies when you think about Workday.

They have important jobs to let dry to hire a great candidate. Once they hired great candidates, they tried to onboard them and train them in the way our company works. They want to build thriving organizations that let people have a really good work experience. They want to manage performance. they want to reward and recognize people And those are the jobs on the HR side and the finance side.

as simple right you ship products you want to write bills and you you have to pay bills and you want to create you know a compliant profit and loss statement and you want to be financially responsible and viable in the long term and manage your cash position and so forth And those are the jobs, right? Now, you know, basically the question is, you know, what do you have available in terms of tools and software that allows you to do the job in the best possible way?

And that's the core of Workday. Workday says that for the jobs that you have, which are software independent, which are emerging from the very core thing that you do as your value creation. We're gonna give you... the best services and products to do everything related to people and money.

I think it's a very important focus to get this straight because sometimes I do think people get confused specifically in technology. AI is a wonderful example of that, by the way, right? Because now some people think... maybe the job is ai right maybe that's my job to do something with ai and if there is a

a certain thrill and excitement that goes with that right but ultimately there is a reason when you look at studies right you know for instance stanford has that ai index survey and you know it's a it's a beautiful 400 page read on the state of the art with AI. And part of that survey is enterprise leaders get asked about their returns on their AI investment, right?

The vast majority said AI gave them less than 5% top-line increase and less than 5% bottom-line efficiency. You wonder, right, with all of that investment, how can that be? And I think ultimately it's because there is a confusion that some people think. Maybe my job is the eye, but actually it's not, you know, the job is.

what you're trying to do for your business. And AI may be a powerful way for you to do this job better. And for software vendors, you know, it's the same, right? How can we help people manage their money and people better through AI?

and being focused on the real job versus on the technical means that facilitates a certain way of doing that job. I saw a similar survey from IBM where they surveyed CEOs and the CEOs, the results were only 25% of the AI projects had returned. So we're in this place where everyone's spending the money. You guys are spending the money on AI. We're going to talk about that. And no one knows why. I'm curious. I'm sure you have an answer. But I see that piece. Then there's the other piece of AI.

The reason people are investing so much money in it is because maybe the AI can use the software. Or maybe the AI will fill out the forms or do the, you know, this is the big promise, the AI will do the boring stuff. Workday, I think, for a lot of people is expressed as the boring stuff in their job, right? They're filling out experience reports or whatever. Or you have all the way up to agentic AI, which is actually doing stuff and making decisions.

How do you see that interaction? Is AI going to use more and more of Workday for people? you know first of all i you know I would say the workday is the exciting stuff. I appreciate that you have to say the workday is the exciting stuff. Because I think sometimes when you say what's the exciting stuff, I actually think I was...

Well, you know, like you said, I worked in enterprise software, you know, in my entire career, but actually all of the enterprise software businesses that I was a part of, they're people businesses, you know, like 100%, right? You know, you drive all of your work through and with.

people and teams right so managing that growing and managing people you know that that's you know that's an exciting part of the job and and workday is you know that system in which you make that happen so this is why i'm saying it's the exciting stuff for me workday is more than doing a ptr request can i ask you about this managing people is the exciting part of the job sure somebody who manages people on their days i agree there are days i disagree i don't think about this software as the man

Right. And maybe I just work in a creative field and our conversations about management are very different. But there's not a place where I'm like, I'm going to use this software and that will accomplish a management. It's much more. I've accomplished the management tasks, and now I need to record it in the software just so I remember what happened. We have a record. But there's a confusion there, right? I think...

Whether or not what happens in the database is real life is maybe the central confusion of the entire tech industry across the board. Maybe the central confusion at the highest levels of our government right now. But how do you see Workday closing that gap, if at all? Is it even possible?

I totally think it's possible to close this gap. I see us having closed that gap and increasingly closed that gap in certain domains. But I completely agree with you, right? Work is so complex and it happens in so many ways. Like I said earlier, it's not that it's all happening in one system only, it's an ecosystem. So I completely agree with that point. And some of the work is even offline, like you said, talking to someone, as simple as that.

But there are domains, for instance, like in the recruiting space. For instance, how do I build recruiting campaigns? How do I interview people? When I interview people, how do I select candidates that are best fit for the job? something more profound than pedigree but you know skills for instance right and skills that they have shown or skills that i can infer those are

actions. This is work where work genuinely happens to a significant degree in a system like Workday. So it may not be happening everywhere. I agree with that. and maybe it shouldn't even happen, you know, for everything everywhere, but there is a significant portion where professionals

actually do their job right in these systems and that's why I think it's so important to get them right. I haven't had to use Workday in a long time so to prepare for this interview I watched a lot of Workday training videos on YouTube. Amazing ecosystem of Workday training videos on YouTube I have to say. And it just occurred to me as I was watching some of this stuff that Workday is expressed to people.

as a database, like very sort of openly. It's a database or maybe a spreadsheet and some other of the interfaces and, you know, people applying to a job experience it as a series of forms to be filled out.

Again, when I'm talking about like you use the software to accomplish the task, a lot of the task is making sure the database has the right That runs sort of headlong into AI, right? Now you've got people using AI to generate the information for the database or you've got an AI system that's going to look at a receipt and figure out what it is and put it in the right fields. And there's a real... there's like a new kind of data

Where you're definitely going to get all the fields filled in. There's one thing generally I can do. It's fill in the fields with little effort. But it might be hallucinations. It might be garbage. It might be worse than if a human didn't fill out the field. How are you thinking about that?

what you describe as um is a question of maturity actually of maturity in both ways both technology and use you know ai is undeniably the most profound change in technology. I think we are just living through the beginning of a renaissance of what AI can deliver. In any domain, material science, medicine, enterprise software being just one of them.

People are solving problems in incredible ways, you know, with the use of AI, right? And I, as a person, right, you know, between you and I. Humankind has big challenges, very big challenges, and I think it's a wonderful opportunity to have broken one of these big technology boundaries on reasoning and judgment and knowledge compression. and being able to use that on virtually any domain that exists.

That is incredible. But what you just spoke about, right, is the flip side of that, right? It's new. The reality is that, you know, we have intuitions about it, right? We have an intuition that, you know, a computer program is right because it's deterministic, right? So there is an intuition that goes alongside them when we use a computer and when you talk to a person

That is different, right? Because we know that, you know, we have biases, we get stuff wrong, and there's a different type of intuition that we have than what we expect a computer program to do. And now we have these generative AI models, and like you have said. They're probabilistic, right? They're not deterministic in many ways. And even very subtle things change their behavior and things that we wouldn't expect them to do, right? It was just, I think, last week or the week before this.

outcry of the latest open iron model and you know it's uh i think it was called the sickle fancy of it right because because it was too nice, right? And it was actually a few small changes which dramatically have changed the behavior of the model, making it too nice and not really helpful anymore.

So what you just spoke about, right, when you think about AI specifically in enterprise context, I think the big point is that AI gets you to a lot of results really quickly. You know, it's so powerful. In many ways, It is really shallow. But in the enterprise space, for instance, here today, we take one of these very powerful models.

We give it a really good prompt, you know, that is reflective of a business problem. The model gives us something and it looks, you know, roughly good. We say, oh yeah, we got it solved, right? We are happy about that. But the reality is when you actually want to make it work with accuracy expectations that you need to have in order to be used in a professional context or that someone makes mission critical decisions upon or in cases which is very important where someone Cannot correct the model

in a direct way. Coding is a good example. Why is coding successful? The model gives you something back in a modality that you understand as a coder. You know what the model is doing. You see the code. You have a chance to lean in. That's why it took off so quickly, right? Because you basically spoke the same language with the model and there was a big corrective.

In an enterprise system, what you have said, you've got to fill out this complex form for maybe a process that you don't even fully understand yourself, and it has language which is legal. compliant that is alien to you and the model is doing something. How do you know? we need to take a quick break we'll be right back

In today's business world, trust matters more than ever. Whether you're a startup founder navigating your first audit, or a seasoned security professional scaling your GRC program, Proving your commitment to security has never been more critical or more

That's where Vanta comes in. Vanta is a trust management that helps businesses automate security and compliance, enabling them to demonstrate strong security practices Vanta automates up to 90% of the work for over 35 in-demand security and privacy frameworks like SOC 2 and ISO 27001, as well as the latest European framework AI Act, and Dora. Join over 10,000 global companies like Flow Health, Synthesia, and Alica Bank, who use Vanta to manage risk and prove security in real time.

Go to vanta.com slash voxpod to meet with a vanta expert about your That's vanter.com slash foxpod.

We're back with Garrett Kazmaier, Workday's President of Product and Technology. Before the break, we were discussing how software fits into the nature of modern work, and what that might mean for the relationship people have with platforms like Workday. Now I wanted to ask Garrett the decoder questions, especially because he's only been at the company for a few months. He's got really fresh eyes when it comes to our big themes around structure and decision making.

I would be a little more reductive. I would describe the problem here as garbage and garbage. The promise of so much enterprise software, particularly HR, finance software, is you just had more information. you would get better decisions. If everyone would just fill out all of the fields, right? If only everybody would just fill out the software correctly, we would have better, perfect real-time information about the business, and then we would make better.

And what AI is giving, maybe not built into Workday, but just in general, that people with a chat GPT app on their phone can now definitely fill out all. Well, 100%. You already see it in job applications, right? People are applying to a thousand X more jobs than they were before because they can just fire a copy into these job applications from Chachi.

And now the systems are overwhelmed with irrelevant... right and so you've got garbage in what on earth like how do you solve this problem in the context having to turn that into actionable information.

It's two points, right? And I do want to go back to, you know, quickly on what I would describe as the, you know, the challenge of shallow enterprise IP before we get to what you just said about, you know, how do we cope with now the new... behaviors that are emergent with the use of AI. I would actually challenge what you have said, right? Models get it wrong a lot. You know, specifically when you talk about something which is not in the public domain. So we have public knowledge, right?

And models are extremely good at compressing this knowledge and that they're terrific. Who would have thought, right? I think everyone was surprised in 2022 then. when it really broke through and how powerful it would become with actually a very simplistic mathematical model. That's the mind-boggling insight, right? The math are simple. It's just applied at volume and it produces these incredible results. You have now these PhD level models.

coming into an enterprise context and showing up for the first day at work. They know nothing about the intrinsics of an enterprise, their proprietary data. You spoke about a database.

This is nothing which is represented in the knowledge base of that model. And yes, some of it is emergent, meaning that without really being trained with it they are reasonably good and doing something with it but the bigger point being is to get it wrong a lot so one side of when you ask what's worth they doing is actually taking these models and making them do something valuable in an enterprise context. You know, just something as simple and it connects to what you just spoke about.

Making sure you are selecting the right candidates for a job. That is a non-trivial task because you need to understand job requirements, behaviors and job applications. you need to basically train and specialize a model, and not only a model, actually a system, a set of models to do that with high accuracy of your reviewing contracts, right? Contracts are... And many times using language terms and have implications, which again are not existing in a public domain, so you have to train a model.

to basically understand enterprise contracts and apply them in a system like Workday. So I think that's Nick. And right now in San Francisco, we have autonomous cars driving around here. I think that's an important insight, right? For something to be used in a mission-critical domain. It needs to work all the time, right? An autonomous car is not viable if it only works 99%, right? Would you use it? I wouldn't use it. There's a lot of Tesla owners out there who have made a difference.

Well, I'm not even going there, right? I know a trick question when I hear it, so I'm not even going there. But way to work needs to work 100% of the time. And doing this in an enterprise context is heavy lifting.

The second thing that you have said is that of course both AI behavior changes in helpful and unhelpful ways. I use AI a lot to research and it's awesome because I have all of this intelligence on tap available to do research. And it's also being used in unhelpful ways, like you said, for creating content spam and unhelpful data signals.

which are overflow systems. The good thing, though, is that this is always a balance, right? There's a constant balance between you know misuse abuse and protection meaning what is the antidote to what you have just described is that if bots generate applications or forge expense lines and try to trick the expense system. You use AI models to also counter that, right? And as it turns out, AI models are terrific in spotting.

patterns that are generated versus you know done from a human i'm sure you have filled out a capture request online in your life a couple right so same idea right you know you basically build protection using ai to um you are not being misrabused by AIs. I think that's not all the same meta-theme of increasing maturity using AI systems and working with AI actors both inside and outside of a company.

I want to ask you a decoder questions, and I want to try to put all this together. You've only been at work a few months. You probably know where the bathrooms are in the office, I'm hoping by now. You've met a lot of people. What are you thinking about how your team, the product org, is structured and how you want...

That's an interesting question because, you know, you actually kind of trying to lead a witness here right you know how you imagine to change that you know i'm not i you know i'm not sure if i am so you know workday is it's a young company workday is 20 years old right you know compare this with many other enterprise software companies, they are twice as old or even older, right?

Workday has a really strong technology foundation. Actually what surprised me the most when I got into Workday is how good its technology foundation is because you know you come and i joined from a cloud provider before i worked at google in the past four years before I joined Workday, so you come back to the enterprise application domain of certain anticipations and Workday.

really is incredible when it comes to its tech stack, its scalability, its elasticity. I mean, it was a cloud-first system from the get-go. It really has a great foundation to stand on. And when I think about evolving us, going into the future, it's pretty much aligned with what you have said, right? It's maturing.

enterprise systems around the use of AI. My take is the following, right? Today you see a lot of bold on AI, meaning you see a lot of legacy system and they just get, you know, an AI overlay and you see... Integration vendors basically dealt with all of this complexity and now AI comes to the scene and they say, well, let's just slap AI over it and we call it automation.

I just wanna go back to autonomous cars, right, you know? If you have AI, the opportunity is to purposefully build with AI to change how a job to be done where we started actually get completely innovated and revolutionized. For instance, when we think about something like job applications, something very natural, we all have an understanding, we all applied for jobs. I'm not sure if you did, actually, but I did.

in my life. Wait, when you got the job at Workday, did you have to apply in Workday? No, I did not. It's a good question. No, I did not, actually. But, you know, work is not my first job, right? I was a school grad once, and I put an application into a system.

and then through the interviewing process. And, you know, the big opportunity that we have by really innovating in work is not taking authentic AI models and not just... writing API automation of an old process that was defined by, if you have human constraints, to a new way of doing it if they have a use of AI, like I've said, for instance.

tailored onboarding experiences tailored experiences for job applicants and targeting who we approach and how are they feeling through that you just said, right? why does it matter how I apply to a job, right? I just fell out of form. But there are industries, you know, for instance, where you have high numbers of frontline workers in retail and hospitality, where you have

thousands, tens of thousands, hundreds of thousands of applicants a year. And for them, actually sign up for a shift or basically joining a company. is something which is frictionless and you can do it through an intelligent experience including your skill assessment on your mobile phone with a conversation, or you have to log on to a classical web application and fill out forms. I mean, which one would you use?

I think there are real opportunities of how we can really change the way how these processes are done from what it used to be, human and document driven, to proactive and AI lab. When you think about those opportunities and how your team is organized, how do you map those things together? How's your team actually structured? We have an AI team today, which is, again, I think a testament to a birthday being a young company and being very forward-leaning when it comes to AI.

So there is a great AI organization that is part of my product organization, which is basically driving the Workday ML and AI platform. Many of the great things that we are doing in the recruiting space and the contract intelligence place, self-service, agent system of record. This is all being driven by that group and as I've indicated, one of the key innovation pillars that we have. And we have our application domains, right? We have our office of the CHRO, office of finance, our industry.

And those are, you know, application teams which are basically building in our technology foundation, the AI foundation, our application server and build. the systems that you and I and any listeners on this podcast would recognize as, oh, that's Workday, right? That's the UI and the workflows around it. And then there's an infrastructure team, as you would imagine, which is basically running our...

deployments into the various cloud providers. I mean, they're running on AWS and they're running on Google Cloud. And as you can imagine, this is infrastructure and a pipeline that also needs to be built and maintained. And those are in a nutshell other groups, AI, our applications.

from HR Finance and Industries and our infrastructure team. Right before you joined, Workday had some big layoffs. I think it was 1,750 people were let go. Obviously, those weren't your decisions. As you came into the company, do you think, oh, I need to hire up?

those cuts, one of the justifications were we need to invest in AI. Tell me about that balance. Did you see, okay, we need fewer engineers because the ones we have are using a bunch of AI tools, or did you see we actually need to go higher? Yeah, you know, you're asking me a question about a time that I wasn't at workday. So, you know, I can't really speak to the thinking that went into that.

Judging from the 60 days or almost 70 days into my role, we are actually investing in AI. We are investing across our application suite. I think in a bigger picture, like you have said, yes, the work of software engineering is changing with the use of AI and with the application of AI, meaning that We build skills inside of Workday to effectively use AI and we are hiring for people that bring that expertise into the company, so both end.

I wouldn't think, though, that this is in any way different or special from what the overall industry is doing. Yeah, I mean, we've seen so many companies, including companies we have interviewed on the show, like Duolingo, say, okay, we're all in on AI. We're through the testing and experimentation phase. The way we're running this company is now formally changing. and we expect AI to appear. Are you all the way there?

We are making, I hope, as any professional software company out there, heavy use of code assistance and wipe coding. And, you know, I've started my career in software engineering myself, but I was a hands-on developer for many years. Seeing.

how much it helps and changes you know the quality and the results you drive on the soft engineering side is amazing with wipe coding actually i think what it tries on the product management side is amazing You can actually specify working prototypes and real interactions. Not just, you know, Figma anymore or PRD, which is great, right? Because it gives so much more fidelity to your ideas. So yes, we make heavy use of that. And I truly believe it delivers real returns.

foremost, because when I was a developer, I made a fair amount of bugs. meaning like introducing issues right in the programs that you've write and you know I hope that you know every software developer out there is you know having the same moral integrity to say yeah you know you know bugs happen

And what I saw, what convinced me the most of assisted coding is that actually most of the bugs that you create on hindsight are, yeah, I should have really got that. I just didn't think the following conditions through. And AI helps in two ways, right? One is, you know, it's so good at test case generation that you just have way better verification. And secondly, the assisted coding generates high quality coding

really not making many of the typical mistakes and anti-patterns that you just make as you're developing from a junior to a very senior software engineer. So we use all of that. That's super exciting. And yes, Workday has... a very powerful concept that's called Everyday AI. What's the second thing, you know, that surprised me about Workday, right? And you're manually, you know, you're asking me these questions. I'm not trying to make advertisement for Workday here, but you're just asking it.

where they had this program, Everyday AI, or has the program. And then I joined the company. We were having an off-site just in week two. And it was basically a review of Everyday AI. And I was so amazed about how broadly Workday is applying AI. I have talked to so many companies. in my past that came to me and my previous role and said, well, how do we use AI? What are the use cases? What work? and then come to workday ranging from employee self-service to contract intelligence.

In legal, you know, basically both front and back office are making heavy use of AI models, AI applications and AI systems. And I think it was. a very smart decision of the company to say Let's experiment very broadly in every function. Let's find what really delivers value and then quickly double down on those scenarios. So I think that workday is incredibly mature when it comes to applying AI for itself.

The other big Dakota question I ask everybody, how do you make decisions? What's your framework? I believe in understanding the details. You can ask the question in another way around. Why do decisions go wrong in the first place? First of all, I think we have to recognize that there is a certain element of uncertainty in every decision that anyone takes.

You can make a really good decision and you can have a bad outcome, right? And you can make a horrible decision and you just get lucky, right? And that's the nature of... The uncertainty, if you will, of future, depending on what you believe system is, right? But I think it's hard to predict the future, and there is always an element of chance and probability. So I think that's something we have to recognize.

about being it and that tells us something right that tells us that The one thing I can influence in decision making actually is having a really robust process that

in average, if you will, or in a great end count, produces significantly more good outcomes than bad outcomes. So I'm basically trying to address... the uncertainty by having a very robust framework and process to get to a high-quality decision process, because I know that statistically that will drive to high-quality decisions in outcome, but you can't make all of them right. And my decision process, you know, follows, you know, actually I think a simple framework, right?

Trying to mitigate as much as possible human bias. We all have them, right? They're so human, right? It's funny that I say that. There's so much inherent in our nature. There's this great book, I think, by Daniel Kahneman, Thinking Fast and Thinking Slow. I'm sure you've come across it.

Right, which talks about all of the biases that we have in our brain functions. And there are just some typical repeat patterns, right? For instance, that we have loss aversion, right? You know, we think about losses. more significantly than potential wins right if I if I give you $10

And if I then take it away again, right? You're not the same happy as you are right now. You are unhappy. I made you unhappy, right? Even though you're exactly the same. It's just the loss feels heavy, right? And it biases decision-making. There is a bias in, you know, preferences, right? There's so many things that... you can address by one having a very structured decision-making process right going through all of the alternatives

listing them out, writing them down, actually, you know, being explicit about them and thinking with pen and paper, if you will, because it helps you to bust all of these biases that you have. And then second of all, in the decision-making process. actually engaging the right set of people to come to an unbiased decision itself, the right balance of expertise. and thirdly understanding the details matter you know the abstractions are helpful yes and you know there is a certain element where

It is not adding value anymore to go even deeper, right? You know, we would all agree, right? You don't need to understand quantum mechanics to know how to throw a ball, right? You know, there are helpful abstractions. But in decision-making on leadership and on businesses,

You really do want to go to the right level of detail to truly understand the dynamics of what's going on. And then thirdly, at being time-bound, right? You know, my father had these... has this great saying that is with me a lot and he says you need to have the courage to take the second desktop solution and what he means with that is that you know the most and fiercest competitor that they have in life is status quo.

Most of the time, we are not taking a decision one way or another. Most of the time, we simply decide to not decide. and let's analyze more. Let's find even more data. Let's pick the can down the road because you are of the idea that if you just give it more time, you will come to a better solution. And the problem with that is that you're actually passing the point there. Progress is more important than 1% more accuracy in the decision that you take.

So if you put those four things together, right, having a really good decision framework that goes against, you know, insulates you from your own biases. Secondly, having the right mixture of experts around you to make sure you are. really having the key influential or the key voices representative, firmly understanding the details so you can make an informed decision and inform. when the clock runs out, you go. And you need to have the courage for the second best solution sometimes.

we need to take another quick break we'll be right back How much money does it actually cost? to do a home renovation. This week on Net Worth and Chill, I'm joined by bachelorette contestant turned home renovation expert, Tyler Cameron. From having just $200 in his bank account to getting a TV show on Amazon Prime, this episode is

Act with practical advice, whether you're a homeowner or just hoping to be one someday. Two ways to take this. The first one is, if you're going to renovate your home, why are you doing it? Are you doing it to make money? If so, then I'd focus on your... I'd focus on your bathrooms. Plus, get the inside scoop on... are worth DIYing. Listen wherever you get your podcasts. slash yourrichbff.

We're back with Workday President of Product and Technology, Garrett Kazmaier. For the break, I was asking Garrett the decoder questions about structure and decision-making. So now, I really want to put his answers into practice.

Because what I really want to know about Workday is how someone new to the job like Garrett might go about making it better, especially when it's reputation among regular users, and the reputation of so many enterprise apps like it, is that Workday is just a total pain to use. Let's put this into practice. Workday, like all enterprise software, suffers from a disconnect between the customer and the user. Every piece of enterprise software has this problem.

It's CIOs and CEOs and CEOs who buy the stuff and their employees who use it. And that means there's not a great feedback loop between the experiences of the people using the software that people are spending. And that means the software is all bad. Like, broadly, we don't use Workday here, we use UltiPro. I think UltiPro is bad. Like, I'll just name all your competitors down the line. The users think the software is bad. Workday has a particular reputation.

Business Insider literally published a piece in 2024 called Everyone Hates Work. And the quotes are brutal. Here's one from an AI company, a copy director at an AI company. The quote is, using Workday is like constantly being bot smacked by bureaucracy incarnate. Getting somebody onboarded using Workday is like trying to get water from your sink to your stove using a column. That's bad. Using a bot? Using a colander, like a string.

Okay. Right, and you're trying to carry water with a bucket of water. You see this everywhere, right? The interface as expressed is bad. People do not like using the software. There's another quote from that same piece. Everything is so non-intuitive. Even the simplest tasks leave me scratching my head. There's one that says...

Great. That's every piece of enterprise software. Workday in particular has this headline, has this reputation. You can see it on Reddit. You can see it in the comments of the training videos I was watching on YouTube. How do you fix that problem?

I think a part of that is A, you know, really understanding what you just articulated. You know, as I said, right, you know, understand the details, right? You know, understand truly the details to make sure you are. taking good decisions when you specifically about what do we invest time in and what do we think generates value for the users of Workday.

When we say understand the details, I think it's really important in enterprise software to go through the workflows in detail and you know sometimes for yourself you know sometimes by observation sometimes by interview and really have first-hand experience about what it is right that people do and how does it feel and what makes it good and what can be improved upon it and i think to your point right that

It sounds so benign, but you said, let's apply this framework. The framework simply states that. Do you understand the problem really when someone is saying, this is great or someone is saying this is bad. What do they truly mean, right? Because all of our biases, right? You know, for instance, one big bias is, you know, you seek validation, right? You seek validation for what you believe to be true and you overemphasize on signals.

that reinforce that. And the first step is really going to the right level of detail and understand What is it at a action level? that drives satisfaction or dissatisfaction in a piece of your application experience. And once you have that, as it turns out, once you understand that,

Usually the framework becomes almost obvious to say, well, this is something that really should be different. Or this is something that actually works the way it's supposed to be. It's just not communicated. It's miscommunicated, right? You're holding it wrong. Or thirdly, actually we have different ways or different expectations now of how you can use that. For instance, when you talk about system interactions, right?

The reality is that it's a dynamic environment. Meaning, when I look at, you know, I have two kids. They have different expectations of using a system than, you know, what I had. You know, I grew up and forms. i was kind of like i was computer stuff right how cool is that right you have a depth one that's amazing My daughter, she is mobile first and dare I say, AI first.

And she's eight years old, right? So that's the amazing part of it. A different intuition. So when I say Workday and AI specifically, right? It's now, hey, how can we make this conversational? Or how can we make it so you don't even have to specify some of this information anymore? Like you said, I have to take information from here to there.

Why is this complex? Why do you even have to? Is an AI model maybe proficient and can we make it proficient? So it just automates that. This is why I wanted to start with what's talking about the software.

is, right? If the goal of the enterprise software, when I see a quote that says, this software is bureaucracy and... What I imagine that means is a bunch of people at a company had a bunch of priorities and they all got expressed in a...

Right. Everybody wants another piece of data from whatever process is happening. And we're just going to put another field in the form and then everyone can get their data. And that's your bureaucracy incarnate. Right. We're literally shipping the org chart in the nature of this. Okay, so now we're going to say AI is going to fix it. We're going to fill in all the forms as fast as possible just by talking and all the forms are going to fill out. And then that looks like the risk.

Like, there you have exactly the risk. Maybe the AI is just going to say 20% more nicer things because the model's wrong because 4.0 got a little too nice one day. Maybe it's just going to make some stuff up because it thinks that's what you want to hear. Maybe it's going to mishear the...

I hear a lot from a lot of companies that AI is the new user interface, right? All the way down to Eddie Q on the stand in the Google trial yesterday said maybe 10 years from now you won't even have an iPhone because AI... That's where we are as an industry. And then I look at this very simple problem of, for a lot of people, Workday is filling out a database. Filling out the database with AI might mean the database is full of bad information.

But no one else has solved the problem in any other way. Yeah, I think it really connects to that we were starting, right? The whole question of what drives value with AI, right? I fundamentally believe with AI as with any other technology. You can apply it superficially or you can apply it in an excellent way. And applying AI in an excellent way actually means getting AI to

differentiated levels of accuracy and outcomes. We talked about autonomous cars and you said some work and some don't, right? So there's clearly a difference, right? Even though you could all say, well, I'm sure they make all use of AI somewhere, somehow, to do processing and trajectory protection and so forth.

And that's exactly what we are focusing on with Workday because some of the information, like you have said, is important information. Guess what? You want to pay people. You want to have internal mobility. in companies In many companies today, a shortage of qualified labor, right, for the work that they want to get done. And they have people sometimes inside the company who could do it or even people outside of the company that they could activate for doing it.

you know just you know to pick a very simple example and now the question is What can you do by excellently applying AI? to really revolutionize and improve these journals. And there are clearly ways. i was just you know speaking about recruiting right now you can help many recruiters make better decisions they don't have to fill in the form anymore they don't have to make the assessment the model helps them to identify

the right candidate. You inherit literally the biases of the models, right? You inherit literally the capabilities of the model. Right now, there's a lawsuit against... saying that the tools are biased against workers and applicants, particularly black workers and applicants over the age of four.

That might be the problem in the model. That might be the problem in how you've expressed the model. It might just be how people are using the model. But now you're saying you're going to help make these decisions and you have this liability. You know, first of all, you know, I cannot possibly comment on any ongoing lawsuit. But in general... But the lawsuit exists, right? You know it exists. This is the problem in depending on the AI. The AI might make errors of this magnitude.

I give you Garrett's opinion. Okay. So because again, right. And you know, if you want to have commentary on the ongoing case, you know, you have to talk to the right person for it. That's not who I am, but I can speak to you in general about AI. I think AI actually helps us to get unbiased. And the same principle applies. You can apply AI very poorly.

And AI, it's a question of maturity. Since the course of the existence of machine learning, people learned that if you have the wrong training data and you're lacking guardrails, The model just expresses what was given the model during its training phase. You basically define it by the act of creating it. And as you know, you move from immature AI to excellent AI, right? When we understand that, you know, the representation of data, the guardrails that we have to put around it.

I think, you know, all of these biases that you described, that humans are susceptible to, you know, just in a different way. But, you know, humans are, you know, humans have emotions, humans have... irrational elements to them, right? We are not computers, and that is what makes humans great, right? But it also makes us, in many cases, poor decision makers. But the AIs are trained on the corpus of their training material.

biased human information. How do you take that and then turn that into a thing that unbiased information? Yeah, exactly. Especially in these contexts. I mean, Amazon had to stop using AI screening tools that were imposing bias into their hiring process. Can you measure it? Can you say, okay, we're good enough?

You know, you do it by getting the recipe right. You're meaning you're getting the training recipe right, you're getting the garbage right, and I think this is the important intersection in AIDA. In order to get AI right, you have to look at it holistically, meaning you have to understand the domain, you have to understand what is the judgment that a model applies, you have to understand what training data you need to provide for it, and you need to provide...

the guardrails that you have to basically put as check-ins, balances around it, so it stays in its defined parameters. And once you do that, that's the power of AI and machine learning models. they will consistently work at the same level of quality, right? But it's the responsibility, right, to create that system around it. And I think if you do, again, my opinion, if you do that, it works.

in an incredibly powerful way. And let's just go back to something we all experience in San Francisco, everyday autonomous cars. that's a great example right you know because so many things can go wrong right and now we are the stage where they work reliably and the lesson is if you design a system the right way

If you think about it holistically, you can actually make it work all the time. Better than a human driver would. Because, you know, we also have human limitations that, you know, we can't get passed on right. What is every good recruiting team doing? What is every good performance review team doing at the beginning of a review session? Let's unbias ourselves. Let's call out the seven biases. Let's talk about them so we free ourselves from that being applied.

There are teams who are good at it, teams who are not as good at it. But if you codify it in a system right, you can basically have the best possible decision making on tap every day. And that's the power of it. You know, Takedra Malakana, the CEO of Waymo, has been on the show. And the thing that's, it's true, that they work great in San Francisco, I think.

Austin and Phoenix now. They're rolling out. All warm weather cities. I asked her, will this thing work in Denver? And she was like, no. Right, too hilly, too snowy. That's what I mean. We've designed systems in very narrow domains under essentially perfect conditions that we trust, and then you make it more complex. And then it's just like, no, we can't do it yet. Maybe we'll get there one day, but we can't do it yet.

I think you're completely right, and that's exactly what I mean, right? You make it work by narrow the domain, right, you know? It's incredibly hard to make a car work everywhere. It's incredibly difficult to make a general AI that works on everything. And that's, again, that's the workday. recipe, right? We are saying in our

claim is not that we're going to make an artificial general intelligence that solves any problem. We do exactly what you said, right? Let's narrow down the domain on something that we really understand, that you understand perfectly. And let's design a system. that basically solves that part of the enterprise ecosystem.

When you think about the complaints people have for Workday today, I'm going to ask you two different questions. One, what are the top five ones that you want to fix, right? People do not like using the software. How would you fix it for them?

That seems to be a really important part for you today. As I said, you were brave. This is why enterprise executives don't come on the show. Because that's honestly what the listeners want me to ask. How are you going to fix my problems today, right? It's not just feature requests. It's the holistic experience of using enterprise software. How would you fix it? I think, you know, my conviction, right, you know, down to the bones of my body, if you will.

i'm a product person you know i i love well-designed products and i i seek them out for myself and i aspire to build them you know i think when they say about Building a product right and I you know, I was talking earlier like are you holding it the right way? beautiful design is you know how it works it's not it's not just how it looks you know designers

how it works in everyday use, you know, from a coffee machine to an enterprise software system. And I think the recipe is for all of them the same. recognizing that this is a big deal you know this is not something that just falls off at the end that's something you have to carefully research design and invest for to make it work and then secondly

When you ask me about my decision-making process, you know, really understanding those details, right? What works well and what doesn't. If something doesn't work well, what's the best way to improve it and to make a tangible... improvement for the ones who are articulating the need for improvement. I believe honestly in a relentless pursuit of the basics. When we say excellence, how do you get excellence in anything? I think it's recognized importance every day.

Secondly, apply the discipline rigorously, every morning, every afternoon before you go to bed to apply it. And if you do this consistently enough over a period of time, you will see huge differences. The problem with all of these things is that you cannot go from here to there. step function change from here to tomorrow, right? Because actually what you're saying is that

How do you achieve excellence in something which is non-trivial? And as I said, first of all, somebody believing in its value. Otherwise, you won't have the strength to see it through. And then secondly, applying the basics of that discipline every single day rigorously and over a period of time you will see amazing return.

i said i was going to ask this question too so here's the second one do you use workday at workday yes what are the five things that bother you most about using workday Can I tell you what the biggest surprise was, first of all, when I came to Workday? I have used Workday before. Sure.

And the Workday at Workday looks so different. I mean, this is one of the issues, right? Because your customers deploy it. Exactly. And I was coming into Workday and I said, I'm surprised because the system that I have just used for everything from entire onboarding from benefits enrollment to corporate credit card to learning my team to any sort of approvals, to ARC review. I've done it all in Workday. Everything.

It is so different. And so I asked, you know, well, explain this to me, right? Because honestly, in my previous workday experience, I have struggled with a couple of things here. This is different. And they said, basically, what you said, yeah, it's a real issue that we have customers who configure and deploy the system.

and are not updating the system to any of the improvements we have done over the recent past. When you say, what do I want to change immediately, right? Go on a campaign and actually make sure that the quality of the experience and i'm not saying there's nothing to be improved anymore but the many many things that i have experienced firsthand myself are 10 times better from what I personally have seen before. Making sure that all of this... What are some other things? Requesting a credit card.

you know searching it you know credit card and getting the form loaded and populated with you know you know the right fields already because i guess not you know my name right you know there's no surprise here and my employee idea and all of that and just making me basically select you know the credit card example what is the limit and if i want express delivery and send

something like that or so search experience one terrific example or the assistant experience right you know and you know one of the workflows that people most do commonly is you know personal time off right In Workday Everywhere, you can do this by using Slack or Teams with a chatbot. So I bet many of the things that you were quoting too is people... trying to do something which to them looks very simplistic I just want to know my PTO balance and put in a request

Why do you even have to log on to that system? So when I talked about the difference in expectations, right, that you just expect it to happen in your collaboration suite while there's workday everywhere. That works. And I was surprised. Before you ask, I didn't request PTO in my first 60 days, but I was trying it out because I wanted to know, because I believe in understanding the details.

So, as I said, one of the things I want to do first is making sure all of this flows through to everyone, because I think there is so much goodness that people are not yet getting to.

You're hinting at something here, this will be the last question, because it's just a big idea that I keep coming back to in all these conversations about AI and software and how we use it, that eventually... The interface will just be natural language, right? There's the small step you're talking about, which is go to the customers and help them deploy Workday more beautifully and make it make more sense for people and use all the tools. Great. And then there's the big one.

which is you're just going to talk to it and it's going to do some stuff. How far away do you think we're from that? I think there's a whole lot of tasks there. People use forms to approximate conversations where conversational is clearly about a paradigm. Like a self-service type of request, like I said, you know, PTO and PTO balance. This is more like, you know...

a self-service scenario which I can easily specify and it's automating that and conversational is a good way of exposing it and there are some others that fall in the same category. But it turns out, you know, there are many that are not you know so you know like like i said right how many things can you remember in a conversation like top of your head you know probably seven concepts you know max at a time

There are some application domains where you have a way more complex context and state model right there. just say something as simplistic, would you Could you design a 3D scene without seeing it just through conversation? Of course not, right? Would you want to specify verbally that you want to select an element in the fourth layer? Probably not, right? It's way too complex. Pointing and clicking is way more efficient.

I argue the case that conversational will be a key part of what everyday experience is for a certain set of problems that just very nicely fit into it. And there is a larger set of problems there. The state model and the context are so dense. that you cannot possibly conceive them in a conversational threat because it's just overloading what you can memorize in your brain.

So I think it's going to be a both end. But I think every scenario where you're going to ask something, can you do this for me? Can you find that information for me? It's more. simplistic and in terms of the information retrieval search is a great example of that by the way

I think that's going to be completely replaced with a conversational interface because why not? Essentially, you have a request-response paradigm with some refinement in the middle for which a conversation turns out to be the best way of facilitating that. One of the reasons to ask this question is because my favorite Slack room at our company is called Finance Support. And it's staffed mostly by bots. And the people who are new to it come in and they ask very nice questions in full sense.

And the people who use it every day just shout nouns into the void. I'm looking at it right now. There's someone who just says extra April expenses. One person literally just typed the word credit card. and then entered into an entire flow with this bot. It's basically a command line. And we've just recapitulated the command line with a more conversational interface where people have realized that the keywords will just do the job. Is that where we're headed? We're just doing command line?

i don't think so you know but i do think what you're describing actually is good thing you know i heard that open my eyes a lot of is using a lot of you know inference cycles because people are just being polite with the model saying thank you and please and right you know but the model's gonna work right for that so

What you are describing, I think, is just an amazing efficiency that people understand, hey, I don't have to write a fully specified sentence with punctuation. I can just keyword it in and the system is going to do it for me. and i think it's because for some of the work this is just very efficient you know this is why Are you really typing a URL in your browser and writing it full out? Or I don't, right? I rely on autocomplete answer.

to do the job for me right that's a perfectly fine way of accomplishing the job but i i do think like i've said right there is a certain set of problems, information retrieval, simple workflows, then this is just a very nice way of doing it. That command line is good for a reason, to your point, and intelligent command line is very powerful. But there's a very bigger set of tasks and jobs there.

You wouldn't command line it, right? You need to see what you're dealing with. You have many elements that are in relationship with each other. Just take something as simplistic as a contract and finance, right? Because you just said finance, right? and you have a context with multiple payment terms that are dependent on each other.

and you're referring a contract right so you do need to see those pieces and how they interact with each other to make sense out of them and an AI is going to help you right and identifying them and telling you right you know

This is a red line in a contract that you have to pay attention to. This is a payment term that you may want to leverage. But if you want to modify that contract, if you want to rearrange it, you want to see the piece that you're working with, right? And you have to... across so many domains and I think AI is gonna change UI and we have AIs that are designed or UIs that are designed with AI in mind.

I don't think that today some vendors are telling you, you're going to have a chatbot and a workflow engine. And that's going to be great. And that's a good story to tell because we have all of this stuff built and having a chatbot open, you know, it doesn't work for sure. but it's not going to change how you run as a company. It's not going to be a transformative outcome for you. But if you design applications with AI collaboration in mind from the get-go, payroll.

benefits election right if you want to elect your benefits you may want to see options you may want to you know have multiple options compared to each other you know There are going to be things where we can decide we're going to render UIs into chatbots or we're going to render AI next to UIs. but it's not gonna lose you know those element of of interactivity where you just

need to break beyond, you know, textual input and output. Well, Garrett, I feel like we can talk about the future of AI and how it changes workplace interface forever. I have to say, by the way, thank you. It is true, not many enterprise executives are brave enough to come on the show and answer the question. So I appreciate it. Thank you so much for being able to come.

Thank you for having me today. It was a pleasure. I don't see why I'm happy to come back on any time. Well, let's read the comments about a specific Workday feature request and see how you feel, but we'll have you back as soon as we can.

I'd like to thank Garrett for taking the time to join Decoder and really invite any other enterprise software executive brave enough to be on the show to join me as well. And thank you for listening. I hope you enjoyed it. If you'd like to let us know what you thought about this episode or really anything else.

drop us a line. You can email us at decoder at theverge.com. We really do read all the emails, even the ones that include brand new suggestions for our taglines. You can also hit me up directly on Threads and Blue Sky, and we have a TikTok and an Instagram. They're both at decoder pop. They're a lot of fun.

If you like Decoder, please share it with your friends and subscribe over your podcasts. Decoder is a production of The Verge and part of the Vox Media Podcast Network. Our producers are Kate Cox and Nick Statt. Our editor is Horsa Wright. The Decoder music is by Breakmaster Saunders. We'll see you next time.