Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
AlexDReeve
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
Product Management Books
(alexreeve.org)
4 points
by
AlexDReeve
3y ago
|
0 comments
2.
▲
by
AlexDReeve
6y ago
In my experience, it's shockingly difficult to stop consuming caffeine. N of 1: I had a similar experience to the author. I was fine for a few weeks, slowly weening down my caffeine intake (I did get to zero eventually w/o headach
3.
▲
Six Tools for Clearer Communication
(reeve.blog)
6 points
by
AlexDReeve
6y ago
|
0 comments
4.
▲
The “Easiest” Paths to Product Management
(reeve.blog)
2 points
by
AlexDReeve
6y ago
|
0 comments
5.
▲
by
AlexDReeve
6y ago
Hey folks — author here! Hope this is useful. Had some great discussion on HN with my last article; always happy to debate!
6.
▲
The Five P's of Product Management
(reeve.blog)
4 points
by
AlexDReeve
6y ago
|
1 comments
7.
▲
by
AlexDReeve
6y ago
Hey folks, author here. I'd love feedback – I'm also happy to answer any questions and/or debate!
8.
▲
Teams Fail When They Lose Control of the Narrative: Five Leadership Lessons
(reeve.blog)
1 points
by
AlexDReeve
6y ago
|
1 comments
9.
▲
by
AlexDReeve
6y ago
What you're describing as a "so-called" leader is in fact what a good leader should do, in my opinion. It's a fine balance!
10.
▲
by
AlexDReeve
6y ago
Thanks for the suggestion! I'm on Digital Ocean; I had to do a quick droplet upgrade to avoid the "hug of death" – I'll keep Cloudflare in mind!
11.
▲
by
AlexDReeve
6y ago
Thank you, and great point — another way I've heard it said by a friend/mentor is that "80% of PM is prioritization and communication". Where prioritization basically means "making good decisions on what gets priori
12.
▲
by
AlexDReeve
6y ago
Thanks for reading! PG has a great article on "maker" vs. "manager" (I borrowed the framing from him and linked it in the article). http://www.paulgraham.com/makersschedule.html To your second point: Ult
13.
▲
by
AlexDReeve
6y ago
That's an awesome way of putting it. I may borrow that! ;)
14.
▲
by
AlexDReeve
6y ago
Thanks! Principle #23, triple-check your links! ;)
15.
▲
by
AlexDReeve
6y ago
I'm saying it's aged well! Despite the author's caveat, I think it's still accurate in a lot of ways.
16.
▲
by
AlexDReeve
6y ago
Completely agree. The PM is there to help the team figure out what to build, and help them succeed in building it. They can do this in a number of ways: Being an expert on the product is "must have", but they also need to know the
17.
▲
by
AlexDReeve
6y ago
I agree. In my opinion, over-communication is to help maintain alignment between people/teams/functions. It can't replace real, valuable work and results. Ideally, if the PM is a good communicator, execution is a lot smoother
18.
▲
by
AlexDReeve
6y ago
One of the greats! It's amazing how well "Good PM/Bad PM" has aged. =)
19.
▲
by
AlexDReeve
6y ago
Back online, sorry about that, folks!
20.
▲
by
AlexDReeve
6y ago
Too true! =(
21.
▲
by
AlexDReeve
6y ago
Ugh, I'm on it!
22.
▲
by
AlexDReeve
6y ago
Hey folks, author here. I'd love feedback – I'm also happy to answer any questions and/or debate!
23.
▲
Principles for great product managers
(reeve.blog)
226 points
by
AlexDReeve
6y ago
|
89 comments