What Every Agile Organization Needs

This elearning, titled "Outcome, Goals, and Rules," explores the interplay between these three elements within an organization and how they can both facilitate and hinder progress, particularly in an Agile environment.

The video begins by introducing the Outcome, Goals, and Rules triangle. It explains how, when goals are unclear or perceived as unattainable, individuals and organizations often resort to "pre-damage control." This involves redefining outcomes and creating new, often unnecessary, rules to protect themselves from blame. These rules become a "security blanket" that deflects the fear of failure, but also stifles innovation and autonomy.

The video then contrasts this defensive approach with the core principles of Agile: Autonomy and Mastery. In an Agile organization, individuals have the freedom to choose how they contribute and are encouraged to learn and improve. The video emphasizes that a culture of fear and rigid rule-making is a major impediment to implementing Agile.

To optimize an organization's potential, the video suggests a shift in focus from what is "practical" (the safest, most individualistic option) to what is "possible" and "feasible." This requires a culture of trust and innovation where risks are encouraged, and a shared "definition of done" is established.

Reflective Exercises

As you engage with the concepts presented in the video, take some time to reflect on your own experiences and observations within your organization. Use the following exercises to deepen your understanding and identify potential areas for growth:

Exercise 1: Identifying "Security Blankets"

Think about a recent project or task where you or your team felt a sense of uncertainty or fear of failure.

1. What were the stated goals and outcomes? Were they clear and achievable?

2. What "rules" (formal or informal) were in place or created during this time? Did these rules genuinely help achieve the outcome, or did they serve more as a "security blanket" to protect individuals or the team from blame?

3. How did these rules impact autonomy and innovation? Did they limit the freedom to explore new approaches or take calculated risks?

Exercise 2: Assessing Autonomy and Mastery

Consider your current role and your team's work environment.

1. To what extent do you feel you have the autonomy to choose how you contribute to your team's goals? What factors enable or hinder this autonomy?

2. How is mastery encouraged and supported in your organization? Are there opportunities for learning and continuous improvement?

3. What role does feedback play in your team? Is it used for learning and growth, or is it more often associated with blame?

Exercise 3: Shifting from Practical to Possible

Think about a challenge or opportunity your team is currently facing.

1. What is the "practical" solution? This is often the safest, most familiar approach that requires the least collaboration or risk.

2. What is "possible"? If you weren't limited by existing rules or the fear of failure, what innovative solutions could you explore?

3. What is "feasible" under current constraints? This represents a balance between what is possible and what can realistically be achieved within a given timeframe.

4. What steps can you take to move your team's focus from the "practical" toward the "possible" and "feasible"? How can you foster a culture of trust and shared responsibility?

Exercise 4: The Role of Leadership

Reflect on the leadership in your organization.

1. Do leaders in your organization demonstrate a willingness to change the culture and embrace Agile principles? How so?

2. How do leaders respond to failure? Is it seen as a learning opportunity or something to be avoided and blamed?

3. What can you do, regardless of your role, to influence a shift toward a more trusting and innovative culture?

By reflecting on these questions, you can gain valuable insights into the dynamics of your organization and identify opportunities to foster a more Agile, autonomous, and innovative work environment.

We often assume that once a team is formed, everyone automatically feels empowered to speak their minds. But as a leader, you might leave a meeting with a "warm fuzzy feeling" while your team remains silent about critical flaws. In this session, we explore Psychological Safety—a condition where every team member feels genuinely empowered to voice uncomfortable truths, regardless of their role. I’ll share a pivotal moment from my own career at a corporate conference, where my decision to ask a difficult question in front of 250 people highlighted the vast gap between feeling empowered and having the safety to vocalize it. We will discuss why it is a leader’s responsibility to create an atmosphere where feedback can be delivered in various ways—whether in person, offsite, or in writing—to ensure that the "Emperor's new clothes" are called out before it's too late.

Reflection: Cultivating a Safe Haven

True autonomy for a team requires the safety to fail and the freedom to challenge the status quo:

• The Nod of Approval: Think of your last team meeting. Did everyone truly agree with the direction, or were they just nodding to avoid conflict? How can you tell the difference?

• Identifying the "Uncomfortable": What is one project flaw you are currently aware of but haven't voiced? What would you need to feel safe enough to bring it up to your manager?

• Flexible Feedback: Some employees thrive in face-to-face debates, while others prefer the precision of a frank email. How can you adapt your communication style to ensure every member of your team has a channel where they feel comfortable sharing their true thoughts?

• The Risk-Taker Mindset: Reflect on my "career-changing" question. Was it an act of defiance, or an act of commitment to the project's success? How can you frame your own "uncomfortable" questions as a way to protect the group's collective goals?

"Psychological safety means you are able to allow team members to show their empowerment in their own way. Empowerment means you care enough about the success of the project to make the effort to ensure that safety is extended to everyone".

Have you ever found yourself saying, "I can't do that," or "I don't know how to do that"? If so, you may be experiencing learned helplessness—a state of mental paralysis caused by conditioning. In this session, we explore the concept defined by Martin Seligman, which illustrates how a perceived lack of control over negative outcomes can lead individuals to stop trying, even when success is easily within reach. I use the analogy of a powerful horse tied to a tiny chair; the horse isn't physically bound, but it remains stationary because it believes it has no options. We’ll discuss how societal stigmas and personal experiences can "condition" us to ignore our own agency and the critical importance of learning to relish in small successes to break these cycles.

Reflection: Cutting the Cord of Conditioning

To reclaim your autonomy, you must recognize where you are being held back by belief rather than reality:

• The "Invisible Chair" Audit: Identify one professional task you've avoided because you "just can't". Is there a genuine physical or logical barrier, or are you the horse believing you're tied to the chair?

• Recognizing the Buzz: How much of your perceived helplessness comes from external "fake news" or societal stigmas? For example, consider the fallacy that "girls are poor at math". What similar false narratives have you internalized about your own capabilities?

• Relishing in Success: When was the last time you allowed yourself to truly feel proud of a professional win? How could celebrating these small victories help you "unlearn" helplessness and build the confidence to tackle larger challenges?

• Group Dynamics: Do you see patterns of learned helplessness in your current team or organization? How can you, as a leader or peer, create an environment that encourages testing the strength of those "invisible cords"?

"Physical constraints are often easy to see, but the mental ones are far more dangerous. Unless you allow yourself to relish in your success, you will never overcome the conditioning that tells you that you can't".

In this session, we address the debilitating "fear of failure" culture that often leads us to hide behind corporate buzzwords when we don't know the answer. We'll explore why admitting "I don't know" is often seen as a sign of weakness in the workplace, yet is actually the first step toward genuine progress and redemption. I’ll introduce a systematic approach to break down large, difficult tasks into smaller, "doable" pieces, helping you move past the "simplistic complexity" of trying to find immediate solutions to complicated problems.

Reflection: Systematizing Success

• Beyond the Buzzwords: Take an honest look at your current projects. Are you using corporate jargon to "fudge" a path forward because you're afraid to admit you don't know the next step?

• The Know/Don't Know Audit: Select your highest priority task. Create two lists: one for what is currently known and one for the unknowns. How much more "knowable" does the project feel once the gaps are identified?

• Breaking Down the 'Difficult': Look at the items on your "difficult to do" list. Are they stagnant because they are too large? How can you break these into smaller pieces—perhaps three-minute segments—to move them into your "doable" column?

"Admission is the first step toward redemption, but a systematic approach is what provides the clarity to actually get things done. We can achieve much more than we think we can".

Live stream held on July 25th, 2020

Have you ever felt like you’re constantly putting out the same fires at work, only for them to flare up again a week later? It’s frustrating, right? Usually, that happens because we’re fixing the symptoms we see on the surface, rather than the root cause hiding underneath.

In this module, I’m going to walk you through one of my favorite tools: The Five Whys.

Don’t let the simplicity fool you. Originally developed by Toyota and famously used by leaders like Jeff Bezos, this technique is a game-changer. We’re going to move past the "technical jargon" and get straight to the heart of how you can use this to communicate better with your team, understand your customers' real needs, and—most importantly—fix problems so they stay fixed.

By the end of this session, you’ll be able to:

• Peel back the layers of a problem like an onion.

• Lead a team "interrogation" that feels like a friendly chat, not a police lineup.

• Use the "Human Factor" to understand why people do what they do.

Reflective Exercises

I’ve designed these activities to help you bridge the gap between "knowing" the technique and "doing" it in your daily life.

Exercise 1: The "Recent Frustration" Audit

Think back to a problem you dealt with in the last week—maybe a missed deadline, a broken process, or a misunderstanding with a colleague.

• The Surface: What was the first thing you complained about?

• The Deep Dive: Now, try to ask "Why?" just three times regarding that event. Does the third answer look different from the first?

• Reflection: Did your initial "fix" actually address that third answer, or just the surface?

Exercise 2: The "Tone Check" Challenge

The Five Whys can feel aggressive if we aren't careful.

• Scenario: Imagine a team member forgot to send an important email.

• Drafting: Write down three different ways to ask "Why didn't that email go out?" without using the word "Why." (Hint: Try "What led to..." or "Walk me through the steps...").

• Reflection: How does changing the phrasing change the "vibe" of the conversation?

Exercise 3: Building Consensus

Consider a problem in your department that everyone seems to have a different opinion on.

• The Exercise: If you sat five of those people in a room and performed the Five Whys, where do you think they would finally agree?

• Reflection: Why is a "group consensus" on a root cause more powerful than just one person’s expert opinion?

The Kano Model: Unlocking Customer Delighters

The Kano Model, named after its creator, Noriaki Kano, provides a framework for categorizing customer requirements into three distinct types:

1. Standard Elements (Basics): These are the baseline features that customers expect and take for granted. Their absence leads to significant dissatisfaction, while their presence doesn't necessarily increase satisfaction. Think of a mobile phone's battery life – it needs to last more than a few hours for the phone to be useful.

2. Performance Elements: These are features that linearly impact satisfaction – more is generally better. Think of things like faster processing speeds or more storage capacity. This is often where companies compete most fiercely.

3. Delighters (Surprises): These are unexpected features that go beyond customer expectations and create a sense of "wow." They can be powerful differentiators, but they often become standard requirements over time as competitors catch up. Think of a unique and convenient packaging design or an "all-you-can-eat" pricing model.

Reflective Exercises

Exercise 1: Identifying the "Basics"

• Think about a product or service you use regularly. What are its "standard elements" – the features you take for granted and would be incredibly frustrated if they were missing?

• Now, think about your own work. What are the "standard elements" of the service you provide to your customers or colleagues? Are you consistently meeting these baseline expectations?

Exercise 2: Finding the "Performance" Drivers

• What are the key performance metrics for the product or service you're analyzing? How can you improve these metrics to increase customer satisfaction?

• Are you currently competing with others on these performance elements? If so, what can you do to differentiate yourself?

Exercise 3: Discovering "Delighters"

• What are some "latent requirements" – needs that your customers may not even realize they have? How could you address these needs to create a "wow" experience?

• Can you think of any "delighters" that have become standard requirements over time? What does this tell you about the need for continuous innovation?

By understanding the Kano Model and reflecting on these exercises, you can gain valuable insights into what truly matters to your customers and develop strategies for creating products and services that truly delight them.

In this session, I explore the psychology behind customer satisfaction and why organizations often struggle to differentiate between basic performance and genuine delight. I introduce the concept of Routine as a double-edged sword: while it's essential for efficiency, it can also lead to stagnation and "Creatures of Habit."

To break this cycle, I challenge you to experiment with your existing processes. By adding, substituting, or removing "actors" (steps or people) within a routine, you can uncover creative solutions and new business rules. These modifications allow for a more tailored experience that can ultimately serve as a powerful delighter for your customers.

Reflective Exercises

As you work through this material, I’d like you to take a moment and reflect on your current workflows:

1. Identify your "Must-Haves": List three routines in your daily work that you consider "standard." How would the customer experience change if one of these was absent?

2. The "Actor" Experiment: Choose one of those routines and imagine adding a new step or person into the mix. Does it make the process more complex, or does it open a door for a creative improvement you hadn't seen before?

3. The Substitution Challenge: If you had to remove one "actor" or step from your most frequent process, how would you maintain the same level of quality? Could this reduction actually lead to a faster, more "delightful" result for the end user?

4. Redefining Success: Look at your revised process from exercise #3. Does this new way of working require different "Business Rules"? How do these new rules better align with customer satisfaction?

In this video, I dive into the often-overlooked but incredibly powerful technique of observation—also known as job shadowing or simply "following people around."

While interviews and focus groups are popular, observation allows us to see what people actually do, rather than what they say they do. This is crucial because we often fall into routines and forget the small details of our daily tasks.

? Key Takeaways:

• Passive vs. Active Observation: * Passive: Observing and taking notes without interrupting. This helps capture the "natural flow" and avoids biasing the outcome.

  • Active: Asking questions and prompting discussions during the observation. This is best for tasks that don't require high levels of concentration. You can even try doing the task yourself to gain a deeper understanding!

• Preparation is Key: Decide who to shadow and what questions to ask beforehand.

• Observation, Not Evaluation: It's vital that those being observed don't feel like they're being "judged" or "monitored" (the "Big Brother" effect). If they're suspicious, it's time for a different approach.

• Expect Revelations: Observation often reveals that what's supposed to happen (the official procedure) is quite different from what's actually happening (how employees have customized the process for themselves).

? Reflective Exercises

Now, let's put these concepts into practice with some reflective exercises. Take some time to consider the following:

1. Identify an "Observation Opportunity"

Think about a process or task in your current workplace that could be improved.

• What's the process?

• Who are the key people involved?

• What specific things would you be looking for during an observation?

2. Choose Your Approach: Passive or Active?

For the process you identified above, which approach would be more effective?

• Passive: Would it be better to just watch and see the "natural flow"?

• Active: Would it be helpful to ask questions and maybe even try the task yourself?

• Why? Explain your reasoning based on the nature of the task and the potential for bias.

3. Communicating the "Why"

How would you explain the purpose of your observation to the person you're shadowing to ensure they don't feel evaluated?

• What specific language would you use?

• How would you emphasize that your goal is to understand and improve the process, not to judge their performance?

4. Anticipating Discrepancies

Based on your knowledge of the process, what "revelations" do you anticipate?

• Do you suspect there's a difference between the official procedure and how the task is actually performed?

• How might these differences be beneficial (e.g., a more efficient "workaround") or problematic (e.g., a safety risk)?

The "Observation Postscript" eLearning video is a compelling look at the power of observation in product development. It features an expert narrator who discusses the challenges and potential of understanding customer needs, specifically when it comes to developing new products.

The video explores several key topics including:

• Understanding user needs: Exploring how observation can reveal needs that users might not be able to articulate themselves.

• The power of prototyping: Discussing how prototypes can be used to gather real-world data and feedback through observation.

• Integrating data and observation: Showing how quantitative data from sensors and qualitative data from observations can be combined for a more comprehensive understanding.

• The evolution of products: Exploring how observation can lead to innovative features and the development of new product categories.

Throughout the video, I use a real-world example to illustrate these concepts, making the content engaging and easy to understand.

Reflective Exercises

Exercise 1: Identifying Hidden Needs

In the video, I emphasize that people often have difficulty articulating their needs. Think about a product or service you use regularly. What are some of its features that you find particularly useful, but wouldn't have necessarily thought to ask for initially?

My reflection: I'm a big fan of my noise-canceling headphones. I never thought I needed them until I started working from home and realized how much background noise can be a distraction. Now, I can't imagine working without them! ### Exercise 2: The Power of Prototyping

The video mentions the importance of prototyping in gathering real-world data. Consider a project you're currently working on or a product you'd like to develop. How could you use a prototype to gather feedback through observation? What specific things would you be looking for?

My reflection: I'm currently working on a new mobile app. I could create a low-fidelity prototype and observe users as they navigate through the app. I'd be looking for things like where they get stuck, what features they use the most, and overall user experience.

Exercise 3: Integrating Data and Observation

I discuss how integrating quantitative and qualitative data can lead to a more comprehensive understanding of user needs. Think about a situation where you've used both types of data to make a decision. How did each type of data contribute to your final decision?

My reflection: When I was choosing a new car, I looked at both quantitative data (like fuel efficiency, safety ratings, and price) and qualitative data (like test drives and reviews from other owners). The quantitative data helped me narrow down my options, while the qualitative data helped me make the final decision based on my personal preferences and needs.

Exercise 4: Identifying Product Evolution

The video explores how observation can lead to innovative features and the development of new product categories. Can you think of any other examples of products that have evolved in this way?

My reflection: One example that comes to mind is the evolution of smartphones. They started as simple mobile phones, but through observation of user behavior and needs, they've evolved into powerful computers that we carry in our pockets.

Welcome to this session on understanding the Customer Journey and Customer Touchpoints. In this lesson, I’m going to walk you through how to shift your perspective from internal operations to the actual lived experience of your customers.

Whether you are a marketer, a software developer, or a business analyst, the goal remains the same: to look at your organization through your customer’s eyes. While different departments might call these artifacts "use cases," "epics," or "process diagrams," we are going to focus on the Customer Journey Map as a tool for meaningful review and improvement.

What We Will Cover

In this lecture, I will guide you through the essential components of mapping a journey:

The Persona: We start by defining exactly who our customer is. We’ll move beyond basic demographics to create a detailed persona—like a 50-year-old father who’s traded his love for alternative music for a more mellow attitude—so we know exactly how to speak to them.

The First Interaction: We track the progress from the very moment a customer realizes you exist, through your first value proposition, and finally to the call to action.

Identifying Touchpoints: We will plot the specific interactions a customer has across various departments.

The Experience Factor: We’ll look at the "cross-channel" reality—how it feels for a customer to move from an online booking to a phone call, and where those "disconnects" often happen.

Elicitation Methods: I’ll share practical ways to gather this data, including focus groups, interviews, observations, and questionnaires.

By the end of this exercise, you won’t just have a map; you’ll have a granular understanding of how your customers feel about their relationship with your organization.

Reflective Exercises

To help you apply these concepts to your own work, take a moment to consider the following:

1. The Persona Deep Dive

Think of a current customer segment you serve. Instead of just listing their age or job title, try to describe their "mellowed attitude" or personal history as I did in the lecture.

How does knowing their personal background change the way you would write a "call to action" for them?

2. Spotting the Disconnect

Recall a time you (as a consumer) were told, "I can’t help you because you booked online and I have no access to that".

Does a similar "cross-channel" wall exist in your own organization?

Which department owns that specific touchpoint, and what is one small change that could bridge that gap?

3. Choosing Your Elicitation Tool

If you had to gather data on a customer's experience by tomorrow but had a very limited budget, which method would you choose?

If you chose a questionnaire, what is one "open-ended" question you could ask to get more than just a 'yes' or 'no' answer?