Leadership and management practices at Google

Google: Leadership vs. Management

In assessing how Google has been able to succeed in intensively competitive industries including online search, advertising, and providing licensing of their technologies for use within corporations and governments globally, their leadership and management practices need to be taken into account. The intent of this paper is to analyze how the differences in management vs. leadership within Google significantly influence their ability to attract, retain, challenge and ultimately give their employees an opportunity to grow personally and professionally. The culture of Google is nonconformist to the traditional software company, concentrating more on giving employees freedom to pursue their own projects up to 20% of their work time (Taylor, 2009). Called the Rule of 20% Time, this practice is now responsible for a significant 50% of all new products for the company (Taylor, 2009). Microsoft has on the other hand relied more on a top-down hierarchy with clear yet at times inflexible lines of authority (Anders, 2007). To manage such a nonconformist and non-traditional approach to the development of Internet services, software development, and rapid application development takes a very unique leadership and management mentality. This paper examines and analyzes why Google continues to be successful at innovating despite their exponential revenue and employee growth.

Managing vs. Leading at Google

Microsoft and Google differ significantly from one another in many areas of management and leadership, yet both cultures' reliance on Expert Power (Humphreys, Pryor, Haden, Oyler, 2009) force these organizations to defy traditional, top-down, hierarchical management structures. They simply do not work when each company must have continuously greater levels of creativity and innovation fueling new products and services. This is a result of team structures moving from being hierarchical to more network-based, and cross-functional in nature over the last two decades (Bennis, 1999). In addition, Expert Power in managers and especially leaders implying greater competency and charisma (Humphreys, Pryor, Haden, Oyler, 2009) has translated to less of a reliance in these company's cultures on a given manager's title or experience level. Of the two, Google has been the one to more pervasively internalize into their culture the role of a leader as an active member of a project team who not only directs, but also assists in the completion of complex projects (Hof, 2008).

From this analysis of the Google culture it is clear that management has more to do with the fulfillment of administrative tasks, functions and processes being enabled, and leadership is much more correlated to the project creation process. A leaders' foundation for effectiveness in the Google culture is based on a platform of credibility that is earned from Expert Power and kept by instilling trust and transparency with team members. This is consistent with the core concept of what makes an effective leader as defined by Bennis (1999). What makes leadership difficult in any company however yet even more so in Google is the fact that for any leader to be effective, their personality, who they are in effect, must be aligned with the needs of those they manage if they are to excel in their role (Maccoby, 2009) (Bennis, 1999). As a result of this critical aspect of leadership in their culture, it is common for Google to hold several interviews with candidates to ensure they have the technical aptitude and also the ability to potentially lead as well (Shipman, 2006). Not only does this hiring process ensure a higher level of technical competency, it also provides Google senior management with a more readily available group of potential technical project team leaders in the future.

For a project or team manager to be effective as a leader in Google they need to quickly get beyond the traditional roles of management, which typically encompass planning, organizing, leading and controlling. This reliance on Legitimate Power is a waste of time for any manager in Google if they hope to get anything accomplished with their teams. Instead, as the research for this paper indicates, a manager can transcend their traditional role and become a leader by concentrating first on earning and keeping the trust of their team members (Maccoby, 2007) and by seeking to create more collaborative groups structures and approaches to attaining shared goals (Bennis, 1999). This is admittedly quite complex and very difficult to do in a company known for hiring the most analytical, intelligent, skeptical and questioning engineering talent available. The common purpose of a project team and its accomplishment must be internalized by each team member if it is to be attained (Bennis, 1999). At Google, managers who transform themselves into leaders have this ability to gain the collaborative efforts of their teams through credibility and rewarding team members with rewards relevant to them. The leader as servant becomes a critical part of success for anyone leading a team at Google; they must know and understand the needs of those who work for them. This includes the need for recognition, need for mastery of a given area, and most critically for Google's engineering and development talent, the need for professional respect as being the best in the industry at what they do. Leaders in Google must do this while at the same time keeping clarity in place with regard to roles, setting the expectation that individual and team performance will be exceptional always, and that both the team and the leader don't evade problems or challenges, they face them. All of these factors together will over time create a level of transparency that fuels the relationship between leaders and team members (Maccoby, 2007). All of these factors combined then form the expectations and foundation of a leader in Google vs. A manager. The differences are significant and make the difference if a team or project manager lasts in the culture or not. Given how extensive the recruiting process is in Google and fact that the most common reason employees leave a company is due to their manager, Google has been known to seek advice on how to get rid of bureaucratic managers for fear they will lose valuable employees as a result (Maccoby, 2009). Leadership is much more difficult to attain in Google, yet its results speak for themselves, with the company being one of the most prolific in terms of generation new product ideas than any other in its comparable short history.

Recommendations for Creating a Healthy Organizational Culture

For Google, their greatest challenges lie ahead, in addressing the enterprise market for their solutions, while at the same time being the search engine of choice for hundreds of millions of people globally. This dichotomy between the need for a more rigid and hierarchical structure to address the unmet needs of the world's larger corporations who seek to standardize on Google technology and hosted applications is contrasted to the wide-open, creative organizational culture of today that thrives on the rule of 20% generating new product ideas that serve literally millions daily (Anders, 2007). Navigating between these extremes will require the company to consider the following two recommendations.

First, as the company is known for having a highly analytical culture where development is quantified at each stage and even the projects generated during the 20% time of employees is measured, Google needs to take the enterprise-level (or large corporation) needs list and prioritize it, and then put incentives on the top fifty of these unmet needs. The pay-off for solving these top fifty problems is the potential to completely run a separate division of Google solely focused on the enterprise marketplace. The intent of this division is to concentrate on creating entirely new products in response to these unmet needs, with the incentive being what many engineers and technical professionals value most, which is autonomy and the opportunity to spend even more than 20% of their time on their projects of interest. The level of competition this would nurture exceptional levels of creativity and would through the selection process find the most qualified staff members to run the new division. The key aspect of this recommendation is that it sets the foundation for highly effective leadership both from a collaborative standpoint as defined by Bennis (1999) and it also will quickly define those members of the development teams who have the technical competence to earn trust and credibility (Humphreys, Pryor, Haden, Oyler, 2009). As the enterprise market is one that has not nearly been addressed well enough by Google, this strategy is critical both from a strategic as well as a management standpoint.

The second recommendation is to consider the practices Sony and other Japanese manufacturers rely on for their rapid pace of innovation and new product development, and that is to have the engineer who created the new product or service "own" it through the entire validation process. Typically in Google today a new product concept is eventually forwarded to Marissa Myer, Vice President of Product Development (Hof, 2008) for review and eventual presentation to the senior management team. In Sony's culture a more egalitarian approach was envisioned by the company's founder since the outset, and it has proven to be successful in finding those product champions who will work the hardest to make a new product a success. This approach would also have within it the opportunity for recognition and one of the most valued aspects of the Google culture, autonomy and freedom to pursue ones' passion. Organizationally this would also allow for even greater levels of cross-collaboration and team orientation as those with ideas that got past the screening process could potentially lead to entirely new project teams. For Google to succeed over the long-term it must continually grow those innovators they have hired, giving them the chance to experience the autonomy and freedom of attaining their visions of new products over the long-term.

Conclusion

Google is an anomaly of American corporations given its rapid, explosive growth and the ability of its culture to nurture and promote innovation using The Rule of 20%. The management and leadership challenges in such a rapidly growing organization have been discussed in this analysis, with an orientation into what differentiates their unique leadership approaches. The global reach of Google is far beyond being for the lowest cost per programming hour, with a strong concentration on having future products reflect cultural, regional and religious variations between nations. This practices makes the company pay attention with great levels of focus on how regional variations can contribute to their strategic performance. Comparability speaking Google appears to have an appreciation of the tenets of the Cultural Dimensions Model (Hofstede, 1983) and its implications on global growth. The most challenging aspect of the company's future however is in the area of transitioning to sell more into corporations and enterprises when its development teams and approaches are more oriented towards applications and services that can be readily used by millions of people globally ever day.