Gather

Problem

Conventional computer and phone apps weren't enabling collaboration the team wanted to see. The hypothesis: an interactive tool (rather than a software app) would make collaboration more efficient because interfaces should adapt to the environment, not the other way around.

Process

Three rounds of prototyping, each one teaching a specific lesson:

1. First prototype — used physical buttons and widgets. Felt too restrictive. Key takeaway: rigid hardware-style inputs forced users to bend to the tool. Interfaces should adapt to the environment, not vice versa.
2. Second prototype — replaced buttons with widgets and used tokens for registration. Redesigned for a more interactive collaborative experience.
3. Final prototype — improved interaction feedback, replaced fixed buttons with pen-like controls, and kept the Journey system visible at all times for better navigation. The goal was to simplify the experience and improve user understanding.

Detail throughout: an onboarding pattern that walks users step-by-step so they always understand what to do next.

Outcome

Gather is positioned as an interactive collaboration tool with:

• Pen-like controls (instead of fixed buttons)
• A persistent Journey system for navigation
• Token-based registration
• Step-by-step guidance baked into the experience

The product has a "Try it now" / fullscreen embedded demo on the live site.

Self-critique / next iteration

The author notes that if they could improve one thing, it would be making the design pages more fluid.

What was learned

Clear planning and open communication are critical in team projects — without them, even well-crafted work can fail to gain acceptance.