Instead of watching Netflix, watch this 1992 MIT lecture by Steve Jobs.
It will teach you more about product and sales than most 2-year MBAs.
Because people don’t buy products
they buy meaning.
And clarity beats features every time.
Politics ya weyrey gan 😃
The small departmental politics I did it school.
Contested for Gen Sec of my department.
On election day.
This one would enter polling room and come out, "I voted for you". The next one, "I voted for you". Another one "I voted for you".
I was so confident of winning that, after voting ended, before counting started, I went to my opponent and told her, "Shade (Kolade), you gave a good fight, but I am winning this one"
Counting started
"Oyewale (me)"
"Oyewale"
"Oyewale"
I was already raising shoulders
then
"Kolade"
"Kolade"
"Kolade"
"Kolade"
"Oyewale"
"Kolade"
"Kolade"
Oh boy, when Insaw the trend, I waltzed to a dark area near the election hall and flagged okada.
"I will not witness this embarrassment"
Okada straight to Awo Hall. Jumped on my bed.
My friend, classmate, roommate and agent, who was inside during counting and repping me @mhuyil was "trapped" in the collation room.
When he arrived in the room like 30 minutes later, he didn't bother to tell me the result.
Baba just carry kettle and do ablution to do maghrib salat 😃
Next day, I was the result pasted in department board:
Kolade: 280 votes (or thereabouts)
Oyewale: 240 votes.
I retired from politics immediately.
I interviewed people for Shell for years.
Here’s how to get in. 🧵
These tips will help you for other O&G companies too because they basically copy each other.
Same concepts. Different buzz words.
In 2014, Sam Altman gave a 1-hour masterclass on turning ideas into billion-dollar companies.
His frameworks:
• Best ideas look terrible at first
• Small markets that grow fast
• Users who love, not like
10 timeless lessons:
1. The idea matters more than you think
PM: Users are begging for customization options. Look at this feedback.
Lead PM: Show me the usage data.
PM: 92% never change the defaults.
Lead PM: Interesting paradox.
PM: Not a paradox. The data is wrong.
Lead PM: The data is never wrong. Your interpretation might be.
PM: Users literally told us they want customization.
Lead PM: What exactly did they say?
PM: "I need to customize the dashboard for my workflow."
Lead PM: Read it again. Slowly.
PM: "...for my workflow."
Lead PM: There it is.
PM: There's what?
Lead PM: They're not asking for customization.
PM: They literally said customize.
Lead PM: They're telling you the defaults don't work for their job.
PM: Same thing.
Lead PM: Completely different thing.
PM: How?
Lead PM: One requires building a settings panel. The other requires understanding their workflow.
PM: We already understand their workflow.
Lead PM: Do you? What job are they hiring this dashboard to do?
PM: Monitor their metrics.
Lead PM: Generic. Try again.
PM: Track team performance?
Lead PM: Still generic. Get specific.
PM: I'd need to talk to them.
Lead PM: Finally. Now you're thinking.
PM: But we already collected feedback.
Lead PM: You collected feature requests. Not jobs.
PM: What's the difference?
Lead PM: Watch. Why do they check this dashboard?
PM: To see their numbers.
Lead PM: When do they check it?
PM: Daily standup?
Lead PM: What happens after they check it?
PM: They... make decisions?
Lead PM: What decisions? Be specific.
PM: Resource allocation. Priority calls.
Lead PM: So they're not monitoring metrics. They're making resource decisions.
PM: Okay...
Lead PM: What information do they need for those decisions?
PM: Depends on their team structure.
Lead PM: Exactly. Different teams, different decisions, different data needs.
PM: So we build team-specific dashboards?
Lead PM: Missing the point again.
PM: Then what?
Lead PM: What if the defaults matched their actual decision patterns?
PM: How would we know their patterns?
Lead PM: You have 92% of users on defaults. That's a massive dataset.
PM: Of people not customizing.
Lead PM: Of people revealing their actual workflows.
PM: By doing nothing?
Lead PM: By showing you exactly how they use defaults. Where they struggle. Where they succeed.
PM: So analyze the 92% instead of listening to the 8%?
Lead PM: Analyze the 92% to understand why the 8% are struggling.
PM: That seems backward.
Lead PM: The 8% are your canaries. They're telling you where defaults fail.
PM: But if 92% are fine...
Lead PM: Are they fine? Or just tolerating?
PM: How do I know?
Lead PM: Look at their outcomes, not their settings.
PM: Meaning?
Lead PM: Are the 92% making better decisions? Shipping faster? Happier teams?
PM: We don't track that.
Lead PM: Then you're measuring the wrong thing.
PM: We measure feature usage.
Lead PM: You're measuring button clicks. Not job completion.
PM: So ignore the customization requests?
Lead PM: Transform them into job research.
PM: How?
Lead PM: Every customization request is a job story in disguise.
PM: Example?
Lead PM: "I need to customize" becomes "When I'm making resource decisions, I need X data because Y."
PM: That's just rephrasing.
Lead PM: It's changing your entire investigation.
PM: From what to what?
Lead PM: From "what features do you want" to "what are you trying to accomplish."
PM: We know what they're trying to accomplish.
Lead PM: You know what you assume they're trying to accomplish.
PM: Fair point.
Lead PM: Here's the trap every PM falls into.
PM: Tell me.
Lead PM: You think conflicting signals mean someone's wrong.
PM: They don't?
Lead PM: They mean you're asking the wrong questions.
PM: Such as?
Lead PM: "Do you want customization?" Wrong question.
PM: Right question?
Lead PM: "Walk me through your last three dashboard sessions."
PM: That's research, not data.
Lead PM: Data without context is just noise.
PM: But we have thousands of users.
Lead PM: Talk to twelve. The right twelve.
PM: How do I find them?
Lead PM: Three from the 8% who customize. Three from power users on defaults. Three from struggling users on defaults. Three who churned.
PM: That's qualitative.
Lead PM: Combined with your quantitative, it's truth.
PM: Seems like a lot of work to avoid building settings.
Lead PM: You're not avoiding settings. You're avoiding building the wrong thing.
PM: The wrong thing that users asked for?
Lead PM: Users don't ask for features. They ask for their problems to go away.
PM: But they specifically said...
Lead PM: They used the only vocabulary they had. Feature requests.
PM: So every feature request is wrong?
Lead PM: Every feature request is a translation error.
PM: From what language?
Lead PM: From problem language to solution language.
PM: My job is to translate back?
Lead PM: Your job is to be bilingual.
PM: Meaning?
Lead PM: Hear the feature request. Decode the job. Design the right solution.
PM: Which might not be what they asked for.
Lead PM: Which probably isn't what they asked for.
PM: Won't they be upset?
Lead PM: Were they upset when Ford didn't give them faster horses?
PM: That's a cliché.
Lead PM: It's a cliché because it's perpetually true.
PM: So I ignore user feedback?
Lead PM: You decode user feedback.
PM: Into what?
Lead PM: Into jobs. Struggles. Workflows. Contexts.
PM: Then build based on that?
Lead PM: Then build what actually solves their problem.
PM: Even if it's not customization?
Lead PM: Especially if it's not customization.
PM: Why especially?
Lead PM: Because customization is expensive. For you to build. For them to use.
PM: They said they want it.
Lead PM: They want their problem solved. They think customization is the answer.
PM: Maybe it is.
Lead PM: Maybe. But probably not.
PM: How can you be sure?
Lead PM: 92% of your users are telling you defaults can work.
PM: Or that customization is too hard.
Lead PM: Great hypothesis. Test it.
PM: How?
Lead PM: Give five power users early access to customization. Watch what they actually change.
PM: Then build those specific options?
Lead PM: Then understand why those changes matter.
PM: This is getting complex.
Lead PM: Welcome to product management.
PM: I just wanted to know if I should build settings.
Lead PM: No. You wanted someone to tell you the answer.
PM: Is that wrong?
Lead PM: It's human. But it's not product management.
PM: What is product management?
Lead PM: Living in the paradox until the truth emerges.
PM: That's very zen.
Lead PM: It's very practical. Rushing to solutions kills products.
PM: But we have deadlines.
Lead PM: You have time to build the wrong thing twice?
PM: No.
Lead PM: Then you have time to understand the problem once.
One thing you'll notice in a business:
If Sales start selling more, everything else seems to fall into place magically.
Production will figure out how to deliver more product. Accounting will determine how to collect the increased accounts receivable. Support will figure out to answer more calls.
As a CEO, the number one needle mover is always answering, "How can we sell more faster?" Everything else is just noise.
@inem_girlie@TOLULOPECHELSEA@nysc360 All right. People i have seen so far who have their call up number registered on Tuesday. Keep checking, yours could show soon.
@Vick_abraham@Smith_LA_frosh@nysc360 Oh okay. People i have seen so far that have their call up number registered on Tuesday. Hopefully you get yours soon.
Engineering professors do not fix generators, anywhere on Planet Earth - anyone who believes they do, did not study Engineering.
If you actually studied Engineering, you'd understand there's a difference between an "Engineering Professor" and a "Maintenance Engineer/Technician".
Everyone asks, "How do I break into PM?" but nobody asks, "What would I actually DO as a PM?"
Here's the truth every aspiring, junior or jaded product manager needs to hear:
Worthy Read: Perspective on Product Management by 5 Product Gurus by Products That Count
"Product managers need to solve for real needs that are identified by real customers." - Dan Olsen
Want to know what makes a great product manager? Five product leaders share their insights on essential skills and best practices 🎯
Here's what you'll learn:
🔍 Why balancing qualitative and quantitative feedback is crucial
💡 How to master product discovery and opportunity framing
🗣️ The importance of being "trilingual" in tech, customer, and finance languages
🤝 Why working well with stakeholders is the hardest skill to master
📊 The value of data-driven insights in product development
These experts emphasize that product management is about understanding customer problems before jumping into solutions, and being curious and humble enough to adapt to changing needs.
Check out the article to learn from Marty Cagan, Teresa Torres, Jeff Gothelf, Rich Mironov, and Dan Olsen: https://t.co/vX96EzKpWg
💭 What do you think is the most challenging aspect of being a product manager? Share your thoughts in the comments below.
Every Product Manager should know these websites!
1. excalidraw. com - lets you easily sketch diagrams
2. genspark. ai - makes anything for you with AI (especially slides)
3. prodmgmt. world - feel like a senior PM from day 1
Share it with your friends! Thanks 💓
This isn’t your regular quote.
@Zlatan_Ibile, my name is Olorunjoba, popularly known as Medo JB, fresh UNILAG grad from Faculty of Arts, Department of EnG, and one of the best fast-rising Afrobeats Artiste out of UNILAG
Let me take you through my music story and struggles. 🧵👇