AI Store demo

PAIN POINTS AND PROCESS DEEP DIVES

Process Pain Point Finder

Turn observation notes into themes worth investigating. Keep what was observed separate from what might explain it.

Illustrative example

A QUICK WALK-THROUGH

How to use

  1. 01Read the fictional ride-along notes.
  2. 02Run an AI analysis and review the supporting observations.
  3. 03Treat hypotheses as unverified and use questions to guide follow-up.

SAMPLE WALK-THROUGH

Order fulfillment · one fictional ride-along

Fictional notes. Not client evidence.

OBSERVATION LOG

Ride-along notes

Fictional sample
Up to 5,000 characters. Only enter text you are authorized to send to the AI service.0 / 5,000

These notes are invented for the demo. Submitted notes go to the configured OpenAI service and are never sent to PostHog.

WHAT TO INVESTIGATE

A structured readout

Illustrative

Read carefully: observations must be supported by the notes; hypotheses are possible explanations to validate.

COPYABLE PROMPT

Take the analysis into your AI tool

The AI analysis uses the same evidence-first guidance. You can also copy this prompt for another AI tool.

Review the process observation notes below. Use only the information in the notes.

1. Group related observations into a small number of process-friction themes.
2. For each theme, separate:
   - Observations: concise, factual statements with the timestamp or exact note that supports them.
   - Hypotheses: possible explanations, clearly marked as unverified.
   - Questions to investigate: open-ended follow-ups that could confirm, refine, or rule out the hypothesis.
3. Call out missing context and avoid assigning blame or claiming business impact that the notes do not establish.
4. Do not present a hypothesis as a finding or infer client results.

Format the response as: Theme | Supporting observations | Hypothesis to validate | Questions to investigate.

Observation notes:
[Paste notes you are authorized to share here]