Você está debatendo com as partes interessadas sobre a viabilidade do recurso do aplicativo. Como você navega em perspectivas conflitantes?

What I find in the technical side of things is that some business people try to help define the technical implementation instead of focusing on the business/functional side. The most common question I ask is what are you trying to accomplish. Let the tech people sort out the tech stuff.

Listen to your stakeholder's perspective in terms of what is the business need for the proposed feature, potentially get some insight into their vision of the finished product and how it should be presented to the user in terms of accessibility for execution via the application. Explain the assessment process that needs to be considered before the feature can be approved for delivery in the requested fashion. Assumptions from a purely DEV perspective may taint the assessment it is best to hear the stakeholder's perspective to understand their need.

It is quite common to come across over features feasibility and potential value associated to it. To me it is about understanding the actual value\business need and mapping it with the efforts to drive the conclusion. For example, something might bring more value to the business by saving admin hours but requires a lot of investment and engagement from the resources. This is where I ask my stakeholders questions like, is it really worth it, is this really what you need by looking at cost & effort VS value.

In reviewing the proposed feature explain the following items need to be assessed in terms of the reality of the feature: 1) What is the perceived benefit of the proposed feature in terms of the stakeholder's vision. Quantify this if possible. 2) Assess the real costs of the propose feature in terms of : DEV, QA, deployment and training for the feature. All of the aforementioned items can help draw a proposed rating in terms of complexity. Help share the outcome of researching a) Perceived Benefit and 2) Real Costs for incorporating the feature into the application.

When debating app feature feasibility with stakeholders: 1. Acknowledge Concerns: Show understanding of their perspectives. 2. Present Constraints: Explain technical or resource limitations with supporting data. 3. Offer Alternatives: Propose feasible solutions, like simpler features or phased approaches. 4. Align with Goals: Connect alternatives to business objectives. 5. Encourage Collaboration: Involve stakeholders in refining solutions. This approach can help resolve conflicts while keeping the focus on delivering value. Saying 'No' is the last thing any Stakeholder would want to hear, if 'No' is the only answer we got then we should have the proper 'Why' to justify.