A Conversation about Designing Motivating Digital Workplaces
Team Leaders' Audio Digest · 2026-05-25 · 23 min
Substance score
39 / 100
Five dimensions, 20 points each
What our scoring noted
Our reviewer’s read on each dimension, with quotes from the episode.
Insight Density
The episode surfaces a handful of genuinely useful concepts—means efficacy vs. self-efficacy, the mediator chain between tools and motivation, and the three-layer tech taxonomy—but they are buried under heavy conversational filler ('Oh wow,' 'Exactly,' 'That makes so much sense') and the baseline frameworks (JD-R model, SDT, flow theory) are well-established in organizational psychology rather than novel.
technology rarely motivates us directly
What the technology actually does is reshape these underlying psychological mediators. Things like your sense of autonomy, the variety of skills you get to use in a day, and your perceived control over your workflow
Originality
The framing around means efficacy and the warning against leaderboards in interdependent work offer some fresh angles, but the episode's backbone is recycled frameworks (self-determination theory, job demands-resources model, flow theory) and the overall thesis that bad tech kills motivation is far from contrarian.
means efficacy is believing that your tools actually work
This actually updates older organizational models that used to think of technology as just a hygiene factor
Guest Caliber
There is no guest; two hosts summarize a brief by Dr. Jonathan H. Westover without any identified practitioner credentials of their own, meaning the episode has zero first-hand operator experience to draw on and relies entirely on secondary interpretation of academic research.
Today we are unpacking a really fascinating brief by Dr. Jonathan H. Westover, and it's titled Designing Motivating Digital Workplaces
Our goal here is to decode how the tools that surround us at work actually shape our motivation
Specificity & Evidence
The episode does name real organizations and research approaches (Siemens Healthineers, Buurtzorg, City of Helsinki, Deloitte Leadership Academy, Bala and Vekatesh's latent growth ERP study) which adds some grounding, but there are zero concrete metrics, dollar figures, or timelines—every case study stays at a qualitative, anecdotal level.
They tracked an erp, an Enterprise Resource Planning System implementation. And they showed that during the rollout, employees perceived job characteristics heavily fluctuated, literally day by day
several European manufacturing groups took a really innovative approach. They set up digital shop floor academies for their CNC operators
Conversational Craft
The hosts use scripted pushback and Socratic questioning to advance the narrative reasonably well (the gamification challenge and the remote-work pushback are functional), but because there is no actual guest the 'follow-ups' are theatrical transitions, not genuine probing of a practitioner's claims, and the format cannot produce real productive disagreement.
Wait, let me push back a little bit here. What about the sheer flexibility of remote work? Doesn't working from a smartphone or, you know, taking your laptop to your couch directly motivate people?
Isn't gamification usually just corporate bribery? Like when my HR software gives me digital confetti for updating my password?
Conversation analysis
Computed from the transcript - who did the talking, and the verbal tics along the way.
Filler words
Episode notes
This research examines the relationship between digital technology and employee motivation, arguing that tools primarily influence engagement by altering job structures rather than through direct impact. The research categorizes workplace technology into spatial, operational, and augmentative layers, highlighting how these elements can either empower or restrict staff. To maintain a productive and motivated workforce, organizations should prioritize job redesign, employee autonomy, and participative decision-making during technological transitions. The guide also emphasizes the importance of building digital competence and using gamification carefully to avoid undermining intrinsic interest. For long-term success, leaders must recalibrate psychological contracts and treat continuous learning as essential infrastructure. Ultimately, the research provides evidence-based strategies for executives to ensure that evolving digital environments support, rather than erode, the human experience at work. See Privacy Policy at and California Privacy Notice at .
Full transcript
23 minTranscribed and scored by The B2B Podcast Index.
Have you ever had your company roll out, like, a shiny new software system or maybe a new messaging app? Oh, yeah, the classic we bought a new toy announcement. Yeah, exactly. Or even, you know, an AI assistant. And they're expecting everyone to be absolutely thrilled about it, but then you find that it just completely drains your will to work. It's the worst. You, you sit down at your desk, yeah. You open the new interface, and suddenly, like everything that used to take five minutes now takes 20. Literally 20 minutes. You're clicking through, what, five different menus just to log a really simple task, and you can practically feel your motivation just evaporating. Yeah. And you're sitting there looking at the screen, wondering why this massive, highly expensive upgrade feels like a demotion. You know? A demotion, Exactly. You go from feeling like a really competent professional to, I mean, feeling like an intern who doesn't even know how to use the printer. That feeling is just incredibly common. And actually, it is the exact mission of our deep dive. Today we are unpacking a really fascinating brief by Dr. Jonathan H. Westover, and it's titled Designing Motivating Digital Workplaces. Great read. It really is. Our goal here is to decode how the tools that surround us at work actually shape our motivation, and more importantly, what leaders should be doing about it to, you know, stop driving their teams absolutely crazy. So, okay, let's unpack this, because it feels like we've all been victims of a bad tech rollout at some point in our careers. Oh, we absolutely have. And I think the stakes for getting this right are. Well, they're much higher than just minor workplace annoyances. Right. It's not just complaining in the break room. Exactly. We are looking at a landscape right now where millennials and Gen Z workers are consistently citing outdated or even just poorly implemented tools as a credible primary reason to quit a job. Wow. So they'll actually walk out the door over bad software? They will. It's, you know, it's a retention crisis masquerading as an IT problem. Ubiquitous computing has redrawn the boundaries of work so fast, completely reshaping, like, who we collaborate with, when we do it, how we do it, that companies just haven't been able to absorb the psychological changes. That makes a lot of sense. So for a modern executive, asking, you know, what does this new software do to employee motivation is no longer some soft HR question. It is a critical bottom line operational input. Because, I mean, if the tools break the workflow or if they just make the user miserable, the work simply doesn't Happen. Right. But to really fix this motivation problem, we have to define the environment first. We need to understand what we're actually talking about when we say technology. Because we aren't just talking about laptops and monitors here. Right, right. That is a really crucial distinction. The research breaks the modern workplace technology portfolio data down into three distinct layers. And if you don't understand these layers, you cannot design a motivating environment. Okay, so what's layer one? The first layer is spatial physical. So this is your built environment. We're talking about the ergonomics, the physical layout of the office, the lighting, the furniture. Okay, so like the standing desks, the glass partitions, maybe those soundproof phone booths that literally every startup seems to have. Now you got it. That's layer one. Then you move to the second layer, which is the operational layer. Operational? Yeah. This is the information communication technology or ict. So this includes your enterprise software, your ERP systems, robotics on manufacturing floor, your communication platforms. So these are the tools that actually mediate the work itself. Like the stuff we usually picture when someone says work tech. Exactly, the functional tools. But then there is the third layer, and this one is growing the fastest. And honestly, it's the most disruptive. It's the augmentative layer. The augmentative layer? Yeah, this encompasses AI, advanced analytics, gamification engines, algorithmic management. And this layer is entirely different because it doesn't just, you know, sit there waiting for you to use it to do your work. It increasingly interprets the data and actually directs the work. Oh, wow. It tells you what to prioritize. So it's literally software actively managing your day. Exactly. And here is where we hit like the big aha moment. From the brief out of all these layers, across all these billions of dollars spent on enterprise technology, the core finding is that technology rarely motivates us directly, which I mean, is a very bitter pill for a lot of tech vendors to swallow. They really want to believe their shiny new dashboard is inherently inspiring. Right. It makes me think of an analogy. It's, it's like buying a state of the art six figure luxury stove for a master chef. Okay, I like this. Right. So the stove is beautiful, but it has this mandatory built in screen that tells the chef exact how much salt to use and it completely locks the oven door if it disagrees with the chef's recipe. Well, that sounds like a nightmare for a chef. Exactly. The stove works perfectly from a technical standpoint, but you've stripped the chef of their autonomy. So the tool itself is a marvel, but the environment it creates for the professional is just miserable. That captures the dynamic perfectly. The tool itself is neutral, really, but the restrictions it imposes are what kill the drive. Wait, let me, let me push back a little bit here. What about the sheer flexibility of remote work? Doesn't working from a smartphone or, you know, taking your laptop to your couch directly motivate people? Because the tech itself enables that lifestyle. What's fascinating here is the concept of mediators. The smartphone itself isn't the motivator. It's not? No. Think about it. The smartphone can just as easily be used by a micromanager to ping you at 11:00pm on a Saturday. Ugh. True. Which is highly demotivating. Right. What the technology actually does is reshape these underlying psychological mediators. Things like your sense of autonomy, the variety of skills you get to use in a day, and your perceived control over your workflow. The technology changes the mediator, and the mediator is what actually drives the motivation. Ah, okay, so it's a chain reaction. It's an indirect relationship. That's the mechanism. Yeah. For instance, the brief highlights this research by Knighton Westbrook on telecommuting. They found that ICT flexibility. So the ability to choose when and where to work using technology is a massive motivator because it fundamentally expands the worker's autonomy. Right. The tech is just the vehicle, the autonomy is the actual destination. Exactly. And this actually updates older organizational models that used to think of technology as just a hygiene factor. Meaning, like it was something that could only prevent dissatisfaction if it worked properly, but could never actually inspire you to work harder. Okay, so if technology operates by shifting our sense of autonomy and control, what happens when it shifts those things in the wrong direction? Because, I mean, we've all been in situations where a new tool makes us feel way less in control. Well, the human and organizational consequences of that downward shift are profound. This ties into something in organizational psychology called the job demands resources model. Wait, define that for me really quickly. What are the demands and what are the resources? In a normal office setting? Sure. Think of your job as a scale. On one side, you have your demands. So the deadlines, the complex tasks, the emotional labor of dealing with, you know, angry clients. On the other side, you have your resources. That's your skills, your supportive colleagues, and critically, your tools. The model shows that when you have adequate resources, you can handle high demands. But inadequate technological resources, like a glitchy platform or a really convoluted workflow, they act as a direct antecedent of psychological strain. The scale tips and you burn out. Oh, so the tool actually becomes an extra demand instead of a resource. Precisely. There is this fascinating study mentioned in the text by researchers Bala and Vekatesh. They used what's called a latent growth approach. Which means what exactly? All that really means is they didn't just take a single snapshot. They continuously tracked employees over time during a massive software rollout to see how their feelings evolved. Yeah. They tracked an erp, an Enterprise Resource Planning System implementation. And they showed that during the rollout, employees perceived job characteristics heavily fluctuated, literally day by day. Meaning they felt like the fundamental nature of their jobs kept changing underneath them, depending on how the software was behaving that day. Yes, and their sense of control completely tanked. That loss of control caused immediate, measurable spikes in psychological strain and negative attitudes toward the company. Wow. And the scariest part for leaders is that it doesn't even have to be a massive system overhaul to cause this. Other research in the brief shows that even modest, everyday hardware friction, like a frozen screen, a dropped video connection, a mouse that lags it accumulates over the course of a workday into a very real, measurable negative mood. It's death by a thousand buffering screens, basically. Exactly. And here's where it gets really interesting. It's not just the worker who suffers when the tech is bad. There is a massive ripple effect onto external stakeholders. If you are frustrated by your tools, the people you're trying to help are going to feel that frustration. The stakeholder impact is the hidden, often completely uncalculated cost of bad workplace technology. Yeah. The brief gives this incredible example from healthcare. It shows that motivated, adequately equipped clinical staff directly correlate with better patient experiences. Right. If a nurse is like standing at a bedside fighting with a tablet to input patient data because the dropdown menus don't make sense. They aren't looking the patient in the eye. They aren't picking up on those subtle visual cues about the patient's pain levels. The tech friction actively degrades the human care. We see the exact same pattern in public administration, too. Studies connect workplace attributes directly to citizen facing service quality. Yeah. If a public worker is battling some clunky legacy database, the citizen on the other side of the desk gets slower. Less empathetic service. The causal chain is remarkably clear. The technology shapes the mediators like autonomy and perceived control. Those mediators shape the employee's motivation, and then that motivation ultimately dictates the quality of the experience the stakeholder receives. Man, it's all connected. You can't Have a good customer experience without a good employee experience. And you just can't have that without good tools. Exactly. So having established how dangerous it is to get this wrong, let's talk about the solution. How do organizations actually get this right? The brief lays out a tactical playbook with five evidence based responses. The first concept is that you have to redesign jobs around the new technology, not just force the technology into the old org chart. And this is where so many companies fail. When you retrofit advanced new technology onto an unchanged role description, motivation almost always plummets. You have to actively map the five core job characteristics. Skill, variety, task identity, task significance, autonomy, and feedback before and after the tech rollout. Let's use that Siemens healthineers case study from the brief to illustrate this, because I thought it was great. So imagine a hospital gets a massive new medical imaging software system. This is a perfect example. Siemens realized that as their imaging workflows became more heavily mediated by advanced software, the technologists using the machines were in trouble because they used to do a lot more manually, right? Exactly. These were highly trained professionals who used to have a rich, varied job configuring the machines and managing the process. But with the new software automating so much of the technical work, they were at risk of becoming mere button pressers. Their task identity. So that feeling of completing a whole identifiable piece of work from start to finish, it was being completely compressed by the automation. It was eroding their professional identity. So instead of just letting them be bored button pressers, Siemens redesigned the job itself. They reframed the technologists roles to encompass the entire diagnostic pathway. Oh, that's smart. They gave them more responsibility in patient interaction, in protocol selection, and in collaborating directly with the radiologists. By expanding the human elements of the role around the new tech, they restored the meaning and significance of the work. Okay, so expanding the job description makes sense on a macro level. But what happens when that technologist, or really any employee, actually sits down at their comp meter for eight hours? Like how do you prevent the software itself from micromanaging them? That leads us to the second response. Implementing technology in ways that actively support autonomy and competence. This concept is deeply rooted in self determination theory, which essentially dictates that humans have fundamental psychological needs for autonomy, competence and relatedness. If a tool frustrates those basic needs, we will inevitably reject it. Practically speaking, this means organizations need to default to employee configurability whenever possible. Like letting people customize their own dashboards. Exactly. Let them control their notification settings so they aren't Constantly interrupted. And critically, you have to place hard boundaries on surveillance features because no one wants to feel like Big Brother is logging their keystrokes or, you know, tracking how long their mouse is idle. It destroys trust instantly. The absolute masterclass in doing this correctly comes from Bertzorg, the massive Dutch home nursing organization. They built a lightweight digital platform for scheduling, documentation, and peer learning. Okay, but the brilliant part is what the app doesn't do. It explicitly leaves all clinical and team based decisions up to the nurses themselves. The app handles the administrative logistics, but it never overrides their professional judgment. It is autonomy supporting, not autonomy replacing. It just clears the path so they can focus on nursing. I love that it actually treats them like adults. It does. And speaking of treating employees with respect, the third tactic is all about procedural justice and participation. This is the idea that you should actually let employees pick and configure their tools in the first place, because the simple act of participation satisfies that innate psychological need for competence we just talked about. Yeah, when you involve the end user from day one, not only do you end up with a tool that actually fits the workflow, because, let's face it, the frontline workers know things the software designers just don't. But you also convey deep respect for their expertise. Yeah, the city of Helsinki did this when they were modernizing their public service workplaces. They literally let the employees lead the configuration of their new coworking spaces. They didn't just, you know, pick out chair colors. They designed how the spaces would actually function. Yes, and what the research highlights here is fascinating. The actual function of the space obviously matters, but the symbolism of being asked for their opinion matters just as much. The procedural justice, the perceived fairness of the process itself, shifts their mindset from feeling controlled to feeling like an active participant. It validates that they are the experts of their own workflow. Now, the fourth response in the playbook focuses on building digital capability, but it highlights a specific concept that I just find deeply fascinating. Means efficacy. Wait, means efficacy. I've heard of self efficacy, like, you know, believing in my own skills and knowing I can do my job. But what on earth is means efficacy? I love this distinction. I could geek out about this all day. Please do. Okay, so self efficacy is believing in yourself. Means efficacy is believing that your tools actually work. Oh, wow. You can be the most confident, highly skilled worker in the world, but if you do not trust the machine you are operating, if you think the data is flawed or the software is going to crash and lose your work, your performance will drop. That Is so true. And when the demands of new technology outpace an employee's skill development, they experience massive cognitive dissonance. Instead of trying to learn the new tool, they revert to self protection. They hide, they complain, and they create elaborate manual workarounds just to avoid using the new system. So when a rollout fails, it's not necessarily a training issue. It's a trust issue. They don't believe the means are effective. That is the core issue. To combat this, several European manufacturing groups took a really innovative approach. They set up digital shop floor academies for their CNC operators. The workers running complex computer numeric controlled manufacturing equipment. Okay, they didn't just dump a bunch of generic e learning modules on them and walk away. They paired short cycle hands on training with peer mentoring. But more importantly, they installed visible reliability dashboards. They went out of their way to prove to the workers that the new advanced manufacturing technology was reliable and safe. They systematically built. That means efficacy alongside the worker's self efficacy. That makes so much sense. You actually have to prove the tool is worthy of their trust. Precisely. Now this brings us to the fifth tactical response, and it's one that usually gets a lot of high rolls. I think gamification, and I have to push back a little here. Isn't gamification usually just corporate bribery? Like when my HR software gives me digital confetti for updating my password? It's the worst, right? It doesn't make me feel fulfilled. It makes me feel like I'm being treated like a toddler. Slapping digital badges on boring work just feels like a trick. You are absolutely right to be skeptical. And the research completely validates that skepticism. Gamification fails spectacularly when you try to graft extrinsic rewards like points or meaningless badges onto tasks that are already intrinsically interesting. Or when you use it purely to force routine compliance, it just breeds cynicism and and makes adults feel patronized. Congratulations. You filled out your expense report on time. Here's a virtual bronze shield. Exactly. It's insulting. Where gamification actually works is when it is designed around flow theory. And what does flow state actually look like in an office context? Flow is that state of deep, effortless concentration where you lose track of time because the challenge of the task perfectly matches your skill level. Good gamification strengthens the feedback loop so you know exactly how you're doing. And it constantly calibrates the challenge to match your growing skill. Okay, so it should help you track your own mastery, not bribe you. Right. And the literature offers a massive warning Here. Organizations must avoid using leaderboards in interdependent work. Because if my success depends on collaborating with you, a leaderboard just pits us against each other. It creates toxic competition and destroys teamwork. Yes, it erodes the psychological need for relatedness. The brief points to Deloitte's Leadership Academy as a prime example of doing this right. They didn't just hand out prizes for logging into a portal. They anchored their gamification in genuine learning challenges. So the game elements were tied to actual professional mastery and problem solving, not just, you know, checking boxes for compliance. Which brings us to the horizon, really. Fixing today's software rollouts is necessary, but as we know, technology cycles are moving incredibly fast. We aren't just talking about a new email client anymore. We're Talking about Industry 4.0, Generative AI, Advanced Robotics. Any specific design choice we make today will probably be obsolete in a few years. The ground is shifting constantly. So what does this all mean for the big picture? Like how do organizations actually build long term resilience so they aren't just constantly playing whack a mole with employee morale every time there's a tech update? Well, the brief outlines three forward looking pillars to secure that long term capability. Pillar one is to recalibrate the psychological contract between the employer and the employee. Trust is the new load bearing element in the workplace. Because the tech is getting so intimate. It's reading our emails, it's summarizing our meetings, it knows everything about how we work. Organizations have to be radically transparent about data use. They need to make visible, binding commitments that they're using AI to augment human workers, not displace them. Because if you introduce an AI assistant and people think it's ultimately there to study their workflow and steal their dogs, they'll sabotage it. Of course they will. They will feed it bad data. Yeah, the tool triggers a primal defensive response unless the that psychological contract is explicitly renegotiated and secured. Which leads right into pillar 2. Continuous learning as infrastructure. Right. If we connect this to the bigger picture, if technology is changing this fast, learning can no longer be an episodic HR program. It can't be a mandatory seminar you attend once a year in a fluorescent lit conference room. Right. It has to be built directly into the operating model of the business. Organizations need to create actual time budgets that protect learning hours from daily operational pressures. And they need career architectures that actively reward adaptability rather than just rewarding tenure or raw output. Learning has to be treated as part of the actual job, not a hobby. You are expected to do on your lunch break. Exactly. And finally, pillar three Steward Data and Algorithms this addresses the newest, most complex layer of workplace tech. Algorithms are now doing the sequencing of work. They are directing employee attention, and in many cases they are evaluating performance. Which is wild to think about. It is these algorithmic managers have to be governed transparently. There needs to be real employee voice in how these algorithms are designed and trained, and there must be clear human escalation paths for when they inevitably produce an unjust or nonsensical outcome. They have to be treated as supportive infrastructure, not as opaque, unquestionable overseers. And that really summarizes the ultimate lesson here for you, the listener. Workplace technology is no longer just background music playing while you do your job. It is the environment itself. The next time a new tool is introduced at your job, or the next time you are the one deciding to introduce a new platform to your team, the question to ask isn't simply will this shiny new thing motivate people? The real question is, how does this reshape my autonomy, the quality of my feedback and my perspective received control over my own work? This raises an important question, though, something that builds on everything we've discussed today. We talk about how crucial it is to believe your tools work, that concept of means efficacy. But as AI and algorithmic managers become a larger, more dominant part of that augmentative layer evaluating our performance and assigning our tasks in real time, what happens to our motivation when we can no longer see how the tool is making its decisions? When the boss dictating your daily workflow is literally a black box of code? Who do you complain to? And how do you maintain trust in a system that you, and maybe even your company's IT department can't even fully comprehend? That is a chilling thought, and one that every leader rolling out a new intelligence system needs to wrestle with before their best people walk out the door? We'll leave you to ponder that scenario. Thanks for joining us for this Dem Divine.