En estos casos lo que a mi me ha dado buenos resultados es: Primero me aseguro de entender claramente el motivo detrás de cada solicitud. A partir de ahí, priorizo lo que realmente aporta valor y lo que es esencial para el proyecto. Mantengo una comunicación abierta y transparente, explicando plazos, costos y posibles impactos en el alcance. A veces, ofrezco soluciones intermedias o una versión inicial del producto que pueda ir mejorando con el tiempo. También me aseguro de documentar todos los cambios para que el cliente tenga claro el impacto de cada solicitud. Finalmente, siempre establezco límites claros para gestionar el alcance y asegurarme de que el proyecto siga dentro de los parámetros acordados sin comprometer su calidad.

Set clear project scope boundaries, prioritize requests based on impact and use a structured change management process. Communicate trade-offs, negotiate timelines and explain resource constraints. If needed, propose a phased approach or additional costs for extra features.

1. Set clear expectations regarding time and budget. 2. Analyze the change requests, their feasibility, and impact on the whole project. 3. Prioritise the tasks, and set a clear plan for the next sprint. 4. Clearly discuss with the clients what they will achieve at the end of the sprint. Be aligned with your client. If you are getting a lot of change requests all the time - this is a problem of your processes. Make sure your client understands his/her own goals and you all have the same vision.

Gerenciar solicitações constantes dos clientes exige equilíbrio entre atender às necessidades e manter a viabilidade do projeto. Para isso: Defino expectativas claras desde o início, especificando o escopo e os limites do projeto. Uso um processo estruturado para avaliar solicitações extras, considerando impacto em custos, prazos e recursos. Mantenho comunicação transparente, garantindo que o cliente compreenda as implicações de cada nova demanda. Dessa forma, evito desvios no projeto sem comprometer o relacionamento com o cliente.

When clients constantly request additional features, it’s crucial to set clear expectations and manage scope effectively. Start by revisiting the initial project scope and reminding the client of the agreed-upon goals. Engage in open conversations about how new features may impact timelines, costs, and overall project quality. Offer to prioritize these features based on business value and technical feasibility. Propose phased rollouts, where new features can be introduced incrementally, ensuring that the project remains on track. Establishing clear boundaries and maintaining transparent communication will build trust and keep the project aligned.

The starting point for any project before one starts designing and implementing is the sign off on the Business requirement documents and the detailing the scope of the project with implementation timelines.. At times the customer is not proficient enough to prepare the BRD and Scope documents, in that case either offer a functional and technical consultant services who can prepare it on behalf of the customer. Post which the documents can be signed off, with detailed sub process and timelines for development and implementation

In my experience working on DHIS2 and data-driven projects, shifting requirements are almost inevitable, especially in health system implementations where real-world needs evolve. While it's critical to define 'what needs to be done' from the start, flexibility is also key to ensuring the solution remains relevant and impactful. My approach? ✅ Set clear expectations—a well-defined scope reduces surprises. ✅ Prioritize changes—not all requests are urgent; some can wait for later phases. ✅ Communicate trade-offs—every addition affects time, cost, or performance. ✅ Leverage agile methods—iterative improvements help manage evolving needs.

Para gestionar solicitudes interminables de funciones de un cliente, es clave aplicar una estrategia estructurada y transparente. Priorizar necesidades, establecer expectativas claras y comunicar el impacto de cada solicitud en el desarrollo del producto ayuda a mantener un equilibrio entre innovación y viabilidad. Además, herramientas como Yoneos permiten centralizar y organizar solicitudes, facilitando la toma de decisiones basada en datos. También es útil aplicar metodologías ágiles para evaluar la viabilidad de nuevas funciones sin comprometer la eficiencia.

Perspective is this instance is key. A client who takes the time to articulate requests are clients that are still engaged and willing to do business with your organisation. As a part of that conversation, it is important to have practical conversations on timelines and possibilities regarding requests so as not create unrealistic expectations for clients. This gives room for proper processes and follow through to ensure that when the clients requests are satisfied, the process can be replicated with efficiency.

Managing evolving client requests is about balancing flexibility with control. Setting clear expectations upfront, reinforcing the project scope, and having a structured change management process ensures alignment. Transparent communication is key—helping clients see the trade-offs between added features, timelines, and budgets keeps projects on track while maintaining strong relationships.