My Design Process
Research Objectives and Scope
The first step in my design process is to clearly define the research objectives, scope, and any limitations. This ensures that the project has a clear direction and that all stakeholders are aligned on the goals and expectations.
Understanding Stakeholders
Next, I focus on understanding the stakeholders, including their demographics, needs, fears, challenges, and motivations. I also highlight any power dynamics and trust issues that may impact the research. This comprehensive understanding helps in designing research activities that are relevant and inclusive.
Research Planning
Based on the research objectives and scope, and considering the stage of the product/solution design process, I plan the research. I define what we know and what we need to know, and choose the appropriate methods accordingly. Collaboration is key at this stage, as sharing ideas with team members can provide valuable feedback and insights.
Participant Recruitment and Existing Data
I research where participants are active and recruit from those areas. I also look for any existing data that may be helpful, as it can provide valuable context and save time. For essential research activities that can be done in a limited time, I conduct pilot sessions to ensure success.
Implementing Research Activities
When implementing research activities, I try to include team members from other relevant departments, such as designers or software developers, especially if the data is highly relevant to them. This way, they see the findings first-hand, we gain another perspective, they help in the note taking, and we ensures nothing is lost in translation. I capture as much data as possible in various ways to identify trends and minimise data loss due to technical errors. The data is then cleaned and analysed, balancing time constraints with the need to extract meaningful insights.
Data Analysis and Reporting
I discuss my early data analysis findings with partners and colleagues to get feedback on my interpretations. I then build my data analysis report, translating the findings into actionable insights for different project teams, such as software engineers, product managers, and designers. I use a combination of visualisation and clear language to ensure the findings are well understood and aligned with project goals and KPIs. This approach minimises defensiveness and creates a solid foundation for any necessary negotiations.
Suggesting Solutions and Designs
In suggesting solutions, ideas, and designs, I focus primarily on the users. I don't take technology for granted as the first and only solution. Instead, I choose technology implementations and design ideas that address the relevant challenges while adhering to well-known design standards and guidelines. Simplicity is often the answer to the biggest problems. With my software development background, I ensure that the designs and scenarios are dynamic enough to accommodate future changes and expansions with minimal technical work.
This section outlines the design model I typically employ in my various projects. This model, known as the CRIT model.
The CRIT stands for Complexity, Relevance, Involvement, and Trust.
The CRIT stands for Complexity, Relevance, Involvement, and Trust.
As illustrated in the figure above, when the dynamics of complexity (problem definition) are thoroughly defined, researched, and understood, the design process activities and resulting systems become contextually relevant.
This relevance fosters increased trust and involvement among stakeholders in both the design process and the final systems. Moreover, stakeholder involvement and trust not only result from relevance but also play a crucial role in achieving a comprehensive understanding of contextual complexity. Thus, trust and involvement are both outcomes of relevance and essential components for grasping the intricacies of contextual complexity.
This relevance fosters increased trust and involvement among stakeholders in both the design process and the final systems. Moreover, stakeholder involvement and trust not only result from relevance but also play a crucial role in achieving a comprehensive understanding of contextual complexity. Thus, trust and involvement are both outcomes of relevance and essential components for grasping the intricacies of contextual complexity.