How to Identify Workflow Friction in Teams

𝗠𝗮𝗽 𝗧𝗼𝗱𝗮𝘆’𝘀 𝗥𝗲𝗮𝗹𝗶𝘁𝘆 𝗮𝗻𝗱 𝗗𝗶𝗮𝗴𝗻𝗼𝘀𝗲 𝘁𝗵𝗲 𝗣𝗮𝗶𝗻 𝗣𝗼𝗶𝗻𝘁𝘀: 𝗨𝗻𝗰𝗼𝘃𝗲𝗿 𝗛𝗶𝗱𝗱𝗲𝗻 𝗙𝗿𝗶𝗰𝘁𝗶𝗼𝗻 𝗕𝗲𝗳𝗼𝗿𝗲 𝗔𝗱𝗱𝗶𝗻𝗴 𝗧𝗲𝗰𝗵 Every successful transformation starts by seeing your current state with crystal clarity. Too often, we rush to evaluate software features before understanding how work really flows and where it grinds to a halt. Imagine treating your processes like a road trip: you wouldn’t choose a new vehicle until you know which roads are blocked. The same goes for systems. A mid‑market manufacturer struggled with late shipments. Leadership blamed their ERP’s lack of functionality, but frontline teams knew the truth: manual handoffs and conflicting spreadsheets created bottlenecks. In addition, 40% of delays stemmed from manual cross‑checks between dispatch and finance, a step invisible on org charts but glaring on the shop floor. By facilitating honest, workshop‑style mapping sessions (complete with sticky notes and whiteboards), they uncovered redundant approvals and invisible handoffs that no feature list could solve. Involving the people who do the work isn’t optional; it’s essential. Their day‑to‑day insights highlight subtle delays, workarounds, and “exceptions” that hide in plain sight. An unbiased facilitator ensures every voice is heard and prevents solutions from being biased by existing hierarchies. The result? A process map that reveals root causes, not just symptoms, and creates a shared baseline for improvement. By critically analyzing your current state, you build a precision roadmap: automate the highest‑impact tasks, redesign workflows to remove dead ends, and close compliance gaps before they escalate. This targeted, human‑centric approach avoids wasted investment, earns frontline trust, and lays the groundwork for sustainable process improvement.    Once you’ve charted reality, you can make targeted changes, whether that’s simplifying an approval step, automating a data transfer, or selecting a tool that fits the way your teams operate. This honest approach prevents costly rework and builds trust across the organization. Ready to uncover hidden friction and chart a focused transformation path? With Digital Transformation Strategist, let’s discuss how a structured pain‑point diagnosis can drive your next wave of operational excellence. #digitaltransformation #operationalexcellence #processimprovement #processmapping #changemanagement

Nobody talks about friction logs. But they'll change how you manage projects. Want to know how it works? Write down every time something feels harder than it should be. Common friction points I see: • Team members can't find the latest project files • Getting approvals takes forever • Status updates require chasing 5 different people • Meetings that accomplish nothing Most project managers just deal with friction in the same 'ol ways. "That's just how things work here." "It's always been complicated." "Everyone deals with this stuff." Smart PMs fix friction. After tracking friction for 2 weeks, you'll see the patterns. The bottlenecks. The time wasters. Then you can fix them: • Centralize file storage • Streamline approval workflows • Automate status reporting • Kill pointless meetings The results compound. Projects move faster. Teams stop complaining. You look like a genius. Friction isn't just annoying. It's expensive. Start logging it. Start fixing it. And watch your projects accelerate.

80% of workflow bottlenecks are hiding in plain sight. But most teams don’t look closely enough to see them. When I design workflows, I don’t add new tools right away or build complex systems. I start by mapping the current process. Without knowing every step, we’re just guessing at what’s slowing us down. Here’s my go-to checklist for spotting the hidden issues: 1 - Map every step Document each click, handoff, and decision. Most teams skip this, but it’s where the real insights are. 2 - Spot repetitive tasks Repeated steps often go unnoticed. They feel like “just part of the job” but usually add no real value. 3 - Measure task times Check how long each step actually takes. When times drag, it’s a sign of inefficiency that needs fixing. 4 - Look for approval delays Every extra approval is a potential bottleneck. Too many checks can slow things down more than they help. 5 - Align skills with tasks Ensure tasks fit the person’s skill level. If experts are doing routine work, it’s time to rethink the setup. 6 - Automate simple tasks Automation isn’t about flashy tools. It’s about freeing up your team’s time for critical work, not admin tasks. It’s surprising how often these basics are ignored. Do this if you want to do more with less. Or skip it if you’re okay with unnecessary delays and wasted resources.

𝗜𝘀 𝗬𝗼𝘂𝗿 𝗧𝗲𝗮𝗺 𝗟𝗼𝗴𝗴𝗲𝗱 𝗜𝗻, 𝗕𝘂𝘁 𝗖𝗵𝗲𝗰𝗸𝗲𝗱 𝗢𝘂𝘁? As part of the key leadership team, you see it, don't you? Everyone's online. Calendars packed. Activity dashboards humming. But... something's off. Innovation feels flat. Proactive ideas are scarce. It feels like people are just... treading water. This isn't laziness. It's often presenteeism – the state of being present but not truly engaged or productive. Why? Some reasons: ➡️unseen family issues ➡️unintended company culture ➡️global uncertainties ➡️organizational instability (yes, including poor leadership) ➡️ineffective wellbeing And what do we typically do? Monitor more closely? (Hello, micromanagement & distrust 👋) Launch another 'engagement' survey? (While being distant and impersonal of course?) Just push harder on targets? (And watch burnout climb?) Honestly? These tactics usually backfire, especially when there's no intentionally devised leadership culture. They treat the symptoms, not the disease. Here’s the brutal truth from having trained over a hundred organizations in the last 31 years: ➡️Focusing only on activity without purpose kills autonomy. ➡️Generic engagement efforts breed cynicism if core issues aren't fixed. ➡️Pushing harder without removing roadblocks through effective processes burns out your best people first. You end up with compliance, not commitment. Busyness, not breakthroughs. So, what's the real fix? Stop trying to squeeze more out of a system clogged with friction. Start removing the friction itself. ✅Find out what wastes your team's time and energy daily. (Hint: if you haven't asked this before, brace yourself - it might actually be their very leaders). ✅Empower them to fix those annoying, energy-draining processes. ✅Reconnect their work to a clear sense of purpose and impact. When you shift from managing activity to enabling impact: 📈You unlock intrinsic motivation. 💖You build trust and psychological safety. ✨You free up mental energy for the work that really matters. Imagine: 🎉Teams proactively solving problems because they can. 🙏Genuine engagement and wellbeing, not just survey scores. 💡Innovation sparking because people aren't bogged down by pointless hurdles. Stop demanding "more" from your people. Start removing what's in their way. This is even more important with impending rising costs of operating in Singapore - and move from just 'logged in' to 'locked in' on results. --- Follow me Stuart Tan MSc., MBA for more tips on Organizational Leadership and Personal Mastery.

I was having team with my neighbors who is Director at a reputed consulting firm. He has seen me facilitate teams for bring clarity through Sketchnotes 📝 He promptly asked me to suggest some way to resolve conflicts in his team. He said “they are always on fire, waiting to put each other down”. My eyes lit up and rolled up 🧠remembering what I did in my team few years ago. In high-performing teams, conflict is inevitable. When collaboration 👥is frequent and stakes are high, differing working styles, communication gaps, and behavioural patterns can often spark friction. But rather than letting these conflicts fester, what if we turned them into opportunities for clarity and growth? One powerful ritual I’ve found useful is something called a Behavioural Retrospective 🙌— a structured conversation that helps teams reflect on behaviours causing friction and co-create better ways of working together. Let’s break it down 🧩 What is a Behavioural Retrospective? Unlike project retrospectives that focus on processes and outcomes, a Behavioural Retrospective dives into the interpersonal actions and behaviours that impact team dynamics. It guides teams to safely surface frustrations, understand the root causes, and collectively agree on more constructive behaviours. Here’s a simple four-step framework to run one: ⸻ 1. Get Frustrations on Paper Start by asking team members to quietly write down actions or behaviours of peers that are frustrating them. Encourage specificity — focusing on actions, not people. ⸻ 2. Take Turns Sharing Create a safe, non-defensive space where team members can take turns sharing what they’ve written. A crucial mindset here: listen to understand, not to defend. Everyone deserves to be heard. ⸻ 3. Ask Revealing Questions Encourage the team to ask revealing, open-ended questions to uncover what’s beneath the surface. This helps build empathy, as people often act from unseen pressures or intentions. ⸻ 4. Make Suggestions for Alternate Behaviours End the session by inviting the team to suggest constructive, alternative behaviours. Focus on actions that can replace the problematic behaviours moving forward. Capture these as actionable, specific agreements. ⸻ Why This Works Behavioural Retrospectives promote empathy, mutual respect, and a culture of continuous improvement within the team. ⸻ If your team has been experiencing behavioural conflicts, this might be a good ritual to introduce in your next cycle. It’s a simple but transformative way to realign as a team — not just on what you build, but how you work together. Have you tried something similar? Would love to hear how you handle behavioural conflicts in your team. #TeamCulture #Leadership #Retrospective #ConflictResolution

Applying Cummings & Worley Group Diagnostic Model #OrganizationalDevelopment #TeamDynamics #PharmaIndustry #Leadership #ChangeManagement Scenario Background: A mid-sized pharmaceutical company has been experiencing declining productivity and increasing conflict within its research and development (R&D) teams. The leadership suspects that ineffective team dynamics and poor alignment of goals might be contributing factors. To address these issues, How L & D professional can utilize the Group Level Diagnostic Model, which focuses on diagnosing and improving group effectiveness within an organization. Step 1: Entry and Contracting: Objective: Establish a clear understanding of the project scope, objectives, and mutual expectations with the R&D teams. Actions: Conduct initial meetings with team leaders to discuss the perceived issues and desired outcomes. Step 2: Data Collection Objective: Gather information to understand current team dynamics, processes, and challenges. Actions: Distribute surveys and conduct interviews to collect data on team communication, collaboration, role clarity, and decision-making processes. Observe team meetings and workflows to identify misalignments and potential areas of conflict. Use assessment tools to measure team cohesion, trust levels, and satisfaction among team members. Step 3: Data Analysis Objective: Analyze the collected data to identify patterns, root causes of dysfunction, and areas for intervention. Actions: Compile and analyze survey results and interview transcripts to identify common themes and discrepancies. Map out communication flows and decision-making processes that highlight bottlenecks or conflict points. Assess the alignment between team goals and organizational objectives. Step 4: Feedback and Planning Objective: Share findings with the teams and plan interventions to address the identified issues. Actions: Conduct feedback sessions with each team to discuss the findings and implications. Facilitate workshops where teams can engage in problem-solving and planning to improve their processes and interactions. Develop action plans that include specific, measurable, achievable, relevant, and time-bound (SMART) objectives to enhance team performance. Step 5: Intervention Objective: Implement interventions aimed at improving team dynamics and effectiveness. Actions: Initiate team-building activities that focus on trust-building and role clarification. Provide training sessions on conflict resolution, effective communication, and collaborative problem-solving. Realign team goals with organizational objectives through strategic planning sessions. Step 6: Evaluation and Sustaining Change Objective: Assess the effectiveness of interventions and ensure sustainable improvements. Actions:Conduct follow-up assessments to measure changes in team performance and dynamics. Hold regular meetings to discuss progress and any ongoing issues. Adjust interventions as necessary based on feedback and new data.

What Hidden System Friction Is Blocking Your Strategy? I've been revisiting the Book Rethinking Users, which challenges how we view roles in complex systems. (I like using books like these to help me see things differently) The insight? Organizations many times stall due to conflicting roles, misaligned incentives, and cultural fractures, not just individual resistance. Here's how I'm adapting their framework to map system friction: -Dependent Functions: Roles needing approval to act. In a financial merger for example dual sign-offs could create delays and risk aversion and cost an organization missed opportunities as competitors move faster. -Complementary Functions: Teams with conflicting incentives. You could have Sales pushing customization while Operations wants to standardize, which can cause a clash between customer-centric and cost-driven approaches. -Generative Functions: Teams adapting processes locally. Think of a manufacturing org that has seven plants with seven "optimized" workflows, creating a 'every plant for itself' environment. Standardization fails not from resistance, but fragmentation. -Parallel Functions: Interdependent teams without alignment. Imagine a tech rollout, Product and Customer Service define "on-time delivery" differently. Result? Weeks of delays and frustrated customers - from conflicting definitions of success. -Direct Functions: The obvious focus but least informative. Most transformation targets direct functions, missing the system dynamics that kill execution. The takeaway? What may look like resistance is usually system friction in disguise. If your strategy is stalling, don't look at motivation first (because it takes more experience and nuance than you have been told). Look at your systems. I map these friction points with clients to visualize where execution stalls and how it's costing them delays and lost opportunities. What friction points are you seeing, and which of these resonates most with your experience?

Your team isn't unmotivated. They're looking for permission you never knew you had to give. The more you push for ownership, the slower things move. You've seen it in Vietnam: A team member spots a process inefficiency. They see it. They know how to fix it. They pause. They check. They wait one more meeting. “𝘛𝘩𝘪𝘴 𝘴𝘩𝘰𝘶𝘭𝘥 𝘩𝘢𝘷𝘦 𝘣𝘦𝘦𝘯 𝘥𝘰𝘯𝘦 𝘢𝘭𝘳𝘦𝘢𝘥𝘺.” And now you’re chasing something that shouldn’t need chasing. They don't move. Not because they don't care. Because no one explicitly said they could. So they hold. You think: "𝘵𝘩𝘦𝘺'𝘳𝘦 𝘯𝘰𝘵 𝘮𝘰𝘵𝘪𝘷𝘢𝘵𝘦𝘥 𝘦𝘯𝘰𝘶𝘨𝘩." They're protecting themselves. ↳ Not passive ↳ Not disengaged making sure it’s safe before acting Look at the map👇 Motivation doesn’t work the same way everywhere. In Vietnam, motivation doesn't come from ownership. It comes from: • Clear approval • Shared expectations • Safety to act without friction Until those are met, • people don’t move • decisions don’t land • execution stalls It is a motivation problem, just not the one you think. You're pushing for ownership in a system that runs on safety and shared alignment. That's the mismatch. If your team isn't moving, check: → Was approval explicit, or just assumed? → Are expectations shared, or still interpreted differently? → Would it feel safe to act without checking again? If not, that’s your bottleneck. Motivation isn’t a trait your team brings to work. It's built, or blocked, by how you structure permission. If you want people to act, don't just push ownership: Not "𝘧𝘦𝘦𝘭 𝘧𝘳𝘦𝘦 𝘵𝘰 𝘪𝘮𝘱𝘳𝘰𝘷𝘦 𝘵𝘩𝘪𝘯𝘨𝘴," But "𝘺𝘰𝘶 𝘩𝘢𝘷𝘦 𝘮𝘺 𝘨𝘳𝘦𝘦𝘯 𝘭𝘪𝘨𝘩𝘵 𝘵𝘰 𝘳𝘦𝘥𝘦𝘴𝘪𝘨𝘯 𝘵𝘩𝘪𝘴 𝘸𝘰𝘳𝘬𝘧𝘭𝘰𝘸 𝘸𝘪𝘵𝘩𝘰𝘶𝘵 𝘤𝘩𝘦𝘤𝘬𝘪𝘯𝘨 𝘸𝘪𝘵𝘩 𝘮𝘦 𝘧𝘪𝘳𝘴𝘵." Not "𝘸𝘦 𝘸𝘢𝘯𝘵 𝘧𝘢𝘴𝘵𝘦𝘳 𝘥𝘦𝘤𝘪𝘴𝘪𝘰𝘯𝘴," But "𝘥𝘦𝘤𝘪𝘴𝘪𝘰𝘯𝘴 𝘶𝘯𝘥𝘦𝘳 𝘟 𝘢𝘳𝘦 𝘺𝘰𝘶𝘳𝘴 𝘵𝘰 𝘮𝘢𝘬𝘦 𝘢𝘭𝘰𝘯𝘦." Not "𝘐'𝘮 𝘰𝘱𝘦𝘯 𝘵𝘰 𝘪𝘥𝘦𝘢𝘴," But "𝘪𝘧 𝘵𝘩𝘪𝘴 𝘦𝘹𝘱𝘦𝘳𝘪𝘮𝘦𝘯𝘵 𝘧𝘢𝘪𝘭𝘴, 𝘵𝘩𝘢𝘵'𝘴 𝘰𝘯 𝘮𝘦." 𝗪𝗵𝗮𝘁’𝘀 𝗺𝗶𝘀𝘀𝗶𝗻𝗴 𝗿𝗶𝗴𝗵𝘁 𝗻𝗼𝘄 𝗳𝗼𝗿 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺 𝘁𝗼 𝗳𝗲𝗲𝗹 𝗺𝗼𝘁𝗶𝘃𝗮𝘁𝗲𝗱 𝘁𝗼 𝗮𝗰𝘁?

Teams don’t struggle because they lack skill. They struggle when the same words mean different things. It’s subtle. Everything looks like it’s moving. Updates are shared. Work is happening. Plans exist. But direction isn’t fully aligned. Because language isn’t. “Scope is clear.” ↳ One assumes fixed ↳ One keeps adjusting “High priority.” ↳ One treats it as urgent ↳ One sees it as important but flexible “Next sprint.” ↳ One hears commitment ↳ One hears possibility “Done.” ↳ One means shipped ↳ One means ready for review Same terms. Different interpretations. That’s where friction starts. What usually follows: • Decisions get revisited • Timelines shift quietly • Ownership becomes unclear • Progress feels slower than expected Not because people aren’t capable. Because meaning isn’t shared. What changes things: • Defining terms early • Making expectations explicit • Aligning on what “good” looks like • Removing room for assumption Term aligned → action aligned Term assumed → effort scattered Strong teams don’t just communicate. They operate on shared definitions. That’s what makes execution feel smooth. ➛ Fewer corrections ➛ Cleaner handoffs ➛ Faster decisions Same work. Different outcome. It comes down to clarity. P.S. What’s one term your team uses that could mean different things to different people?

One of the best ways to align teams, stakeholders, and strategy is to make the invisible visible. That’s why I’m such a fan of mapping techniques. They help you zoom out, focus in, and uncover the things that are often hiding in plain sight. Whether it’s unclear goals, conflicting priorities, or pain points users are quietly putting up with. Here are 7 mapping techniques I keep coming back to and how I use them in delivery: 🗺️ User Story Mapping Helps me turn flat backlogs into something visually dynamic, tangible, and user-focused. I use this to map out a user's journey step by step, then slice features based on what really matters to them. It’s a brilliant way to align teams around MVPs and delivery releases. 🗺️ Impact Mapping Just like Simon Sinek this one starts with why. It links business goals to user behaviors and potential features, helping teams focus on outcomes over outputs. I’ve used it to reframe entire product roadmaps around expected impact instead of a list of things to build. 🗺️ Wardley Mapping This is more strategic and it's great for mapping components of a system by how visible they are to users and how mature they are. It’s helped me spot where we should innovate, where we can standardise, and where buying makes more sense than building. 🗺️ Dysfunction Mapping I use this when things feel off, but the problem or solution isn’t immediately obvious. It’s a structured way to identify root causes of delivery friction whether it’s misaligned priorities, unclear ownership, or recurring blockers. Great for retros and recovery plans. 🗺️ Stakeholder Mapping Simple but powerful. I use this to understand who’s influencing the project, who needs to be kept in the loop, and who we might be unintentionally leaving out. It’s especially useful when stepping into a new team or navigating complex stakeholder landscapes. 🗺️ Experience Mapping This is about stepping into the user’s shoes and walking through their journey. Not just where the product touches them, but where the experience begins and ends. I’ve used this to uncover gaps, friction points, and opportunities we hadn’t considered. 🗺️ Empathy Mapping When we’re trying to build something truly user-centric, empathy mapping helps us understand what users think, feel, say, do, and hear. It goes deeper than roles or personas and helps teams emotionally hook in with the people we’re building for. If you’re in delivery, product, UX, or transformation work there’s probably a mapping method in here that can help you in your day to day role. Let me know if I've missed any effective mapping techniques and if a deep dive into any of these would be useful!