Garry Mansell recently wrote a great post on the a rule of two that dictates when the founder of a growing start-up needs to hire a COO to help manage the day-to-day to keep the start-up on the growth track. Garry labels the position the second-in-command — a true strong number two! But he should call it number one, because the role of this CEO’s right hand is to create pace without drama … absorb ambiguity and turn it into clarity … make the founder less central … and allow the organization to scale without burnout.
As Garry points out, when it hits the wall where the company struggles to scale, the company is in a state where it looks like the founder being busy, but not effective. It looks like things moving, but not compounding. It looks like decisions being made, but not sticking. It looks like the organization waiting for the founder to be present to progress. As a result founders often try to solve this with many more heads. Another manager. Another lead. Another layer. It can help in the short term … until the founder becomes the bottleneck for alignment across those layers. They don’t admit that the hardest part is not finding talent. It’s letting go of the belief that ‘only I can do it properly’. They don’t realize it becomes the thing that limits growth.
But when the organization has a good COO, she doesn’t just take tasks. She takes load. She takes ownership of outcomes … and they make the founder better by refusing to let everything sit in the founder’s head. And Garry’s right on all accounts.
The same logic more-or-less dictates when the organization needs to hire a CPO. Even if the CPO is the entire team. Once an organization is big enough for the founder to hire a COO, a true #1, one of the hats the COO inherits is the CPO hat — and takes over the Plague of Purchasing. But as the organization continues to grow, more and more divisions/teams need to buy more and more products and services of all shapes and sizes, which requires more and more decisions and analysis, more policy, and more decisions … which get made, not properly codified, forgotten in the heat of the moment, and made again. Just like when the organization reached the point it needed a CEO, we again have the situation where it looks like the COO being busy getting Procurement done, but not effective. It looks like things moving, but not compounding. It looks like decisions being made, but not sticking. It looks like the organization waiting for the COO to be present for Procurement to progress.
Even though the organization might only be spending a few million, and the savings might only be a few hundred K, which would barely cover the cost of a CPO, making it look like it’s too early to hire the CPO, but it’s the right time. Hiring early allows the CPO to define proper processes and procedures, define platform and automation needs, determine the right time to pull the trigger on platforms and applications, identify when category managers / senior buyers are needed and the team needs to expand, and because processes and platforms were built into the organization as it grew, the CPO will be able to delay hires longer than peers because Procurement will be efficient from the get-go.