Many years ago I had a direct report who had been very successful in a similar role at a previous company. They were rightly very confident in their technical ability. They knew what they were doing.
But when they moved companies, they unexpectedly recognised that they were missing clear and mutually agreed targets. Something was wrong.The issue couldn’t be anything professional, because their skillset had been proven in a previous role. The issue couldn’t be personal, because as a person they hadn’t changed. So what’s left? It must be a cultural fit issue.
This is where it gets tricky. Culture in an organisation permeates everywhere, but ultimately it comes from the top. It’s very confronting and complex to determine how the role you know and love is perhaps wildly different in this new culture. You need to question your own strengths and weaknesses and decide whether you can or even want to adapt.
Instead it’s far easier to pin the cultural conflict on one or all leaders within the company and put it down to a personality conflict. “I’m doing the role right, it’s the company that needs to change”. This may in fact be true and even in the best interests of the company, but you’ve effectively decided it’s you vs the company. That never ends well.
It’s performance review time of year again! It’s hard enough to clear your head and objectively self-reflect on your own performance, let alone on the performance of others. For many of my team this was the first time that they’d been asked to provide 360 feedback on their peers, and so there was an extra level of discomfort. I recorded the following Loom video demonstrating the Situation, Behaviour, Impact (SBI) framework, in order to help them approach the feedback process and make their feedback more actionable. I hope it’s useful to others too.
Google provides a one click install option for WordPress on their Google Compute Engine instances. This is a very economical and customisable way to spin up a WordPress blog if you’re comfortable with a Debian shell. Unfortunately it only spins up a HTTP rather than secure HTTPS instance, so here’s how to add a free SSL certificate.
Firstly, log into your Cloud console and open an SSH shell for your instance
Then in the shell, run the following commands as mentioned here:
Words like “consultant”, “workdriver” and “special projects” still create a PTSD style effect in my head. These words drip with corporate context, very clearly and precisely signalling whether you were succeeding or failing. The email announcing a VP moving to “special projects” triggered a global cascade of watercooler conversations where we each dissected and calibrated their missteps and realigned our own. It feels like a high performing culture because you’re communicating in flow – there are barely any words exchanged but you can replay together how a pattern of behaviour over years became fatal for said VP. It’s almost a cult like sensation. People worry about leaving because they fear never experiencing this level of flow (read: intelligence) ever again?
Tim Fung from Airtasker reminded me of that on his webinar this morning. Why do leaders communicate? His example was a mistake he made, sending an email whilst under stress that the expected working hours were 8:30am – 6pm. On reflection, he wasn’t trying to communicate an expected outcome – people in seats. Instead his company was under serious financial pressure and the next few weeks required a mammoth effort to keep the dream alive, but he failed to communicate that context and lost good people because of it.
So what was Tim trying to communicate? Well the zeitgeist answer would be that he was trying to communicate a cultural expectation. But if your company goals are service quality and people focus, perhaps that internal culture would be counterproductive? No, this wasn’t an attempt at ongoing cultural change.
Tim specifically reflected that the goal of this communication was to set context. He wants to know that when a specific context is shared, a certain set of behaviours are triggered at scale. For example if an “investor presentation” is announced for a few weeks time, an increasingly large ship needs to transform immediately. The operations team cut costs, HR cancels all off-sites, engineering ships the shiny MVP that wasn’t quite ready. This is not a cultural theme that persists during the year, but instead a carefully communicated and indoctrinated context that dictates specific behaviour.
I suppose most of the time this context, just like culture, is set through repetition. But what if you could construct context more deliberately? If there are 3 regular events that are critical to your business every year, how could you communicate the context of those events in a crystal clear way? For example if you are Apple and your company’s innovation appetite pivots on the annual WWDC event, how do you describe that context to a new hire or even a customer?
Pivot points get a lot of discussion in the startup world, but I think these context events are the pivot points every company needs to know, and communicate heavily and precisely.
Like every great episode of Silicon Valley, it all starts with a whiteboard. Customer (demand) and worker (supply) names are written on the board, with relevant skills and availability scribbled down. Everyone gets on the phones and calls each side, trying to make connections. Every connection is a new possibility, a new thread in the web you’re trying to spin. You’re losing money on every one, but if you’re doing it right they start to become sticky.
This means customers are not just delighted that you introduced them to someone that can solve a problem for them, but that it has the seeds of an ongoing relationship. They enjoy working with the person, they need that problem solved ongoing and (for your benefit at least) they see the value you add as the third wheel.
At worst they appreciate the comfort of having you on the phone to handhold them through the process, at best you are a critical part of the value chain that is hard to replicate without scale. Except you don’t yet have scale so this might cost you big time upfront – software, insurance, data, templates, logistics, call centre etc. Don’t resent the cost, because it’s also your barrier to competition. Watch that burn while you find market fit.
2. The Acquisition Marketing phase
Once the relationships are sticky and your churn is under control, you need to scale quickly to bring your unit cost down and start to pay off that upfront investment (or raise on a growth pitch to kick this can down the road). It’s time to look at the chicken and egg problem of liquidity. What services are not getting traction, and how might each translate into an efficient performance marketing campaign?
You probably have no brand equity, so your performance marketing needs to be very targeted and ideally not competing with established sector players. It’s also tricky to scale, because your segments could be very small and fast moving. 95% of marketplaces are demand constrained, so start by focusing on 1 side only.
Start testing campaign segmentation by customer type first until you get your CPA down to at least breakeven, before trying to solve for secondary variables like geography or availability. You’ll also need to start building a view on Lifetime Value (LTV) by each segment, so eventually you can think about bidding based on Return On Ad Spend (ROAS) or similar metrics. But every customer is different, and so this quickly also becomes a scale challenge that will require marketing data investments.
Don’t purely optimise on cost however, as the goal of this phase is to build number of connections not the number of users. Don’t underestimate power users who create a lot of connections even if they don’t spend a lot, you need to talk to and learn to love these people without becoming too dependant.
This phase is why 50% of startup investor’s money goes to Facebook and Google, you need to learn to love their tools and optimise (aka the sexier “growth hacking”) like crazy. But this needs to be just a phase – if you never graduate then you are at the mercy of the next algorithm change and/or well funded competitor. Don’t become the next GroupOn who spent like crazy here but never graduated.
3. The Product Growth Phase
Also called the Network Effect phase. This is the holy grail, where your product flywheel starts to spin and growth happens organically. There are 3 major things required here.
Finally and foremost – you need to understand what part of those calls in phase 1 relied on the human touch, and what was to overcome objective friction. Pour the gold of your customer service team over the trust issues, and scale the rest in-product with great UX that makes your funnel so intuitive as to be invisible.
Focus relentlessly on removing any friction in making a new connection; this could be through removing double commits, applying data and recommendation engines, teaching your users how their behaviour affects their success, systemically weeding out quality and fraud issues and many more concepts.
Finally you should clearly commit only to verticals where you can be number one. Your next key competitor will play in a narrower not a wider vertical than you, so you need to lead market share not just overall but more importantly in the key customer segments you care about. The network effect is a big moat, but it isn’t the winner takes all endgame it was first thought to be.
Is the company you work for a “tech” company? What does this even mean in today’s world where almost every company would grind to a halt without its technology systems?
There appear to be short and long term answers to this question.
The short term answer is that when you’re disrupting an industry and trying to raise capital, calling yourself a tech company helps. It promises higher growth, more access to tech VC capital, higher appeal to talent and disruption through innovation. These are all critical for kickstarting your startup and so adopting a tech company mantra at a startup phase makes commercial sense.
The long term answer is more complicated. In my experience, there are a number of behaviours within a company that determine it’s true identity as a tech company:
Resourcing – At Google, the sales team proudly proclaim “we keep headcount tight so that we can invest in engineering”. Everyone knows the resource priority and it is actually realised. This is not purely a political hierarchy, the non-technical teams truly believe that only technology can scale fast enough to hit the audacious growth targets. There’s no such thing as “throwing bodies” at the problem – at least in terms of full time employees. Vendor or contractor growth however is a sign of masking an emerging problem here.
Growth Targets – Technology works best at scale. For example, most national retailers don’t need automated warehousing because the number of SKUs and locations is not that high. If you’re Amazon however, you absolutely need this technology automation to even have a chance of hitting your massive growth targets – it only later amortises to become a competitive advantage. Tech companies truly believe that their growth goals far outstrip any organic growth projection for the sector as a whole.
Time Horizon – Tesla believe that their most valuable asset will be the self-driving data accumulated over millions of kilometres of driving. This not only takes years of operating at scale to collect, but won’t become valuable until self-driving cars are truly pervasive and actually autonomous. It’s not a priority to fix the panel gaps on a $100k+ car, this will get fixed with scale and simplification. The core strategy and focus is their long term goal that requires almost puritan belief. This approach is certainly rooted in the evangelical beliefs of those who originally settled the west coast of the US.
Leadership – You can’t stay the course on these long term goals if your leader doesn’t have the engineering ability and credibility to constantly reinforce the mission. As Bond Capital put it, “successful companies are led by planners – they have short and long term (10-20+ year) visions and business plans focused on data, execution, iteration, engineering and science”. It’s not just CEOs that need engineering ability, but also the board and investors are required to be increasingly technical in order to understand and support the tech company’s long term vision.
So, do you still believe you work at a tech company?
Last week Liam invited me to participate in a webinar titled “Pivoting Product and Product teams through a Crisis”. It was a real honour to be invited, as the panel was made up of a number of great product leaders from Sydney. Mable in particular has seen some big swings in supply and demand, as well as winning a very exciting Department of Health contract.
If you’d like to view the webinar, please see this YouTube video:
I recently completed the Mastering Growth online course with Harvard. As an avid listener of the Masters of Scale podcast I was aware of the content, but this course really made me take the time to reflect on the themes in the context of my role as CPTO of a startup.
The podcast episode that resonated most with me was featured in one of the lectures – Uber’s How Pirates Become The Navy. The episode is about the band of startup pirates learning the benefits and behaviours of becoming a navy. Coming from Corporate land however, I needed to do the opposite and learn when to be a pirate.
Google teaches you to plan big – if it’s not in the hundreds of millions of users or $ then it’s probably not worth doing. That implies that planning and robust debate is important, and exemplifies an engineering lead culture where scale is thought through.
When shifting to a startup, although you might get hired for scale they will give you credit for speed. The company and founders has lived through a period of survival and built a credit structure around that. If you want to earn enough credits to spend on that big scale investment, you had better show you can jump on a quick dollar today. It doesn’t really matter whether that dollar aligns with the strategy or not, what matters is that you moved quickly and you closed it. You have survival instinct.
The trick is knowing when you need to show this hustle. Anyone from corporate land can tell you that quick wins buy credits, but in corporate land there are very clearly articulated strategies and even words that will help you find wins. One example is a corporate mantra of being a “trusted advisor” – just go and get a customer testimonial that shows how they relied on your advice to make a decision. Pre-meditated decision making.
In startup land, it’s more opportunistic. You need to jump on the opportunity as soon as you see it, and then work out the messaging later. A key customer mentions a tangential opportunity? Launch an MVP and then test if there’s a market for it. Worst case the takeaway message is we moved too fast – there’s no punishment for that. Best case, you made a customer happy and a dollar. Now you can put your scale hat on, market size it, and think about whether it’s something worth planning for.
Is this a good core strategy? No, if you focused on this then your ever increasing team would be in an ever bigger state of fragmentation and disarray. As a rough rule of thumb, 20% of your effort should be launching MVPs and 80% should be landing the proven ones.
On my previous blog post, 3D printing a sportomatic brake pedal, I shared some pictures and detail of the process. There were so many comments and requests to share the file, that I have decided to upload it here:
When I was about 11, I created a Lego greenhouse that grew a real plant. That’s when I first believed that I could create technology that makes a difference in the real world. I came to Google as a level 3 just over 9 years ago to work with the best people in the world to achieve that mission. Being part of programs like YouTube Symphony only confirmed this truth. Four promotions later I hit an EQ brick wall, leading to 2 years of hard self reflection both inside (thanks Take the Lead) and outside Google (thanks INSEAD).
At the end of this period I wrote a thesis with a paediatric surgeon in Singapore. She turned up late to our first group meeting… typical university group work right? Except she was late due to performing a liver transplant on a newborn. I reflected that the ads I delivered today didn’t give me that same feeling, she reflected that she only had one pair of hands and YouTube educates the world on health every second.
In the couple of years since this experience I’ve felt a need to more deliberately structure teams to solve real world problems. Full time this was helping my awesome Publisher team find a way to fund journalism again, but at night I was kept awake by failed health startups and raising our 3rd child. My list of requirements for a healthtech role that would be good enough to leave Google for was extensive, but after a lot of sleepless nights and consultation with family and mentors, I think I’ve found one.
There are a huge number of people to thank for this journey – Neeraj, Estee, Alan, Abhay and Scott for being amazing mentors and advocates. My teams and peers across Brand, CSE and Publishers who have pushed me to be a better person and manager, but more importantly shared so many personally meaningful TGIFs, off-sites, coffees and lunches. I’m sorry for pushing so hard on PDPs and career development, but if it helped spark even one new insight into what motivates you then I leave content.
Please stay in touch, it’s a small world even outside the Google bubble.