Update a-day-in-the-life-of-a-product-manager-at-the-daily-beast.mdx

Author: sonnynomnom

blogs/a-day-in-the-life-of-a-product-manager-at-the-daily-beast.mdx

@@ -31,6 +31,12 @@ That startup ended up getting acquired by [VSCO](https://www.vsco.co) and I was
 
 For me, the best part of working as a PM is that every day is different and there is always something new to learn. Depending on which part of the product lifecycle I’m in, I could be working on vastly different types of tasks, which keeps the job interesting. Each time I take on a new project, there is so much to learn from understanding different user problems and figuring out potential technical solutions. Learning is cool! 😎
 
+## Favorite thing that you worked on at The Daily Beast?
+
+My favorite thing I've worked on at the Daily Beast is probably **Commenting**, which just launched last month. 
+
+This project involved coordination between 2 third-party vendors, (1) [OpenWeb](https://www.openweb.com) which is our comments / moderation provider, and (2) [Zephr](https://www.zuora.com/products/zephr) which is our user-authentication / subscription provider. The trickiest part was designing the user-flow / data-flow in such a way that when a user signs up to comment, their user profile is automatically linked between these two parties in the background, while the user sees a single account and seamless experience on the front-end. It's been really exciting to watch it come to life and see the transformation of our site from passive to active. Since our launch in mid-August, we've already received ~15k comments.  
+
 ## A Day in the Life
 
 My role is hybrid, so my days change a bit depending on whether I’m in the office or working from home. I’ll lay them both out!
@@ -48,9 +54,11 @@ My working hours are from 10AM - 6PM, so I tend to get up around 8:30 to give my
 
 ### 10AM to 1PM
 
-For the first half of the day, I’m typically focused on comms between teams. When I first sign on, I check through my unread messages and check on our topline metrics to get a sense of the day’s needs. Maybe there’s an engineer that needs clarification on a spec I wrote, maybe there’s been a dip in traffic following a recent release, or maybe someone from leadership is asking for a status update on the launch timeline for a new feature. I take inventory of all these things to plan out my day.
+For the first half of the day, I’m typically focused on **comms** between teams. 
+
+When I first sign on, I check through my unread messages (I'm an inbox-zero guy! I generally do have 2-5 "unread" emails and slacks that I have read, but need to keep the reminder on to reply) and check on our topline metrics to get a sense of the day’s needs. Maybe there’s an engineer that needs clarification on a spec I wrote, maybe there’s been a dip in traffic following a recent release, or maybe someone from leadership is asking for a status update on the launch timeline for a new feature. I take inventory of all these things to plan out my day.
 
-At 10:30 I join our daily standup with the engineering team to get an understanding of what all of the engineers are working on. This is where I can flag high priority tickets or bug reports.  It's also where I can help unblock the engineering team, if say, they’re waiting on feedback from another team (this often comes up with ads related work, which is QA’d by our ad operations team).
+At 10:30 I join our daily standup with the engineering team to get an understanding of what all of the engineers are working on. This is where I can flag high priority tickets or bug reports in [ClickUp](https://clickup.com).  It's also where I can help unblock the engineering team, if say, they’re waiting on feedback from another team (this often comes up with ads related work, which is QA’d by our ad operations team).
 
 After standup, I follow up on my morning messages and anything that came up during standup. I think of this as my "unblocking time” where I try to clear up any confusion between teams and make sure everyone has what they need for the day.