This site is run by Andrew Welch

It started as a Goldsmiths MA Design Critical Practice methods and processes portfolio piece. It is opinionated, subjective and not supposed to be authoritative. It is not always well referenced. Apologies, I’m working on it… slowly.

If you are interested in discussing how to implement some of the information here into your work please get in touch.

In software engineering, a design pattern is a general reusable solution to a commonly occurring problem within a given context. It is a description or template for how to solve a problem that can be used in many different situations. >

Why do we need a design method?… “Now the real reason…. it gives you rules to break”. Ross Olson >

Kids sit at desks, are told what to do and what not to do. They are given facts and ideas to learn and memorize. Obedience is rewarded, deviance or non traditional ways of approaching things are thwarted. Emphasis on testing as the be-all-end-all goal means that seemingly superfluous areas – art, drama, music, play are rmoved to give more time to learn the things that will be on the test. Creativity and innovative thinking is not only not taught, it is actively supressed. – What are some systems we live with today that were designed for a a world of the past, Quora. Accessed 2012.



Other stuff

  • Guidelines of Lateral Thinking
  • Generate alternatives for their own sake
  • Any assumption can be challenged
  • Living with but not controlled by cliches
  • Suspended judgement – not afraid to be wrong
  • Design different ways of doing things
  • Fractionation – deconstruct the problem
  • Restructuring not explanation
  • Reversal
  • Brainstorming – with other people
  • Analogies