Ben is an engineer by training and spent over 10 years in the Royal Engineers in the British Army career before moving to McKinsey. In 2002, he moved to Coca-Cola where he ran teams across Eastern Europe before turning around the Indian business leading 12,000 salespeople. Ben then moved to Google where was COO of UK and Ireland for 2 years before being promoted to COO Europe where he was responsible for writing the monetisation blueprint of Google’s various properties. This involved defining the role of ad units, properties, interactions with agencies and partners, and devising how auctions should work. Ben then ran a Yellow Pages turnaround before running an ad-tech business for 6 years which ran $200m of ad spend through the major technology platforms. Ben is the author of Marketing for CEO’s and is on the Board of The Oxford Foundry where he is a mentor and investor to multiple startups.
Management and leadership are both important, but if you’re going to be running a team, there is some really good, basic stuff you can put in place that will stop you screwing up. It might not make you an amazing leader, but it gets the basics done. I’ll start with routines. If you have a team, you need routines, and I’d say they break into weekly, quarterly, and annual.
You probably need to have a team meeting once a week, in which you go through how we’re doing against our most important tasks, go around the room and see who’s doing what, they update each other, support each other, etc. Typically, you need other meetings too, focused on specific tasks, but I won’t go into that. You typically need a one-to-one with every member of the team, either every week or every two weeks, in which you go through with each individual how they’re doing against their tasks, how are you feeling. I’ll go into more detail on that in a moment.
Then quarterly, most companies work on a quarterly cycle of goals, so most individuals will have MBO's (management by objective) or OKR's (objectives and key results), there are lots of phrases, but basically, quarterly goals of what they need to achieve. Typically, three to five is the guideline, and every quarter, it’s good to review and say how did you do against last quarter’s goals, how are you doing against next quarter’s goals.
And then, on an annual basis, it’s good to have more reflective feedback; what are your skills, what are your weaknesses, maybe do it 360 feedback, in which you get feedback from your peers, from your direct reports, etc. Those are some of the basic building blocks, and every single leader should put those in place, and it will get all the basics done, stop you screwing up, and actually, you’ll learn through that process how to be a better leader. Those are important.
I’ll zoom in on one, which is the one-to-one itself. For many one-to-ones, they go down one of two bad directions. One is just focusing on the leader’s agenda. Okay, from you, I want to know about this, this, and this. When you’ve finished talking, you go away. That’s the wrong way of doing it. Another is to have no structure and just have a chit-chat about life.
It needs to be a two-way street. You need to both talk and listen. And quite frankly, the first thing I always do in a one-to-one as the leader is say, “How are you feeling?” Because quite frankly, if their dog just died, if they’ve just found out a family member’s got cancer, they’re not going to want to talk about work straight away. Find out about their life first. If their life’s absolutely fine, get on with work. If there’s a problem, work out if you can help. Work from home today, or whatever it might be. I think that’s the most important one.
Then, as a general guideline for one-to-ones, a good place to start is “How are you doing against your quarterly goals?” “Are you getting the support you need from your peers?” because most tasks don’t happen in isolation, they need support from elsewhere. “Is there anything I need to know that I didn’t ask?” is a good question. “What else is going on in your life, work, etc?” You can add more engineering to that, but that would be a pretty good start.
This document may not be reproduced, distributed, or transmitted in any form or by any means including resale of any part, unauthorised distribution to a third party or other electronic methods, without the prior written permission of IP 1 Ltd.
IP 1 Ltd, trading as In Practise (herein referred to as "IP") is a company registered in England and Wales and is not a registered investment advisor or broker-dealer, and is not licensed nor qualified to provide investment advice.
In Practise reserves all copyright, intellectual and other property rights in the Content. The information published in this transcript (“Content”) is for information purposes only and should not be used as the sole basis for making any investment decision. Information provided by IP is to be used as an educational tool and nothing in this Content shall be construed as an offer, recommendation or solicitation regarding any financial product, service or management of investments or securities.
© 2023 IP 1 Ltd. All rights reserved.
Ben is an engineer by training and spent over 10 years in the Royal Engineers in the British Army career before moving to McKinsey. In 2002, he moved to Coca-Cola where he ran teams across Eastern Europe before turning around the Indian business leading 12,000 salespeople. Ben then moved to Google where was COO of UK and Ireland for 2 years before being promoted to COO Europe where he was responsible for writing the monetisation blueprint of Google’s various properties. This involved defining the role of ad units, properties, interactions with agencies and partners, and devising how auctions should work. Ben then ran a Yellow Pages turnaround before running an ad-tech business for 6 years which ran $200m of ad spend through the major technology platforms. Ben is the author of Marketing for CEO’s and is on the Board of The Oxford Foundry where he is a mentor and investor to multiple startups.