Skip to content

Archive for August, 2009

Stop treating me like a grown-up

I can’t recall the number of times I heard an employee, a colleague, and even a manager say “I wish my boss would give me more responsibilities and stop telling me what to do“. This seems to be a recurring theme but what really surprises me is how quickly people want to give up their new responsibilities and run to their boss to ask them what to do once they are given more responsibilities.

Growing up is a difficult endeavour and many people would prefer to remain “children” (sort of speak) within the organizational environment. Notice how, even within self-organized teams, people will go to the leader and ask for permission to do something – Can I delay my current assignment to start working on something more critical? Can I skip the recurring weekly status meeting tomorrow to help Peter resolve an important client issue? Can I spend $200 to purchase a new tool that will save me 10 days of work?

It is my firm belief that people are very capable of answering their own question and take the best decision. If they need additional information, I’m there to provide it to them. If they need my experience, I’m there to share it with them. If they need me to support them, I’m there for that also. But if they want me to take the decision for them, sorry I am not available or even interested in doing that. I like people to be accountable.

Every time, I ask people why they are asking ME for a permission to do something, I invariably get “I’m afraid to make the wrong decision” as the answer. Organizations are so slow to change, to evolve, to mature because of the constant fear maintained by the organizational structures, processes, and (yes) people.

Give some slack to your people and support them in the process of organizationally growing up but don’t get into the position of taking the decisions for them unless you want your organization to stop growing.

Project Charter – Agile Project

In the spirit of sharing, below is an example of  a Project Charter we use to launch a Agile Projects. Do you use a similar document? In which context? Are there sections that are more critical for the success of your projects?


Vision

The Electronic Balanced Scorecard (EBS) project for Company Y is designed to develop and implement a simple tool to aid the decision making process of all managers and to help them evaluate the impact of their actions and determine if it is in line with corporate strategy.

Objectives of the EBS Project

  • Total transparency of the information for all managers;
  • To generate conversations among managers with regards to the performance indicators;
  • The tool should be easy to use by everyone;
  • To monitor the performance of the organization with respect to the strategic objectives;
  • Supporting the decision making process of all managers;
  • Guide and adjust the strategic discussions.

Success Conditions

To have implemented all the key performance indicators (highlighted in green in the definition document) in time for the strategic meeting that will take place in November 2009.

  • The information must be accessible by everyone;
  • The information must be understandable by everyone;
  • The information must be updated within a pre-defined timeline;
  • The information must be relevant and practical for managers to use;
  • The strategic objectives must be defined, communicated, measurable and measured regularly;
  • The strategic objectives must be communicated to all managers prior to launching the project;
  • The ESC supports the decision making process of the managers on a daily basis.

Priorities and Compromises Matrix

  • Scope: Not Negotiable (priority 1)
  • Schedule: Negotiable (priority 3)
  • Budget: Difficult to Change (priority 2)

Risks

  • Adoption of the new decision-making tool by all managers;
  • Introduction of several new processes;
  • Incomplete and / or erroneous information
  • Availability of key managers;
  • Implementation of a Human Resource Management System;
  • Integration of financial systems from various countries.

Risk Mitigation

Implementation of a change management program.

Role of the various team members

  • Product Owner: Paul Bergeron
  • Scrum Master: Christine Clark
  • Team Members: Patrick Allen, Christopher Green, Anthony Stephanopoulos, Cynthia Martin
  • Ergonomics Expert: Francis Albert

Top People in the Agile Business Intelligence and Agile Data Warehousing World

Although the notion of Agile Business Intelligence is still fairly recent, I decided to do some research (aka Googled) to find out who are the Top 10 People in the Agile Business Intelligence / Agile Date Warehousing World. Assuming that Google’s ranking is accurate, I compiled the following list of thought leaders.

My objective was to identify the Top 10 and much to my surprise, I was only able to identify 4 people (companies were excluded)! These 4 individuals’ name consistently appeared in the search results.

  1. Scott W. Ambler
  2. Ted Malone
  3. Ralph Hughes
  4. Ken Collier

Do you feel there are names that aren’t in the list and should be there? Let me know.

Defining Agile Management – part 1

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?

Inline with an Agile Organizational Structure

As time goes by, I realize there is no such things in life as coincidence. I’ll probably expend on this topic in an upcoming post but for now I’ll jump to the purpose of today’s blog post.

If you have been reading some of my recent posts (this one, this one and this one) you will notice that I took upon myself to help implement an innovative organizational structure for the organization. As a consequence, Raphaël suggested I take a look at Holacracy.org.

I had the pleasure of sitting in on the webinar given by Brian J. Robertson from Holacracy and found the content was very much in line with the organizational structure we are aiming to implement. In short, here are two take-away I got from the presentation:

  • We need to distinguish the organization from the individuals that compose the organization.
  • The organization has to be purpose driven. Its goal is not only to generate profits for the shareholders but to have a purpose of its own.

Although there is much more to this than these 2 points, the 60 minutes presentation gives a good introduction to the concept. I am unfortunately unable to attend their next events in Philadelphia and Dallas both hopefully they will add events to their calendar shortly.

If you get a chance, I suggest you sign up for one of their upcoming presentation and share your thoughts.

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

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 …

Simple Definition of Strategy

I’m spending a lot of time working on our Strategy these days and working with colleagues to define our objectives in order to achieve the corporate vision. Coincidentally, I got to the section of the book (Winning) where Jack Welch describes his perspective about strategy and his three steps to defining a good strategy.

In a nutshell, Welch states that strategy isn’t much more than selecting and prioritizing the right activities in order to achieve the vision. More specifically, he explains that strategy as promoted by strategy gurus is overly complex and that the process can be simplified to deliver better value. In simple terms, determining which activities (at a macro level) are required to reach the vision, prioritizing and sequencing them logically, and then allocating the right amount of resources to achieve them.

Once we understand Welch’s perspective on strategy, it becomes easier to understand his threes steps:

Step 1: Come up with a big “Ah Ha” for your business – a revelation, an insight that will give you a true competitive advantage within your industry

Step 2: Put the right people in the right job to drive the “Ah Ha” forward – matching the right personal attributes to the task at hand is critical

Step 3: Relentlessly seek out Best Practices to pursue your big “Ah Ha” – develop and/or borrow best practices to establish a competitive advantage.

Although it may sound simplistic, I like these 3 steps as it forces the organization to pick a direction to take and then work hard at implementing the strategy. Welch’s perspective of strategy is very similar to what we use within our organisation. Strategy is an approximate course of action that needs to be revisited and redefined according to market conditions. Strategy is an iterative process and more time should be spent implementing the strategy than defining it.

Facilitation Cards

After facilitating a few challenging meetings where people talk a lot and sometimes have parallel conversations, I’ve decided to use facilitation cards to maintain a certain flow and ensure we stick to the time boxes. Since people agreed that the meetings aren’t efficient but they wish to maintain a fun atmosphere I added a couple of fun cards. Below are the cards I use – feel free to borrow them.

Voting Cards

These are pretty self explanatory.

Agrees with the proposal

Agrees with the proposal

Does not agree with the proposal

Does not agree with the proposal

does not go to vote or does not cast a ballot

does not go to vote or does not cast a ballot

Questions Cards

I use these cards to control the flow of conversations. Before participants can talk, they need to notify the group about their intend. This also helps the facilitator determine if further questions or additional information is required about the topic being discussed.

I have a question

I have a question

The participant would like to ask a question.

I would like to add something

I would like to add something

The participant would like to add information to the current conversation.

I have a different topic

I have a different topic

The participant wants to raise a different topic than the one currently being discussed.

Behavior Cards

A fun way for people to comply to the rules of the meeting. Inspired by penalty cards used in many sports.

Yellow Card

Yellow Card

“it most commonly indicates a caution given to a player regarding his or her conduct” – wikipedia

Red Card

Red Card

“it most commonly indicates a serious offence and often results in a player being permanently suspended from the game” – wikipedia

Do you use facilitation cards? Do you tricks you can share with others?

Follow

Get every new post delivered to your Inbox.