Tag Archives: agile

Introduction to Agile: Principles and Practices

GUEST POST from Chateau G Pato

What is Agile?

Agile is not just a methodology, but a holistic approach to project management and software development. It emphasizes flexibility, collaboration, and rapid iteration. The core of Agile lies in its set of principles and practices designed to advance productivity and responsiveness to changing customer needs.

The Core Principles of Agile

Customer Satisfaction through Early and Continuous Delivery: Deliver valuable software frequently, with a preference for shorter timescales.
Welcome Changing Requirements: Even late in the development process, Agile processes harness change for the customer’s competitive advantage.
Deliver Working Software Frequently: Prefer shorter timescales from a couple of weeks to a couple of months.
Collaborate Daily with Business People and Developers: Ensure a close, daily cooperation between business stakeholders and developers.
Build Projects around Motivated Individuals: Provide support and trust to the team, allowing them to get the job done.
Face-to-Face Conversation: The most efficient method of conveying information to and within a development team is direct communication.
Working Software is the Primary Measure of Progress: Focus on functional software to gauge how well the project is advancing.
Maintain a Sustainable Pace: Agile processes promote sustainable development — the team should maintain a constant pace indefinitely.
Continuous Attention to Technical Excellence: Enhances agility by focusing on good design and technical details.
Simplicity is Essential: Maximize the amount of work not done, which is important.
Self-Organizing Teams: The best architectures, requirements, and designs emerge from self-organizing teams.
Regular Reflection and Adjustment: Periodically, the team reflects on how to become more effective and adjusts their behavior accordingly.

Case Study 1: Pixar’s Agile Film Making

Many might be familiar with Agile in software development, but Pixar, a leading animation studio, has effectively applied Agile principles in film making. Pixar’s process is not linear. Instead, they iterate on pieces of the film, from storyboarding to final animation, with constant feedback loops.

One key Agile principle Pixar uses is “early and continuous delivery of valuable increments.” This is evident where they focus on delivering short, rough sequences of the film for team and stakeholder review. These rough animations, or ‘reels,’ are iterated upon until the final movie emerges. Pixar also promotes a culture where it’s safe to fail early, as their focus is on rapid prototyping and feedback cycles.

Case Study 2: Spotify and Agile Scaling

Spotify, the global music streaming service, provides a stunning showcase of scaling Agile. Instead of traditional teams, Spotify uses “squads” — small, cross-functional, and self-organizing teams. Each squad operates much like a mini-startup, with accountability for a particular aspect of the service.

Spotify has scaled Agile by structuring squads into Tribes, which work on related areas of the service, allowing for collaboration and alignment. Governance is decentralized, and autonomy is high, which aligns with the Agile principle of self-organizing teams. Another critical aspect is Spotify’s use of “guilds” — groups of individuals with shared interests spanning across different squads, facilitating knowledge sharing and continuous improvement across the organization.

Agile Practices to Implement

Below are several Agile practices to consider implementing in your organization:

User Stories: Captures requirements from the perspective of the end-user.
Sprint Planning: Prioritize and plan work in time-boxed iterations.
Daily Stand-ups: Short, focused meetings to synchronize the team and address obstacles.
Sprint Reviews: Demonstrate and inspect the product after each iteration.
Retrospectives: Reflect on the process to identify improvements.
Kanban Boards: Visualize workflow and limit work in progress to optimize efficiency.

Conclusion

The adoption of Agile introduces a paradigm shift in how teams approach project management and execution. By embracing its principles and practices, organizations can enhance flexibility, foster innovation, and better respond to evolving customer needs. The case studies of Pixar and Spotify illustrate the versatile application of Agile across different domains, highlighting its potential to drive success whether in film making or global software services.

SPECIAL BONUS: The very best change planners use a visual, collaborative approach to create their deliverables. A methodology and tools like those in Change Planning Toolkit™ can empower anyone to become great change planners themselves.

Image credit: Pixabay

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Building Resilient Organizations

Leave a reply

Strategies for Designing Agile and Resilient Organizations that can Effectively Navigate Industry Disruptions

Building Resilient Organizations

GUEST POST from Chateau G Pato

In today’s fast-paced and ever-evolving business landscape, organizations face continuous disruptions that challenge their ability to remain competitive and thrive. To navigate these disruptions successfully, organizations must prioritize resilience and agility. By designing resilient organizations that can adapt and respond effectively, leaders can better position their businesses to weather industry disruptions and emerge stronger. In this article, we will explore strategies that can help build agile and resilient organizations, showcasing two compelling case studies that demonstrate their practical application.

1. Embracing a Culture of Adaptability:

A resilient organization begins with a resilient culture. Companies that foster a mindset of adaptability and continuous learning are better equipped to navigate industry disruptions. Organizations must first assess their current culture and identify areas in need of improvement. By encouraging innovation, risk-taking, and employee empowerment, businesses can build an environment that promotes flexibility and agility.

Case Study 1: Netflix

Netflix, originally a DVD rental service, recognized the shift in consumer behavior towards streaming services. Instead of resisting the change, Netflix embraced the disruption by evolving into a leading provider of online content. By prioritizing adaptability and empowering employees to experiment and take risks, Netflix capitalized on the opportunity to transform its business model, ultimately becoming one of the most influential disruptors in the entertainment industry.

2. Developing Robust Strategic Planning:

Strategic planning is essential for building resilient organizations. Effective planning allows businesses to anticipate disruptions, make proactive decisions, and quickly adapt to market shifts. Organizations must be willing to challenge conventional thinking, explore alternative scenarios, and foster an environment that supports experimentation.

Case Study 2: Amazon

Amazon’s journey from an online bookstore to a global retail giant serves as a testament to the company’s strategic planning capabilities. Amazon consistently invests in innovation, technology, and supply chain optimization to maintain a competitive edge. By staying ahead of industry disruptions, Amazon successfully integrated new business models like marketplace platforms and cloud computing, ensuring long-term sustainability.

3. Building Collaborative Networks:

In an increasingly interconnected business world, organizations cannot thrive in isolation. Resilient organizations actively cultivate partnerships, collaborations, and networks that allow them to leverage shared knowledge, resources, and expertise. Building strong relationships with suppliers, customers, and industry players fosters resilience by enhancing access to valuable information and enabling collaboration during times of disruption.

Conclusion

Building resilient organizations is vital to navigating industry disruptions successfully. By embracing a culture of adaptability, establishing robust strategic planning processes, and cultivating collaborative networks, businesses can enhance their resilience and fortify their ability to thrive amid uncertainty. The case studies of Netflix and Amazon exemplify these strategies’ effectiveness, showcasing how organizations that prioritize agility and resilience can not only survive but also lead industry disruptions. By leveraging these approaches, organizations can position themselves as catalysts for positive change and build a future-ready business ecosystem.

Image credit: Pixabay

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Change Leadership for Agile Organizations

1 Reply

Adapting to Rapid Change

GUEST POST from Art Inteligencia

In today’s complex and unpredictable business landscape, change has become a constant rather than an exception. Agile organizations that embrace change and adapt rapidly are more likely to succeed in an increasingly dynamic marketplace. However, achieving agility requires effective change leadership that empowers employees, aligns organizational values, and ensures seamless transitions. In this thought leadership article, we will explore the principles of change leadership for agile organizations through the analysis of two compelling case studies.

Case Study 1: Spotify’s Agile Transformation

In recent years, Spotify, the global music streaming giant, underwent a profound transformation to embrace agile practices and foster a culture of innovation. Their shift from a traditional hierarchical structure to a “tribe-squad-CT” model empowered autonomous cross-functional teams. Top management encouraged experimentation, where squads were free to take calculated risks and learn from failures. This cultural shift required strong change leadership that aligned the organization and inspired employees to embrace change.

Spotify’s change leaders focused on three core aspects:

1. Communicating a Compelling Vision: Leaders articulated a compelling vision that emphasized the need for agility and explained how it aligned with the organization’s strategic goals. They emphasized the benefits of empowerment, collaboration, and adaptability, ensuring that employees felt a sense of purpose and understood the value of change.

2. Nurturing Change Agents: Change leaders identified, trained, and empowered change agents within the organization. These agents served as advocates, mentors, and facilitators of change, supporting their respective teams through the transition. By creating a network of change agents, Spotify established a grassroots movement that accelerated the adoption of agile principles and practices.

3. Encouraging Continuous Learning: Recognizing that agility requires continuous learning, Spotify’s change leaders established a learning-oriented culture. They encouraged employees to embrace experimentation, learn from failures, and share their experiences. This created an environment that fostered innovation, collaboration, and rapid adaptation to change.

The successful transformation of Spotify showcases the effectiveness of change leadership in enabling organizational agility.

Case Study 2: Toyota’s Lean Manufacturing Revolution

Toyota’s journey towards becoming a global leader in automotive manufacturing is a testament to the power of change leadership in fostering agility. In the 1950s, Toyota faced significant challenges, including a resource-constrained post-war economy. They responded by developing the groundbreaking Toyota Production System (TPS), which revolutionized manufacturing processes and established the foundation for lean manufacturing.

Toyota’s change leadership approach encompassed the following elements:

1. Empowering Frontline Employees: Change leaders at Toyota recognized the value of frontline employees’ expertise. They empowered workers to identify and solve problems, emphasizing the importance of continuous improvement. This empowered culture fostered a sense of ownership, creating an environment where employees actively contributed to adapting to rapid changes and driving innovation.

2. Embracing Kaizen: Toyota’s change leaders popularized the Kaizen philosophy of continual improvement throughout the organization. They facilitated cross-functional collaboration and encouraged employees to seek incremental improvements in their work processes. This focus on Kaizen nurtured a culture of proactive responsiveness to change, benefitting not only the production line but the entire organization.

3. Leadership through Servant Mentality: Toyota’s change leaders assumed a servant leadership mentality, seeking to serve and support employees rather than commanding them. Leaders actively listened to the concerns and ideas of employees and provided the necessary resources and guidance to implement change.

By implementing these change leadership principles, Toyota transformed into an agile organization capable of rapidly adapting to shifting consumer demands and market conditions.

Conclusion

Change leadership is the catalyst for agility in organizations navigating rapid change. The case studies of Spotify and Toyota demonstrate how effective change leadership enables organizational adaptability, fosters a culture of innovation, and empowers employees to embrace and drive change. By communicating a compelling vision, nurturing change agents, encouraging continuous learning, empowering frontline employees, embracing Kaizen, and practicing servant leadership, organizations can pave the way for successful transformations in an increasingly volatile business environment. Embracing change leadership is the key to thriving in the face of rapid change.

Bottom line: Futurology is not fortune telling. Futurists use a scientific approach to create their deliverables, but a methodology and tools like those in FutureHacking™ can empower anyone to engage in futurology themselves.

Image credit: Pixabay

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Designing an Innovation Lab: A Step-by-Step Guide

1 Reply

Designing an Innovation Lab: A Step-by-Step Guide

GUEST POST from Art Inteligencia

Innovation has become a driving force for organizations looking to adapt and thrive in an ever-changing business landscape. To foster a culture of creativity and problem-solving, many companies are now investing in innovation labs. These dedicated spaces provide employees with the tools, processes, and environment necessary to drive impactful change. This article aims to present a step-by-step guide on designing an innovation lab, exploring key considerations and showcasing two inspiring case studies.

Step 1: Defining the Purpose and Objectives

Before embarking on the design process, it is crucial to define the purpose and objectives of the innovation lab. Is it primarily focused on developing new products, enhancing customer experience, or addressing internal efficiency challenges? Identifying the intended outcomes will help shape the lab’s design, resources, and methodologies.

Step 2: Creating the Right Environment

A successful innovation lab requires a physical and cultural environment that encourages collaboration, risk-taking, and creativity. This includes considerations such as open floor plans, flexible workspaces, comfortable furniture, and access to cutting-edge technology. Attracting natural light and incorporating natural elements can also enhance productivity and well-being.

Case Study 1: Google X Moonshot Factory

One of the most renowned innovation labs is Google X, the parent company of Google. The Moonshot Factory, as they call it, is responsible for developing radical, moonshot ideas that address global issues. The lab’s unique design features open spaces, colorful furniture, brainstorming walls, and prototypes scattered throughout the area. This innovative approach creates an atmosphere that fosters creativity, experimentation, and a sense of purpose, enabling teams to tackle audacious challenges with confidence.

Step 3: Promote Cross-Pollination and Collaboration

To maximize the potential of an innovation lab, it is essential to encourage cross-pollination of ideas and collaboration among employees from various departments. By integrating diverse perspectives and expertise, organizations can foster a more holistic and inclusive approach to problem-solving. Setting up common areas, organizing regular ideation sessions, and facilitating knowledge-sharing opportunities all contribute to a vibrant collaborative culture.

Case Study 2: Autodesk’s Pier 9 Workshop

Autodesk’s Pier 9 Workshop in San Francisco serves as an innovation lab that brings together artists, designers, and engineers to explore the intersection of technology and creativity. The lab provides users with cutting-edge equipment and a platform to experiment and create innovative projects. By fostering collaboration between diverse disciplines and offering access to advanced tools, Autodesk empowers individuals to push their boundaries and unleash their creative potential.

Step 4: Implement Agile Processes and Iterative Techniques

To drive innovation effectively, organizations should embrace agile processes that allow for rapid experimentation, continuous improvement, and quick iteration cycles. Encouraging teams to adopt proven methodologies like Design Thinking or Lean Startup principles helps create a structure that balances creativity with tangible results. Emphasizing the importance of learning from failure and celebrating successes also fosters a growth mindset within the lab.

Conclusion

Designing and implementing an innovation lab requires a strategic approach with careful consideration of the purpose, environment, collaboration, and iterative processes. By following this step-by-step guide, organizations can establish a dedicated space that cultivates creativity, engagement, and breakthrough innovations. The case studies of Google X Moonshot Factory and Autodesk’s Pier 9 Workshop serve as inspiring examples of successful innovation labs that have revolutionized industries by embracing the power of human imagination and collaboration. The future belongs to those who dare to innovate, and an innovation lab is the gateway to unlocking boundless possibilities.

Image credit: Unsplash

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Rise of the Evangelist

3 Replies

by Braden Kelley

What is an evangelist?

When many people hear this term, their minds used to picture Billy Graham or Pat Robertson, but this is changing. Why?

Our perceptions of evangelists are transforming as the pace of change accelerates to construct a new reality faster than most human brains can process the changes.

This creates a chasm in understanding and change readiness that evangelists can help bridge in a number of different ways.

Let us look at what an evangelist really is…

Oxford Dictionaries say an evangelist is a “zealous advocate of something.”

In business, the evangelist is a role that any of us can take on (with varying levels of success). Evangelism is very important to innovation success, which is why the evangelist is one of The Nine Innovation Roles™. This is how I define this particular role:

“The Evangelists know how to educate people on what the idea is and help them understand it. Evangelists are great people to help build support for an idea internally, and also to help educate customers on its value.”

Notice at this point we are talking about an evangelist as a role that can be played by one or more people, and not as a job that one or more people hold. Evangelism normally will be a role and not a job, but there are inflection points where this must change.

Outside of an innovation context, evangelism often falls on the shoulders of CEOs, business owners and product managers within organizations. When the need for evangelism is small, this can work. But for most organizations, this is no longer the case.

When should you hire an evangelist?

The time to cross over from evangelism as a role to evangelism as a job is when:

The pace of internal change is accelerating faster than employees can grasp without help
The pace of external change is accelerating faster than customers can understand without help
Your company is facing disruption by new entrants or existing competitors
You’re considering a digital transformation
You’ve already embarked upon a digital transformation
You’re using Agile in product development
Your brand essence is being shifted by you or your customers
You need a more human and personal presence in your marketing efforts to better connect with customers

When one or more of these conditions are true, you’ll find that it isn’t possible for CEOs, business owners and product owners to meet the needs for evangelism in the short spurts of time these people can dedicate to the necessary activities.

As highlighted by Agile Product Development’s presence in the list, organizations leveraging Agile to develop software-based products will find that their product managers are always engaged with the backlog with little time to focus on evangelism. They’re always focused on shipping something.

Some organizations will resist adding evangelists to their team, feeling that such a role is superfluous, but having one or more people focused on evangelism delivers value to the organization by executing a range of incredibly important activities, including:

Growing awareness

Building a community around the company and/or plugging the company into pre-existing external communities (potentially taking the brand to places it has never been before)

Generating interest

Working with customers and the marketing team to identify the stories that need to be told and the themes that need to be introduced and/or reinforced

Creating desire

Building and maintaining conversations with the community that cares about your products/services/brands

Engaging in an open and honest dialogue to help gather the voice of the customer

Facilitating action

Practicing a human-centered design mindset to continuously elicit needs and surface wants and desired outcomes

Depending on the size of the organization you may decide to have a single evangelist, or some larger organizations have more than one type of evangelist, including:

Chief Evangelist
Brand Evangelists
Product Evangelists
Service Evangelists
Innovation Evangelists

This specialization occurs when the evangelism an organization needs become too big for one evangelist to handle. At that point a Chief Evangelist creates the evangelism strategy and manages the execution across the team of brand, product, service and other evangelism focus areas.

So what makes a good evangelist?

Evangelists arrive from a range of different job specialties, but key knowledge, skills and abilities include:

Empathetic
Passionate About the Company’s Mission, Products/Services, and Customers
Comfortable Public Speaker
Efficient and Effective Writer
Human-Centered Design Mindset
Experienced with Social Media, Audio and Video
Skilled Content Creator
Continuous Learner
Self-Directed and Comfortable with Ambiguity

… and ideally your chosen evangelists will already have some presence in the communities important to you, or the knowledge of how to establish a presence in these communities.

Customer buying journeys are notoriously unpredictable, meandering, long and non-linear. Evangelism is a critical part of helping to build relationships with potential buyers and increasing the chances that your brand will be top of mind when a non-buyer finally becomes a potential customer of your products or services.

It’s a long-term non-transactional investment, one that will pay dividends if you see the wisdom in making the expenditure.

Has your organization already invested in evangelists? What learnings would you like to share in the comments?

Are you ready for the evangelists to rise in your organization?

Or do you need help with evangelism? (contact me if you do)

Share the love!

p.s. I wrote a follow-up article for InnovationManagement.se that you might also enjoy — Increase Your Innovation Reputation and Velocity with an Innovation Evangelist

Accelerate your change and transformation success

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

The Evolution of Change Management

Leave a reply

From Top-Down to Agile Approaches

The Evolution of Change Management

GUEST POST from Chateau G Pato

Change is an inevitable part of any organization’s growth and survival. In the past, change management strategies primarily followed a top-down approach, where leaders dictated the changes and employees were expected to comply. However, over time, as organizations faced increasing complexity and speed of change, a more agile approach to change management has emerged. This article explores the evolution of change management from top-down to agile approaches and provides two case study examples showcasing the benefits of adopting agile change practices.

The traditional top-down approach to change management involved leaders identifying the need for change, setting objectives, and then cascading the change down through the hierarchy. In this approach, employees were often not adequately involved or consulted, leading to resistance or low engagement. The lack of employee involvement also hampered creativity and innovation, with change initiatives frequently facing roadblocks and slow implementation.

Recognizing the limitations of the top-down approach, organizations began embracing agile change management methodologies, inspired by the principles derived from agile software development. The agile approach emphasizes collaboration, flexibility, and iterative progress, empowering employees to actively participate in the change process. This shift enables organizations to respond swiftly to changing circumstances and capitalize on emerging opportunities.

Case Study 1 – Spotify

One notable case study that highlights the effectiveness of an agile change approach is the transformation of Spotify. This music streaming giant faced the challenge of scaling rapidly while maintaining innovation and adaptability. They shifted from a traditional top-down approach to a squad-based, agile organizational structure. In their agile change management, cross-functional teams were empowered to make decisions, experiment, and continuously improve. This resulted in faster implementation of ideas, increased employee satisfaction, and enhanced customer experiences.

Case Study 2 – Dutch Government

Another case study illustrating the benefits of agile change practices is the digital transformation of the Dutch government. Facing the need to modernize and improve service delivery, they adopted an agile approach to change management. Using this methodology, they formed multidisciplinary teams responsible for specific projects, involving end-users throughout the development process. By conducting frequent iterations and incorporating feedback, the Dutch government successfully rolled out digital initiatives such as the Digital Identity App and the My Belastingdienst portal. The agile change approach ensured that the final products met users’ needs and expectations, leading to improved citizen engagement and satisfaction.

The shift from top-down to agile change management approaches is driven by the understanding that employees are key stakeholders and vital sources of expertise and innovation. By involving employees throughout the change process, organizations can tap into their knowledge, unlock creativity, and improve the quality and sustainability of change initiatives. This collaborative approach results in higher levels of ownership, engagement, and commitment from employees, fostering a culture of continuous learning and adaptation.

Conclusion

The evolution of change management from top-down to agile approaches represents a paradigm shift in how organizations navigate and embrace change. The agile approach, with its emphasis on collaboration, flexibility, and employee involvement, enables organizations to adapt swiftly in an ever-changing environment. Case studies such as Spotify and the Dutch Government’s digital transformation illustrate the positive outcomes of adopting agile change practices. Embracing agile change management not only accelerates the implementation of changes but also nurtures a culture of innovation, empowerment, and resilience in organizations.

Image credit: Pexels

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Human-Centered Design and Agile Methodologies

Leave a reply

A Powerful Combination

Human-Centered Design and Agile Methodologies

GUEST POST from Chateau G Pato

In today’s fast-paced and competitive market, organizations are increasingly realizing the importance of incorporating both Human-Centered Design (HCD) principles and Agile methodologies into their product development processes. By doing so, companies are able to create innovative and user-centric products while staying agile and responding swiftly to changing customer needs.

Human-Centered Design is an iterative design approach that focuses on understanding and meeting the needs, desires, and behaviors of end-users. It involves continuously involving users throughout the design process, gaining insights through user research, and incorporating their feedback to build products that truly address their pain points. On the other hand, Agile methodologies emphasize flexibility, collaboration, and adaptive planning, enabling teams to iteratively deliver value through frequent and incremental product releases.

When combining HCD with Agile, organizations can leverage the strengths of both methodologies and achieve remarkable results. Let’s explore two case studies that highlight the power of this combination.

Case Study 1: Airbnb

One of the most prominent examples of successful integration of HCD and Agile methodologies is Airbnb. In its early years, Airbnb faced the challenge of low user engagement and failed to attract users to their platform. Recognizing the importance of putting users at the center of their design strategy, Airbnb embraced HCD principles alongside an Agile development approach.

Airbnb extensively researched the needs and preferences of its target audience, even going as far as sending its designers to live with hosts in different cities to truly understand the user experience. The insights gained from these immersive research experiences helped Airbnb identify pain points and develop innovative features that addressed them effectively.

By integrating Agile methodologies, Airbnb was able to quickly implement and test its design ideas, gaining rapid feedback from users. They released regular updates and constantly improved their app based on user feedback, ensuring that the product remained user-centric. Today, Airbnb is a global leader in the accommodation industry, revolutionizing the way people experience travel.

Case Study 2: Intuit

Intuit, a leading financial software company, is another example of successfully combining HCD and Agile methodologies in their product development process. Intuit’s flagship product, TurboTax, enables users to file taxes easily and efficiently. However, in observance of a common challenge faced by many organizations, Intuit realized that users often dropped out during the tax filing process due to its complexity.

To address this issue, Intuit adopted an HCD approach. They conducted extensive user research, including in-depth interviews and usability testing, to understand the pain points hindering user adoption. Based on these insights, Intuit redesigned their tax filing process to be simpler, more intuitive, and less time-consuming.

Intuit complemented their HCD efforts with an Agile development methodology. By releasing regular updates and engaging with users throughout the development process, Intuit ensured that the changes made aligned with user needs. The incremental approach allowed them to constantly improve the product and significantly reduce customer drop-offs during tax filing.

The integration of HCD and Agile methods played a crucial role in the success of TurboTax, making it the most popular tax preparation software in the market today.

Conclusion

The combination of Human-Centered Design and Agile methodologies has proven to be a powerful tool for organizations seeking to create user-centric and innovative products. The case studies of Airbnb and Intuit demonstrate how this integration can lead to significant improvements in user experiences and overall business success. By prioritizing user needs and leveraging feedback through an iterative and adaptive approach, companies can adapt to changing market requirements while delivering products that make a lasting impact.

EDITOR’S NOTE: Braden Kelley’s Problem Finding Canvas can be a super useful starting point for doing design thinking or human-centered design.

“The Problem Finding Canvas should help you investigate a handful of areas to explore, choose the one most important to you, extract all of the potential challenges and opportunities and choose one to prioritize.”

Image credit: misterinnovation.com

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

The Benefits of Agile Project Management for SMEs

Leave a reply

The Benefits of Agile Project Management for SMEs

GUEST POST from Art Inteligencia

The rapid pace of technological advancement and the increased competition in the business landscape have made project management a critical factor in the success of any organization. Small and medium-sized enterprises (SMEs) are no exception, and the implementation of agile project management can provide numerous benefits that can help them stay ahead of the competition.

Agile project management is a methodology that emphasizes flexibility and iterative progress, allowing teams to adapt quickly to changing conditions and customer needs. This type of project management has become increasingly popular in the business world and is a great option for SMEs looking to improve their project management capabilities. Here are five key benefits of agile project management for SMEs.

1. Improved Efficiency

Agile project management allows teams to break down large tasks into smaller, more manageable chunks, which can help teams complete projects efficiently and on time. The iterative nature of agile project management also encourages teams to test and revise plans and strategies regularly, which can help teams identify and address inefficiencies more quickly.

2. Improved Communication

Agile project management encourages teams to communicate frequently and collaboratively. This regular communication helps teams stay on the same page, reduces misunderstandings, and encourages everyone to contribute their ideas and perspectives.

3. Enhanced Flexibility

The iterative nature of agile project management makes it easier for teams to adjust to changing customer needs and priorities. This allows teams to respond quickly to changes, and to adjust their strategies accordingly.

4. Improved Quality

Agile project management encourages teams to consistently review and test their work, which can help identify and address any issues or problems more quickly and effectively. This can result in higher quality projects and products.

5. Increased Visibility

The regular communication encouraged by agile project management helps keep stakeholders informed of project progress and allows teams to identify potential risks or issues more quickly. This can help teams to take proactive steps to address any potential problems before they arise.

The implementation of agile project management can be a great way for SMEs to increase their project management capabilities and stay ahead of the competition. The five benefits discussed here are just the beginning of the many advantages that agile project management can provide.

Image credit: Pixabay

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Beyond Scrum – The Human Skills That Make Agile Work

Leave a reply

LAST UPDATED: November 18, 2025 at 11:23AM

Beyond Scrum - The Human Skills That Make Agile Work

GUEST POST from Chateau G Pato

For more than two decades, organizations have chased the promise of agility, seeking faster time-to-market and better customer alignment. The standard solution is mechanical: implement frameworks like Scrum, hire certified coaches, and meticulously follow ceremonies like Daily Stand-ups and Sprint Reviews. However, this approach has led to the frustrating reality that many teams perfectly adhere to every rule of the Scrum Guide and still end up slow, rigid, and ultimately, unable to deliver true agility. Why?

The answer is simple: agility is not a framework; it is a mindset, rooted in deep human skills. Scrum, Kanban, and SAFe are merely organizational containers — they provide the structure. But the true human operating system inside that container determines whether teams merely busy themselves with process or truly innovate. When Agile fails, it is overwhelmingly a failure of leadership and communication, not a failure of the process documentation itself.

The imperative for human-centered change leaders is clear: we must stop obsessing over velocity metrics and start cultivating the core relational skills — the soft skills that are actually responsible for delivering the hard results of a high-performing Agile organization.

The Illusion of Mechanical Agility

Mechanical Agility is the systemic dysfunction that occurs when an organization focuses only on adopting the nomenclature and processes of a framework. This structural compliance often masks critical human failures, leading to common dysfunctions:

The Daily Status Meeting: Daily Stand-ups become formal status reports delivered to the Scrum Master or management, rather than collaborative planning sessions owned by and directed for the team.
The Product Owner Bottleneck: The Product Owner acts as a sole gatekeeper, centralizing every micro-decision and effectively recreating the same Paradox of Control that Agile was supposed to eliminate.
The Ceremonial Retrospective: Retrospectives are passive, rushed, or devolve into superficial complaints, lacking the essential psychological safety required for deep, honest, and transformative institutional learning.

To move beyond this mechanical trap, we must focus on mastering the human skills that underpin the Agile Manifesto’s core values (e.g., Individuals and interactions over processes and tools; Collaboration over contract negotiation).

Key Human Skills for True Agility

True agility is built upon a foundation of psychological safety and communication mastery. These are the skills that enable the machinery of Scrum and other frameworks to function as intended:

Conflict Literacy: The ability for team members to engage in direct, constructive, and productive disagreement without fear of retribution or damaging relationships. This is crucial for vetting ideas, challenging assumptions, and avoiding harmful groupthink.
Radical Transparency: Not just making the backlog visible, but making intentions, risks, and assumptions visible across the team and with stakeholders. Leaders must share what they truly know and what the organization truly fears.
Proactive Feedback Loops: Establishing a culture where constructive feedback is given continuously, immediately, and empathetically, rather than being saved for formal reviews. This requires emotional intelligence and clear, non-judgmental communication protocols.
Distributed Facilitation: Moving the responsibility of meeting guidance and decision-making facilitation beyond a single role (Scrum Master or PO). Every team member should be skilled at guiding group dialogue, ensuring inclusion, and driving collective decisions.
Contextual Leadership (Servant Leadership): Leaders must transition from issuing commands to setting clear Guardrails and North Star objectives, then trusting and empowering the team to determine the “how.” This requires immense trust and a willingness to let go of granular control.

Key Benefits of Human-Centered Agility

When an organization masters the human skills of agility, the benefits are profound and measurable, extending far beyond predictable sprint cycles:

Sustainable Velocity: Teams maintain speed not because of mandates, but because they self-organize, proactively remove their own systemic impediments, and burn less energy on internal friction or political maneuvering.
Enhanced Resilience: Teams can adapt quickly to unexpected changes and market shifts, as they are skilled at honest, difficult conversation and rapid, collective problem-solving, making them robust to external shocks.
Deeper Innovation: Psychological safety allows for necessary risk-taking and the sharing of nascent or “bad” ideas that often lead to truly great ones, accelerating the path to breakthrough concepts.
Improved Morale and Retention: Team members feel respected, trusted, and empowered to own their outcomes, significantly reducing burnout and turnover.
Higher Quality Decisions: Decisions are made by the people closest to the information (the teams), supported by transparent conflict and rigorous challenge, resulting in more effective solutions.

Case Study 1: The Insurance Giant and the Conflict-Averse Team

Challenge: Feature Delivery Slower than Waterfall

A large insurance firm’s newly “Agile” claims processing unit had adopted Scrum perfectly, yet their feature delivery was slower than their old Waterfall model. Quantitative data showed high technical debt, but the root cause — a human one — was hidden.

Human Skills Intervention:

The intervention focused not on optimizing sprint length, but on Conflict Literacy and Psychological Safety. Through targeted, facilitated workshops, the team learned to use structured protocols for difficult conversations (e.g., using “I observe X, I feel Y, I need Z” statements). They uncovered that mid-level technical experts were afraid to challenge senior architects on technical debt issues, leading to flawed designs being pushed through every sprint. Leadership then explicitly coached the senior architect to adopt a Contextual Leadership style, actively rewarding technical disagreements.

The Agile Realized:

By fixing the human operating system — the fear of conflict — technical debt discussions became rigorous, not aggressive. The team’s improved ability to challenge poor design decisions led to an immediate dip in velocity (as they fixed old code), followed by a 40% sustainable increase in speed and a drastic drop in post-release bugs. The human skill of constructive conflict unlocked their technical potential.

Case Study 2: The E-Commerce Platform and the Product Owner Gatekeeper

Challenge: Stagnant Idea Flow and Low Team Ownership

An e-commerce platform’s core development team had a single, highly competent but overwhelmed Product Owner (PO). The PO’s backlog management was flawless, but teams felt like “code monkeys” simply executing tickets. Innovation ideas died on the vine, as the PO became the sole point of decision, resulting in the dreaded PO Bottleneck.

Human Skills Intervention:

The change focused on Distributed Facilitation and Contextual Leadership. The PO transitioned from being the “Decider” to the “Vision Holder” (Contextual Leader). The responsibility for initial idea vetting, risk assessment, and technical trade-off decisions was formally delegated to the development team leads. The PO trained the team in high-quality decision-making protocols and delegated specific budget allocation rights to the development team for small, experimental feature tests. The team practiced running their own refinement and planning sessions, ensuring all voices were heard.

The Agile Realized:

The team immediately began proposing and implementing small, high-value ideas without needing PO approval for every detail. The PO’s time was freed up to focus on market strategy and customer validation — true Product Ownership. The transition from centralized command to distributed empowerment significantly increased team ownership, leading to a 25% jump in measured team engagement and the launch of three highly profitable, team-led features within six months.

Cultivating True Human Agility

Leaders must stop treating human skills as peripheral “nice-to-haves.” They are the essential engine of organizational performance. The strategic investment must shift from expensive framework certification to robust training in: negotiation, difficult conversations, active listening, and distributed leadership.

Agile frameworks give us the map and the rules of the road. But the human skills — the trust, the communication, the willingness to engage in constructive conflict — provide the fuel and the steering wheel. We must cultivate a culture where human relationships are prioritized over rigid procedures. That is how we move beyond simply doing Scrum to being Agile.

“If your team can’t argue well, they can’t innovate well. Conflict literacy is the true measure of Agile maturity.” — Braden Kelley

Your first step beyond Scrum: Identify the meeting in your organization that suffers the most from poor participation or passive agreement (often the Retrospective or Planning meeting). Introduce a structured, facilitated protocol (e.g., using anonymous input tools or a “Decisions/Assumptions/Learnings/Experiments” structure) specifically designed to foster transparent feedback and constructive conflict, and delegate the facilitation responsibility to a different non-leader team member each time. This distributes the power and builds essential human skills.

Extra Extra: Because innovation is all about change, Braden Kelley’s human-centered change methodology and tools are the best way to plan and execute the changes necessary to support your innovation and transformation efforts — all while literally getting everyone all on the same page for change. Find out more about the methodology and tools, including the book Charting Change by following the link. Be sure and download the TEN FREE TOOLS while you’re here.

Image credit: Unsplash

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Leading by Letting Go in an Agile World

Leave a reply

The Paradox of Control

LAST UPDATED: November 14, 2025 at 12:18PM

Leading by Letting Go in an Agile World

GUEST POST from Chateau G Pato

Leadership often feels like a constant struggle to maintain control — of outcomes, resources, and people. This desire for centralized control is deeply ingrained, inherited from the industrial-era operating model built for predictability and repetition. But today’s reality is constant, chaotic change. In an Agile World, where market feedback is instantaneous and disruption is the norm, the leader who grasps the tightest is the leader who falls furthest behind.

This is the Paradox of Control: The more leaders try to exert granular control over their teams and processes, the more they actively suppress the very agility, innovation, and resilience required to succeed. True leadership is not about having all the answers; it is about designing the systems, boundaries, and safety nets that empower others to find the best answers locally. It is leading by letting go.

Moving from a “command” structure to a “context” structure is the single most important human-centered change a modern organization can undertake. It redefines the leader’s role from a solver to an architect.

The Two Axes of Control: Why Centralization Fails

Centralized control fails because it creates debilitating friction across two key axes:

1. The Speed Axis (Time-to-Decision)

In a hierarchical model, low-level problems must travel up several layers for approval and budget allocation. This process adds significant time-to-decision latency. When market demands or customer needs change instantly, a decision that takes two weeks to escalate and approve is functionally worthless. Decisiveness at the top slows the entire organization at the bottom.

2. The Knowledge Axis (Context Drain)

The further a problem travels from the front line — where the customer is talking, the product is breaking, or the process is jamming — the more context is drained from the data. By the time a decision reaches the executive level, it is often based on sanitized, summarized, or incomplete information, leading to sub-optimal choices. The people closest to the work are always the ones who know the most about the work.

The Solution: Control by Context and Guardrails

The human-centered solution is not anarchy; it is structured autonomy. Leaders trade procedural control for control over the boundaries and outcomes.

1. Define the Guardrails (The Non-Negotiables)

Guardrails are the strategic and legal constraints that teams cannot cross (e.g., maximum budget allocation, regulatory compliance, brand safety standards). The leader’s job is to define these constraints with absolute clarity and delegate everything outside of them. This answers the question: “What is the biggest mistake you are empowered to make?”

2. Establish the Context (The North Star)

The leader must tirelessly communicate the North Star — the company’s mission, its top strategic priorities, and the “Why” behind the current change initiative. When teams have a crystal-clear understanding of the context, they can make decentralized decisions that are 90% likely to align with executive intent. This minimizes the need for centralized approvals.

3. Decentralize Decision Rights (The Speed Multiplier)

As we explored in previous work, Decision Rights must be explicitly pushed down to the edge of the organization. If a team owns the metric (e.g., customer satisfaction score), they must own the budget and authority needed to improve it. Control shifts from the leader’s approval to the team’s accountability.

Case Study 1: The Software Company and the Release Train

Challenge: Slow Feature Deployment and Executive Micromanagement

A B2B software company suffered from release cycles that often exceeded nine months. The CEO, nervous about bugs, had to personally approve every major feature launch, slowing the organization to a crawl. Developers became cynical, knowing their work would be stalled by top-level scrutiny.

The Intervention: Leading by Letting Go

The company shifted to a “context-over-control” model by implementing a Scaled Agile framework. Crucially, the CEO defined a single, non-negotiable Guardrail: No feature could ship if its code quality score was below 95% (an objective, automated metric). Once that standard was met, the authority to ship was permanently delegated to the Product Owners on the development teams. The CEO stopped attending release reviews. The CEO’s new role became auditor of the guardrail and communicator of the North Star (improving time-to-market).

The Paradox of Control Realized:

By letting go of the decision (when to ship), the CEO gained control over the outcome (quality and speed). Feature release cycles dropped from nine months to six weeks, and code quality actually improved due to the clear, objective guardrail.

The Human-Centered Shift: From Hero to Gardener

The transformation required by the Paradox of Control is profoundly human. It requires the leader to abandon the image of the Hero — the person who swoops in to solve every problem — for the role of the Gardener.

The Gardener creates the ideal conditions for growth: rich soil (clear resources), sunlight (context and mission), and strong fences (guardrails). The Gardener does not control how the seeds (teams) grow, but ensures the environment maximizes their potential. This shift builds psychological safety and trust, which are the oxygen of innovation and resilience.

Case Study 2: The Healthcare Provider and Decentralized Compliance

Challenge: Excessive Compliance Friction in Patient Care

A large hospital system was struggling with high administrative costs and physician frustration. Every procedural change, even small ones aimed at improving patient flow, required sign-off from a centralized compliance office, leading to delays and workarounds that actually increased risk.

The Intervention: Control via Defined Accountability

Leadership recognized that the compliance office was trying to maintain control over process instead of risk. The intervention created a Decentralized Accountability Model. The centralized compliance team shifted their role from approver to designer of auditable compliance playbooks. They gave specific patient-care teams (e.g., Emergency Room staff) the authority to rapidly trial new process improvements, provided they documented the changes and adhered to pre-defined, measurable Risk Guardrails (e.g., HIPAA compliance, maximum wait time reduction goals). Audits were then performed immediately after the change was deployed, not before.

The Paradox of Control Realized:

By decentralizing authority over process, the organization gained greater control over risk. Risk exposure was actually reduced because teams could quickly implement official, documented solutions instead of creating risky, undocumented workarounds to solve immediate patient problems. Speed increased while anxiety decreased.

Conclusion: The Highest Form of Control

Leading by letting go is not passive leadership; it is the highest, most complex form of strategic control. It requires a leader to shift their energy from managing transactions to designing the organizational architecture.

The Paradox of Control asserts that your power isn’t in your ability to dictate, but in your ability to define the boundaries within which your empowered people can execute with speed and confidence. This is how you embed true agility and build a resilient, human-centered organization.

“The moment you stop seeking control over the how, you gain absolute control over the what.”

Your first step to leading by letting go: Select one low-risk, high-friction decision currently handled by you, define two non-negotiable Guardrails for it, and permanently delegate the decision authority to the team closest to the work.

Image credit: Pexels

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.