Master Design Thinking Tools

Still image scanning is an observational method based on taking regular photographs of situations, environments, objects, and people without interfering with the unfolding moment. The goal is to build a visual archive that reveals recurring patterns and differences between what is supposed to happen and what actually happens. It is useful when it is difficult to stay in the field for a long time or when we need visual evidence to share with the team later.

1. Determine the situations and places to be documented.
2. Take still photos according to a clear temporal or spatial plan.
3. Arrange and categorize the pictures according to context and activities.
4. Analyze visual patterns and extract unmet needs.

Example: The service center team takes hourly pictures of the waiting hall, employee offices, and self-service machines over the course of a week, then arranges them chronologically to discover that crowding is related to the moment a batch of morning transactions arrives, not to the total number of customers, so it redistributes windows and tasks accordingly.

Tip: Make your shooting plan systematic (fixed time/place/angle) and do not rely on random images; Then review the series with the team looking for patterns, not just dramatic shots, and ensure approvals and privacy before any capture.

Remote monitoring is a model that parallels business ethnography while maintaining an objective distance: the team observes behavior in context without attracting attention and without interfering. They are used to record what people do and do not do, who is present and absent, and the interactions between people and systems. The POEMS (People, Objects, Environments, Messages, Services) framework helps to comprehensively observe rather than strictly categorize them.

1. Go to the target environment and pretend as a customer.
2. Monitor people and behaviors without intruding.
3. Use the POEMS (People, Objects, Environments, Messages, Services) framework for monitoring.
4. Analyze observations to derive ideas about motivations.

Example: A banking team poses as customers in branches and observes the use of ATMs, queues and staff interaction without directly asking first, then documents silent frustrations such as repeated retries or whispered requests for help, to formulate hypotheses that are later tested with contextual interviews.

Tip: Be objective: record behavior before interpreting, and go beyond superficial observations to patterns and transitions between activities. Do not intervene too early and spoil the context. Later combine observation with inquiry to understand causality.

Thinking about what is missing is a complementary concept to observation and questioning that directs the researcher to ask about what is absent, not just what is present: Who was supposed to exist? What was left unsaid or done? What tool, time or place was expected and did not appear? The goal is to uncover non-specific needs that customers do not express because they are accustomed to their absence or do not imagine their alternatives.

1. Ask: Who are the people who are not there and were expected to be there?
2. What action was not taken that could have been taken?
3. What statements are not made?
4. Keep asking questions down to the root cause of the absence.

Example: In a hospital, it was noted that elderly people were absent from self-service kiosks despite their availability. By asking the missing questions, it became clear that the interface requires digital knowledge and a long pause without a seat or companion, so the insight turned into design requirements for accessibility, not just “awareness of using the device.”

Tip: Continue the series of absence questions to the root cause, and incorporate them during the field observation, not just afterward. The biggest opportunities for innovation are often in what people avoid or don't even see in the landscape.

Behavioral Implications Close examination of tools and environments to infer lifestyles, customs, rituals, values, and priorities without relying solely on what people say about themselves. The observer studies the arrangement, adjustments to instruments, frequency locations, and usage patterns as psychographic clues that help understand what actually motivates the user.

1. Choose the user's environment or workspace.
2. Examine the props, general order, places, and costume styles.
3. Draw clues about people's habits and priorities.
4. Use inferences to understand user behavioral drivers.

Example: A study of donors' home offices revealed stacks of unsorted papers and sticky notes on a screen; The team concluded that a donation app should capture intent immediately and delay sorting, not impose a complex administrative model from the first screen.

Tip: Sometimes the environment speaks truer than words; Pay attention to the user's modifications to his tools (temporary solutions, labels, shortcuts), as they are signs of unmet needs. Link each effect to a testable hypothesis.

Spatial behavior mapping studies how people occupy space by tracking static locations and dynamic movement over a specific time frame, then transforms this into paths, traffic patterns, and behavioral zones. It is useful in designing physical environments, wayfinding systems, and preparing spaces for desired behavior.

1. Determine the area or environment to be studied.
2. Track people's locations and movements over a time frame.
3. Drawing movement paths and specific traffic patterns.
4. Identify areas that are exposed to specific spatial behaviors to improve the design.

Example: At a retail store the team tracked shoppers' routes for rush hour and mapped congestion and avoidance zones; Complementary products were redistributed on the actual paths rather than on the theoretical scheme, and the questions of 'Where can I find...?' were reduced. Improved purchase completion time.

Tip: Establish a time frame and sufficient sample before generalizing, and distinguish between forced movement (congestion/closure) and voluntary movement. Link the map to concrete design decisions for the space, not just a general description.

Business ethnography is an in-depth field study of customer behavior in their real context over relatively extended periods, combining observation and light immersion to understand rituals, language, tools, relationships and values. It produces cultural and behavioral insights that are difficult to obtain by questionnaire or laboratory interview alone, and feeds into the stages of empathy, identification, and point of view.

1. Define your target user segment and environment.
2. Spend enough time in the field observing and interacting lightly.
3. Document rituals, language, tools, and relationships.
4. Turn observations into usable design insights.

Example: Accompanying delivery drivers for several shifts revealed that 'application delay' is not the only problem; Rather, the customer's instructions conflict with the restaurant's policies and the pressure of real-time evaluation. The team reframed the problem around managing multi-party expectations, not just map speed.

Tip: Allow enough time for recurring context and do not limit it to one visit. Trust the language of the respondents, separate observation from interpretation, then transform insights into needs and hypotheses before jumping to solutions.

Digital ethnography is a systematic observation of users' behavior within digital environments: websites, applications, communities, and support paths. It looks at language, posts, click paths, abandonment points and social interaction to uncover needs and barriers as they appear in online life, while respecting ethics and privacy.

1. Identify relevant digital platforms and channels.
2. Monitor interactions, posts, and usage paths.
3. Record patterns, barriers, and language used.
4. Connect digital insights to real-world design needs.

Example: An analysis of the comments on the Hukoomi app and the support forum for a month showed repetition of the words 'Take me back to the beginning' after uploading an incorrect attachment. An improvement was built that saves a draft and displays file requirements before uploading, and support tickets related to this issue have been reduced.

Tip: Observe only stated public behavior, and do not invade private spaces. Link digital insights to real-life observation or interview for verification; What is written online may be exaggerated or lacking in context.

Contextual inquiry or shadowing Approaching people to observe them closely with their consent during their real routine: The researcher shadows the user, notes interactions and natural language, and engages in routine conversation to build trust and extract stories and motivations. It differs from remote observation in the depth of integration, and from the office interview in that the field context remains.

1. Obtain the permission and cooperation of the subjects of the study.
2. Shadowing and directly observing their behaviors closely.
3. Engage with them in routine conversation to build trust.
4. Extract stories about their experiences to explore motivations.

Example: A researcher accompanies a nurse on his tour of the hospital and notices his frequent interruptions to re-enter data into separate devices. The insight turns to the problem of designing a mobile workstation and information flow that is not 'training for speed'.

Tip: Familiarity and trust are a condition for the subject not to change his behavior. Get clear permission, start observing before asking too many questions, and document momentary obstacles that people don't remember later in the interview.

Cultural probes are task packages or tools sent to participants to record their lives, rituals and feelings through photographs, diaries and short exercises. It reveals values ​​and behaviors in moments that the researcher cannot reach through direct observation, and expands the sample of contexts at a lower field cost while preserving the voice of the user.

1. Design a simple task package (pictures, diary, questions).
2. Distribute it to participants for a specified period.
3. Collect outputs and discuss them with participants.
4. Extract cultural patterns and implicit needs.

Example: Families were sent a package (camera + notebook) to document morning routines associated with medical appointments; The photos revealed the chaos of preparing documents before discharge, so a digital checklist was designed to be completed the night before, not at the clinic’s door.

Tip: Keep tasks short, fun, and time-bound so participants will commit. Review the outputs with them to clarify the meaning; Don't interpret photos alone in isolation from their story.

A day in the life method traces a representative day or routine of the user from start to finish to understand the sequence of activities, tools, times, waiting points, frustration, and satisfaction. Empathy shifts from isolated moments to a coherent timeline that reveals where effort is wasted and where critical decisions are made.

1. Agree with the interviewee on a representative day for observation or documentation.
2. Record activities, times, and tools used.
3. Identify moments of frustration, satisfaction, and waiting.
4. Summarize the day as a journey that reveals opportunities for improvement.

Example: Tracking an HR employee's day from opening mail to closing orders revealed that an entire hour is spent every day copying data between two systems. The problem was redefined as systems integration before any single model interface improvement.

Tip: Choose a normal day, not an exceptional one, and agree on the level of documentation in advance (note/diary/shadow). Summarize the day as a journey with stages and peak moments before generating solutions.

Tours accompany the respondent on a guided tour of the spaces and activities affected by the problem, where he explains his environment while the team explores the objects, interactions, and implicit values ​​associated with the place. The client's presence in the context during the explanation activates his memory and real emotions better than description from a distance.

1. Arranging a field tour with the user within his relevant environment.
2. Exploring and examining space and the objects it interacts with.
3. Listening to the user's point of view as he explains his environment.
4. Understand the implicit values ​​and intentions associated with place.

Example: A tour with a warehouse employee between the shelves showed that the difficulty of accessing some materials resulted from the height of the storage and the conflicting paths of the crane, not from 'weak personal organization' as was assumed internally; The solution changed to replanning the height and movement paths.

Tip: Let the user lead the tour and talk; Ask about meaning, not just inventory. Picture or draw breakpoints and emotions, and ask for examples of the last time a problem occurred in each area.

Time-lapse photography captures changing behavior, movement, and density in a given environment at a higher speed than continuous eye observation. It is used to detect peak waves, downtimes, and occupancy patterns that are not apparent in a short visit, turning clips into design notes for a space or operation.

1. Fix the camera at an angle that covers the target area.
2. Set the shooting interval.
3. Review clips and extract traffic and crowding patterns.
4. Turn feedback into design recommendations for your space or service.

Example: A fixed camera on a hospital entrance for an entire day showed a sudden peak simultaneous with multiple clinic appointments; Early opening of some windows was rescheduled and ground routing was added ahead of the bottleneck at reception.

Tip: Get legal and ethical approvals first; Logging may capture sensitive data. Fix the angle and time interval, and analyze by patterns, not by individual scenes.

Depicting relationships of influence, support, communication, and dependence among people and groups associated with the problem or service. It reveals the intermediaries, gaps, and informal channels that actually move the decision away from the stated organizational structure, and directs who should be interviewed or involved in the design.

1. Identify entities and individuals relevant to the situation.
2. Draw connections (communication, influence, dependence, conflict).
3. Analyze the density of relationships, gaps, and mediators.
4. Use the map to guide who you meet and whom you involve in the design.

Example: The stakeholder map of the elderly care service showed that the decision to subscribe goes through the son/daughter more than the beneficiary himself, and that the neighborhood WhatsApp group is a stronger source of trust than the official website. The message and awareness channels were redesigned accordingly.

Tip: Don't be satisfied with the formal structure; Ask 'Who do you turn to when things go wrong?' Update the map after each interview, and use it to select the research sample, not just as an aesthetic drawing.

Workarounds Detect unintended or altered uses of tools and processes when users compensate for system shortcomings with their own paths (including desire lines or paths). Each workaround is a clear indication of an unmet need and an innovation opportunity to address the root of the deficiency rather than punish the behavior.

1. Monitor the customer while using the product.
2. Search for paths of desire or external aids.
3. Understand why the user had to make this adjustment.
4. Convert these shortcomings into features in the new design.

Example: Observing employees sending files via external chat applications because the business system is slow with attachments; Instead of just blocking the app, a quick sharing feature was built into the system with clear permissions, so leakage was reduced and compliance increased.

Tip: Put the alternative solution under the microscope: What does it accomplish? Why? What fails in the official tool? Turn shortcomings into feature requirements, and don't just block the alternative path.

Monitor customers' self-invented modifications and innovations to products or procedures to fill need gaps. Customer penetration is valuable raw material for innovation because it is experienced in reality and pays the cost of effort to solve its problem; The team's mission is to understand the motivation and turn it into a formal, scalable solution.

1. Monitor the real usage of the product or service.
2. Document any modification or hack created by the user.
3. Understand the motivation and need behind this hack.
4. Turn the hack into an official feature opportunity in the new solution.

Example: Users modify official Excel templates because the system does not support their daily reports; The team collected these 'hacked' templates and extracted the actual fields required to build a native report screen that eliminated manual export.

Tip: Collect breakthroughs without judgement, and ask for the story of the last time they needed adjusting. Distinguish between a popular breakthrough worthy of a product and a rare individual breakthrough.

Contextual interviews are direct interviews conducted with the user within the context of an actual situation of interest, not in an isolated office. The researcher first collects observation of behavior and body language and then interviews about what happened and why at the same moment. The environment stimulates memory and emotions and reveals gaps in expectations versus actual outcomes and alternative solutions.

1. Go out into the field and be in the user's real environment.
2. First observe the subjects and record behaviors and body language.
3. Conduct the interview in the same context about what they did and why.
4. Focus on the observational depth of the experience.

Example: Interviewing passengers inside the arrivals hall while waiting for bags revealed tension related to the ambiguity of the belt time, not just the length of the wait alone. A real-time status panel and alerts have been added, improving the sense of control even before the process itself is accelerated.

Tip: Don't bring a client into your office if the context is essential. Observe first and then ask about specific events, not generalities, and carefully incorporate questions of causality into the field dialogue.

Focus groups Invite a small group of users to have a guided dialogue about past experiences with a product or service. It is a form of group empathy interviewing that elicits stories, needs, motivations, and values, and may generate ideas through the interaction of individuals. According to the evidence, it alone is not sufficient to replace observation and contextual interviews, but rather enriches it after building hypotheses.

1. Define the goal and discussion questions in advance.
2. Choose a relatively homogeneous group (6–8 people).
3. Facilitate dialogue without imposing answers.
4. Summarize patterns and differences after the session.

Example: A session with parents about electronic school registration showed that the fear of 'losing a seat' drives them to send applications repeatedly; A clear confirmation message and consistent request status are designed to reduce duplicate requests and support calls.

Tip: Make sure everyone speaks, not just the boldest, and beware of groupthink and the tendency to agree. Use them to enrich observation, not replace it, and do not test solutions with direct questions that lead to answers.

Having people sketch their perception of a particular activity or experience and then compare the sketches to reveal different mental models and prioritization. Technical quality is not important; what matters is how the customer arranges the steps and what they inflate or omit, so that the design covers multiple styles rather than one that the team assumes.

1. Ask respondents to sketch the steps or path of their experiment.
2. Collect different drawings from multiple users.
3. Analyze the differences in how they conceptualize.
4. Use graphics to ensure all thinking styles are covered when designing.

Example: Asking those dealing with a government department to draw up the steps of the transaction from start to finish. Many people drew the 'inquiry about what is missing' as a separate stage that was not in the entity's plan, so a path of clarity was added to the requirements before payment.

Tip: Ask the silent drawing first, then the explanation, and compare the differences between the participants. Look for omitted or exaggerated steps, as they are the keys to friction.

A collaborative examination method in which clients are asked to map multiple aspects of their situation and abstract phenomena: relationships, systems, pressures, and extremities. It reveals mental models, biases, and how complex reality is filtered from a person's perspective, and builds deeper empathy within the team through shared visual insights.

1. Provide the user with space and drawing tools.
2. Ask him to draw a map of the systems or people related to his problem.
3. Analyze the client's mental models and biases through drawing.
4. Share insights with the team to build empathy.

Example: A teacher was asked to draw his relationship with the administration, students, curriculum, and parents; The 'multiplicity of conflicting guidance channels' emerged as the center of pressure, not the density of quotas alone, so the solution initiative turned to unifying guidance before adding new tools.

Tip: Provide space and simple tools, and ask that symbols be explained rather than assumed. Use the diagram to share insights with the team, not as a finished work of art.

Build a shared mind map with users or the team to break down a complex topic and show connections, assumptions, and branches all at once. The oral discussion is transformed into a visual structure that can be edited collectively and guides subsequent research or idea generation steps.

1. Place the central subject in the middle.
2. Invite participants to add branches and ideas freely.
3. Collect links and categorize topics.
4. Use the map to guide your research or generate ideas.

Example: With call center employees, a map of the elements of the complaint experience was drawn; The 'Re-explain the issue to each section' branch was found to be larger than the 'Wait Time' branch, so cross-system reporting was redesigned as a priority.

Tip: Have participants write themselves on the map so that the facilitator's vision does not dominate. Stop expanding when recurring patterns appear, and turn branches into research questions or opportunities.

An activity in which participants place pictures, words, or clippings that express their feelings, preferences, and experience, and then discuss the reason for the choice. It elicits non-verbal meanings and emotional values ​​that may not appear in direct questions, and opens a richer dialogue about identity and perceived experience.

1. Provide various visual materials (pictures, words, scraps).
2. Ask participants to build a painting that expresses their experience.
3. Discuss why you chose each item.
4. Extract emotional and value themes.

Example: Patients were asked to construct a picture of what it was like to wait in the clinic; Images of 'the unknown' and 'loss of control' were more frequent than 'long time', so visual status updates and occupancy options were designed for time rather than just seat increases.

Tip: The goal is the story behind each clipping, not the aesthetics of the painting. Prepare diverse, culturally neutral materials, and ask 'Why this?' After construction, not during.

Invite participants to bring or display personal objects linked to the context and explain their story to infer values, customs, priorities and symbols. Objects act as narrative stimuli that open deeper layers of meaning than abstract questions about preferences.

1. Ask to bring objects related to the context studied.
2. Let the interviewee explain the story of each object.
3. Record meanings, symbols, and motives.
4. Connect insights to the design of the experience or product.

Example: Asking travelers to explain the contents of a carry-on bag revealed frequent 'reassurance' items (medications, copies of documents, multiple chargers) that reflect a fear of losing control; Documentation and shipping reminders have been added to the digital service as part of the pre-trip journey.

Tip: Gently ask when the item was last used and why it is being kept. Don't judge the objects; Transform symbols into needs and jobs to be accomplished.

Free discussion, less restrictive than traditional focus groups, allows participants to direct the dialogue towards what really matters to them without a strict questioning agenda. It is useful for discovering surprising topics and underlying emotions, provided that the facilitator remains present to pick up signals and turn them into research hypotheses.

1. Set a general topic without a strict agenda.
2. Have the facilitator listen and follow the energy of the group.
3. Document emerging topics and emotions.
4. Turn surprises into hypotheses for deeper research.

Example: An open session with users of a financial application entitled 'My relationship with money' without a long list led to a conversation about the shame of asking family, not about the transfer interface; The scope of innovation has shifted towards private and secure financial education within the app.

Tip: Lack of focus is not chaos: prepare a general topic and clear ethique boundaries, follow the energy and not the agenda literally, then document the surprises as hypotheses for field verification.

Involving users as real partners in generating, designing and prototyping solutions, not just as a source of information. Builds shared concepts that are immediately testable, increases ownership of the solution among those who will live it, and requires the team to relinquish some control to user experience.

1. Invite users to a joint design workshop.
2. Provide simple drawing and modeling tools.
3. Build concepts together and test them instantly.
4. Document user contributions and incorporate them into the following template.

Example: A workshop with people with disabilities to design an access path in a government building produced a model with tape and alternative paths within two hours; It revealed angles that did not appear in the engineering drawings and entered directly into the implementation requirements.

Tip: Provide simple drawing and modeling tools, and set a shared decision at the end of the workshop. Clearly document user contributions so that they are not corrupted later during implementation.

Participants were asked to write down their experiences, feelings, and decisions daily for a specified period to capture details that would be forgotten or glossed over in subsequent interviews. It reveals change over time, the daily context, and accumulated pressures in a longitudinal way that is richer than a single encounter.

1. Determine the duration of study and blogging topics.
2. Provide a simple template daily.
3. Review blogs periodically and ask for clarification when needed.
4. Analyze temporal and emotional patterns.

Example: A week's diary for users of a medication delivery service showed that anxiety was concentrated the night before the appointment, not at the time of delivery. Added proactive evening confirmation and reduced morning clutter.

Tip: Reduce the burden of writing with short, daily questions, and review the samples during the period, not just at the end, in order to adjust the guidance if necessary.

A visual version of a diary study in which participants rely on photos and video with short captions to document moments of the experience. It reveals body language, hesitation, and spatial context better than text alone, and provides rich material to share with the team.

1. Decide what to shoot and when.
2. Combine media with short comments.
3. Review the materials with participants to clarify the meaning.
4. Visually extract moments of climax and pain.

Example: Filming moments of using a self-service kiosk over the course of a week and then reviewing them with the user demonstrated a frequency of backing out of the screen after an English error message; The message has been Arabized and the 'What do I do now?' button added.

Tip: Determine what will be filmed and when in advance, and respect privacy. Review the media with participants to clarify the meaning before the team interprets it in isolation.

Study people's perceptions of their own behavior by asking to narrate or show how to perform a task, then comparing that to documented behavior (preferably on video) to extract perception gaps and cognitive dissonance. What people say they do is often different from what they do; This gap is a powerful source of insight.

1. Ask the client to show or tell how to perform a particular task.
2. Record actual behavior (preferably on video).
3. Show the recording to the client and explore the discrepancies with him.
4. Look for points of friction that the customer has forgotten or ignored.

Example: Asking a surgeon about the sterilization steps, then photographing the practice and discussing the differences, revealing small steps that are unconsciously skipped under time pressure; A visual checklist has been redesigned at the point of washing, not just an additional training session.

Tip: Gently view recording as a discovery tool, not an accounting tool. Focus on the forgotten points of friction, and ask what the intention was in that moment.

In-depth interviews—which may be conducted out of context when the field is not possible—focus on stories, feelings, motivations, and perceptions rather than general opinions. According to the guide: open the narrative, stay on specific events, constantly ask why, monitor nonverbals, and pick up on inconsistencies between words and actions.

1. Prepare open-ended questions that focus on experiences, not opinions.
2. Listen more than you speak and leave useful silence.
3. Ask for specific stories, not generalizations.
4. Summarize feelings and needs after the interview.

Example: An interview with a chronic patient about his daily journey with medical follow-up revealed that the greatest pain is 'retelling the story to every specialist'; A journey summary is designed that is shareable among the medical team with the patient's consent.

Tip: Start with stories, not questionnaires, and avoid broad generalities such as 'Tell me about a time...' without any connection to an event. Use silence, and ask why even if you think you understand.

Interview users at both ends of the spectrum (very expert, very novice, or borderline cases) to extract acute needs, advanced tricks, and extreme difficulties. Carefully designed solutions for thoughtful parties often also improve the majority's experience and uncover requirements unseen in the 'average' user.

1. Determine who the extreme users of your context are.
2. Conduct in-depth interviews about their tricks and difficulties.
3. Extract their greatest needs and innovative solutions.
4. Test if their solutions work for the average user.

Example: Interview an employee who processes 50 orders a day and another who uses the system once a month; The first revealed a need for collective shortcuts and the second for a step-by-step guided dialogue, so two interface modes were designed instead of a compromise that would fail with both.

Tip: Define who is an extremist in your context before making a choice. Extract the greatest need and then test whether its solution serves the broader segment without complicating it.

Have team members observe a familiar situation as if they were visitors from another culture, describing what seems strange or illogical without prior explanation. It breaks down professional familiarity and turns assumptions into research questions that uncover new user barriers.

1. Ask the team to describe the scene without prior explanation.
2. Record what seems 'strange' or illogical to an outside visitor.
3. Turn observations into research questions.
4. Test assumptions by observation or interview.

Example: A bank team described its branch as first-time tourists; Notice the absence of a clear indication of 'Where do I start?' There are many nets without an understandable difference. The feedback turned into testing wayfinding and task signage before any awareness campaign.

Tip: Write the strange description before the explanation, then turn each strangeness into a question that can be tested by observation or interview. Involve those outside the department to break expertise bias.

Categorizing customer requirements into essential, performance, and attractive via a functional and reverse questionnaire helps guide development priorities and avoid confusion between what satisfies, what delights, and what is the minimum expected. What is attractive today may become essential tomorrow; Therefore, the evaluation is re-evaluated periodically.

1. Select suggested features.
2. Design a functional and inverse questionnaire.
3. Collect the answers of the target segment.
4. Categorize features and direct resources accordingly.

Example: A government body thought that 'processing speed' was an attractive feature; Kano showed it to be a performance advantage while the attraction was 'real-time transparency of demand status'. Budget was reallocated towards clear tracking while gradually improving speed.

Tip: Model features carefully and test on a representative chip. Don't base your roadmap on the team's assumptions for the Kano category; Let the rating come from users' answers.

A co-creation activity in which clients or the team visually draw ideas and solutions and then discuss the reasons and combine the drawings in successive rounds. It takes thinking out of verbal argument to comparable concepts, and reduces the dominance of the more eloquent in favor of visual ideas.

1. Present the challenge to the participants.
2. Ask to sketch ideas and solutions.
3. Discuss the reasons for each design in the group.
4. Repeat the drawing to incorporate and develop new ideas.

Example: A bank asked customers to draw the ideal branch and they came up with cafe-like drawings with clear waiting areas and semi-private consultations; These elements became design principles for branch rehabilitation.

Tip: Technical skill is not required. Repeat drawing rounds after discussion, integrating recurring elements into a unified visualization before detailing.

A technique from the Toyota system used to go from the surface symptom to the root cause by repeatedly asking 'Why?' Within broader interviews (contextual/empathic) rather than in isolation. According to the guide, basic motives and values ​​are revealed so that symptoms are not treated with a bandage instead of the source of the wound, and are presented gently, not as an interrogation.

1. Ask about a specific situation.
2. When he answers, ask 'Why?'
3. Repeat the question (3-7 times).
4. Stop when you reach the root impulse.

Example: The Why series, with a user who buys expensive coffee every day, went from 'self-reward' to 'feeling valued under work pressure'; Service innovation was directed toward small rituals of appreciation within the work environment, not just price reduction.

Tip: Use it within the context of a broader interview, and repeat 3–7 times until the root need. Change the wording of the question (Why does it matter to you? Why?) and keep the tone of a human conversation.

A planning technique for a matrix of interview questions (who/what/where/when/why/how x tenses and verbs) ranging from simple about the past to more complex about the future. Preparation in advance frees the interlocutor's mind to listen and guide instead of improvising the next question, and helps build a chain that deepens until the moment of realization.

1. Design a question matrix (interrogative object x verb/tense).
2. Start with simple questions (past, who, what).
3. Gradually towards questions of the present and then the future (more complex).
4. Connect the series of questions to get to the deep truth.

Example: Step up with a client: What did you buy yesterday? How did you choose? How would you evaluate your options if the price changed tomorrow? Get to the hidden decision criteria that are not evident in a direct question of 'What is most important to you?'

Tip: Prepare the array before the field, start with the easiest to build security, then work your way up to complexity. Don't read the questions as a list; Use it as a flexible map.

A common form of questioning begins with the most important need, then works its way up with 'why' questions to the common summary need, then goes down with 'how' questions to detail functions and behaviour. 'Why' gives meaningful abstract answers and 'how' gives actionable details; Together they build an integrated picture without restricting the answers to radical thinking.

1. Start by describing a specific behavior or situation.
2. Ask 'how' to break down the steps.
3. Ask 'why' to explore motivations.
4. Cycle between them until the root need becomes clear.

Example: In the payments service: Why do you want instant notification? For reassurance. Why? So I don't follow manually. How do you follow up today?... The 'Close Worry' function unfolded and I designed a live payment status instead of more marketing messages.

Tip: Don't let the 'how' details limit you to only incremental solutions; Translate customer likes/dislikes into jobs and then devise better ways to achieve the result. Pay attention to when you dive into details.

Collecting real-time samples of respondents’ behavior via alerts or short requests during their real day (text/image/quick assessment). It reduces the reliance of research on end-of-day memory, and detects the frequency of behavior and its surrounding context across multiple days.

1. Identify moments or triggers for sampling.
2. Request a quick response (text/image/rating).
3. Collect samples over a period of days.
4. Analyze the frequency and context surrounding the behavior.

Example: Random employee alert: What are you doing now and what is your frustration level? Showed a concentration of frustration when transferring data between two systems in the afternoon; The integration initiative was directed to this time window first.

Tip: Make the response very quickly so as not to burden the respondent’s day, and distribute the samples over different days and times before extracting a generalizable pattern.

Require sequential storytelling of the user's experience as lived to extract emotional details, turning points, and mental order of events. The narrative reveals the plot, conflict, and climax in a richer way than a scattered list of questions, and paves the way for building a user journey based on a true story.

1. Invite the interviewee to tell the story from beginning to end.
2. Ask for sensory and emotional details without interrupting prematurely.
3. Identify peak and breaking moments.
4. Turn narrative into user journey and design insights.

Example: An employee's account of the first day with a new human resources system highlighted the height of frustration when 'not knowing whether the order has arrived or not' after submission; Added instant status message and simple time tracking.

Tip: Do not interrupt the narration early; Ask for sensory and emotional details after the plot is complete. Identify peak and break moments and turn them into design opportunities.

An activity in which participants arrange concepts, features, or contents on cards according to their logic (open or closed) to reveal preferred information structures and natural labels. Differences in sorting between users indicate the need for flexibility in classification or reformulation of labels.

1. Prepare cards with the items you want to organize.
2. Request open sorting or according to specific categories.
3. Note the labels and grouping.
4. Build the information structure according to the patterns of the majority while taking into account the minority.

Example: Sorting the electronic portal service cards as seen by the citizen showed the grouping of “updating data” with “appointments” and not with “personal file” as classified by the entity; The menu has been restructured according to the user's language.

Tip: Watch the labels that participants create for the groups, they are golden for the interface of information. Analyze the patterns of the majority without neglecting an important minority if it is a target segment.

Fast free writing of thoughts and feelings on a topic without self-censorship or correction for a short time. The raw material is taken out before the analysis, the social control that appears in the group dialogue is reduced, and later repetitive thoughts are learned.

1. Set a short time (5-10 minutes).
2. Write without stopping or correcting.
3. Read the output and mark recurring ideas.
4. Move key insights to your team board.

Example: A customer service employee's blog post about 'worst moment of the week' showed a pattern around 'promises from other systems that I don't have the authority to keep'; An initiative has been opened to clarify the permissions of the customer upon transfer.

Tip: Prevent evaluation while writing, set a strict time limit (5–10 minutes), and then move recurring ideas to the team board for later group analysis.

An exercise in which participants quickly associate words or adjectives with concepts, signs, or services to reveal first mental perceptions and associations. Immediate answers are often more truthful than 'improved' answers after long thought, and are useful in formulating the message and positioning.

1. Show target words or concepts.
2. Ask for quick first links.
3. Discuss the reason for the link.
4. Use the results to craft your message or position your solution.

Example: Linking words such as trust/speed/complexity to different payment services revealed that internal service is associated with 'complexity' even though it is faster in time; The interface language and visual progress signals have been redesigned.

Tip: Ask for the first connection without a lengthy justification first, then discuss the reasons. Use the results in conjunction with other behavioral evidence, not in isolation.

A creative stimulation technique that uses a random word or image to force association with a challenge and break intellectual inertia. It is not a substitute for understanding the user, but rather a tool for awakening unfamiliar paths and then filtering out what serves the real need.

1. Choose a random word/picture.
2. Forcibly link it to the design challenge.
3. Generate ideas from this connection.
4. Describe the most promising ideas for development.

Example: Associating the word 'garden' with the challenge of a hospital waiting room generated the idea of ​​green calm stations and short walking paths; Tested as a scale model, it improved pre-appointment self-assessment of stress.

Tip: Set a random launch time and then a strict filtering gate based on user insight. Keep what serves a real function, not weirdness for its own sake.

Collect extensive digital data (questionnaires/scales) to investigate the magnitude and priorities of the phenomenon after or alongside qualitative research. Quantity answers 'How many times/which slice?' The qualitative answers 'why?'; Together they prevent a single story from being exaggerated or a broad pattern ignored.

1. Formulate hypotheses from qualitative research.
2. Design measurable questions.
3. Collect a sufficient sample and analyze the results.
4. Connect numbers to stories for clearer decisions.

Example: After qualitative interviews on payment failure, a survey of 500 users measured the frequency of the problem by device type; It turned out to be focused on an old version, so the fix was directed there first instead of a complete redesign.

Tip: Formulate hypotheses qualitatively first, then measure them quantitatively. Do not make a productive decision from a number without a story, nor from a story without an appreciation of its size.

Short exercises at the beginning of sessions to break the ice and stimulate participation and thinking before interviews, storms or workshops. It increases energy and psychological safety without stealing real work time if it remains limited and linked to the spirit of the session.

1. Choose a light exercise related to the spirit of the session.
2. Set a short time (3–7 minutes).
3. Encourage participation without evaluation.
4. Move smoothly to the main activity.

Example: Before Empathy Workshop: A quick round in which each member shares 'something that surprised them this week'; It increased participants' openness and facilitated the transition to telling stories from the field.

Tip: Choose a light exercise for 3-7 minutes without evaluation, link it to the spirit of the session if possible, then move immediately to the main activity without prolonging it.

Physically embodying the idea in space by representing movement and interaction with simple objects and tools (Bodystorming) to discover design flaws related to space, effort, and sequence early, before technical investment. Sitting and talking alone hide movement problems.

1. Select the scenario you want to simulate.
2. Represent the steps with available objects and spaces.
3. Notice the friction, fatigue, and confusion.
4. Immediately modify the concept and repeat the simulation.

Example: Simulating a patient's path from reception to clinic with adhesive tapes on the office floor revealed a two-way conflict at a narrow angle; The route was modified in the building's prototype prior to the costly implementation.

Tip: Really act out the scenario with your body, and notice the fatigue, confusion, and congestion. Modify the concept immediately and repeat the simulation in a short cycle.

Role-play the user or stakeholder to experience the situation from their perspective, test dialogues and scenarios, and build deeper empathy within the team. He takes the role seriously; Sarcasm impairs learning. Useful across stages from empathy to concept testing.

1. Identify characters and context.
2. Represent the scene as realistically as possible.
3. Switch roles between team members.
4. Elicit emotions, barriers, and opportunities for improvement.

Example: Playing the role of a senior citizen trying to complete a transaction through a complex application in front of the team made the difficulty tangible; The steps have been rearranged and the mandatory fields on the first screen have been reduced.

Tip: Switch roles between members, establish a clear character and context before acting, and elicit emotions and obstacles immediately after the scene.

A practice in which the team experiences the product or service themselves as real customers as possible to obtain a direct assessment of frustrations and feelings before and after the solution. Direct, lived pain guides design more powerfully than a theoretical questionnaire.

1. Select the current service.
2. Experience the experience like a real customer.
3. Record your frustrations and feelings.
4. Repeat with the new solution for evaluation.

Example: A traffic enforcement team tried to report a fake accident in the rain under real conditions; The image upload failed easily so the quick reporting path was redesigned with partial offline mode.

Tip: Subject to the same constraints as the client (time, place, stress). Record frustrations in real time, and repeat the experiment with the new solution for comparison.

Using tools or simulators that restrict the senses or abilities to experience part of reality for users with different conditions (impaired vision, limited mobility, etc.). It is an approximation and is not a substitute for dialogue with those with real experience, but it builds a quick sensitivity to the requirements of inclusion.

1. Identify the capability or constraint you want to understand.
2. Use a suitable simulation tool safely.
3. Perform real-life daily tasks under constraint.
4. Document difficulties and turn them into comprehensive design requirements.

Example: Wearing glasses that simulate visual impairment while using an electronic portal Detection of contrast failure and small touch targets; mandatory accessibility standards were introduced prior to launch.

Tip: Implement simulation safely, and carry out real tasks, not show off. Always complete by interviewing the person living the restriction daily to verify the conclusions.

Write or visualize a specific use story with a person, goal, context, and time that shows how they interact with the solution through steps, decisions, and emotions. It unifies the team around a targeted experience and serves as a basis for testing scenarios and prototypes away from loose, generic stories.

1. Define character, purpose, and context.
2. Write the sequence of steps and interactions.
3. Highlights of decisions, emotions and obstacles.
4. Use the scenario for team alignment or as a basis for testing.

Example: Scenario of a remote working mother booking a school appointment during a short lunch break. Enforce a restriction: Complete within 4 minutes from mobile; Any screen that required multiple attachments was rejected in that session.

Tip: Personalize the scenario with real time, place, and constraints. Use it to align decisions and test compatibility with personalities.

Gather feedback by presenting different scenarios via step-by-step cards regularly, recording direct reactions and asking to compare alternatives. Displaying systematically, card by card, reduces user confusion and distraction compared to displaying everything at once.

1. Design a deck of cards for each scenario.
2. Present each scenario step-by-step to respondents regularly.
3. Record your immediate reactions to each scenario.
4. Ask respondents to compare scenarios to extract the best solution.

Example: Display 3 bank login scenarios (password/fingerprint/one-time code) with sequential cards; Users preferred a path that combined a fingerprint with a clear recovery option without the complexity of the first screen.

Tip: Standardize your presentation for each scenario, and don't explain the benefits of your solution during testing. Ask for an honest comparison at the end after everyone has tried it.

Presenting a concept or prototype to real users and observing their interaction with specific tasks to gather validity evidence before scaling. Five Focused users often uncover the most critical problems early if the tasks are realistic and the hypothesis is clear.

1. Define the test hypothesis and tasks.
2. Present the form without excessive explanation.
3. Observe behavior and ask after performance.
4. Decide: confirm, modify, or reject.

Example: Testing an appointment booking form with 5 reviewers without assistance measuring task completion; 4 When branch selection failed due to ambiguous naming, the names were renamed before any further background development.

Tip: Define the test hypothesis in advance, explain less, observe behavior and then ask. Close with a decision: confirm/amend/reject with notes arranged by severity.

Evaluating the ease, effectiveness, and efficiency of using an interface or service across specific tasks and metrics (completion, errors, time, post-task satisfaction). Usability is measured by performance on tasks, not by the overall impression of 'I like it'.

1. Create realistic tasks for the user.
2. Monitor completion, errors and time.
3. Collect post-test impressions.
4. Rank the problems by severity and impact.

Example: A test of completing a bill payment within two minutes without errors repeatedly revealed an error in the amount field due to the comma; Coordination was addressed immediately and the completion rate increased.

Tip: Formulate tasks in real-world use, rank problems by severity and impact, and don't confuse interface aesthetics with task achievability.

A quick, informal test in a public place to gather spontaneous impressions from available people about an idea or model with one clear question. Suitable for early cues and trends not for final statistical verification or high cost decisions alone.

1. Prepare a simple form and one clear question.
2. Approach appropriate people briefly and tactfully.
3. Collect quick and diverse responses.
4. Summarize the recurring signals for the next iteration decision.

Example: Showing a recording screen graphic to café patrons and asking: Where do you press to start? Majority clicked on a promotional item; The primary button was re-highlighted prior to a deeper user testing session.

Tip: Prepare a simple form and one clear question, and be nice and brief. Use the signal to guide the next iteration, not as a final statistical guide.

A frame of mind that calls for putting aside experience and assumptions and seeing the situation through the eyes of a child who asks, 'Why are things happening this way?' According to the evidence, it is often the only way to break away from established patterns that become burdens when trying to think again, and open the door to x10 thinking patterns and disruptive paradigms.

1. Let go of your preconceived assumptions and experiences.
2. Ask the question 'Why?' On familiar things.
3. Avoid making value judgments while observing.
4. Look for patterns that break conventional thinking.

Example: Naql Team Question: Why do we need signals at this intersection? Led the review of physical flow and the development of smart roundabouts/signals rather than just increasing time; The problem frame changed from 'Signal control' to 'Continuous safe flow'.

Tip: Experience is a temporary enemy in empathy; Put it on hold temporarily. State assumptions explicitly and then challenge them with intentional, non-judgmental questions while observing.

Collect and analyze existing information (reports, research, data, policies, complaints) to establish initial understanding and knowledge gaps before or alongside the field. It saves time and reveals quantitative or historical patterns, but it does not replace the need to meet the real user to verify meaning and context.

1. Identify secondary research questions.
2. Gather reliable and diverse sources.
3. Summarize the facts and gaps.
4. Determine what needs to be verified in the field.

Example: A review of satisfaction reports and complaints a full year before the field highlighted an increase in 'lack of clarity of requirements'; Observation and interviews were directed at this point rather than rediscovering it from scratch.

Tip: Define secondary questions in advance, summarize facts versus gaps, and distinguish what needs to be verified in the field. Don't base the solution on an old report without examining the context change.

Synthetic and semi-fictitious profiles based on observations of real people embodying target segments with demographic and psychographic characteristics, and functional and emotional needs. It serves as a living reference for design decisions and testing the compatibility of ideas, and should remain a mirror of the data and not imaginary characters for decoration.

1. Collect real field data.
2. Create a stereotypical character and give him a name and a picture (eg: John Seger).
3. Identify her motivations, pains, and gains.
4. Use them to test the compatibility of ideas and solutions.

Example: The character 'Umm Ahmed - an employee busy with three children' was tested on vaccination reservation screens; Any step that required multiple attachments in a limited time was rejected, so the path was simplified to one short session.

Tip: Based on field data, give a name, photo, motivations, pains and gains, and update the character as new evidence emerges. Use it in every decision portal, not in a forgotten folder.

A tool that complements personas by collecting client feedback through what they hear, see, think/feel, and say/do, then deduce the pains, gains, and story of the business (when… I want… until I can…). It links internal processing to external influence and pushes formulations of a need rather than premature solutions.

1. Draw 4 quadrants (hears, sees, thinks/feels, says/does).
2. Fill it out from field notes objectively.
3. Elicit pains (tensions) and gains (goals).
4. Summarize it with the story of the work (context, motivation, function).

Example: A map of a college student showed that he hears colleagues complain about schedule conflicts and thinks about lack of time; Pain is the distraction of the decision, not the difficulty of the interface. A need was formulated: 'Achieve a stable weekly schedule with confidence' before any new feature.

Tip: Fill in the quadrants of the field objectively, separating observation from interpretation. Express the pain/gain in need-output terms, not solution statements, and then summarize the business story below.

A technique in which the team comes together and each member tells his or her field stories while others take titles and post notes on the wall to discover patterns. Storytelling overcomes individual perception bias and creates group empathy and shared saturation of the workspace with information.

1. The team gathers in one room (operating room).
2. Each member tells what they saw and heard in the field as a story.
3. The rest extract meanings and differences and write titles (notes/quotes).
4. Stick notes on the wall to discover patterns.

Example: Researchers who returned from the hospital recounted the strangest moments with patients while colleagues wrote quotes; The 'fear of missing out' pattern appeared stronger than the waiting pattern and directed the familiarization phase.

Tip: Make the narration anecdotal rather than point reports, capture verbatim quotes on the wall, and then move on to grouping without early evaluation until collective patterns emerge truthfully.

A framework of observation that separates what happens superficially (what), how it happens procedurally (how), and why it happens in terms of motives and meanings (why). It prevents jumping to interpretation before recording reality, and then builds a bridge from behavior to need in an organized way that can be shared.

1. Record 'what' happens objectively.
2. Describe 'how' step by step.
3. Infer 'why' through context clues and dialogue.
4. Turn answers into insights and needs.

Example: Observing an employee re-entering data manually: What? Copies between two screens. how? Repeated copy/paste. Why? Doesn't trust system synchronization. Insight turns into a problem of confidence and integration, not a typing speed training.

Tip: Write the 'what' objectively first before the 'why'. Use the framework in the field and after it during group analysis to standardize the team's language.

A series of graphics illustrating the client's scenario and interactions with systems and people over time to achieve a common understanding of obstacles and solutions. Simple diagrams are sufficient; The goal is clarity of the journey and pain points, not technical quality.

1. Draw the scenario step by step.
2. Explain customer interactions with systems and people.
3. Identify obstacle points in the drawings.
4. Draw modified and proposed solution scenarios.

Example: Draw a traveler's journey from baggage drop to the gate. Specify the moment of loss when the gate changes without notice. An immediate alert and ground guidance path were designed for that point.

Tip: Draw the current situation and then the proposed situation. Don't let poor drawing hold you back; Linear characters work if the steps and emotions are clear.

Embodying the idea in a tangible or semi-tangible form (figure, diagram, story, flipchart) to share understanding and test direction early. The model is a cheaper means of dialogue and learning than the complete construction. The level of accuracy is chosen according to the stage of risk.

1. Choose the appropriate resolution for the stage.
2. Build the model with the fastest materials available.
3. Show it to the team or users.
4. Collect feedback and modify the concept.

Example: A cartoon mockup of the 'Receive documents without a queue' service was shown to reviewers before development; They rejected the idea of ​​a fixed, strict deadline in favor of a time window, so the concept changed before a line of code was written.

Tip: Build with the fastest materials available, test, and disengage from the model if evidence that contradicts it appears. Make clear to testers what is assumed and what is real in the model.

Use visual or linguistic metaphors to describe a complex experience and connect elements of the metaphor with elements of reality to create a shared understanding and language within the team. A powerful metaphor shortens a long report and motivates solutions consistent with the user's true feeling.

1. Identify the difficult aspect of the experience.
2. Ask or suggest evocative metaphors.
3. Draw a map linking the elements of the metaphor to the elements of reality.
4. Use them to standardize team language and motivate solutions.

Example: Describing a government transaction journey as a 'maze without signs' led to design principles: a sign at every decision, a progress map, and an emergency exit for human assistance.

Tip: Choose an honest metaphor for data, not an exaggerated one, and test whether it moves the team toward the right problem before using it externally.

Compare how different cultures or contexts approach a similar challenge to inspire new principles and practices. The goal is to transfer the principle, not copy the formal shell, while adapting the solution to local values ​​and constraints.

1. Identify the core challenge.
2. Research the different cultural contexts you encounter.
3. Compare practices, values ​​and outcomes.
4. Adapt what suits your context without blind copying.

Example: Comparing clinic waiting locally with queue management practices in other contexts highlighted the value of 'time transparency'; A lively waiting palette was applied without replicating inappropriate foreign decor.

Tip: Identify the core challenge first, then look for contexts that excel at it. Ask: What is the principle? What needs to be culturally adapted?

Identify who influences and is affected by the problem or solution, along with their interests, power and position, to plan engagement, manage change and guide research. Omitting a silent stakeholder, the launch may fail even if the end user likes the solution.

1. List all relevant parties.
2. Categorize them by influence and interest.
3. Identify supporters, opponents and neutrals.
4. Plan how to engage each group.

Example: Analysis of a municipal service automation project revealed silent resistance from audit staff who are measured by number of transactions, not quality; Internal incentives have been modified and the citizen experience has been improved.

Tip: Categorize parties by influence and interest, plan to engage each group in a different way, and update the analysis as the scope of the project changes or new resistance arises.

Break down the current process into sequential steps with time, systems, and responsibilities to uncover waste, waiting, bottlenecks, and repetition. It measures actual time, not the theoretical time written in the manual, and paves the way for redesigning a simpler, testable flow.

1. Draw the steps from start to finish.
2. Record the time, systems, and who is responsible for each step.
3. Limit repetition, waiting, and errors.
4. Suggest a simpler flow and test it.

Example: Drawing the flow of a certificate from order to delivery, revealing three identical reviews between two departments; Combined into a single checkpoint, cycle time is reduced without compromising compliance.

Tip: Walk the process in the field and document the real wait. Distinguish valuable steps from manipulations, and test the new flow with a model before generalizing.

A flow chart that divides work into lanes by roles or departments to show delivery points across organizational boundaries. Most pain occurs when crossing lanes; Therefore, optimization focuses on transitions and redundant loops between entities.

1. Define roles or departments as lanes.
2. Draw the steps within each lane.
3. Show handover points between lanes.
4. Simplify transitions or eliminate redundant loops.

Example: A lane diagram between customer service, finance, and technology for a refund path that showed a double bounce for an attached deficiency; A checklist is designed at the first point of entry to prevent bounce.

Tip: Draw the deliverables clearly, and ask at each crossing: Is it necessary? Can it be integrated or automated? Involve representatives of each lane in a reality check.

Understanding the mental models and cognitive steps an agent takes to understand and interact with a system or scenario: his sensory inputs, his decisions, his actions, and the feedback he receives. It looks for moments when the user is left without a clear state or meaning for an interface element.

1. Divide the experiment into separate tasks.
2. For each task, determine the sensory input (visual, auditory) that the client receives.
3. Identify decision points and resulting actions.
4. The feedback values ​​that the system gives to the customer.

Example: Analysis of the moment a user stands in front of a mysterious button in an application before pressing it revealed the absence of feedback about the outcome of the previous step; Added a clear status message before any new action is requested.

Tip: Divide the experience into tasks, and for each task determine what the user perceives, decides, does, and what the system returns. Address feedback gaps first, as they generate frequent errors.

Studying body proportions, movement and physical ability to ensure products and environments fit real users across the human range - not one 'average' that excludes the extremes. Universal design supports and reduces stress and errors associated with access, vision and placement.

1. Identify critical tasks and movements.
2. Collect relevant metrics data or review their parameters.
3. Evaluate the design against the target human reach.
4. Adjust dimensions, heights, and distances according to the results.

Example: Re-height and inclination of the Kiosk screen to suit standing people and wheelchair users after field measurement; Requests for assistance at the machine decreased and self-service completion improved.

Tip: Designed for the mid-range, not just the mid-range, and tested with a variety of bodies and abilities. Review the relevant standards and relate them to real tasks, not abstract numbers.

Study the types of possible errors, their causes and effects, their probability and severity, with the aim of designing prevention, detection and easy recovery. It is assumed that an error will occur; Success is in escaping it and reforming it with dignity, not in denying it.

1. List tasks and decision points.
2. Identify possible errors for each point.
3. Assess probability and impact.
4. Design to prevent, detect or correct error easily.

Example: Analysis of ID number entry errors showed a pattern of number deletion; Instant verification, slot formatting, and visual segmentation have been added, reducing failed submissions and support calls.

Tip: List errors for each decision point, evaluate probability x impact, and design a clear prevention, detection, or correction. Do not rely on user training alone as a solution to an expected error.

Visualizing the exchange of value (information, money, services, trust, time, reputation) between the parties to the system to understand who benefits, who bears the cost, and where the imbalance is. In service networks, non-financial values ​​are often crucial to the sustainability of the solution.

1. Identify the parties in the system.
2. Draw what each party exchanges with the other.
3. Discover imbalances and gaps.
4. Design more balanced and sustainable value flows.

Example: A valuable network for a volunteer platform revealed that the authorities receive reports while the volunteer does not obtain clear proof of impact. A moral reward and a personal impact report were added, and persistence increased.

Tip: Draw two-way flows, discover gaps and imbalances, and design balanced value for each party influencing success.

Explore solution domains in completely different domains that share similar challenges (time, pressure, accuracy, cost) to inspire and then align brainstorming paths. The best solutions often come from outside the industry when the principle is conveyed rather than the shell.

1. Identify the critical challenge in your problem (eg: the need for maximum speed).
2. Look for other fields with the same challenge (eg: race car maintenance teams).
3. Observe that field and be inspired by the mental pathways to their success.
4. Adapt those solutions and adapt them to the scope of your problem.

Example: Developing an emergency room was inspired by the efficiency of the Formula 1 tire changing team in distributing roles and preparing in advance. The preparation time before receiving a critical situation has been reduced.

Tip: Pinpoint the critical challenge first, then look where it has been solved well outside your sector. Observe the field if possible and transfer principles after adapting local constraints.

Clarify the relationships between customer tasks and product/service characteristics by evaluating the impact of each feature on each task (+ / − / neutral). Innovation focuses on closing gaps and turning negative impact into positive especially where mission criticality is high.

1. Type client tasks in rows/columns.
2. Write the characteristics of the product or service in the other axis.
3. Rate the impact of each feature on each task (+, -, O).
4. Innovation focused on filling gaps and turning negative impact into positive.

Example: Evaluating the weight of a device on the task of carrying it all day showed a critical negative effect; Light weight was introduced as a design constraint rather than a secondary advantage, and the priority of materials changed.

Tip: Make tasks and properties from real data. Start from the 'Important Task x Negative Impact' cells, as they are the most powerful opportunities for joyful innovation.

A group synthesis method that records ideas and notes on cards and then silently groups them according to similarity to reveal relationships and themes without imposing a prior classification. Naming the groups is done after grouping so that the team does not project its mental structure onto the data prematurely.

1. Write each note on a separate card.
2. Silently move the cards into similar groups.
3. Name each group after it is completed.
4. Use themes to formulate insights and perspectives.

Example: Collecting 200 field notes led to a recurring theme of 'uncertainty of the next step' that was stronger than the theme of 'slowness of the system'; The priority of definition and redesign has changed.

Tip: Silent group first, name after the groups are complete, and carefully combine stray cards. Use themes to formulate insights and perspectives, not as a list of solution ideas.

Visually transcribe the results by saturating the workspace with notes and then compiling them to discover patterns at multiple stations in the process (post-empathize, define, point of view, generate, test). It creates a common synthesis and prevents knowledge from remaining in the heads of separate individuals.

1. Write each note or quote on a separate sticky note.
2. Fill the operating room wall with these papers.
3. Move the cards to group similar items into groups.
4. Identify titles for the patterns and themes that emerge.

Example: A team saturated the wall with 500 notes and discovered by collecting that the root of the problem was “timeliness of service” and not “quality” as assumed; The project was completely redirected.

Tip: Post-it note for each note/quote, visually group and label the patterns, and re-saturate after each new field stage so the image stays alive.

Visually map the actors, relationships, flows, and environment around the product or service. It reveals that a solution within a single product may fail if it ignores the broader system, and helps choose the highest impact points of intervention.

1. Put the user or value at the center.
2. Add surrounding actors and systems.
3. Draw relationships and dependencies.
4. Identify the intervention points with the highest impact.

Example: Imagine a school transportation service system (parents, school, driver, application, monitoring) that showed the breakdown of communication between the driver and parents when the bus is late. A shared state channel is designed instead of just map path optimization.

Tip: Place the user or value at the center, add actors and dependencies, and define intervention points. Update the map as partners and channels change.

A tool for sorting and prioritizing across two orthogonal axes of significance (e.g. impact/effort or importance/satisfaction) for group visual decision making. Good axles force a real trade-off; Synonyms produce empty discussion.

1. Choose two axes of significance for the decision.
2. Place the elements on the array collectively.
3. Discuss the disputed positions.
4. Make a decision based on the resulting quadrants.

Example: Screening 20 Improvement Ideas for Beneficiary Impact vs. Ease of Implementation Identify quick wins in a high-impact/low-effort quadrant and implement them within two weeks to build momentum.

Tip: They agreed to define the two axes before placing the elements, discussed the disputed areas openly, and came up with an implementation decision, not just a mural.

A comprehensive depiction of the elements of the current situation, including people, evidence, systems, feelings, and obstacles, to create a common picture before jumping to the solution. A team alignment tool that is updated as new evidence emerges and reveals inconsistencies and gaps.

1. Gather input from field research.
2. Distribute the items to the sections of the map.
3. Discuss gaps and contradictions.
4. They agreed on the priority of what should be understood or solved first.

Example: A situation map for renewing a license showed a confusing overlap between attendance, the application, and the call center, without a single source of truth for the situation; The order status across channels has been unified as the first fix.

Tip: Distribute field input to map sections, discuss discrepancies and gaps, and agree on the priority of what needs to be understood or resolved before generating solutions.

A strategic planning tool developed prior to research to determine who, where, and when the observation or interview will take place based on the experiment scenario: stakeholders, tasks, tools, and interaction activities. It becomes part of the broader insight plan and prevents friction points in the field from being overlooked.

1. Choose the experiment scenario you want to investigate.
2. List all stakeholders, tasks, and associated tools.
3. Make a plan to arrange procedures and interviews according to the list.
4. Integrate it into the broader project insight plan.

Example: Plan a department hospital visit today to meet a patient, monitor a nurse, and analyze instruments at a recording point; The team discovered friction that would not have arisen if they had limited themselves to a single meeting in an office.

Tip: Build the list from the scenario, not just from logistical convenience, and integrate it into the insight plan with complementary quantitative and secondary research.

An early workshop run by the project sponsor with the team and stakeholders to consolidate the vision, present the initial problem and preliminary research, and come up with a project charter for research and design. Prevents subsequent argumentative fights and unifies the compass from day one.

1. Bring together the team, stakeholders, and project sponsor.
2. Present the initial problem and preliminary research.
3. Discuss the challenges and their importance to the business and the client.
4. Come up with a unified project charter for research and design.

Example: A two-hour session with the department manager and innovation team before the field agreed on a measurable goal and scope boundaries; Prevented subsequent random expansion in the middle of the search.

Tip: Come up with a written charter that includes the goal, scope, non-scope, and milestones. Make the project sponsor physically present, not just by delegation, until the compass is established.

Use storytelling based on real data to share insights with the team or stakeholders in an impactful and memorable way. A compelling story selects and condenses facts, not makes them up, and connects a character to a conflict and a desired outcome to drive a decision or inspire a solution.

1. Choose a character and plot based on real data.
2. Build a clear beginning, climax, and conclusion.
3. Highlight the need, conflict, and desired outcome.
4. Use the story to drive a decision or inspire a solution.

Example: The story of 'Abu Saad' who failed three times to upload a document due to the file format convinced the leadership of the priority of clear error messages over a long statistical slideshow.

Tip: Build a beginning, climax, and conclusion from real data, use a literal quote, and tie the end of the story to a clear resolution so it doesn't remain just emotional inspiration.

Identify barriers to progress (organizational, technical, behavioral, cultural) and environmental trends that drive change to guide strategy and innovation towards overcoming obstacles or riding the right waves. The hidden cultural barrier may be stronger than the obvious technical barrier.

1. List the barriers (organizational, technical, behavioral).
2. List relevant trends (technical, social, market).
3. Link it to opportunities and risks.
4. Direct thoughts towards overcoming barriers or riding trends.

Example: Mapping digital payment adoption barriers against the mobile penetration trend among seniors. Orient the solution towards simplifying the steps of trust (optional human confirmation) rather than towards more complex technical features.

Tip: Clearly separate barriers from trends, estimate the impact of each element, and turn the output into constraints and opportunities that guide generation rather than a descriptive list that is not used in the decision.

A clear description of the ideal user experience as an emotional and practical outcome before detailing the features. Acts as an arbiter when the team disagrees on features: we come back to the target experience and its success criteria.

1. Describe the feelings and desired outcomes for the user.
2. Identify the critical moments in the experience.
3. The team agreed on emotional and practical success criteria.
4. Use the model as a reference for design decisions.

Example: Sample experiment: 'Feel confident within 60 seconds of opening the app without assistance' Driven the rejection of any sponsored first screen that prolonged access to the core mission and unified the team's decisions around the priority of clarity.

Tip: Describe emotions, results, and critical moments with simple success metrics, and return to the model at each feature differentiation so that the team does not get lost in the features.

Collective thinking passes the papers around in a circle so that each individual builds on the ideas of others by force, thus transcending stagnation and the ego’s perspective. Useful for breaking the attachment to the first idea and forcing multiple perspectives to come together before evaluation.

1. Everyone writes their initial thoughts on a piece of paper.
2. Pass the papers to the person next to you.
3. The person reads ideas and adds new ideas to build on them.
4. The cycle continues until the paper is returned to its owner and the group discusses the results.

Example: A paper that started with a 'banking application' and was then built on by 'voice control' and then 'voice financial advisor'; A concept emerged that would not have appeared in a short, traditional storm because the forced construction on the ideas of others forced new paths.

Tip: Prevent criticism during passing cycles, determine the number of turns in advance, and open a group discussion only after the paper is returned to its first owner.

Using groupthink to generate the largest number of ideas around a challenge in the form of 'How can we...?' Deferring judgment and building on the ideas of others. Quantity opens the way to quality; The best ideas often come out of the ordinary. It is preceded by clarity of the challenge and followed by organized sorting.

1. Pose a clear challenge in a 'How can we...?' approach.
2. Encourage a wide range of ideas, no matter how wild.
3. Strictly prohibit evaluation or criticism during the session.
4. Build on other people's ideas and integrate them together.

Example: Generating 100 ideas to improve the work environment within 30 minutes without evaluation. Later, 5 bold concepts were produced after screening for impact/feasibility that were not among the first suggestions.

Tip: Formulate a clear challenge in the form of how can we, prevent criticism during generation, encourage creativity and building on the ideas of others, and then separate in time the sorting and convergence phase.

A structured sentence template to formulate the user's point of view, such as: A user needs a need for insight. It forces the team to relate a segment to a need supported by field insight rather than a broad, general problem statement, and paves the way for how-can questions and focused generation.

1. Use a template such as: '[User] needs [need] because [insight]'.
2. Fill out several copies of the search.
3. Experience its clarity and power collectively.
4. Choose the strongest generation weatherization formulation.

Example: The formulation 'The urgent reviewer needs immediate confirmation of the status of his request because he loses confidence with every silence from the system' became a compass for testing any case design and tracking interface before brainstorming.

Tip: Write several versions of the data, and test its strength with a critical reading checklist. If the statement is very general, it is not yet a point of view; Go back to the field or narrow your vision.

Formulating the essence of the insight through a familiar analogy makes the problem emotionally understandable and facilitates stakeholder engagement. It is used to clarify, not to exaggerate; Remains custodian of field data.

1. Extract the essence of field insight.
2. Find a familiar analogy that reflects the feeling.
3. Test if the analogy moves the team toward the right solution.
4. Use it in indoor presentations with caution and precision.

Example: Likening the support experience to a “dark maze without a map,” he justified a step-by-step guidance project before a committee that saw the problem as “a lack of training for beneficiaries.”

Tip: Test whether the analogy moves toward the correct solution and does not distort the problem. Use it internally first with caution before external displays, and keep it data safe.

Formulating the team's perspective on the customer and their need as a fun and engaging classified ad that distills the defining characteristic, implicit need, and field insight in a humanistic way that breaks the rigidity of the administrative script and makes the problem emotionally sensible within the team.

1. Identify the defining characteristic of your target customer.
2. Determine the underlying need and desired outcomes.
3. Add flavor that reflects field insights in a metaphorical advertising style.
4. Discuss the ad as a team to extract the real problem from it.

Example: 'A busy working mum looking for a care service she trusts to chat to. Serious people only.' I helped a team sense the human side and formulate the problem of trust, not just price, instead of reducing the need to price.

Tip: Keep the ad based on field insight, not empty humor, and then discuss it as a team to extract the real problem and formulate a generateable need.

An assessment tool for the point of view statement across questions of meaning, health, excellence and relevance: is the angle unique and insightful? Is it backed up by data? Is it new? Are you worthy of enthusiasm? If you are not excited, it is better to return to the field than to beautify the phrase.

1. Ask: What's the point? (Is the angle unique and based on insight?)
2. Who says that? (Is the insight supported by data from the field?)
3. What's new in it? (Does it provide new added value?).
4. Who cares? (Is it a problem worth solving with enthusiasm?)

Example: A review of the statement about 'Waiting at the Bank' revealed it to be repetitive with no unique angle; Reframed around 'the ambiguity of waiting time and loss of control' after a short field trip.

Tip: Apply the four questions with collective rigor. Don't pass along a cold point of view; Either deepen insight in the field or repeat the research before moving on to obstetrics.

Imagine how another iconic brand with a different philosophy would approach your challenge to break molds, generate bold trends, and then re-adapt what is best for your identity and context. The goal is a creative metaphor, not imitation of the identity of others.

1. Choose brands with contrasting philosophies.
2. Ask: How will this sign solve it?
3. Generate concepts in her own way.
4. Re-adapt what's best for your identity and context.

Example: Question: What if a luxury hospitality brand designed a passport renewal experience? It generated ideas about welcome, anxiety management, and timeliness that entered service principles without copying a logo or colors.

Tip: Choose tags with varying philosophies to explore new angles, generate freedom without imitation, then filter ideas through the constraints of your tag and your user's field needs.

Design the external presentation of the concept — name, promise, benefits and image — before building the internal details to test whether the value is understood within seconds. If the box fails to deliver value, the concept needs clarification before further construction.

1. Write the name of the solution and its main promise.
2. Identify three clear benefits.
3. Visually design the interface of the box.
4. Test whether strangers understand the value in seconds.

Example: 'My transaction in my pocket' concept box with the promise of completing the transaction from mobile was tested on employees outside the project; Half of them understood it as a payment app only, so the promise was reframed around 'tracking and completing transactions'.

Tip: Write down one promise and three believable benefits, and quickly test understanding on people unfamiliar with the project; If the fund fails, the concept needs clarification before construction.

A parallel thinking framework from Edward de Bono that separates the angles of facts, feelings, caution, optimism, creativity and managing the debate through 'hats/lenses'. The difference is prevented from turning into a personal conflict through temporal separation of angles, and the most appropriate lenses for the situation can be chosen.

1. Identify the idea or decision under discussion.
2. They passed the hats sequentially.
3. Stick to the color of the hat at the moment.
4. Summarize the decision after the corners are complete.

Example: Evaluating a new characteristic: a white hat for data, then black for risk, then green for alternatives, then blue for the decision; a conditional decision came out with a limited experience instead of a circular argument between a supporter and an opponent.

Tip: Stick to the color of the hat at the moment and do not mix angles in one argument. End with a management hat to clearly summarize the decision, steps, and responsibilities.

Study the evolution of a situation or field over time to understand the roots, avoid repeating previously failed solutions, and understand why some 'new ideas' seem familiar to veterans. Connects the present to a path of change that helps make clearer bets.

1. Collect related historical milestones.
2. Determine what has changed and what has been proven.
3. Draw lessons and patterns.
4. Use understanding to choose clearer future bets.

Example: Following the customer service channels of a government entity over 15 years revealed recurring cycles of launching a new channel without closing the old one; the project changed from 'adding a channel' to 'simplifying the portfolio'.

Tip: Collect reliable milestones over time, identify what has changed and what has proven, and extract explicit written lessons before proposing the next solution so as not to repeat a failed cycle.

Distributing phenomena, technologies, and behaviors over time periods to envision the major transformation and build a common future perspective. It helps monitor interruptions and signals of the coming era, not just confirming what is known today.

1. Choose two axes or a clear time path.
2. Distribute events and transitions over epochs.
3. Discuss interruptions and opportunities.
4. Link the map to innovation scenarios.

Example: A map of the transformation of citizens’ dealings with services from the home office to the mobile phone highlighted the gap between the elderly people between eras. A dual-channel strategy was developed with a gradual, supported transition.

Tip: Choose a clear time axis, distribute clues rather than slogans, and discuss where the next break might occur so that the map is not merely used for decoration.

Anticipating an approach to long-term trends and their impact on users and offers, while building flexible strategic options in the face of multiple scenarios rather than false certainty in a single scenario. Connects current signals to today's design decisions.

1. Collect trend signals from multiple sources.
2. Build long-term hypotheses.
3. Assess impact and likelihood.
4. Identify flexible strategic options for each scenario.

Example: Predicting the impact of population aging on government services within 20 years prompted the inclusion of accessibility requirements and human support options in the design of the current digital service, not as a later addendum.

Tip: Gather signals from multiple sources, build impact and probability hypotheses, and design for flexible options rather than a fragile bet on one future that seems certain.

A forward-looking exercise in which the team writes headlines of potential successes or failures to motivate today's initiatives and link them to tangible results. Bold titles move the work forward if they remain honest and can be translated to tasks, not empty propaganda.

1. Write titles for potential successes and failures.
2. Discuss what to do now to make or avoid each heading.
3. Turn titles into initiatives and metrics.
4. Review it periodically as the project progresses.

Example: Target headline: 'Entity

Tip: Write down potential successes and failures, ask what we are doing this month to make or avoid each one, and then review the titles periodically as the project progresses.

A tangible embodiment of what the near future (1–5 years) might look like through models, stories, or experiences that can be touched today to reduce fear of change and gather early reactions to the trend rather than an abstract idea.

1. Select a short time horizon (1–5 years).
2. Build a tangible impact for the foreseeable future.
3. Test user and stakeholder feedback.
4. Figure out what's worth building now.

Example: A model of a future self-service room was shown to staff and visitors; Concerns of losing human assistance arose and a hybrid aid station was incorporated into the concept before full investment.

Tip: Set an immediate time horizon (1–5 years), build an impact that can be experienced today, and extract from the feedback what is worth building immediately, not later.

Construct multiple plausible future scenarios across critical uncertainty drivers to test the robustness of concepts and strategy under varying conditions. The goal is to be prepared, not to claim to know the only 'correct' scenario.

1. Identify critical uncertainty drivers.
2. Build 3–4 distinct scenarios.
3. Test your concepts within each scenario.
4. Make strong choices across more than one scenario.

Example: Three scenarios for digital service adoption (fast/slow/organizational resistance) revealed a need for a hybrid service option that is resilient across scenarios rather than a fragile, purely digital solution.

Tip: Identify two or three drivers of uncertainty, build distinct scenarios, test your concepts within each, and make strong choices across more than one scenario.

A structured group review of a concept, design, or plan according to agreed-upon standards to uncover gaps before implementation or external testing. Separate time between generating feedback and responding to it so that ideas are not killed prematurely.

1. Distribute materials to participants in advance.
2. Review according to agreed standards.
3. Take notes without early defense.
4. Close with a list of improvements and task holders.

Example: Collaborative inspection of a sample application prior to external testing uncovers ambiguity in user permissions; Fixed before external testers' time was consumed on an apparent internal issue.

Tip: Distribute materials in advance, review according to agreed-upon criteria, record feedback without immediate defense, then close with a list of improvements and account for each item before the next session.

Collaborative work on a large shared space (wallpaper/board) to visually illustrate insights and solutions and force convergence towards a unified visualization prior to detailed design. Shared space prevents individuals from being isolated in their own thoughts.

1. Hang a long strip of paper on the wall of the room.
2. Each member sketches out elements of the design solutions and makes notes.
3. The team discusses the options and ranks them in order of importance and sophistication of the drawings.
4. Convergence on a final, unified concept before detailed design.

Example: A team draws projected screens for an application on long paper and combines the best elements into a central drawing; This visual reference became an informal contract before digital interfaces.

Tip: Provide a large shared space, make everyone draw and observe, and push the discussion towards rapprochement and merging of elements, not towards individual parallel presentations without resolution.

Intentional application of strict and unusual constraints to focus thinking and generate high-value solutions off lazy paths. The mind creates more in the face of limitations that prevent easy solutions. Constraints are removed and replaced to activate multiple angles.

1. Identify the overall challenge for the team.
2. Apply an unexpected constraint (example: no technology, only 5 minutes, zero budget).
3. Collect ideas within this strict constraint.
4. Remove the restriction and put a new one to activate other angles of thinking.

Example: Generating customer service ideas on a 'never speak to any employee' requirement produced self-service and proactive support paths that would not have arisen in a wild storm.

Tip: Apply one clear constraint for each generation round, collect ideas, then change the constraint. After the rounds, adapt the best ideas to reality without losing useful audacity.

Frame the challenge as Motivating Questions (HMW) from the point of view and design principles of opening storming. A good question is broad enough to inspire and specific enough to focus; Formulating it is half the solution.

1. See the statement of view that was adopted.
2. Break a big challenge into smaller challenges.
3. Crafted as a 'how can we…' question so that it is broad for inspiration and specific for focus.
4. Use questions to start a brainstorming sequence.

Example: 'How do we make waiting time in the hospital an enjoyable/useful part of treatment rather than wasted time?' Opening up solutions that go beyond 'reducing waiting' alone towards the waiting experience itself.

Tip: Break the big challenge down into smaller, sequential questions based on the point of view. Avoid a question that is too broad or narrow that imposes a preconceived solution.

Reframe the challenge by doubling or dividing the constraints by a factor of ten to force radical, non-incremental solutions. Deliberate exaggeration breaks up lazy solutions, opens x10 pathways, and then reformulates bold ideas into reality.

1. Take the current challenge.
2. Ask: What if we had to improve it x10 or with /10 resources?
3. Generate solutions under excessive constraint.
4. Readapt bold ideas to reality.

Example: 'What if we completed the transaction in a tenth of the time?' Push to cancel entire steps does not optimize seconds within each step; Some verification has been moved to before placing an order.

Tip: Consciously use multiplication or division by 10 to break down lazy solutions, then filter out what can be adapted to reality while keeping the root idea useful.

Start from the desired end result and work backwards to determine the requirements, milestones, and dependencies needed to reach it. It reveals what needs to be achieved before each step up to the present, and prevents late implementation surprises.

1. Clearly define the end result.
2. Ask: What needs to be achieved immediately before it?
3. Return back to the present.
4. Turn the series into an action plan and milestones.

Example: From the goal of 'instant certificate issuance', the team returned to the requirements for verifying identity, payment and source data; An early external data dependency was discovered and managed before the interface was developed.

Tip: Define the end result precisely, ask at each layer what needs to be true before it, and turn the chain into clear milestones and responsibilities.

A short video that captures the future solution experience to explain the idea, gather emotional reactions, and quickly create a shared understanding. Sells the feeling of the experience; He must remain honest and not overpromise so that false trust is not built.

1. Write a short story of the target experience.
2. Produce a simple video (even with a phone).
3. Show it to users and stakeholders.
4. Gather what they liked and what didn't convince them.

Example: A minute-long video of a citizen completing his transaction from the car without the window sparked enthusiasm and questions about the exceptions. The cases that require attendance were made clear before development could proceed.

Tip: Keep the story short, honest, and don't overpromise. Gather what convinced and what didn't, and tweak the promise of the experience before investing fully in the build.

A constructive feedback framework divides comments into positives (I like), wishes (I wish), and imaginative suggestions (what if) without direct attacks. Maintains the team's creative integrity during critique and makes it easier to turn feedback into editing decisions.

1. Ask raters for 'I like' statements.
2. Then 'I wish'.
3. Then 'what if'.
4. Turn feedback into neat adjustment decisions.

Example: After viewing a sample: I like the clarity of the buttons; I hope the steps are shortened; What if the draft is saved automatically? It turned straight into three tasks in the next iteration.

Tip: Enforce the tripartite structure on each rater, prevent personal attacks, and turn each feedback category into prioritized decisions in the next iteration.

Organized distribution to collect and classify feedback during tests and presentations (eg positive/negative/questions/ideas) live on a visual grid. It prevents signal loss and speeds up the decision of what to change in the next iteration.

1. Draw a grid with four or more cells.
2. Distribute session notes directly there.
3. Remove redundancy and prioritize.
4. Close with a decision: What do we change in the next iteration?

Example: Feedback grid after testing a payment interface filled with questions about hidden fees; In-screen graphic transparency was processed prior to payment prior to any cosmetic color or icon enhancement.

Tip: Clear the grid immediately after the session, remove repetitions, arrange by severity and impact, and close with a clear repetition decision with an owner for each item.

Review competitors' offers and alternatives by trying them as a user to compare journey, value, pain points and extract differentiation opportunities rather than copying. It puts the solution in the context of market expectations without replacing the insights of your users.

1. Identify direct and indirect competitors.
2. Try their offers as a user.
3. Compare journey, value and pain points.
4. Extract opportunities for differentiation, not copying.

Example: A survey of local appointment booking apps showed that one of them excelled in the confirmation step and notifications; The principles of clear emphasis were incorporated without copying the interface verbatim, also based on user interviews.

Tip: Experience the competition as real tasks, not a superficial preview, compare journey points, and build your advantage on the insights of your users, not on imitation of the visual surface.

Learn from best practices in areas that are not direct competitors but excel in a similar capacity (speed, confidence, hospitality, accuracy). Conveys the principles from where the problem has been solved with excellence and then adapts them to your context.

1. Determine the capability you want to improve (speed, trust, hospitality...).
2. Choose sectors that excel in that ability.
3. Study their practices in the field or through research.
4. Translate the principles into your context with intelligent adaptation.

Example: Comparing waiting clinics to queue management at airports conveyed the principle of continuous status updating and segmentation of the wait; It was implemented without replicating the airport environment as it was.

Tip: Carefully define the capability you want to improve, choose sectors in which you excel, study the field principle and then adapt it to your cultural and organizational constraints.