What Needs to be Done Before You Start Your Project

In this session, I explore the fundamental role of Business Process Management (BPM) as a cornerstone of organizational health. I view business processes not just as tasks, but as organizational assets that must be carefully managed to maintain agility.

I emphasize that while organizations often resist change, they must adapt to uncontrollable external forces like market trends, government regulations, and shifting customer demands. To me, if the people are the "lifeblood" of an enterprise, then the processes are the blood vessels that keep everything moving.

? Key Lessons & Strategies

I covered several critical components of effective BPM:

• The Power of Questions: Before diving into analysis, I always ask: Who owns the process? What is the current performance data? Where is the real opportunity?

• Continuous Improvement: I advocate for the Deming Cycle (Plan-Do-Check-Act) to ensure processes are constantly refined.

• The Maturity Curve: Just like human development (crawl, walk, run), organizations must build maturity incrementally. Leapfrogging steps often leads to failure.

• Technology as a Tool: I strongly believe technology is a supporter, not a leader. It is the enabler that serves the process, not the other way around.

• Executive Support: Without a strategic "yes" from upper management, even the best BPM initiatives are likely to fail.

? Reflective Exercises

To help you internalize these concepts, I’ve designed the following exercises to apply BPM to your current environment:

1. The "Blood Vessel" Audit

Think of one major process in your current organization (e.g., onboarding, sales, or technical support).

• Reflect: Is the "blood" flowing smoothly, or is there a blockage (bottleneck)?

• Action: Identify one specific external influence (like a new regulation or a competitor's move) that could "rupture" this process if you don't adapt.

2. Maturity Mapping

Assess your team's current process maturity using the Crawl-Walk-Run analogy.

• Reflect: Are you trying to "run" (implement AI automation) before you can "walk" (standardize manual data entry)?

• Action: List the foundational skills or documentation needed to move from your current stage to the next.

3. The "Servant" Technology Check

List the primary software tools your team uses daily.

• Reflect: Does the technology dictate how you work, or does your workflow dictate how you use the technology?

• Action: Identify one feature in your current tech stack that complicates a process rather than simplifying it. How would the process look without it?

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 your customers' lived experience.

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 will 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?

In this session, I explore the concept of Power Laws and why our standard expectations of "normal" often fail us. Using the Fukushima reactor's design as a starting point, I discuss the danger of using models of uncertainty to produce a false sense of certainty. While experts believed a tremor larger than 8.6 was statistically impossible, the 2011 earthquake reached 9.1.

We often ignore events that fall outside the "three standard deviations" of a typical bell curve—the 99.7%. However, not all data has a "mean" or average that tells the whole story. In many systems, infrequency does not equal minimal impact. This is the essence of a Power Law: a relationship where "freak events" (the long tail) are responsible for the most significant changes.

I also delve into the Pareto Principle, or the 80/20 Rule. This principle illustrates that in many systems, the majority of effects come from a small minority of causes. By understanding that large catastrophic events often occur for the same reasons small ones do, we can move away from a false sense of security and better respect the interdependencies of the world around us.

Reflective Exercises

• The "Black Swan" Moment: Reflect on a major turning point in your life or career. Was it the result of a slow, predictable trend, or did it happen because of a single, unforeseen "freak event"?

• The 80/20 Audit: Look at your daily habits or the tools you use. Do you find that a small fraction (20%) of your efforts or resources produces the vast majority (80%) of your results? How does that change your perspective on where to focus your energy?

• Beyond the Average: Think of a system you interact with (like traffic, the weather, or social media). When has "the average" completely failed to predict what actually happened? What was the impact of that outlier?

• Interdependency: Consider a "small" event you’ve witnessed that spiraled into something much larger. Looking back, what were the hidden connections that allowed that small change to trigger a massive outcome?

In this session, I’m taking you beyond the textbook. We aren’t just memorizing a list from 1980; we are diving into the "perfect storm" of the European Aviation Industry to see how Michael Porter’s framework actually functions in the real world.

Think of these five forces as a hydraulic press. When they all push inward at once, profit margins are what get crushed. I want to show you why it’s significantly harder to keep a plane in the air profitably than it is to sell a can of soda.

The Five Forces in the Cockpit

• Industry Competitors: I look at the European skies and see a "clash of titans." On one side, we have the legacy giants like Lufthansa; on the other, the relentless efficiency of Ryanair. Because a seat is essentially a commodity, I see a permanent price war, with the only way to win being to be the cheapest.

• Suppliers: This is where the squeeze gets real. If I’m running an airline, I can’t just "shop around"—I’m stuck in a duopoly between Airbus and Boeing. To make matters tougher in 2026, I’m now mandated to use expensive Sustainable Aviation Fuel (SAF), giving fuel suppliers massive leverage over my bottom line.

• Buyers: I recognize that the modern traveler has unlimited bargaining power. With tools like Skyscanner, I know my customers will swap loyalty for a €10 saving in a heartbeat. There is zero "switching cost," putting the buyer in the captain's seat when it comes to ticket prices.

• Potential Entrants: I’ve watched how the internet lowered the barriers to entry. New players like Norse Atlantic can bypass traditional agents and sell directly to my customers, forcing even the most established legacy carriers to rethink their entire transatlantic pricing strategy.

• Substitutes: I never assume the customer has no choice. In Europe, my biggest threat isn't always another plane; it’s the High-Speed Rail. If a train is greener and faster from Paris to Lyon, I’ve lost that passenger. Even digital tools like Zoom have become substitutes for my most profitable business travelers.

Reflective Exercises

Pause for a moment and consider your own professional context through this lens.

Exercise 1: Identifying Your "Squeeze" Of the five forces mentioned, which one currently exerts the most "pressure" on your specific business or industry? Is it a powerful supplier, a price-sensitive buyer, or a new digital entrant? Write down one specific way this force limits your ability to raise prices.

Exercise 2: The Substitute Reality Check Think about your primary product or service. If it vanished tomorrow, what is the least obvious thing your customers would use instead? (Remember: for airlines, it was a webcam and a Zoom link). Does that substitute offer a convenience or environmental advantage you are currently ignoring?

Welcome to this e-learning module on Organizational Modeling. I’ve designed this session to be more than just a lecture; it’s a toolkit for understanding the "bones" and "nervous system" of any company or team you work within.

1. Defining the Landscape

First, let’s start with a definition of what we are covering. I like to think of Organizational Modeling as a diagnostic tool. We use it to determine if the organizational units or people involved have unique needs, interests, or constraints that must be considered for the business to function.

In this session, I’m going to walk you through what an organizational model actually is, why they are structured the way they are, and finally, we’ll examine the classic organization chart.

What is an Organizational Model?

At its simplest, an organizational model explains how a unit is set up. The goal is to group people together to fulfill a common objective or goal. That purpose might be functional (people with similar skills or knowledge) or market-based (people grouped because they serve the same customer or geographic area).

2. The Three Basic Structures

There are three frameworks you’ll encounter most often. I’ve worked in all of them, and each has its own "vibe":

• Functional Organization: This is "business as usual." Everything is based on what you do every day—your specific job craft. It’s stable, but it can be rigid.

• Matrix Organization: This is where things get interesting. You might have multiple reporting lines—a solid line to one boss and a dotted line to another. If it sounds confusing, it is. I can tell you from personal experience, balancing two bosses is an art form.

• Projectized Organization: Here, the project is king. Virtually all activities are tied to specific projects rather than ongoing departmental work.

? Reflective Exercise: Where Do You Fit?

Stop for a moment and look at your current (or most recent) workplace.

• Do you report to one person or many?

• Are you grouped with people who do exactly what you do, or people who serve the same client?

• Reflect: How does this structure affect how quickly you can get a decision made?

3. Deep Dive: Purpose and Silos

The form an organization takes speaks volumes about how they do business. Structure is a clear environmental factor that dictates how work flows.

• Functional Structures group people by expertise. It’s great for keeping costs down through standardized processes, but it’s the best model I know for creating silos. People stop talking to other departments, and information gets trapped.

• Market-Oriented Structures mimic the customer. They are agile and customer-focused, but you often lose standardization. Service standards can become inconsistent because every "market" or region is doing its own thing.

4. The Org Chart: The Essential Diagram

The essential tool here is the Org Chart. While there’s no formal "legal" standard, we usually follow these conventions:

1. Organizational Units: These can be small (one person) or large (entire departments or regions).

2. Lines of Reporting: A real labyrinth! A solid line usually denotes formal authority (the person who signs the paycheck), while a dotted line is often for administrative or efficiency-based communication.

3. Roles and People: It should show the roles that exist and who is currently assigned to them.

A word of caution: You might find that an up-to-date org chart is the hardest document to find. Some companies treat them like goldmines for the competition, fearing outsiders will "read" too much into their inner workings.

5. Beyond the Chart: The Ecosystem Map

Traditional charts are great, but they don't show how work actually happens. For that, I look at the SIPOC model (Suppliers, Inputs, Process, Outputs, Customers).

When we turn this into an Organizational Ecosystem Map, we see the interactions. It’s a flow: Suppliers on the left, Customers on the right. Sometimes, the customer is the supplier (giving you raw materials so you can give them a finished product).

My "Recipe" for Building an Ecosystem Map:

1. Validate the Org Chart: Find the latest one and see if it’s actually accurate today.

2. Cross-Reference Process Diagrams: If a department exists in a process map but not on the org chart, you’ve found a discrepancy. One of them is obsolete!

3. Map the Interrelationships: Draw the flow between suppliers, departments, and customers.

4. Validate (Carefully): You usually can't ask customers or suppliers directly, so validate internally as much as possible.

6. Why Bother? (The "So What?")

Why do I spend time on this? Because an Ecosystem Map is a powerhouse for:

• Process Improvement: You’ll hear people say, "Why am I doing that? I just throw it away when I get it from you anyway!"

• Impact Analysis: If you change a process here, who "downstream" gets hit?

• Strategic Alignment: Are we actually doing what we planned? Or is the "process tail wagging the strategic dog"?

? Final Reflection: The "Invisible" Map

Think of a process you handle daily.

• Who is your "Supplier" (who gives you the info or material to start)?

• Who is your "Customer" (the next person in line who relies on your output)?

• Reflect: If you disappeared tomorrow, who would feel the "gap" first? That link is the most important line on your ecosystem map.

? Navigating the "Hidden" Office: A Guide to Informal Organizations

In this session, I explore the fascinating (and often messy) world of informal organizations. While the official org chart tells us who reports to whom, it rarely explains how work actually gets done. I’ve lived through enough "reorgs" to know that when the formal structure breaks down, the informal one—the real engine of the company—kicks into high gear.

What We Covered:

• The Formal vs. Informal Divide: I define the difference between the rigid, documented structure of a company and the fluid, human-centric ways employees solve problems.

• The "Mushroom" Effect: I describe how procedural workarounds "pop up like mushrooms" during organizational changes, especially when roles and responsibilities become blurred.

• The Jack and Jill Dilemma: Through a relatable story, I illustrate how employees often perform "forbidden" tasks or help each other out of sight just to keep things moving.

• Communities of Practice: I dive into the concept introduced by Lave and Wenger—social learning networks where people share expertise because they want to, not because they’re told to.

• Motivators: I contrast external motivators (bonuses, sales targets) with internal motivators (autonomy, mastery, and the simple desire to help).

? Reflective Exercises

Take a moment to think about your own workplace through the lens of our discussion.

1. Mapping Your "Mushrooms"

Think about a recent change or bottleneck at your company.

• What "workaround" did you or your colleagues create to bypass a slow or broken process?

• If that informal step were removed tomorrow, would the work still get done?

2. Identifying Your "Joe"

In the video, "Joe" was the bridge between Jill and Jack.

• Who is the "Joe" in your department? The person who knows everyone and knows exactly who to call to get a "favor" done?

• How can you better support these informal connectors?

3. Your Community of Practice

Think about the last time you learned a new skill at work.

• Did it come from a formal training manual, or a casual conversation with a peer?

• What topics or skills would you be willing to share with others for free, simply because you enjoy the mastery of it?

"We share because it doesn't cost us anything... and we never know when we might need that help in return."

?️ Course Overview: Navigating Your Stakeholder Landscape

In this session, we dive into the "why" and "how" of Stakeholder Analysis. I believe this is one of the most critical activities in any initiative because projects don't exist in a vacuum—they are powered (and sometimes hindered) by people.

Key Takeaways:

• The Definition: A stakeholder is anyone—positively or negatively—affected by your initiative.

• The Strategy of Grouping: Not all stakeholders are equal. We explore how to categorize them by interests, needs, or influence to keep your project on the path to success.

• Primary vs. Secondary: We distinguish between those directly impacted and those who are on the periphery.

• Building the List: I share my personal approach, which starts with analyzing existing processes, moving to organizational charts, and finally, using brainstorming techniques when documentation is scarce.

? Reflective Exercises

To get the most out of this, take a moment to consider these questions based on a project you are currently working on:

1. The Hidden Influencer: Looking at your current project, is there someone you haven't officially listed as a stakeholder but who could be "negatively affected" by the change? How might their influence impact your timeline?

2. The Actor Audit: Think about the "actors" in your project. Are there any non-human actors (like a specific software system or a legacy database) that you need to account for in your analysis?

3. The Brainstorm Challenge: If you had to lead a 10-minute brainstorming session today to identify stakeholders, who are the three most diverse people you could invite to ensure you don't miss any "secondary" stakeholders?

"The more exact you are in your categorization, the better—but you have to start somewhere."

Mastering the RACI Technique: A Practical Guide

As a professional, I've found that the RACI technique is one of the most valuable tools in my project management toolkit. It’s an effective way to clarify roles and responsibilities within an organization or a specific assignment.

RACI stands for Responsible, Accountable, Consulted, and Informed. Each of these roles has a distinct function:

• Responsible: The person who actually performs the task.

• Accountable: The person who is ultimately answerable for the task's completion and quality.

• Consulted: The subject matter experts who provide input and guidance.

• Informed: Those who need to be kept up to date on progress.

The RACI matrix is a powerful way to visualize these roles, as it allows you to see at a glance who is involved in each task and what their role is. It's also an excellent way to develop a communications plan, as it helps you identify who needs to be informed and how much detail they require.

Reflective Exercises

Now that you’ve learned about the RACI technique, take some time to reflect on how you can apply it in your own work.

1. Identify a project or assignment where the RACI technique could be useful. What are the key tasks and who are the stakeholders involved?

2. Create a RACI matrix for this project. Assign the roles of Responsible, Accountable, Consulted, and Informed to each task and stakeholder.

3. How will this RACI matrix help you manage the project more effectively? What are the benefits of clarifying roles and responsibilities in this way?

4. Think about how you can use the RACI technique to improve communication with your stakeholders. What information do they need to know and how often should you communicate with them?

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?

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: Those being observed mustn'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. I discuss 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.

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.

This is what it's all about: Vision, Mission, Strategy, Objectives, Organization, and Tasks. The lecture uses a pyramid model to illustrate how these elements build upon each other, from the high-level purpose to the daily activities of employees.

Key Concepts and Definitions

Vision: The "Why"

• Definition: A forward-looking statement that defines what the company stands for and where it wants to be in the future.

• Purpose: To inspire and gain commitment from everyone in the organization.

• Characteristics: Often idealistic, setting a clear direction and reflecting the company's core values.

Mission: The "What"

• Definition: A statement that describes what the company does, its business field, products/services, and target audience.

• Timeframe: Typically has a shelf-life of 3 to 5 years.

• Impact: Organizations with actionable and well-communicated mission and vision statements tend to perform better.

Strategy: The "How"

• Definition: The plan of action designed to achieve the vision and mission. It sets the tone for management and provides a roadmap for success.

Objectives: The Benchmarks

• Definition: Measurable goals that determine whether the strategy is effective.

• Examples: Market share, productivity, innovation, financial performance, human resources, and social responsibility.

Organization and Tasks: The "Execution"

• Organization: The structure of the company must reflect the vision and facilitate the execution of the mission and strategy.

• Tasks: The specific activities performed by employees to fulfill the organization's goals. These are the practical application of the higher-level concepts.

Reflective Exercises

To help you internalize these concepts, consider the following exercises:

1. Analyze Your Organization: Identify the vision, mission, and strategy of your current or a previous organization. How well do these elements align with the daily tasks you perform?

2. Personal Vision and Mission: Create your own personal vision and mission statement for your career. What do you want to achieve, and what steps will you take to get there?

3. The Impact of Communication: Reflect on a time when an organization's vision or mission was clearly communicated. How did it affect your motivation and performance?

4. Aligning Tasks with Strategy: Choose a specific task you perform regularly. How does this task contribute to the overall strategy and objectives of your organization?

5. Evaluating Success: Think about the objectives mentioned in the lecture (e.g., market share, innovation). Which of these do you think are most important for your organization's success, and why?

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 session, I introduce a technique developed by Edward de Bono in the mid-1980s. The "Six Thinking Hats" method enables individuals and groups to move beyond simple brainstorming by adopting six distinct roles, or "hats," one at a time. This structured approach fosters parallel thinking, where everyone in a group looks at the same aspect of a problem simultaneously.

The six hats are:

• White Hat: Focuses on available facts and data.

• Red Hat: Expresses emotions and intuition without the need for justification.

• Black Hat: Identifies potential risks, problems, and what could go wrong.

• Yellow Hat: Represents pure optimism, focusing on benefits and advantages.

• Green Hat: Encourages creativity, ideas, and solutions.

• Blue Hat: Acts as the facilitator and analyzer, managing the overall process.

By the end of this session, you'll understand how to apply this technique to real-world scenarios, such as improving customer service, while following specific ground rules to ensure objectivity and structure.

Reflective Exercises

To help you internalize this method, I invite you to complete the following exercises:

1. Analyze Your Natural "Hat": Think about a recent decision you made. Which of the six "hats" did you naturally wear the most? Were you more focused on the facts (White Hat), the risks (Black Hat), or your feelings (Red Hat)?

2. Practice Parallel Thinking: Identify a current challenge in your work or personal life. Spend five minutes looking at it exclusively from the Yellow Hat (optimistic) perspective. Then, spend five minutes looking at it only from the Black Hat (critical) perspective. How does this shift in focus change your understanding of the situation?

3. The Blue Hat Challenge: Imagine you are leading a team meeting to solve a specific problem. How would you use the Blue Hat to structure the order of the other hats? Remember, the process should always begin and end with the Blue Hat.

4. Objectivity Check: Think of a topic you feel strongly about. Try to analyze it using the White Hat (facts only). How difficult is it to separate your emotions from the data? What steps can you take to improve your objectivity in the future?

In this module, I’m going to walk you through one of my favorite tools for navigating the professional world: the SWOT Analysis. I’ve found that whether I’m leading a massive project or just trying to improve my own department's efficiency, I need a way to cut through the noise.

I designed this course to show you how to look at any situation through a four-part lens: Strengths, Weaknesses, Opportunities, and Threats. I’ll show you how I separate the internal factors we can control from the external forces we can’t, and most importantly, how I turn those observations into a concrete plan of action. My goal isn’t just to teach you a definition; it’s to give you a framework that helps you decide—with confidence—whether a solution is actually viable or if a risk is worth taking.

Reflective Exercises

I’ve included these prompts to help you bridge the gap between theory and your actual daily work. Take a moment to grab a notebook or open a blank doc.

Exercise 1: The "Internal Mirror"

Think about a project you are currently working on or a team you belong to.

• Reflection: If I had to be brutally honest, what is the one "Weakness" currently holding us back? Is it a lack of resources, a gap in knowledge, or perhaps a communication breakdown?

• The Pivot: Now, look at your "Strengths." Which specific strength do I possess—or does my team possess—that could directly neutralize that weakness?

Exercise 2: Scanning the Horizon

Think about your industry or field over the next twelve months.

• Reflection: What is one "Threat" I see looming on the horizon? (e.g., a new competitor, a shift in technology, or a change in regulations).

• The Strategy: Instead of just worrying about it, I want you to identify one "Opportunity" that this threat might actually create. How can I position myself to take advantage of that shift before others do?

Exercise 3: The Viability Test

Consider a "New Idea" or a change you’ve been wanting to implement at work.

• Reflection: If I plot this idea into a SWOT matrix right now, does the "Opportunities" list outweigh the "Threats"?

• The Decision: Based on this visual, is this a solution I would advocate for in a high-stakes meeting? Why or why not?