Problem solving in a company - Don't wait too long

What is happening when something goes wrong in a big company?
First things is a buzz, then people start to talk between them, after that a lot of meetings are organized at different level to see identify the root problem, the causes and discuss a lot of around what they should do.
In the end a committee is organized, with a stakeholder, an accountable and other so on. This committee will start all the process from beginning, will try to understand exactly what went wrong and prepare one or more solutions.
Of course each solution has a strict plan, with new process and imaginary solutions.
Why imaginary solutions?
Well, none of them were tested. Unfortunately, people from the committee didn't worked on the 'war' field and don't know the voice of the 'people'. Because of this solutions proposed by them will not be seen with good eyes by people.
A lot of time, this solutions don't have any connection with the real problem, are very complicated and are coming to late. To late means a fail, because you already lost the war.

What should we do in situations like this?

I would involve people from field to resolve the problem.
Try the most simple solutions.
Don't wait too long, try a solution, see if it's works and move to another one if the problem persist.
Don't add a new process to an existing one only to have more control.
Let solutions to grow and die organic. Don't enforce and die with them if are not good.
Be open to change.
Be prepared to recognize a fail - "fail fast".
React to change and don't wait too long.

All this ideas and many more are around to things that are very important:

React fast, don't wait to much. Each additional second that you wait will add an extra cost to you. Try each solution.
Involve people from field when you investigate the problem and search for a solution.

If everything fails don't be afraid to ask for help from an external resource. All around the world there are people better than you, that already had this issues and solved it.

Comments

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users. This information might be useful in the future when we need to decide where we want to keep and manage our users. Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

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

Cloud as a Story - Vunvulea Radu

Search This Blog