A Conversation about Designing Human-Centered Work in the Age of AI

Speaker A: I want you to think about, um, a smoke detector in your house.

Speaker B: Okay. Yeah.

Speaker A: Just sits up there on the ceiling. Right. Completely silent, totally useless until the exact moment your kitchen is, like, already filled with smoke.

Speaker B: Right. The fire is already going.

Speaker A: Exactly. I mean, it doesn't put out the fire. It doesn't teach you how to chop vegetables, and it definitely doesn't teach you how to, you know, cook safely in the first place.

Speaker B: No, it just screams at you.

Speaker A: It just screams to alert you to a disaster that is literally already happening. And, uh, for decades, we've basically been treating the global employee engagement industry exactly like that smoke detector.

Speaker B: Yeah, that's a really good way to frame it.

Speaker A: Right. We wait for the alarm to go off rather than just, I don't know, designing a kitchen where things don't catch on fire.

Speaker B: Yeah.

Speaker A: So whether you're, you know, prepping for a big strategic meeting or maybe rethinking your own career trajectory or just insanely curious about why your daily workflow feels like such an uphill battle, we've got something special for you today.

Speaker B: We really do.

Speaker A: On, um, this deep dive. We are unpacking a massive shift in how organizations function. We're talking about a fundamental rethinking of the workplace. Moving away from just, you know, measuring retrospective misery and moving toward actively designing human centered work.

Speaker B: And, um, the structural failure of that smoke detector approach, it's just staggering when you actually look at the economics behind it.

Speaker A: Well, the numbers are wild, right?

Speaker B: I mean, Gallup estimates that the global engagement industry is, ah, a $100 billion annual enterprise.

Speaker A: Wait, 100 billion? With a B?

Speaker B: With a B. Organizations are literally spending $100 billion a year just to take a picture of the past.

Speaker A: That is insane.

Speaker B: It is. And if you look at the visual backdrop behind me right now, um, you'll see a transition taking place. It's shifting from this incredibly sterile, gray, you know, isolated cubicle farm into a vibrant, interconnected, dynamic cityscape.

Speaker A: I love that visual.

Speaker B: Yeah. And that visual evolution is really the core premise of Dr. Jonathan H. Westover's research, which is our main source today. He argues that we have to move from viewing people as like, isolated units of labor in a gray box to recognizing them as whole humans operating in a complex ecosystem.

Speaker A: So moving from this idea of employee, uh, engagement to people experience.

Speaker B: Exactly. What's fascinating here is that organizations are entirely misaligned. They measure these retrospective snapshots instead of designing prospective environments.

Speaker A: Okay, let's unpack this. Because that $100 billion figure is just hard to wrap your head around.

Speaker B: It's massive.

Speaker A: We are spending the equivalent of like the GDP of a small country every single year just to ask people to rate their workplace on a scale of 1 to 5.

Speaker B: Yep. Strongly agree to strongly disagree.

Speaker A: Right. And then the executives look at the dashboards and HR runs these focus groups to interpret the low scores, and managers are pushed into, uh, emergency training sessions. But the actual fundamental reality of the workday doesn't change.

Speaker B: No, it rarely does. The high performers still leave remote. Workers still feel totally isolated.

Speaker A: Because the core issue seems to be that an engagement survey, it basically just identifies dissatisfaction after it's already crystallized.

Speaker B: Precisely. By the time that data is processed and presented to a leadership team in a PowerPoint, the opportunity for a real meaningful intervention is just gone.

Speaker A: Right. The person who was frustrated back in March has already mentally checked out by the time you're reading the survey results in October.

Speaker B: Exactly. And the limitation isn't necessarily, um, the statistical validity of the surveys themselves. The problem is the whole conceptual framing.

Speaker A: How so?

Speaker B: Well, we're basically applying a reactive measurement tool to a systemic design problem. We can actually borrow a foundational concept from Pyne and Gilmour here.

Speaker A: Oh, the experience economy, guys.

Speaker B: Yes, exactly. Consumer market. It's universally accepted that a company doesn't just compete on the like, utilitarian function of a product anymore. They compete on the entire end to end experience.

Speaker A: Right. Discovering it, buying it, using it, getting support.

Speaker B: Exactly. I mean, if you buy a smartphone and the unboxing process is a nightmare and the software is super clunky and customer service is just unreachable, you blame the company, right?

Speaker A: Totally. I don't blame myself for being a bad consumer.

Speaker B: Right. But internally, inside the walls of the organization, we have historically blamed the worker for not being engaged with the completely broken system.

Speaker A: Wow. We blame the user.

Speaker B: We blame the user. And we are just now waking up to the reality that organizational design requires the exact same experiential rigor that we apply to consumer products.

Speaker A: But wait, let me push back a little here. Yeah. Isn't People Experience just like a trendy HR rebranding of employee experience? I mean, why does this terminology actually matter to the listener who is just logging into their computer at 9am?

Speaker B: That's a totally fair question. It can definitely sound like corporate rebranding. Just a trendy new domain name and a different font on the handbook, right?

Speaker A: Yeah, exactly.

Speaker B: But there is a massive psychological difference between those two terms. When an organization uses the word employee, they're framing that individual purely through a contractual transactional lens.

Speaker A: So we pay you capital, you give us labor.

Speaker B: Exactly. The relationship is entirely confined to a job description. But the term people, uh, that forces an acknowledgement of a much more complex reality.

Speaker A: Because you don't just stop being a person when you clock in.

Speaker B: Right. The person logging into that virtual meeting at 9am doesn't cease to be a parent or a caregiver or a community member. They might be managing a chronic health condition.

Speaker A: Right.

Speaker B: Recognizing those multiple identities is not just a moral stance, it's an operational imperative. And this is where Rothbard and Ramarajan's research is so crucial. They dive into this concept of identity fragmentation.

Speaker A: Identity fragmentation? What exactly is that?

Speaker B: Well, when a workplace culture demands that an individual suppress their non work identities, like when they feel forced to hide the anxiety of managing an aging parent's healthcare, or they have to conceal that they need to leave at 5pm sharp for a civic commitment, they have to maintain this fragmented facade.

Speaker A: And M. That takes effort.

Speaker B: A massive amount of effort. The mechanism at play here is a severe cognitive and emotional tax. Suppressing a core part of your identity requires active, continuous psychological energy.

Speaker A: It makes me think of, um, a computer running way too many heavy applications in the background.

Speaker B: Yes, that's a perfect analogy.

Speaker A: Like, even if you're just trying to type a simple document on the screen, the battery is just draining so fast because the processor is working overtime on tasks you can't even see.

Speaker B: Exactly.

Speaker A: If you have to spend 20% of your mental energy just pretending to be this idealized, unencumbered corporate robot that is 20% less cognitive capacity you have for

Speaker B: creative problem solving or strategic thinking or deep focus, you are exhausted before the actual work even begins.

Speaker A: Yeah. You're burnt out by 10:00am Right.

Speaker B: And when an organization designs a people experience that legitimately supports the whole person, they're actively closing those background applications. They're reducing that cognitive tax.

Speaker A: So that's the real difference between the two approaches.

Speaker B: Exactly. Engagement measures psychological attachment at highly specific isolated intervals. It's checking your pulse once a year. But people experience measures. Continuous daily touch points.

Speaker A: Like the onboarding clarity or IT support.

Speaker B: Yes. It's the clarity of the instructions on day one. It's the responsiveness of the IT department when your system crashes. It's the tone of the email your manager sends after a mistake. It is the cumulative effect of every single interaction.

Speaker A: Okay, so acknowledging this whole person isn't just a warm fuzzy HR concept.

Speaker B: Yeah.

Speaker A: Has a massive financial implications.

Speaker B: Right. Yeah.

Speaker A: Uh, let's talk about the hard roi.

Speaker B: Oh, it absolutely does. Supporting the Whole person isn't just about empathy. It has quantifiable structural impacts on the bottom line.

Speaker A: I know. The source cited some IBM data that was pretty wild.

Speaker B: Yeah, the IBM Smarter Workforce Institute data. They found that organizations scoring in the top quartile for experience design achieve 4.4.2 times higher average profit.

Speaker A: 4.2 times?

Speaker B: Yeah. And 2.1 times higher average revenue growth compared to organizations in the bottom quartile.

Speaker A: That's not just a minor bump in efficiency. I mean, a profit multiple of four fundamentally alters a company's entire market position.

Speaker B: It changes everything.

Speaker A: But, you know, correlation isn't always causation. What is the actual granular mechanism that is driving that massive profit differential? Like, where is the money actually being lost in the bad companies.

Speaker B: If we connect this to the bigger picture, the primary mechanism eroding that profit is what researchers call workplace friction.

Speaker A: Friction? Okay.

Speaker B: Yeah. Friction is basically the unnecessary effort required to accomplish a task. It's the gap between what you need to do and the systemic barriers the organization places in your way.

Speaker A: Got, uh, it.

Speaker B: And research by Mark and colleagues quantifies this brilliantly. They found that for knowledge workers, workplace friction drains roughly 20 to 30% of daily productivity.

Speaker A: 20 to 30%. That is a huge chunk of the day.

Speaker B: Right, and if you scale that across an enterprise, the financial bleeding is just catastrophic.

Speaker A: I mean, think about it. If A company has 10,000 employees and they're losing a quarter of their day to unnecessary effort, the company is basically paying 2,500 employees a full salary to do absolutely nothing.

Speaker B: Nothing but fight with internal bureaucracy and broken systems. Exactly.

Speaker A: It's like having a pebble in your shoe.

Speaker B: Oh, that's a good way to put it.

Speaker A: Yeah, it doesn't seem like a big deal for the first block. Right? You just adjust your stride slightly and keep going. But try running a marathon or, you know, a, uh, fiscal year with it.

Speaker B: You'd be in agony.

Speaker A: Right. Your back aches, your pace drops by 30%. Suddenly you've lost all your speed. But how does 20 to 30% of our day just vanish into this unnecessary effort? What does that actually look like?

Speaker B: Well, it evaporates through compounding micro barriers. Um, it's a procurement process that requires sequential approvals from four different stakeholders. And none of them have visibility into the other's workflows. Ugh.

Speaker A: Uh, I've been there.

Speaker B: Right. Or it's outdated enterprise software where an employee has to manually enter the exact same client data into three separate, totally disconnected databases.

Speaker A: Oh, the worst. Or when you have a matrix organization and literally no one knows who has the final decision rights.

Speaker B: Exactly. Which results in those endless diplomatic email chains that consume hours and produce zero outcomes. But the real danger of this friction isn't just the immediate time lost. It's the organizational scar tissue it creates over time.

Speaker A: Scar tissue. I like that phrase. It implies that friction doesn't just reset at the end of the day, it builds up.

Speaker B: Exactly.

Speaker A: If a workforce spends three years fighting a terrible expense reporting system, their psychological posture toward the company fundamentally changes.

Speaker B: And this is exactly what Rafferty and Jimison found in their research on change management. They showed that an employee's willingness to embrace any new organizational initiative is almost entirely dictated by their accumulated experiences with past changes.

Speaker A: So if the last three software rollouts were just like chaotic, poorly communicated disasters.

Speaker B: Right, that resulted in lost files and weekend work, um, the workforce develops a deep structural skepticism.

Speaker A: So the next time leadership announces an exciting new strategic pivot, everyone is just rolling their eyes.

Speaker B: Exactly. The default response isn't enthusiasm. It's active resistance, or just quiet non compliance. Past poor experiences create skepticism for future changes.

Speaker A: That makes total sense. So to see the inverse of that, what happens when you actively target and remove a source of friction, we can look at the Adobe case study, right?

Speaker B: Yes. Adobe's, uh, a perfect example. They realized that the traditional annual performance review was basically the ultimate organizational pebble in the chute.

Speaker A: Oh, absolutely. Annual reviews are the worst.

Speaker B: They really are. For decades, companies have relied on these massive backward looking evaluations. They generate profound anxiety for the individual, they create weeks of administrative dread for the manager, and they rarely provide any actionable developmental value.

Speaker A: It's just an incredibly high friction process that taxes everyone.

Speaker B: Right, and Adobe recognized that this annual review was actively harming the neuroplasticity required for learning and growth.

Speaker A: Wait, neuroplasticity?

Speaker B: Yeah, I mean, when an employee sits down for a review that dictates their compensation and basically judges their entire year, their brain enters a defensive state. And you cannot learn when you are defending yourself.

Speaker A: That is so true. Your fight or flight kicks in.

Speaker B: Exactly. So Adobe completely dismantled that architecture. They shifted from the annual review to continuous check ins.

Speaker A: Like just regular conversations?

Speaker B: Yeah, frequent forward looking conversations that focus on strengths, immediate, uh, course correction and future growth, rather than just pointing out deficits from eight months ago.

Speaker A: The mechanics of that shift are actually brilliant. By breaking one massive high stakes confrontation into a dozen low stakes conversations, they completely neutralize the anxiety spike.

Speaker B: Yes, it has a dual benefit. The emotional tax on the person plummets, but the performance feedback loop for the Company actually gets tighter and more accurate.

Speaker A: It's a win win. And when companies fail to make these kinds of systemic fixes, the cost of employee turnover is just staggering. I mean, the estimated replacement cost for a knowledge worker's what, 50 to 200% of their annual compensation, depending on the

Speaker B: scarcity of their skills?

Speaker A: Yes, that's massive.

Speaker B: And that turnover cost is where the theoretical concepts of experience Design hit the CFO's ledger. Salesforce provides one of the most compelling examples of this.

Speaker A: What did Salesforce do?

Speaker B: Well, they identified a significant retention problem occurring within an employee's first 12 months. And the traditional corporate response to early turnover is usually a blunt instrument. Right. Like increase starting salaries or offer retention bonuses.

Speaker A: Throw money at it.

Speaker B: Right. But Salesforce took an experiential approach. They utilize journey mapping and iterative prototyping to completely redesign the new higher onboarding experience.

Speaker A: Though they shifted the onboarding process from like a transactional checklist to an actual supportive journey. And didn't they improve their 12 month retention by something crazy?

Speaker B: 18 percentage points.

Speaker A: Wow.

Speaker B: Yeah. And that single intervention saved them over $50 million annually in reduced recruiting, hiring and training costs.

Speaker A: $50 million just by making sure a new employee doesn't feel like they're in a chaotic freefall on day one.

Speaker B: Exactly. But beyond the corporate ledger, we really have to acknowledge the human cost of bad design. When you force people to operate in a high friction environment day after day, it literally makes them sick.

Speaker A: You mean clinical outcomes?

Speaker B: Yes. Maslach and Leiter's foundational research on burnout shows that sustained workplace frustration, ambiguity, and lack of autonomy contribute directly to clinical anxiety, depression, and physical health issues.

Speaker A: That's sobering. So a poorly designed workflow is actually a public health issue?

Speaker B: It really is. And ironically, the organization ends up absorbing those costs anyway through escalated health care premiums, short term disability claims, and chronic absenteeism.

Speaker A: So designing a human centered experience isn't just a nice HR thing. It's a financial necessity and an ethical obligation. Okay, so if friction is the enemy and experience is the product we're building, how do organizations actually start designing a better day for you? I mean, you can't fix a workflow you don't understand, right?

Speaker B: No, you can't. And this is where we have to move away from those process flowcharts drawn by auditors in a boardroom and move toward actual journey mapping.

Speaker A: Here's where it gets really interesting. Tell me about journey mapping.

Speaker B: Journey mapping is the core methodology of experience design. It's the practice of visualizing the end to End trajectory of a specific workplace experience strictly from the perspective of the user.

Speaker A: So not how it's supposed to work.

Speaker B: Right. An auditor's flowchart shows how a process is supposed to work. In a perfect world, a journey map captures how the process actually feels.

Speaker A: In reality, it captures the emotional arcs, the confusion. All those shadow IT systems people invent just to bypass broken rules.

Speaker B: Exactly. And the techniques used to build these maps are fascinating because they require actual observation rather than just asking people to fill out a survey.

Speaker A: Like shadowing?

Speaker B: Yes. Shadowing. Researchers physically or virtually observe an employee's workflow to see the silent workarounds they rely on. They also use experience diaries, where employees record their emotional state and friction points in real time over a week.

Speaker A: That sounds super intensive. What about critical incident interviews? I read about those in the Source.

Speaker B: Yeah, those dive deep into the specific chain of events that led to a major failure or a major success. But honestly, the most intriguing technique is the sentiment analysis of digital interactions.

Speaker A: Okay, wait. How does an organization analyze sentiment without violating privacy? I mean, that sounds a little Big Brother.

Speaker B: That is the crucial distinction. It is about metadata and aggregate trends, not individual surveillance. Using natural language processing, organizations analyze communication patterns across the enterprise, but not the private contents.

Speaker A: So they aren't reading my DMs to see if I'm complaining about my boss.

Speaker B: No, no. The system is looking at the metadata of a workflow. For example, if a specific procurement process consistently generates help desk tickets containing high stress keywords. Or if resolving a routine approval suddenly requires a huge cluster of cross departmental messages at 8vero p a Friday.

Speaker A: Oh, I see.

Speaker B: Yeah. The data passively flags that journey as broken. It identifies the friction hotspot, allowing the organization to intervene without requiring a single employee to complain on a survey.

Speaker A: That's brilliant. But once you map these journeys and find the friction, you have to figure out where to put your resources. You can't fix every single minute of the workday all at once.

Speaker B: You have to prioritize. And this is where Nobel laureate Daniel Kahneman's peak end rule becomes incredibly useful.

Speaker A: Okay, let's break down Kahneman's peak end rule. This is so relatable.

Speaker B: Kahneman's research reveals a profound quirk in human psychology. When we evaluate an experience after the fact, we do not take a mathematical average of every minute we spend.

Speaker A: We wait certain moments. Heavier.

Speaker B: Exactly. Our memory heavily weights two specific points. The most intense moment of the experience, which is the peak, and the final moment, which is the end.

Speaker A: Right. So think about your last vacation. If you spend 10 days in Hawaii and months later, someone asks you how the trip was. You don't calculate an average score of all 240 hours.

Speaker B: No, you definitely don't.

Speaker A: You remember the peak like the afternoon you went scuba diving and saw a pod of dolphins. And you remember the end. The grueling, delayed, turbulent flight home where the airline lost your luggage.

Speaker B: Exactly. You completely forget the five days in the middle where you just ate average hotel breakfast and read a book by

Speaker A: the cool work is the exact same way. You don't remember the 200 random Tuesday mornings you spent answering emails. You remember the day you received a massive promotion. And you remember the day a huge project failed spectacularly.

Speaker B: And that moment of failure is an excellent example of a peak moment. The way a manager reacts the first time an employee makes a significant mistake establishes the psychological safety baseline for the rest of that employee's tenure.

Speaker A: So if the manager yells at them.

Speaker B: Right. If the manager reacts with punitive anger, that peak moment solidifies a culture of fear that will dictate the employee's behavior for years. Organizations have to map and curate these high stakes moments.

Speaker A: They can't just leave them up to chance.

Speaker B: Exactly. And Intuit provides a brilliant case study in applying this logic to the hiring journey, specifically for, you know, highly competitive software engineering talent.

Speaker A: What did Intuit do?

Speaker B: Well, they mapped the candidate journey and isolated a massive friction point. The temporal gap between the final interview and the actual delivery of the offer.

Speaker A: Oh, that waiting period is the worst.

Speaker B: It is. For the hiring manager, a two week delay is just routine administrative processing. But for the candidate, that two week gap is an agonizing black hole of uncertainty.

Speaker A: And that anxiety probably drives them to just accept competing offers. Right? Just to relieve the stress of waiting.

Speaker B: Exactly. And the genius of Intuit's intervention is that they didn't attempt to win the talent war by simply jacking up the salary offers. They fundamentally redesigned the experience of waiting.

Speaker A: How so?

Speaker B: They implemented transparent timelines, provided constant interim communication, and gave candidates real time visibility into the exact status of their application.

Speaker A: So they just communicated better.

Speaker B: Yeah. And by removing the anxiety of the unknown and curating that specific peak moment, Intuit reduced their offer decline rate by 23%.

Speaker A: Wow. Just by being transparent. And MasterCard did something similar with their onboarding, right?

Speaker B: Yes. MasterCard recognized that the first 90 days of employment are basically a prolonged peak moment.

Speaker A: Because traditionally, onboarding is just an administrative gauntlet.

Speaker B: Totally. Here's your laptop. Sign these tax forms, watch this boring compliance video. Now get to work. Right, but MasterCard shifted this from A transaction to a highly curated journey. They integrated personalized welcome content, structured conversation guides for managers, and they built in these things called relationship accelerators.

Speaker A: Relationship accelerators? What are those?

Speaker B: It's a way to actively connect new hires with mentors and key stakeholders right away. Because the hardest part of joining a massive enterprise isn't learning the software. It's understanding the invisible social network of who actually gets things done.

Speaker A: Oh, 100%. It's knowing who to ask when the printer breaks or when a project stalls.

Speaker B: Exactly. And by engineering those connections early, MasterCard radically reduced the isolation of the new hire. The result was a reduction in timed productivity by six weeks.

Speaker A: Meaning they were generating value a month and a half faster.

Speaker B: Yes, and it boosted their 12 month retention rate by 15 points.

Speaker A: That's incredible. But you know, a journey map that works perfectly for a 22 year old single software engineer might be an absolute nightmare for a 40 year old manager with three kids.

Speaker B: Oh, absolutely.

Speaker A: I mean, what is a delightful peak moment for one person might just be an annoying distraction for someone else. So if you can't rely on a single universal journey map, how does a massive company actually scale this?

Speaker B: Well, this brings us to segmentation. You scale it through the development of Personas. You have to completely abandon the illusion of the homogenous workforce.

Speaker A: Personas. Like in marketing?

Speaker B: Exactly like in marketing. Highly detailed research back representations of distinct user segments. For example, Unilever, which has over 150,000 employees globally, recognized that their legacy one size fits all HR strategy was failing

Speaker A: because it was aiming for a statistical average that doesn't actually exist.

Speaker B: Precisely. And when Unilever built their Personas, the divergence in needs was stark. They discovered that their young early career employees in emerging markets were highly focused on aggressive skills development and and international exposure.

Speaker A: They wanted to climb a ladder fast.

Speaker B: Right. But they're experienced veteran professionals in developed markets prioritized entirely different factors. They wanted, uh, deep work life flexibility, autonomy over their schedules, and specific health and wellness benefits.

Speaker A: So if you give everyone the exact same benefits package, you're pleasing no one.

Speaker B: Exactly. By acknowledging these distinct Personas, Unilever could target their investments. Instead of rolling out a global leadership program that half the company didn't want, they tailored the learning pathways and benefits to match the specific needs of each segment.

Speaker A: Which improves engagement and probably saves a ton of money.

Speaker B: Yes, it optimized operational efficiency by eliminating waste on broad brush initiatives.

Speaker A: And the necessity of these Personas becomes undeniable when you look at caregiving responsibilities. I mean, the Harvard Business school research from 2019 showed that 73% of US employees have some form of caregiving responsibility.

Speaker B: 73% let that sink in.

Speaker A: It's massive. That encompasses parents of newborns, people with school age kids, those caring for aging parents or family members with disabilities. Nearly three quarters of the workforce. And yet corporate policies are usually designed around this myth of the ideal worker.

Speaker B: Yeah, that ideal worker construct is a total relic of the mid 20th century. It assumes an employee with zero outside responsibilities, infinite schedule flexibility, and a partner at home handling all the domestic labor.

Speaker A: Which is just not reality for almost anyone anymore.

Speaker B: No, it's not. And when you design career progression models and daily workflows around that outdated assumption, you create a system that inherently penalizes the 73% of your workforce who cannot meet that standard. You force caregivers into an impossible zero sum choice between their family and and their financial security.

Speaker A: And because of, you know, deeply entrenched societal norms. This friction disproportionately impacts women who statistically still shoulder the majority of caregiving duties.

Speaker B: Absolutely. If an organization does not explicitly design Personas and workflows that accommodate caregiving, they are actively pushing vital talent out of their pool. Flexibility cannot be an exception. Granted by a nice manager. It has to be a systemic default.

Speaker A: Right. It has to be built in. And speaking of being built in, the evolution of Personas leads us directly into the role of artificial intelligence.

Speaker B: Yes, this is where it gets very futuristic.

Speaker A: Because static Personas are a big improvement. Sure, but AI allows for dynamic hyper personalization in real time, right?

Speaker B: Exactly. Instead of just placing an employee in a static working parent bucket, an AI driven platform can adapt to their immediate context. It can dynamically match them with mentors who navigated similar transitions or surface highly specific Micro M learning content. Right. When they take on a new project.

Speaker A: But wait, let me push back here. Isn't there a massive danger here with AI?

Speaker B: There is.

Speaker A: I mean, if an enterprise algorithm is constantly ingesting my behavioral data, tracking what links I click, analyzing who I message, monitoring my time on tasks, all, uh, to determine my Persona, doesn't this just become a creepy surveillance tool under the guise of personalization?

Speaker B: This raises an important question, and the researchers are acutely aware of this risk. Work by Tambe, Capelli and Yakubovich explicitly outlines the dangers of deploying AI in hr.

Speaker A: So they warn about it.

Speaker B: Yes. The foundational rule for AI in experience design is that the technology must serve employee agency and well being, not just function as an extraction mechanism for productivity.

Speaker A: Okay, so if the AI is just tracking my mouse movements to make sure

Speaker B: I'm not slacking off, then it instantly destroys psychological safety. It weaponizes the technology against the worker.

Speaker A: But if that same AI infrastructure is utilized to, say, proactively identify systemic overload. Like if the algorithm notices that I've been logging in for 60 hours a week for a month, and it automatically tells my manager to check in on me and suggests mandatory time off.

Speaker B: Yes. That fundamentally enhances the experience. It shifts the AI from a surveillance mechanism to a, uh, protective mechanism. It's the difference between having a warden monitoring your cell and having a highly competent executive assistant protecting your calendar.

Speaker A: I love that distinction. A warden versus an assistant.

Speaker B: Exactly. And there's a secondary risk with AI that we have to manage the automation of human connection. Right at the moment, empathy is required most.

Speaker A: Oh, like dealing with a chatbot when you're having an actual crisis.

Speaker B: Right. If an employee is navigating a highly complex, emotionally charged situation, like trying to arrange emergency medical leave for a spouse, forcing them into a doom loop with a friend. Frustrating. Dead end chatbot creates an incredibly traumatic experience.

Speaker A: It's so alienating.

Speaker B: It is. Organizations have to map their journeys to understand exactly where AI can seamlessly augment human capability and where the nuance and empathy of a human being are just absolutely irreplaceable.

Speaker A: So speaking of technology, the tools we use and the managers we report to are basically the two biggest architects of our daily experience. And right now, both of those are heavily flawed.

Speaker B: They're under immense strain. Yes.

Speaker A: Let's talk about the digital architecture first. There's this massive chasm between consumer tech and enterprise tech.

Speaker B: Oh, it's night and day. In our personal lives. We navigate ecosystems built by Apple or Google. We're used to apps that are instantly intuitive, integrated and zero friction.

Speaker A: But then you log into your corporate

Speaker B: network and you're transported back decades, literally.

Speaker A: Think about the last time you had to log into four different portals with four different passwords just to request a single day off.

Speaker B: Oh, it's so common. You have to log into a legacy HR system to submit the request, a separate scheduling app to block the calendar, A, uh, project management tool to reassign your deliverables, and then an email client to notify your team.

Speaker A: The cognitive load required just to manage the software exceeds the cognitive load of the actual job.

Speaker B: This is why the research insists that organizations adopt an experience led digital principle. Historically, IT departments bought software based on security and feature lists promised by the vendor. They rarely asked what is the actual sequence of tasks this human being needs to accomplish today?

Speaker A: They didn't start with the user needs.

Speaker B: Exactly. But Schneider Electric provides a masterclass in solving this digital friction at scale.

Speaker A: Schneider Electric, they have what, like 135,000 employees?

Speaker B: Yes. Huge global workforce. And they realized people were losing vast amounts of time navigating this labyrinth of legacy systems. But instead of attempting the impossible task of ripping out and replacing every single

Speaker A: piece of software, which would take a decade.

Speaker B: Right. They built a unified single layer digital experience over the top of the existing infrastructure. They used APIs and single sign on to create one clean dashboard with intelligent search and AI support.

Speaker A: So the employee just deals with the clean dashboard and it talks to the ugly systems in the background.

Speaker B: Exactly. And this architectural overlay saved an average of 35 minutes per employee per week.

Speaker A: Wow, 35 minutes a week times 135,000 people. That is millions of hours of human potential reclaimed.

Speaker B: Millions of hours previously burned on digital frustration.

Speaker A: Okay, so you fix the tech. But digital friction doesn't just hurt the frontline worker, it burns out the manager. Which brings us to the second pillar. The managerial squeeze.

Speaker B: Yes, research by Harder and colleagues demonstrates that the manager is the single most important variable in the employee experience. A great manager can shield a team from a toxic culture, but a terrible manager can ruin the experience at a great company.

Speaker A: But the research is also really empathetic to managers.

Speaker B: Right.

Speaker A: Because they are in a punishing position.

Speaker B: The managerial squeeze. We expect managers to be empathetic coaches, strategic visionaries, and rigid operational taskmasters all at the same time.

Speaker A: It's like expecting an air traffic controller to also serve peanuts in the cabin.

Speaker B: That is hilariously accurate. And as organizations flatten, they continuously pile new administrative responsibilities onto managers without ever sunsetting the old tasks.

Speaker A: So they're buried in budget approvals and compliance audits. And we're telling them to also be these deep empathetic mentors.

Speaker B: Right. And a panicked, burned out manager cannot create a safe environment. Their stress cascades down the organizational chart.

Speaker A: So how did Cisco fix this? They did a whole redesign.

Speaker B: Right. Cisco realized that sending exhausted managers to a two day seminar on active listening was a futile bandage. They needed structural change. So they deployed AI powered administrative assistance specifically designed to absorb the routine low value friction.

Speaker A: Like calendar Tetris and basic approvals.

Speaker B: Yes. And by automating that minutia, Cisco managers reported spending 40% more time engaging in actual high value coaching and team development.

Speaker A: They freed the humans to actually do the human work.

Speaker B: Precisely. Start with user needs, not system capabilities.

Speaker A: But fixing the tech and clearing the manager's schedule isn't enough. If the foundational systems are inherently biased. Like if you take a biased system and make it run faster with a sleek digital overlay, you're just accelerating the inequity.

Speaker B: That is a critical point. We have to look at experience design strictly through the lens of equity and inclusion. Standard neutral policies actually perpetuate inequity all the time.

Speaker A: Right, and the research by Carel and Simard on performance evaluations really illustrates this. We think of performance reviews as objective

Speaker B: measurements of merit, but the sociological data proves they are highly subjective. Carell and Simard found that women consistently receive feedback that is significantly vaguer than the feedback provided to men.

Speaker A: And vague feedback doesn't help you get promoted.

Speaker B: Exactly. It deprives the individual of the specific actionable guidance required to navigate the corporate ladder. Disabled employees are also frequently evaluated against entirely different moving criteria.

Speaker A: So what does this all mean? How do organizations stop retrofitting diversity and actually build it in from day one?

Speaker B: It requires inclusive design as a core architecture, not a peripheral HR initiative. Accenture's redesign of their parental leave policy is a profound case study here.

Speaker A: Oh, this is the one about the fathers taking leave?

Speaker B: Yes. Accenture offered a generous parental leave policy that was, on paper, entirely equal, available to any new parent, regardless of gender. But the behavioral data showed it was almost exclusively being used by mothers.

Speaker A: Because the unwritten cultural norms basically said if a man takes three months off, he's not committed to the firm.

Speaker B: Exactly. Having technical permission from HR is very different from feeling culturally secure enough to actually use it.

Speaker A: So how did they fix the culture?

Speaker B: They implemented targeted manager training to actively dismantle unconscious bias. But more importantly, they built internal peer communities for fathers who were taking substantial leave.

Speaker A: Providing social proof.

Speaker B: Yes, they engineered the culture to make it socially expected for non birthing parents to step away. And the outcome was a 300% increase in fathers taking parental leave.

Speaker A: That is a masterclass in inclusive design. Yeah, you don't just offer the policy, you design the usage of the policy to be socially acceptable.

Speaker B: And by normalizing leave for fathers, they leveled the caregiving playing field, which significantly improved the retention and return to work experience for mothers, too.

Speaker A: It's all connected. But this level of cultural engineering relies entirely on psychological safety. Right? Amy Edmondson's work.

Speaker B: Yes. Psychological safety is the shared belief that you can speak up, admit mistakes, or propose wild ideas without facing humiliation. It's the bedrock of belonging to. Without it, your journey maps and AI Personas are totally useless.

Speaker A: A great onboarding app means nothing in a toxic culture.

Speaker B: Exactly. The research draws a sharp Line between tactical improvements and cultural foundations. Patagonia is the ultimate example of this.

Speaker A: Because their culture is rooted in genuine purpose.

Speaker B: Yes. Steger and colleagues confirmed that when employees perceive their work as meaningful, their well being and performance skyrocket. Patagonia operationalizes this from day one. During onboarding, new hires actively participate in environmental activism projects.

Speaker A: They don't just read the mission statement, they actually go out and do it.

Speaker B: Right. And when the cultural foundation is that coherent, the tactical policies, like their extreme schedule flexibility to go surfing when the waves are good, they make logical sense. They're structural reinforcements, not just random HR perks.

Speaker A: Okay, all this sounds incredible, but how does an organization actually build and maintain this without it being just another passing HR fad? I mean, structurally, how do they do it?

Speaker B: Well, a, uh, 2022 Deloitte survey exposed a severe capability gap. 87% of organizations are doing those legacy engagement surveys, but only 34% have dedicated, experienced design teams.

Speaker A: And only 18% actually map journeys.

Speaker B: Right, so the intent is there, but the architectural capability is completely missing. To build it, you have to restructure Power Dynamics. Microsoft did this by completely overhauling hr. They placed employee experience directly under the chief people officer.

Speaker A: Oh, they made a dedicated specialized team.

Speaker B: Yes, staffed with behavioral scientists, UX researchers, service designers, and they mandated experience quality standards for all HR initiatives.

Speaker A: So they treat the employee experience with the exact same rigor that a tech company treats its flagship product.

Speaker B: Precisely. Uh, and IBM addressed this by creating an experience design academy to build t shape's capabilities.

Speaker A: T shaped capability.

Speaker B: It means building broad horizontal literacy across the whole HR population. Like basic journey analysis coupled with deep vertical expertise in a specialized subset like behavioral economics or predictive data analytics.

Speaker A: So HR is borrowing heavily from marketing.

Speaker B: And it Absolutely. And Marriott shows us how to maintain this with a continuous improvement methodology. They don't wait for an annual survey. They do quarterly reviews. And they a b test new frameworks with a small cohort before deploying them globally.

Speaker A: Which brings up a huge risk here for the listener. Survey fatigue.

Speaker B: Oh, yes. Uh, the worst reaction to this is replacing the annual survey with a pop up microsurvey after every single task.

Speaker A: Nobody wants a pop up survey asking how many stars would you rate this calendar invite after every email.

Speaker B: Exactly. Aggressive measurement degrades the very experience it's trying to evaluate. The structural shift has to be toward passive behavioral and predictive metrics like tracking

Speaker A: internal mobility rates or monitoring m the resolution time of IT tickets.

Speaker B: Right. Or using that aggregate sentiment analysis to detect early warning signs of team burnout before people actually quit. You have to generate operational insight passively.

Speaker A: So we've really moved from an annual survey to treating the workplace as a continuously evolving product.

Speaker B: Yes. As artificial intelligence accelerates the commoditization of products and services, the technology available to competing firms will reach parity. When the tech is equal, the only sustainable competitive advantage remaining is the structural quality of the daily human experience.

Speaker A: That is powerful. Well, I want to thank you, the listener, for coming on this extensive deep dive with us today. To quickly recap the ground we've covered, we unpacked the billion dollar failure of engagement surveys, the hidden tax of workplace friction, and how, uh, companies like MasterCard, Cisco and Patagonia are entirely rewriting the architecture of the modern workday.

Speaker B: And if we extrapolate these findings into a final provocative thought for the future, if organizations are now forced to compete on the quality of the daily human experience, just like they compete for customers, it fundamentally shifts the power dynamic.

Speaker A: How so?

Speaker B: It means that you, the worker, are no longer just the labor. You are the ultimate consumer market. And that changes not just how companies act, but what you should unequivocally demand the next time you accept a job.

Speaker A: You are the consumer of the workplace experience. So think about your own workplace journey this week. Where is the friction draining your energy? What are the peak moments? And most importantly, is your organization designing for the whole you, or are they just waiting for the smoke detector to go off? Keep asking those questions and we'll see you on the next deep dive.