Workday のプロダクト責任者 Max Wessel が語る、生成UI・信頼できるAI・ポリマス型組織(Workday Rising 2026 ライブ収録)

SE 34: Max Wessel, SVP of Product at Workday | Live from Workday Rising 2026

Workday のプロダクト責任者 Max Wessel が語る、生成UI・信頼できるAI・ポリマス型組織(Workday Rising 2026 ライブ収録)

Workday のプロダクト責任者 Max Wessel が語る、生成UI・信頼できるAI・ポリマス型組織(Workday Rising 2026 ライブ収録)

AI and the Future of Work: Artificial Intelligence in the Workplace, Business, Ethics, HR, and IT for AI Enthusiasts, Leaders and Academics

0:0030:10

要約

Workday の SVP of Product、Max Wessel が Workday Rising 2026 の会場で、AI 時代のプロダクト開発について語った回。コード生成が容易になるほど、課題理解や品質への「センス」と判断が重要になると述べている。エージェントが即時に画面を作る生成UI、監査可能性や責任あるAI委員会による信頼の設計、職種の境界が溶けるポリマス型組織への移行についても触れている。

この回のポイント

  • ●コードや仕様の生成が容易になった今、プロダクト担当の仕事は「どの課題を解くか」を見極める判断力と品質へのこだわりに、より重心が移ったと Wessel は述べている。
  • ●生成UIとは、エージェントがその場で作るUIのこと。Workday Decision Intelligence ではグラフを再生成できるプレイブックとして保存でき、Sana エージェントがフォームや表を組み立てる。
  • ●信頼構築の鍵は監査可能性。AI の思考過程や前提を検査できるようにし、ブラックボックスを積み重ねない姿勢を示した。
  • ●報酬・採用・処遇に影響する判断には人間の関与を必須とし、責任あるAI委員会が新機能を審査する。設計の初期段階から倫理チームも関与する。
  • ●組織はジョブディスクリプションよりミッション中心に再編され、ポリマス(多分野に通じる人材)が増えると予想。一方で、モデルの出力を検証できる専門性の価値も高いと語った。
  • ●5年後には進捗確認などのプロジェクト管理が自動化され、自身の時間は体験の質や直感・判断に集中するだろうと見通している。

章立て

  1. Max Wessel の経歴と現在の役割

    14歳で起業して以来エンタープライズソフトに携わってきた経歴と、Workday で全アプリケーションチームを率いる現在の役割、「世界最大のスタートアップ」という方針を紹介。

  2. AI時代にプロダクトの仕事が難しくなる点

    コード生成が容易な時代には、課題理解・センス・判断・説明責任が重要になるという持論。実装が間に合わず見送った報酬体験の刷新の例も挙げた。

  3. 生成UIとエージェントの設計

    エージェントがその場でUIを生成する仕組みと、Decision Intelligence のプレイブック機能を説明。チャット一辺倒ではなく、人が情報を消費しやすい形にする重要性を語る。

  4. 擬人化しないAI文化と信頼の設計

    AI を擬人化せず裏方で自然に働くものとして設計する考え方と、監査可能性・透明性で従業員の信頼を得る方法。福利厚生の相談や問い合わせ約25%減の例も紹介。

  5. 責任あるAIと委員会の運用

    人事・処遇に関わる判断での人間の関与、責任あるAI委員会の構成、エージェントの行動範囲やエスカレーション経路を設計に反映した例。

  6. ポリマス型組織と人材育成

    職種の境界が溶ける「ジョブの拡散」、ミッションチームへの再編、若手へのアドバイス(作って出荷する)、専門性の価値について。

  7. 来年の期待と2031年の展望

    来年も期待以上を届けられるという自信と、5年後にはプロジェクト管理が自動化され判断や体験の質に集中するという見通し。

解説記事

Workday Rising 2026 の会場から収録されたこの回では、ホストの Dan Turchin 氏が Workday のプロダクト責任者(SVP of Product)Max Wessel 氏に、AI 時代のプロダクト開発の変化を聞いた。Wessel 氏は14歳で最初の会社を起業し、Degreed の CEO や SAP の EVP を経て、ここ1年半は Workday の中核アプリケーションの AI 変革を率いている。

「作るのが簡単」な時代に問われるもの

AI がコードを書き、仕様まで提案するなら、プロダクトの仕事は楽になるのではないか。この問いに Wessel 氏は否定的だ。YouTube 登場期に書かれたある書籍を引き、コンテンツが潤沢になるほど品質の高いものに人が集まると述べている。同じことがソフトウェアにも当てはまり、簡単に「ゴミ」を量産できる時代だからこそ、解くべき課題の理解、センスと判断、決断への説明責任が仕事の中心になるという。

基調講演の洗練されたデモの裏側についても率直だった。報酬・福利厚生体験の刷新は、フォームや表をエージェントが組み立てる生成UIの基盤が整っていないため、今回は見送ったと明かしている。見栄えの良い例は、この1年の地道なエンジニアリングの上に成り立っているという説明だ。

生成UIとエージェント

Wessel 氏が強調したのが生成UI、つまりエージェントがその場で生成するUIである。たとえば新製品の Workday Decision Intelligence は、対話でデータを分析するエージェント型の分析ツールだ。ユーザーが望むグラフが得られたら、それをプレイブックとして保存でき、次回以降は同じ問いに対して最新データで更新されたグラフが返る。

同氏は、ECサイトを例に、人間にはチャットよりも画像付きの見やすいレイアウトが適していると述べる。エージェントがデータをそのまま表で返しても人には使いにくく、翻訳層が必要になる。Workday にはそのための部品群を作り、Sana エージェントがそれを使って人に語りかけるよう調整するチームがあるという。昨年の「AI is the new UI」は何でもチャットにするという意味ではなく、AI が望ましい形のインターフェースになるという意味だと説明した。

擬人化しないAIと信頼の作り方

Turchin 氏は、基調講演に不気味なボットの画像や AI の擬人化がなかった点を評価した。Wessel 氏は、同社が目指すのは人間の可能性を引き出す未来であり、AI は事務作業を肩代わりする裏方として自然に溶け込むべきだと答えた。恐怖を煽る議論は自己都合になりうる、との見方も示している。

信頼の要は監査可能性だとする。Workday は元来、監査可能な取引記録を価値の中核にしており、戦略的人員計画のような AI の成果物についても、思考過程や前提を確認し、疑問を投げかけられるようにするという。ブラックボックスが重なるほど人は疑いを持つため、仕組み・目的・ルールを透明にするほど従業員は信頼しやすいというのが同氏の考えだ。福利厚生の選択を例に、手取りへの影響や制度文書を分析できるツールを従業員に渡す利点も語った。セルフサービスのエージェントでは、シェアードサービスセンターへの問い合わせ件数が約25%減ったとも述べている。

責任あるAIと人間の関与

報酬、採用、将来の就業機会など従業員の立場に影響する判断には、人間が判断に関与すべきだというのが同社の考え方だ。基調講演ではエージェント構築・展開の設定可能なパターンが発表され、重要な判断には人間の関与を組み込めるという。さらに、新機能は責任あるAI委員会が審査する。メンバーには Wessel 氏のほか、最高AI責任者、CTO、IT責任者、法務責任者、倫理・コンプライアンス責任者などが含まれる。

具体例として、組織構造を扱う人員計画では、エージェントが HRBP などによるレビューの流れの外で事業責任者と作業しないよう、委員会とエスカレーション経路を詰めてワークフローに組み込んだという。倫理チームは完成後ではなく設計の初期段階から関与するとのことだ。

ポリマス化する組織とキャリア

職種の境界が溶ける「ジョブの拡散」について、Wessel 氏は今後ポリマス(多分野に通じる人)が増え、組織は職務記述書よりミッションを軸に編成されると予想する。Workday でもエンジニアにデザインを、プロダクトマネージャーに Claude Code でのプロトタイプ作成を促し、プロジェクトの管理者と人の管理者が別になる構造も試しているという。

若手へのアドバイスは「作って出荷すること」。LLM に自己検証させる仕組みやレイテンシなどは実際に作らなければ分からないと述べ、新生児の動きを記録するアプリを作った顧客の話を例に挙げた。新卒は入社時から AI に慣れているとも語る。一方で、誰もがゼネラリストになれる時代には、モデルの初期直感を検証できる専門性にプレミアムがあるとも指摘した。言語化しにくい専門家の直感を、次世代にどう育てるかが組織リーダーの課題だという。

まとめ

本編は Workday 側の担当者による発言であり、製品の見せ方を含む点には留意が必要だ。それでも、生成UIをエージェント設計の中核に据える発想、監査可能性を信頼の土台とする姿勢、高リスクな人事判断への人間の関与と委員会による審査は、HR テックに限らず業務AI を導入する企業の参考になる。また、プロダクト職に求められる力が実装から課題設定・判断・センスへ移るという見方は、日本の開発組織やキャリア設計を考えるうえでも示唆的だ。5年後に進捗管理が自動化されるという展望も含め、役割の再定義にどう備えるかが注目点となる。

文字起こし(英語・自動生成)

Yo, it's the future, don't hit the snooze, AI is you're giving humans the boost. Team humans rolling, brains in the game, with Dan Turchin, y'all remember the name. People hanging in the middle, stopping to float. Better work, better life, yeah, we're ready to go. Robots and humans are collab, you know. Okay, let's start the show. Welcome back to another special episode of AI and the Future of Work, recording live from Workday Rising here in the bowels, the fourth floor. of the Venetian in Las Vegas. And I am joined for a special conversation with the Senior Vice President of Product, Max Wessel from Workday. Max, I believe, received his undergrad from Northwestern, Go Wildcats, and his MBA from HBS, Austin's Harvard Business School, Go Crimson. One thing that of the many things that Max has done in his career, he has not yet appeared as a guest on AI and the Future of Work.

That's about to change. Max, welcome to the show. Let's start by having you share a bit more about your background and how you got to where you are today. Well, first, thanks for having me. I'm super excited for the conversation. Obviously, it starts with GoCats. So thanks for the Northwestern shout. I founded my first company when I was 14 years old. I saw the magic of the internet and applications, and I thought it was just phenomenal. Like you could beam a form anywhere in the world and thought, holy smokes, we need to do this at scale. And ever since then, I have been building product and shipping it, like focusing on how we do new things faster and change how we work, how we operate, how businesses form. It's always been in enterprise software. I've worked in a mix of enterprises and startups and have spent the last year and a half here at Workday focusing on the AI transformation of a lot of our core applications.

So very excited to be with you and talking about this magical moment where we can bring software that acts as a partner to everybody in the world. Based on the amazing innovation that Anil and the team talked about at today's keynote, it feels like you went from being an entrepreneur to an intrapreneur. Talk about your current role and what goes on in your day job. I lead our applications teams across Workday, so all of the applications that folks know and love. And what Anil has really set out as a mantra is we want to be the world's largest startup. We want clear accountability. We want clear direction. We don't want decision fatigue. We want to empower people to move fast and build new things. And a lot of what you saw in our keynote today at Rising was about just that. How do we, when we emancipate teams to focus on the most exciting use of the technology in front of us, they can create. Whether it's turning a performance conversation into an actual coaching and development conversation through what we release with Sonic Coach.

Whether it's putting a team of analysts in your pocket by activating an agentic analytic system that's connected to your core. All of that is the work of teams that are empowered to move fast independently inside of Workday. Some looking in from the outside would look at our roles as product people and say, let's be easy because AI does all the work. It writes the code and it specs the features and it even recommends what you should be doing more of. That's actually not the case. Talk about what's hard about your job and maybe even what's harder than it was in the past. there's a great book that was written i don't know 20 years ago um that was in the early days of the youtube moment and it was about what is creation look like for video in an era where anyone has the tools to build new content and it was that contrarian position the author a woman named Anita Elberci basically said,

in an era where there is completely abundant long-tail content, what we're going to see is gravity to the things that are high quality. And I actually think we lost sight for a while there that part of the act of product management is around understanding the problem, having the taste in judgment, and the accountability to take a decision when it's very easy to generate code. It's very easy to create slap. And so more of the job is what product was always about, which is understanding what real problem are you solving in the world. How do you make something easy and delightful and intuitive for a human that interacts with it? And how do you focus on that very simple interaction, making it real? So along those lines, when someone like me in the audience this morning at the keynote sees all these beautiful polished demos, it looks effortless. like divine from heaven. These beautiful demos dropped out of the sky.

Talk us through something that we didn't see in the keynote, maybe an idea that didn't quite make the cut or something where you contemplated and ended up not building it. Well, I'd say there are a lot of things that we started building that we stopped because we couldn't get it there in the way that we wanted to make it real. I'll give you an example that we're still very much working on, but it requires a lot of underlying engineering effort behind the scenes. We talk about taking core modules and workflows, like how do we redesign the compensation and benefits experience for Workday. There's a lot of hard work that will go into creating a new generative UI system for forms and tables, all the elements that need to be composed by an agent like Sana. and we haven't gotten there yet. It is well underway, but we took things like the redesigned compensation experience out of this conversation

because the hard engineering work hasn't gotten there. The effortless examples that you talked about today, I mean, part of them are on the backs of a lot of incredible engineering work to give an agent like Sana the capabilities to generate great menus and incredible interactions around clicking buttons. That work has happened over the last year, and we're very proud of it. One of the things that I thought was most elegant about some of the new interfaces is that it felt like the right amount of UI, like the right amount of conversational AI balanced with the right amount of, I don't know if it's traditional, but classic forms and classic UI. How do you think about the way to build agentic workflows and conversational AI in at the right point in the workflow? So the cool thing about that UI that you saw today, it's all generative UI. And so we actually use the interaction with the agents

in order to figure out what UI needs to be generated. One of the examples from today we released a product called Workday Decision Intelligence WorkDate decision intelligence is an agentic analytics tool You could chat your way through data but it easier for humans to consume data in charts. And when somebody asks for a chart to be created and it comes out the way they want, in Decision Intelligence, you can save that as a playbook. And the next time you ask the question, when the agent goes through and does the analysis, understands the data relationships, and comes back with an answer, it'll come back in that chart updated. And so we think a lot about how do we connect this incredible alien technology that is AI with all of the tools that we need to translate it into the way we consume information. You said something profound, more profound than I think you realize,

that I think will define kind of the next maybe decade of how humans interact with machines, the term generative UI. So you kind of tossed it out and then went on. But take a step back. What does that mean at work, Dave? How do you think about the role of generative UI? So generative UI is UI that is created on the fly by an agent. And there are a lot of emerging standards around generative UI, and we're still very early in the process of building out all of the frameworks, all of the tools to be able to give agents the ability to speak in the way we consume information. UI is wonderful. I don't want to chat to my e-commerce sites because the way they are laid out beautifully with pictures allows me to figure out exactly what I want to buy, the way that I want to buy it. It is a experience designed for a human. Getting a code full data dump in a table is not the same.

Even though an agent might speak that language, we need that translation layer. And so when it comes to the work that Workday is doing right now, a lot of our focus is how do we build the generative UI components? How do we create the interaction system? How do we coach the agents to use those components to speak to humans? and what you get on the other side is things like forms and charts and workflow tools that feel like the types of systems we are all used to interacting with but they're created flexibly on the fly by the agents and so we have a whole team at Workday that focuses on creating those elements for our our SANA agent to use as it interacts with users until you see it done right like the way you just described, it feels like for 30 years we've been trying to convince humans to behave like machines. And now finally when you see these kind of lightweight just-in-time interfaces,

you're like, yeah, like AI kind of is the new UI, but just-in-time UI or generative UI is really what we're headed. Yeah, we said this last year. AI is the new UI, and the challenges, we all thought that that meant, oh, we're going to chat to everything. No, the AI is actually going to be the interface the way that we want it to look. I made a comment in the exec meeting earlier to Anil. I said, in 90 minutes, there were no images of creepy bots, and there was no anthropomorphizing of AI. I shared as a compliment to you and to the leadership team, Because I think that's something intentional that you've done. Talk about the culture of AI and how you maintain that humanness. And you're thinking about the customer, building for the customer while still innovating. Yeah, we believe in a future where AI allows us to unlock human potential.

And we spend all of our time dreaming up those situations. and fundamentally, I think that's core to what you saw. You saw a vision for Workday that is the what if in the positive. There are a lot of companies out there right now that are talking about the what if and the negative. And in some cases, the fear-mongering can be self-serving. For us, we were out there to inspire a brighter Workday from day one. That's our mission. and this technology gives us the ability to imagine a world where folks focus on the things that brought them to work in the first place and not chasing paperwork or completing mundane tasks that they have to do as a byproduct of trying to do the work they want. And so when we think about that, we want AI that seamlessly works in the background. It should feel like part of what you always wanted it to be.

And this idea that we would anthropomorphize or try to sort of create a vision of the future that is somewhat other than sort of misses the point. If we do this the right way, it will be well integrated into the way we operate. And yet it must be said that workday is like an end of one when it comes to organizations that aren't tripping over themselves to do things that confuse humans into thinking that the AI is human-like. I think we have the benefit of a lot of folks in the organization who are AI native. You know, we brought them into Workday after the only thing they did in their career beforehand was work on the application of AI in a situation. And so they have great mental models of how this works. And when you couple those types of innovators like Joel Hellermark from ZANA with the deep expertise that we have within Workday around the business processes themselves,

what you get is this vision of the world. We in HR Tech have a tremendous burden trying to convince employees to trust AI and that somehow it's in their best interest because it doesn't always feel that way. It feels like AI is being done to them as opposed to with them or for them. When you're designing product, how do you think about placing guardrails and building up the right kind of guardrails and earning the trust of users. Part of it is about auditability. And so we spend a lot of time thinking about how do we expose the thinking, the logic, how do we make sure that everything that AI is doing is available for inspection. And when we do it, that, by the way, has always been at the core of Workday's value proposition. We have a transactional record that's preserved and has always been auditable. And so when we're able to come and say, hey, here's how we built a strategic workforce plan,

inclusive of how do we think about reskilling employees in an era of AI? What are the things that we think have the potential for automation? Where are the places where we need more human skills? Being able to ask that question of an agent and then also see how it thinks through the process and frankly question whether or not the way it made assumptions about the use of a certain technology was right or wrong that important Right now we have a series of black boxes in the industry stacked up and naturally people are suspicious Because if we see a black box after a black box after a black box, what we end up with is just a bunch of questions. And the more we make it transparent, how does the AI work? What is it trying to achieve? What are the rules by which it operates, the easier it is, I think, for employees to trust it. It takes a tremendous amount of empathy when we're building software and asking humans to automate leads of absence or manage benefits,

things that impact their lives, their children's lives, their parents, people they love. How do you think about those micro decisions that we're automating into software that ultimately have real impact on people? We think a lot about kind of human in the loop and which human should be in the loop. So it's funny, I actually find our advice that we can give in benefits decisions, for instance, to be a great example of the positive side of this. Because when you think about a benefits election, it has impact on your take-home pay. It has impact on your family's position if something might emerge. and it's really quite complicated to look at policy documentation, information on the public internet, to go back and translate that into how much is something in the cost and how is it going to impact me after the fact, what's my savings rate. The fact that an employee can be given not only information about the programs that our companies are putting in place, but the tools to then go analyze that set of decisions is powerful.

And when we put that, I just showed a demo yesterday, of putting those types of tools across take-home pay inspection, benefit selection, and policy documentation in the hands of an employee, you can ask all the right questions to make the right decision for you. Crazy thought experiment, but extrapolate that one out, and there could be a time when employees feel safer engaging AI because it is perfect recall. And maybe, it seems like heresy, but the traditional way of calling the benefits help desk or something where maybe that benefits professional's view of you is limited to what shows up on their screen, could there maybe be a time when we trust the AI agent because I suspect there will be? And we already see this with our self-service agent, that case volumes to the shared service centers. drop about 25%. And so when you have context, when you understand the decisions, when you understand the policy,

the agent can provide a better answer faster. And part of it is around building that context and building the trust with employees. So in your leadership role, your organization is somewhat looking to you to send a signal about what is responsible AI. And you kind of have to evolve an opinion and then you're responsible for operationalizing whatever that means to you. In Mac's world, what is responsible AI? Well, we spend a lot of time on this at Workday, and we think anything that impacts an employee standing, their compensation, their hiring, their job opportunities in the future, these are decisions where humans need to be in lieu to apply judgment. And so we spend a fair bit of time thinking about, okay, when we build systems, when we think about automation, what type of decisions are being either recommended or taken by an agent in a given situation?

And in those high-profile decisions, the ones that really have meaningful impact on employees, we spend a lot of time building those loops for human inspection. And you saw a bit of that today. We announced some configurable patterns for how people think about building agents and deploying agents. For areas where these types of decisions are being made, we ensure that there's a human in the loop on those types of decisions. we at Workday also have a responsible AI board that needs to review all of the new features that we are are releasing the market and ensuring that they're appropriately classified and that we're taking the right decisions around how we've applied different levels of automation and so we take it super seriously and we think that all of our customers should be taking it equally seriously because how we build these systems will ultimately dictate how much we trust these systems

How is that board? Who's on the board and what role do they have in making these decisions? So I sit there with our chief AI officer, our chief technology officer, and our president of product and technology. We have our head of IT, our general counsel, our chief ethics and compliance officer, as well as we have a responsible AI leader as well. Any examples of where that board has pushed back on something that seemed innocuous, but maybe you ended up not pursuing a feature that that responsible AI board flagged? Yeah, we actually spend a lot of time talking about what actions can be taken by an agent. So we think about workforce planning as an example. where we may want to talk about organizational structures.

And because that has real-world impact, what we don't do is allow the agent to work with a business leader outside of the appropriate loop for review from HRBPs, from whoever it might be. And so we worked with our responsible AI board to make sure we understood what was the right escalation path, who needed to be involved, and built that into the workflow itself. And the outcome change. Yeah. I mean, we involve the AI ethics team very early in the process as well. So this is not, it's not that we build something and then it comes to the Responsible AI board. We involve them in the early stages of the design process. Great example. One of the things that's a very disruptive force in the world of building enterprise software is that the lines are completely blurred between traditional roles. developers are now product owners, product managers. People in UX are writing code or using agents to write code.

Code is writing itself. Teachers are recommending how they should be constructed. As a product leader, how do you think about the current structure of your org and how will it look different in 18 months? I think we're going to have a lot more polymaths. So people who know all sorts of different skills and we're going to be a lot more organized around missions. There's great empowerment in that, right? I think we going to focus more on problem statements than job descriptions and skills and kind of the capability to manage through than the sort of static documentation that we had historically I would call it as job diffusion all the lines are blurring and they going to continue to blur as more and more of the capabilities are absorbed And we really are pushing in that direction from a product and engineering perspective at Workday. So we're encouraging engineers to learn to do more design work. We're encouraging product managers to operate

in quad code and build their own prototypes. And we're very much organizing ourselves around mission teams. And frankly saying, hey, we may have structures where we have people managers who aren't the project or team manager for the given mission. And that's a modernization of our organizational structure that allows us to move faster in capturing these opportunities. So let's make that real. So let's say you're talking to a lot of early career professionals, maybe even kids in college, who say, hey, I want to be in Max's org to use their polymaths. So what should I do now that will be maybe future-proof or make me an attractive candidate in a world where traditional roles are maybe giving way to polymaths? I mean, I think building is the most important thing. So it's the same thing I say to our teams is that the technology is changing quickly and your intuition around how it works and how you can create something that, to this point we made earlier, it has high value and it has high taste.

The only way to get there is by building and shipping things, seeing how the technology works, seeing what it requires in order to build a piece of software with the right feedback loop so it checks its own answer. The LLM checks its own answer and comes back with a validated result. It requires trying to ship something and seeing what doesn't work, what works, how is latency. Sometimes I had an example earlier today. A customer said, you know, I figured out how this works because I built an application to monitor all of my newborn baby's movements. And then I saw what worked and what didn't work and, you know, how it could come together. And that's a great example of just getting hands-on. And we need more people to do more of that. I will say most of the kids that we hire out of university, they are AI-pilled from the moment they walk in the door. So I love the energy and the enthusiasm and the way they think about problems because they've never existed in the workforce where they didn't have these tools that were effectively superhuman.

It feels like the way we have traditionally selected and nurtured talent have to change. Like the kind of artifacts of time we had more traditional or like any specific examples of how your talent selection and nurturing process is changing? i i do think that we're finding more of the process of intentionally developing people based on projects so what are the types of projects this person has been on what type of experience do we need to put in in place um i really like the the sort of direction of travel of the the sort of conversation in the industry around changing this the one thing that I'd say as well is that expertise actually has a premium today. And so we've lost a little bit of the focus when everybody can be a great generalist on what builds the level of expertise that is required in order to check the initial intuition of the models. And so much of what creates great

expertise is very difficult to describe. It's like your intuition that this is the right first step in a given direction and experts have a very difficult time talking about that but we as people leaders as organizational leaders need to figure out how to make sure we groom the next generation of talent that has that great intuition to make sure when we point our incredible ai agents at a given problem it's the right problem garrett stood on stage today and said something that is hard for a person in that role to be able to say. And he probably said, here's what I said a year ago, and we've over-delivered, and walked us through chapter and verse about what's happened last year. The pace is only accelerating. Just talk us through. How can he or you or Neil, et cetera, possibly be on stage next year and say that we also over-delivered with such wildly high expectations about the next year will hold.

The good news is we have new tools in all of our hands that give us the ability to continue accelerating alongside all this change. I'd say every one of the folks inside of Workday wakes up every day to make every piece of this a reality and then to add more. So what gives me the great expectation that next year we'll say, hey, we delivered on all of this, and what's more, we over-delivered. It's just that there are 20,000 workmates around the globe who are ready to help usher in this world. We'll be back here in a year, Max. We'll be having a version of this conversation. We'll both be floored by what happened, right? I'm looking forward to it. All right, we're about out of time, but you're not getting off the hot seat without answering one last very important question for me. Let's say it's 2031 and we're having a version of this conversation. what about max's job in 2026 will have been automated and what what's left what's max is the head of product at workday doing in five years i think there will be a lot of project

management that we still do today that will turn more into coaching right instead of the follow-ups to check the boxes, that still has to occur in order to keep everything moving at the velocity that we need. That's the type of thing where the system itself can take over. And then more of the time that I spend as the headed product will be around the pixels, the intuition, the judgment. How was that experience relative to expectation? And that's the exciting part. I want to believe that's true. I love the vision. We'll have a chance also to unpack that one. not just the one year out but maybe even the five year I look forward to it Max has been wonderful where can the audience learn more about you and the great work that your team does well we will have all sorts of recaps rising on the Workday website and I would encourage everybody to check it out we are an open book when it comes to what we're thinking about and look forward

to folks diving in thanks to how you know it was a lot of fun thank you well that's Max Wessel Senior Vice President of Product at Workday And gosh that's all the time we have for this Conversation on AI and the Future of Work As always I'm your host Dan Turchin from PeopleRain And of course we're back next week with another fascinating guest Yo it's the end of the show time to power it down AI subsist for humans wear the crown Team human in the house got the vibe so clever Dan Turchin from PeopleRain making us better We learned about AI for humans We're ready to conquer the future that's all for now See you next time

番組の概要欄(原文)

Send us Fan Mail Max Wessel is the SVP of Product at Workday, where he leads the applications teams and has spent the last year and a half on the AI transformation of its core applications. He founded his first company at 14, and before Workday he was CEO of Degreed and an Executive Vice President at SAP. Recorded live from the floor of Workday Rising 2026, this lightning round explores how product work is changing as it gets easier to generate code, and what it takes for people to trust the ...

出典・この記事について

番組
AI and the Future of Work: Artificial Intelligence in the Workplace, Business, Ethics, HR, and IT for AI Enthusiasts, Leaders and Academics(Dan Turchin)
元の回
SE 34: Max Wessel, SVP of Product at Workday | Live from Workday Rising 2026
配信日
要約作成日
公式サイト
www.PeopleReign.io

この要約・解説記事は、元の音声を文字起こしした内容をもとに AI(Claude)が日本語で作成したものです。 固有名詞や数値に誤りを含む場合があるため、正確な内容は元の音声でご確認ください。制作方法について

X でシェアApple Podcasts で聴く

関連エピソード