"I really want to break into Product Management"

make products.

"If only someone would tell me how I can get a startup to notice me."

Make Products.

"I guess it's impossible and I'll never break into the industry."

MAKE PRODUCTS.

Courtesy of @edbrisson's wonderful thread on breaking into comics – https://t.co/TgNblNSCBj – here is why the same applies to Product Management, too.
There is no better way of learning the craft of product, or proving your potential to employers, than just doing it.
You do not need anybody's permission. We don't have diplomas, nor doctorates. We can barely agree on a single standard of what a Product Manager is supposed to do.
But – there is at least one blindingly obvious industry consensus – a Product Manager makes Products.

And they don't need to be kept at the exact right temperature, given endless resource, or carefully protected in order to do this.

They find their own way.
Since the dawn of capitalism, life has given children lemons, and they have sold lemonade for extortionate profits.
You, my dear time traveler, find yourself in 2018, a time not just of plentiful lemons, but lots, lots more. It is easier than ever to...
Learn to code (if you like to get your hands dirty) https://t.co/DwowAOZFJu
Build without code (that's okay too) https://t.co/nyK1hnfZrl
Find people to try your product https://t.co/T5Iu5mq6E1
And here's a wonderful secret: if your product fails, it doesn't really matter.

Most things we try don't work. Failure is a fact of life in Product.

In some cases, failure is the best demonstration of your potential.
We look for candidates that can fail and OWN their failures.

Candidates that cannot tell us about past failure are either unable to take risks (bad PM), liars (worse PM), or are some kind of nature defying superhero (probably not within our hiring budget).
A great Product Manager takes risks as a matter of habit. They chase after uncertainty. They learn at every step of the journey.
So there is no excuse 😉

M A K E P R O D U C T S !

More from Tech

A common misunderstanding about Agile and “Big Design Up Front”:

There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.

You’re allowed to think about a desired outcome from the beginning.

It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.

It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.

It’s not BDUF if you help every team member know what success looks like.

Agile is about reducing risk.

It’s not Agile if you increase risk by starting your sprints with complete ignorance.

It’s not Agile if you don’t research.

Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.

It would be a mistake to assume this research should only be done by designers and researchers.

Product management and developers also need to be out with the team, conducting the research.

Shared Understanding is the key objective


Big Design Up Front is a thing to avoid.

Defining all the functionality before coding is BDUF.

Drawing every screen and every pixel is BDUF.

Promising functionality (or delivery dates) to customers before development starts is BDUF.

These things shouldn’t happen in Agile.

You May Also Like

So the cryptocurrency industry has basically two products, one which is relatively benign and doesn't have product market fit, and one which is malignant and does. The industry has a weird superposition of understanding this fact and (strategically?) not understanding it.


The benign product is sovereign programmable money, which is historically a niche interest of folks with a relatively clustered set of beliefs about the state, the literary merit of Snow Crash, and the utility of gold to the modern economy.

This product has narrow appeal and, accordingly, is worth about as much as everything else on a 486 sitting in someone's basement is worth.

The other product is investment scams, which have approximately the best product market fit of anything produced by humans. In no age, in no country, in no city, at no level of sophistication do people consistently say "Actually I would prefer not to get money for nothing."

This product needs the exchanges like they need oxygen, because the value of it is directly tied to having payment rails to move real currency into the ecosystem and some jurisdictional and regulatory legerdemain to stay one step ahead of the banhammer.
क्या आप जानते हैं कि क्या है, पितृ पक्ष में कौवे को खाना देने के पीछे का वैज्ञानिक कारण!

श्राद्ध पक्ष में कौओं का बड़ा ही महत्व है। कहते है कौआ यम का प्रतीक है, यदि आपके हाथों दिया गया भोजन ग्रहण कर ले, तो ऐसा माना जाता है कि पितरों की कृपा आपके ऊपर है और वे आपसे ख़ुश है।


कुछ लोग कहते हैं की व्यक्ति मरकर सबसे पहले कौवे के रूप में जन्म लेता है और उसे खाना खिलाने से वह भोजन पितरों को मिलता है

शायद हम सबने अपने घर के किसी बड़े बुज़ुर्ग, किसी पंडित या ज्योतिषाचार्य से ये सुना होगा। वे अनगिनत किस्से सुनाएंगे, कहेंगे बड़े बुज़ुर्ग कह गए इसीलिए ऐसा करना

शायद ही हमें कोई इसके पीछे का वैज्ञानिक कारण बता सके।

हमारे ऋषि मुनि और पौराणिक काल में रहने वाले लोग मुर्ख नहीं थे! कभी सोचियेगा कौवों को पितृ पक्ष में खिलाई खीर हमारे पूर्वजों तक कैसे पहुंचेगी?

हमारे ऋषि मुनि विद्वान थे, वे जो बात करते या कहते थे उसके पीछे कोई न कोई वैज्ञानिक कारण छुपा होता था।

एक बहुत रोचक तथ्य है पितृ पक्ष, भादो( भाद्रपद) प्रकृति और काक के बीच।

एक बात जो कह सकते कि हम सब ने स्वतः उग आये पीपल या बरगद का पेड़/ पौधा किसी न किसी दीवार, पुरानी

इमारत, पर्वत या अट्टालिकाओं पर ज़रूर देखा होगा। देखा है न?

ज़रा सोचिये पीपल या बरगद की बीज कैसे पहुंचे होंगे वहाँ तक? इनके बीज इतने हल्के भी नहीं होते के हवा उन्हें उड़ाके ले जा सके।