Which direction are IT heading?
Author: Tomasz Szymanski

Which direction are IT heading?

The natural career path in IT is something like:

specialist -> team leader of specialists -> technology manager / project leader -> CIO/CTO.

It's to build technical awareness and social skills especially management. Working with people who follow such a career path is simpler and with less conflicts. Such people in fact connect and are at the same time mentors for those at lower career levels. Predictable actions with development plans for employees.

But unfortunately, this is slowly becoming more and more rare. I like to analyze various things in the field of management and I am surprised by the trends that can be observed. In my opinion, these trends are negative in a way. And above all, the very definitions and job titles are slowly being degraded.

In management theory, the word manager is used for being responsible for between 5-7 people. Today, you can be a manager of yourself - meaning 1 person.

Project management as the only thing you finished was a theoretical project management course. How can you manage a technical project without knowing the technology in which that project is embedded? Through stories and tales at working group meetings? [Doesn't work does it?]

The problem with strict technical staff - instead of increasing the hiring of exactly such specialists (programmers, networkers, etc) - today the problem is solved by increasing hiring for coordinators or new project managers (see example above). [Doesn't work does it?]

Since more coordinators don't work how about a matrix structure and assigning specialists to multiple projects? [Doesn't work does it?]

Then how about taking on even more projects and somehow overloading the specialists even more? Maybe it will have an effect? [Doesn't work does it?]

The hardest thing about IT is understanding what impact it has on the business and what impact the business has on IT. This is not an easy topic and really requires cross-cutting knowledge.

To do the project (short version) you need:

  • design the architecture and link it to the revenue model (!)
  • consider technology options - that is, which technology meets the substantive requirements
  • delegate tasks and coordinate them for common points (mile stones) for the selected technology
  • execute tests and analyze application's security

Technology knowledge is required at each of these stages.

It seems that the current career trend in IT is as follows:

(empty) -> (empty) -> technology manager / project leader -> CIO/CTO.

And looking at the job descriptions, the CTO/CIO is really Project Leader. Some companies have already figured out what the problem is and are increasing their hiring of technical staff. But.

They are not solving project management problems like number of coordinators of coordinators.

A pretend leader without technical knowledge can't get respect since he lacks domain knowledge. It is not possible for him to have prestige and full confidence in the decision.

So how do the specialists themselves look at this subject. They also confirm that increasingly the requirements are to specialize in several technologies. This is unrealistic because a day has only 24 hours.

In a sense, automation can be a way out. It is best to automate standardized technology with good documentation. Meanwhile, in companies we know how it looks like.

I will honestly say that I do not know how it will end up with 5-10 years.

It seems that companies in terms of organization cannot continue to operate in an efficient manner. It is rather reasonable to expect that the time to solve problems will permanently increase.

This is not about on-premise or cloud technology - this is about a permanent lack of resources in the form of knowledge.

Even if someone creates a new ticket, even if the technology because it quickly processes, assigns and even tries to solve the problem - many new events will be closely related to changes in the organization and technology. Someone will have to make decisions. Decisions that will affect ... whether this business will still exist. This is not a pessimistic comment, this is the natural task of the market - to self-regulate within the limits of law and technology.

The old motto is:

Chaos -> Management -> Chaos.

probably slowly it is time to change it to:

Chaos -> Information Technology + Management -> Chaos.

The latter is interesting because many companies have not yet matured to the stage of having an Enterprise Architecture. [You're guessing right for this position, too, you need to know something about technology]

#management #itmanagement

要查看或添加评论,请登录

Tomasz Szymanski的更多文章

  • AI in App* ... social impact?

    AI in App* ... social impact?

    Artificial Intelligence in Applications..

  • Basics of economics and management (Part 1-5)

    Basics of economics and management (Part 1-5)

    Part 1: https://www.linkedin.

  • Color Schemas in Digital Camera

    Color Schemas in Digital Camera

    How do we see colors? As a fresh air hobby, I just tested several Color Schemas. My vision is to represent nature as it…

  • OS Statistics

    OS Statistics

    This time the post is more serious, it's about data and statistics. What is striking is the reliability of the data.

    3 条评论
  • Open Source Software and Product Marketing

    Open Source Software and Product Marketing

    Surveys This week I asked you to complete the surveys: Question A: Do you know what FreeIPA is? 700 Views / 13…

    1 条评论
  • Open Source Software and Linux

    Open Source Software and Linux

    The inspiration to write this article. In the last few days I've read a few dozen publications about Open Source and I…

  • Nowa epidemia - jako komedia

    Nowa epidemia - jako komedia

    Wyobra?my sobie ?e jest 01.04.

    6 条评论
  • Enterprise Architecture Introduction #4

    Enterprise Architecture Introduction #4

    Before I start describing the planned topic (a little postponed), something that has recently appeared on the forum for…

  • Enterprise Architecture Introduction #3

    Enterprise Architecture Introduction #3

    After part 2, it is time for part 3 - What a sample project might look like? Let's imagine a situation that you have…

    1 条评论
  • Enterprise Architecture Introduction #2

    Enterprise Architecture Introduction #2

    And why is it difficult? In the case of simple IT systems, they can usually be presented as a 2D or with semi-depth i.e.

社区洞察

其他会员也浏览了