I've had the opportunity to work for many different types of companies and consult at many places around the world. Each project has had its own challenges, varying in complexity and scope. Designing a product for people is inheritly dynmaic and naturally challenging. But, a product is only a success when it makes a persons life better than it was before. That is the reason I love what I do.
I believe it is important to keep product design involved throughout the process of building the product or designing a service. While it should be very involved from the very beginning with contextual inquiry, user research and usability tests, UX should continue to have a stake throughout the entire process.
This is a very early prototype created to understand the needs of the business and validate its technical buoyancy. Often I will create these to be reviewed by the team and stakeholders, define a general vision and begin moving forward in one direction. Along the way, I may create more prototypes to help explain interactions and intended functionality.
Understanding the information architecture of a tool, is very important for the team and stakeholders responsible for the product. I create these flow diagrams as articfacts that can be referred to during development and shared with those who have buy-in to the project. Periodically I will update them when things change during the lifecycle of product development.
Agile developement incorporates test driven development, continuous integration, paired programming and quick iterative cycles. So how does design fit into this model? In 2012 I attended a conference called UXMad and gave a talk explaining the role and value of design on an agile team.View Presentation