Archive

Posts Tagged ‘Management’

Comments from the peanut gallery…

November 25th, 2009 Martin Proulx 2 comments

Let me start by affirming I am in favor of democratic structures in “for-profit” organizations. I believe people should have a say in decisions, no doubts about that. In my opinion, the concept of democracy is closely related to the wisdom of crowds where diverse opinions from a larger group of people systematically leads to better decisions and solutions.

Comments from the peanut gallery

Comments from the peanut gallery

Now that’s established, I want to make a distinction between democracy (participating in the selection of the decision) and the discussions leading to decisions – which I will call the debates.

The debate is not a democratic process. Let me use an example to explain why I have an issue with opening debates to crowds.

Following another disappointing loss of our local hockey team, a few colleagues gathered in the cafeteria were loudly debating their opinion on the cause of the team’s poor performance…

  • Paul: “Price [the goal tender] doesn’t deserve to play with the team, he lacks consistency…”
  • Mario: “What do you mean? Price did what he could but he can’t do everything. With Markov’s and Gill’s injury our defensive line is weak and Price is too often left to himself…”
  • Richard: “Did you guys watch the same game I did? We have no offensive line. We gave a lot of talent to bring Cammalleri to Montreal but he is just not the scorer we need and nobody actually has the right skills…”
  • Mary: “No, no. It’s the referee who influenced the game…”

I’ll stop here but that is enough to show my point. How many of these people do you believed played in the NHL? None.

How many of these people took coaching training or even played junior hockey? None.

How many of these opinions are actually useful to make the right decision? None. That’s right!

This is what my wife calls the “comments from the peanut gallery“.

Let me use another brief example to prove my point further.

Assume a skilled people manager joins his highly technical team for a brain storming session. The team is looking to improve performance of their Java application and the tension in the room is high.  The manager – for sake of clarity, doesn’t have a clue about computer programming except maybe for a 3 hours introduction to Microsoft Excel taken 5 years ago – suggests to replace the framework and maybe the sorting method. What are the chances that his suggestion will be accepted? None.

The same situation applies when people with no management experience or training jump into a discussion about people management or organizational strategies. To take part of the discussion there needs to be a few pre-requisites. It is not enough to want to participate in the discussion, to really contribute people need: knowledge of the topic being discussed, experience, and a willingness to move the debate forward.

What is not needed is a personal opinion without facts, knowledge or experience but this is exactly what happens when a debate is open to the general public. When these conditions are met (knowledge, experience, and willingness), people should be welcomed to join the discussion so to take advantage of the wisdom of crowds. When these conditions aren’t met, people should stay on the sideline waiting for the debate to end and propositions to be open for selection.

Just like in the Canadian Parliament, a selected (elected) number of people were selected to represent others in the discussion. Once options are selected, the democratic process can allow people to vote.

  • Share/Bookmark

Stop telling me HOW to do my job

November 2nd, 2009 Martin Proulx No comments

Americans hate their jobs more than ever” … ”Majority of Americans dislike their jobs” …

These are only 2 examples of a quick google search that returned over 44.1 million pages. Try “I hate my job” and the content of the pages returned is also very sad.

I don’t intend to go into socio-psychological analysis in this post but I wonder if something as simple as trusting your employees to do their job properly would actually increase job satisfaction?

For most people, enjoying their job would simply mean doing the same type of work but in a different work setting. Many people have spent years studying to develop their expertise in a specific field that they love. Then, one day, they start working and life becomes miserable – not because they hate what they are doing but because of the way the are treated at work. Once again, I don’t want to go into harassment or this type of treatment. The only point I’m raising is that letting professionals determine the best way for them to complete their work would is such a simple of increasing job satisfaction.

“Yes, but I’m the boss” – you reply.

So what? The fact that you were hired to lead or manage people in achieving a team or departmental objective doesn’t make you the most qualified individual to resolve day-to-day issues.

“Yes, but I’ve done this job before” – you insist.

Once again, so what? The individuals performing the job now bring different skill sets and expertise to the equation and as such are qualified to address their work as they see fit. You may provide guidance or answer your employee’s questions when they come ask for help but not tell them how to do their job.

Put together a community of expertise so people doing similar work can support each other. Provide tools if they need, support your employees in finding the right answers to their problems but don’t tell them how to do it.

There is a small Japanese car-manufacturer that understood that concept a while ago. They are now the largest car manufacturer in the world. Don’t you wonder how they achieved their success?

  • Share/Bookmark

Defining Agile Management – part 1

August 10th, 2009 Martin Proulx No comments

Following a post I wrote a few months ago, I keep trying to define the principles behind agile management and so far I came up with the following:

  • Be humble: When it comes to the details, your team knows more than you do. Tell your team what you are trying to achieve and the reasons why but don’t tell them how to achieve the goal. Offer your help if they need it.
  • Provide space for experimentation: Not all outcomes are known at the beginning of a project. Give your team time and resources to experiment. Playing is highly educational.
  • Try quickly: When someone has an idea, try it out immediately with a trusted audience. No single brain can anticipate all potential issues. Share the ideas as soon as possible to get feedback.
  • Start small: In line with the previous principle, use prototypes. An incomplete tool will provide far more information than a simple explanation. People need to see and feel things, don’t just rely on their imagination.
  • Learn from mistakes: Allow failures and learn from them. Nothing significant has been accomplished in a single iteration.
  • Do not punish failures: In line with the previous principle, failure is part of the learning process. Penalizing people for their mistakes sends a strong message that your team is risk averse.
  • Maintain constant communication between the demander and supplier: Communication is key to building relationships. Bi-directional communications will help prevent assumptions and increase chances of success.
  • Have strong integrity: Say what you will do and do what you have said. People will respect you for it.
  • Do not be afraid to commit: Nobody likes indecisive people. Commit to other people will give you increased credibility.
  • Make sure to re-negotiate: In line with the previous principle, if you are unable to meet your commitment re-negotiate them immediately. Do not wait.
  • Focus on results and not process: The methods used to achieve results are much less important than the results themselves.

What are your thoughts? Have I missed anything important?

  • Share/Bookmark

Can you grow a business profitably while improving the lives of people?

August 5th, 2009 Martin Proulx No comments

In today’s post, I am publishing a translated version of the blog post I co-wrote with François Beauregard, President and Founder of Pyxis Technologies. The article is reproduced here with permission.


Quite by chance I came across an article (The Smart Growth Manifesto) that triggered some interesting thoughts in my mind. I immediately sent the article to François asking him about Pyxis’ position compared to what is described in the article as the 21st century capitalism.

Below is the content of our exchange and personal perspectives on this article.

Martin: In recent years, I frequently asked myself “Are we the last generation for whom the standard of living is better than the generation that preceded it? Will our children and our children’s children have an income level lower than ours? Will they be happier? “. The type of organizations described in this article is rare but I believe that Pyxis would qualify as one of these companies. What do you think?

François: In your opinion, how does Pyxis rank compared to other companies?

Martin: I think we are definitely in the “trail blazers” category. Very few organizations have a business model that fits the way of thinking and operating described in the article. I believe we could establish an exciting objective to continue our rapid growth while remaining true to our business model. In fact, the model described in the article is close to the concept of  ”NPII” (Number of Positively Impacted Individuals) and the concept of welfare which we often referred to at Pyxis – maybe without the negative connotation of the long robes, the sandals and the flowers in our hair! I like the phrase People Outcome used in the article and the definition of smart growth – “smart growth is sustainable, equitable, and resilient“.

Does this speak to you?

François: Of course it speaks to me, it’s screaming in my head! Whether or not we agree with everything stated in this article, it certainly raises several interesting lines of thought and it seems very healthy to ponder about them and identify elements that could lead us to make improvements to our organization. Let’s start with the first pillar Outcomes, not income that translates for me as well-being more than remuneration. I have been repeating for a while now that the fundamental objective of Pyxis is not to generate profit for its shareholders but to achieve its mission, its purpose; to the point that many believe that money has no importance at Pyxis. Money is absolutely essential for a company to function, it is the air and without air the system can not breathe and it dies. In this analogy, participants in the enterprise would be seen as the muscles that allow the company to act, to make things happen.

Having a purpose that is shared by all ensures that the system is geared towards achieving a fundamental objective and avoids wasting energy to move in inconsistent directions. For Pyxis, the reason for being is: Pyxis helps software development organizations to become places where results, quality of life and pleasure coexist in a sustainable way by being first an example of what it proposes to its customers. Having defined a clear future makes it possible to set concrete targets.

To go back to well-being more than remuneration, it is my firm belief that if the employees are also the shareholders of the organisation that points to (but not absolutely) a more responsible (sustainable) and equitable model of redistribution of wealth. This also leads to a better balance between the desire to produce economic benefits in the short term for shareholders, and long-term value creation and welfare for the employees (in fact the shareholders). In our case, we set up a worker-shareholders cooperative (WSC) who now holds 30% of the companies’ share (Class A) and there are efforts underway to significantly increase the percentage of shares held by the WSC of Pyxis.

I’d like to hear you on Connections, not transactions.

Martin: It’s interesting that you translated Outcomes, not income as well-being more than remuneration. At the last Open Space held at Pyxis in April, I frequently used Wellness, rather than ownership. I think it extends the notion of personal happiness to a wider meaning than the simple financial perspective.

On the other hand, I agree with you that some people within our organization incorrectly interpret the message when you state that the main objective of the organization is not to generate profit. I heard some people mention that happiness and pleasure were the fundamental objectives and that money is not a priority. I know you try to correct perceptions whenever you have the opportunity.

On a completely different perspective, the notion of fairness is a concept that is also confusing for some and causes major discrepancies. In my opinion, fairness is a concept that applies to both the opportunities and the results. First, fairness in opportunities means that the largest number – ideally all – have access to participate in the economic process and to benefit from it. I am not talking about charity or social programs, but a true opportunity to be part of the economic process. I like, among other things, the concept of micro-lending such as the Grameen Bank or organizations like Kiva, which allows individuals to participate in the local economy.

On the other hand, fairness in earnings means that individuals are rewarded in proportion to their contributions. Some mistakenly believe that equity in the results means that everyone must have an equal portion of the benefits. Fairness and equality are not the same thing. I think fairness means that the benefits are available to all of those who participated in the achievement of the objectives and the distribution is in proportion to the contribution of the individuals. Recent examples of senior American executives who pocketed large bonuses when their company came close to bankruptcy is quite absurd.

In line with the concept of welfare, Connections, not transactions take us back to a more human perspective of trade and economics. Pre-industrialization commercial transactions were much more collaborative. The local farmer didn’t aim to maximize its revenues at the expense of its customers. Not only did the farmer not have that goal, but the maximization of income was not in his interest since he was himself a client of his customers. If the farmer inflated the price of his eggs to increase his personal wealth, the baker would do the same. The system would balanced itself as short-term profit of the farmer would be quickly eliminated by higher prices for goods purchased from the baker.

What do you think?

François: When I read the previous paragraphs, I can not help but think of Lean and references to the principle of optimizing the whole process and avoid local optimizations. It’s been quite some time that Toyota has understood that the objective is to optimize the supply chain as a whole to create maximum value for all stakeholders. This is quite contrasting with what I saw in North America since the beginning of my career where I feel that the mental model applied to maximize the value received is to keep pressure on the suppliers without considering the value created for them. In other words, in this mental model, if a supplier is successful, it is absolutely necessary to renegotiate their prices downwards to ensure the organization obtains the maximum value for its money. This is the model of the “pressure on the throat” that inevitably leads to sub-optimizations and ultimately to conflicts.

Connections, not transactions in my opinion represents a huge challenge because it forces us to significantly revise the way we do business. When I talk about my perspective of business to customers and suppliers and I sometime have the impression that they take me for an extra-terrestrial.

Let’s now go to People, not product.

Martin: For People, not product, I will tackle this one from a different angle than the one used by Umair Haque. For me, the perspective is less about product and more about humanization of work. For too long, organizational structures assumed that people at the bottom of the pyramid were less competent and less capable to determine for themselves how best to perform their tasks. The methods, processes and outcomes were defined at the top of the hierarchy, while execution was delegated to non-managerial staff.

As the economy turns toward services and knowledge, the role of the managers is losing its importance while advanced technical expertise increases in value. The challenge is therefore to put in place mechanisms – not structures – that maximize cooperation and knowledge sharing to achieve the organizational objectives. Decentralized and non-hierarchical structures set up within Pyxis are a good example, aren’t they?

François: You knew that is a core belief of mine! Let’s begin with People, not product. I was strongly influenced by the work of Peter Block, in particular his book Stewardship. At Pyxis, I tried to create a strong culture focused on individuals and their individual responsibility (not to be confused with individualism). I’m looking for a way to explain it all and I see no other way than to express my vision of the enterprise systems. Here I go.

A company is a human system whose complexity is growing exponentially, a system comprising 100 individuals is much more than 10 times more complex than a system with 10 individuals. For the purpose of this post, let’s imagine for a moment a company called Chaotic Inc. which includes 100 employees. In this organization, there is no structure, no rules, no identified purpose. It is interesting to observe Chaotic Inc. but it is obvious that the system is not optimal for achieving a fundamental objective.

We have discussed above, giving the company a purpose that is understood and shared by all stakeholders to give direction to the system thus avoiding to some extent that stakeholders spend energies tackling fundamentally incompatible goals. Clearly establishing the values for the participants to understand the appropriate behaviors and encouraged those behavior when operating inside the company (the system). In other words, some defining rules for what is in play and what is out of play. So one can imagine that Chaotic Inc. after a collaborative exercise to establish its purpose, its values and vision over several years is significantly more effective then it would have been even if its operations were still relatively chaotic – sort of speak.

To become a successful business and achieve its purpose and its vision, Chaotic Inc. should probably put in place structures. It then becomes quite difficult to adapt from a systemic point of view, since putting structures in place sediments the system because if the structure is inadequate with an evolving system, removing the inappropriate structure in order to replace them for better suites structures requires a substantial quantity of energy. It is therefore essential to establish mechanisms that encourage flexibility and dynamism of the system (more details about this topic in an upcoming blog post). The basic structure most common in our organizations is the hierarchical structure and it is inappropriate to me in a system as complex as a modern business. So then what is the alternative? At Pyxis we adopted a principle of mapping the areas of responsibility without violating the fundamental principle that no individual can be responsible for someone else. This helps to loosen the system by clarifying who is responsible for what, and specifying processes (more specific rules about what is in play and what is out of play) without giving formal authority.

Within Pyxis, we also put structures in place to develop the maturity and competence of all employees. It may be interesting to write a few posts to elaborate on these structures. Much work remains to be done but I think we have in place the foundations of a highly-performing human system. As such, Pyxis’ 2013 vision is: By implementing what we believe, repeatedly obtain extraordinary results in the projects we are involved with.

Whew! You want to initiative Creativity, not productivity.

Martin: There are considerable efforts being invested in achieving maximum productivity, i.e. producing as much as possible at the lowest cost. In my opinion, the perspective of productivity without other consideration is absolutely incorrect. Creativity, not productivity is for me a fair and sustainable productivity, which is different than simple creativity aimed only at improving productivity. In several sectors, the unit production costs are so low that organization come to a complete waste of resources at the end of the cycle – they sell 60% of their production at full price and they discard the remaining 40% since its production cost is not high.

In the context of software development, this is equivalent to writing more lines of code at a lower unit cost. Organizations find ways to ensure that resources produce more (extensions of work hours, outsourcing, time constraints) without wondering if there are better way to achieve results. Using creativity and innovation in production methods, achieves better results and hence gives more value to the organization. I believe that evolutionary processes are not desirable. It takes innovation and revolutions rather than evolution methods.

It is time that organizations begin to think in terms of results rather than accounting costs or productivity as per the Taylorist approach – this is what Pyxis is aiming to do.

At the end of his article, the author raises an interesting question Can you build a business powered by smart growth? I know you would answer yes to this question. The question that applies to Pyxis is rather, how does it happen?

François: It is a difficult question. What comes to mind is how Peter Block discusses this issue in his work where he talks about the role of the social architect, creating space for individuals to act on what is important for them. I take this personal commitment to Pyxis and strongly wishes that others would do the same.

Martin: Finally, our exchange on the theme of 21st century capitalism has raised the following question for me: “For the shareholder-employees, what concrete evidence would show that the business model set forth by Pyxis really works?” Although preliminary, my response would be as follows:

Using varied and innovative approaches Pyxis substantially increases the level of performance of the companies it serves. As such, Pyxis generates a high profitability that it re-distributes to its shareholder-employees and to the community.

To its shareholder-employees:

  • By introducing the 80% rule where shareholder-employees receive 100% of their salary while working 80% of the time on an annual basis. Individuals use the remaining 20% to spend more time with their family and their friends, their colleagues and their community;
  • By paying annual bonus and dividends in relation to company performance;
  • By increasing the capital value of the company.

To the community:

  • By allocating financial and human resources to advance social causes.

I’ll leave you the last word.

François: I really enjoyed this collaborative mode of writing and I encourage everyone to try it out. Martin, thank you for having kept our energy level high and helped me write about a topic that is really close to my heart. Fortunately, we both discovered there are plenty of opportunities continue this conversation.

Stay tuned …

  • Share/Bookmark

Helping employees grow without an HR department?

July 21st, 2009 Martin Proulx No comments

Our organization is using an innovative human resource management approach inspired by the “golfercaddy” relationship in golf. Although the approach isn’t fully matured and there are still adjustments to be made, I believe there is value in sharing the process.

Some background

During its early years, human resources management was done entirely by the management team. The communication was centralized and the company’s founders had relations with all employees. They were responsible for hiring, annual evaluations and taking decisions relating to salary revisions. The fast growth of the organization highlighted certain limitations:

  • Managing the relationships between employees and the founders was increasingly difficult to maintain as the organization grew;
  • The centralized communication channels weren’t efficient;
  • The willingness to develop a new process without hiring specialized HR specialists;
  • The management of special situations and salary determination lacked transparency and were perceived to be unfair.

To address these emerging issues, the organization developed the “Caddy” process, a model of decentralized community-based human resource management.

What is a Caddy?

In golf, the caddy is the person who carries the golf bag, gives advice and provides moral support. A good caddy is aware of the difficulties, obstacles and peculiarities of the course, as well as the best strategies to play the course. The caddy is not the one who plays the game, the golfer is!

Objectives of the process

The objective of the process is to support employees’ success and monitor their well-being. In addition, the caddy process is a way for all employees to participate in the management of the organization by helping their peers to receive the proper feedback and skills to be successful in their role. The caddy process is deemed more efficient than the traditional hierarchical model.

The process

When an employee joins the company, he/she is assigned a caddy for a period of six months. After that period, an employee may decide to change caddy any time. A discussion between the golfer and the new caddy is required to identify the expectations of each party and determine if the match is possible and desirable.

Role and responsibilities of the Caddy

The caddy has certain responsibilities to the employee. In a traditional organization, these responsibilities are held by the Human Resources Department:

  • Communication of the corporate strategy;
  • Keeping track of business objectives;
  • Accompanying the employee in his career development and providing the support to develop new skills;
  • Assisting the employee to set goals and support them in achieving these objectives by offering the means to do so;
  • Preparing the salary revisions and making recommendations.

Caddy Team Charter

“I am unwavering in the success of each of my players, my caddy and the caddy team”.

Why?

Because people are the most important asset of the organization. Their development is linked to the success of the organization.

What?

The Caddy process is based on trust and respect. It is a relationship of support and coaching without direct authority.

Who?

The Caddy is a humble person with great listening capabilities. He has the courage to confront the person if necessary and the wisdom to do so in respect of the person. Above all, he shares a common goal with his golfers: the professional success and development of the latter.

Mean

The Caddying is one of the most important roles in the organization and he is recognized as such, encouraged and valued by the organization.

Result

The Caddy process has a significant positive impact on the development of the golfer.

  • Share/Bookmark

6 ways to know if you are working for an archaic organization

July 8th, 2009 Martin Proulx 2 comments

For years you have been hearing that you work for a leading-world-class organization but somehow that statement doesn’t resonate with you. How can you tell if you are truly working for an innovative and caring organization? Find out if the slogan “Our people are our #1 asset” is meaningless in your organization by looking at the 6 ways to know if you are working for an archaic organization.

1. Do you work for a democracy?

Does your organization believe the authoritarian power of a single ruler is better than collective intelligence?

Many have demonstrated that collective intelligence delivers better results than relying on the knowledge of a few (The Wisdom of Crowds: Why the Many Are Smarter Than the Few and How Collective Wisdom Shapes Business, Economies, Societies and Nations).

As imperfect as it is, we trust democracy to select the people who will lead our countries, vote laws, decide to go to war (or not), and determine taxation level – among other things. When it comes to business, organizations typically prefer to give complete authority to a single person who will ultimately decide what is good (or not) for the organization.

Why can’t organizations adopt a more decentralized management approach?

2. Is your organization at war with its competitors?

Does your organization think of competitors as enemies and use war related terms and strategies in an attempt to eliminate them?

The Cluetrain Manifesto: The End of Business as Usual has a great chapter on the analogy between business and war and the attitude your organization has towards competition is a good indication of how innovative it is.

Has your organization ever thought of cooperating with competition to increase the overall size of the market instead of competing for portions of a smaller market?

3. Does your organization force its employee to follow rigid rules to get things done?

Does your organization believe access to resources should follow a well defined sequential process with gatekeepers along the way?

Remember the days of video cassettes? To access a specific scene in the movie, you would need to forward to it forcing you to painfully have to watch all the content before getting to your end goal. Then came the DVD where you can now jump directly to the scene of your choice without having to follow the defined sequence.

Many organizations are still like old video cassettes and have implemented structure, rules, and processes to control access to resources and decision making authority. They are controlling their operations. By comparison, look at organizations that empower their employees to make the best decisions and allow them to get to their end goal as fast as possible.

Which model do you think will allow the organization to prosper?

4. Are fortresses built within your organization?

Does your organization allow people to build a fortress around them to reduce threats from other employees?

Closed offices and controlling assistants are obvious ways to protect against other people. In some cases, managers are clever and typically hire weak employees so they are not threatened in their role. Others are trained politicians who have learned to look good in front of senior management but are bullying their colleagues and employees.

Shouldn’t organizations ensure that the leaders are confident individuals who are not afraid to take risks and sometimes fail in order to move the organization in the right direction?

5. Is slavery still permitted when it comes to resource management?

Does your organizations assign resources to projects and departments as if they were disposable resources?

In the information age, people are required in order to deliver value-added knowledge. Unfortunately, many organizations still dispatch individuals as if they were lifeless (and emotionless) objects to projects that are doomed from the start. There are some beliefs that with the proper pressures, people can work endless hours to make up for un-realistic deadlines and still deliver quality outputs.

Why not threat individuals as competent and knowledgeable contributors to the success of their assignement instead of believing they should simply execute order to achieve the required goal?

6. Are employees threated as if they were back in grad school?

Does your organizations believe it is fair to receive performance evaluation by a single individual?

Many organizations still rely on the manager to obtain feedback and communicate it to employees. Unfortunately, many people have not been trained to seek proper feedback let alone communicating it. Some organizations have started to implement 360 degrees feedback and as such the content is much more helpful to the individuals.

Why not gather feedback from various sources and have a trained communicator provide the feedback to the employees so they can actually learn and improve based on the information provided?

In conclusion

There are many ways to lead an organization. Not challenging some of the existing practices is the best way for an organization to have the same faith as the dinosaurs…

  • Share/Bookmark

Agile Principles Applied to Management

April 17th, 2009 Martin Proulx No comments

As I was driving back home after another exciting day at the office, I was wondering how much information I would find on “Agile Principles Applied to Management”. Google.ca returned 273,000 results most of them about Agile principles applied to workflow management or Agile project management (scrum) but nothing about applying those principles to management in a business setting. Interesting! 

The Principles behind the Agile Manifesto were originally drafted in 2001 to promote a new approach for software development but with the growing success and pragmatic approach of Agile, I believe the principles can indeed by applied to management. Below is my first attempt at rewording the Agile principles so they can be applied to management. To avoid confusion, I am presenting my proposal in brackets [].

  • Our highest priority is to satisfy the customer through early and continuous delivery of [our goods / services].
  • Welcome changing requirements, even late in [the production / delivery process]. Agile processes harness change for the customer’s competitive advantage.
  • Deliver [innovations] frequently, with a preference to the shorter timescale.
  • [Externally focused employees] and [internally focused employees] must work together daily throughout the project.
  • Build projects around motivated individuals. 
  • Give them the environment and support they need, and trust them to get the job done.
  • The most efficient and effective method of conveying information to and within a [] team is face-to-face conversation.
  • Working [products are] the primary measure of progress.
  • Agile processes promote sustainable development. 
  • [The extended project team] should be able to maintain a constant pace indefinitely.
  • Continuous attention to [] excellence and good design enhances agility.
  • Simplicity–the art of maximizing the amount of work not done–is essential.
  • The best [work / products] emerge from self-organizing teams.
  • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Which I would summarize to the following Agile Principles Applied to Management:

  • Customer satisfaction is the highest priority – demonstrate it by constantly delivering on their expectations.
  • Focus on providing your customers a competitive advantage.
  • Improve your product / service frequently – even in small increments.
  • Assemble cross-functional teams and ensure they work together.
  • Assign motivated people to your critical projects.
  • Trust your motivated people to get the job done.
  • There is no better communication than face-to-face communication.
  • Progress can only be measured with working products – incomplete products are useless.
  • Maintain high focus on quality and simplicity.
  • Self-organized team produce better results.
  • Allow the team to inspect and adapt.
  • Share/Bookmark