I think most people would prefer this. #Science
Posts by David Jesse
Love this Fermi quote at the end:
“There are two possible outcomes: if the result confirms the hypothesis, then you’ve made a measurement. If the result is contrary to the hypothesis, then you’ve made a discovery.”
Waze works great when there is no traffic
It's the weekend in some time zones, go follow some soccer nerds
Yes and…
• Invest in their growth
• Give them stretch opportunities
• Remove obstacles from their path
Talented people need great leadership too.
Yes and…
• Invest in their growth
• Give them stretch opportunities
• Remove obstacles from their path
Talented people need great leadership too.
Tell me what you think afterwards
Fair enough. Just recommend you visit both if you can!
For sure it’s great but even in Colombia I prefer Cartagena.
Most product teams are stuck in reactive mode — saying yes to everything or chasing the next big bet.
The result is a roadmap that's happening TO them rather than coming FROM them.
The fix: building your plan.
New post 👇
www.buildcrescendo.com/blog/own-you...
Although RICE scores are relative, there is a massive disconnect:
For many teams the "confidence" scores range from 50% for low up to 100% for high. The success rate of features without iteration is usually closer to 20%, and not enough teams iterate.
www.buildcrescendo.com/blog/overcon...
Yes we do have an amazing defense. Thank you.
That isn’t what the article said.
And unless it is literally on the last kick of the match nobody knows whether the results would have been different. Teams play differently based on the game situation.
“The Gunners have had no VAR mistakes against them.”
Any comment on the Havertz incident Saturday?
If you want to work as a team, the time to get the team bought in is BEFORE you start a war without them.
And pushed him with two hands
AI doesn't change the fundamentals of great product development. It raises the consequences of skipping them.
Read more here: www.buildcrescendo.com/blog/ai-feat...
They become delivery teams & create the TV remote with 100 buttons -- capable of everything but impossible to use. Or someone creates the Homer Simpson car with ideas nobody wants.
When everyone can build fast, delivery stops being the differentiator. Discovery & validation matter more than ever.
Something is nagging me about how product teams are responding to AI coding-driven productivity.
More development capacity doesn't reduce the need for product sense. If anything, it amplifies it.
Teams are producing more and filtering less, at exactly the moment when filtering matters most.
imagine if your heuristics for buying a train ticket were that the train has to be fast, new, and clean, but did not include "is going to the right place"
Agree that coding isn't a substitute for all the other work that has been/continues to be core to the PM role.
Quick prototyping can be useful, just as long as they use that for feedback and don't fall in love with what they created too much/too fast.
It was better when "hitting the tech lottery" meant only being a millionaire not billionaire.
The vast amount of money has had a way of both attracting the mercenaries and bringing out the worst in people.
The new bottleneck for most products won’t be coding but evaluation post launch: data collection or even sales cycles.
Solving for these means maximizing the success rate of launches by understanding customer problems deeply.
This isn’t new to PM but now is more important than ever.
When execution is cheap, those without discipline will overbuild and have cluttered experiences.
Rigorous discovery, post-launch evaluation and iteration will be even bigger advantages.
Most teams are bad at these and fast coding will make that worse, not compensate for this weakness.
The new bottleneck for most products won’t be coding but evaluation post launch: data collection or even sales cycles.
Solving for these means maximizing the success rate of launches by understanding customer problems deeply.
This isn’t new to PM but now is more important than ever.
When execution is cheap, those without discipline will overbuild and have cluttered experiences.
Rigorous discovery, post-launch evaluation and iteration will be even bigger advantages.
Most teams are bad at these and fast coding will make that worse, not compensate for this weakness.
So they are meeting to decide how to have fewer goals?
Andrew is opening a board game club in Berkeley and coding software to do personalized player introductions for his son’s little league.
Hope you can join us for this virtual event. Rich's book is excellent and I am excited to hear him discuss this live.
4 March, 4pm Central US time.