I like simple drawings.

They often say more about organizations than 200-slide strategy decks.

In this image, four roles appear: Controllers, Creatives, Producers, and at the center, Glue. It looks almost playful. But it captures something essential about how products and services actually come to life.

At its core, product and service development is not about ideas.
It is about holding three forces in tension:

• Desirability – Do people actually want this?

• Feasibility – Can we realistically build and sustain it?

• Viability – Does it make business sense?

When one dominates, the system tilts.

Viability – The Logic of Sustainability

The Controllers represent viability.

They care about:

• Financial health

• Strategic alignment

• Risk

• Measurable outcomes

Without viability, innovation becomes expensive experimentation. We build things that impress but do not endure.

But when viability dominates, fear quietly shapes decisions. Short-term control replaces long-term courage. Exploration shrinks.

Viability is not the enemy of innovation. It is its stabilizer. But it cannot lead alone.

Feasibility – The Discipline of Delivery

The Producers represent feasibility.

They care about:

• Capacity

• Competence

• Systems

• Processes

• Operational reality

They live in the tension between ambition and resources.

Without feasibility, strategy remains conceptual. Roadmaps become fiction. Teams burn out trying to deliver what the system cannot support.

But when feasibility dominates, the organization slowly becomes allergic to change. “This is how we do things” hardens into culture.

Feasibility is not about limitation. It is about responsible realization.

Desirability – The Courage to Care About Users

The Creatives represent desirability.

They ask:

• Does this solve a real problem?

• Is it intuitive?

• Does it matter to people?

• Is there product–market fit?

Without desirability, organizations become efficient at producing irrelevance.

But when desirability stands alone, ideas remain beautiful and disconnected from reality.

Desirability gives direction.
Feasibility gives structure.
Viability gives endurance.

The Most Undervalued Capability: Glue

At the center sits Glue.

The one who:

• Connects finance and design

• Translates constraints into creative possibilities

• Aligns delivery teams with strategic intent

• Holds difficult conversations

• Builds shared understanding

Glue is rarely a formal job title. It often shows up in:

• Strong product leaders

• Service designers

• Innovation leads

• Facilitators

• Mature product owners

Glue is not soft. It is systemic.

Without Glue:

• Controllers push back.

• Creatives push forward.

• Producers protect stability.

• Silos win.

With Glue:

• Trade-offs become conscious.

• Tension becomes productive.

• Decisions become clearer.

Most organizations do not struggle because of lack of talent.
They struggle because no one is intentionally holding the whole system together.

A Quiet Diagnostic

If you look at your current context, where is the imbalance?

• Are financial controls suffocating experimentation?

• Are delivery teams overloaded and reactive?

• Are user insights disconnected from strategic priorities?

• Or is no one bridging the conversations that matter most?

The quality of your products often reflects the quality of the conversations between these roles.

Product Excellence Is an Orchestration Problem

Great product and service development is not about maximizing one dimension.

It is about consciously orchestrating:

• What users need

• What teams can sustain

• What the business can support

And developing the capability to move between these perspectives without losing alignment.

That orchestration does not happen by accident. It is designed.

If You Are Navigating This Tension

Many leaders I speak with feel this pressure:

• Finance pulling one way

• Delivery teams overwhelmed

• User expectations evolving

• Strategy unclear

If you are working in that space, trying to create coherence across disciplines, reduce friction, and strengthen collaboration, this is precisely the work I support.

Through facilitation, advisory work, and coaching, I help leaders and teams:

• Clarify strategic intent

• Strengthen cross-functional dialogue

• Navigate complexity without oversimplifying

• Build stronger “Glue” capabilities inside the organization

If this reflection resonates with where you are right now, let’s have a conversation.

Sometimes what organizations need most is not a new framework.
It is better alignment between the people already there.

We live and work in a world that feels increasingly unstable.

Volatile.
Uncertain.
Complex.
Ambiguous.

VUCA is no longer a theoretical framework from military strategy textbooks. It’s Tuesday morning in your organization.

Add to that:

• Climate transitions

• Digital transformation

• AI disruption

• Budget cuts and reorganizations

• Shifting citizen expectations

• Talent shortages

• Political polarization

And suddenly we’re not just dealing with “problems.”

We’re dealing with wicked problems.

What Makes a Problem Wicked?

Wicked problems:

• Have no clear definition

• Have no single right answer

• Involve many stakeholders with conflicting perspectives

• Change while you’re trying to solve them

• Cannot be solved once and for all

Healthcare reform. Urban development. Digital inclusion. Youth unemployment. Organizational transformation.

You don’t “fix” them.

You navigate them.

And that’s where service design becomes essential.

Service Design as a Navigation System

Service design is often misunderstood as post-it notes, workshops, or journey maps.

But at its core, service design is something much deeper:

A structured way of thinking and working in complexity.

It helps organizations move from:

• Assumptions → Insight

• Silos → Systems

• Opinions → Evidence

• Big ideas → Tested prototypes

• Fear → Learning

In a VUCA world, service design doesn’t remove uncertainty.
It makes uncertainty workable.

1. From Chaos to Clarity

In volatile environments, people rush to solutions.

Service design slows us down just enough to ask:

• What problem are we actually trying to solve?

• For whom?

• In what context?

• What does success look like?

Through stakeholder mapping, user research, system visualization, and journey mapping, complexity becomes visible.

And once you can see the system, you can start influencing it.

2. From Complexity to Collaboration

Wicked problems live between departments.

But most organizations are structured in silos.

Service design brings:

• Cross-functional workshops

• Co-creation sessions

• Shared language

• Collective sense-making

Instead of fighting complexity, teams learn to hold it together.

This builds alignment, ownership, and psychological safety — all prerequisites for innovation in uncertain environments.

3. From Risk Avoidance to Safe Experimentation

In ambiguous situations, many organizations freeze.

Service design introduces prototyping as a mindset:

• Test small

• Learn fast

• Reduce risk early

• Iterate continuously

Instead of betting everything on a five-year master plan, you create learning loops.

In a VUCA world, adaptability is more valuable than certainty.

4. From Outputs to Real Value

Many organizations measure activity:

• Number of projects

• Number of initiatives

• Number of digital tools launched

Service design shifts the focus to outcomes:

• Did it create value for users?

• Did it simplify processes?

• Did it reduce friction?

• Did it improve trust?

• Did it increase engagement?

In complex systems, value is relational and systemic — not just transactional.

The Deeper Layer: State of Mind in Complexity

Here’s something we rarely talk about.

Navigating wicked problems is not only about tools and methods.

It’s about state of mind.

In VUCA environments:

• Fear rises

• Control tightens

• Defensiveness increases

• Blame spreads

But service design, when practiced well, cultivates:

• Curiosity

• Openness

• Empathy

• Systems thinking

• Shared responsibility

The external complexity mirrors our internal state.

When leaders operate from clarity rather than fear, complexity becomes manageable.

When teams feel safe, creativity emerges.

When organizations listen deeply, innovation follows.

Service Design Is Not About Control

It’s about:

• Seeing the whole system

• Engaging the right people

• Learning continuously

• Designing with, not for

• Creating value that lasts

In a VUCA world, control is an illusion.

But direction is not.

Service design provides direction.

If You’re Facing a Wicked Problem Right Now

Ask yourself:

• Have we truly understood the problem?

• Have we involved the people affected?

• Have we visualized the system?

• Are we testing small before scaling big?

• Are we measuring real value — or just activity?

If the answer to several of these is “no,” you don’t need more pressure.

You need better design.

Final Thought

VUCA is not going away.

Wicked problems will not disappear.

But organizations that embrace service design as a way of thinking — not just a toolkit — will:

• Move faster with less chaos

• Collaborate better across silos

• Reduce waste and friction

• Create meaningful, measurable value

• And build resilience for whatever comes next

The question is not whether your organization faces complexity.

The question is:

Do you have a way to navigate it?

Ready to Navigate Complexity Differently?

If your organization is facing:

• A messy transformation

• A stalled innovation initiative

• Cross-silo friction

• Unclear direction

• A wicked problem that refuses to “go away”

You don’t need more pressure.

You need clarity, alignment, and a structured way to move forward.

That’s where I can help.

As a Senior Service Designer and Innovation Lead with deep experience navigating complexity in both public and private sectors, I help leaders and teams:

• Make sense of messy systems

• Align stakeholders around real problems

• Design practical, testable solutions

• Create measurable value — not just activity

I’m currently available and actively looking for new professional challenges where I can contribute strategically and hands-on.

If you’re working on something complex and important — let’s talk.

Send me a message.
Book a coffee.

Invite me into the conversation

Wicked problems don’t solve themselves.

But with the right mindset and the right design approach, they become navigable.

Let’s design value in complexity, together.

In modern IT organizations, technology evolves fast but people and collaboration often struggle to keep up. The biggest challenge today is not building the right product, but building the right team to make it happen.

That’s where the Team Coach comes in.

A Team Coach helps teams and leaders navigate complexity, collaborate effectively, and create the conditions where both people and performance can thrive. Their work goes far beyond process or tools, it’s about enabling trust, autonomy, and continuous learning at scale.

What Does a Team Coach Do?

A Team Coach works with one or several teams to strengthen how they work together.
They don’t manage the team or tell them what to do instead, they create space for reflection, experimentation, and growth.

Their work typically involves:

• Coaching teams and leaders to become more autonomous, value-oriented, and self-improving.

• Facilitating conversations that surface challenges, align expectations, and strengthen relationships.

• Designing and leading workshops on topics like feedback, collaboration, or goal-setting.

• Building a culture of learning through retrospectives, health checks, and continuous improvement.

• Connecting teams and stakeholders to ensure transparency and shared purpose.

• Supporting the organization in becoming more adaptive, resilient, and human-centered.

A Team Coach helps the system work, not by adding more control, but by enabling people to take ownership and make smarter decisions together.

The Value a Team Coach Brings

1. Stronger collaboration and trust
They help teams build psychological safety — the foundation for open dialogue, shared responsibility, and real problem-solving.

2. Better alignment and outcomes
When teams understand their purpose and how it connects to larger goals, motivation and ownership rise.

3. Sustainable performance
Healthy teams deliver more over time because they learn, adapt, and recover faster.

4. Healthier culture
Through daily interactions, the coach nurtures feedback, learning, and transparency across the organization.

5. Less dependency on management
By empowering autonomy, the Team Coach brings decisions closer to where knowledge lives, inside the team.

The Challenges a Team Coach Helps Solve

In IT, challenges are rarely just technical. They’re human and systemic:

• Siloed communication and lack of alignment.

• Overloaded teams with unclear priorities.

• Low psychological safety.

• Firefighting with no time for learning.

• Leadership expectations disconnected from reality.

A Team Coach helps teams face these issues, not by providing quick fixes, but by facilitating lasting change from within.

What Kind of Profile Fits This Role?

A great Team Coach blends experience, empathy, and curiosity.
They’re not a manager, not a consultant, but a growth enabler.

Key traits include:

• Experience in modern tech or product organizations.

• Strong facilitation and communication skills.

• Deep understanding of team dynamics and group development.

• High emotional intelligence and empathy.

• A learning mindset, not a “framework-first” approach.

• Ability to coach both individuals and systems.

• Comfort with ambiguity and change.

Formal certifications help, but what truly matters is the ability to listen deeply, read the room, and enable others to find their own clarity.

Coaching as a Partnership, Not a Prescription

The coach doesn’t come with all the answers.
They ask questions, mirror back observations, and help teams uncover their own insights.

Their role is to shift the mindset from:

• “We’re stuck” → “We understand what’s blocking us.”

• “We need someone to fix this” → “We can fix this together.”

• “We don’t have time for reflection” → “We can’t afford not to reflect.”

The Bigger Picture

When organizations embed coaching as part of their culture, they build organizational muscles for learning, collaboration, and resilience.
It’s not about scaling a framework, it’s about scaling awareness, trust, and growth.

In a complex IT world, that becomes the true competitive advantage.

Final Reflection

A Team Coach is not a luxury, it’s a catalyst for transformation.
They work quietly, behind the scenes, helping teams find clarity amid chaos, and reminding everyone that how we work together is just as important as what we deliver.

In times of constant change, the Team Coach might just be the most strategic role an IT organization can have — not because they lead from the front, but because they help everyone else rise.

I hope this post, made sense and you found it useful.

If “HELL YEAH!”, please like it and share it in social media so more people can get can also benefit from it :-)

I would also appreciate if you subscribe, and give some comments here if you wonder something and want to give me some feedback. I would love to read your input here!

If you have a Substack yourself and like my content, I would love for you to recommend “Facili-station” to your subscribers.

Have a nice one!!

Looking for a coach?

In service of those who serve others.

Leadership is hard. Whether you’re stepping into management, leading an entire organization or wondering about your career, the challenges are real: confusing, overwhelming, and sometimes isolating.

I offer a tailored 1:1 or team coaching quarterly program to help you move forward with clarity and confidence. I’ve walked in your shoes, and I’ll work with you to build the resilience and relational skills needed to lead well, beyond just the work.

If this sounds like what you need, let’s talk. Email me at jose@facilistation.com to book a no-strings attached, no-obligation call to talk about your needs and see what I can offer that will fit you the best. Because coaching isn’t expensive. Staying stuck is.

You should see the cost of a life and work that you don’t love... sometimes one good conversation can change your life and your career forever.

Looking for a facilitator and workshop designer?

If you need a workshop designer and facilitator to help you or your team to solve challenges, find solutions, make decisions, and to be more effective an perform better and faster, or a trainer to teach your team on how do this, please contact me at jose@facilistation.com

My workshops are designed to provide the structure required to quickly align and move forward with a plan or idea so you can reclaim time, energy and headspace.

In the fast-moving world of teams and projects, whether in tech, public service, design, or community initiatives, one simple ritual can drastically improve communication, alignment, and momentum: the daily stand-up.

While it's often associated with Agile and Scrum practices, the daily stand-up is a flexible tool that can be adapted to any context where a group of people works toward a shared goal. In this post, we'll explore what a daily stand-up is, its key elements, its benefits, and when it makes sense to use it—even outside the traditional Agile bubble.

What Is a Daily Stand-Up?

A daily stand-up (also known as a daily huddle or morning check-in) is a short, structured meeting—typically held standing up to keep it brief—where team members quickly update each other on their current work and any blockers.

The typical duration is 10–15 minutes, and it usually happens at the start of the day and It is done standing up (to keep things brief), it’s a pulse-check, not a deep-dive.

Think of it as your team’s heartbeat: regular, grounding, and energizing.

Key Aspects of a Daily Stand-Up

1. Same time, same place
   Routine builds rhythm. Consistency helps the team plan and reinforces accountability.

2. Everyone speaks, but briefly
   It’s not a reporting session to the manager—everyone addresses the team.

3. The standard 3 questions (but flexible)
   Traditionally:

   • What did I do yesterday?

   • What will I do today?

   • Are there any blockers?

   But these can be adapted. For example, a design team might ask:

   • What feedback did I get?

   • What am I prototyping today?

   • Where do I need input?

4. Visual management helps
   A Kanban board, a shared digital workspace, or even sticky notes can enhance focus and help spot bottlenecks.

5. Time-boxing is key
   It’s not a space for deep discussions—those should happen afterward with the relevant people.

Benefits of a Daily Stand-Up

• Improved communication: Everyone stays in the loop with minimal overhead.

• Faster problem-solving: Blockers are identified early and can be addressed quickly.

• Increased accountability: Team members track their commitments day by day.

• Higher engagement: Everyone has a voice and visibility in the process.

• Better flow of work: It helps identify patterns, delays, and opportunities to rebalance workloads.

• Strengthened team culture: Regular, informal contact builds trust and cohesion.

• Human rhythm: When things are messy or uncertain, this ritual builds momentum.

When (and Where) to Use Daily Stand-Ups

Daily stand-ups originated in Agile and Scrum, but their utility goes far beyond.

Here are a few settings where daily stand-ups work wonders:

• Design teams using the Business Model Canvas or Service Blueprinting, needing to sync on iterative work and stakeholder feedback.

• Public sector innovation teams, balancing policy design, user insight, and cross-departmental collaboration.

• Startup teams, where speed and clarity are essential, and everyone wears multiple hats.

• Operations teams, such as those running live services or community programs, who need daily coordination and rapid response.

• Event or campaign teams, working toward a clear deadline with multiple moving parts.

• Volunteer or civic groups, where consistent check-ins can build a rhythm without formal hierarchy.

It’s especially useful when:

• Work is interdependent

• Teams are remote or hybrid

• Timelines are tight

• Projects are ambiguous or evolving

• You want to build trust and rhythm in a newly formed team

Try This With Your Team

Want to get started tomorrow? Here’s a simple script:

1. Set a fixed time (e.g., 09:00) and keep it consistent.

2. Gather around your canvas, board, or task tracker.

3. Ask:

   • “What moved yesterday?”

   • “What’s my next small move?”

   • “What’s stuck or unclear?”

4. End with:

   • “Anything that needs a deeper chat?”—and then park that for after.

Stick with it for one week, then reflect: What’s working? What’s missing?

Final Thoughts

The daily stand-up is a facilitation tool disguised as a tech ritual. It gives your team just enough structure to reduce friction, it’s a pulse check, a coordination tool, and a team health booster.

And while it’s rooted in software development, it’s not confined to it. Whether you're redesigning a public service, launching a campaign, or running a cross-sector collaboration, the daily stand-up can help keep things moving, aligned, and human.

Try it for a week. Keep it short, honest, and regular. And don’t be afraid to adapt it to your context. Like any great tool, it works best when it’s shaped by the people who use it.

PS) Exciting Changes Ahead at Facili-station!

Thank you for being part of this journey! From now on, 90% of Facili-station's content will be available exclusively to paid subscribers. For just $100 per year, less than the cost of a couple of Starbucks coffees each month, you’ll not only access premium facilitation and innovation insights but also receive free coaching, mentoring, and be part of an exclusive professional community.

From now on I will publish one open post each month that will be accessible to all subscribers (like this one), both free and paid. In addition, I will share four exclusive posts every month, available only to my paid subscribers.

These exclusive posts will dive deeper into service design, innovation, facilitation techniques, and practical insights to help you grow as a facilitator.

Paid subscribers will also enjoy added benefits like

• free facilitation coaching and mentoring with me, and

• access to a special social community.

Your support keeps this platform thriving, and I’d love for you to be part of this next chapter. Join us and continue growing with Facili-station!

— José Manuel Redondo Lopera

I hope this post, made sense and you found it useful.

If “HELL YEAH!”, please like it and share it in social media so more people can get can also benefit from it :-)

I would also appreciate if you subscribe, and give some comments here if you wonder something and want to give me some feedback. I would love to read your input here!

If you have a Substack yourself and like my content, I would love for you to recommend “Facili-station” to your subscribers.

Have a nice one!!

If you need a workshop designer and facilitator to help you or your team to solve challenges, find solutions, make decisions, and to be more effective an perform better and faster, or a trainer to teach your team on how do this, please contact me at jose@facilistation.com

My workshops are designed to provide the structure required to quickly align and move forward with a plan or idea so you can reclaim time, energy and headspace.

Change is at the heart of progress, but successfully navigating it requires both structure and empathy. Too often, change initiatives fail because they focus only on processes or only on people. What if we could combine the best of both worlds?

Enter The Change Journey—a new tool that blends Change Management principles (such as the ADKAR model) with Service Design methodologies (like the Customer Journey). This fusion creates a powerful framework for leading change in a way that is both systematic and human-centered.

Why Merge Change Management and Service Design?

Traditional Change Management tools, like Prosci’s ADKAR model, offer a structured approach to organizational change, guiding individuals through five key stages:

1. Awareness – Understanding the need for change.

2. Desire – Developing the motivation to support change.

3. Knowledge – Gaining the necessary skills and information.

4. Ability – Applying new behaviors or processes.

5. Reinforcement – Sustaining the change over time.

Meanwhile, Service Design focuses on user experiences and journeys, mapping out interactions to ensure seamless and meaningful engagements. The Customer Journey tool visualizes how different touchpoints affect emotions, behaviors, and decision-making processes.

By integrating these two approaches, The Change Journey allows organizations to design change initiatives that are not only strategically sound but also deeply aligned with the experiences and needs of those affected by the change.

What is "The Change Journey"?

The Change Journey is a visual and strategic mapping tool that connects the stages of ADKAR with service design elements such as touchpoints, pain points, and moments of truth. It helps organizations understand how people move through change, where they struggle, and what interventions can make transitions smoother.

Key Components of The Change Journey:

• Thoughts & Feelings – Understanding emotions, motivations, and concerns at each stage of change.

• Resistance – Identifying key points where resistance arises and addressing barriers to change.

• Opportunities – Finding ways to enhance engagement and leverage strengths to facilitate smoother transitions.

• Touchpoints – Mapping out interactions, communication channels.

• Actions to be Taken – Mapping the concrete steps needed to support change at that stage.

How to Implement The Change Journey in Real Life

If you want to successfully apply The Change Journey in a real change process, you need to run at least four 1/2-day workshops mapping the change process in this order:

1. Workshop with Employees – Gather a representative sample of employees who will be directly impacted by the change. Include a mix of new hires, long-term employees, and those in between to ensure diverse perspectives.

2. Workshop with Direct Managers – Engage the managers of these employees, as they will also be affected by the change. Present the employees' Change Journey and then map the managers’ own journey to understand their challenges and roles in the process.

3. Workshop with Secondary Stakeholders – Include suppliers, vendors, and third-party actors who will be influenced by the change. Mapping their journey helps uncover overlooked dependencies and friction points.

4. Workshop with Strategic Stakeholders and Change Sponsor – Present the previous Change Journeys and then map their own, focusing on how they will support employees, managers, and third parties throughout the transition.

After completing these workshops, use the insights to create a comprehensive change plan and implement it with a structured approach.

Benefits of Using The Change Journey

1. People-Centered Change – Instead of forcing change from the top down, this approach designs change with and for the people involved.

2. Better Adoption Rates – By addressing pain points proactively, employees and stakeholders are more likely to embrace change.

3. Clearer Communication – The journey map acts as a shared visual language, ensuring alignment between teams.

4. Stronger Long-Term Impact – Change efforts are reinforced through continuous feedback and iteration.

Applying The Change Journey in Practice

Whether you're leading a digital transformation, a cultural shift, or a new policy implementation, The Change Journey helps you:

• Map the current and desired states of your organization or service.

• Identify resistance points and opportunities to enhance engagement.

• Co-create solutions with the people experiencing the change.

• Test interventions before rolling them out at scale.

Conclusion

Change doesn’t have to be a struggle. By bringing together Change Management and Service Design, The Change Journey offers a more holistic, effective, and human-centered way to implement transformation.

Are you ready to rethink how you approach change? Let’s embark on this journey together!

PS) Exciting Changes Ahead at Facili-station!

Thank you for being part of this journey! From now in April, Facili-station's content will be available exclusively to paid subscribers. For just $100 per year—less than the cost of a couple of Starbucks coffees each month—you’ll not only access premium facilitation and innovation insights but also receive free coaching, mentoring, and be part of an exclusive professional community.

From now on I will publish one open post each month that will be accessible to all subscribers (like this one), both free and paid. In addition, I will share four exclusive posts every month, available only to my paid subscribers.

These exclusive posts will dive deeper into service design, innovation, facilitation techniques, and practical insights to help you grow as a facilitator. Paid subscribers will also enjoy added benefits like free coaching, mentoring, and access to a special social community.

Your support keeps this platform thriving, and I’d love for you to be part of this next chapter. Join us and continue growing with Facili-station!

— José Manuel Redondo Lopera

I hope this post, made sense and you found it useful.

If “HELL YEAH!”, please like it and share it in social media so more people can get can also benefit from it :-)

I would also appreciate if you subscribe, and give some comments here if you wonder something and want to give me some feedback. I would love to read your input here!

If you have a Substack yourself and like my content, I would love for you to recommend “Facili-station” to your subscribers.

Have a nice one!!

If you need a workshop designer and facilitator to help you or your team to solve challenges, find solutions, make decisions, and to be more effective an perform better and faster, or a trainer to teach your team on how do this, please contact me at jose@facilistation.com

My workshops are designed to provide the structure required to quickly align and move forward with a plan or idea so you can reclaim time, energy and headspace.

An agile coach is a professional who supports individuals, teams, and organizations in adopting and improving their agile practices.

Agile methodologies, such as Scrum, Kanban, and Lean, focus on iterative development, collaboration, and customer feedback to deliver value quickly and efficiently.

The role of an agile coach varies depending on the needs of the organization, but typically involves…

• Training and Education: Providing training sessions and workshops to help teams understand agile principles, practices, and frameworks.

• Coaching and Mentoring: Working closely with teams to guide them in applying agile principles effectively, addressing challenges, and improving their processes.

• Facilitation: Facilitating meetings, such as daily stand-ups, sprint planning, retrospectives, and other agile ceremonies, to ensure they are productive and aligned with agile principles.

• Change Management: Assisting with organizational change by fostering a culture of continuous improvement, encouraging experimentation, and promoting transparency and collaboration.

• Conflict Resolution: Helping teams navigate conflicts and overcome obstacles that may arise during the agile transformation process.

Agile coaches play a crucial role in helping organizations embrace agility, going through transformations and achieve their goals by empowering teams to deliver value iteratively and adapt to change effectively.

A dysfunctional team is characterized by several key traits that hinder its ability to work effectively and achieve goals.

Lack of trust

Team members are unwilling to be vulnerable with each other, leading to a lack of openness and honest communication. They might not share their ideas or concerns, fearing judgment or conflict.

Fear of conflict

Dysfunctional teams avoid healthy debate and discussions. They often suppress disagreements, which leads to unresolved issues and passive-aggressive behavior. When conflict does arise, it may be unproductive or personal.

Lack of commitment

Because of the absence of open dialogue and unresolved conflicts, team members may not fully commit to decisions or goals. This results in a lack of unity and focus on the team’s objectives.

Avoidance of accountability

Team members avoid holding each other accountable for their actions and performance. This might be due to fear of conflict or a lack of clarity about roles and responsibilities. As a result, poor performance or behavior often goes unchecked.

Inattention to results

In a dysfunctional team, individual goals and personal agendas often take precedence over the team’s collective goals. Members may be more concerned with their own success or recognition rather than the team’s success.

These traits can severely impair a team's performance, leading to low morale, high turnover, and failure to achieve objectives.

A change agent is someone who initiates, facilitates, or leads change within an organization, community, or society.

Change agents can operate at various levels within an organization, from top management to frontline employees. They play a crucial role in driving and implementing changes in processes, structures, behaviors, or strategies to achieve desired goals or outcomes.

Change agents typically possess strong leadership, communication, and interpersonal skills. They often need to navigate resistance, manage conflicts, and inspire others to embrace change. Additionally, they may need expertise in specific areas such as organizational development, project management, or change management methodologies.

Overall, change agents are catalysts for transformation, driving positive changes that improve efficiency, effectiveness, and adaptability in response to evolving circumstances or challenges.

A catalyst agent, typically referred to simply as a catalyst, originally is a substance that increases the rate of a chemical reaction without itself undergoing any permanent change in its own composition.

Catalysts function by providing an alternative pathway for the reaction to occur, lowering the activation energy required for the reaction to proceed. This allows the reaction to happen more quickly or under milder conditions than it would without the catalyst.

In the context of organizational change initiatives, a catalyst agent can be a person, group, or mechanism that accelerates or facilitates the process of change within an organization

Catalyst agents play a crucial role in initiating, guiding, and sustaining organizational change by mobilizing resources, overcoming resistance, and creating conditions conducive to successful transformation.

In today's rapidly evolving world, organizations face unprecedented levels of complexity and uncertainty. The ability to effectively navigate these challenges is crucial for survival and success.

The Cynefin framework, a decision-making model developed by Dave Snowden, offers a valuable tool for understanding and responding to different types of complexity. By providing a structured approach to categorizing and addressing various situations, the Cynefin framework empowers individuals and organizations to make informed and adaptive decisions based on the domain a problem falls into.

The framework divides problems into five domains:

1. CLEAR

   • In this domain, cause-and-effect relationships are straightforward and predictable. Best practices can be applied because there is little uncertainty.

   • Decision-Making Approach: Sense, Categorize, Respond

     • In clear situations, cause-and-effect relationships are obvious, and there is a known best practice to follow. The decision-making process involves recognizing the situation (sensing), categorizing it correctly, and applying a proven solution.

   • Appropriate for: Highly stable environments with little room for deviation.

   • Approach: Use best practices.

   • Example: Manufacturing processes, Standard operating procedures (SOPs), repetitive tasks.

2. COMPLICATED

   • There is a clear relationship between cause and effect, but it requires analysis or expertise to understand. There may be multiple solutions to a problem.

   • Decision-Making Approach: Sense, Analyze, Respond

     • Complicated situations have clear cause-and-effect relationships, but expertise is required to figure them out. The decision-making process involves sensing (gathering information), analyzing the situation (often requiring expert knowledge), and then responding with an appropriate solution.

   • Appropriate for: Problems where analysis and expertise are essential, but the solution is known once discovered.

   • Approach: Use good practices.

   • Example: A complex engineering project where multiple specialists need to work together to come up with a solution.

3. COMPLEX

   • Cause and effect can only be understood in retrospect. The situation is dynamic and evolving, and patterns emerge through experimentation.

   • Decision-Making Approach: Probe, Sense, Respond

     • In complex environments, cause and effect can only be seen in retrospect. The decision-making approach involves probing the system with small, safe-to-fail experiments to gather more information (probing), sensing the results to look for emerging patterns, and then responding based on those patterns.

   • Appropriate for: Unpredictable, dynamic environments where solutions emerge over time.

   • Approach: Use emergent practices.

   • Example: Unpredictable, dynamic environments where solutions emerge over time like organizational culture change, market disruptions, product & service development.

4. CHAOTIC

   • There is no clear relationship between cause and effect. The situation is highly unpredictable, requiring immediate action to stabilize it.

   • Decision-Making Approach: Act, Sense, Respond

     • In chaotic situations, immediate action is required to bring some level of stability. There’s no time to analyze or experiment, so the decision-making approach involves acting quickly (often decisively), then sensing whether the action had the desired effect, and responding accordingly.

   • Appropriate for: High-urgency, high-stakes environments where quick decisions are necessary.

   • Approach: Use novel practices.

   • Example: Crisis management, like during a natural disaster or cybersecurity breach, where immediate actions are required to regain control.

5. CONFUSION OR DISORDER

   • This is the state of not knowing which of the other domains a situation belongs to. Decision-makers are unsure how to categorize the situation.

   • Decision-Making Approach: Break into Domains

     • This is the state of not knowing which domain a situation belongs to. The decision-making approach here involves breaking down the situation into parts and figuring out which domain each part fits into. Once categorized, appropriate decision-making approaches can be applied to each part.

   • Appropriate for: Situations where it’s not immediately clear what type of problem you are dealing with.

   • Approach: Break the situation down and assign parts to one of the other four domains.

   • Example: Complex organizational challenges that include elements of chaos, complexity, and routine operations.

When to Use the Cynefin Framework:

• Complex environments: When dealing with unpredictable environments where the relationships between cause and effect are not immediately apparent (e.g., managing innovation or navigating uncertainty).

• Decision-making in organizations: To match leadership approaches to the nature of the problem and avoid applying overly simplistic solutions to complex issues.

• Problem-solving: When you need to clarify the nature of the problem first before applying the right tools to solve it.

How to Use It:

1. Understand the domain: Assess which domain your situation falls into.

2. Tailor your approach: Based on the domain, decide whether to apply best practices, rely on expert analysis, experiment, or take immediate action.

3. Reassess and adapt: Since situations can shift from one domain to another, constantly reassess the environment and adapt your approach as needed.

The Cynefin framework has emerged as a powerful tool for navigating complexity in a chaotic world. By providing a clear understanding of different decision-making contexts, the framework enables individuals and organizations to tailor their approaches to specific situations.

By recognizing the importance of sensemaking, experimentation, and adaptation, organizations can enhance their resilience, innovation, and overall effectiveness.

As the world continues to become increasingly complex and uncertain, the Cynefin framework offers a valuable guide for making informed and effective decisions.

A wicked problem is a complex issue that is difficult or impossible to solve because of incomplete, contradictory, or changing requirements. These problems are typically societal in nature and are characterized by their complexity and the interconnectedness of various factors involved.

Wicked problems often have no clear definition or endpoint, making it hard to determine when a solution is found or whether it even exists.

Some key characteristics of wicked problems include:

1. No definitive solution – Solutions are not right or wrong but better or worse, and stakeholders may disagree on what constitutes success.

2. No stopping rule – There's no definitive moment when the problem is "solved"; new solutions may always be possible.

3. Unique nature – Every wicked problem is essentially unique and cannot be solved in the same way as previous problems.

4. Interconnectedness – Solutions often have unintended consequences that can exacerbate the problem or create new issues.

5. Multiple stakeholders – Different groups have different perspectives and conflicting interests, making agreement on the problem and solution more difficult.

6. Complexity and uncertainty – Many factors contribute to the problem, and those factors often change over time, making the problem hard to pin down.

Examples of wicked problems include climate change, poverty, healthcare reform, and global inequality. Solutions to wicked problems often require collaboration across various sectors, and while a perfect solution may not exist, progress can be made by addressing parts of the problem.

Solving wicked problems is a complex task, and because of their nature, they can't be "solved" in the traditional sense. However, there are strategies that can be used to manage and improve wicked problems. Here are some approaches.

1. Engage Stakeholders in Dialogue and Collaboration

Wicked problems involve many stakeholders with differing perspectives and interests. It's crucial to bring together all affected parties to collaborate and create shared understanding. This can lead to more comprehensive and accepted approaches. Tools for engagement include:

• Public forums, workshops, and consultations to hear diverse voices.

• Co-design approaches where stakeholders participate in designing solutions together.

2. Define the Problem Iteratively

Wicked problems don't have clear definitions, so instead of trying to pinpoint a single problem definition, treat the definition process as iterative. As more information and perspectives are gathered, the understanding of the problem will evolve.

• Adaptive problem-framing allows solutions to shift as new data and insights arise.

3. Break the Problem Down into Manageable Parts

While the problem as a whole might seem overwhelming, it can often be addressed by breaking it down into smaller, more manageable components. While no single component solves the whole, addressing parts can lead to incremental improvements.

• Focus on specific, solvable aspects and work towards smaller victories that build momentum.

4. Adopt an Iterative, Adaptive Approach (Agile Problem-Solving)

Since there is no final solution to a wicked problem, an iterative approach—where solutions are continuously tested, adapted, and refined—can work better than a one-size-fits-all solution.

• Pilot programs or prototyping small-scale solutions, then scaling successful initiatives.

• Continually monitor and revise strategies based on outcomes and feedback.

5. Embrace Systems Thinking

Wicked problems are interconnected with other problems, so solutions require a holistic approach that considers the entire system. Systems thinking helps identify patterns, relationships, and leverage points within the system.

• Look for systemic causes rather than focusing only on symptoms.

• Map out relationships and feedback loops to understand potential ripple effects of any action.

6. Encourage Multi-Disciplinary and Cross-Sector Collaboration

Many wicked problems cut across different fields, so bringing in experts from diverse domains (economics, sociology, science, politics, etc.) ensures a more well-rounded approach.

• Establish cross-sector partnerships between governments, businesses, non-profits, and communities.

• Promote transdisciplinary research to combine insights from different areas of expertise.

7. Tolerate and Plan for Uncertainty

Accept that uncertainty is inherent to wicked problems. Planners must be willing to experiment and accept that not all initiatives will work as expected.

• Create flexible strategies that allow for mid-course corrections.

• Use scenario planning to consider multiple future outcomes and build resilience into solutions.

8. Avoid Perfect Solutions – Focus on Progress

Rather than seeking a complete and definitive solution, aim for progress. Small, incremental changes can reduce the problem's impact or prevent it from worsening.

• Iterate rapidly and continuously improve based on new insights and experiences.

• Use feedback loops to adjust and refine approaches.

9. Create Shared Accountability

Distribute responsibility across various actors rather than relying on one group or organization. Collective ownership increases the likelihood of sustained commitment and action.

• Collaborative governance models can ensure that all stakeholders have a role in addressing the problem.

10. Leverage Technology and Innovation

Innovative tools and technologies, such as artificial intelligence, data analytics, and new forms of communication, can provide fresh perspectives or enhance problem-solving capacity.

• Use big data and machine learning to track patterns, analyze causes, and predict potential outcomes of interventions.

11. Promote Public Awareness and Behavior Change

Some wicked problems, like climate change or public health crises, require shifts in behavior on a societal level. Public education and awareness campaigns can help mobilize people toward action.

• Media campaigns, educational programs, and grassroots efforts can raise awareness and inspire changes in behavior.

12. Focus on Equity and Inclusion

Wicked problems often disproportionately affect marginalized or vulnerable communities. Solutions must take equity into account and ensure that no group is left behind.

• Prioritize inclusive decision-making that empowers underrepresented communities.

• Target interventions that address the specific needs of those most affected.

13. Anticipate Unintended Consequences

Solutions to wicked problems often have ripple effects, creating new challenges. When designing interventions, consider potential unintended consequences and plan accordingly.

• Use scenario modeling to explore how different solutions might interact with other parts of the system.

Ultimately, tackling a wicked problem involves constant adaptation, collaboration, and learning. There’s no one-size-fits-all approach, but by addressing small parts of the problem, fostering dialogue, and embracing change, real progress can be made.

Change management and service design share a common foundation in understanding and addressing human needs, employing iterative processes, focus on improving organizational processes and experiences and ensuring effective communication and stakeholder engagement.

USER-CENTERED FOCUS

Both Change Management and Service Design emphasize the importance of understanding and addressing the needs and experiences of users (or employees, in the case of change management).

In Service Design, the focus is on creating or improving services that meet user needs.

In Change Management, it's about guiding people through change in a way that minimizes disruption and maximizes acceptance.

HOLISTIC PERSPECTIVE

Both disciplines require a broad view of the organization and its processes.

Service Design looks at the entire service ecosystem, considering all touch points and interactions. Similarly, Change Management considers the overall impact of change on the organization, including its culture, processes, and people.

ITERATIVE PROCESS

Both Change Management and Service Design rely on iterative processes.

Service Design often uses prototyping and testing to refine services before full implementation.

Change Management involves iterative feedback and adjustment to strategies based on how the change is being received and implemented.

CROSS-FUNCTIONAL COLLABORATION

Both fields require working across different departments and levels of an organization to achieve their goals.

FOCUS ON IMPROVING EXPERIENCES

Change Management aims to improve the employee experience during transitions, while Service Design focuses on enhancing the customer experience.

COMMUNICATION & TRAINING

Effective communication and training are critical in both fields.

In Service Design, clear communication ensures that users understand and can effectively use the service.

In Change Management, communication and training help employees understand the change, why it’s happening, and how to adapt to it.

STAKEHOLDER INVOLVEMENT

Both practices involve actively engaging stakeholders throughout the process.

Service Design involves co-creation with stakeholders to ensure the service meets their needs, while Change Management involves engaging stakeholders to build support for the change and ensure smooth implementation.

EMPATHY & EMOTIONAL INTELLIGENCE

Both fields require a deep understanding of human behavior and psychology.

In Service Design, this translates to creating services that resonate with users on an emotional level.

In Change Management, it involves understanding how change impacts people emotionally and finding ways to support them through the transition.

Developing an innovation culture and mindset in large companies requires a strategic approach that encourages creativity, risk-taking, and collaboration across all levels. Here are key steps to foster this:

Leadership Commitment

• Role model innovation: Leaders must visibly prioritize innovation, demonstrating openness to new ideas and encouraging others to do the same.

• Empower teams: Give teams the autonomy to experiment, make decisions, and learn from failures without fear of excessive repercussions.

Create a Safe Environment for Risk-Taking

• Encourage experimentation: Foster a mindset where failure is seen as part of the learning process. Recognize and reward employees who try new things, even if they don't succeed.

• Reduce fear of failure: Create systems that encourage low-cost experimentation and make it clear that calculated risks are part of the innovation process.

Encourage Cross-Functional Collaboration

• Break down silos: Facilitate collaboration across departments and functions. This leads to diverse perspectives and innovative solutions that may not emerge from isolated teams.

• Build diverse teams: Encourage diversity in thought, background, and experience to foster creative problem-solving.

Invest in Training and Development

• Offer innovation workshops: Teach employees creative thinking techniques, problem-solving methods, and how to approach challenges with a design-thinking mindset.

• Promote continuous learning: Make professional development a priority, with a focus on emerging trends, new technologies, and market shifts.

Implement Systems for Capturing Ideas

• Idea management platforms: Use technology to collect, evaluate, and implement ideas from across the organization. Open up channels for employees at all levels to contribute.

• Hackathons and innovation challenges: Organize internal competitions to generate new ideas and solutions for business challenges.

Celebrate and Reward Innovation

• Recognize innovators: Publicly celebrate teams or individuals who contribute innovative solutions, regardless of the final outcome. Offer rewards for creative thinking and experimentation.

• Monetary and non-monetary incentives: Offer tangible rewards for innovation, such as bonuses or career advancement, but also non-monetary rewards like additional development opportunities or flexible working arrangements.

Align Innovation with Company Goals

• Link innovation to strategy: Ensure that the push for innovation aligns with the company’s overall goals and vision. This helps focus efforts on areas that will drive business impact.

• Set clear expectations: Define what success in innovation looks like and communicate it across the organization to ensure employees know what to aim for.

Foster a Long-Term Innovation Mindset

• Adopt a long-term view: Innovation doesn’t happen overnight. Embed a culture of continuous improvement where the organization is always looking to evolve.

• Build partnerships and external collaborations: Encourage collaboration with startups, universities, or other industry leaders to bring in fresh ideas and new technologies.

By embedding these principles into the company’s DNA, large organizations can cultivate a culture where innovation thrives and becomes a core competitive advantage.

Do you wonder how to make it happen in your organization?

Let´s have a talk together so we can get to know each other so I might help and support you.

Let's talk

Other related articles:

Does your organization want to build an internal innovation culture and mindset, and maybe build an cost effective Innovation Program that creates actual results and is both sustainable and scalable?

Use then Design Sprints as a primary tool and build a Design Sprint program that will accelerate the transformation and build facilitation skills in an effective way, while introducing Design Sprints to the whole organization.

Design Sprints can be costly if they fail. It is therefore important to have good facilitators who plan, prepare and lead the team through the sprint. Not least the follow-up work after the sprint is important. All this falls under the responsibility of the facilitators.

What is a "Design Sprint Launchpad"

Many organizations want to build up facilitation skills so they can run Design Sprintes by themselves, and not using external consultants.

Facilitation is a performance sport that requires more than just theoretical knowledge. Facilitation is an executive role where the craft requires both inherent qualities and learned skills in group dynamics, presentation technique, leadership and improvisation. Practical experience and extensive training are therefore needed.

Good facilitators are essential for creating good team dynamics in a Design Sprint.

I therefore recommend a program to develop internal Design Sprints facilitators in the organization. I call this program “Design Sprint Launchpad”.

Through a series of real Design Sprints in your organization, future facilitators get involved and gradually take on more responsibility for planning, preparing, carrying out and summarizing Design Sprints.

Why a "Design Sprint Launchpad"

With the approach in the Design Sprint Launchpad, you kill several birds with one stone: the organization gets safely started with Design Sprints, you build real experience as facilitators and as an organization you build up a system, process and culture to build up and scale innovation facilitator competence internally.

Get started safely with Design Sprints.

It is important to succeed with the first sprints in an organization, so that there is room to carry out more sprints later. If you make a mistake, there is a danger that you will assume that it was due to the sprint form, and not the underlying reasons. It is therefore important to build some success stories at the start. Having experienced facilitators helps you ensure the best possible implementation and creates security for both participants and stakeholders.

Build real experience as facilitators.

Through the program, the future facilitators will build security and achieve a sense of mastery, which is very important for becoming confident in the role of facilitator. With ongoing feedback and coaching along the way from our experienced mentors, the learning outcomes will be raised considerably.

Scale competence.

With Launchpad, you also get a model that you can use to build and scale the facilitation skills in your organization.

How to do it

Step 1: Observation

In the first step, an experienced extern facilitator (like me) takes responsibility for facilitating a Design Sprint in your organization. He then takes two internal candidates (to-be future facilitators) who act as observers before, during and after the sprint. The candidate's job will be to observe and learn.

They are involved in all planning work and all activities that the mentor does. He starts and ends each day without the rest of the sprint team, so that the candidates get as much learning as possible from each individual day.

Step 2: Co-facilitation

In step 2, the candidates move up as co-facilitators. The mentor takes the leading role as facilitator, while the candidate takes the co-facilitator role. The candidate will then be executive facilitator for parts of the activities and otherwise support the main facilitator. Ahead of the sprint, mentor and co-facilitator will distribute tasks and responsibilities, and every day they will run a debrief with feedback.

In order to scale facilitation skills, two new internal candidates and observers can be brought in here. These are then at stage 1, and will move up as co-facilitators in the next round.

Step 3: Independently facilitate Design Sprints

In the third step, the candidates from step 1 become main facilitators and lead Design Sprints themselves independently. They will now have enough security, experience and knowledge to be able to implement these in a very good way.

In order to further scale facilitation skills, you can bring in two new observers and carry out the same training round as with the first four candidates.

Step 4: The way forward

The original experienced facilitator from step 1, joins as further support, and gets a new role as a innovation and facilitator coach for the new facilitators, and for the leadership group.

He also designs and facilitates workshops for Problem Definition and Problem Framing, which are critical for a successful Design Sprint.

Effective team development involves fostering collaboration, communication, and continuous improvement among team members.

Here’s a guide to working with team development.

Establish clear goals and roles

• Define objectives: Ensure everyone understands the team’s goals and the expected outcomes.

• Role clarity: Assign clear roles and responsibilities to each team member to avoid confusion and overlap.

Foster a positive team culture

• Inclusive environment: Promote an environment where all team members feel valued and included.

• Encourage innovation: Encourage team members to think creatively and bring new ideas to the table.

• Support work-life balance: Be mindful of workloads and respect personal time to prevent burnout.

Encourage open communication

• Regular meetings: Hold frequent meetings to discuss progress, challenges, and next steps.

• Use communication tools: Utilize tools like Slack, Microsoft Teams, or Zoom to facilitate communication, especially in remote or hybrid teams.

• Active listening: Encourage team members to listen to each other’s ideas and feedback.

Build trust and respect

• Lead by example: Show commitment, transparency, and integrity in your work and interactions.

• Respect diversity: Embrace the diverse perspectives and skills that each team member brings.

• Empower team members: Give team members the autonomy to make decisions in their areas of responsibility.

Manage conflict constructively

• Address issues early: Don’t let conflicts fester; address them promptly and constructively.

• Encourage healthy debate: Create a safe environment where team members can express differing opinions without fear of reprisal.

• Mediation: If necessary, mediate conflicts impartially to find a resolution that respects everyone’s viewpoints.

Celebrate successes

• Recognize achievements: Acknowledge both individual and team successes to keep morale high.

• Team celebrations: Organize team events or informal gatherings to build camaraderie and celebrate milestones.

Promote collaboration

• Pair programming / peer review: In development teams, practices like pair programming or peer code reviews can help share knowledge and improve code quality.

• Collaborative tools: Use platforms like GitHub or Bitbucket for version control, allowing team members to work together on the same codebase seamlessly.

• Shared goals: Foster a team environment where success is shared, and team members are encouraged to help one another.

Focus on continuous improvement

• Retrospectives: After each sprint or project phase, conduct retrospectives to identify what went well and areas for improvement.

• Training and development: Encourage continuous learning through workshops, courses, or knowledge-sharing sessions within the team.

• Feedback loops: Create mechanisms for continuous feedback, both formally (e.g., performance reviews) and informally.

Adapt to change

• Agile practices: Adopt Agile methodologies to stay flexible and responsive to changes in project requirements or team dynamics.

• Iterative development: Break down work into smaller, manageable chunks and iterate based on feedback and new information.

Leverage technology

• Project management tools: Use tools like Jira, Trello, or Asana to track progress and manage tasks.

• Automated testing / CI / CD: Implement automated testing and continuous integration / continuous deployment (CI/CD) to streamline development processes and reduce errors.

• Documentation: Maintain clear and updated documentation to ensure that knowledge is preserved and easily accessible.

By implementing these practices, you can effectively work with and develop a strong, cohesive, and productive team.

With an educational background as an Organizational Psychologist and MBA, I get steady asked by people that are new to people-centric innovation approaches (Design Thinking, Lean Startup, Service & Business Design) about articles that might help them to kickstart their knowledge and career on the topic.

I have gathered here the top 7 articles everybody should read in the right order.

Enjoy and let me know what you think and what you miss.

Creating psychological safety as a manager is crucial for fostering an environment where team members feel comfortable expressing themselves, taking risks, and sharing ideas without fear of negative consequences.

Here are some strategies to help you build psychological safety within your team.

Build trust

• Be consistent: Follow through on your commitments and be reliable in your actions. Consistency builds trust over time.

• Show empathy: Understand and acknowledge the feelings and concerns of your team members, and respond with compassion.

Encourage open communication

• Create opportunities for input: Involve your team in decision-making processes and actively solicit their opinions.

• Listen actively: Show genuine interest in what team members are saying. Paraphrase their points to confirm understanding, and ask clarifying questions to ensure you fully grasp their perspectives.

  

Model vulnerability

• Share your own mistakes: Be open about your own errors and what you’ve learned from them. This sets the tone that it’s okay to make mistakes and encourages others to do the same.

• Ask for feedback: Regularly seek feedback from your team, showing that you value their input and are willing to improve.

Regularly check-In

• Conduct one-on-one meetings: Use these meetings to check in on individual team members’ well-being and address any concerns they might have.

• Use pulse surveys: Periodically survey the team to gauge the overall sense of safety and make adjustments based on feedback.

Respond constructively to mistakes

• Focus on learning, not blaming: When mistakes happen, frame discussions around what can be learned rather than assigning blame.

• Celebrate lessons learned: Recognize and praise the team when they share lessons learned from failures, reinforcing that learning is a valued outcome.

Establish clear expectations

• Clarify roles and responsibilities: Make sure everyone understands their role and what is expected of them. This reduces uncertainty and anxiety.

• Set norms for respectful interaction: Establish and enforce norms around respectful communication and behavior.

Recognize and address issues promptly

• Don’t ignore problems: If issues related to psychological safety arise, address them immediately. Ignoring them can erode trust and safety.

• Facilitate conflict resolution: If conflicts occur, mediate in a way that restores safety and trust among team members.

Provide support

• Offer resources and assistance: Ensure your team has the tools, training, and support they need to succeed.

• Be available: Make yourself accessible to your team, showing that you’re there to support them when challenges arise.

Foster inclusivity

• Value diverse perspectives: Encourage input from all team members, particularly those who might be quieter or less confident in sharing their views.

• Create an equitable environment: Ensure everyone has equal opportunities to speak in meetings and contribute to discussions.

Encourage risk-taking and innovation

• Create a safe space for experimentation: Allow your team to try new approaches without the fear of harsh consequences if things don’t work out.

• Reward innovative thinking: Recognize and reward efforts to innovate, even if they don’t lead to immediate success.

By applying these strategies, you can cultivate an environment where your team feels psychologically safe, leading to increased engagement, creativity, and overall performance.

The cooperation between Service Designers (desirability), Product Managers (feasibility), and Business Developers (viability) is a dynamic and iterative process.

It ensures that the final product or service not only meets user needs but also achieves business objectives, leading to a successful market fit.

The service designer brings the user perspective, the product manager balances this with product strategy, and the business developer ensures alignment with broader business goals and market opportunities.

USER RESEARCH AND INSIGHTS

The service designer leads user research efforts, but the product manager and business developer provide input on what user segments are most valuable from a business perspective.

Together, they ensure that the insights gathered are actionable and align with both user needs and business goals.

PRODUCT AND SERVICE VISION

The product manager sets the product vision, which is informed by the service designer’s understanding of user needs and the business developer’s market insights.

The service designer helps visualize how this vision can be implemented through the user journey, while the business developer ensures it aligns with potential business opportunities.

FEATURE PRIORITIZATION AND ROADMAPPING

The product manager, in collaboration with the service designer, prioritizes features based on user value and business impact.

The business developer may weigh in to ensure that features that open up new markets or revenue streams are given appropriate consideration.

PROTOTYPING AND TESTING

The service designer typically leads the prototyping and testing phases, but works closely with the product manager to ensure that the prototypes align with the product strategy.

Business developers may use these prototypes to validate assumptions with potential partners or in new markets.

GO-TO-MARKET STRATEGY

The product manager and business developer collaborate on the go-to-market strategy, ensuring that the product launch is aligned with both user needs (as informed by the service designer) and business opportunities.

Service designers might ensure that marketing and support channels provide a consistent and positive user experience.

A retrospective, often referred to as a sprint retrospective in Scrum, is a meeting held at the end of each iteration (sprint) in agile methodologies. Its purpose is to reflect on the recent work done by the team, identify areas for improvement, and make actionable plans for implementing those improvements in future iterations.

Key aspects of a retrospective include:

1. Reflection: The retrospective provides a dedicated time for the team to reflect on the previous iteration. This includes discussing what went well, what didn't go well, and any surprises or unexpected events that occurred.

2. Continuous improvement: The primary goal of the retrospective is to identify opportunities for improvement and make concrete plans to address them. This could involve changes to processes, tools, communication methods, or team dynamics.

3. Safe environment: Retrospectives are conducted in a safe and blame-free environment where team members can openly share their thoughts and feelings without fear of judgment. This encourages honest and constructive feedback, which is essential for effective improvement.

4. Actionable outcomes: The retrospective should result in actionable outcomes that the team can implement in the next iteration. This might include specific tasks or experiments aimed at addressing identified issues or improving team effectiveness.

5. Facilitation: A facilitator, often the Scrum Master or another team member, guides the retrospective process to ensure that it stays focused, productive, and respectful. The facilitator helps keep the discussion on track, encourages participation from all team members, and ensures that actionable outcomes are identified.

The retrospective is a vital practice in agile methodologies because it promotes a culture of continuous improvement. By regularly reflecting on their work and making iterative adjustments, teams can become more effective, efficient, and resilient over time.

Agile leadership is a management approach that focuses on fostering a flexible, collaborative, and adaptive environment within an organization. It emphasizes principles derived from Agile methodologies, commonly used in software development but applicable to a wide range of industries and contexts.

Key aspects of agile leadership include:

Adaptability

Agile leaders embrace change and uncertainty, enabling their teams to pivot quickly in response to new information, market conditions, or unexpected challenges.

Collaboration

They foster a culture of teamwork and open communication, encouraging collaboration across all levels of the organization to leverage diverse perspectives and expertise.

Empowerment

Agile leaders empower their teams by delegating authority, trusting their team members to make decisions, and providing the necessary support and resources.

Customer Focus and Value Creation

They prioritize delivering value to customers, ensuring that the team's efforts are aligned with customer needs and feedback.

Continuous Improvement

Agile leaders advocate for ongoing learning and improvement, promoting iterative processes and the regular assessment of practices, products, and outcomes.

Servant Leadership

They practice servant leadership, putting the needs of their team members first, helping them grow and perform to the best of their abilities.

Transparency

Agile leaders ensure transparency in decision-making processes, goals, and feedback to build trust and accountability within the team.

By embodying these principles, agile leaders aim to create a dynamic and resilient organizational culture that can thrive in an ever-changing business environment.

The agile mindset is a set of values, principles, and beliefs that guide individuals and teams in their approach to work, problem-solving, and collaboration. It emphasizes adaptability, flexibility, transparency, collaboration, and a focus on delivering value to customers. Key aspects of the agile mindset include…

Customer-centricity

Agile emphasizes the importance of understanding and prioritizing customer needs and delivering value to customers early and continuously. Teams focus on building products and solutions that address real customer problems and deliver tangible benefits.

Iterative and incremental approach

Agile encourages an iterative and incremental approach to work (MVP), where solutions are developed and delivered incrementally in small, manageable increments. This allows for faster feedback, reduces risk, and enables teams to adapt to changing requirements and circumstances more easily.

Continuous improvement

Agile promotes a culture of continuous learning and improvement, where teams regularly reflect on their processes, practices, and outcomes and look for opportunities to make iterative improvements. This includes practices like retrospectives, where teams reflect on their performance and identify areas for improvement.

Collaboration and teamwork

Agile emphasizes the importance of collaboration and teamwork, both within and across functional teams. Teams work closely together, share knowledge and expertise, and collaborate to solve problems and deliver value. This includes practices like daily stand-up meetings, where teams synchronize their work and identify any obstacles or dependencies.

Adaptability and flexibility

Agile values adaptability and flexibility in response to changing requirements, priorities, and circumstances. Teams embrace change as a natural part of the development process and are willing to adjust their plans, priorities, and approaches as needed to deliver value effectively.

Transparency and openness

Agile promotes transparency and openness in communication and decision-making, both within teams and with stakeholders. Teams openly share information about their progress, challenges, and decisions, enabling better collaboration, trust, and alignment.

The agile mindset is about embracing a set of values and principles that prioritize customer value, collaboration, flexibility, and continuous improvement.

It provides a foundation for agile methodologies like Scrum, Kanban, and Lean, enabling teams and organizations to deliver high-quality products and solutions more effectively and efficiently.