Ihr Kunde möchte auffällige, aber unpraktische VR-Funktionen hinzufügen. Wie gehen Sie effektiv mit ihren Anforderungen um?

First step would be to assess the impact the demands - look at feasibility and risks that come with extravagant features. It is easier to demonstrate viability as someone with experience in VR, which clients usually don't have. Honestly, they're not to blame - the marketing around VR is sometimes really ridiculous and overpromising. This must be emphasized, demonstrated, and explained on concrete examples that will be understandable to the client.

The basic principle is to understand how much the customer knows about the Virtual Reality technologies. Next is to understand their business before filling up them with Technical jargons. Focus on the problem that you think will be useful if VR is deployed in there ecosystem. Show Virtual Reality examples of similar industries even if it’s there on YouTube or public platform. The customer will appreciate that you are talking in his language rather than just showing ppt. After that ask for what is the initial use case that comes to his mind for VR implementation and then take it from there.

The desire for flashy and impractical features is all too common. Everything, especially early in a company's VR journey, should be linked to a measurable business outcome. VR needs to show ROI. If an impractical feature is brought up, highlight the cost to implement it, the change in process it will require users to make and help them see that there is no business metric that will be impacted by it.

It is important to note that your client is paying you to solve his problem or he is looking for a solution. The one suggestion that I can give based on my experience, You need to drive the project and wear the cap of expert, Solution can be solved by different ways. Sometime just for the sake of sale and dependency on certain technologies, companies make commitments which lead to wrong business impact, it’s important to think for alternatives and focus on the problem statement rather than just throwing any random solution just for the sake of sale or fancy technology

Setting is realistic goal is very crucial on the same side don’t be resistive. Be open to attempt what the customer asking, important is not to commit and come back to him after some homework.This depends on your teams capabilities and some time as a founder/ key member of startup you have the belief that this can be achieved , take that of risk and partner with people outside your team and integrate the solution.

It’s important whatever you are building in VR is solving the basic problem that customer is asking. First make the experience principally right and then focus on smaller things. Use a backend analysis which shows that how your Virtual Reality app is performing, give that access to customer and to your customer success manager. That feature is useless if it’s not solving the basic problem.

One of the major mistakes I have seen companies make while they are working on VR solutions, they decide on important aspects of the application in isolation because they feel it’s right but it’s important to note whether the same things liked by your customer or not. For example you are making a VR experience but it can be made by hand based interaction or controller based interaction. Show the options to customer and then proceed and follow this principle at every stage of project. Mark my words you will a smooth handover and also appreciation.