We lift barriers between creativity and technology, and converge advanced development into outcome-driven solutions. Pushing boundaries in gaming, digital, and experiential since 2010



Posts: 407
Reposts: 0

"Read This Before You Build Uber for X"

Interpreting a challenge or brief can be relatively simple, but truly understanding the problem that we are trying to solve is no doubt the most important of all.

To achieve this, at Rush we embed a design-driven culture in our approach, putting "the customer" first by applying human-centric creative processes to build meaningful and effective solutions.

Design thinking requires stakeholders to always question the brief and the problem to be solved and to revise the opportunity before embarking on its creation and execution with a common goal -- by truly understanding the problem can we ensure the solution meets the user’s / customer’s needs as closely as possible.

In the below post, Sam addresses some interesting points at a more semantic level, things to understand, before you dive ahead to build the next "Uber for X / Tinder for Y"

The problem, however, seems to occur in the execution of this idea. That is to say, technologists have been trying to use the Uber product as the exact roadmap to disrupt the entire service economy [...] The reason for this high failure rate is most founders underestimate the intricacies and nuances of the specific service industries they are trying to uberize.

As a free user, you can follow Passle and like posts.

To repost this post to your own Passle blog, you will need to upgrade your account.

For plans and pricing, please contact our sales team at

Sorry, you don't have permission to repost or create posts.

Repost successful!

View the repost

Repost successful!

Your repost is currently a draft. Review your repost and request approval.

Something went wrong whilst reposting - please try again.

Sorry - this is not an option. This post already exists in the Passle you have selected.

Try reposting to another Passle.