Author: geoffand

  • Modified Joke – Product Manager, the Lawyer and the doctor

    A doctor, a lawyer and a product manager were discussing the relative merits
    of having a wife or a mistress.

    The lawyer says: “For sure a mistress is better. If you have a wife and
    want a divorce, it causes all sorts of legal problems.”

    The doctor says: “It’s better to have a wife because the sense of security
    lowers your stress and is good for your health.”

    The product manager says: ” You’re both wrong. It’s best to have both so that
    when the wife thinks you’re with the mistress and the mistress thinks you’re
    with your wife — you can do some product management.

  • Lost hour of productivity

    Gotta whine.

    About once a month, I get an error in Outlook.  Something to the point of “OUt of resources” yada yada.  And it advises to “close some programs to free up memory…”

    Has that EVER worked?  Sigh.  I have 16 gigs, and am running 64-bit Windows 7 so there is literally a metric ton of memory free.

    Anyhow, from prior experience the only way to recover is to restart.  Sucks, but that is the only way. So I save all the work I have been doing and go to restart.  First warning that something is not copacetic: I get warnings that I have a modified normal.dot file in Word.  And I can’t ignore/cancel past it.  WTF.  Finally name it something bizarre and it reboots.

    Then I get a warning that PGP full disk encryption isn’t working right.  That has happened before, and it always is a fluke.

    Then outlook fails to start.  Says it can’t find the server, or my outlook.ost file.  Sigh.  I know what this means, I need to run scanpst.

    three iterations of that later, and one more reboot, and I am finally back working.  Lost time 1 hour. Lost time if I had called support? 3 hours (BTDT).

     

    Coda: I suspect these issues are caused by our policies and group settings in the domain. I have never experienced anything like this on any other Win 7 system, and I have been running it since 2009.

    Sigh. One of those days. Back to my wireframes and product requirements.

  • Ok, I get it already, we lose orders because we don’t have feature X

    I recently joined this company, and inherited a product that is world class.  But it is missing a pretty important capability (to be fair, when the product was originally developed, this was a feature that wasn’t even a twinkling in the eye of the market). 

    I get that we lose orders because we lack it. We are developing a capability.  It is not a 2 week (or 2 month, or even a 2 quarter) project. But there are still at least 1/2 the opportunties that do not demand the capability.

    Is it too much to ask you to not waste time on lost causes?  Is it too much to as you to sell what you have?  Our product is vastly superior in performance to all our in class competitors. It isn’t even close.  Focus on selling what you have. We will address the rest as soon as possible.

    But one thing I can tell you is that continuing to chase lost causes, and sending lost order reports will not get the project done faster.  In fact, it will cause me to tune out your grumbles.

     

  • Weird email problem – support useless

    The joy of working in a large enterprise. 

    We have been working with a web development partner for some new sites and moving some older sites to their hosting. 

    Part of this means that we have been exchanging details on the web sites we are migrating.

    Suddenly, these emails stopped coming in.

    They aren’t spam. They have no executables. There is no malware. Just business oriented emails, originated from a credible and trustworthy source.

    THe funny thing is, our contractor can send me emails that are not this (like “Did you get that PDF?”) fine.

    But copy that block of text, and it is halted. Save that text to a PDF and email. And it is halted. He had to friggin fallback to faxing it to me to get this information to me.

    Support – snort, is useless. Regardless of how much detail I put in the trouble ticket, or how many times I talked to them on the phone, there is no resolution.

    Da fuq is up with that?

  • Only three excuses from Engineering to change a Spec (requirement)

    You are sitting in you cube, listening to some kick ass tunes in your headphones, and an engineer drops in. “I need you to change spec X”.

    My response is to ask why, like all good product managers do.

    Invariably there are three answers

    1. It is impossible to meet that spec without changing the fundamental physical laws of the universe, and here is why …
    2. It is very difficult and we don’t know how to do it.
    3. It is difficult.

    Only one of those I will accept. Guess which it is…

  • Feeling like an underachiever

    Sometimes you stumble across someone who has accomplished so much in life that it makes you ponder your own life path. This happens frequently with me, but a few days ago, I bought the latest Paul Gilbert album, Vibrato (kick ass guitar work), and on it is a song that sounded familiar. Blue Rondo a’la Turk.  This sounded vaguely like some Keith Emerson pieces so I went searching (Paul Gilbert had done a live cover of the ELP staple “Karn Evil 9”). 

    Instead, as any true jazz afficionado will attest, that it is from the Dave Brubek Quartet’s seminal album “Take Five”. Fortunately, spotify has a lot of Dave Brubeck music.  But since I know nothing about Dave Brubeck, I hit wikipedia. Damn, what a long, and storied career. Here is his entry

    Feeling mighty small indeed. Still grooving to the Dave Brubeck quartet.

  • Annual Sales Training/Meetings

    Ah, I am procrastinating in the preparation of my decks for the sales meeting and/or training next week, I have come to reflect on the whole concept.

    I have written in the past on “Sales Meeting Musings“, as have others, including a snark filled comment by The Cranky PM.

    But this ritual is rife. Once a year (or every other year), you gather the sales people into a room, and you let them bask in the glory that is Sales, have them tell Paul Bunyon sized bullshit tales of their heroics (never once acknowledging the parachuting in of Product Management to salvage a HUGE deal), and to drink expensive booze and smoke cuban cigars.

    Every time, I have to prepare a deck. I have to tailor it to the lowest common denominator, usually a greenhorn sales asociate, or a senior guy that “doesn’t know how to spell AFM let alone how it works” even though he has 10 years of experience in the company.

    This is a hugely difficult task.  You have to cover the basics, and cater to the vast middle ground.

    This invariably comes down to stroking egos, yielding up the best nuggets from my market and competitive analysis (that I don’t want to share, because the blabbermouths will email it to their friends at our competitors) to keep their interest.

    One year, we had a product that was going gangbusters in photovoltaic research.  But our sales people couldn’t speak the language.  I put together a 4 hour bootcamp that started from the basics (semiconductor diode) through the principal technologies, and what we could do to improve efficiency and reduce costs.

    And not even a week later, I was required to fly to the Philippines to talk with a customer, because our sales team was too weak to do it.

    Weak sauce.

    Why bother?

  • The risks of expert-network participation

    At the referral of a friend several years ago, I joined the GLG group to offer myself as an expert.  I have a lot of knowledge of a lot of technologies, and companies.

    I got my invitation, filled it out, took their ethics training (every year), set my hourly rate, and waited.

    Every single query I have received was a request that seemed to imply that they wanted details of my employer’s business.

    Then I read this in the NY Times, and I am happy that I have applied the smell test of ethics to the queries.

    http://dealbook.nytimes.com/2012/11/25/new-breed-of-sac-capital-hire-is-at-ce…

    Increasingly, these “expert networks” are being implicated in insider trading scandals. Perhaps I was not being to paranoid and reading too much into the queries.

  • Presentations that are SO bad.

    About 6 months ago, I started a new job.  The former product manager had left about 18 months prior to my arrival, and they “limped” along.

    Now, I am going through sales presentations, sales training decks and curriculae and I am aghast at what I have to work with.

    The previous occumant of my role was a PhD scientist.  He had the attitude of “I’m the smartest man in the room” and he was out to prove it to the audience.

    However, that led him to build very wordy powerpoints. 10 bullet points each with two rows of text.  No illustrations of complex concepts (I mean, you are talking to sales, and they crave handholding). No thread or story.  

    In short, while there is some good information, the vehicle destroys the message.

    Sigh, it is going to be a long holiday weekend whipping some of these into shape.

     

  • The joys of a quality web developer

    Two days ago, we pulled the plug on the hapless guy who was on our project.  Not that he is a bad resource, but the project we handed him was beyod his scope, and it was flailing.

    We consulted another group in my company as to who they would recommend (and, most importantly who know our “system” if you catch).  We got turned on to a group in Pennsylvania.  Quick call, I forward on my original design document, and mockups, and the next morning we got a proposal.

    The price was very fair, and they were going to put extra people on it to allow us to launch on 11/27. At 10:00AM yesterday (MST) we gave the go ahead.  By 2:00 PM, we had artwork.  It looked awesome.  They captured what I was envisioning (and put in my mockups) perfectly. Today they have another two interfaces prototyped, and after a quick review are busy coding.

    I am beginning to think I might be able to start testing this next week.

    Of course, they were ecstatic about the fact that I had a document that described the workflow, the use cases, some typical user stories, and detailed mockups.  Apparently that is all stuff they have to tease out and build themselves.  I guess being a product manager has some positive attributes.

    Fingers crossed, but so far I am really happy.