Block Gemini

Explore the connected ecosystem.

Can a visitor recover a booking without calling support?

Compare two versions of a booking change screen, then introduce a slot that another visitor has taken. Inspect the choice, the information the visitor sees and the next task.

Scope my product prototype

Interactive example · fictional records

Inspect a prototype path

Booking change prototype · Visit B-12

Visitor’s goal
Move a Tuesday visit
What the screen shows
Cancel booking
Next step
Call support to rebook
Original path
Review decision

Identify the risky step in the original path

The only visible action cancels the current visit. In a usability session, ask someone to move the booking and observe whether they expect their original slot to survive.

Scope my product prototype

What we can build with you

A testable prototype of the critical journey, a decision log and interaction specifications for the engineering team.

Bring to discovery
Bring one customer task, the current screens and the error or support request that interrupts that task.
How to test the pilot
Ask representative users to change a booking and recover from an unavailable slot. Record where they hesitate or accidentally cancel.
Implementation details and questions

Founders and product teams aligning users, stakeholders and engineers before a major build.

Explore how a product should work before committing to its full build. We translate user tasks into information architecture, interactive prototypes and interface systems, including the review and recovery paths that AI-assisted experiences need.

  • A new product concept or MVP
  • A complex operational interface
  • An AI feature with review and recovery
  1. Understand the task

    Identify the users, information needs and moments of friction. Separate essential jobs from features that do not yet have a clear purpose.

    A journey map and priority tasks
  2. Make it interactive

    Create a prototype showing real choices, information hierarchy and the main success, empty, error and approval states.

    A reviewable product prototype
  3. Validate and specify

    Collect structured feedback and refine the design. Document components, responsive behaviour and acceptance details for engineering.

    Design decisions and implementation guidance

User tasks → information architecture → interaction model → component system → engineering handover. AI experiences include uncertainty, evidence, review and recovery states in their design.

  • User journeys and task models
  • Interactive product prototypes
  • Design system and interaction states
  • Usability findings and engineering handover

Make assumptions visible through a prototype, then use the learning to shape what the engineering team should build.

  • A prototype demonstrates intended behaviour; it does not provision integrations or establish production performance.
  • Research coverage depends on access to suitable participants; assumptions remain visible when direct research is unavailable.

Bring to discovery

  • Target users and business objectives
  • Existing research, content and brand assets
  • Access to stakeholders and representative users
Can you design within our existing brand or design system?

Yes. We assess the current components and constraints, reuse what works and document any extensions needed for the product.

Can the same team build the design?

Design can lead into a custom engineering engagement or be handed to your team with agreed specifications and review support.