On Cultural Competence In Product, Startup Success
By Avichal Garg (Co-Founder & CEO, Spool)
Core competence is a factor that cannot be easily replicated and gives the business a competitive advantage in delivering their product or service to customers. Core competencies are how a business does something; the lens through which opportunities are identified and evaluated. Cultural competencies are how a business figures out what to do. 
Every business, no matter the size, has cultural competencies.
- Cultural competencies are a reflection of the founders’ personalities. It’s no coincidence that Google was started and led by Ph.Ds, Apple by a designer-perfectionist and Amazon by a quant from a hedge fund.
- Cultural competencies are directionally set as you go from 0-20 people. If you achieve product-market fit, you will only deepen your cultural competencies. You can inject new culture via new (strong) leadership, but the existing leadership has to be receptive. The larger the organization, the harder this is.
- Product market fit is easier to achieve if you work with your cultural competencies, not against them. Often times when a company builds the wrong product, the market they are pursuing does not align with their cultural competencies.
- If you understand your cultural competencies, filtering potential opportunities becomes much easier. Be honest about whether or not the market you are pursuing can be won given your cultural competencies.
- Don’t emulate another company’s cultural competencies, as many do against Apple. Pursue a market through your own cultural competencies to create a differentiated (and more successful) offering, as Amazon has done with Kindle Fire.
How do Cultural Competencies develop?
Cultural competencies are an emergent property of people in an organization. It starts with founders who pursue ideas and markets they understand. If they get traction, they hire a team that thinks about the opportunity similarly (belief in the vision). If they achieve product market fit, they hire more people. These people then pursue scaling a business in the way that has worked best thus far, reinforcing the cultural competencies and world view. This yields more revenue, which results in more people hired to support that core business. At each iteration, the new hires cause a deepening of existing cultural competencies.
An example: Amazon vs. Google
Amazon and Google share core competencies. They’re focused on large data problems, machine learning, exploiting massive infrastructure, experiment driven monetization, and more. They have non-overlapping core competencies, as well. Amazon has phenomenal customer support and logistics, while Google has deep expertise in search and performance-based advertising.
Given their similar core competencies, no one should be surprised that Google and Amazon both pursue the smartphone and tablet markets. However, their approaches are dramatically different because of their different cultural competencies.
- Google’s cultural competence sees the world as signal and noise that must be filtered. A minority of the signal is commercially useful, and Google monetizes the shit out of it. This is how they manage to make money on search, email, and maps when few others can.
- Amazon’s cultural competence sees the world as a series of transactions on which it can build a platform. Amazon pursues opportunities that will facilitate repeated transactions and then builds the platform to own all of these transactions. The Kindle was made to drive the sale of digital books. Free Shipping and Amazon Prime are levers to drive more sales on Amazon. It’s all about increasing and owning transactions.
How Cultural Competence Skews Perspective
- For Google, Android is the key to owning mobile search and ads. Google’s cultural competence perceives Android as a moat for Google’s castle — search and ads.
- For Amazon, Android is about selling more video content, pushing Amazon Prime (which results in more sales on Amazon.com), and the Amazon Android Market (a digital goods store). Amazon’s cultural competence sees Android as a platform to enable more commerce and monetize directly.
Same platform, yet dramatically different perspectives, and ultimately different ways to extract value out of the ecosystem.
How Cultural Competence Impacts Product Success
It is not a surprise that Google makes a small amount of money directly from Android. Google’s cultural competence does not align with what the market demands from a direct monetization product — Google Wallet, Checkout, and the Play Market are examples of how Google fails because their cultural competence prevents them from building the right product.
For example, Google has rich analytics in the Android Developer Console and has search baked into the core Android experience. Given their cultural competence, it makes sense Google would prioritize these features. At the same time, the platform has no subscription billing and has yet to create a seamless integration of apps and content, 9 years after iTunes revolutionized digital content delivery. Google’s cultural lens has led them to either build the wrong product or be unable to come to a decision about what the right product is for a direct monetization market.
Meanwhile, Amazon has had no problem defining a transaction platform because of their cultural competence, and they execute on this market opportunity efficiently because their core competence is building transaction based products. Amazon has demonstrated this in multiple markets.
Google’s lack of direct monetization from Android is not a surprise. Apple’s lack of monetization via iAds is not a surprise. Amazon’s lack of monetization through auctions is not a surprise. 
Hosting platforms are another great example of how cultural competence skews outcomes. Amazon looked at Amazon Web Services the way they look at their retail site. Find the simplest set of things people will buy, then broadening out to related offerings. They manage inventory, demand, and have efficient pricing. Amazon figured out what developers wanted (S3 and EC2), sold it to them, and then expanded the offerings.
Google’s cultural lens skewed their perspective towards thinking that what developers want is the most efficient way to manage large amounts of data and not worry about scaling. Most businesses don’t have Google scale problems and don’t want Google’s internal platform approach to manage their non-Google problems. They need something that works with existing (open source) systems and leaves them the freedom to customize infrastructure. Google tried to apply it’s cultural lens to a market, rather than find a market where it’s cultural competence would give it a competitive advantage.
Hosting is fundamentally a retail problem, not a signal vs. noise problem. Amazon Web Services does $1 Billion in revenue and Google has been tweaking App Engine for years. This is a prime example of how to filter opportunities and pursue ones that align with your cultural competence.
3 – Examples of Cultural Competence Failure
Companies that have a strong cultural lens will stay focused and thrive. Those that dilute their cultural competence die because they lose a very important filter for which ideas to pursue and how. Companies that try to build outside their cultural competence tend to fail as well.
- Apple – Apple’s cultural competence is finding large industries full of geeky products and Apple’s core competence is building simple, cool status symbols in their place. Laptops, desktops, phones, and music players are all examples. Ping (their music social network), MobileMe, Pages/Keynote/Numbers, and iTunes are great examples of where if the product succeeds by piggybacking on their hardware business, not because it’s a great in its own right.
- Facebook – Facebook’s cultural competencies lie in identifying opportunities to enable sharing. Every software, app, or platform upgrade is about fostering more connections and data flow between people. Facebook sees markets as an opportunity to get users to share more, find out more about their friends/connections, and elicit relationships (family, friends, worked with, who likes whom) that were previously unknown. When they try to extend this into another area, like daily deals, they don’t do well. Daily deals are not about the relationships between peers, they’re mostly about Facebook’s relationships with merchants.
- eBay – has core competencies in peer-to-peer transactions (sometimes with goods changing hands). eBay’s cultural competence is around bringing groups of people together into a marketplace and getting them to trust each other and the marketplace. When they diverged from this (Skype, StumbleUpon) they failed. When Skype and StumbleUpon spun out from this cultural lens, they thrived. When eBay applied their cultural competence to Paypal, it worked beautifully because Paypal is fundamentally a trust network.
- HP – has core competencies in manufacturing, distribution, and enterprise sales. What is their cultural lens? How does HP decide what opportunities to pursue and how to leverage its core competencies? They’ve floundered on this for quite some time.
- Microsoft – has core competencies around desktop software, business applications, and selling through enterprise distribution channels. Their cultural competence has always been finding ways to make businesses more efficient with their PCs. They make a healthy profit in their servers and tools division since this aligns nicely with their cultural lens. Every time they stray away from this cultural competence, they struggle. Signal vs Noise businesses (Bing) burn cash and Entertainment (Zune, Xbox) operates at break even.
This post was originally posted at Avichal Garg’s blog.
About the guest blogger: Avichal Garg is Co-Founder and CEO of Spool, a personal Internet recorder that allows a user to download her favorite Internet content to any device and share it easily with friends. Previously, Avichal was a product manager at Google, where he worked on Search Quality and Ads Quality. He holds a B.S. in Computer Science and M.S. in Management Science, both from Stanford University. Follow him on Twitter at @avichal.