I believe design is about clearly communicating your message and I approach the design process in the same way. Straight talking, transparent communication.
I've tried to reflect that in this portfolio of my work and be clear about the inevitable learning experiences on each project along with the successes. I hope this shows that I have reflected and learned from each experience to ensure the most successful project I'll do will always be the next one.
I've had a healthy interest in human psychology since university and taken a more professional interest in user psychology around three years ago.
User experience research has been a part of the design process for centuries. With digital design we can continuously test and iterate a product at a much lower cost. I've adopted the principles of Lean UX design into my process. Identifying the assumptions and building the simplest feature to test it's effectiveness through short iterations.
It's been 15 years since I designed my first website made in a wysiwyg editor and not very intuitive but the start of a continuing learning process. I've always communicate directly with the client as we worked through each stage of the design process.
I feel it's important to keep people in the loop with each decision, creating mood boards, low and high fidelity mockups and then moving to build. To get important feedback at the earliest stage.
I've been working on applications for four years. Elearning, LMS, project management software to list a few. I find it important to keep track of all the standard design patterns as users spend more time using other applications.
Interface designer is like a therapist, ask the correct questions and read the sub text in the answer. I enjoy the meaningful feeling of been genuinely helpful to improve how someone uses something in their day.
I've been native in the core languages for a long time. In my opinion a good knowledge of how the technology works is vital for design.
Often I see designers putting a feature in the design without knowing the development time. I'd argue that to include a feature you need to know it's cost and it's value, if the cost is greater than it's value then don't buy it.