Verandr Philosophy

Challenge the requirement

It is critical to form a deep understanding of customer requirements, especially during early stages of a project. There are a thousand ways to implement every feature, and it’s our job to understand why the customer has chosen a specific path. A great way to do this is to challenge the solution itself.

We believe in making the most of our varied experiences and diverse backgrounds to suggest alternative solutions that may be more efficient, simple or delighting to customers.

Customers bring requirements in many stages of refinement. Sometimes they are loose ideas which we can fine-tune together. Other times they can be very detailed and specific about how something should be implemented. But taking detailed requirements and implementing literally is not an excuse for broken software.

We do not hold customers hostage to their own requirements.

We take responsibility for ensuring requirements will deliver the expected outcome.

Regardless of the outcome, challenging requirements is an effective method for understanding why. If we suggest an alternative and the answer is “no”, it’s an opportunity to open up dialog about the original solution.