I've worked in E-commerce, Enterprise Retail, E-Learning, Enterprise Learning, E-Government, Restaurant Technology, as well as other Content Platforms
I start by asking a ton of questions to try and understand the problem we're trying to solve. Once I have a clear understanding I'll jump into generating multiple hypotheses based on the data I have, or by talking to the users to understand their pain points. Then the research begins and discussions start happening about what we know and what we don't know. At this point, I understand the goals, the personas, the market, which helps inform the product vision or direction we want to take. It's now time to get out the pencil and paper and start sketching. This is an ongoing iterative practice throughout an entire project to flush out ideas rapidly and not jump the gun too quickly to high fidelity mocks. I'll share my sketches and ideas with the team. Often iterating again and again to all be inspired about the direction. I'll then jump into high fidelity wireframes, do some more UX iteration's based on user tests, more research, and ongoing findings. Once the user experience starts to become more solid with testing it's then implementation time. This also can happen very early, it just depends on goals, timeline, key metrics of success, and truly making sure that what we're doing is solving problems, and overall making a better world class user experience. At this point it's building out the interactions, documenting by either google docs, or a workflow map depending on how complex the interactions are. Then I go back to the internal and external user testing to validate my designs. Then move it along to high-fidelity visual designs followed by more user validation. After all this work has been completed it needs to be documented so others can use it, or learn from it. I'll then work closely with front and back end engineers to make sure all is on par with the outcome we desired. We then move to testing environments to polish and refine our work. Then onto release where we can AB test or throttle a certain amount of users to start using what we built. Throughout the entire life cycle of a project, there is constant iteration and new discoveries that we'll have to adapt to. New insights that pour in that we need to evaluate and understand. This is the process I strive to utilize but it's not always this smooth. Timelines and compromises will be made from all parties to help push the project to success.
If you have any questions feel free to message me.