I think the reason that founder mode appeals (and works) is that singular vision and execution generates opinionated and effective outcomes.
Unfortunately, even brilliant individuals have rate limits
- productive time
- cognitive load
- specialist skills & experience
So we hire to unlock more opportunity, with a hope that that tether to an opinionated individual (or a culture that hive-minds to a shared point of view & ambition) will avoid the inevitable decay of design-by-committee.
But the reality is like all human systems, the quality of this operating model tracks to the behavior of its agents. That brilliant specialist expert becomes a diluting force in a sea of a diluting forces. Because of time, cognitive load, and pro-social collaboration cultures, opinions become weakly held, that shared POV gets lossy, and execution (speed and quality) suffer.
Everyone owns a lil slice and the whole suffers.
What makes me so unbelievably excited about AI is it breaks down many of the barriers for maximizing the impact of a single, smart, ambitious individual. With the tools we have today you can
- offload administrative thought and maximize using your human brain for creativity
- access and even implement specialized skills & initiatives, without necessarily having to compromise on vision
- create more effective time by allowing automations to work while you don’t
THIS is why I’m so bullish on this being the era of the IC. I’d bet on the visionary, AI powered, beast-mode individual over the mythical “empowered product team” in most situations.
If startups beat big companies, then individuals might also beat teams.
Does this mean I’m anti-collaboration and anti-team? NO. I think brilliant teams working in the same direction can make A LOT happen. I’ve been and am part of some pretty great teams.
But I do suspect there is something we need to start planning for, designing for, and optimizing for when we build organizations to win. And that means deciding where the individual rules the roost.
I don’t find this dystopian at all; in fact, I think if we can maximize what one person can do, we’ll open up a whole exciting world of creative ideas, new technologies, and things to build.
More people can have MORE impact, and that to me is a win.
So learn what you need to learn.
Remove your rate limits.
And apply teams with caution ⚠️
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Standing 1:1s are still not the best tool for most jobs
Context sharing, coaching, progress updates, brainstorming, and creating personal connection (professionally) are almost always better served by either small group meetings or writing.
But as someone who started a new role recently and hired a bunch of new folks, I will admit 1:1s are helpful for two specific things:
1. First 90 day onboarding 2. Career conversations
The blameless post mortem (which we embrace, fwiw!) has real drawbacks—the most significant of which is the tendency towards abstract, passive language (“code was insufficiently reviewed”, “production was deleted”) which obscures a bunch of the who/what necessary to root cause.
I’m not saying this sort of abstracted documentation and root causing of issues is a necessary method of blameless post mortems, I have just seen humans who constantly hear “keep it blameless!!!!” shy away from crisp language and pointed discussion.
As a ex-founder I hate (hate!!!) the narrative of CPO vs CEO. Especially the “you bring in a head of product to ‘professionalize’ thr product org” and somehow a micromanagey founder gets in the way.
Sometimes LITERALLY THE MOST IMPORTANT PROBLEM TO BE SOLVED is delivery. Yes, being a roadmap driver. Setting pace. Getting the right org in place. Winning over internal partners.
This work should not be “below” the office of the CPO and is not at odds at being a strategic… twitter.com/i/web/status/1…
One of the only ways for me to stay on top of what really matters is to be high throughput when it comes to the wave of questions/asks/decisions that come across my proverbial desk.
There is basically only 3 kinds of work for me:
1. Existential - will make or break a meaningful part of the business. Requires high quality decisions. Consumes most of my time/thought.
I can only manage a few of these.
2. Passthroughs - Someone else should own it. My goal is to identify an owner, make it clear their goal, and set them up for success as quickly as possible.
I have to pass thru tasks as soon as I identify them. “Find someone” can’t be a todo, just has to be done.
I cancelled 80% of my reoccurring 1:1s and I don’t think I’m ever going back.
I’ve replaced them with these 5 things that are 10x more effective.
First - why did I cancel them?
Aren’t 1:1s the lifeblood of management?
Between my directs and my skips and my peers I have ~20 people that I had standing mtgs with on a frequency from wkly-monthly.
I was booked 7-9 hours a day. It was completely untenable.
What sucked:
- sitting all day
- no deep work time
- no time to prepare for 1:1s
- short meetings with 30% of time spent on “busy week, huh?”
- only saw my circle of directs/peers/skips
- being pinged on slack constantly during meetings
I’ve been a CPO under both models, currently running all of product, eng, design, data and (while I’m at it!) technical services & support. Either model can work, but there are a few reasons why the PED (prod/eng/design) leadership consolidation happens:
The most basic reason is that these teams need to work in tight alignment to deliver, and the CEO wants a single trusted partner to manage the technical, strategic, organization, and leadership needs to ensure it happens well. A good PED exec gives a CEO leverage.
Running a scaled engineering team is a big job. Running a big product portfolio is a big job. Ensuring great user centric design & experience across those is a big job. Making sure those big jobs all happen in sync where 1+1+1=10 is a big job. And being CEO is a big job.