Each new project poses unique challenges, but the methodology to handle them remains the same.

Beginning to work on a problem is an evaluation of the resources versus needs, in which case time and money are some of the more common resources. 

With little time and money, these days I can still do a lot to understand the problem and define a solution to a simple project for small businesses like building a scalable website with SEO.

With more time or more obscure problems, understanding what results are expected are more important than the problem presented.

Building a well considered plan for researching the problem and gathering a mix of quantitative and qualitative data is essential to defining the right question for the results we want, and synthesising the findings into actionable results means we can justify our decisions with rational user insights.

When building a prototype I consider Material Design, Human Interface, and Carbon system guidelines when generating a cohesive design, but where this isn't possible testing is imperative.

In a perfect world, this process would be beginning to end in one clean sweep, but perfect is the enemy of good and we live in a world of iterashons  itarashions  iterations.