What kind of business are you in?

The question “what kind of business are you in?” seems simple enough and is a standard question that businesses ask themselves to stay relevant and not lose sight of their market. However as we know, the answers to simple open questions can end up being complicated. Looking at an example of a wrong answer for this question: railroad company thinks of themselves as a company in the railroad business, not realizing they are in the transportation business. An extreme example of bad decision making was Kodak not realizing they were in the memory / emotion capture business and instead they focused on providing film and print material because it had made them money for over 100 years. By the time they realized what business they were in, it was too late.

You might be wondering what direction I am taking this in. I want you to consider how you would answer this question in relation to your current career as a business analyst.

As a business analysts, I consider we are there to help generate improvement of profit and or reduction of costs for the companies we work at. However most employers (who are actually our customers) don’t see that in our role but instead look upon us to be specific in what we provide them in terms of knowledge and experience. Examples would be:

  • Payment handling
  • Healthcare data processing
  • General data analytics
  • Anti money laundering
  • Utilities
  • Mobile applications development
  • etc..

This narrow role definition by our customers puts us back into the mental mode of thinking that we are in the railroad business and not in transportation. Basically our customers are not going to tell us that they plan to make us obsolete with a new solution to their business needs or that they are losing market share in their industry (leading to job losses). We have to think beyond what we immediately provide to the customer and consider at least two things in our careers.

  1. Industry trends
  2. Tools we use

Industry Trends:

  • Is the Industry that we are working in shrinking or growing in our geographic location of work? Example – think of factories that get closed or corporate mergers either of which would reduce people needed in the industry.
    • To overcome, you would either need to gain experience / knowledge in a new industry or move location to where the work is (if that is an option).
  • Are there current or future disruptions to the way the work is being done in our industry that we need to be aware of? Example – looking at the railroad, the rails, trains and railcars are just a tool used in transportation. Certainly they help the railway business make money but as the railway companies found out in America after the interstate roads were built, new options for transportation by road upset the apple cart. Money invested in trains and railcars was lost because these tools did not work on the road. Basically being only in the railroad business was going to cause a loss of market share, decline in profits and decline in employment opportunities.
    • To overcome, you need to stay aware of advancements in technology / process that could impact your industry and seek knowledge / experience with the new and even considering changing industry if the new will make your industry obsolete and or reduce its market share causing a reduction in employment.

Tools We Use

  • Are the tools required to do your job changing? Example – with the move to more Agile IT work we are expected to have used formal tools for managing user stories, backlogs etc.. Reporting is another area where tools are continually evolving.
    • To overcome, you need to monitor the tools specified in job postings prior to your next job, have a budget set aside for training, get the training and if possible work out how to get experience with the tool/s.

In summary, don’t let your current success with customers blind you to the market. Stay current with what industries are doing (growing or shrinking) and what tools you need to do your job. That way you will continue to help companies improve their profits and reduce their expenses. Plan to budget for time and money to be spent to keep yourself marketable to customers. Be prepared to ditch an industry if the future looks grim. Don’t focus on pure profit, invest in yourself to stay in line with the market otherwise you may become the next Kodak.

3 Generic Certifications that help you get IT BA interviews!

There is no getting past it that the IT BA market has become saturated. It is no longer enough to be someone who has worked as a BA for years as the market is full of that experience. So the question becomes how do you make it to the interview pile instead of the reject pile?

Today I want to focus on 3 generic IT certifications that are not tied to an industry or solution that can help move your resume into the pile to be interviewed.

#3 Certified Business Analyst Professional or equivalent: This one has been around for quite a few years now. If you have been doing BA work as long as I have, it really does not bring much value in terms of knowledge. If you have less than 10 years of experience, this one is good to add onto your resume. However its value has somewhat diminished with Agile development.

Pros:

  • Shows that you have at least been educated as a BA.
  • Great for when you have limited real world experience.

Cons:

  • Has not become a job requirement like A+ certification (for pc repair).
  • BA roles differ from company to company so some companies add more or less weight to the certification.
  • Does not carry as much weight in the Agile development world.

#2 Certified Scrum Master: You can look on this certification as selling yourself to the client as two for the price of one. For the longest time, clients have liked to put their BA’s in the role of backup Project Manager, being a Scrum Master is the new flavor that Agile development has brought to us.

Pros:

  • Shows that you understand Agile development.
  • Makes you more appealing to the client as you can now fill two roles.
  • Could increase your salary as Scrum Masters can make more money than ordinary BAs.

Cons:

  • You may end up doing more Scrum Master work than BA work.
  • Could make your life busy as you juggle two roles.
  • You may not like being a Scrum Master.
  • Only applicable to Agile development. For non Agile, you could look to taking Project Management certifications instead.

#1 Certified Product Owner: You can look on this certification as being the natural career progression of the BA involved with Agile development. Any BA that wants to stay more in the BA world should look to get this certification sooner or later. It shows a client that you understand Agile and that you understand the BA role through the Product Owner viewpoint. With the advent of the Product Owner role, certain tasks normally performed by the BA have moved to the Product Owner and this is why it is not a large step for a BA to move into this role.

Pros:

  • Shows that you understand Agile development.
  • Makes you more appealing to the client as it shows you should be able to represent what the business wants.
  • Could increase your salary as Product Owners are more involved with the money making side of the business.

Cons:

  • More applicable to Agile development but does carry over into other types of development methods.
  • May not pay as well

In summary, if you are wondering how to get more interviews as an Information Technology BA, getting at least one of these generic certifications can help you move forward. What school or method you choose to get these certifications is not as important as actually having a certification that you can add to your resume.

From a long term perspective with these certifications, you will need to decide if you want to go more on the high paying Scrum Master side (which is more like the old Project Management) or look to move into Product Ownership which is the natural next step for Business Analysts.

Business Analysts who want to become Product Owners should know these two things.

As the market changes for business analysts and more consider the move into the product owner world, the question becomes, what is the difference between the role? Product owners can sometimes just be business analysts with a new job title and in other cases they are really product owners with full authority to make decisions.

Agile development has driven the growth of the product owner role. No longer do business partners have to wait months for development to implement new features / functions, instead they can be delivered in weeks. Since business partners usually have to run the business they don’t have time to spend on agile work so they delegate business representation to the product owner.

Now, let us consider two of the key differences in the product owner role vs business analyst:

  1. Industry knowledge – with the traditional BA role, there is usually time to get up to speed in the industry being worked in (Retail, Utility, Finance, Health, Transportation etc..) as the requirements are gathered. This means that having industry knowledge is not a deal breaker to being hired. In the product owner world, you had better know the industry as decisions have to be made quickly to keep the development moving. For example glass devices are not allowed in food processing plants, so developing a product solution that uses cell phone applications would be a bad decision for any industry that goes inside food processing plants because of the glass touch screen.
  2. Metrics / research – product owners need to make decisions on the priority of features / functions to be developed. As a product owner, you need to know how to justify the decision based on real world facts. This requires an understanding of the research options / data available and metrics desired in new development. Think Google Analytics, combined with any restrictions on data that can be collected / solutions that can be delivered. Business analysts on the other hand normally get this information and direction from their business partners.

How to get the skills needed to be a product owner?

  • Industry knowledge can be gained by either working as a business analyst in the industry for a period of time or getting a job on the business side. Both options will be good to getting the necessary experience.
  • Knowing research options / metrics to justify decisions is not always needed as not all companies expect this of their product owners. However for those product owners that do need to know the information, joining external groups in the industry, reading trade publications, staying on top of trends, working on the business side etc.. can all help to build up the knowledge required to justify decisions.

Health Insurance & Tax impacting the American Consultant take home pay

This post is about unexpected costs that the American Government has brought to bear that are reducing the income of Consultant BAs in America.

If you work in America or thought of coming to work in America, certain changes over the past few years have really reduced the take home pay of consultants who are not self employed – known as W2 employees because of the end of year tax form received by employees.

For this post, I have assumed that the tax rate for the consultants income will be 30%.

To be self employed (known as 1099 – tax form produced at end of year for employees not directly employed), the client that you work for has to be willing to accept a Corp to Corp relationship and some clients will not accept that. If you are lucky you might be able to get a preferred vendor to hire you on self employed basis. At the end of the day, being able to work either W2 (employee) or 1099 (Self Employed) opens up the number of job opportunities that you can pursue.

How did we get to the point of losing money?

First off, Obamacare (Affordable Care Act) did not reduce the cost of health insurance for the majority. Instead, Obamacare has more than doubled the cost of health insurance since it was introduced – a $500 family policy in 2014 would cost around $1300 today based on what I have seen.

Obamacare also removed the ability to deduct private health insurance costs from your taxable income. Private health insurance was important for consultants as they change employers often. Buying into an employee policy did not always make sense as the relationship with the employer may be only for 3 months (duration of the contract). This private health insurance policy cost could previously be deducted against your taxes whether you were W2 or 1099. What Obamacare effectively did, was to get rid of that deduction option for W2 employees. This is like a 30% surcharge on health insurance because you now pay for the private health insurance policy with after tax income. 1099 employees can still deduct the cost of the health insurance against their income since the insurance can be deducted as a business expense. However, even if you are 1099, that does not overcome the fact that health insurance costs have more than doubled.

The second reason W2 consultants are losing more money is because of the tax law change of 2018. Previously if you had travel expenses that exceeded 2% of your W2 income, you could deduct that amount from your taxable income. This deduction was removed starting tax year 2018. This means that if you do any amount of heavy travel for work that your company does not pay you for, those travel expenses are now 30% more expensive. I spoke with a recruitment agency the other day who said that more and more consultants are declining W2 job opportunities that would require them to work out of their home town because of the tax law change.

If you are W2 and you need to travel for work overnight or longer, you could ask for “Per Diem”. This is a IRS approved amount that is not taxed and the amount is based on the location that you are working in. One way to negotiate this is to get an agreed rate and then ask for some of the income to be converted to Per Diem money. However there are flaws with this approach:

  • Per Diem expires after a period of time. Basically after your have been in a location for 12 months or you expect to be at a location longer than 12 months, the IRS no longer considers you eligible for tax free Per Diem.
  • You have to have a tax home more than 50 miles away from where you work.
  • The client or employer that you are going to work with may not want the hassle of doing Per Diem reporting.

In summary, the American system has started to close the door on W2 employees that are Business Analyst Consultants by increasing the cost to do business. Consultants will need to:

  • Pursue more Corp to Corp jobs (basically be self employed).
  • Work at reduced rates for companies that will cover their expenses.
  • Work only on local jobs that do not have expenses associated with them.

AI will end the need for IT Requirement Business Analysts

Will say up front that this is purely an opinion piece as I don’t plan to provide the textual references to back up the statements. Purpose is just to think about the evolution of technology that had led us to this point and the impact to the IT Requirements Business Analyst.

Historical speaking if we start at the Industrial revolution, machines were used to speed up production. Back then, the equivalent of a software programmer was a mechanical engineer who designed the levers; shafts and cogs etc.. to produce the desired result. More often than not, workers were required to keep the machines fed with raw material and to remove the finished product. You could think of the raw material as being the equivalent of data coming into a modern day data processing software and the end product being the finished use of the data such as reports / dashboards or account updates.

When the electronic computer moved into the office world in the late 40’s we started to see where the processing of data by human clerks was being replaced by the computer. The mission of the computer back in those days was to reduce the number of humans involved in processing data. At this point, businesses are not looking for the computer to give them guidance but just to allow data to be processed quicker and more cheaply. Designers of software could focus on the tasks already done by the human and create software and peripherals such as printers that replaced those tasks. This would be done by job shadowing to understand the process.

Moving into the fifties and sixties, computers became available that could be programmed with complex algorithms to allow data to be processed in a way that predictions could be made from the data. At this point, the designers are no longer thinking about replacing workers but instead leveraging the processing power of the computer to produce decisions related to business. While some of this you could argue was done in WW2 to break codes, those machines were specifically built for the task. What the more modern computers allowed was for programming languages to change the decision task to meet the current need. However the one handicap was the speed of the computer in those days. Decisions generated by the computers were not done in real time and the programming involved was complicated.

With the advent of the more powerful and useful computers that come out of the late sixties, we start to see where computers become part of real-time processing. Computing processing power and storage keeps increasing every year allowing for businesses to look at new way of saving costs / increasing investments by letting the computer streamline their processes beyond replacing people to even including the ability to expand their business. This is achieved by the development of new interfaces beyond the punch card of old. Now terminals are available that allow for direct access to the computer processor allowing for live updates of data – think airline ticket handling. In this period the designer was seeing how new tools available via technology could enhance rather than replace the current process. However even with all these advances, the use of the computer was still dependent on a designer working out the needs of the business and getting it coded. Software solutions were ridged and limited to the design parameters provided.

Even when we go into the turn of the century, the faster computers with more data handling are still moving along with limited software design that involves fixed parameters and limited interfaces for data collection.

Where we seem to make the evolutionary leap towards AI is when the processing power and data handling ability of computers crosses a threshold where it can consume non-human prepped data that is beyond just text. Previously, data processing power limited what a computer could do in real time. Now a computer can process not just plain textual data but also images, sound etc. and determine decisions based on this. It is like we have removed a prisoner from a small cell where the only thing they could see was text and their hearing / touch / sensing was deliberately disabled. Now we are in a scenario where computers can be educated to interface with humans on a natural level. All the designer needs to do is define the data streams (based on the context – driving a car for example) and the measures of success. AI can then learn to process the data.

Now before I talk about the impact of AI on the BA role, I want to break the role into two:

Role 1 is the BA that looks at business processes.

Role 2 is the BA that looks at interfacing IT with business processes.

Business process BAs (Role 1) are already heavily being replaced by the Product Owner role so while this BA will eventually not exist, the role has a chance of living on for a period of time with the advent of AI as a Product Owner. Eventually however even Product Owners will be replaced by more sophisticated AI solutions. Big risk though, is that businesses become clones of each other. An AI analyzing the marketplace may come up with the same opportunities as another business AI thus killing the market opportunity as both deliver the same solution at the same time making neither have an advantage over the other. While this happens with humans today, the occurrence is less as humans cannot deliver ideas at the 24x7x365 speed that AI can. Stock market meltdowns have already been shown to happen when multiple different stock monitoring software trigger sell decisions because a trigger event occurs. This will be the same issue when AI takes over the business Product Ownership.

Role 2 BAs that focus on requirements for IT design are most likely to be impacted in the very near term by the advent of AI. This role has already seen a significant amount of work being moved to UI designers and Data Warehousing Specialists (both of whom are at risk of being replaced by AI as well) that the amount of work left is limited. With the advent of AI, its is conceivably possible for the BA person to be replaced by an AI solution that interfaces directly with the business to produce either IT solutions or output that can be used to create IT solutions. For years this has been a dream of many companies. Easier to use software being the traditional way to limit IT expenses – think about how many business users use Excel for example without ever talking to a BA. AI will make it a reality for everybody to ditch the IT requirements BA. Instead of having to learn an interface specific to a piece of software, the AI will instead provide a sophisticated human interface that replicates what the BA does today. For the business it will be as if they are working with a BA but without the human cost. Certainly it will take time and money to develop this BA replacement AI but once it is developed it can easily be distributed and shared.

In summary, AI will be a great move forward for business but will negatively impact the Business Analyst market as we know it today. Business Analysts who focus on only IT requirements would be well advised to move into Product Owner roles or be involved with the AI development that is happening so that they can be an expert in the field.

Testers working for nothing – why you should not go into testing as a career

Often Business Analysts will see in their job description the act of testing. True heavy testing requires special skills that do not tie in well with good Business Analysts skills.

Business Analysts often need to get out and communicate with a variety of people and dig beneath the surface of conversations to find the true requirements / processes.

Testing however relies on the information presented from the Business Analyst along with other documents and  industry standards to validate the work done. Testers effectively thrive in an atmosphere where communicating with a variety of people is not required.

While small amounts of testing such as a minor enhancement can be covered by a BA, care must be taken if the BA role requires more than that as it will weaken your BA skills over time.

Maybe the above is not enough to dissuade you from heading down a testing career path from your BA role but two trends should discourage you from heading into testing as a career:

1 – Outsourcing

Recently I saw a corporation completely outsource their Testing Department. Part of the reason behind this is the theory that the size of a testing department varies according to the work being done. A vendor was considered a better solution to handling the waves of work as opposed to having staff on hand.

2 – Testing for nothing in hope of potential rewards

This is the most worrying concern for anybody involved in testing. It looks like a Silicon Valley startup has ditched paying testers a wage. Testers have to compete to win cash by being the first to identifying bugs / issues that nobody else has identified. If they are not the first then they get nothing for their efforts. The prizes are also so small that only someone living in a country overseas could justify the risk of time and effort for little to no reward.

PM versus BA – the dead discussion and why being a PM may be better than being a BA

It can be interesting to read articles on the Ideal Way that things should happen. These articles are somewhat like the ones about why all people should be debt free and happy. If you are not debt free and happy, then you personally are doing something wrong.

Focus of this website is in the reality of the workplace which is usually far from Ideal. Politics, Oligarchies, Budgets etc. can all get in the way of achieving the Ideal or “World Peace”.

If you want to read up on the debate around the fact that there is no difference between PMs and BAs but it is all about what you bring to the table (“Ideal Approach”) then check out this link – PM vs BA.

Honestly however, the whole conversation is dead one which is what the author of the article states. The author basically questions why PM versus BA is even a discussion point to which I have to agree (having had a foot in both camps (PM / BA) I see no reason why the right BA cannot do PM work and vice versa). Business Analyst term has become so watered down anyway it means many different things to people in the industry. There is no one definition (outside of the textbooks) for what a BA is. Effectively as the author of the article states, project success is based on collaboration and not on title. However in the real world, project teams (especially in larger companies) are formed based on titles / roles / budgets / deliverable dates and that is where the Ideal is left behind. The company that you are at will dictate your role to you based on their process / procedures / politics etc.. Some companies will be Ideal while others will miss the mark.

From a current trend perspective over the past 20 years, I have seen the companies go from using BAs to manage small projects as they gather requirements to the other scenario of having PMs gather requirements as they manage projects. Talk about territory wars. As the trend continues, the BA starting out might be better off to go into Project Management first since they will get better experience than trying to come up through the BA ranks where they run the risk of being no better off in experience than a secretary.

From a historical perspective (ignoring the above about collaboration approach), let us talk about the facts around the PM being different from a BA.

1 – Project Managers are brought on before Business Analyst so why bother with the BA.

– Pure Business Analysts are seen as an unnecessary expense in a lot of companies – last hire in your small companies. More and more the Project Manager is being looked at to deliver the Business Case / Requirements as part of their role to avoid the expense of having a Business Analyst. Personally I have seen two recent larger clients push to have the PM do most of the work since the rational is that they need to have a PM anyway so they might as well leverage them to do everything with the theory that the project is saving money. In these companies, the BA is getting downgraded to little more than a secretary required to document whatever the PM states and store it in the appropriate software.

2 – Project Managers can always do BA tasks or vice versa

– A project that is on a tight deadline cannot afford to have the resource distracted from requirements gathering with PM paperwork / issues. Try to gather requirements while putting together multiple project status / dashboards (and they all have the same deliverable date) and you will see what I mean. Sure this is not a problem when deadlines are not important.

– Not all BAs can do financial reporting / resource management as they have not been trained nor do they have the experience. After you have sat through a few cost center allocation discussions with Finance, you will enjoy getting back to requirements gathering

– Paperwork / Software used by PMs may be unfamiliar to BAs. MS Project and the latest tools all require some form of training / experience. Dashboards have to be designed / populated for projects which takes time away from requirements. It is the same for PMs trying to capture requirements as they may not be familiar with the software where the requirements are stored.

– Some PMs have no clue about proper requirement writing (ambiguity), business case development (what does the business really want and how to justify it) and it shows when the project moves through the phases. It is kind of like expecting a BA to be able to design databases. Some have it and some don’t.

3 – PM is the natural career progression for a BA

– NO it is not! Pure Project Management is different to Business Analysis. Even the IIBA acknowledges this when they ask you to describe the role you had in the projects you worked on. If you answer too many questions from a PM perspective they will not acknowledge that experience as being BA relevant.

 

Hopefully I got the point across that the BA versus PM debate is dead. To argue it anymore would be to ignore the trend in the industry which is downgrading / killing the Business Analyst job title making this whole discussion pointless.

As Business Analysts, we should be more concerned with making sure the role we are in ties into our skills. Remember, the BA title by itself is pretty much worthless these days as it means so many different things to different companies. Your focus should be on getting the skills / experience to be in the role you desire and not on the job title.

For a list of Business Analyst job titles, see links below:

Job Titles Job Titles

 

8 pitfalls to avoid with your job application.

1- Online Profile Check

An interesting development these days in looking for jobs compared to 15 years ago is that your online profile can haunt you years later. Remember that every time you post information about your current or previous positions it is available to others as well. When applying for jobs, be sure to make sure that any online profile you find when searching on yourself does not reveal embarrassing or contradictory information that weakens your job application.

2 – Certain level of education required

Education is not something you can fake. Employers have been burnt by this so they check applicants often and the process for validating education is becoming easier. In some cases, companies will not hire you until the education has been validated. The old trick of picking an education establishment in the middle of nowhere does not always work anymore and at the very least they will want to know why you got your education from this far off place.

Some warnings from the BBC about resume checks.

http://www.bbc.com/news/business-31594181

How to handle Education:

Compromise here is to at least be attending a course that leads to the qualification required. Employer will see that you are in the appropriate education and may let you get to the next stage of the job application. As to when you actually complete the education and how long you have been studying it, that is up to you.

3- Years of Experience more than currently experienced

If you are lying just to get a job, you don’t have the experience and are not a quick learner you can be sure it will be worked out quickly that you are not a fit. Even as a quick learner you may not be given the time to learn the job before they are onto you for lack of experience.

I read a resume once where the person had a master’s degree, was 27 years old and had 9 years of relevant work experience. Where you might ask is the problem? This person had 7 years of full time schooling with 9 years of work experience coming to a total of 16 years and they did not start college at 11 but at 18. It gets murky here. Some people will consider a working month; week or even a day in a calendar year as 1 year worth of experience and put such on their resume.

Understand that no two persons will have the same experience for the same time period. Someone who consults will have a larger variety of experience compared to someone who works in the same job / company for the same period of time. However someone who works in the same job / company for years may have more depth of experience since they have been totally focused on that role.

A lot of time, employers put years of experience required to exclude the candidates with no experience at all or based on their judgment of what experience brings to the role. As stated above, someone with one year of experience may have the equivalent of another person’s 10 years just depending on the jobs that they did. In the 80’s the rule of thumb for consulting was 2.5 years experience before you could become a consultant. The number of years has been increased significantly for job applicants due to lies that people have been putting around experience. An average of 5 years seems more like the norm these days.

How you can get caught with lack of experience:

– You go into a role where other colleagues have the experience so your lack of experience is obvious. I worked at a site where on the first day of the job I was asked to perform a simple task under the eye of the manager who hired me. Failure to have successfully performed that task would have led to a quick exit.

– You are not a quick learner. If you do not have the experience and you can’t pick it up quickly, you will end up being found out.

– During the interview, you could be asked to describe the projects that are relevant to the experience and how long you spent on each. Mistakes in duration will quickly add up to not matching your resume experience. Explaining that a project lasted for months or over a year could also trip you up if the normal experience for the role is short projects.

– When hired, you ask too many basic experience questions making it obvious you do not know your stuff.

– Employer has an acquaintance from your previous employer who states in their opinion what your work role was at your previous employer that does not tie with what you stated you did.

How to handle years of experience:

Nobody asks if you did 2000 hours in a particular role over a calendar year, they just want to know that you held a job in that role for the particular year combined with whatever else you did for the remainder of the year was related. Putting it plainly you have to look at the months/year when you did not have the role and translate the experience of the role you were in into the position you are applying for. Unless the employer has a direct acquaintance at your previous employer it is unlikely that the new employer will get the exact project by project details of what you did.

4- Job skills required are specific

I have been to interviews where specific skills were requested but that was because the employer had gap in skills that needed to be filled. Other times I have gone to employers where the skills were already present so the employer was looking for someone that would fit in with the existing team.

How you can get caught with lack of specific skills:

– Testing of your skills during the interview process.

– Monitoring of you as you put your supposed skills into action.

– Ask you to describe previous projects where the skills were used.

How to handle lack of specific skills:

If you don’t have experience in the specific skill requested you need to at least get an understanding of it. Understanding can either be obtained thru training or via reading a book on the subject. Any training you take can be easily added to your resume under training. If you only read a book, then you will need to tie the specific skills back to projects you have worked on so that the skills will at least appear on your resume. Sometimes as you learn the skill you may find that you were already using it in your job anyway, you just called it something else. In both cases (training or book reading), where appropriate, any work that you did that is relevant to the skill, you should mention.

5- Job title is not one you have held

Maybe you are trying to change career from being a Project Manager to a Business Analyst and as a Project Manager you performed Business Analyst tasks. So all your employee job titles state Project Manager. When your resume lands on the employers desk they won’t bother looking at it if you state you were a Project Manager so you change it to Business Analyst.

How you can get caught with not having job title:
– Somebody provides a reference stating that you were in a different role. Make sure you references understand the role that you are presenting yourself for.
– Old profiles of you exist on the Internet saying you were something else.

How to handle lack of job title:
Change your thinking to the “title for my job”. Ditch the words “job title” and instead say who employed you and focus on the title for the role you performed. Avoid using the words “Job Title”. If they ask what your job title was at the interview, just state the title for the job you performed as that was really your job. If part of the time you were in one job role and the rest of the time in another for the same employer, don’t break out the experience by role but instead mention you were in both roles and state the years at the employer.

6 -Gap in job years or currently unemployed

How you can get caught with  job gaps:
– You are unable to provide references for a period of time.
– The experience dates don’t add up on your resume.

How to handle gaps and unemployment:
Even if you do not have a paying job, you should be providing your relevant expertise to others. Point here is to have a 3rd party that will vouch that you worked for them (paid or unpaid) in some capacity. The minute you are between jobs or are trying to get back into the workforce, look for those opportunities which can build references. Review your past period of gaps and see if anything you did over that time is relevant to the work you are applying for. Document it all and be ready to provide references that will back you up.

7 -Previous job at much higher level than one being applied for

How you can get caught with level of role in previous job:
– You use terms that may not be applicable to the role being applied – example managed financial budgets when applying to a developer job that is all about pure coding.
– You talk about the people you managed when the role has no people to manage.
– Previous experience is overly impressive – such as worked at the United Nations when job is for a small company.
– You have an internet profile that shows what you were before.

How to handle higher level role in previous job:
It is ironic that on the one hand we are told to play up our successes but the on the other hand we do not get hired because our success scares the employer. Going for a lesser job requires making the employer feel that you are not going to get bored and quit. You need to remove any terms / experience that is not relevant to the job you are applying for. You will have to set the title of your previous job to match the role being applied for. Downplay large companies you have worked for by focusing on describing the small team or department you worked in. Avoid mentioning words that would associate you with large global organizations if at all possible by looking for other ways to describe projects / experience.

8 -Samples of work not your own or incorrect

So your future employer asks you for samples of relevant work and you grab whatever you feel like sharing. This can be great aid but it can also bite you in the butt.

How you can get caught with an incorrect or someone’s document:
– Employer has an acquaintance at your previous employer who can validate the original author of the document.
– You are unable to talk intelligently about the document.
– It contains glaring errors that make you look unsuitable to hire.
– Document sample is way larger than anything the employer would expect you to deliver making them suspicious that others helped you with it.

How to handle document samples:
Best to use your own work. Keep your document samples small and make sure they do not provide confidential information. If needed, mock up some samples based on your experience. A page here or there and never a whole document. Be prepared to talk to every page shared as if you were doing a presentation. Verify that what is present in the document is correct as it represents your best work.

In summary I hope you find this information useful and it helps you get your next gig.

Good Luck

14 tips for surviving Senior Level meetings.

At some point in your Business Analyst career you may be asked to meet with Board level staff. This should not frighten you if you follow some logical tips.

1 – Don’t go it alone.
Find someone to help you setup, run and share results/minutes of meeting.

2 – Make sure someone in the room can vouch for you.
Someone in the room of a senior enough level has to be able to support you when things get tough. If you don’t know anyone, reach out to at least one individual prior to the meeting to introduce yourself and get them on your side. Failure to do this could leave you in front of a firing squad.

3 – Know who the most senior people are in the room and respect their authority.
If you don’t know who a person is that has the power to end your job, better to find out before you challenge their meeting behavior or statements.

4 – Define the rules and objective of the meeting.
Always good to define the rules and objectives. Please note however, the higher the level of meeting the less the participants are willing to listen to the rules, in those cases you have to go with the flow.

5 – Dress to match the meeting participants.
If the meeting is a suit and tie affair, wear them.

6 – When things go astray.
Ask the participants if they are open to taking a break.

7 – Be Bold but not Reckless.
Be careful of how you control the meeting. Being respectful to participants is key and don’t get sucked into arguing with them. Note and accept their objections then move on.

8 – Meet one on one post meeting to resolve issues.
Since you avoided the argument, afterwards is when you meet with the individual or subordinate and work to resolve their issues.

9 – For long meetings, meetings at lunch or dinner make sure the food and drinks match the level of staff.
Quite often you can reach out to the personal admin of the highest of the participants and work with them to schedule the right food and drinks.

10 – Be flexible.
Senior level staff availability changes at the last minute. You may find your meeting getting shrunk or bumped. Often these people are used to meeting in the evenings post the regular work day.

11 – Learn the individual personalities before hand.
Knowing what to expect from the individuals involved in the meeting keeps the surprises to a minimum.

12 – Know the terminology / acronyms
Either learn the stuff before the meeting or have someone with you who can whisper / Instant Message you what is being said.

13 – Use IM to get live meeting feedback
If you or your companion is not presenting, have your senior friend in the room (point 2) let you know if you are going off track by Instant Messaging you feedback to the computer that is not presenting – don’t want the IM to appear on screen.

14 – Prepare psychologically.
Follow whatever routine you use to relax and stay relaxed during the meeting.
http://www.bbc.com/capital/story/20140904-jitters-act-like-a-starfish

Are you just a glorified factory worker or do you focus on enhancing Skills/Experience?

Times have changed and along with it the expectation of the Business Analyst role.

There was a time when Business Analysts were hard to find and the skills of the role were high. Now however, a lot of roles are getting labeled as Business Analysts which is causing confusion since the people in these roles feel they are Business Analysts. In other cases, skilled Business Analysts are finding their roles not what they expected.

I make an analogy to the “Factory Worker” to state that if your skills are not unique then what value do you personally have to differentiate yourself from the competition for work? Factory workers are tied to the factory they work at. Certainly some of them may be skilled in operations of machines that can transfer to other factories but overall, the focus of the role is:
– turning up on time to work
– being efficient at the task.
– being able to complete a shift.
– skills required of the task are low.

If the above describes your current role, you may need to start questioning your future since now your success is tied to the metaphorical factory which can always move or have your role taken over by a cheaper resource. Just ask any US factory worker of the past 30 years if they are aware of this happening.

Focusing on the phrase of “skills required of the task are low”, think about the fact this means the person can be replaced by another easily. It would not take much to train a person to do their job. Now ask yourself if in your present role you are using skills/experience that could quickly be picked up by another?

If you are not careful and you take on a role or end up in a role that has low skills you are putting your future career at risk.

Time and time again, I see Business Analysts putting in long hours thinking that this will guarantee their future without looking at learning skills/gaining experience that will bring uniqueness to their personal skill set. End result for the ignorant Business Analyst is a future drop in salary and probable unemployment.

Next Page »