# Innovation Research

> Consolidate innovation research into evidence-based product and brand inputs for software projects. Use when Codex needs to organize raw notes, interviews, documents, market observations, user problems, solution hypotheses, differentiation, risks, validation gaps, and strategic briefs that will feed branding, style guides, frontend presentation layers, product pages, pitch material, or UX direction for any software product.

- Skill: `b-holanda/innovation-research` (Agent Skill)
- Install (CLI): `npx skillmds@latest add b-holanda/innovation-research`
- Raw SKILL.md: https://api.skillmd.com/api/skills/b-holanda/innovation-research/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: b-holanda (https://skillmd.com/u/b-holanda)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/b-holanda/innovation-research

---


# Innovation Research

Transform raw research, notes, conversations, product ideas, documents, and discovery material into a clear evidence base for software innovation decisions.

This skill prepares strategic inputs for:

- product positioning;
- brand strategy;
- visual direction;
- frontend or view-layer messaging;
- landing pages and product pages;
- pitch narratives;
- user research follow-up;
- software product discovery.

## Core Principle

Innovation research is not decoration or filler. It should reduce uncertainty and help future brand, product, and interface decisions stay grounded in evidence.

Every important claim should distinguish what is known, inferred, assumed, or still missing.

## Evidence Rules

Never invent:

- sources;
- market size;
- competitors;
- interviews;
- customer validation;
- technical results;
- user preferences;
- usage metrics;
- partnerships;
- regulatory constraints;
- product maturity.

When evidence is missing, say:

> There is not enough evidence in the available material. Treat this as a hypothesis that requires validation.

## Classification Labels

Classify important information as one of:

- User-provided fact;
- Documented evidence;
- External evidence;
- Reasonable inference;
- Strategic hypothesis;
- Requires validation.

## Workflow

### 1. Gather Available Material

Look for useful context in:

- user prompts and pasted notes;
- repository documentation;
- product briefs;
- research summaries;
- interview notes;
- analytics notes;
- support tickets;
- competitor notes;
- frontend copy or UI screens;
- existing brand or style documents.

If no source files exist, work from the user's supplied material and mark the result as preliminary.

### 2. Organize by Strategic Area

Group the material into:

- problem;
- target users;
- current alternatives;
- solution;
- product behavior;
- technical approach;
- innovation angle;
- differentiation;
- adoption barriers;
- trust barriers;
- business context;
- brand implications;
- presentation-layer implications;
- risks;
- validation gaps.

### 3. Create an Innovation Brief

Answer:

- What problem is being solved?
- Who has this problem?
- What does the product do?
- Why is this meaningfully different?
- Why should users trust it?
- What is the current maturity level?
- What must be validated next?
- What should the brand and interface make immediately clear?

### 4. Build an Evidence Map

Use this format for important claims:

| Claim | Source | Classification | Confidence | Notes |
| --- | --- | --- | --- | --- |

Confidence levels:

- High;
- Medium;
- Low;
- Unvalidated.

### 5. Identify Gaps

Map missing information:

| Gap | Impact | Priority | How to validate |
| --- | --- | --- | --- |

Use priority levels:

- Critical;
- Important;
- Useful later.

### 6. Prepare Handoffs

Prepare compact inputs for:

- `branding-strategy`;
- `style-guide`;
- frontend or view-layer implementation;
- landing page or product page copy;
- pitch or sales narrative;
- user validation tasks.

## Output Format

Use the sections that fit the task:

## Executive Summary

## Consolidated Brief

## Problem

## Target Users

## Current Alternatives

## Solution

## Innovation Angle

## Differentiation

## Trust and Adoption Barriers

## Evidence Map

## Hypotheses

## Gaps

## Risks

## Validation Plan

## Inputs for Branding Strategy

## Inputs for Style Guide

## Inputs for Frontend or View Layer

## Quality Criteria

A good output from this skill should:

- reduce ambiguity;
- separate facts from hypotheses;
- expose weak evidence;
- make the product easier to explain;
- prepare brand and visual decisions;
- support software frontend or presentation-layer work;
- list concrete validation actions.