Analytical-Mind
A blog offering new paradigms to improve performance and quality of life at work.
  • Home
  • About Me
  • My Virtual Bookshelf
  • Contact Me

All Posts Tagged Tag: ‘culture’

Is it better to work for a small organization or a large one? 0

There obviously isn’t a clear and straight forward answer to this question. The answer depends on the perspective of the person you ask and what they value. After working 10 years in corporate America, I came back almost 3 years ago to work for a smaller organization (less than 100 employees). Two of my colleagues (Yves and Ida) also recently made the switch. We got together to exchange our thoughts on why we believe working for a smaller organization is better for us.

Martin: You have spent a large part of your career working for large organizations, what struck you when you joined Pyxis?

Yves: One first obvious observation goes along something I experienced before in a young publicly traded technology startup (less than 100 employees). For a given amount of effort you invest towards an initiative, whether on a individual scale, with a group or at the enterprise-wide level, your ROI (Return on Investment) is quite higher in a small organization than in a large one. The outcome on the initiative may end up being very successful in both environments, but in the small organization context:

  • The decision-making process will be faster and will involve less people;
  • The frequency at which you will be able to challenge and refine a set of actions on your initiative will be higher. Furthermore, your chances for celebrating at the end increases accordingly;
  • The whole initiative will execute at a faster pace and will complete sooner most of the time. Hence, a key variable inducing a positive impact is the reduced number of hand-offs between departments or people.

Ida: The first blatant differences I noticed were the lack of anonymity (you don’t feel like a number) and the lack of rules and regulations. The lack of anonymity puts you out there right away and is an enabler to allowing you to contribute and make a difference right off the bat. The fact that there aren’t many rules and regulations can also help in allowing you to make that difference faster, with no red tape to slow you down in your tracks.

Martin: Changing organization is an important decision that is usually done without having all the information. In hindsight, what information would have allowed you to make a better decision?

Yves: Organizational culture; without a doubt! Although I usually spend as much time being interviewed as making my very own due diligence on the organization, culture remains the number one factor for which you never get enough insights.

In an interview process, I do take extra care at being very transparent and straightforward on my value proposition. I do expect the same in return from the organization; and it is usually the case. However, the organizational part of the equation is far more complex than one individual being interviewed; putting everything he or she has on the table.

In hindsight, I do realize that most of my career changes would not have been different with more organizational culture intelligence at hand, so, same decision at the end. But gathering more info on that side of the story allows you to prepare yourself much better for the ‘culture tango’ coming at you.

Ida: From my perspective, I don’t feel that any additional information would have helped me make a better decision. The decision was a good one because of my mind set. I was ready for a change. I knew that a change in company or industry wouldn’t cut it, it had to be a bigger change of sorts, and ironically the BIG change translated into moving to a SMALL, privately owned company.

Martin: Many people who join smaller organizations feel more appreciated and a stronger sense of contribution toward the organizational goals. What are your thoughts on these?

Yves: Most of your actions in an smaller organization are very visible; for the better or for the worst… This allows you to have a positive impact towards your colleagues and the enterprise itself, without seeing all your efforts being diluted inside complex chains of commands, large hierarchies and impractical politics.

So, the visibility factor brings more appreciation and a stronger sense of contribution most of the time. It is actually a key attribute of smaller organizations, from my own point of view. This stimulates people at performing towards excellence, knowing their chances of being recognized for their hard work are quite high.

Ida: In a smaller organization, the impact is immediate. A decision can be made and an action is put in place. The lack of heavy hierarchies means that each individual is much more empowered to get things done and not necessarily have to wait for various levels of approvals as in large organizations. This empowerment is motivating, energizing and stimulating.

Likewise in a smaller organization, the breadth and depth of one’s responsibilitiesis usually much wider than in larger companies. This in itself provides additional satisfaction since people are not «boxed in» to a role that is strictly defined, allowing them the latitude to spread their wings.

Martin: What do you miss about working in a larger organization?

Yves: Sometimes, smaller organizations are facing challenges less prevalent in larger ones. For instance, financial stability may be a focus discussed over a monthly, or even over a weekly basis in a small company. Whereas in a larger organization, these matters will be discussed less often and more upon large-scale changes like restructuring plans and/or financial results being bellow expectations.

Furthermore, larger companies are having less of a hard time raising capital for their growing needs; in comparison with smaller organizations which are struggling a good deal in order to maintain an attractive balance sheet for banks and venture caps.

I still remember those funny days about 12 years ago; when it was so easy for startups to raise literally millions of venture cap out of PowerPoints or based on theoretical MBA classroom business cases. Hopefully these days are gone and we all now raise money based on common sense and sound financial practices. This however, illustrates how difficult it can be for a smaller organization to secure its financial future in 2011.

Ida: My answer to what I miss about a large organization is a two part answer, and each part contradicts the other, let me explain. Similar to Yves reply, financial stability is the most noticeable aspect that I miss. The luxury of knowing that there are enough funds to pay all expenses when they come in, invest in projects, expansions, acquisitions, etc. and be around in the long run, fosters an environment of growth, possibilities and positive reflections, in theory.

I say, in theory, because the existing reality in most large corporations, even though highly profitable, is the continual squeeze to do more with less. Hence the pressure is such that you are never profitable enough. It becomes an endless race. Factor into this internal pressure, pressures from the market and shareholders, legislation, the economy, and so on, and it becomes the endless race with umpteen hurdles. This is the part that I don’t miss, but it is very much tied to that financial stability I spoke of above.

Martin: Thank you Yves and Ida for sharing your thoughts on this topic. This was an interesting exercise. We may do this again in the near future.

Posted on: 03-14-2011
Posted in: Agile Leadership Model, Leadership, Organizational Structure, Perception

Interesting blog posts (January 22, 2010) 1

On the importance of creating the right organizational culture (Thanks to Andrew)

By the time we got to 100 people, even though we hired people with the right skill sets and experiences, I just dreaded getting out of bed in the morning and was hitting that snooze button over and over again Corner Office – Tony Hsieh of Zappos – Celebrate Individuality – Question – NYTimes.com.

On why an Agile approach is better suited to deliver value (Thanks to Alfonso)

Most organizations that depend on software are struggling to transform their lifecycle model from a “development” focus to a “delivery” focus. This subtle distinction in wording represents a dramatic change in the principles that are driving the management philosophy and the governance models – Improving Software Economics

On the meaning of Agile transformation for managers

What many people mistakenly do is equate agile project management with doing more work, with less documentation and fewer people. Although the premise is to get more done in a more favorable way, I have never met a team that could successfully implement agile principles without having to slow down first - VersionOne – Agile Adoption For Managers.

On the fact that the true value of an organization is not mapped via its organizational chart

But it’s not the fact that you have many more boxes and lines that I’m most envious of.  It’s your “white space” I want – Oh, Yeah? Well, My Org Chart is Bigger and More Beautiful Than Yours!

On the need to manage self-organized teams when required

The interesting thing is, the further we go into agile management territory the less typical the managerial job we expect. Teams are self-organizing and cross-functional, and sometimes we think a manager should just get out of the way. By the way, surprisingly often this is exactly the best choice. But whenever one of the asshole-moments is needed, it is time to show up and do what has to be done. Otherwise the atmosphere starts rotting as people wait for someone who will fix things. Someone who will do something about this guy adding a new technology every time he reads some nice article. Someone who will deal with that lass taking a few days off because she doesn’t really care about the project being late and the team working their butts off to get back on the right track. That’s always a job for a manager, and a harsh one, no matter how self-organized the team is - Good Managers Sometimes Have to Play Assholes – NOOP.NL.

Posted on: 01-22-2010
Posted in: Agile, Leadership, Management, Organizational Structure, Other Blog Posts, Transition to Agile

Do you know why you show up at work every day? 0

Inspired by a colleague, I recently decided to document my reasons for showing up at work on my personal page of our company’s wiki. A few people “copied” the idea and told me it helped them crystallize their purpose and helped them focus on their contribution toward the success of the organization. Some of them told me others outside our organization might be interested in this – so here it is. There is no copyright on the content ;) so feel free to use it.

My dream for Pyxis

Using varied and innovative approaches Pyxis substantially increases the level of performance of 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.

My personal commitment

In line with the vision, mission, values and culture of the organization, I pledge to exercise strong leadership, to ensure the sustainability of our operations and to support the organization’s growth by deploying efforts and resources needed to achieve the objectives.

My reason for being

In line with my personal commitment to the organization, my goal for the next 24 months is to act primarily on the following 4 vectors:

  1. Establish an Agile Business Intelligence consulting practice.
  2. Participate in the sales and marketing process for our products and services.
  3. Lead the definition and implementation of our corporate strategy.
  4. Support the development and capabilities of my “golfers” through the Caddy process.

My commitment as the owner of the strategic process

I promise to take the leadership and work with all interested individuals in the establishment and implementation of a corporate strategy allowing the organization to achieve its objectives and its mission.

My commitment as a caddy

I am unwavering in the individual success of my players, my caddy and the caddy team.

Posted on: 07-27-2009
Posted in: Leadership, Management

Popular Posts

  • Agile self-organized teams - is the team self-organized or not?
    01-25-2011
  • Agile transitions are hard. I wonder why people feel the need to control?
    10-5-2010
  • Which stance should I take? The 4 quadrants of Agile Managers
    12-20-2010
  • My Virtual Bookshelf
    01-24-2011
  • What is the job of the president in a self-organized company?
    10-18-2010

Blogroll

  • Agile Gardener – Gardening Agile Knowledge
  • Great Leadership – Opinions and information on leadership and leadership development by Dan McCarthy
  • John Baldoni On: Leadership, Leadership development, Managing people
  • Management 3.0 – Leading Agile Developers, Developing Agile Leaders
  • Management, Development, Complexity, and Me
  • Marshall Goldsmith On: Leadership, Managing people, Coaching
  • Pyxis Technologies
  • Umuntu – It's all about people and humans, anyone at all …
Avatars by Sterling Adventures
Recent Posts
  • Analytical-Mind has moved
    08-10-2011
  • Adapting your leadership style to the maturity level of your self-organizing team
    08-9-2011
  • Agile managers do not act like cowboys
    08-1-2011
  • 12 tips to be a better coach
    06-20-2011
  • Gartner's Enterprise-Class Agile Development Defined
    06-6-2011
Recent Comments
  • links for 2011-08-14 « Dan Creswell’s Linkblog on Adapting your leadership style to the maturity level of your self-organizing team
  • Michael cardus on Analytical-Mind has moved
  • Making The Entire Organization Agile | Pyxis blog on The myths of self-organized teams
  • Making The Entire Organization Agile | Pyxis blog on Yet Another Agile Maturity Model (AMM) – The 5 Levels of Maturity
  • Adapting your leadership style to the maturity level of your self-organizing team | Analytical-Mind on Seven wrong reasons to adopt Agile
About Me

Meta
  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org
© 2008-2011 Martin Proulx