Skip to main content

Product Parenthood

It has been a long time since I've been able to sit down and write a lucid blog post.  This one will not be one of them.

I've come to realize that my full-time job as a Product Manager, my other full-time job as a husband, and my newest (and most demanding) full-time job as a parent (to a delightful son) consume roughly 100% of my time; leaving precious few moments in the day in which to gather and synthesize my thoughts.  Thus, I've been using Twitter more often and blogging less.

"Blogging less?  What?  You only have 3 prior entries!"

I used to blog quite a bit under a different moniker.  However, as a parent, I have come to the realization that composing longer, thoughtful essays are a luxury that I generally cannot afford.

With that, I've added my Twitter feed to the left, and will make an effort to write "larger-than-micro" blogs here on at least a weekly basis, if not more frequently.

And now it's back to full-time job #1, followed by #s 2 and 3 this evening.

Cheers!

Comments

  1. Can fully appreciate that, not even 3 months into item 3.

    ReplyDelete

Post a Comment

Popular posts from this blog

Improving Win Rates

Still here at the Gartner Local Briefing. In a session with Richard Fouts about customer win rates. Sharing Win/Loss Data Sales teams tend to advertise their wins, yet contain their losses. Why is this so? Q:  How many global IT companies conduct win/loss on an enterprise scale? Less than 5%? About 10%? About 20%? A: Less than 5% Why? CEOs and Sales people say "I know why we win/lose".  Some politics are touchy; people don't want you to expose what they did well/not (especially in competitive environments).  "I clicked the won/loss checkbox in Salesforce.com" One company evaluated their win/loss data. They looked at 140 wins, and 55 losses. Looking at this data, they noticed a correlation between the wins and the fact that they beat their competition to market with compelling announcements in over a third of the scenarios. An IT services firm attempted to sell a more sophisticated solution. Upon evaluation of the win/loss data, they fo

Luck Is Not The Answer

As the 2011 season of the National Football League approaches, so does the rabid anticipation of its parasitic counterpart; fantasy football. Anyone who knows me knows that I love football (not fútbol); particularly the NFL . I grew up a dedicated Patriots fan and have since become more of a fan of the game itself rather than just a New England loyalist. I tend to keep up with NFL news throughout the year, and regularly download the Rich Eisen Podcast for listening during my morning commute. Rich's guest on the most recent episode was Michael Fabiano, the resident fantasy football expert at NFL.com. At one point during the podcast, Rich and Mike were exchanging viewpoints on what constitutes being an expert and how no matter how much of an expert you are, you need to be lucky to win a fantasy league. A similar sentiment was expressed during a 2010 podcast by one of the guests (I forget whom); that it's all luck and you can't really predict anything. I take exception t

Hiring: Scheduling Interviews

Interviewing candidates is never easy. There's a lot at stake . Many notable managers and companies will bloviate about their hiring processes; often in self aggrandizement but occasionally to share tidbits of wisdom. A successful hiring process requires that a lot of pieces be firmly in place. Corporate messaging. Job descriptions. Salary ranges. Benefits packages. Application process. Referral programs. The list goes on... One very important yet often overlooked item is scheduling, and that is the focus of this post. While interviewing a candidate recently, I was doing my routine pre-interview preparation and reviewed with whom and when the candidate had already spoken. To my confused dismay, I learned that the candidate had spoken to 5 people already on three separate days . I was to be the 6th interviewer (on day #4), and there was still one more interviewer scheduled for later that week. That's 5 distinct interview periods!!! After conducting the interview, I