Frank19 wrote
Chris...thank you again for all your help. I can definatly say that I have touched on small aspects of all areas in which you have listed. However, I have not gotten into the formal things such as creaing Process Flow Diagrams and the like. The closest thing that I have done similarly to this is when we brought in our new sofware solution I filled out a 50 page business analysis questionaire which they then used to make a business analysis for our company.
I am going to e-mail you a working draft of my resume now. It's the first time I've been re-working it since I graduated college a few years ago so there are definate areas for improvement. Let me know what you think.
Lastly, I am going to look into all the skills that you have listed and I'm glad I found this site because it seems to be a great resource for all of them. However, my question is once I read up on these skills are they things I should list on my resume? Also, once I start submitting my resume is there a certain position I should be applying for? For instance at this point should I only be looking for Junior Analyst positions or are there other possitions leading up to a BA where I can get my foot in the door?
Thanks again and the resume is on it's way!
|
Frank,
First, I’ll quickly answer your direct questions.
Q: Once I read up on these skills are they things I should list on my resume?
A: You should probably have a skills section in your resume which lists theoretical skills and experiential skills. This section is just a list of skills such as; UML, BPMN, Process Flows, Activity Diagrams, Data Flow Diagrams, etc. Anything that you feel you can explain well and do if required. There is no need to differentiate in this section whether you have on the job experience with it or not. But in the interview they will ask and you must be honest. With that said, try to get the experience. More on that later.
Q: Once I start submitting my resume is there a certain position I should be applying for?
A: Probably Jr. Analyst and Analyst positions. Avoid Sr. Analyst positions, you don’t have the experience yet. However, since you have some (maybe even a lot) of informal analysis experience you may follow a shorter career path curve than others to make it to that Sr. Analyst position. There may be other positions that you can apply for to get in through the back door, but until I know a bit more about your background it is hard to say.
Now the general stuff.
So you have done business analysis (as I expected) but more informally. Now is your chance to formalize your experience prior to changing jobs. You are in a unique position. Small companies offer amazing opportunities since they offer the chance to take on so many different types of challenges. You become the big fish in the little pond. I learned this from my own experience after spending 4 amazingly valuable years at a small engineering firm (150 employees). So take advantage of it. How you ask?
The first thing you should do is write your ideal resume. As you read up on more formal and structured business analysis methods, write you resume as if you have the experience already. This ideal resume represents the goals that you want to achieve in your current position. Now that you have your goals, tailor the way you do your job and the assignments you volunteer for to meet these goals.
Now, let’s continue from my previous post. I mentioned the following three high-level tasks.
- Document the business workflows/processes as they exist today
- Analyze the business workflows/processes and identify possible improvements
- Compare options and weigh cost of each versus benefits of each
Let’s drill down on them one at a time (one per post) with a specific example you may have from your experience.
First, we will start with Documenting the business workflows/processes as they exist today. This is often referred to as documenting the AS-IS Process (opposed to the TO-BE Process). In your email to me you mentioned that you come up with “ways to make the warehouse more efficient in picking material”. Let’s pretend for a minute you haven’t yet improved this process. Now, you may already think you know how to improve the process, and to some extent you are probably right. But by following a structure analysis process we might even identify further improvements that can be made. Use this example to answer the following questions for me.
- What triggers the process? Is it some kind of request for an order?
- Once we know what kicks the process off we need to identify and document each step in the process. The steps may be performed by different workers. This is also important information to capture. Provide as much of this as you can. For now just list the steps in sequence and who is doing them. Then I can walk you through how to put this in a process flow (if you need assistance with this)
- Verify the process with all of the different types of workers involved. After all, if you are documenting your understanding of the process it may be wrong. Also, if you spoke with a worker or two they could have different perspectives and understanding of the process become they perform only a small part in it (while this is very important when actually doing the work, for this forum we will assume your process is correct)
After verifying the process with the different people involved, it should become pretty clear whether you have documented it correctly. Now you have your AS-IS Process documented.
Once you provide the process we can take the next step of analyzing it to identify areas that could be improved.
Chris