Learning How to Learn for A New Role

Taking on a new role in an organization or a new company is always an interesting opportunity that can make people experience a myriad of emotions ranging from being charged up and motivated all the way to feeling imposter syndrome.

When the role is out of the traditional field or work that the person has been doing, or even in a new company, one of the key challenges the person has is learning how to learn.

After being in a role or place for a while a person develops the ability to know where to go for information, how to stay ahead of the curve in terms of what’s next in her/his respective field, or even where to start when s/he doesn’t initially know something.  When starting something or somewhere new, that usually has to be learned all over again.

The key then is knowing that, while initially obtaining certain specific information (like laws, codes, or processes) could be important to hit the ground running,  the key focus for longer term success and growth in a new domain or place is really figuring out where to go to get the right learning.

Some of the key places to look are standard industry or internal group resources that are readily available, but there are a myriad of less obvious resources as well. One of the things I like to do is search for people on twitter that have conversations or are well known in that field, and then see where they seem to re-tweet information from or what they allude to in terms of where their getting information.  Lots of times these type of resources are the ones that aren’t generally as obvious, but more valuable.

So, how do you learn where to learn from?  Who could benefit if you wrote out exactly how you’re learning in your current field, would that process even surprise you? Any good tips on hacking the on-going learning process for a specific field?

Matt Kane

Share and Enjoy:
  • Facebook
  • Twitter
  • LinkedIn
  • StumbleUpon
  • Digg
  • Google Bookmarks
  • Print
  • del.icio.us

Leave a Reply

Your email address will not be published. Required fields are marked *