Day one within any startup represents a blank canvas. You decide your company name, brand, website URL, and the type of product you’re building.
Another bonus of building your own business? You get to pick the people with whom you’re going to work with to get all of this done. All of this will ultimately shape your company culture, whether you purposefully and actively build your culture or not.
We know that a company’s culture is important; it is what keeps the team happy, helps attract top, new talent to the team, and it will have a significant influence on interactions with stakeholders.
Having a bad company culture albeit an excellent company in all other respects (superb product, successful marketing, etc.) is literally like having one bad apple in a box; it will eventually spoil the rest.
If you need a reminder of what bad culture looks like, consider all of the recent negative press that Uber has received. Regardless of how you would like to define or label their culture, it was a culture focused on growth at all costs. The recent revelations though have seen Travis Kalanick leave his position and the company reportedly losing an estimated $10BN in market cap.
While these revelations just came to light recently, some quick research shows that there has been some recurring trend related to questionable behaviour from Uber for years. The negative press has just been a lagging indicator of a bad company culture.
When you are just starting up, company or team culture is yet another thing that is on your to do list for survival. While most founders are paying more attention to culture sooner, this is often limited to recruitment where the focus has shifted slightly from hiring “people with skills” to “people over skills”. This is often not enough to create a sustainable, wholesome culture.
Jason Cohen, co-founder of WP Engine, says: “Every company has a culture. The only question is whether or not you decide what it is.”
In this article, I will share how my team and I defined our culture on Day one, but then evolved it as our team and the reach of our business grew. The approach we took can be best described with a borrowed and slightly-adapted term: Minimum Viable Culture.
At the outset, there are many things for which you will not have answers. And your company culture will be one of them. You should, however, draw a line in the sand and give yourself some point of reference from which to work. It doesn’t have to be perfect; it just needs to be something to which you can point.
Interestingly when I founded Conversio, my point of reference was a simple list that I had scribbled down in my notebook after I had exited WooThemes a year prior.
The list was simply titled “Things I will not do in my next company” and was my retrospective of things that I would like to change in future startups and teams.
At WooThemes, the culture was more something that happened to us; my co-founders & I were younger and inexperienced in leading a team.
Based on that list and inspired by the likes of Buffer and Hubspot – who had published their respective culture codes – I created a simple list of ten values that would make up Conversio’s first culture code. Two considerations influenced these values at the time:
As I started the search for our founding team members, these values were a prominent part of the recruitment process as they were included in all of the initial job listings and successful candidates had to accept them alongside their decision to take a position on our team. This is an example of one such acceptance email from our early days:
The benefit of this is that it shapes the collective awareness around certain ideas; the most important one being that every individual will be joining a team that will pursue our commercial goals that align with a set of values. This is about setting the stage, and you can see that also in the way that I had communicated in the above email.
At this stage in your journey, it is not about having clear values or a visible culture; it is just about agreeing that you will purposefully build your company’s culture.
You are now at a stage where the wheels of your startup are beginning to turn nicely; you might have a public product, your first users/customers and some things you are learning about has accelerated considerably. This also means that your operational to do list has grown significantly which could put softer considerations (like culture) on the back burner.
In an effort of keeping culture at the top of our mind, we scheduled our first team retreat about six months after the team first came together and four months after we had launched the first version of our product. The five of us had been building our internal relationships and workflow, were acquiring new users at a nice pace and had just decided to raise our seed round of funding.
I can remember our first retreat was quite an unexpected experience for me. At WooThemes our annual retreats, for example, had a prominent boozy culture, whereas Conversio’s first retreat had a distinct lack of alcohol. Alcohol aside, I realized that my expectations of what our business culture could (or should) be would need to be fine-tuned with the help of this team.
Even though I had tried to recruit individuals with a focus on who they were instead of merely what skills they could contribute to our startup, the truth was that no recruitment or interview process would make us all know each other fully immediately. For us to define and to create a culture based on our collective values, we would need to get to know each other better.
That first retreat was the first time that we re-visited the original culture code I had created. We discussed what culture could mean to us relative to that initial code, but also alongside the things we had learnt working together the previous six months. Since we were also starting to raise our Seed Round, we could also consider the kind of company that we wanted to build in the long-term.
This discussion helped us identify the bugs that we would need to consider and fix going forward. It also revealed some of our strengths that we could use as opportunities for future growth.
One of these strengths we embedded in our decision was to be a fully distributed and remote working team. We had managed to find the majority of our initial team through We Work Remotely and this became one of the first clear things to which we could point to help us grow the team.
The reason something seemingly simple like a particular job board helped us, was because it highlighted a possible strength and made it an explicit value to pursue. It helped serve as a filter and attracted a certain kind of individual (that was experienced in and keen to work in a certain way.) To this day, we have found about three-quarter of our team through We Work Remotely and this “strength” also evolved into one of our core values: Independence.
In product design, we often speak about product-market fit; the moment when you have built your product in such a way that the market considers it a solution to their wants or needs. Once you reach this point, your operation mostly shifts beyond learning how to get to this point and more towards doing more of the things that have helped you get here.
Building your culture in an MVP-esque way will also lead you to the point of team-culture fit. I would define that as the moment where the team can define – and put into words – a significant part of your culture.
For us, this happened on our second team retreat, about 15 months after we first started working together, when we were ten team members. Here we prioritised a big discussion specifically about our culture with the exclusive aim of coming up with a concise definition of our culture. It is that our “Life- and Family-First” Culture properly shot roots with five core values: Passion, Curiosity, Independence, Honesty and Rebellion.
These were the values that we agreed most clearly defined both the way that we had been working until then and also how we wanted to work and act in future. This felt like a good representation of who we were and wanted to be. These values – while refined – were also consistent with the original culture code that I had written, which was proof that a bigger framework of related values had been influencing our behaviour and culture until now.
In the months following this, we often had discussions – only sometimes proactive – where our values would pop up into the conversation. One such discussion, for example, led to us creating a better maternity – and paternity – policy. Or I can remember a conversation about a possible second round of funding where we decided that it would limit and challenge our future independence; so we didn’t pursue it.
What I found is that once we were able to define our values concisely, it was easier for us to identify specific things that we could implement to build out our culture. One example was our paternity policy. Another was how we changed our unlimited holiday policy to a required minimum holiday policy (to remove any guilt around taking time off and encouraging our team mates to take more time off).
This part of the process is all about identifying the things that were working and doing more of that.
In Start with Why, Simon Sinek proposes that more companies should align the things they do with their “why”. He explains this using this diagram:
Using other words, your “why” is best manifested in your value and culture. As your company and team grows, you want to keep growing the prominence and significance of that inner circle. You want your culture to permeate everything you do; be the North Star for all your decisions and actions.
Culture is something that will continue to evolve as you grow the team because every additional individual will be adding their unique personality to the mix. As the company grows, macro considerations will also set new challenges or requirements of you and your team. In this sense, your culture is liquid, and like moving water, it does find a way through all cracks.
Here is a couple of things that we have done to both maintain and evolve our culture as we mature:
The title of this article promised to give you a map to building your culture in the pursuit of global success.
I believe I had made the argument of why culture matters and at the very least – using Uber’s example – highlighted the risk of having a bad culture.
The truth is that culture – on its own – is not the thing that will bring you success in whatever way you may define it for yourself and your team. Building a successful business requires many different things to work well. Culture is, however, the pulse that influences every one of those things.
Let me explain with a personal story. I recently took ten days off to travel to Iceland with my wife. During this time, I switched off all of my email and Slack notifications; and I left the team to guide our ship.
The only reason that I could do this without an anxiety needing to check in or influence a decision was that we had a defined culture. Our team might use buzzwords like “cost-benefit” or “Adii%” (our definition of MVP) to describe my perspective on most decisions, but the fact that these are known reconnects all decisions and actions to our values and culture.
And crucially this happens with any one of us being exclusively responsible for this. Our culture is our hive-mind.
If scalability and repeatability are two attributes that startups pursue on their path to success, building a culture is one of the best things you can do.
Once defined and clear, your culture becomes the ever-present framework within everything in your company happens. People, products and market conditions may change, but your culture is the one constant that will continue to drive you forward to success.
Also worth a read: Conversio On How To Build a Great Company Culture
This is just a small sample! Register to unlock our in-depth courses, hundreds of video courses, and a library of playbooks and articles to grow your startup fast. Let us Let us show you!
Submission confirms agreement to our Terms of Service and Privacy Policy.
Already a member? Login