Bruce’s Top Ten List got me thinking along similar lines, so here are the 10 things I think are the best tools in job search.
1. Friends; Kind of weird to put our friends in the category of tools, but they are the single most important piece of your job search. Study after study and anecdote after anecdote tell us the same thing, The precise numbers vary, but they all say, “More than 80% of all jobs come with some level of personal introduction.” In other words, a friend introducing you to someone who introduces you to ….. So your friends are your most important tool in job search.
2. Pay-it-forward networking. This is a direct corollary to 1. We make friends by helping people we genuinely like and the people we like are those very friends reviewed in 1. Look at the book “I’m at a Networking Event, Now What” by Sandy Jones-Kaminsky, it provides simple clear tools for effective networking. Its all based on the idea of helping first. Useful networking starts with relationships that go beyond a simple business card and elevator pitch. That comes from trust and common values etc. There simply isn’t a better, faster way of doing this then helping.
3. Linkedin. Speaking of our friends or “network”, Linkedin is the best tool for documenting and mining that network. It’s work related social networking and allows us to understand how to help our friends and allow our friends to help us.
4. Internet “aggregators” . Tools that allow us to set up one search that covers a bunch of web pages on a regular basis. For example, Indeed.com covers several hundred job boards, so we can set up a single search that routinely sends the results to your email, or on an RSS feed. Another one is Linkup.com, it searches company pages with opportunities. Google Alerts does the same thing with information, so if you are focused on a particular company or job title, virtually anything, it will give you a daily list of updates
5. Work-Life DB™. This is a tool we created (and trademarked) and I haven’t found anything as effective or as complete in helping a person document their success and their history. We all know and pay at least lip service to the idea that job search is a sales position. The first step in effective, ethical sales is product knowledge, in this case that translates to the history of our success.
6. Strengths Finder. A corollary to 6. This is an outstanding test/process that helps us refocus our heads on our strengths, those things we naturally do very well… which is the same list of the things we do in a non-voluntary way. Check out my earlier post on this, it’s very cools stuff.
7. Public Libraries. Given that research is one of the crucial steps in job search, there simply isn’t a better place to do research. Locally, King County Library has this amazing list of research tools for job search and researching companies.
8. GIST. If research is one of the keys to success in the job search, then this add-in to either Gmail or Outlook is an amazing shortcut in that process. It automatically collects basic info, actually more than basic, about our contact list. Once someone is set up as a contact, Gist will provide you with an ongoing way of staying current. Is someone on Twitter? It will give you their last 5 tweets each week, Blogger? Their last posting. Linkedin? Any changes.
9. Bing/Google. Our old friends the basic search engines. What can I say that hasn’t been said? I include both because Bing has become a very useful tool and isn’t a clone of Google, so running searches in both tools provides additional information and both are very helpful.
10. Job Clubs. Groups like Notes From the Job Search (check out our schedule in the right column) provide support as we go through job search. So much of job search is incredibly difficult simply because of the isolation inherent in spending time looking for opportunities. Even the most qualified candidates can spend weeks and months sending off 10’s, 20’s even 100s of resumes without any response, so how the dickens can we remember that much of the craziness isn’t personal. Heck, it’s not even related to the quality of your applications. Finding a peer group going through this makes it much much easier.
Showing posts with label strengths. Show all posts
Showing posts with label strengths. Show all posts
Tuesday, December 28, 2010
Wednesday, October 13, 2010
Do what you love and the money will follow
One of my clients recently forwarded an article from a group named “Recourses” about work-life balance and following your passion.
It’s very interesting but actually comes across as a bit of a rant suggesting that following your passion is a great way to starvation…. The article isn’t signed, but my guess is that the company is small enough so that if you are a regular, you pretty much know who the author is.
I think my client sent it to me because I have asked her several times, “What would you do for free?” as we have focused her career search. So here comes someone with a dramatically different point of view, or it sure looks that way to begin with.
The first clue is that he frankly acknowledges that he personally “loves his work”. So how does that fit with the idea that we shouldn’t follow our passions?
I think the part he is actually objecting to isn't that people want "to love what they do", but that many times people don't include market realities. I love music... really really love it, but making a living at it would be more than a stretch.
The challenge isn't so much identifying things that we are passionate about, but things that we are passionate about and that people will pay us to do. He's also ranting about people wanting their job to be all of the good and none of the rest. He's right about this as well, heck even musicians need to practice. The man who invented classical guitar as a legitimate discipline, Andres Segovia would practice a new piece for 2 years before he performed it. When the great Seattle Sonics point guard, Gary Payton entered the NBA, he was amazing at getting to the basket, passing and controlling a game, but he had no outside shot. He spent the next several years shooting 500 shots 4 days a week and 300 on the other 3. He did this on his own time. Was it his favorite part of the day? Probably not, but it was necessary if he was going to be as good as he hoped and it was necessary if he was going to be able to lead his team. I love being a Career Coach, but part of being a coach is writing, which I actually hate, I also know that I need to continuously research the job market to stay current and to have deep enough pockets to last long enough for it to become a viable business.
The point is that every job has both good and bad. The author uses his own childhood, growing up on a coffee plantation as an example of what it means to work hard at something you don’t care much about. In fact his example of the coffee farming is in many ways apropos, as I do know people who are passionate about coffee and who grow coffee because of this. They know exactly how hard it is and bust their tails doing it. The consequence of this passion is their coffee regularly wins awards, sells for $36 a pound and sells out every year.
Another piece not being acknowledged is what the job market is like right now. Employers have choices. A consequence of this is that they are choosing the very cream at every opportunity and frankly, if you aren’t passionate about what you do, it’s much harder to be part of that cream.
I repeatedly ask my clients “What would you do for free?” The reason is that in today’s market place, if we hope to keep up, then we are studying our profession on our time and our nickel. No one does this when they aren’t passionate.
Going back to the coffee plantation analogy. My guess that his farm was moderately successful, but the people making more than a simple living are the ones continuously learning and improving their product.
So will the money follow just because you are doing what you love? Maybe…. Will the money follow if you are doing things you don’t like? Probably not. The key in both cases is what you do or don’t do to prepare and doing what you love makes that preparation much much easier.
It’s very interesting but actually comes across as a bit of a rant suggesting that following your passion is a great way to starvation…. The article isn’t signed, but my guess is that the company is small enough so that if you are a regular, you pretty much know who the author is.
I think my client sent it to me because I have asked her several times, “What would you do for free?” as we have focused her career search. So here comes someone with a dramatically different point of view, or it sure looks that way to begin with.
The first clue is that he frankly acknowledges that he personally “loves his work”. So how does that fit with the idea that we shouldn’t follow our passions?
I think the part he is actually objecting to isn't that people want "to love what they do", but that many times people don't include market realities. I love music... really really love it, but making a living at it would be more than a stretch.
The challenge isn't so much identifying things that we are passionate about, but things that we are passionate about and that people will pay us to do. He's also ranting about people wanting their job to be all of the good and none of the rest. He's right about this as well, heck even musicians need to practice. The man who invented classical guitar as a legitimate discipline, Andres Segovia would practice a new piece for 2 years before he performed it. When the great Seattle Sonics point guard, Gary Payton entered the NBA, he was amazing at getting to the basket, passing and controlling a game, but he had no outside shot. He spent the next several years shooting 500 shots 4 days a week and 300 on the other 3. He did this on his own time. Was it his favorite part of the day? Probably not, but it was necessary if he was going to be as good as he hoped and it was necessary if he was going to be able to lead his team. I love being a Career Coach, but part of being a coach is writing, which I actually hate, I also know that I need to continuously research the job market to stay current and to have deep enough pockets to last long enough for it to become a viable business.
The point is that every job has both good and bad. The author uses his own childhood, growing up on a coffee plantation as an example of what it means to work hard at something you don’t care much about. In fact his example of the coffee farming is in many ways apropos, as I do know people who are passionate about coffee and who grow coffee because of this. They know exactly how hard it is and bust their tails doing it. The consequence of this passion is their coffee regularly wins awards, sells for $36 a pound and sells out every year.
Another piece not being acknowledged is what the job market is like right now. Employers have choices. A consequence of this is that they are choosing the very cream at every opportunity and frankly, if you aren’t passionate about what you do, it’s much harder to be part of that cream.
I repeatedly ask my clients “What would you do for free?” The reason is that in today’s market place, if we hope to keep up, then we are studying our profession on our time and our nickel. No one does this when they aren’t passionate.
Going back to the coffee plantation analogy. My guess that his farm was moderately successful, but the people making more than a simple living are the ones continuously learning and improving their product.
So will the money follow just because you are doing what you love? Maybe…. Will the money follow if you are doing things you don’t like? Probably not. The key in both cases is what you do or don’t do to prepare and doing what you love makes that preparation much much easier.
Monday, October 4, 2010
Stories from NFJS -- Fred’s Story
This one is about Fred (not his real name). He joined NFJS as our Work-Life Data Base™ was maturing and he embraced it. What makes his story interesting is the consequence of this process.
Fred’s profession is software and hardware testing, with a strong element of audio technology thrown in. He joined us at the very bottom of the recession when more than half of the jobs being advertised were bogus and at least half of the rest required that you walk on water without looking for the rocks. One job description asked for a web developer who could answer phones, run purchasing and pick the laundry… and the only part I’m making up is the purchasing. Microsoft had just cut what they would pay contractors 10% across the board and was routinely demanding skills that were a full step above the pay they were willing to provide. I don’t ever remember a time when the economy was worse or when finding a job was tougher.
Fred sounded very realistic about his situation. He said that he was hoping for a new contract where his pay would be at least 80% of the last one. I’m very familiar with the skills he described and with the employment environment in that area having recently left the industry myself. When I reviewed his original resume, it sounded like that was a reasonable hope, but he better be capable of making more than a few house payments with his unemployment.
NFJS was just at the beginning of our resume section at that time. We spend four weeks of meetings going over the “How to”. It starts with the basic fundamentals of resume writing and ends with our Work-Life DB™. This is a tool that allows people to document their success and put it in a format that easily translates into a custom resume.
By far the most important part of all this is the Work-Life DB™. The first thing it does is highlight the most powerful stories in their work history. It helps the writer understand that they are not asking for charity. Great candidates are not asking for handouts, they are offering to help a company solve specific problems.
Back to Fred.
He understood all of this immediately, then he did the work. There are three parts that matter in this story. Number one: documenting your success. Fred went back through his history and wrote down what he was responsible for and what he accomplished at each of his previous positions. Number two: putting this information in structures that communicate effectively what he accomplished. And three: Using the language that companies expect and understand.
The result was dramatic: “Executed weekly test passes of more than 5,000 tests (Tux and Tuxnet) generating more than 100,000 results.” Became “Lead the XXXXX automation test lab for the development of XXXXX, maintaining more than 5,000 tests cases and managing the execution of test passes generating more than 100,000 results.” The first one is ok… the second one is excellent. The second one highlights the context in which his work occurred and claimed all of the responsibility Fred had. The first one names tools that are important to Microsoft, but only Microsoft. If Fred wanted to work somewhere else, then the hiring company would either scramble for Wikipedia or eliminate (this is the kind of thing Fred would have included when applying at Microsoft.)
Fred got the job!
The new resume has energy and it has relevance and it has the language that was being looked for by companies that do the kind of testing Fred does and is responsible for. The result of this work was that he got an interview for an FTE position at another company, then got the job! His new role is leading automated testing for both hardware and software for one of the products this organization produces and he got a 20% raise!!!
Yes, Fred is highly skilled and yes, he is in a role that is always looking for quality people, but when he joined NFJS, that was not clear, especially to Fred. As he dug into his experience, he developed an understanding that allowed him to identify, apply for and win a position he had been preparing for, for most of his professional career…. Even while the “economy” totally tanked.
Fred’s profession is software and hardware testing, with a strong element of audio technology thrown in. He joined us at the very bottom of the recession when more than half of the jobs being advertised were bogus and at least half of the rest required that you walk on water without looking for the rocks. One job description asked for a web developer who could answer phones, run purchasing and pick the laundry… and the only part I’m making up is the purchasing. Microsoft had just cut what they would pay contractors 10% across the board and was routinely demanding skills that were a full step above the pay they were willing to provide. I don’t ever remember a time when the economy was worse or when finding a job was tougher.
Fred sounded very realistic about his situation. He said that he was hoping for a new contract where his pay would be at least 80% of the last one. I’m very familiar with the skills he described and with the employment environment in that area having recently left the industry myself. When I reviewed his original resume, it sounded like that was a reasonable hope, but he better be capable of making more than a few house payments with his unemployment.
NFJS was just at the beginning of our resume section at that time. We spend four weeks of meetings going over the “How to”. It starts with the basic fundamentals of resume writing and ends with our Work-Life DB™. This is a tool that allows people to document their success and put it in a format that easily translates into a custom resume.
By far the most important part of all this is the Work-Life DB™. The first thing it does is highlight the most powerful stories in their work history. It helps the writer understand that they are not asking for charity. Great candidates are not asking for handouts, they are offering to help a company solve specific problems.
Back to Fred.
He understood all of this immediately, then he did the work. There are three parts that matter in this story. Number one: documenting your success. Fred went back through his history and wrote down what he was responsible for and what he accomplished at each of his previous positions. Number two: putting this information in structures that communicate effectively what he accomplished. And three: Using the language that companies expect and understand.
The result was dramatic: “Executed weekly test passes of more than 5,000 tests (Tux and Tuxnet) generating more than 100,000 results.” Became “Lead the XXXXX automation test lab for the development of XXXXX, maintaining more than 5,000 tests cases and managing the execution of test passes generating more than 100,000 results.” The first one is ok… the second one is excellent. The second one highlights the context in which his work occurred and claimed all of the responsibility Fred had. The first one names tools that are important to Microsoft, but only Microsoft. If Fred wanted to work somewhere else, then the hiring company would either scramble for Wikipedia or eliminate (this is the kind of thing Fred would have included when applying at Microsoft.)
Fred got the job!
The new resume has energy and it has relevance and it has the language that was being looked for by companies that do the kind of testing Fred does and is responsible for. The result of this work was that he got an interview for an FTE position at another company, then got the job! His new role is leading automated testing for both hardware and software for one of the products this organization produces and he got a 20% raise!!!
Yes, Fred is highly skilled and yes, he is in a role that is always looking for quality people, but when he joined NFJS, that was not clear, especially to Fred. As he dug into his experience, he developed an understanding that allowed him to identify, apply for and win a position he had been preparing for, for most of his professional career…. Even while the “economy” totally tanked.
Friday, September 24, 2010
Stories from NFJS
My desperate hunting for blog ideas has been solved!
I mentioned that I joined a “support group for reluctant bloggers” in an earlier blog and this week I was able to get to there for the second time. While participating, I had an epiphany as another member talked about the stories of her clients and their success, I realized that I haven't written a single story about the participants from NFJS and what's happened to them. Once that penetrated my thick skull, the hard part is choosing. While I’ve been doing Notes from the Job Search for a little more than a year and a half, the principles I use evolved over 30 years, so the stories end up going back a long time.
Here’s a story about a young soldier reentering the civilian world
Somewhere along the line I learned the value of separating the activity a candidate does from the product they work on. About 3 years ago a young friend of mine sent me an email asking for help. This young man (I’ll call him “Jim”) went to college majoring in Computer Science on an ROTC (Reserve Officer Training Corp) scholarship, graduating in 2002. Well surprise, surprise, he was immediately activated and spent the next four years on active duty with the last two being in Iraq as a transportation officer. He mustered out in 2006, took a year off and had been looking for work for six months prior to reaching out to me. In those months, he had received nothing more than an automated response while submitting more than 100 resumes for various jobs in the IT industry. His goal company was Microsoft and he hadn’t even gotten an automated response from them.
I asked him to send me a copy of his resume and upon reading it understood the problem immediately. His resume was completely built around his experience in Iraq and he was applying for jobs as a project manager in IT.
We got on the phone together and I had him describe what he was responsible for. As he was doing this I kept asking him to avoid talking about trucks or transportation and spend more time focusing on his personal responsibilities. So when he said something like, “I had to get trucks filled with medical supplies from town A to town B on a weekly basis while making sure that we had supplies coming in from the States that would allow us to meet our schedules.” I helped him transform that into “developed schedules for multiple teams, coordinating multiple interdependent projects to deliver requirements on time and on budget.” Which is in fact a description of what he did, minus the references to Iraq and the Army and trucks. It is also describing his behavior in IT terms rather than Army terms.
One of the many great things Jim brought to this was an openness and ability to learn very quickly so the time necessary for him to completely re-write his resume was less than a week. When he submitted this new resume he started getting personal responses within the first week, interviews within a month and he received a Microsoft offer (that he took) within 3 months.
The principle Jim implemented was simply describing his experience in terms of what he personally did, not what he did it on, using terms his target audience understood. He did not drive or load trucks, he did plan, develop “critical path analysis”, and coordinate multiple interdependent projects. When put in terms that automated systems expect and that IT recruiters understand, the quality of his experience became obvious, as did Jim’s desirability as an employee. It also helped him understand how to communicate his experience during interviews in terms understood by the people interviewing him.
Most important, it got him the job!
I mentioned that I joined a “support group for reluctant bloggers” in an earlier blog and this week I was able to get to there for the second time. While participating, I had an epiphany as another member talked about the stories of her clients and their success, I realized that I haven't written a single story about the participants from NFJS and what's happened to them. Once that penetrated my thick skull, the hard part is choosing. While I’ve been doing Notes from the Job Search for a little more than a year and a half, the principles I use evolved over 30 years, so the stories end up going back a long time.
Here’s a story about a young soldier reentering the civilian world
Somewhere along the line I learned the value of separating the activity a candidate does from the product they work on. About 3 years ago a young friend of mine sent me an email asking for help. This young man (I’ll call him “Jim”) went to college majoring in Computer Science on an ROTC (Reserve Officer Training Corp) scholarship, graduating in 2002. Well surprise, surprise, he was immediately activated and spent the next four years on active duty with the last two being in Iraq as a transportation officer. He mustered out in 2006, took a year off and had been looking for work for six months prior to reaching out to me. In those months, he had received nothing more than an automated response while submitting more than 100 resumes for various jobs in the IT industry. His goal company was Microsoft and he hadn’t even gotten an automated response from them.
I asked him to send me a copy of his resume and upon reading it understood the problem immediately. His resume was completely built around his experience in Iraq and he was applying for jobs as a project manager in IT.
We got on the phone together and I had him describe what he was responsible for. As he was doing this I kept asking him to avoid talking about trucks or transportation and spend more time focusing on his personal responsibilities. So when he said something like, “I had to get trucks filled with medical supplies from town A to town B on a weekly basis while making sure that we had supplies coming in from the States that would allow us to meet our schedules.” I helped him transform that into “developed schedules for multiple teams, coordinating multiple interdependent projects to deliver requirements on time and on budget.” Which is in fact a description of what he did, minus the references to Iraq and the Army and trucks. It is also describing his behavior in IT terms rather than Army terms.
One of the many great things Jim brought to this was an openness and ability to learn very quickly so the time necessary for him to completely re-write his resume was less than a week. When he submitted this new resume he started getting personal responses within the first week, interviews within a month and he received a Microsoft offer (that he took) within 3 months.
The principle Jim implemented was simply describing his experience in terms of what he personally did, not what he did it on, using terms his target audience understood. He did not drive or load trucks, he did plan, develop “critical path analysis”, and coordinate multiple interdependent projects. When put in terms that automated systems expect and that IT recruiters understand, the quality of his experience became obvious, as did Jim’s desirability as an employee. It also helped him understand how to communicate his experience during interviews in terms understood by the people interviewing him.
Most important, it got him the job!
Thursday, February 11, 2010
Strengths (again)
My last entry was on the book Now Discover Your Strengths so obviously it’s a key element in the Notes From the Job Search (NFJS) approach to job search. Another component of NFJS is our suite of weekly support groups for professionals looking for new jobs. What these groups provide is a continuing reality check for ideas and strategies in general. This includes the ideas expressed in Now Discover Your Strengths. (http://www.strengthstest.com/)
This book, as well as the others in the series, positions our strengths as tools we have choices regarding. Which isn’t the experience NFJS has of them, or at least isn’t a complete description of our experience with strengths. The Top Five Strengths, which is the report we get when we take the test, look far more like a description of how we approach the world. One friend of mine took the test last summer and found her number one strength is “woo”. This means she always finds ways to embrace the people around her and have them embrace her. This is who she is. One example of this is she has never been in a job interview without getting a job offer. She is certainly smart and hard working and other good things, but so are lots of other folks. Her consistent approach to relationships—all relationships—is to find ways for people to align with each other.
As I mentioned in my last entry, my greatest strength is “ideation” and my second greatest is “strategic.” I also wrote about how those have played out in my career. Turns out that is a darn good description of how I function. I always want to understand the ideas that drive how something works and I always approach it strategically first. When working on new development, this can be a huge advantage. It allows me to create clear coherent programs that do what they are supposed to do and that can be changed over time, etc, etc.
When working on maintenance (fixing/modifying something someone else created), I still approach it looking for the ideas behind the whole, and then how a particular piece fits. That doesn’t work—essentially it’s as big a problem as it was an asset for new development.
There is just very little that is as much fun for me as a discussion of how something works. It’s part of what drives me at NFJS. What is the suite of tools, the process that allows people to identify and achieve their dream job? That’s what I can build on. It’s a strength; it’s also not especially negotiable. I can acknowledge it and build on it, or I can frustrate myself and everyone around me by ignoring it and trying to be what someone else wants.
I can give lots of examples: A “learner” I know is always investigating new ideas and new areas of knowledge and new ways to do his current job. He is partially motivated by the enjoyment of solving problems, but mostly he is simply trying to learn something new.
Where taking the “strengths test” helps in the job search is by giving us words to describe what we do and why we are special. Then as we examine our work history, it helps us identify more easily where we were successful and how that success occurred. It gives us a coherent set of characteristics to build our “brand” around. What is it that makes you special? Looking back at your career through the filter of your strengths will help you identify those characteristics and help you identify the proof required to make you stand out in this market.
This book, as well as the others in the series, positions our strengths as tools we have choices regarding. Which isn’t the experience NFJS has of them, or at least isn’t a complete description of our experience with strengths. The Top Five Strengths, which is the report we get when we take the test, look far more like a description of how we approach the world. One friend of mine took the test last summer and found her number one strength is “woo”. This means she always finds ways to embrace the people around her and have them embrace her. This is who she is. One example of this is she has never been in a job interview without getting a job offer. She is certainly smart and hard working and other good things, but so are lots of other folks. Her consistent approach to relationships—all relationships—is to find ways for people to align with each other.
As I mentioned in my last entry, my greatest strength is “ideation” and my second greatest is “strategic.” I also wrote about how those have played out in my career. Turns out that is a darn good description of how I function. I always want to understand the ideas that drive how something works and I always approach it strategically first. When working on new development, this can be a huge advantage. It allows me to create clear coherent programs that do what they are supposed to do and that can be changed over time, etc, etc.
When working on maintenance (fixing/modifying something someone else created), I still approach it looking for the ideas behind the whole, and then how a particular piece fits. That doesn’t work—essentially it’s as big a problem as it was an asset for new development.
There is just very little that is as much fun for me as a discussion of how something works. It’s part of what drives me at NFJS. What is the suite of tools, the process that allows people to identify and achieve their dream job? That’s what I can build on. It’s a strength; it’s also not especially negotiable. I can acknowledge it and build on it, or I can frustrate myself and everyone around me by ignoring it and trying to be what someone else wants.
I can give lots of examples: A “learner” I know is always investigating new ideas and new areas of knowledge and new ways to do his current job. He is partially motivated by the enjoyment of solving problems, but mostly he is simply trying to learn something new.
Where taking the “strengths test” helps in the job search is by giving us words to describe what we do and why we are special. Then as we examine our work history, it helps us identify more easily where we were successful and how that success occurred. It gives us a coherent set of characteristics to build our “brand” around. What is it that makes you special? Looking back at your career through the filter of your strengths will help you identify those characteristics and help you identify the proof required to make you stand out in this market.
Wednesday, January 27, 2010
Now Discover your Strengths
If you read this regularly, you will have noticed that I try to focus on the positive and help people build on their strengths. A piece of this comes from Now Discover your Strengths, and somehow I've missed writing the book up. What this book does is validate things most of us know intuitively, but may be afraid to commit to.
In my case, math and science are noticeably easier for me than reading and writing, or at least it started out that way. :) Unfortunately, I was 32 before I allowed myself to use that information in relationship to my career. I also have a need to understand how things work and while that’s useful in lots of areas, I didn’t nurture that as part of my career until about the same time. This combination led to changing careers and embracing computers and systems development... More accurately, my previous careers hadn’t been all that successful, so when I chose a new path, I actually included this information in the equation. The result was a career in computers and development that lasted most of 30 years and that was very successful.
The point is not about me, but what happens when building a career based on strengths, which leads back to Now Discover your Strengths. One element in their process is an online test that can provide a view of your natural strengths. You can go straight to the test via http://www.strengthstest.com , but context helps, so maybe you borrow the book and take the test. What you will get back from the test will be a list of the five areas of how you approach life and problem solving that are your strongest tools. For example my first one in “Ideation”, in this case it means I need to understand stuff, there’s more to it of course and you can look that up if you care, but the real point is that when I took the test 20 odd years after I switched into computers systems, I found something that actually had language around why my choice worked. Very powerful stuff.
When you take the test, it will not tell you what your career should be, “ideation” doesn’t tell me I should be a developer, but when I look at an opportunity, it allows me to evaluate my chances for success much more clearly and with significantly better tools. It will also help you understand the styles of work that will facilitate your success.
In Now Discover your Strengths Marcus Buckingham defines a strength as “consistent near perfect performance in an activity.” The level of performance must be consistent, which means you’ve done it before and can expect this when you do it again. One of Buckingham’s examples is Tiger Woods. Woods drives are amazing and consistent and he can (and does) rely on them. Realistically, there isn’t anyone who drives like Tiger, but driving is a strength for a lot of golfers and many of them build their games around their drives. In other words, “near perfect” is relative. What the test will give you isn’t a description of your drives, just a description of how you can optimize your approach to many things.
Using my own example again, “ideation” is my first strength, and “strategic” is my second. As a developer, I found I did a great job on new development and honestly struggled with maintenance work. My strengths translate to someone who is almost exclusively a top down thinker, and if I don’t understand context I struggle until I get the context. The strengths of a good new system developer includes an ability to understand the whole and to get the details right inside that whole. A maintenance developer works best if they don’t need the whole, just the three or four details required to fit the new code into a program/system etc. Prior to taking the test, I understood that my performance was distinctly different in maintenance mode vs development mode and I just could not figure out why. Taking the test made the reasons very clear and really drives me to focusing on one vs the other. What the test did for me was give me vocabulary to understand why one function was relatively easy and very satisfying while what seems to be a very similar track was just a major challenge and nothing but frustrating.
Equally important, the test results help me understand what would be a successful future choice. Moving from IT to career coaching, it’s clear to me that I need to base my coaching on my strengths… Actually it’s clear that I will base it on my strengths because I don’t know how to do it any other way. If that way is incompatible with career coaching then I need to come up with a plan B. Your particulars are different than mine, but you do work from your strengths or you struggle, just like me. Knowing what these are allows you to avoid a lot of frustration.
Start by reading the book and taking the test. The words it will come back with might not be all that familiar so read the descriptions. Think about how those apply to your work life. The descriptions will be describing things you did when you were successful, how can you build on these? How can you use more of these in your life? Your work?
In my case, math and science are noticeably easier for me than reading and writing, or at least it started out that way. :) Unfortunately, I was 32 before I allowed myself to use that information in relationship to my career. I also have a need to understand how things work and while that’s useful in lots of areas, I didn’t nurture that as part of my career until about the same time. This combination led to changing careers and embracing computers and systems development... More accurately, my previous careers hadn’t been all that successful, so when I chose a new path, I actually included this information in the equation. The result was a career in computers and development that lasted most of 30 years and that was very successful.
The point is not about me, but what happens when building a career based on strengths, which leads back to Now Discover your Strengths. One element in their process is an online test that can provide a view of your natural strengths. You can go straight to the test via http://www.strengthstest.com , but context helps, so maybe you borrow the book and take the test. What you will get back from the test will be a list of the five areas of how you approach life and problem solving that are your strongest tools. For example my first one in “Ideation”, in this case it means I need to understand stuff, there’s more to it of course and you can look that up if you care, but the real point is that when I took the test 20 odd years after I switched into computers systems, I found something that actually had language around why my choice worked. Very powerful stuff.
When you take the test, it will not tell you what your career should be, “ideation” doesn’t tell me I should be a developer, but when I look at an opportunity, it allows me to evaluate my chances for success much more clearly and with significantly better tools. It will also help you understand the styles of work that will facilitate your success.
In Now Discover your Strengths Marcus Buckingham defines a strength as “consistent near perfect performance in an activity.” The level of performance must be consistent, which means you’ve done it before and can expect this when you do it again. One of Buckingham’s examples is Tiger Woods. Woods drives are amazing and consistent and he can (and does) rely on them. Realistically, there isn’t anyone who drives like Tiger, but driving is a strength for a lot of golfers and many of them build their games around their drives. In other words, “near perfect” is relative. What the test will give you isn’t a description of your drives, just a description of how you can optimize your approach to many things.
Using my own example again, “ideation” is my first strength, and “strategic” is my second. As a developer, I found I did a great job on new development and honestly struggled with maintenance work. My strengths translate to someone who is almost exclusively a top down thinker, and if I don’t understand context I struggle until I get the context. The strengths of a good new system developer includes an ability to understand the whole and to get the details right inside that whole. A maintenance developer works best if they don’t need the whole, just the three or four details required to fit the new code into a program/system etc. Prior to taking the test, I understood that my performance was distinctly different in maintenance mode vs development mode and I just could not figure out why. Taking the test made the reasons very clear and really drives me to focusing on one vs the other. What the test did for me was give me vocabulary to understand why one function was relatively easy and very satisfying while what seems to be a very similar track was just a major challenge and nothing but frustrating.
Equally important, the test results help me understand what would be a successful future choice. Moving from IT to career coaching, it’s clear to me that I need to base my coaching on my strengths… Actually it’s clear that I will base it on my strengths because I don’t know how to do it any other way. If that way is incompatible with career coaching then I need to come up with a plan B. Your particulars are different than mine, but you do work from your strengths or you struggle, just like me. Knowing what these are allows you to avoid a lot of frustration.
Start by reading the book and taking the test. The words it will come back with might not be all that familiar so read the descriptions. Think about how those apply to your work life. The descriptions will be describing things you did when you were successful, how can you build on these? How can you use more of these in your life? Your work?
Subscribe to:
Posts (Atom)