Vous avez du mal à donner un sens à un problème complexe. Comment pouvez-vous développer vos compétences analytiques pour le résoudre ?

The problem statement must be clear, concise and must be reviewed by the sponsor and all parties must be in alignment that the problem statement defined captures a the scope and impact while also considering what is in-scope and out-of-scope for the problem statement. Essentially, there must be a business case which defines clearly the outcomes and quantifiable benefits of the project you are trying to solve and how it aligns with the business goals. The problem statement must identify the opportunities for improvement - what’s wrong, where is the problem appearing & how big is the problem. The problem statement also has to SMART - Specific, Measurable, Actionable, Result and Time-bound.

Best thing to do is to listen or observe and understand the actual problem. In my experience many customers actually define their problems as per their perception and our brain (technician's brain) usually starts jumping into solution mode. If there is a possibility get the problem recreated, check the environment, check if you can recreate it to have more clarity

Using modern problem solving tools such as lean six sigma with its DMAIC methodology or any other lean manufacturing tool will help you to correctly analyze the problem You may use Pareto chart or fish bone diagram or any other analytical tool

The first step is to clearly define the expected outcome. This allows one to view the problem from a solution perspective and avoids paralysis by over analysis.

Desenvolver habilidades analíticas pode ser desafiador, mas é uma habilidade valiosa em muitos aspectos da vida, especialmente ao lidar com problemas complexos. Aqui estão algumas dicas: Desenvolva Habilidades de Comunicação: A capacidade de explicar suas análises de forma clara é crucial. Pratique a comunicação eficaz. Pratique Resolução de Problemas: Envolva-se em problemas práticos e desafiadores. Quebre problemas grandes em partes menores para torná-los mais gerenciáveis. Leia Regularmente: A leitura diversificada expõe você a diferentes perspectivas e lógicas de pensamento. Considere ler sobre tópicos que não estão diretamente relacionados ao seu campo de estudo para obter insights inovadores.

There are two key aspects to consider: first, achieving the appropriate level of granularity, and second, formulating task descriptions along with the necessary steps for execution. Experimentation with various time and task groupings is crucial for the first aspect. Generally, tasks should be equivalent to one manday of work, and the total workload should not exceed 10 mandays. As for the second aspect, the level of detail in task descriptions depends on the crew's experience. More experienced individuals require less guidance and handholding, leading to less verbose task descriptions.

For me the Break it down option works for me. By dissecting the problem into its components, you can identify patterns, relationships, and dependencies that may not be apparent at first glance. This approach allows you to focus on solving one aspect at a time, reducing overwhelm and facilitating a deeper understanding of the problem as a whole. Also, breaking down the problem enables you to prioritize your efforts, allocate resources effectively, and develop a structured approach to finding solutions.

Extending on my point above about defining the problem. Next most logical step is to break it down into more sizeable chunks. Doing that will enable us to not only actually size it up but will also help us in actually initiating and prioritising where to start. In addition, it will enable one as to which tooling may be required to create a resolution.

Muitas vezes podemos resolver um problema pós fases. Entender o mesmo e sua complexidade permite entender se há soluções paliativas. Em tecnologia o principal objetivo é tornar o "sistema" novamente disponível, ainda que não seja a solução definitiva. Entender a complexidade e o que fundamental para a operação te ajuda a dar foco e não gastar energia em coisas secundárias. Ouvir o usuário também faz diferença. E dividir com ele o problema ajuda a dar foco no que é de fato necessário.

Olha, tenho visto tantos profissionais dispostos a estruturar problemas mas não a resolvê-los. Não burocratize problemas simples, mas faça o processo a seguir apenas para problemas que não dependem totalmente de você ou que não pode resolver (por falta de algo). Tendo o problema já definido, desenhe o problema, suas causas, impactos e encaminhe para resolvê-lo.

Avoid the perfectionist pitfall: a good solution is generally enough. Pursuing the "best" solution is a tested way to increase the chances of failure. Identify a couple of viable variants, but not more. If one of the approaches satisfies the requirements, go for it. You can always improve in a future iteration. At the same time, do not use "good enough" as an excuse for lousy quality. Even an imperfect solution has to be well thought through.

I believe that analyzing different options are extremely important. This helps us understand what options are better and what are not. This also provides us different perspectives and provide us freedom to deselect alternatives what’s not relevant and also help us achieve desired action.

Una vez analizado el problema se puede proponer una o varias soluciones, mostrando los pros y los contras de cada una de ellas. No es recomendable tener un numero elevado de las mismas, con 2 o 3 debería ser suficiente en la gran mayoría de casos.

After you got all the information you need and zeroed-down on the source of the problem, you need to contemplate which direction is best and fastest way for the resolve the problem.

There can be many options that provide a solution. Utilizing your teammates and coworkers can provide other viewpoints and other solutions. If you’re struggling reach out for expertise and help. You’re not alone.

The best solution is often the preference of stakeholders – perhaps the target is cheaper infrastructure or the least possible latency... These often clash, so ensuring that the correct parties have the right information to make the decision that they consider "best" is key.

As I said above, pursue the best among the ones which you could come up with, not in absolute terms. If you apply point 4 by the letter you may be drawn into a perfectionist spiral which has a big potential to make you fail.

Nesse momento, vamos refletir com todos, sobre as possíveis causas raizes levantadas. Aqui veremos que muitas vão se repetir, dessa forma traremos apenas uma delas. A partir daqui, vamos utilizar a Matriz GUT, para priorizar as possíveis causas, utilizar a matriz de priorização com a votação dos participantes, e levantar as melhores ações após a aplicação das matrizes, para discutimos do ponto de vista técnico, se de fato devem ser consideradas para elaborarmos um plano de ação. Aqui muito importante a participação de pessoas técnicas, com conhecimento do processo, líderes e gestores, para avaliarmos a viabilidade de tratarmos a causa e o motivo pelo qual se justifica a atuação nessa dor.

For instance, if the chosen solution to improve customer satisfaction is to implement a dedicated customer support team for the specific product line: Justification: The analysis revealed a concentrated dissatisfaction in post-purchase support for the specified product line. A dedicated support team can provide specialized assistance, resolving issues faster and enhancing overall customer experience. Evidence: Data from customer feedback surveys and market research highlighted the dire need for personalized support in this product line, indicating a direct correlation between enhanced support and improved satisfaction metrics.

Melhor do que apenas ter na sua cabeça qual foi o caminho traçado até a melhor escolha, é anotar e descrever como que tudo foi pensado e planejado, porque dessa opção e não a outra. Ter um ponto de vista claro e transparente contribui para convencer de que a sua resolução foi a melhor alternativa para o caso. Tendo como principal fator a comunicação assertiva. Se a pessoa para quem você vai justificar não entender muito do quesito técnico, o mais ideal a se fazer é ser simples e objetivo, eliminando qualquer possibilidade de dúvida ou objeção.

Do not judge how good or bad a solution is only on paper (or, only on ppt). Do early testing. Validate assumptions. Get real. Ivory tower architecture is worth nothing. Go for full life cycle involvement and roll up your sleeves. A little bit of dirt on an architect's hands have never killed anyone.

Implementing and evaluating the chosen solution involves putting the selected course of action into practice and assessing its effectiveness. This step includes executing the solution, monitoring its progress, and collecting relevant data or feedback. By closely observing the implementation process and evaluating the outcomes against the desired goals, you can identify any areas of improvement, make necessary adjustments, and ensure that the solution effectively addresses the problem. Continuous evaluation allows for refinement and optimization of the solution as needed.

Una vez alineado con el resto de actores se aplica la solución consensuada en los plazos estimados, siempre se hará primero en un entorno de test controlado y luego se puede aplicar en producción a un pequeño grupo para luego extenderlo al resto.

This is very important step, here you need test/perform and evaluate the solution which is going to provided to customers. And monitor the process and observe if it can be reach the expectations without affecting other factors.

Assim como nas etapas anteriores, se faz necessário ter um planejamento da implementação também. Entender e avaliar como que foi a jornada até chegar ao estágio atual, buscar feedback tanto de quem te supervisionou, quanto dos interessados na resolução. Manter a atividade de monitorando por um período pós-implementação para ter a garantia que tudo o que precisava foi solucionado. Além disso, documentar o fato para a base de soluções. E ao final, fazer uma retrospectiva de como foi, quais foram os pontos que geraram mais dúvida, e qual foi o aprendizado mais relevante.

In a nutshell, This is how I develop analytical skills to solve complex problems: By breaking down the problem into smaller parts and I ask questions to gain a deeper understanding too. I then collect and analyze data, look for patterns or connections and I test hypotheses and refine my thinking. By following these steps, I can make sense of even the most complex problems. Remember to take it one step at a time and keep an open mind.

Always be quick to listen, slow to defend and never assume until the problem statement is properly defined. Assumption is a common mistake in defining the problem statement. Collaboration involves active listening, patience and the will to solve the actual problem.

Fixing complex problems isn’t linear, You don’t often get the problem that you just know the resolution to. I like to reset the customer expectation by letting them know I don’t know. But what I can offer them is a real educated opinion on the top culprits. I’ll line them up and we will shoot them down. It helps them understand the real world complications with harder issues. From there it’s a matter of setting the issue up from most probable to least probable. Take the customer from thinking the path to their resolution is solidly on your shoulders to a shared expectation of being a team - it’s on our shoulders together. It becomes a conquest and and a shared experience at the end.

In this open space, I highlight the significance of fostering collaboration for innovative problem-solving. Diverse perspectives contribute to more effective solutions. Embracing a growth mindset is crucial, viewing challenges as learning opportunities. Celebrating both successes and failures cultivates a dynamic problem-solving culture. Leveraging technology, from analytics to collaborative platforms, enhances capabilities. Recognizing the interconnectedness of problems encourages interdisciplinary approaches, essential in our complex world.

In addition to all the steps, maintain a thirst for knowledge and a desire to understand how things work. This continuous learning will fuel your analytical thinking and equip you to tackle any challenge.