- - understand as much about the product as possible, primarily from a user point of view
- meet as many different verticals as possible and understand how they work
- speak with all other senior PMs and tech leads and understand their workflows
You're going to be working with multiple teams and stakeholders and it's crucial you have a mental map of how everyone's workflow is. You also will have an 'outsiders' view for the first 30-90 days as you look at the product with fresh eyes. Use this to drive insights for the product if applicable.
Lastly, don't ever stop customer meetings. It may not be on the agenda for other Senior PMs, but don't let that stop you. Customer meetings will keep your insights fresh and valid.
- 1 point
- 3 points
- 11 points
- 2 points
- 3 points
- Thanks for the response! I'm looking at it more from a business POV. I'm assuming I can get the land for decent rates. I don't want to use it for farming, because of lack of expertise, plus longer turnaround time.
The usual stuff comes to mind: paintball arena, minimal restaurant, storage yard etc. but wanted to know if there's something innovative that I haven't thought of as yet.
- 1 point
- 2 points
- 7 points
- I ran a search for 'How to scrape Linkedin Profiles'. At a quick glance 1 out of the top 4 results actually contained some instructions. The rest was more SEO-bait. Just thought I'd share with you - not sure if this is the exact use case.
Congrats on the launch! I can vouch that this is indeed a problem devs face, especially new devs. The number of times I've had to steer away my students at Edyst away from SEO optimized articles!
- Taken to the extreme though, this could lead to neomania. New for the sake of new.
What should we term the quality of knowing not to fix something if it ain't broke?
I think that line of thinking would be the intellectual opposite of PG's (albeit still coherent in it's conjectures or lack thereof)
- It's a step in the right direction. They face issues that plague traditional LMS systems in that LMS systems are pretty much archaic and opaque in documentation.
The CI part works well (I would expect the same from github), but things like syncing up your class roster or just inviting an ad-hoc set of students.... that's very clunky.
- As a business owner, I would love to use Whatsapp to communicate with my users. Not to spam or advertise, just communicate. The email open rates for our target audience (Indian college students) are abysmal, and SMS is just too unpredictable (but what we end up using because that's the best we've got).
I reckon that there would be similar business owners in my predicament who would just like to genuinely notify users. Just like with email, users can have an opt-out option as well.
I think some of this functionality is already there in their Business API (which is quite opaque fwiw).
On the other hand, I can see how this can quickly devolve into spam if used incorrectly (which is inevitable).
It has allowed me to escape the news cycle. I am yet to find an equivalent of the Economist for India (where I'm residing right now). As a result, I'm currently quite oblivious to the day-to-day in India, but honestly that hasn't been of much consequence.