Most founders introduce prioritisation frameworks too late. Not because they do not think of it, but because structure seems at odds with the mindset of the early years. We move fast, we adapt, we pivot. Putting OKRs (Objectives and Key Results, a system for setting and tracking priorities through measurable objectives) or RICE scoring into an organisation of fifteen people feels corporate. It feels heavy.
That reasoning has a cost. When scattered focus sets in, with too many projects running in parallel, too few finished, resources diluted across twenty simultaneous fronts, it does not show immediately. It shows three quarters later, when the team is exhausted and growth slows for no obvious reason.
The question is not "should we structure prioritisation?" but "at what stage, and with what?"
Scattered focus: the most common problem and the least visible
In a growing organisation, the number of opportunities rises faster than the capacity to handle them. Every team has its projects, every manager their own priorities, every quarter its new ideas. The result is predictable: many workstreams open, few actually completed.
This phenomenon is hard to spot from the inside. Teams do not feel disorganised: they feel overloaded. The distinction matters. Being overloaded is seen as a sign of growth, when it is often a signal of a prioritisation deficit.
The consequences are concrete. High-impact projects wait while secondary projects tie up resources. People lurch from one emergency to the next with no clear view of what matters most. And prioritisation decisions, for lack of a method, systematically escalate to the founders, who become the bottleneck of their own organisation. This is precisely the stage at which the operating partner can play a decisive role: making the diagnosis and creating the conditions for a transition towards more structure.
What prioritisation frameworks are not
There is a persistent confusion around OKRs, RICE and other structured methods: they are associated with the rigidity of large groups. This confusion leads either to introducing them too late or to introducing them too heavily, with endless planning cycles, complex spreadsheets and an administrative overhead that exceeds the value produced.
A prioritisation framework that is well used does not make the organisation rigid. It reduces noise. It lets every team know, without having to ask, what is a priority this quarter. It avoids endless meetings to arbitrate between priorities. And it creates an organisational memory that survives changes of team, a particularly sensitive issue in post-acquisition phases.
What the frameworks replace is implicit, informal prioritisation, which exists in every organisation but creates uncertainty because it is never formalised.
Which framework, at which stage
There is no universal answer, but a few rules of thumb hold in most cases.
Below ten people, informal prioritisation works. The team is small enough for the founder to align everyone in real time. Adding a formal framework at this stage creates more friction than it resolves.
Between ten and thirty people, written documentation of priorities becomes necessary. Not yet a full OKR system, but at the very least a clear list of the three to five topics that matter this quarter, visible to everyone. The RICE method can be useful here for product teams that have to choose between competing features: it forces you to quantify impact, reach, confidence and effort before deciding.
Beyond thirty people, OKRs become relevant. At this stage, strategy can no longer be aligned through physical proximity. You need a system that translates company objectives into measurable results at every level of the organisation, and that lets each team see how its work contributes to the whole.
The most common implementation mistakes
Introducing OKRs too late is a problem. Introducing them badly is another. Several mistakes come up every time.
The first is to define OKRs only at founder level, without involving the teams. OKRs do not work as top-down directives. Their value comes from collective ownership: teams that define their own Key Results from the company objectives commit to them differently.
The second is trying to cover every project. That is not the aim. OKRs should concentrate on the two or three issues that genuinely define the quarter, not the entire backlog.
The third, identified in several experience reports from French startups such as Dashlane, is excessive purism in the initial approach. The first OKR cycles will be imperfect. That is normal: the method is built over time, not from the first quarter.
Written documentation: the first step before frameworks
Before even implementing OKRs or RICE scoring, there is a simpler and often neglected step: writing the priorities down.
A shared document listing the three priority topics of the week or the month, updated regularly by the founder or the managing director, already changes the dynamics of a growing team considerably. It reduces requests for clarification, avoids misunderstandings about what is urgent and what can wait, and creates a common anchor for day-to-day decisions.
It is the recommended entry point before investing in a more structured system. Written documentation disciplines executives' thinking as much as it informs teams.
Conclusion
Scattered focus is not an inevitable part of growth. It is the result of prioritisation that stays informal for too long. Introducing structured methods, even simple ones, even imperfect ones, preserves the organisation's capacity to execute as it grows.
The right moment is before scattered focus starts to cost you. Not after.
Key points
- Introducing structured prioritisation early is not a matter of company culture: it is a matter of preserving the capacity to execute as the organisation grows.
- Scattered focus is the most common and least visible problem in growing organisations: it sets in gradually, while everyone thinks they are making progress.
- Prioritisation frameworks do not make the organisation rigid: they replace the informal, implicit prioritisation that creates uncertainty.
- The right entry point is not necessarily OKRs: written documentation of priorities is an accessible first step from ten people.
- OKRs become relevant at around thirty people, when strategy can no longer be aligned through physical proximity.
FAQ
At what headcount should a startup introduce OKRs?
There is no universal threshold, but most practitioners place the right moment at around thirty people. Below that, written documentation of priorities is generally enough. Beyond it, strategic alignment can no longer rely on proximity and informal exchanges.
What is the difference between OKRs and RICE?
OKRs (Objectives and Key Results) are a system of strategic alignment across the whole organisation. RICE (Reach, Impact, Confidence, Effort) is a scoring framework for prioritising features or projects at product-team level. The two are complementary: OKRs define where to go, RICE helps decide what to do first to get there.
How do you stop OKRs from becoming a bureaucratic constraint?
By limiting the number of OKRs (two to three per team at most), involving teams in defining them rather than imposing them from above, and accepting that the first cycles will be imperfect. OKRs are a method that is built over time, not a system to be deployed perfectly from the first quarter.
Can you prioritise effectively without a formal framework?
Yes, provided the priorities are explicit and written down. The problem is not the absence of a framework: it is the absence of shared prioritisation. A list of the three priority topics for the quarter, visible to everyone and updated regularly, is better than a badly implemented OKR system.
When do OKRs do more harm than good?
When they are introduced too early, when they cover too many topics at once, or when they are defined unilaterally with no involvement from the teams. In those cases, the administrative overhead exceeds the value produced and teams see the system as a constraint rather than a tool.


