2 Methods That Could Give Structure to Your UX Research

In essence, research is an organized and systematic way of finding answers of questions (Tabish, 2013).  Organized and systematic means you’ll have a set of rules and structure when preparing and conducting your research. But the dynamic nature of a research process could send you into a long winding journey that sometimes obscures the initial structure and system you’ve set up. 

This is especially true when it comes to qualitative research. Unlike quantitative research where you have clear numbers that could give measurement, qualitative have words and opinions which could be troublesome to measure. It gets harder when you have a large pool of data to deal with. That’s when structure and organized documentation are even more important. 

So, whether you’re an old-timer researcher looking for inspiration, or a rookie researcher looking for a place to start, here are 2 methods that we think can help you reinforce your research structure.  

1. Thematic Analysis

Thematic analysis is “a method for identifying, analyzing, and reporting patterns (themes) within data” (Braun & Clarke, 2006). It’s a qualitative approach commonly used to process text, interview or transcripts. It helps you focus on the theme and meaning across the data, which will help you see the overall picture of what’s going on.

Thematic analysis can be helpful when you deal with large numbers of qualitative data because it helps you to divide it into smaller thematic chunks which are easier to digest. It is also a good approach to use when you want to find user’ opinion or view from an interview result. 

It is especially useful if you’re:

  • New to qualitative research
  • Wants to find pattern or trend in data
  • You need a system that involves visual aids

In general, thematic analysis can be split into 3 main steps: Data Coding, Identifying Key Theme, and Data Interpretation. 

  • Data Coding
    Simply put, data coding is a process of labeling or “coding” important parts of data. Whether you create a set of code beforehand or during the analysis, it’s all about assigning labels or code that represents the information that are relevant to the goal of your research. Let’s see an example of the interview snippet below and how we could assign code to some interesting information. 
Transcript and coding example

In the snippet above, we’ve marked some statements that are relevant to our research. Each statement corresponds to different code. For example, we code “Hard to find the menu that I want” with “Negative Page Experience”. And as we go through the whole transcript, we might add more codes if there is any information that we see relevant or interesting. Don’t forget to create a codebook so you can keep track of all the codes you’ve used. 

  • Identifying Key Theme 
    Once you’re done with coding, now it’s time to gather all the code and group them into themes. Themes are generally broader than codes but it’s a powerful way to spot trends and patterns, or to get the gist of what’s important or urgent. It’s also a way to sort your codes, to see if there are codes that are actually irrelevant at the end of the day. 
Theme example
  • Data Interpretation
    Lastly, once you have all your themes, you can start writing down your interpretation. You can also try to group them into a feasible action plan; which themes need to be prioritized and which themes could still wait on the sideline. In short, this step will depend on the type and the goals of your research.  

2. Repository for Data Organization & Documentation

Your research structure will only be as strong as your documentation. Imagine going through a lengthy research process just to find yourself fumbling for important information at the end of the stage due to bad documentation. How can a repository help reinforce your research structure, you wonder?

  • It gives a centralized documentation where all related parties could easily access relevant documents or even get the general view of the research. You can put all the related previous research from various projects. It will save you time, no more digging around tenth of folders just to find one research document. 
  • It serves as a guideline, a document that helps you get back on track in the middle of a long research process. You can relook at your goal or at all the important points that need to be addressed in your final design. 
  • Can act as a reliable source of information for many stakeholders and during deck-making. No more misinformation and say hello to a smooth decking process. 

What to put inside the repository? Good question. 

We know it’s lame, but it depends on your needs and your working culture. Who are you working with? Who will need what? What kind of problems do you want to resolve with this repository? At the end of the day, a repository should be a flexible but centralized source of information.

We’ll give you a glimpse of possible sections that you can add to your repository. 

  • Documentation and tools : Maybe a link to a client’s brief or previous research deck. It’s a section that includes all the documents and tools that you’ll find crucial for your research process. 
  • We call it the “Bear in Mind” section : It’s where you plop down all the information that could serve as your guideline. It could be a one-liner brief, project/research objective, previous insight or evidence, or even your problem statement. 
  • Design Checklist : It’s basically a table where you list down all the requirements that have to be met in your design with the approach you want to take based on research you’ve done. 
Design checklist example

At the end of the day, research is a dynamic process and there are tons of methods you can try out there. What we discuss here were just a few that we think could help you start your research with a proper structure and documentation; thematic analysis as a way to help you spot patterns in a more organized way and a repository that helps you as a guideline and a centralized source of information. 

The Art of Iterate’s #MeaningfulUX


Category: Design

Ellipse 51

Clara, Rifqi, Mahisi — November 2021

A purpose is a guiding principle and a fundamental belief that explains the reason why we do what we do. We believe that everything that we create should be driven by a strong one. Therefore, we believe in #MeaningfulUX.

These past couple of years have been known for many things, and the highlight of it all is the ongoing pandemic that is happening around the world. However, it’s a different story with our industry. Everything is now about digital transformation.

Being in the business, we gathered, we brainstormed, we made coffee, we ordered food, we thought hard and deep and we realized what we started in 2009 has now grown and turned into something bigger, and that the world is evolving.

So with everything going on in today’s world, we asked ourselves, “What can we do to push through? What value defines us wholly?”

You see, building a presence in digital is more than just about making innovation; it’s making continuous improvements, it’s creating a meaningful experience. And that, my friends, is the idea that we hold dearly at Iterate.

Bringing #MeaningfulUX to Make Everyone’s Life Better

To have meaning has always been about the purpose of humankind. So to represent that feeling, we’ve created #MeaningfulUX to give a sense of what Iterate is trying to bring to the table. Here we do not only want to help users by creating products, but we also want to reach a point where there’s an emotional significance between our works and the users; because they feel empowered and enlightened.

#MeaningfulUX is a value that shows we can always make an impact and help everyone to have a better life. It’s an effort to fit technology into people’s lives so effortlessly that empowers them to focus on the bigger things in life. We’re proud to introduce #MeaningfulUX and how it has become the value within each team of the Iterate family.

Building digital presence is more than just about making innovation, but also creating a meaningful experience
and continuous improvements.

1. #MeaningfulUX for Our Project Management Team

Within Iterate’s Project Management team, to attain #MeaningfulUX in the work that PMs do, we have to be equipped with 4C.


A manner in which team members must have the courage to guide both client and production to cater to user needs. It requires a high level of leadership skill to show that PM can conduct and lead all internal and external meetings.


Where collaboration among PM, Clients, and Production happens and is a vital point in producing certain outputs, such as the running of internal meetings and workshops in a project, and the making of project timeline which has been agreed upon by each team at Iterate. This also requires PM to completely understand what internal and external users need.

A team attitude to understand user needs and stay committed to the project’s objectives. It’s important to be an effective facilitator in charge of the workshop, or meetings in accordance with the ground rules of the Project Management division.
Continous Improvement
Learning process needs to be conducted in the weekly PM meeting to define learning from each project especially on technical sights, to give us insights into what we can actually improve continuously for current and for future projects.

2. #MeaningfulUX for UXD Team

For the UXD team, #MeaningfulUX is defined as a combination of great product design and a delightful user experience. Hence, we believe in PICTure.

3. #MeaningfulUX for Tech Team

Meanwhile, as for the Tech team, we have what we call iURL to define our version of #MeaningfulUX that we ought to implement in our works.

In which developers gotta stay up to date and implement the latest and most fitting technologies trends in our products. By being innovative, the Tech team is expected to at least have a growing list of the latest technologies we’ll be using, and it’s important to understand the users’ needs regarding the suitable technology for them.
User Driven
Developers need to have extensive knowledge within the scope of implementing technology in a project or a product. Therefore, having a comprehensive understanding of users’ pain points and tech insights is expected, so we can share it all with all teams across divisions since it is crucial in the making of a design and/or product.
The ability to create a reliable application and the ability to protect the privacy and the safety of users’ data is what robust is all about. In realizing a #MeaningfulUX, developers have to deliver, cope with errors during execution and handle erroneous input, and ultimately solve the problems.
Ensuring that the product or application we create is light when being used. This can be done by utilising frameworks or applying clean code so that the program code is easy to read, understand, and be traced for efficiency purposes. Thus, it’s important to make sure the deliverables have been validated with the relevant measurement tools.

4. #MeaningfulUX for Elevate Team

Last but not least, Iterate’s Elevate Team has DISC to embody #MeaningfulUX in every project or product we’re working on.

In the end, to be in a ‘place’ where the result of the design process elevates us — Iterate, we have to go through a journey. To build a relationship with the users emotionally and at the same time opening doors conveniently for everyone, also requires thorough awareness, commitment, and passion. And we feel like nothing can express Iterate more profoundly than the value in #MeaningfulUX that we try to instill in every work we’re doing — the belief that #MeaningfulUX can take us in motion.