Hunch

An AI Workspace for the Future of Knowledge Work

An infinite canvas allows users to break down complex work into AI task 'blocks' that AI models are good at, improving AI output and enabling users to work on even more complex tasks.

Role

Principal Founding Product Designer

Challenge

To create an AI workspace that allows users to overcome the limitations of traditional chat interfaces.

Contributions

As the Founding Product Designer of Hunch, I led the development of a groundbreaking AI workspace that allows users to overcome the limitations of traditional chat interfaces.

Impact

I worked with the team to define, research, and develop Hunch's core UX, brand, and visual helping the product establish a core community of engaged users.

Context

I joined the team in early 2023 to work on a data analytics product the team had been developing. Following the release of GPT-4 and other AI advancements, the team decided to explore new strategic directions that integrated AI into the core UX, enabling users to perform more general tasks, not just limited to data analytics. After this strategic shift, I collaborated with Hunch's founders to explore, prototype, and define the key aspects of the product.

My role as a Founding Product Designer involved driving the product strategy and vision alongside the founders, conducting user research, overseeing the brand & visual design, and designing the core product experience and UX paradigm. As the only designer on the team, I worked closely with the engineers and led continuous discovery and prototyping efforts to validate concepts and enhance key product interactions.

My work encompassed multiple milestones, from product discovery and early product positioning/strategy to subsequent product iterations, community building, and product growth. Over 1.6 years of work, my efforts have helped Hunch evolve from an idea to a product loved by an early community of 1,000 users (and growing). With key aspects of the product offering validated by early beta users, Hunch is now expanding its user base while implementing new features that improve the initial core canvas UX.

Problem

In an era of rapid AI advancement, the interfaces we use to interact with AI lagged behind, constraining the authentic potential of human-ai collaboration. Hunch emerged from two crucial insights: first, that AI's capabilities far exceed what current chat interfaces allow, and second, that elite knowledge workers and AI early adopters were eager to leverage AI more effectively to automate and accelerate their existing tasks.

Linear Interaction Paradigms: Traditional chat interfaces force users into a sequential mode of communication, unsuitable for multifaceted problems that require parallel processing or iterative refinement.

Limited Control Over AI Reasoning: Users cannot fine-tune AI processes or provide nuanced context, often leading to suboptimal outputs that require multiple revisions.

Inefficiencies in Reusability and Sharing: There's no straightforward way to reuse or share AI workflows and prompts, leading to duplicated efforts across teams and projects.

Inability to Leverage Multiple AI Models Simultaneously: Users can't easily harness different AI models' strengths within a single workflow, limiting the potential for more sophisticated problem-solving.

The Block System

Ultimately, we chose a flow-based language paradigm, implemented through an infinite canvas where users could create and connect "blocks" representing AI tasks and data. Each block wraps a function, from processing information like AI blocks or storing data. While flexible and powerful, each block feels familiar, like a Notion page or Google Doc.

When blocks are connected, the canvas compiles all the information from the connected content blocks into a single prompt that is sent to the AI model. This allows for complex context to be provided without cluttering individual blocks.

At the core of Hunch's interface is a block system:

Content blocks: serve as static containers for contexts—such as company information or problem specifics—that can be connected to AI blocks, keeping instructions clean and workflows organized.

AI Blocks as Actuators: Each block receives input, processes data using specific AI models, and passes output to other blocks.

Complex Tools: Some blocks encapsulate multiple AI/Code operations but are exposed as simple, user-friendly units, allowing users to achieve more.