Preparing for the Technical Group Task (45 Minutes)

1. Possible Types of Tasks (for a short, group UX challenge):

• Rapid Design/Prototyping Challenge:
  • "Brief: Ocado wants to introduce a feature to help users quickly re-order a full past shop with minor modifications. Sketch the key screens and user flow."
  • "Brief: Design a simple mobile interface element for warehouse staff to quickly report a low-stock item for a specific product."
  • Focus: Quick ideation, user flow mapping, lo-fi sketching (pen/paper, or simple digital shapes if a tool is used), and clear presentation of the concept.
• UX Problem-Solving/Critique:
  • "Brief: Here’s a wireframe for a new Ocado partner onboarding step. Identify 3 key usability issues and propose quick fixes for each."
  • "Brief: Based on this snippet of user feedback about finding recipes, suggest 2 design changes to the current recipe Browse interface."
  • Focus: Analytical skills, applying heuristics, justifying improvements, quick solution generation.
• Concept Ideation & Prioritization:
  • "Brief: Ocado is considering a new 'ultra-fast' delivery option for a limited range of essential items. Brainstorm 3 key features for this service and decide which one is most critical for an MVP."
  • Focus: Creative thinking, understanding user needs for a new concept, prioritization based on impact/effort.

What to Expect: You'll likely get a brief, need to understand it as a group, brainstorm/design, and then present or summarize your solution.

2. Effective Collaboration – Your Quick Guide:

• Communicating Your Ideas:
  • Be Clear & Concise: Start with your main point. "I think we should focus on [X] because it addresses [Y user need]."
  • Sketch it Out: Even a very rough drawing on your paper can make an idea much clearer to others quickly. If you can hold it up to the camera or describe it simply.
  • Connect to the Goal: Always tie your idea back to the task's objective or a user need. "This approach could help us achieve [task goal] by..."
  • "Yes, and..." not "No, but...": Build on others' ideas. "That's a great point about [X], [Teammate's Name], and perhaps we could also add [your idea] to enhance it?"
• Listening to Others:
  • Really Listen: Don't just plan what you'll say next. Nod, show you're engaged.
  • Acknowledge: "Good thought, Maria." "I understand your point about X, David."
  • Ask Clarifying Questions: "Could you elaborate a bit on how you see that working?" This shows interest and ensures you're on the same page.
• Discussing & "Arguing" Constructively:
  • Focus on the Idea, Not the Person: "I see a potential challenge with that approach regarding [specific issue]..." instead of "That won't work."
  • Provide Your Rationale: "My concern with [Idea X] is that it might [potential negative impact]. What if we considered [Alternative Y] instead, as it could [positive impact]?"
  • Seek Common Ground: "It sounds like we all agree on [core principle]. Maybe we can find a solution that incorporates both [Idea A's strength] and [Idea B's strength]?"
  • Be Okay with "Good Enough": In 45 minutes, you won't achieve perfection. If the group leans a certain way after discussion, be ready to commit and move forward, even if it wasn't your top choice.

3. How to "Think Out Loud" & Focus on Business Goals:

• "Thinking Out Loud" (Making Your Process Transparent):
  • Start with Understanding: "Okay, so if I'm understanding this brief correctly, our main goal here is to [rephrase the core task] for [target user, e.g., 'busy parents doing their weekly shop' or 'new Ocado customers']."
  • Verbalize Your Steps: "My first thought is to consider the main user flow..." / "I'm wondering about the key information a user needs at this stage..." / "From an accessibility standpoint, we should consider..."
  • Share Your Questions: "A question I have is, are we prioritizing speed of interaction or comprehensiveness of information for this feature?"
  • Narrate Sketching (if you do it): "I'm just quickly sketching a screen here to show [X element] and [Y element] to support that..."
  • Why it helps: It lets the assessors (and your team) see your analytical process, even if your final idea isn't "the one." It shows how you approach problems.
• Focusing on Business Goals:
  • Identify from the Brief (or Infer): Does the task hint at increasing efficiency, improving conversion, reducing errors, supporting a new Ocado service, or enhancing brand perception?
  • Connect Your Ideas to Value: When you propose something, briefly state how it helps the business.
    • "This simpler flow could reduce user errors [user benefit], which in turn might lower support queries for Ocado [business benefit]."
    • "Making this feature more discoverable could increase adoption [business benefit] and help users complete their shops faster [user benefit]."
    • "If we focus on [X priority], it aligns with Ocado's goal of enhancing customer loyalty by providing a more [efficient/personalized/reliable] experience."
  • Consider Feasibility/Impact: "While a very complex solution might be ideal, for a 45-minute task and an MVP, perhaps focusing on [simpler solution] would deliver the most immediate user value and business impact with less development effort."

Key Actions in the 45 Minutes:

1. Clarify the Goal (5 mins): As a group, make sure everyone understands the task and the deliverable. Assign a timekeeper.
2. Brainstorm/Ideate (15-20 mins): Generate ideas. Sketch. Discuss pros and cons.