I’m starting to call these the “apple pie positions” => the personal risk of pushing back is so high that almost everyone nods “yes”, even though it is rarely the right answer for the team / company / user. Great example in the quoted Tweet. Will add more in the thread below:
We need to define the success metrics for <whatever is being discussed>.
Apple pie position #3:
We need incentives and priorities to be aligned across all of the teams working on <whatever is being discussed>.
Apple pie position #4:
We need a weekly [check-in || update || executive review] to keep all the stakeholders in the loop.
Apple pie position #5:
We need to stop thinking tactically and think strategically.
Sometimes seen in the wild as:
We shouldn't miss the forest for the trees.
AND
We need to zoom out a bit.
Apple pie position #6:
We need more executive buy in before we can execute on <whatever is being discussed>.
Apple pie position #7:
We don't expect the business to grow a whole lot this year because we are laying the foundation for massive growth in future years.
(fast forward: the promised massive growth never actually materializes)
Apple pie position #8:
We have too many meetings.
Apple pie position #9:
We need to sync more often.
Apple pie position #10:
We need more apple pie!
(this one I agree with entirely)
Apple pie position #11:
We need better metrics before making a decision here.
Apple pie position #12:
We need a better go-to-market strategy to improve product adoption.
Apple pie position #14:
We need an offsite!
Apple pie position #15:
We need to do a retrospective to determine the systemic changes that are necessary.
Also seen in the wild as:
We need to post-mortem this.
Apple position #16:
We need to clarify our expectations from people in this role so we can set them up for success.
Also seen in the wild as:
We need a better career ladder for this role.
AND
The reason this role isn't impactful yet is that role expectations are unclear.
Apple pie position #17:
We need [person being discussed] to be more strategic and less tactical.
Apple pie position #18:
We need more internal documentation!
Apple pie position #19:
We shouldn't forget [quote one of the company's core values].
(often used as a tool to justify one's position, especially when faced with rational counter-arguments)
Apple pie position #20:
We need to replace our team meeting with written updates.
Fast forward a few weeks/months:
People are missing live interactions with team members, they don't know what's going on across the team, nobody's reading the written updates. We need a meeting.
Apple pie position #21:
Our current org structure doesn't set us up for optimal execution of our strategic goals. That's why we are announcing a re-org.
Apple pie position #22:
Remember, we need to hire for strengths not a lack of weakness.
(usually employed to justify hiring a highly pedigreed person for an important role)
Apple pie position #23:
We must not slow down our shipping velocity.
(usually applied to push back against a fairly rational measure that will cause a minor delay in shipping the product but will prevent bigger problems for the user / company further down the road)
Apple pie position #24:
[A] We have done tremendous user research over the past 3 months and have identified these [top N] product gaps. We are confident that product adoption will soar once we address these gaps within the next [M] months.
Fast forward M months: goto [A]
Apple pie position #25:
Remember, we are a mission-driven company.
(particularly effective in justifying below-market compensation for current and prospective employees)
Which ones did I miss? Feel free to add your most favorite (or least favorite) Apple Pie Positions in replies or retweets.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Lack of time is a perpetual source of stress in the product manager’s journey.
No matter how well you’ve prioritized, no matter what milestone your product has just reached, there is a near-infinite list of really important things you could be doing that you just cannot do.
There are many well-known resources & principles for managing time: systems such as GTD, “managing your energy, not your time”, prioritization formulas, Eisenhower Matrix, etc.
These are no doubt useful, but for product managers, these systems leave a lot to be desired.
Why do companies with major resources & distribution make products that are mediocre & often fail to reach their potential?
There are a handful of reasons, many of which you already know. But there is one under-discussed reason: Operators Optimizing for Optics
Thread:
To understand this, let’s start with a story.
START OF STORY
Acme Inc has brilliant, visionary founders (Alice & Bob), amazing culture, has built a well-loved product, and thereby created a business much larger than the early people (including the founders) had ever imagined.
With this growth, they’ve had to hire a bunch of Operators: leaders who are skilled in scaling process, teams, operations, and overall execution. So far so good. As the business & the customer-base grows, it is a no-brainer for Acme to tackle adjacent areas of opportunity.
Some reflections since turning on Twitter’s Super Follows two weeks ago.
800+ superfans have joined 🙌🏾
Biggest benefit:
I am tweeting a lot more freely because I know I am speaking to superfans who understand what I am about. More advanced & nuanced content. Fewer unsent drafts
Biggest surprise:
The community aspect of Super Follows has been A+ thus far.
While not a primary goal, it was 1 of my hypotheses for doing Super Follows. And it has vast exceeded everyone’s expectations. I polled folks yesterday for feedback, and community was mentioned by most
Many super followers mentioned that they are now using Twitter more frequently & are replying/sharing a lot more freely with the community than they might in public, because of shared alignment.
One super follower said it best: people writing without fear of being misunderstood
As they grow in size, teams within megacorps and startups tend to implicitly bias more towards Project Thinking and not enough Product Thinking.
Product Thinking is a mindset and a process that, once you see, you cannot unsee it.
Product Thinking, Project Thinking, a thread:
From my experience working in individual contributor & leadership roles over the past couple of decades, and from my advising work with a number of fast-growth startups, I have often seen myself and founders / CEOs / execs worry about these things:
And, having been in the trenches of product work for a large part of my career, and having managed / mentored / coached hundreds of PMs & PM Managers, I have often seen myself, and other ICs & managers worry about these things:
1) Be proactive 2) Begin with the end in mind 3) Put first things first 4) Think win-win 5) First understand, then seek to be understood 6) Teamwork & creative cooperation 7) Continuous improvement
Basically, the habits in the classic book.
I know that many Product Managers will ignore this because they want something more advanced.
They have already read Covey's book at age 23, so there's nothing more & nothing new to learn from it.
They want an edge over others, so they seek & love esoteric advice & tactics.
And yet, 9 out of 10 times when I am working with extremely smart & ambitious PMs who are struggling (not getting promoted, not getting the performance reviews they think they deserve, not executing well, etc.) it is because they have forgotten one (or more) of these 7 habits.