When a client requests changes in strategy after a project has already started, it may seem like a challenge, but with the right structure and communication it can become an opportunity to improve the project. It is essential to understand why the client wants to change the strategy. Organize a meeting to discuss in detail the new needs and the reasons behind the request. This helps clarify new objectives, avoiding misunderstandings and aligning on expectations. The key approach is to maintain clear and open communication with the customer, aligning the intermediate steps with their needs. The end result should be a project that reflects an agile strategy and the ability to adapt, an important added value in any data analysis project.

As Charles Darwin said, "It is not the strongest of the species that survive, but those most adaptable to change." In my experience, pivoting during a data analytics project requires adaptability and a structured approach to maintain progress. For example, I once addressed mid-project strategy changes by meeting with the client to clarify new objectives and assess how they impacted the timeline and resources. One helpful strategy is breaking down the project into adaptable phases, allowing you to integrate new goals without losing momentum. A common mistake is rushing adjustments—taking time to recalibrate with the client ensures alignment and sustained quality in the final output.

Entenda o motivo da mudança, busque saber os objetivos da nova demanda, alinhe bem a expectativa com os stakeholders, fale com o usuário final para entender se tudo tem aderência. Com isso feito desenhe os cenários (A, B e C) reorganizando o backlog e redistribuindo os recursos no tempo, priorizando de acordo com o valor x esforço. Chegue em consenso com os interessados de equilíbrio entre ganhos e perdas e definam um dos cenários para seguirem. Divida a responsabilidade de definição, assim todos ficam comprometidos com as decisões tomadas e com o que foi deixado de lado para que a mudança fosse possível e documente tudo isso. Para reduzir as mudanças tente focar menos em desejos e dores/sintomas e mais em casas raiz dos problemas.

Accepting and responding to changes mid-project is not just a technical matter, it’s a show of empathy and commitment to the client’s vision. To adapt means we’re truly listening and understanding their evolving needs, recognizing that circumstances can shift. This approach assures the client that we’re on their side, valuing their vision and working to make it a reality. Beyond merely completing a task, adaptability demonstrates our dedication to delivering results that align with the client’s goals, even if it means making adjustments along the way. This level of commitment builds a relationship of trust and collaboration.

1. First have a frank discussion with the client to understand why they are changing the strategy in the middle of an analysis. Tell them that you will need to evaluate the impact on the scope of work and adjust the effort and billing . 2. Do a thorough impact analysis, specially factoring the cost to demobilize existing skills/applications and mobilizing new ones.The impact may be from "easy enough" to "we might need a new contract". also consider hybrid or in-between solutions. Have atleast 3 alternative options handy apart from the main solution 3. Communicate the main solution , alternatives and cost impact to the client for each. You will definitely end up with one favorable outcome