Fast Growth Startups: Team Collaboration interview with aioneers
Find out more about why startup collaboration culture is a critical success factor for fast growth startups like aioneers and building winning teams.
Discover strategies to improve Objective Key Results (OKRs). Workplace Culture and Cross Team Collaboration can make your OKR process more successful.
When companies conduct their first OKR process, in almost all cases it is completely over-engineered, from the amount of objectives to the interoperability between each objective and key result.
So you’re an early stage company or preparing to scale. Awesome.
Your team is growing fast. Amazing.
You feel it is time to take a more structured approach with your company objectives. Great.
You have heard about OKRs. Excellent.
You think your first set of objectives should be all about profit, customer acquisition and funding. Ah. Okay. Hmm.
You think your teams are collaborating well…
You think your teams are highly engaged…
You think no-one is at risk of burnout…
You might need to think again…
An objective key result (OKR) is a process that a company can use to set business or strategic objectives, including the criteria and key results that will be required to achieve each objective.
For an early stage company or a company preparing to scale, deciding upon the right objectives from the myriad of feasible objectives can be overwhelming.
In its simplest form, company level objectives in the OKR process are intended to filter down through the entire organisation creating alignment through an overarching framework for mini goals, key results and individual actions that will ultimately contribute to the OKR process.
This theory is neither new nor groundbreaking, but we see it consistently presenting major challenges for startups by curtailing their ‘culture and agility’ when arguably they need it most.
A rigid OKR process can have a crippling impact by narrowing company vision and changing employee behaviors.
This can ultimately prevent your company from being nimble and fast-moving, instead leaving you hamstrung by objectives which creates disharmony.
These examples are just a glimpse of the potential problems that OKRs can cause for Startups, these can be further compounded by not having a solid data led decision making foundation and the ‘treadmill syndrome’.
The ‘treadmill syndrome’ suggests ‘you cannot out-exercise a bad diet’, this rings true for OKRs - ‘you cannot positively achieve a bad objective’.
Not only is workplace culture, agility and innovation threatened by OKRs, but we see the OKR process failing to deliver any positive impact on employee engagement, collaboration or productivity.
“OKRs can be harmful for startups trying to launch or scale, they can cause teams to chase a rigid objective without checking whether it is even the right one to start with.”
When you combine an over-engineered process with the potential impact on culture, agility and employee collaboration, a situation evolves rapidly that will prevent your company from even hitting one of your objectives, let alone hitting the minimum requirements of all your objectives required for the OKR process to be successful.
Every search engine will return hundreds of thousands page results on the reasons ‘Why companies Fail’. The elephant in the room however is ‘Premature Scaling’.
I have seen OKRs forced on companies as part of a funding cycle when preparing to scale, even though the funding partner has a very loose grasp on the culture of the company, what really makes it tick and what core factors amplify employee engagement, collaboration and productivity.
Think of it like going ten pin bowling, if an ‘Objective Key Result’ mindset is not already part of the fundamental culture of your company, then the first time your company implements an Objective based process it will be like bowling without the lane barriers, you chances of throwing a gutterball increase exponentially.
Through years of experience of working with successful startups, we would like to share some valuable considerations that will help you turn a potential gutter ball into a strike.
Personally, Individual OKRs are not a good objective to begin with, especially for an early stage company or a company preparing to scale, they are more often than not outright harmful.
At an early stage company, individuality should be encouraged and should be expressed through the actions each member is best positioned to take, but individualised actions must align to a single or small set of strategic company objectives.
If each individual is accountable for a different strategic objective, you create dilution and empower individuals to work in silos.
1. Use shorter cycles.
Don’t cookie cut an OKR process from another business, don’t be too rigid when reviewing your objectives. OKRs typically follow a quarterly cycle, but this is your company and your rule book.
Organization priorities by their very nature indeed change fast. But you need at least some level of certainty before setting off down an objective path.
2. Terminating the cycle and current strategic objectives.
If you gather new information based on target audience feedback or a market condition or a competitor and you want to pivot immediately or make a change to your product for value based reasons — that's ok for companies to do.
But proceed with caution, pivoting or product changes is likely something you won't want to do often. Arguably it would still be best for your team to finish the current objectives and measure the results. If you are considering terminating your current objectives then focus on data-informed decisions and empower your team to collaborate on situations or solutions that may occur.
If you decide not to finish your current objectives and measure the results, you might end up repeating the same activities albeit under a new set of objectives, so it is critical that everyone involved in an OKR process agrees that terminating current objectives is the best course of action.
3. Focus on learning and validating your startup ideas.
For early-stage and comapnies preparing to scale, the best set OKRs you can implement are objectives and key results that would allow you to learn from your customers quickly, validate this feedback as fast as possible and implement through team collaboration. If a key result doesn’t say ‘talk to x customers’ within an objective, your objective direction and foundation could be set up to fail.
4. Don’t underestimate cross-team collaboration power.
Really getting under the skin of how your team collaborates, but more importantly, understanding how better collaboration can amplify the positive results of your organizational objectives is potentially the single most critical success factor.
Before setting out any Objective Key Result structure within your company, ask yourself these questions:
Will my employee engagement and employee productivity be positively enhanced through an objective key result structure?
Do we have the right tools to do the right job and maximize the power of cross-team collaboration to achieve all our objectives and key results?
Interested to read more? Take a look at our recent article 10 ways of improving cross-team collaboration and alignment.
Find out more about why startup collaboration culture is a critical success factor for fast growth startups like aioneers and building winning teams.
Understand the benefits of cross-team collaboration and take our free cross-team collaboration assesment to identify improvement areas for your teams.
Improve meeting culture with meeting OKRs and Flowtrace analytics. Learn 10 examples to enhance productivity, engagement, and collaboration in...