Skip to main content

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

By
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

Post a Comment

Popular posts from this blog

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

By
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(...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
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...
Post a Comment
Read more

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

By
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...
Post a Comment
Read more