The first step: identifying and understanding the problem. I want to make sure that I am thoroughly informed about the problem so that I can accurately pursue solutions.
I dedicate the beginning of the project to meeting with internal stakeholders, understanding the target customer, familiarizing myself with the industry and competitors — collecting as many insights as I can.
These insights form a solid base the plan for whole project. Trying to solve the wrong problem leads to wasting resources.
The plan is then defined for the second step, strategy.
Am I solving for one main problem? Several? What relevant content should they be presented with in order to lead them to reach their goals using the product?
User stories and journey maps define how the people would interact with the product. We plan the structure and catalog the content that will be published, making sure it responds to use cases and scenarios.
Having planned the priorities in the previous step, I start working through a broad range of solutions in the execution phase, validating each of them, looking for the best approach.
I align with developers to ensure that the solutions can be built with the available resources. I translate my wireframes to a prototype to put in front of users in order to test their validity.
Adjust and then proceed to the visual design phase while elaborating the style guides and specifications for the project.
The client communication style and the development workload determines the handoff process.
Once everything has been worked through, presented, finalized, I’m taking a support role during the development process. I make myself available to project managers and developers so we can ship successfully and on time.