IT Employment

General discussion


How do you best market your efforts

By whatsmystatus ·
I have been in IT for 8 years and have seen many changes during that time. One thing that I would like input on is how I can best market my efforts internally.

Recently due to a lack of the business being aware of what IT really does they reduced head count. I want to learn from this and communicate what I have done and what I am working on in a way that doesn't look like I am just trying to get attention.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Balanced Scorecard

by JamesRL In reply to How do you best market yo ...

A balanced scorecard will show a high level health check of your organization every month.

I was at an organization where we implemented it and sent it to the other department's managers/directors/VPs every month and they gained a new appreciation for the kinds of efforts that went on in IT.


Collapse -

Status Reports

by Craig_B In reply to How do you best market yo ...

It sounds like you need some sort of status report. The key is to find out what/how the company values things and write a report based on that.
They may value time of completion of calls/projects, or uptime of systems, or money, etc.
Find out what the company values, how they like it reported and write regular scheduled reports based on this.

Collapse -

Status Reports are a good things but ...

by Errk'd Guy In reply to How do you best market yo ...

I am all for status reports and have found them to be very useful
for my fellow managers as well as for myself. The frequency and
style of the report is what you will need to work on with your
management types. It is likely that they will want a monthly (not
weekly) summary of IT?s productivity and/or major projects.
Most will not be interested in the 'behind the scenes magic' that
keeps network services humming. But a monthly reminder will
help with the perception that you don't have enough to do.

Be sure that you write your narratives in plain English avoiding
techno-babble and acronyms most people would find unfamiliar.
I have even resorted to "plumbing" analogies on more than one
occasion to explain bandwidth. Also, be careful of what numbers
you report. The number of server and application patches
installed is not nearly as descriptive as the time and number of
staff it took to do them, test the patched system, not to mention
the "why it is important to keep the system current".

Try to structure the narrative in a way that not only reflects what
was done and how long it took, but also what that (end product)
means to them as far as services (ie. continuity of service,
updated redundant system for DRP, maximum email server
reliability, etc....)

One last thing ... If management had the impression that you
could do with fewer staff, it leads me to ask the question. ?What
were they doing during their down time?? While other managers
don?t see the brainstorming and trouble shooting in the server
room, or the imaging of a new machine not to mention all those
great things we can do with remote management software, they
do notice to many copier/water cooler conversations. Be sure
staff have low priority tasks to do when downtime does occurs.
Be it cleaning up the mess of wiring at on the patch panels to
online or CD skills training.

Collapse -

Track your work

by max39 In reply to How do you best market yo ...

Most IT departments are terrible at tracking effort. Status reports are ok, but if you work on many tasks during the week/month, you have to spend quite a bit of time remembering what you did. More importantly, your experience gained by performing even simple tasks has great historical value when you encounter a similar situation down the road.

I realized this several years ago and started using MS Outlook "Tasks" to manage my work ( pick your favorite tool) My main motivation was to create a "historical repository" for my own reference to remember solutions to particular problems...I found that it was also a great way to let my boss know what I was working on as well as the details.

When I complete a task - any task, I forward the task status report to my manager. That way he knows everything I have done....It also allows me more freedom since it demonstrates "self-management". You don't just want to communicate the fact that you add value, you want to communicate that you can manage your own efforts to add value.

Collapse -


by Errk'd Guy In reply to Track your work

This is true and very useful if you are ever required to generate
statistics and/or defend a staffing budget. Being in a small
agency with a small IT staff I didn't need a full fledged Help
Desk, Trouble Ticket system. However, I did build in-house a
served database that tracks projects and resolved issues
(including who was the problem, who was the tech, what was the
issue, when/how was it resolved and how long it took.)

Sometimes it is a pain as smaller user fixes take as long to
resolve as it does to eneter them into the tracking dbase. But in
the end, it provides a great report on how things are running
who (or what machine) may be becoming a problem, etc.

Related Discussions

Related Forums