My friend Lindsay Hill wrote about the potential negative sides of joining an
ambassador program. Lindsay brings up lots of valid points. My response here is
to explain why I’m in one, which might not be obvious from the outside looking in.
Independence
Both Lindsay and I are CCIEs. Going after that certification is not something you
are going to do unless you find that vendors products to be of acceptable quality.
As a CCIE if I have two comparable products at the same price and one of them is Cisco,
then I’m going to lean towards Cisco.
If the Cisco device does not match the requirements or if there is a big difference in
price then I’m not going to promote the Cisco device at all costs. I’m a professional and
I’m expected to to know my way around HP, Huawei or whatever comes in my way.
I’m not afraid to speak up if I find something negative about Cisco, however the best
result is usually achieved by trying to find the right channels to bring up your issues.
Blindly writing stuff on Twitter is less likely to get any attention.
Why I’m a Cisco Champion
Let’s be honest, it’s always nice being recognized. It’s human behaviour. If I were
to list the reasons why I’m in the program though it would look something like this:
- Earlier access to news about products/events
- My contact list within Cisco is growing
- The chance to actually affect what Cisco puts out on the market
- The chance to interact with other champions and pick their brains
- Recognition
How does that help my clients?
I’m a senior network consultant and I spend a lot of time working on Cisco. By
knowing more about what’s going on inside Cisco I can give better advice to my
clients. Obviously a lot of stuff is under NDA so I can’t talk to my clients about
it.
By having a bigger contact list I can reach out to people when I am facing issues.
I also have a chance to influence people within Cisco to bring up these issues
internally which could lead to a bug fix or a new software version.
Conclusion
I agree with Lindsay’s thoughts. In the end it’s up to the person joining if it’s
worth the benefits and if you can stay neutral. Personally I would never advocate
a Cisco solution if I think there are better options out there for my clients.
If you are in doubt you should ask your consultant to explain why they are
choosing vendor X over vendor Y. If they can’t motivate it, then they are out
on thin ice indeed.
Why I’m a Cisco Champion
Let’s be honest, it’s always nice being recognized. It’s human behaviour. If I were
to list the reasons why I’m in the program though it would look something like this:
Earlier access to news about products/events
My contact list within Cisco is growing
The chance to actually affect what Cisco puts out on the market
The chance to interact with other champions and pick their brains
Recognition
——————————————–
In other words none of these could be achieved without being a champion.
There is a couple of good CCIEs around who write articles about network devices that are not branded Cisco. I am curious to find out if being a Cisco champion restricts your choices to write about any other vendors and I am looking forward for articles about other vendors’ products.
Some of these can be achieved by working for a large SP or company that is important to Cisco. Or if working for an important partner.
I’m not restricted to writing about Cisco, this is my own blog so I write about what I wish. It’s just that I work mostly with Cisco but if I run into something interesting I will write about it. Maybe I’ll write something about Huawei in the future.
Pingback:Vendor Clubs: Watch Your Independence | LINDSAY HILL
Write about Linux virtualization haha.
Its human nature. Not all the things can be attractive to us at the same time.
I will not go into discussing products etc but Cisco has good contribution to knowledge base as well. Cisco has great influence in standardization bodies etc. Today besides few large SPs and companies in Sweden there is hard to find any enterprise who have total Cisco solutions. The world is more multi-vendor than it was yesterday.
Thanks