SIGH.
I am here for the bi-annual Sales Meeting that my company has every year. Today I had to present my product and product updates for all the sales folks. It was nerve-wracking but fine. I don't like public speaking but it's a necessary evil in my job. Typically, all of the presenting participants are invited to dinner to mingle and press the flesh of the revenue generators they hardly ever get to see. Let's face it, they have better things to do than hang out with a bunch of product folks. Because of this, I decided not to pack running clothes or shoes because I figured (as has been the case in the past) that I'd go straight from the meeting to dinner. But this time, that was not the case. I ended up dateless for dinner with nothing but time on my hands.
UGH! I could have gotten a nice, long RUN in.
Oh well, I guess there are just some things you can't account for. Not being "required" at dinner is one of them. I have to admit, I'm a little disappointed. I like our sales folks. They are fun, positive and vibrant. They keep the faith and add cheer to a company that sometimes has trouble seeing the opportunities for the risks. I love them for that. They believe!
So my thoughts turn from technical product roadmaps to the triathlon off season, my lackadaisical training regime as of late (sorry Coach Liz) and what the next season will hold. I have pondered another 70.3 race and when it's all said and done, I don't wanna. AND, I feel GUILTY about that. I did not have what I would call at GREAT race this year. I trained, stressed and really put the time in only to have it not work out on race day. STILL, I feel some sort of odd obligation. So as I sit here sort of pouting and pondering next year's race calendar, I realize that putting together next year's roster of races is not unlike certain aspects of product management.
As a product manager, you consider your buyer and/or user (me), what characteristics, abilities and limitations she has and build a product that meets her needs or addresses her pain points. As the "user" I've had some good training experiences and some not so good ones this season. I have sensitive feet that need constant monitoring due to past injury and a longing to get more than two rest weekends of my summer back from relentless triathlon training. I love to train and combine my vacations with training and/or exercise (there is a difference). If I had a wish list for swimming, I'd swim in the sea every. SINGLE. day. Rivers freak me out and there are always those damn jellies! I am very busy with the day job and really need to race in events that "sharpen the spear" instead of build toward something big.
When I consider myself as the "user" of my race season, the complexion changes. I become less emotional and more logical about what's best for my body, mind, spirit and life.
I ponder the requirements list for a good race calendar:
- Not so short that's it's boring (sprint) but not so long that I am panic stricken if I miss a long brick (70.3 or over)
- Breaks the monotony
- Fewer jellyfish stings
- Allows for more pure run races
- Keeps my weekend training down to less than three hours
If I were to try to design a schedule for the me tri user based on these requirements I would choose Olympic distance tris and/or duathlons. And you know what else? I would NOT feel guilty. I would feel like I'd MET the requirements and answered the pain points.
So as I sit here and type instead of run, maybe the best way to think about the new season and assuage my guilt is to see it through the lens of a product manager. Internalize what the requirements are instead of what I feel on emotional level is "not enough". I can then choose races and set goals around the time for those races that make me feel proud for having made the effort.
The product approach, who would have thought?
Posts
No comments:
Post a Comment