Why Product Signal
Most product teams
don't struggle
with execution.
They struggle with clarity.
Product Signal was created to help founders and product teams make more intentional, evidence-backed decisions — before a single line of code is written.
The problem
The pattern I kept seeing
Working across product design, product strategy, user research, and software development, the same pattern kept appearing — in early-stage startups, in growing teams, in mature organisations.
The teams weren't slow. They weren't unmotivated. Most of them were genuinely capable people working hard on real problems. But something was consistently missing.
Assumptions stayed hidden.
Teams shipped based on beliefs they'd never written down, let alone tested.
Research changed nothing.
Insights were gathered, decks were presented, and then the original plan continued anyway.
Confidence without evidence.
Roadmaps were full. Priorities felt clear. But the underlying reasoning was fragile.
Speed without clarity.
Teams moved quickly — into the wrong things. The cost showed up weeks or months later.
These aren't execution problems. They're thinking problems. And most tools aren't built to address them.
The purpose
Why I built Product Signal
Most tools help teams execute faster. Very few help teams think more clearly.
Product Signal was built to fill that gap — to make product thinking visible, structured, and accountable before execution begins.
Visible
Decisions, assumptions, and evidence written down in one place — not scattered across Slack threads and meeting notes.
Structured
A consistent format that surfaces the reasoning behind every decision, not just the outcome.
Accountable
Clarity about who owns the decision, what it was based on, and what success looks like.
Better decisions come from better assumptions. Better assumptions come from better evidence. That's the loop Product Signal is designed to support.
The foundation
Core principles
These are the beliefs that shaped every design decision in the product.
- 01
Assumptions should be explicit.
Hidden assumptions are the most common source of wasted work. Making them visible is the first step to making better decisions.
- 02
Research should influence decisions.
Evidence that doesn't change anything isn't evidence — it's documentation. Research has value when it's connected to what gets built.
- 03
Evidence matters more than opinions.
Strong convictions held lightly. The goal isn't to be right — it's to find out what's actually true about the problem.
- 04
Clarity is more valuable than speed.
Moving fast in the wrong direction is expensive. A little more thinking upfront consistently outperforms more execution later.
- 05
Better products start with better decisions.
The quality of a product is a reflection of the quality of the decisions that created it. That's where the work begins.
The creator
Why I'm building this
I've spent years working across product design, product strategy, user research, and frontend development. Across those roles — and across the teams I worked with — the problems that cost the most weren't engineering problems. They were decision problems.
Product Signal is my attempt to build the tool I wished had existed. Not to replace the hard work of product thinking, but to give it a more consistent structure — so that the thinking actually happens, and the reasoning doesn't get lost.
The product
What Product Signal does
A small set of focused tools, each designed around a specific part of the decision-making process.
Decision Board
A structured workspace for defining the problem, listing assumptions, attaching evidence, and writing a clear decision.
Research Distiller
Turn raw interviews, notes, and signals into concise, usable insight that actually connects to a decision.
Clarity Feedback
Surface weak reasoning before it becomes a weak decision. Identify where the thinking needs more work.
Decision Timeline
A chronological record of how a decision evolved — what changed, when, and why.
Decision Library
A searchable archive of past decisions. Context for future decisions, and a record of how the team thinks.
A different way to think about product decisions
Most product problems begin long before code is written. They begin in the assumptions that were never examined, the evidence that was never gathered, and the decisions that were made without enough clarity.
Product Signal exists to help teams think more clearly before execution begins — so the work that follows is grounded in something real.