If I were to choose one thing to tell my younger IT professional self, it would be “know your business.” That could mean many things, but what I’m talking about is make sure you have a solid understanding of the following:

  • Expectations – make sure that what you are doing is what is wanted/expected
  • Your role – in your team, your organization, and your company
  • Your value – what you bring to the table that others appreciate
  • The numbers – any numbers about you, your role, your job, and what you deliver that others look at or that guide business decisions
  • Measurements – related to numbers; what gets measured gets done, so know the key performance indicators
  • Money – how it effects your position, your team, your organization, how budgets are decided, and what gets tracked

I have worked with too many people in my careers that have flawed thinking. A lot of it stems from not knowing the business of what they do. They could be subject matter experts at X, but still not be successful. Knowing your business helps you to see the “big picture” in a light that will help you understand what decisions are being made, why they are being made, and what decisions are likely to be made in the future when Y happens. Many IT professionals complain that management just doesn’t get it; however, perhaps a more useful approach is to ask how management is looking at things.

  • We used to have this displayed in the engineer department at work. Always put a smile on my face!

  • Part of knowing your business might also be knowing how much time your business requires.  I was about fourteen or fifteen when I realized there were more things to do than I had time in a day, and I would have to prioritize between them--and DROP one or more of my fun pastimes.

    Talk about "adult shock!" 

    Perhaps worse, I whined about it for a few days until I realized everyone had the same problem, and didn't need me to share it with them.  Sigh.  The trials of youth.

    Maybe something to send back in a time capsule would have to do with that.  "Figure out the obvious about something, and don't say it.  Because someone's already heard it--maybe dozens of times--and won't appreciate you being obvious about it."

    Or "Walk a mile in someone else's shoes . . . "

    • Expectations – make sure that what you are doing is what is wanted/expected

    As a long time manager of IT professionals I have two views on this:

    1. It is my job to set expectations of behavior and performance for those that work for me. If I do not then I have no authority or right to hold them to any metric. It is a failure on my part. I also, need to set my expectations based on their past. Remembering that a young person may not have ever encountered a particular situation before. They may need extra attention or assistance in moving a project forward. You are the one preparing them for better things and the next job.
    2. As an employee, you have to ask your boss and peers these questions. It is something that has to be discussed every so often. Not just in performance reviews, but in weekly or monthly meetings. WHat of the two dozen things on my plate do you want time to work on. Here is how I think they should be ranked and what level of effort I think they deserve.

    Both of these help make life in middle management livable and I hope it translates into me being a decent boss.

  • " It's about the business stupid!"

    rule #1 for IT.

  • You can’t know it all, but an understanding of the business can help a lot.