Be a Chef, Not a Cook: Exploring Solutions in Complex Adaptive Systems

In the world of Agile, particularly within complex adaptive systems, there’s often a gap between the goal and the direction we should take to achieve it. This gap can lead to us seeking out the simplest, most convenient solutions—solutions that, while easy to implement, are often wrong or ineffective.

Instead of chasing the next shiny tool or trendy framework, I want to encourage you to think like a chef, not a cook. This approach allows you to experiment, explore, and create custom solutions tailored to your unique challenges.

In this blog post, we’ll explore how a combination of complexity thinking, Scrum, and additional frameworks and practices—like the Hexi approach—can empower you to develop viable solutions in complex environments. So, let’s dive in!

The Problem: Clear Goals, Fuzzy DirectionWhat are we solving?

The problem many teams face is this: The goal is clear, but the direction is not. When direction is unclear, we often look for the easy but incorrect solution. This might sound familiar:

“Oh, let’s use this tool—it worked for that other team.”“Why don’t we adopt that methodology? It seems to fix everything!”

This line of thinking is a trap. You end up shopping for solutions rather than understanding the problem or the system you’re working within. Instead of diving deep, you grab the first available answer, hoping it will stick. But in complex adaptive systems, where the environment is constantly changing, there is never a simple solution.

Be a Chef, Not a Cook

Here’s where I introduce the concept of being a chef rather than a cook.

A cook follows recipes and executes predefined steps. They rely on someone else’s solution, often without fully understanding the “why” behind it.A chef, on the other hand, creates new dishes. They understand the ingredients, techniques, and the environment they are working in, and they adjust to create a customized, effective result.

In a complex system, we need to experiment, explore, and create our own solutions based on a deep understanding of the system itself. This is what the Hexi approach encourages: thinking for yourself and experimenting with different tools and techniques to develop your own unique dish.

Why is this important in Agile?

In the complex domain, especially when working with Scrum and other Agile frameworks, there is never a one-size-fits-all solution. The real power of Scrum is that it’s a minimal framework. While it provides the foundation, it is not sufficient on its own. Scrum needs to be enriched with other practices, tools, and frameworks to effectively address the unique challenges of your context.

I’ve often brought in complexity thinking and mixed it with Scrum to build more viable solutions. It’s about understanding that Scrum is a starting point—it’s the canvas on which you paint, but you need other tools to create the full picture.

Exploring and Experimenting with HexiWhat is the Hexi Approach?

The Hexi approach is a set of cards or tools that encourage exploration and experimentation. Each card represents a different tool, technology, framework, or method that can help you understand the complex adaptive system you’re working within.

Here’s how it helps:

Exploration: You’re encouraged to explore various options rather than jumping to the simplest, most convenient solution.Experimentation: It allows you to test multiple frameworks and approaches to see which combination works best for your situation.Customization: Instead of copying and pasting someone else’s recipe, you craft your own based on your team’s needs.

By experimenting with different tools, you deepen your understanding of the system and can create solutions that are uniquely suited to your context. This goes back to the chef analogy—each solution you create is a dish that’s tailored to the environment you’re working in, not just another cookie-cutter recipe.

How Does This Apply in Scrum?

Let’s be honest—Scrum is not enough. While it provides the foundation for building agile teams and driving continuous improvement, it’s only a starting point.

I often bring in other ideas from the Hexi cards to enrich Scrum, especially when dealing with complexity. Here’s how:

Complexity Thinking: Helps teams understand the system they are working within, acknowledging that the solution is not straightforward and requires continuous adaptation.Additional Practices: Integrating practices from other frameworks or methodologies helps solve unique challenges that Scrum alone cannot address.Viable Solutions: By combining Scrum with other tools, you can model viable solutions that fit the specific complexities of your environment.

For example, when working with teams in a complex environment, I often use practices from Kanban to visualize workflows and identify bottlenecks, while Scrum helps in structuring the team’s iterative progress. It’s this mix-and-match approach that delivers real value.

Personal Experience: When I Became the Chef

Let me share a personal example. I was working with a team in a highly regulated environment where the complexities of the system were overwhelming. Scrum alone wasn’t cutting it. We kept running into bottlenecks and inefficiencies, and the team’s progress was stalling.

I decided to experiment by bringing in elements from Lean and Kanban. The team visualized their entire process, from request to delivery, and used WIP (Work in Progress) limits to manage their flow. The result? The team had a clearer understanding of their workflow, we identified and removed bottlenecks, and productivity skyrocketed.

This wouldn’t have been possible if we’d stuck solely to Scrum. By being willing to explore, experiment, and bring in additional frameworks, we created a solution tailored to our unique situation.

Recommendations for Your Agile Journey

So, how can you apply this thinking to your own Agile practice? Here are a few recommendations:

1. Avoid Simple SolutionsDon’t fall into the trap of using the first shiny tool that seems to solve your problem.Take the time to understand the complexities of the system you’re working in.2. Experiment and ExploreBe willing to try out different frameworks, tools, and practices.Use methods like Hexi to explore various approaches before settling on a solution.3. Enrich ScrumRemember, Scrum is just a minimal framework. Use it as a foundation, but enrich it with practices from other methodologies.Mix Scrum with complexity thinking, Lean, Kanban, or any other tool that makes sense for your context.4. Be a ChefThink for yourself. Create your own solutions rather than relying on pre-made recipes.Customize your approach based on the challenges you face.Final Thoughts: Be Curious, Stay Flexible

In complex adaptive systems, there is no one-size-fits-all solution. As Agile practitioners, we must be willing to explore, experiment, and create our own custom solutions. By enriching Scrum with other practices and thinking like a chef, you can model solutions that are effective, viable, and tailored to your specific environment.

Remember, Agile is a journey of continuous learning and improvement. Stay curious, stay flexible, and be open to trying new things. You’ll be amazed at what you can cook up.

The post Be a Chef, Not a Cook: Exploring Solutions in Complex Adaptive Systems appeared first on effective agile..