Explorations

Questions before products.

An exploration is a structured investigation into a recurring problem. It becomes a product only when the evidence supports a focused solution and a meaningful audience.

Research board

Current themes

All themes are observing only. No customer evidence, commercial validation, or product commitment is being claimed.

Observing

Repetitive work still managed through spreadsheets

Repeated copying, checking, and reconciliation can turn a flexible spreadsheet into a fragile workflow.

Audience: Small teams using spreadsheets as operational tools
Evidence: A research theme only. No validated opportunity or product claim yet.
Decision: Continue observing recurring patterns and the cost of workarounds.

Last updated Aug 6, 2026

Observing

Fragmented workflows across multiple tools

Important context can become scattered when a process crosses several tools, inboxes, and hand-offs.

Audience: Teams coordinating work across disconnected software
Evidence: A research theme only. No validated opportunity or product claim yet.
Decision: Look for repeated hand-off failures and measurable coordination costs.

Last updated Aug 6, 2026

Observing

Reporting and coordination bottlenecks

Routine reporting can depend on chasing inputs, normalising formats, and rebuilding the same view each cycle.

Audience: Operators responsible for recurring updates and internal reporting
Evidence: A research theme only. No validated opportunity or product claim yet.
Decision: Observe frequency, urgency, and where existing tools fall short.

Last updated Aug 6, 2026

Observing

Manual processes that consume small teams’ time

Necessary but repetitive tasks can quietly take time away from customer work and higher-value decisions.

Audience: Small teams with recurring administrative or operational work
Evidence: A research theme only. No validated opportunity or product claim yet.
Decision: Identify tasks that are frequent, consequential, and poorly served.

Last updated Aug 6, 2026

Status key

Progress is an evidence standard.

A status describes what is known and which decision is active. It is not a marketing label.

Observing

A recurring pattern is interesting enough to watch more closely.

Gathering evidence

The pattern has earned structured conversations and closer measurement.

Validating

A specific problem and audience are being tested against clear decision criteria.

Building

Evidence supports a small, useful product test.

Archived

The evidence did not support continuing, or conditions changed.

A useful stop

Some explorations will be abandoned.

That is part of disciplined product discovery. A weak signal, a low-consequence problem, a preferred workaround, or a poor path to a focused solution can all be good reasons to stop before building.

Open research channel · 01

Have a recurring problem worth investigating?

Tell us about work that is frustrating, repetitive, expensive, or unnecessarily manual. A useful description is more valuable than a polished pitch.

Share the problem