Skip to main content

Company journey

When the size of an IT company change, the people expectation are changing. They usually expect more benefits from the company and many more. In the same time the company expectation increase - higher level skills, higher commitment and so on. You know the story.
On the same page, for a company it is more important to deliver and to achieve annual targets than the vision for next 3-5 years. This targets can be expressed in number of employees, number of projects, revenue, new clients or other metrics.
In small company we are oriented to people. Giving our best to keep people happy. Having happy employees, a company can go even on the Moon. People will feel that they are part of the company, they are part of the company dream. In this way a company will have a great success.
For such a company, the journey is the most important thing. It is not so important if the target was reached, the journey was the most important thing for company and people.

When a company grows, things are starting to change. First of all the journey it is not important anymore. The target becomes that most important thing for all employees. The target has to be reached without taking people into account, how the journey is or even the quality of the product that is deliver.
Because of this, the final target becomes more important than people and people needs. Company becomes a slave of the target that is only a small part of the original vision. The level of pressure on each employ increase.
Odds situations appears when people are not important anymore.
First thing is the ‘overtime’ that is becoming part of company structure and way of doing business. This will have a direct impact not only on people but also on the quality of the products. You cannot have quality when the team is over burn.
People can lose very easily the focus and the things that make them happy. For example you can have a person with great skills on backend. But, because you need people on UI you will allocate him on that part of the system. After this, another project will come that requires people with skills on DB. The same person will end up on DB. Or that person ends up making things like team leading or management without liking.
Yes, it is great that you will have a person with all this skills, but in the same time you can end up with an unhappy person, because he/she do things in an area where they don’t feel happy.
In such a company you cannot afford to be wrong or make mistakes. Once you made a commitment, even if you realize that it will be a fail you cannot do anything. In this kind of companies, a person that recognize that he was wrong will be placed against the wall.  Odd situations will appear like organizing an event that you know that will not bring value to the company. But you going forward with it because at the begging of the year you made that commitment.

This is vicious circle and once a company is there it will be very hard to get out. The greatest risk for a company in this situation is to lose the company culture and values. Once this values were lost you will become another company from a city.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...