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

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
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

[Post Event] Azure AI Connect, March 2025

By
On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.
Post a Comment
Read more