Ankesh retweeted
As the pace of the world accelerates, the most important skill becomes the ability to change. But that's easier said than done:
* Change means accepting that what you've done before may not matter.
* Change means being a beginner again and not having the accolades or bonafides of an expert.
* Change means feeling dumb sometimes.
* Change means that work doesn't get easier over time.
* Change means not expecting that your age correlates with relevance or other career assets.
* Change means starting over.
Of course this concept has thousands of pages of philosophy written about it, so this is nothing new. But the urgency for people adapting has never been more significant.
For me, I've had some career success and learned a few things. But I know that I need to change too and I'm really enjoying it. Starting over (which I've done in various ways at work and personally) is an incredible feeling once you accept it.
Ankesh retweeted
A big thank you on behalf of everyone at @CRED_club as we turn 7. 🙏
Ankesh retweeted
In today's 996 chest-thumping culture, don't forget about the quiet ones keeping your company together..
Ankesh retweeted
The correlation between talking to customers and truly understanding customers is in fact not as high as your content diet would have you believe.
Ankesh retweeted
It is frustrating when your CEO/executive always implies that “everything is a priority”.
This tendency — especially evident during big product review meetings in many companies — is rooted in one of these 3 causes:
1) You haven’t given them the right context: there is no clarity on product strategy, so absent that, they see no choice other than to prioritize everything that intuitively 'sounds' important to them 😐
2) The executive doesn’t trust your team’s innate motivation to make an impact: so they try to brute force it by pushing you to “do all the things” (basically: produce more, work harder) 😬
3) The executive tends to fall prey to the Focusing Illusion (ref: Kahneman) “Nothing is as important as you think it is while you are thinking about it”: you’re talking about issue X right now, so X is the highest priority - tomorrow, you’ll talk about issue Y, so Y will be the highest priority, and so on ad infinitum 😱
What is the solution?
You have a ton of control over item #1, some control over item #2, and hardly any control over item #3.
#1 can be addressed in weeks/few months.
#2 can take a while to address (several quarters).
#3 requires a culture change.
Now, remember this: as a senior manager at the company, it will be easy & convenient for you to assume that your executive is definitely suffering from #3.
But I’d suggest still trying #1 first, and presenting a proper product strategy (not one of those nonsense manifestos that follow the Mission → Vision → Values → Strategy format).
As a senior manager, clarifying a proper product strategy is YOUR job. Truth be told, it is one of your most important jobs.
If your executive is competent, in practice, you can get pretty far in solving this problem by presenting a proper product strategy. Challenge is that it is not easy to do this, so most senior managers
a) procrastinate with great excuses, or
b) only do it under external pressure (e.g. during the forced 2026 strategy planning cycle) and the output is inevitably just meh (as evinced by the fact that this fancy strategy doc is forgotten within less than 3 months into the new year)
The real reason for this procrastination is that deep down nearly every such senior manager knows that s/he is not very good at product strategy.
S/he might be good at presenting a nice-looking doc (with many charts, diagrams, data, fancy words like MECE, LTV:CAC, orthogonal, flywheel, blue ocean, ecosystem, 2nd derivative, etc. and loads of inspiring rah-rah language).
But deep down s/he knows that s/he only knows how to present a Performative Strategy and doesn’t quite know what a good product strategy is and how to formulate one.
This is true even for — perhaps especially for — senior managers who went to fancy b-schools like GSB, HBS, INSEAD, ISB, Wharton, etc. etc. (nothing against these schools - they are just teaching what their students want, not what their students actually need)
The way out of this is to first accept the problem and then intentionally grow your product strategy competence (it doesn’t come naturally to most), work in a small team (at most 3 people, not a committee) to formulate a real strategy, and utilize the help/expertise of a strategic genius at your company.
This latter point seems obvious, but in practice I’ve found that senior managers will go quarters / years getting feedback that there isn’t clarity on their strategy, but they will refuse to enlist the help of a peer who is a strategic genius.
So just because it seems obvious doesn’t mean that people will actually do it.
In fact, the higher bar to get hired at a given company, the more senior managers will avoid getting anyone’s help to improve their own strategic competence.
So ultimately your biggest foe might be your ego i.e. to prioritize winning over ego preservation.
Everyone says they can do it, but we have millennia of evidence that few of us actually do. And what you do with all of this information is up to you.
Ankesh retweeted
I won’t lie, the CRED coin rush is outperforming the spike we saw during our Shark Tank episode airing.
Didn’t see this coming!
Ankesh retweeted
Wow its been 16 years of Credit building and 400 + Payments made on time.. @CRED_club Thanks for the sharing the achivements.. #ccgeeks
Ankesh retweeted
Today @CRED_club did it the apple way.
Ankesh retweeted
A very Apple/Tech release feel to the @CRED_club launch today
Ankesh retweeted
attended a physical event for a tech product launch for the first time.
pretty good show from cred team 💯
Ankesh retweeted
CRED pulled off a cool Apple-style event. What’s new? All in pics, in text sometime.
I was hoping for a card, that, I wish happens someday.
Ankesh retweeted
Parents should never put their daughters in a position where any random person can come and reject them based on their complexion, weight, facial features, height, level of ambition, etc. Why would you want someone to have tea with you and count your child's 'flaws'??
Ankesh retweeted
Many things should be created on a deadline but your product strategy is not one of those things.
Ankesh retweeted
Every company goes through 2 stages:
Stage 1 is when it’s fine for you to just reply with your answer to the CEO’s email asking you a question about your product.
And then with some success comes Stage 2 when you don’t just reply with your answer (are you crazy?), you first create a Google Doc, you type a draft reply, invite a bunch of people to the doc including your manager, comments flow back and forth for hours, every word is scrutinized, every line is keenly inspected w.r.t its impact on everyone’s upcoming perf, and after everyone is equally happy and unhappy and satisfied with the reply, the group chooses a tribute who’ll copy the consensus text from the Google Doc and reply back to the CEO — but wait, the really seasoned pros also know that you must Paste Without Formatting because otherwise the other seasoned Gmail pros including likely your CEO can tell that your reply was authored & doctored in Google Docs 😆
Stage 2 very different from Stage 1.
Ankesh retweeted
You can't force yourself to think any faster.
Speeding up your thinking process often results in poor decisions that create future problems. You can't force yourself to make faster decisions just because you're faced with an unrealistic deadline.
Slow down.
Ankesh retweeted
This is a key observation by @anujrathi:
"The worst part is, they also tilt the arrangement between engineers and PMs by spoonfeeding obvious requirements to nth level which engineers get used to."
If this is left unchecked, over time the entire definition of "what it means to be a good PM" changes: a good PM becomes synonymous with someone who seems to make engineers' life easier.
If you are wondering "what's wrong with making engineers' life easier?", there is nothing wrong with it, but that is not the main role of product management. Product success is.
IMO there is something deeper going on here.
Operation stuff feels way more controllable, and gives you the self-esteem of "I did good, tangible, productive work".
Product discovery is tough, not tangible, and the benefits or cons are seen after product is shipped and used. And even after doing "good product discovery", there is still a hard part of product definition and crafting your product amongst tons of possible combinations. And the product may still fail.
Most PMs would rather work on measurable progress, feel in control, not do the hard and risky work of true market understanding product discovery.
I call it "hiding behind tech".
The worst part is, they also tilt the arrangement between engineers and PMs by spoonfeeding obvious requirements to nth level which engineers get used to.


































