Day#207: My process for a project

Day#207: My process for a project

I was recently asked what my process would be on a new check out system for an interview, I really felt like I didn’t answer the questions as well as I could have and for this reason I have decided to lay out a very basic step by step process of how I would handle the project in general. Let me know what you think!

Discuss with stakeholders

This is where you sit down with everyone that is involved with the project and understand the business goals and ideas that people have. Dependent on the setting, but often these are not ideation workshops, they are more similar to a meet and greet with introductions and getting to know the project history and future projection. Discussing deadline goals can be done here, which can be renegotiated when the outcomes and features are decided on in the next phase

Ideation sessions

Here Ideation sessions can be held to discuss ideas, there are many methods for conducting ideation sessions and dependent on the company culture, activities can be used that can help everyone come to a consensus on features and outcomes. It is so important to involve developers and designers as well as business in these meetings.

Creating user journeys

This is where the company objectives have been outlined and the features and main product has been defined and understood by everyone working on the project. Here creating a user journey will help with keeping the flow on track, it will also help to match up when creating wire-frames, and setting tasks for usability testing.

Research with potential or current users (dependent on the project)

This is research that is done with users to ascertain their lives, you can find out income brackets and their likes and dislikes. You will then be looking at similarities and create personas from this information, the personas help to revert back to, when changes are being considered etc. Understanding if the user is tech savvy or if they are more novice on tech products will help you make decisions on assisting the user interface designers in icon development as well as many other facets of the design and development process of the project

Wire-framing and prototyping

This is where wire-framing is done, start with low fidelity prototypes and again share with stakeholders and developers, this will help with discussing time that will need to be allocated to developers for ensuring tasks can be completed. Low fidelity prototypes can also be have some corridor testing with colleagues to help ascertain shortfalls of the process that users will have to go through early.

Presenting of low fidelity prototypes

This is where low fidelity prototypes which have gone through some testing is presented to developers, business and stakeholders. Dependent on the company culture and procedure you may have to do it separately, but together is always best then everyone has a chance to air their concerns together and discuss on ways to move forward together as well. This is where changes to the layout can occur, having the user journey presented first with a clear outline of the user goals with the mention of the personas will help with identifying that the project s on the right track

Creating high fidelity prototypes

This can be done with a number of UX tools ranging from Sketch, to Axure RP. Creating a high fidelity prototype instead of going straight to development will save the company money and time by testing on a prototype instead of investing resources into a final product that has not been tested etc.

Presenting the Hi Fi Prototype to stakeholders etc

As you can see there is a lot of communication that needs to be had with everyone involved on the project. I have learnt this from past mistakes, including everyone early makes everyone feel involved and valued. Also you ensure that all the needs are dealt with instead of creating the product and then having to make more changes because people were only involved at a later stage.

Usability testing of Hi Fi prototypes

This is where you can run usability testing, speak with the company if they are okay with you contacting existing groups of users that they perhaps have information for. You can create a usability test plan and ensure you are organised for asking users a range of questions of how the check out system works for them. Making sure to not have questions with a hint of the answer you want ie “Do you like our new check out system?” haha just don’t do that! There is a lot of steps in this topic from planning the usability test to actually carrying it out and collecting the data there after, I will do more posts on this topic in particular in the next few weeks. Here you can conduct A/B testing with users, check out my post on various platforms for usability testing here

Briefing of other teams

Here you could be tasked with briefing design and development with the next steps of the project. Understanding the time it will take each team to recreate the project needs to be taken under consideration and consistently keeping up with weekly sprints to monitor progress and shortfalls of the project moving forward will be advantageous for the project success.

Going live

This should not be a stressful time with all the planning and preparation that has gone into the project, but it sometimes still is.Work on keeping to deadlines and maintain contact with stakeholders and everyone else involved if deadlines change

Iterate iterate iterate!!!

This is where the project has gone live, but usability testing does not stop above where I indicated. Consistent testing can happen with users to see if patterns form or change on the process. Constantly revising the end product will ensure that it is the best possible experience for users

To end off, I really wish I had said even half of everything I discussed here. Sometimes I think of all this in my head but then don’t say it aloud, the curse of an introvert I suppose. Anyway happy researching until next time Uxers!

Bye for now

2 Replies to “Day#207: My process for a project”

  1. Genuinely excellent process, but can I ask where the user research is in the process. You may have just left this out, but it is really important not to take the business’s goals as gospel, They are riddled with biases and they are not the user. Also, they are regularly at odds with what the business says they want to deliver to the user.

    1. Hi Sean, thanks for reaching out! This blog has been a journey of me documenting my learning, processes, reviews and goals etc. I do think this particular post needs to be updated with more in depth details on User Research, I think the little reference to personas and usability testing can certainly be improved and described in WAY more detail. I’ve since been working on my knowledge, and learning a lot so most of my earlier posts are cringe worthy haha! This has inspired me to do a newer more refined post on my updated general process for projects. Thanks again for the comment, much appreciated 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *