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(...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...