Search results matching tags 'Professional Development' and 'Training'http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&tag=Professional+Development,Training&orTags=0Search results matching tags 'Professional Development' and 'Training'en-USCommunityServer 2.1 SP2 (Build: 61129.1)CIOs: Stop Mandating Traininghttp://sqlblog.com/blogs/merrill_aldrich/archive/2013/11/04/cios-stop-mandating-training.aspxMon, 04 Nov 2013 19:36:03 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:51596merrillaldrich<p>I love to learn about new technology, and I especially love a long deep-dive technical session with a real expert or a well-crafted, inches thick technical book. Even if either one is expensive. Learning is probably my favorite thing to do.</p> <p>Yet I stand before you with an appeal: Stop “sending people to training.”</p> <p>Why would I say such a thing? Because failure is baked right into that very phrase: “sending people to training.”</p> <h2>Death by Training</h2> <p>Most of us in the IT world have probably experienced this scenario:</p> <p>The company has “vouchers” for “training” to be used at some training facility. A group is “sent” there to learn about some technology we ostensibly lack that will help the organization. In the group we have, let’s call him “Joe,” who is relieved to be out of the office with a legitimate excuse not to do any work, because it saves him from the work of not doing any work in the office. There is also “Phil” who has real work to do, but can’t, because he’s been sent to training. His phone is likely to ring a lot in the session, and he may or may not pay attention. Next to Phil is “Pat” who goes to every possible training session with enthusiasm, but as far as anyone can tell has not retained much of any use from those many hours. Undaunted, she is eager to soak up this WhateverTech 2.0 because it really is the future, etc. etc. etc.</p> <p>At the front of the room is a barely-interested instructor who just read up on this subject matter the night before, and will lead us in a death march of alternating PowerPoint slides, interactive exercises and coffee/bio breaks.</p> <p>This is deadly. It’s waste of time for the individuals involved and a waste of money for the company. If there is anyone capable in this episode, it’s even debilitating for them. This will fail, because the people participating aren’t going to provide the outcome you seek. It’s because they are not engaged, or not capable, or both. It’s because the situation is framed by expecting them to sit through training, not expecting them to succeed at their work. It almost guarantees the vouchers and the hours are wasted.</p> <h2>Expect Learning, not Training</h2> <p>What can you do instead? The technology landscape does change rapidly and the people on your team really do need to stay engaged in what is new, to keep your organization efficient and competitive. What you need is a culture of learning, not a culture of training. Consider whether you can incorporate these ideas into your team:</p> <ol> <li>Expect <em>learning</em> instead of expecting <em>training</em>. Create a culture in your team where new skills are valued because there’s a genuine sense that they matter, and reward the people who bring those new skills.</li> <li>Measure the team’s performance and make visible where new skills and tech have made a difference. Someone automated a horrible manual process? Celebrate that. Fixed a reliability issue that plagued operations? Celebrate. Created an HA solution where you needed one? Super. But make sure these gains are real, so the tech staff who know what’s what on the floor don’t become jaded about false praise.</li> <li>Support your team in finding <em>quality</em> learning opportunities they they are excited about. In my field that something like the PASS Summit, or SQL Skills Immersion Events. Fund those, and let people go (notice I didn’t say “send them”). If they aren’t excited about real learning opportunities, then start to wonder about how they are fitting in to this learning culture you need to create.</li> <li>Make learning a legitimate part of your team’s time – “I don’t have time to learn PowerShell” is not something you want to hear, just for example. Then make it an expectation. Then find and reward the results that people produced who stepped up with real commitment.</li> <li>Find the real skills gaps on your team, and proactively locate people to fill them. Look ahead six months or a year and see if you have people to successfully meet the changes coming down the road. Ask your best technical staff where the gaps are.</li> </ol> <p>This might look different in different organizations, and people have different styles. I can read a 1,200 page technical book, if it’s a good one. It takes hours – but the organization benefits from that time as I get better at my job. I realize not everyone wants to read like that. Some people use the web, some like conference attendance or conventional training - but good quality training and not PowerPoint death marches – and still others would like mentoring.</p> <p>No matter the style, it’s up to you to make the structure and create a set of expectations where the people on your team can, and want to, learn and grow. If they are personally committed then the team becomes unstoppable.</p>The Mentoring Experimenthttp://sqlblog.com/blogs/andy_leonard/archive/2011/04/21/the-mentoring-experiment.aspxThu, 21 Apr 2011 11:00:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:35058andyleonard<P><STRONG>Introduction</STRONG></P>
<P>I saw a <A href="http://thomaslarock.com/2011/04/the-mentoring-experiment/" target=_blank>recent post</A> on Thomas LaRock’s blog (<A href="http://thomaslarock.com/" target=_blank>Blog</A> | <A href="http://www.twitter.com/SQLRockstar" target=_blank>@SQLRockStar</A> | <A href="http://sqlpeople.net/post.aspx?postHeaderId=9" target=_blank>SQLPeople</A>) about <A href="http://thementoringexperiment.org/" target=_blank>The Mentoring Experiment</A>.</P>
<P><STRONG>The Experiment</STRONG></P>
<P><A href="http://thementoringexperiment.org/" target=_blank>The Mentoring Experiment</A> is a(nother) brain-child of Steve Jones (<A href="http://www.sqlservercentral.com/blogs/steve_jones/default.aspx">Blog</A>&nbsp;| <A href="mailto:w@way0utwest" target=_blank>@way0utwest</A>) and Andy Warren (<A href="http://www.sqlandy.com/">Blog</A>&nbsp;| <A href="http://twitter.com/sqlAndy" target=_blank>@sqlAndy</A> | <A href="http://sqlpeople.net/post.aspx?postHeaderId=85" target=_blank>SQLPeople</A>). As with their previous endeavors, this new venture is profound and elegant. It solves a problem for the community:</P>
<BLOCKQUOTE>
<P><EM>Finding a good mentor is hard. Most of us find mentors by chance or luck. It takes time to discover someone and build the relationship, some degree of chemistry, and a lot of luck. Or does it?</EM></P></BLOCKQUOTE>
<P>I like the premise a lot. </P>
<P><STRONG>Conclusion</STRONG></P>
<P>If you’re interested in finding a mentor, check out <A href="http://thementoringexperiment.org/" target=_blank>The Mentoring Experiment</A> today!</P>
<P>:{&gt;</P>