Ship Happens, Week 1: How to write requirements, tiny habits for your brain, and staying up to date on the AI race
Just in time for the flood of new ideas from your boss! š A roundup of helpful reads and ideas heading into the new year.

The new year is here! Iām sure some of you are back in offices or on Zooms and starting to get after it.
I am definitely not lol. In pajamas writing this in my study, Iām back to work on Monday. But the job of product management in a lot of ways is 24/7. I like to stay sharp over the holidays by staying up to date on whatās happening in tech and in markets overall, both here on Substack and elsewhere.
So Iām going to use this newsletter to share at least three things Iāve come across this week to help you build better product. Subscribe so you donāt miss these when they come out:
Some of what Iāll put in here is directly relevant to product management. Some of it will help you get into that user mindset. Iām going to sprinkle in also some of the critical reads and videos that have made an impact on me in my product management career.
Thatās a nice segway into the first thing, here we go!
1. Joel on Softwareās blog series on product requirements
This series of blog posts is admittedly old school. The Chief Product Officer I worked for when I first started out as a baby PM recommended this series, thatās how old it is. š“š¼
But I have to say it continues to be relevant, and itās one of those resources I recommend over and over and over again. Why? Joel makes a lot of key points that I find gets lost quite often in discussions about product requirements, like:
Product requirements are being written to clarify requirements and align on those requirements with your design and engineer team. If the requirements donāt do those jobs, theyāve failed. Thereās no point in having them.
Thus, you should write requirements that are designed to be read and understood by actual human beings. You donāt get points for having the longest requirements that no one reads. Since itās for actual people, try to be concise and direct but also make them fun and easy to read.
Requirements are complete when no one has any more questions or feedback. This is a really simple but powerful idea. If the above is accomplished fully, everyoneās on the same page, edge cases are clarified and we are ready to move forward quickly to completion.
I hope youāll find it particularly useful heading into the new year writing all of those requirements that you put off in December. 𤣠I did it too donāt worry! On to our next topic:
2. 7 Tiny Habits That Will Change Your Brain and Help You Not Go Product Manager Crazy in Q1 2025
Okay I admittedly changed up the title, but
brings it here with some great little shifts for 2025:The one Iām personally working on the most is taking little breaks throughout the day. My Oura ring loves to tell me that I get 0 restorative time. Shove it Oura ring! But it was totally right. My sleep has been improving as Iāve been forcing myself to take more breaks and more down time, especially at night.
The Q1 onslaught is here, itās gonna be stressful. Take your breaks and take care of yourself.
3. Make double-sure youāre staying up to date with the AI race
I personally follow Azeem Ahar for content like this on AI:
Once youāve mastered the basics, product management starts to become about getting intuition and foresight about how to build better products for human beings. That requires understanding where the puck is going and skating towards.
Sometimes the puck is a mirage, but AI is definitely not a mirage. Weāre early, so sometimes AI can feel like āglorified autocomplete,ā to borrow a phrase from an engineering manager I worked with. But AI is here, itās coming, and itās going to have a big role to play in building products going forward.
So itās best to understand the latest on these technologies. It reminds me of mobile when I started out in startups in 2010 š“š¼ I never worked at Apple, but knowing what was happening and what users wanted/grew accustomed to helped me build much better products.
In this case, what weāre staring down the barrel of is something like GPT-o3, where with enough compute power the model is able to more and more complex tasks:
Basic facts: The new model is good at reasoning in mathematical and programming domains. It scores really well on a particular benchmark called ARC-AGI, which is above the average human. Spend more money on it, up to $3,500 per task, and it approaches the performance of a STEM graduate.
Crazy. What should you take away from this as a product manager?
These models are only going to get better and better. It was thought that weād hit a wall after LLMs trained on all of the data on the internet. But now OpenAI and others are turning to newer techniques like āthinkingā and they are paying off big time.
Thus, users are going to expect more and more from products and experiences. The use of AI in your products is going to be a given in a few years. So if youāre not thinking about how to use AI in your product experience now, good chance youāll be behind.
The tolerance for screw-ups is going to get lower and lower. āIf AI can do STEM-graduate level math problems, why canāt it tell me correctly when my new Nike shoes are going to deliver?!ā I can already feel this feedback coming. Start planning to invest in lower and lower product error rates.
Thatās it for this week! š
If youāve found this helpful, please consider showing your support by subscribing:
And please consider becoming a paid subscriber at $5/month or $50/year. Iām going to start sharing things like my resume template, resume reviewer for paid subscribers only. Iām also thinking about opening up chat to paid subscribers so you can ask me questions and get some 1:1 coaching. So consider going paid to get some of those great benefits. š¤
Finally, share with someone else that you think would find this useful:
Iāll be back around this time next week with more useful product manager things!