Discussion Locked

First year working plan.

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

For example,I have finished a Diploma in IT in some college.
Before looking for a job, I have to sit down and plan out my first working year in the industry.
What could I use to develop this plan.
Are there any links to some sites where I could find this information, or maybe such an example.
Thanks.

7 replies

by penguinsrule

I don't know of any sites or anything that can help. Here's what my first year was like.

December 21st - 1st day on the job.
December 22nd - I get the pager
December 23rd - everyone leaves town
suffering begins...
I learn..
more suffering
learn more..
and on and on..

by Ryan Boudreaux140

It all depends on what you want to accomplish. I know it sounds funny at first, but start with thinking of the end, what is your goal. Ask yourself, "Where do I want to be a year from now?" Draw a matrix diagram on a sheet of paper, split it into three columns. The first column lists all your skills, knowledge, training, etc. The second column is blank (for now), and then in the third column list your goal ("...a year from now"). Then this is the fun part, in the middle column is the "delta"or the divide between where you are now and where you want to be in a year. This is what separates you from your goal; think of what you will need to accomplish to reach your goal. Will you need more training, experience, or certifications? Each item you list here will give you clues to what your game plan for the next year will include. I hope this tool is helpful for you. It helped me over two years ago when I was still in school and working in another career, I am now a Network Administrator.

by penguinsrule

First take a piece of paper and draw a line down the middle. One one side title it applications, on the other side write administration.
Draw a line below that. Then on the applications side you can write a few things like various software products, programming languages, project design, project leadership, software engineering, quality and testing, desktop support, helpdesk support, applications migration, etc.. Note that on the applications
side of things these things are often moretransportable, i.e. not vendor specific.

On the administration side then write down things like helpdesk support, technical support, troubleshooting, operating systems support, systems administration, database administration, network administration, user support, storage, printers, tape drives, disk drives, servers, pc's, hardware, all kinds of things like that.

Then make a decision which way you want to go.
Then you can draw some lines as far as direction you want to go on the side you choose. The line of growth has to do with the amount of decision making that you'll be doing and the amount of autonomy you'll have. On the lower end, people tell you what to do. On the higher end, you have to figure all that out yourself and you decide.
You really do set the stage for yourself.

This discussion is closed to new replies.