Partners vs. Not Partners

Oh well, it’s happened a few times to date, but it happened again recently.

I joined an internal customer con-call a while back and got through the initial design only to be told that the customer doesn’t like partners working on their projects.

Like I said – it’s happened a few times.  The strange thing about this one is that a few other sources said that this was more about the preferences of the EMC Sales team than it was the customer.  Again, not surprised, but what they don’t understand is that a lot of EMC’s best talent are partners.

Just for the record.  I do as good or better a job than most of my internal counterparts.

I just do it without 90% of the tools they have at their disposal.

2 comments

    • on October 12, 2008 at 6:52 pm
    • Reply

    I’ve worked both for an EMC partner and then as EMC PS staff. It was easier to get stuff done as a staff on the partner company. Whilst EMC has fine products, I think their professional services division is trying to look bigger than EDS, etc which means more red-tape and pleasing chain of command than actually doing the work. As partner I could pull rank through the customer’s channels and get stuff done. Of course, it helps to have a good collection of SymCLI based scripts and NOT have to use EMC’s GUI tools – which (at least for me) always required a lot more futzing to get the same things done.

  1. I like to look at it more along the lines of: If I can do this well without the tools, imagine what I could do WITH them. 😉

    As far as GUI based tools, I’m not a big fan either. If I can’t do it through command-line I’m really not interested in doing it. The only time this doesn’t apply is when talking about doing Symmetrix/DMX changes via SYMCONFIGURE or doing a bin-load using SymmWin.

    Then I’ll take SymmWin any day of the week and twice on Sunday.

Leave a Reply

Your email address will not be published.