Trading One Silo for Another

I think we have silo busting all wrong. Well… partially wrong. I recall a story about a university campus. When buildings were put up on campus, there was a deliberate choice to not build any sidewalks or walk paths. Students, staff and faculty moved freely from building to building and over time, paths were worn into the ground where people had walked. The worn paths were the natural walking routes between buildings. Sidewalks were built on the beaten paths.

The usual approach to sidewalks and walk paths is to make straight lines, usually perpendicular or parallel to buildings. They look nice, neat and organized. But they are often not the way people choose to walk from point A to point B. Traditional organization design creates a neat, easy to understand model of how things should work. When it doesn’t work, we re-organize in the hope we are busting a silo. What happens instead is that we create a new silo. Silos are impossible to avoid. We trade one for another.

If instead, we could focus on the paths, we might have a chance of finding something better. In large knowledge-worker enterprises, the flow of information is the real organization. The rules and policies and containers we build are often not respected when something just has to get done. We use our network of trusted colleagues who have access to the right levers and information. When designing an organization, think about the flow of information. Go out into the organization and look for the beaten information paths. Find the “natural networks”, the ones that actually get things done and reinforce them. The challenge is to reinforce them without inhibiting natural change, or without constraining them.

C-Minus – How far are you from your customers?

When was the last time you had a conversation with a customer either on the phone, or in the flesh? As a programmer, if you view your test team as your customer, you’ve got it wrong. I’m talking about customers that buy what you build–those fine folks who ultimately pay your salary.

As an employee, are you concerned with how far you are from the CEO in the hierarchy? Do you count levels to measure your relative importance in the corporate food chain? Try this instead. Count the degrees of separation between you and your customer.

  • C-minus zero means you have direct contact with customers (real end-users of your product or service).
  • C-minus one means you are one step removed from direct customer contact, and so on.

It may not be feasible, nor desirable to have frequent direct customer contact for everyone when you have projects that are huge, with hundreds of engineers spread around the world. Customers would balk as well. However, there is nothing more valuable or powerful than getting direct feedback from customers, especially for the builders of the product.

If you have many degrees of separation between yourself and your customer, find ways to reduce this even if it is infrequent. Bring your customers in for a “Demo Day” and have them meet the engineers. You can do this on a schedule cadence that makes sense in your context. The frequency will vary depending on:

  • The project’s importance
  • The number of people involved in development
  • Geographic dispersion of teams relative to the customer
  • The depth of innovation in your project

What’s your C-minus? How can you reduce it?

Engagement, passion – the big WHY.

Only one in five employees are fully engaged. (Deloitte’s Center for the Edge: The Shift Index).

I personally view this video as a warning; the perils of over-rotating on a left-brained, rational approach to life, which removes context, meaning, and the big WHY of what we do.  Passion and vision are largely missing in the world of work, and when they do exist in doses that are sufficient to stir our emotions, we often fail to realize their potential. We don’t connect the WHY with the HOW and the WHAT.

The intuitive mind is a sacred gift…and the rational mind is a faithful servant. – Albert Einstein.

We need both, not only to survive, but to thrive.

 

The never-ending renovation, and what I learned… so far

I live in an old stone house which was built between 1839 and 1849. In the 1970′s, an addition was added on, extending the original house with a large family room, extra bedrooms, a rec room, and two extra bathrooms. Over the past three weeks during my vacation, we’ve been working on upgrading the dated interior. This included:

  1. Updating two bathrooms. These were stripped to bare walls and redone. The demolition had been done before the vacation, so all that was left was to repair floors, install tiled flooring, new tub, shower, vanity, toilets, and associated fixtures. Plumbing is not my favorite thing, and my plumber, like me, was on vacation, so I ended up doing it. The pipes are circa 1970, and waste pipes are all copper or cast iron. None of the sizes seemed to match the modern brass or PVC / ABS pipes so that created some adaptation problems. Read more of this post

Lead like the great conductors

Create the conditions for others to tell the story with you. Enjoy!

Deliberate Practice – the Leadership Kata

A kata is a set of actions that are assembled in sequence to help you train your mind and body to perform with precision, proper form, and to help you develop muscle memory so that these forms are available to you without thinking. The word “kata” comes from the martial arts. At the Agile2011 conference there was a tutorial titled “The Agile Leadership Kata: Discovering the Practice of Leadership” by Tom Perry. We applied the kata to the practice of leadership. Slides form the session can be found here.

Stephen Denning refers to leadership communication as performance art. All performance requires practice. Katas are a practice tool. Why bother? As a leader, why does it mater if I practice? If my current set of leadership tools are working, do I really need to develop new ones?

Read more of this post

Cultural Architecture

Last week I had the opportunity to present at Agile2011, which was attended by 1604 registered participants and over 250 talks. The conference was a wonderful opportunity to connect with old friends and make new ones.

The talk, titled Cultural Architecture was about how culture influences the way we work and interact differently depending on our cultural biases, rules and filters. Each culture presents unique challenges, and as change leaders, coaches, and practitioners, we have a responsibility to educate ourselves on how cultures influence what people do, why they do it, and how. As teams become increasingly cross-cultural and global, cultural knowledge becomes more important than ever.

Listening Tools

A great TED talk on how we are losing our listening…

Particularly interesting for me was the part on filters that we apply when we listen.  In a world where we we are increasingly broadcasting, Julian Treasure reminds us of the importance of listening, and shares five tools for improving our listening. Enjoy.

What does it mean to have a 100% Agile organization?

This is a question that comes up from time to time and to me, it’s like asking; “What does it mean to be 100% Chinese, Indian,  German or Italian?”

If we have everyone doing Scrum, does that mean we are 100% Agile? That’s like asking, “If I listen to Italian music, eat Italian food, drink Italian wine, and live in Italy, does this make me Italian?” Maybe it does…maybe it doesn’t! If you  have read about my talk at Agile-2011 know where I am going with this. Being 100% Agile to some extent means we cannot explain why we are Agile, we simply are. Why am I Italian? I just am.

I come from a Punjabi culture. While  preparing my talk for Agile-2011, I asked my sister why we value respect and deference to our elders. Her comeback was “The culture of guilt and shame.” We laughed. She reminded me of how if we failed to accord the appropriate respect to our elders, which included our parents’ best friends, we were taken aside and admonished with, “Aren’t you ashamed of yourself? Go say sorry to your Auntie!” Mom and Dad never explained WHY we should feel ashamed, only that we should…
Read more of this post

Leadership and Process Principles for Agile Finance

I’ve been reading “Implementing Beyond Budgeting” by Bjarte Bogsnes. Finance is sometimes a neglected area in terms of Agile Transformation and Bogsnes’s book offers rock-solid advice. The first element is the set of leadership and process principles.There are 6 of each:

Leadership:

  1. Customers. Focus everyone on improving customer outcomes, not on hierarchical relationships.
  2. Organization. Organize as a network of lean, accountable teams, not around centralized functions.
  3. Responsibility. Enable everyone to act and think like a leader, not merely follow the plan.
  4. Autonomy. Give teams the freedom and capability to act; do not micromanage them.
  5. Values. Govern through a few clear values, goals, and boundaries, not detailed rules and budgets.

Process:

  1. Goals. Set relative goals for continuous improvement; do not negotiate fixed performance contracts.
  2. Rewards. Reward shared success based on relative performance, not in meeting fixed targets.
  3. Planning. Make planning a continuous and inclusive process, not a top-down annual event.
  4. Controls. Base controls on relative indicators and trends, not on variances against the plan.
  5. Resources. Make resources available as needed, not through annual budget allocations.
  6. Coordination. Coordinate interactions dynamically, not through annual planning cycles.

These are difficult principles to live by without trust, transparency and simplicity in your organization. Adopting these principles takes time and effort, and a rather gargantuan mind shift. Eventually you’d want them all, but if you had to start somewhere, which principles would start acting on tomorrow?

Can we apply Pareto to the budgeting process, focusing on the top 20% of financial decisions and issues aligned with the Product Backlog?

Decisions on what to STOP doing are as important as the decision on what to START doing. Are you making the hard calls? Can you apply Pareto to both decision types? What will we fund? What will we kill?

More to follow on this topic in a future post.

Follow

Get every new post delivered to your Inbox.