Interface Technical Training Blogs - Mike Storm - How Quality Training Directly Relates to Job Performance

How Quality Training Directly Relates to Job Performance

So here it is...the Granddaddy of all discussions with regards to training. Was it worth it?

Was it worth the money? Was it worth the time I spent? Arriving at a difinitive answer for these questions can be difficult; for the student, for the Training Coordinator, Managers, etc.

Why?

Let's set the scenario...

You took a training class somewhere, and well, you learned some stuff, some stuff was relevant, some was just marketing you had already read, some stuff you had never seen before and didn't really apply at all, but one of your biggest issues was that, even though you saw some "Really Cool" technologies work, there was still a mental loss or disparity as to how it really applied to you, your organization or maybe even the current project you are involved in that drove you to get the training in the first place. Ring any bells?

Having a Fantastic Instructor helps a lot, but there is still an element missing....Hmmmm, what is it? Many students have found themselves in this predicament, and even if the Instructor is one of the best in the world, that Instructor is NOT going to be sitting next to you when you are in the middle of your project when what you've learned (or didn't) really counts.

If you are a person that has ever been there, and experienced this phenomenon, then this blog is for you.

This blog relates to what defines "True Quality Training", you know, the kind of training that is worth every penny to attend because you are learning and mastering "everything" you need to be an effective engineer or developer or whatever it is that you do. Sometimes as early as the first or second day you realize that the class is already worth every penny you've spent and every moment that you've given up to be there.

The kind of training that meets your objectives more completely than you may have even realized when you came into the class. Maybe even discovering expectaions for the training that you were not even aware of when you signed up."True Quality Training" should always exceed your expectations, not because the Instructor is really funny and tells good jokes or shows videos in class as a replacement for his/her ineptitude to actually facilitate learning properly... I am referring to training at such a level of quality that you achieve the deepest understanding possible of your chosen discipline, some may call it mastery, and that is a fair term to use. Whatever you call it, "True Quality Training" should empower you to immediately apply what you have learned upon exit from the class, with confidence! You won't even want that Instructor sitting next to you to guide you because it's now not necessary. You have already succeded on your own, and are confident that you can continue to do so. You may not realize it, but "True Quality Training" begins in the classroom...and continues...perpetually. Once you've attained the mastery of the subject matter, you'll be surprised when you realize that you've also attained the skills needed to continue to master new challenges, even outside of the classroom.

So I've rambled long enough about what we have seen and what we now want to see with "True Quality Training". Without getting into a class on psychology of the adult learner and blasting you with educational principals that just won't make any sense to someone unless they themselves are educators. Let's relate this to technology and business issues, stuff that makes sense to engineers, developers and techie types like yourselves.

One incredibly important element (principal) behind "True Quality Training", is the use of what some refer to as "real world." A term used so loosely in the technical educational arena, that half of the technical Instructors aren't even sure what the term means, much less how it applies to the educational process.

What really is a Real-World Scenario? (most all Training Centers claim that they understand it and use it...for most, this is not the case)

Real world is defined as a situation or problem presented in a context directly relative to a realistic situation. This may include, but is not limited to the process used by many or most to solve a common realistic scenario, whether right or wrong, or the analysis of the situation and it's direct relationship to the underlying business problem(s) and surrounding and related technology elements. Normally the phrase "real-world" is over used by anyone that feels that they can replicate at least part of a business problem or represent a single technology within a context that is applicable to the business problem. In truth, to be defined as a real-world scenario, the complete presentation of the business driver, business problem, analysis of the various courses of action, whether right or wrong, risk associated with each course of action, and the implications for the remainder of individual technologies that must blend within the Solutions Architecture are all required.

Yeah, that was pretty deep.

Simpler example. Just because you get to install Windows or Linux on a Rack Mounted Server instead of a Client PC, doesn't make it a "Real-World Scenario". But knowing why that server was chosen, what the server is intended for and what it will integrate with when complete, and how each action involved during the process affects the overall outcome of successfully integrating the intended technology that server will execute in conjunction with the 200 other servers your business uses could make this scenario classified as "Real World". Without a complete picture, a plan, a risk assessment and an impact analysis, this server install should never be allowed to happen. Get the idea?

Another major concept that was eluded to (in Bold Print above) when defining "Real-World" was the "Solutions Architecture". Let's face it, as engineers or developers or whatever, our job is to create solutions, solve problems, so everyone can make more money and enjoy their careers, right? We think, by human nature, as problems solvers, we make decisions and basically everything we do leads to a solution. Solution-based thinking is how we mature, and if we are subject to a learning environment that forces us to solve problems by creating feasible solutions and making good decisions, then the mastery of our "Real World Scenario" can begin to evolve.

So what then is this concept of a "Solutions Architecture" that becomes the catalyst for our mastery of a given discipline?

Solution Architectures are a blend of all relative units of study that make up a complete business solution. Business solutions may be derived from many aspects of business problems, risk or business technology challenges. The point of a solution architecture is to create a complete solution regarding all major units of technology study combined within the same relative context, producing a regression tested solution that meets the requirements of all aspects of the business problem(s) simultaneously. Students that operate within a solutions architecture have the luxury of experiencing all relative units of study simultaneously within their chosen solution, how they interact, how they affect one another, how certain interactions impose complications and implications that can hinder the goal of achieving the complete solution. While operating within the solutions architecture, a student will become intimately aware of all aspects of the proposed solution and gains a higher level of understanding of what is the sum of all parts. This deeper understanding of variables and implications lends itself to more effective application of what has been mastered when leaving the classroom environment.

I am a huge advocate of developing complete solutions architectures throughout all of the classes that I create and deliver. If you come to a Cisco routing and switching class, not only will you become intimately familiar with the gear you use, but you will be exposed to what the end result of a properly implemented Solutions Architecture is all about. How to mitigate various risks, create good documentation (and actually use it), how to design and execute based on a project-level plan, among other things that set Interface Training apart from everyone else I can think of. Using six basic solutions principles (in the Cisco world) Solutions architectures can be successfully created correctly the first time, every time:

1) Performance - What is expected for the business to operate its converged applications to an acceptable level with plans for what to expect in 3 years, 5 years or even longer

2) Reliability - Our Solutions architecture should provide this expected level of performance reliably 24/7/365, not just at midnight when no one is in the office

3) Redundancy - Rule of thumb is that you WILL lose 50% of what you have at some point and you MUST be able to maintain the reliable, expected level of performance if this occurs. "2 is 1, 1 is none"

4) Scalability - Being "future-proof" in your design is critical. You should be able to add technology, port density or additional locations without requiring a re-design of the network. Having free slots in a switch chassis is one good example versus fully populating a switch because you are not thinking ahead.

5) Defense-in-Depth Security - Barriers everywhere...inside, outside, in between, dynamic products and excellent correlation and analysis products are very important. Your network should be a fortress. If your first line of defense is compromised, there is another defense mechanism there to prevent an all-out breach.

6) Management or Managability - Toughest of all to achieve, especially with the diversity of products that we use today. Normally it takes several management platforms to monitor and respond to everything proactively in a large enterprise. But necessary nonetheless.

You have probably guessed that this amount of effort was put into this blog is to prove some sort of point...and you would be right. True Quality Training is extremely hard to find, especially from a typical technical training center. What I would want to accomplish here is to create a vision in your own mind of what you expect 'Quality" to be. Take that vision, focus on it, defend it, be critical of those that claim to offer it, and do yourself a favor...EXPECT IT! If your training provider does not meet your expectations, continue searching until you find the environment that meets your needs. Myself, I am extremely critical of Instructors and training programs alike, primarily due to being in that line of work myself. I am a perfectionist, always trying to push my own bar higher and I take great pride in my work, but most important to me, is the effect I can have on the success of my students. When they enter my classroom, I have but one objective; everyone in the room leaves 'primed for success'. The students expectations and educational needs become my direction for execution of each moment of the course. I am a learning facitlitator, and if I am to do my job well, everyone will learn, and they will master. Mastery leads to success and success keeps you moving perpetually forward, which leads to additional success; a most reiterative process. Training may begin in the classroom, but if it is good enough, it will never stop when you leave. Remember that you "do not always get what you pay for", and paying too much for bad training is always a raw deal. Quality only comes when one cares enough to acheive excellence. In education, quality can not be given a standard price tag; true quality can be priceless. It can be life-changing.

Now it seems, we are really pushing the envelope of impossibility, right? Well, I do know of one place that actually has the ability to do it, does it consistently, and you happen to be on the website as we speak...Interface Technical Training. (sure it sounds like shameless marketing; when you see it for yourself you'll know why I wrote this blog)

The quality principals discussed herein extend to all of our programs, Windows, Systems, Enterprise Applications, Cisco, Security, Development...you name it, we live it. ...And we are proud of it. Our Instructors rate highest in the country for student experience and success. (ask MTM for a report) Our programs do more than educate on technology. They are founded in educational principles; designed to help our students develop planning, execution and problem-solving skills critical in the real world, in addition to their mastery of the technology. Classtime discussions and hands-on exercises fixate on mastery of each technology based on its practical orientation within the 'big picture' and implementation based on industry proven technique and best practice. The framework for our solutions-based classes is deliberately architected to mimic the realistic and universal scenarios, focing you to think through them and implement precise solutions based on stated objectives, not recipe steps like most labs go; step-by-step instructions do not exist in real life and have no place in the mastery process. As a human being, believing your 'own data' is all that you can trust, and discovering that data on your own, so it is second nature and never forgotten is the key.

Don't take my word for it. Decide for yourself. Schedule a time to come in and check out the environment, maybe sit in for a few minutes while several Instructors teach to see what I am talking about. It's free. You must discover quality for yourself and it is a very individual experience. I am confident that our team at Interface will surprise even the most critical learner, and will always go the extra mile to exceed your learning expectations. It's called 'Quality'.
Its what we do.
It's what we will always do.

The next time you actually have to Master a Technology or Solutions Architecture and want to experience it in the most "real-world" environment possible, it'll be worth your time to check out what Interface has to offer you......SUCCESS!