Ivanti Consultant, developer, or architect?

Ivanti Project Implementations are quite simple, it’s people that make Ivanti implementations difficult.

Gregor Anton | Freelance ITSM Consultant wih100+ Implementations, worldwide, since 1996

DISCLAIMER: Not endorsed by, affiliated with, or sponsored by Ivanti, ServiceNow, Remedy, Infor, or Sage. Any use of the software product names is descriptive of product experience/skillset or used to review the ITSM and CRM products.

When you’re dealing with an Ivanti Consultant you really need to take a step back and evaluate the skill set and more importantly the competencies.

Nowadays anyone that has gone through Ivanti’s Certifications uses the “consultant” title. More often than not most Ivanti HEAT Consultants are junior developers. I know of many consultants with 10+ years experience that still are junior developers. Why? Experience, Skill, Competency. Fun fact, the word consultant is derived from Latin, “to discuss”.

Case & Point, most “consultants” do little more than gather technical requirements. A real consultant will elicit business requirements, offer practical solutions, best practice advice, discuss solutions with a business perspective, all with a holistic approach.

One notch above Consultant are Ivanti HEAT Architects. From Latin, “chief builder”, that have intimate knowledge of the technical architecture and possess an uncanny ability to design and discuss. This is the rarest type of consultant you will come across in the Ivanti HEAT World. Most “consultants” are really “developers” focusing on configuration & details, vs discussing, designing, and leveraging experience in building business systems & solutions. In other words left brain meets right brain.

What about Project Managers you might ask? Well Project Managers are for scheduling resources, booking calendar appointments, getting the team organized, checking holiday schedules, but quite frankly should not be involved in the decision making process.

This should matter to you because most Ivanti Implementations go off-track or fall quite short on delivery simply because a lack of skill, competency and quite frankly having the wrong people involved. Worse yet often the software product is blamed because the developer, consultant, project manager, or architect don’t have the skill set, experience, or know-how.

Are you getting the most out of your ITSM Implementation? You are not. Not until you “consult” with me!