I usually like to work with at least these three UX inputs in a project, so far this approach was enough fair to start with, but at the same time in some other projects the needed of more inputs was an addition value in the success chain. Anyways, if you start with these three, you’re in the right way.
A fundamental input in the UX design process is a solid understanding of the underlying business objectives.
- What are you trying to accomplish?
- Do you want to sell products or services?
- Are you improving a process?
- There’s an issue in current digital channels impacting customers convertions?
- Provide customer information to reduce phone calls?
- Engage and entertain users?
- A clear definition of the business goals and objectives is the first and most critical step.
- Want to improve the transformation process from visitor to a fan?
After you define these objectives, you also have to determine how you will measure success.
It’s critical to define the key success metrics, or key performance indicators (KPIs), at the start of the project because they will impact all other decisions and actions you make throughout the process.
These metrics also ensure that the final experience aligns with your original goals.
In addition, though, you consider other operational business objectives, which may be also important.
- How will the experience be maintained?
- Who will update the content?
- Who will define the content strategy in future?
- How will the experience be modified and enhanced over time?
In many of the projects I’ve worked, was pretty important to consider the competitive landscape:
- Who else possesses a similar product or service that is on the market? is there something similar?
- Has he built a user experience to promote, sell, or support his product or service?
- How mature is that UX?
- What can you learn from assessing the UX of that service?
- What do you like?
- What features or content may be missing?
- Is any specific feature you considered as an differentiator?
Assessing your competition means that you assess what others in the same industry are doing, especially around any types of user interaction they create.
Given the iterative nature of digital design, where websites and applications are continually updated and enhanced, it’s particularly useful to take a deep look at any similar experiences (products or services) that exist on the market.
You can learn a lot from quickly assessing these services, and avoid many of the UX pitfalls that are common in design today.
This input includes which technology is necessary to support the solution you are building.
- Which technology is necessary to create, produce, publish, and maintain your user experience?
- Where will the user experience exist (for instance, a website on mobile, tablet, and desktop)?
- What technology will support you solution?
- What’s customer current technology architecture? (As-Is)
- What will be future customer technology architecture? (To-Be)
- Is there any specific consideration about Technoogy Stack to take in care?
Taking time to assess the underlying technology architecture will ensure that the design choices you make throughout the process will be supported by the underlying technology.
Assuming we’re working in a digital product, some of the more simple technology questions that need to be addressed are:
- Which web browsers will be supported?
- Will the solution be used via mobile devices, and if so, which operating systems will be supported (Apple, Android, and so forth)?
- Any specific device or device feature to be considered?
If you are designing an e-commerce or more complex solution, you need to explore additional areas, including:
- Is there a system to publish and manage content, such as a content management system?
- If you are selling products, how will the product catalog be updated and maintained?
- How will you process payments?
- Will the website or app require a user to register or authenticate herself?
These topics can get very technical, very quickly, so it is critical for all team members on a UX project to have a common understanding of the technologies that will enable the experience.
They play a critical role in the eventual experience.