Explore the entire PULSE workflow — no approval needed to switch stagesChoose any tab at any time. Edit your draft in any order; approval gates are optional demo sign-offs, not page locks. Draft inputs are saved locally in this browser.
ALL 4 STAGES OPEN
01 · MONITOR — Review performance, capture a signal and add initial hypotheses.

Continuous Product Lifecycle Management

Product Health Dashboard

Turning product performance into actionable signals.

Demo snapshot · 27 Sep 2026
MTD is compared with the same days last year.
VIEW PERFORMANCE

Portfolio overview

Click a product to explore its performance ↓

Product performance

Selected category

Signal screening

PM review

Reading the signal

Priority observations

PM Diagnosis Brief

    Hypotheses are not validated root causes. Consumer research belongs in Diagnose.

    01A / SIGNAL CAPTURE

    Signal Intake & Hypothesis Brief

    Capture automated red flags and subjective weak signals. Separate what is observed from what is assumed, then decide what must be checked before opening a PM diagnosis project.

    Input + stage-gate review

    What signal did we observe?

    What should we validate?

    Market growth (dummy): —Growth vs market: —

    Hypotheses are available immediately in Diagnose, even if Gate 1 is still a draft. Neither a signal nor internal feedback proves the root cause.

    Gate 1 · Open Diagnosis

    Optional: record a formal review of signal relevance, evidence needs and scope. All tabs stay accessible.

    DRAFT

    OUTPUT · PM Diagnosis BriefSignal classification, source, observations vs assumptions, verification checklist, initial hypotheses and documented gate approval.

    PULSE 02 / DIAGNOSE

    From signals to validated insights.

    Lead a focused PM project: define the performance issue, develop competing hypotheses, review existing evidence, and run targeted consumer research where the evidence is insufficient.

    Diagnosis not started
    PRODUCT IN FOCUSSelected product signalLast 3M · illustration

    1. Identify the issue

    2. Formulate hypotheses

    These are potential causes — not verified root causes. Select each hypothesis you want to investigate.

    Diagnosis workflow

    Initial hypotheses captured in Monitor flow into Step 3 below. Define how to test them, collect findings in Step 4 and record one clear PM decision in Step 5.

    What happens next
    03 · Hypothesis validation & research method
    04 · Findings and evidence log
    05 · PM diagnosis decision & sign-off

    02A / HYPOTHESIS VALIDATION

    3. Validate Hypotheses from Monitor

    Choose which initial hypotheses to test, select the most suitable research method and plan the validation. The competing hypotheses in Step 2 are optional.

    Research plan & validation setup

    Gate 2 · Authorize Research

    Optional: record resource authorization before actual fieldwork. Demo research and draft findings can be explored anytime.

    DRAFT

    Consumer research tracker

    No timeline0 evidence items

    A completed research task does not automatically validate a hypothesis. The conclusion must specify what the evidence supports, contradicts, or leaves unresolved.

    02B / EVIDENCE RECORD

    4. Research Findings & Evidence Log

    Record what research actually found and attach a source link when available. Every finding remains linked to the hypothesis being tested.

    3 / 5

    Evidence collected

    No evidence recorded.

    02C / PM DECISION

    5. Diagnosis Conclusion & Proposed Decision

    Summarize what the evidence says, decide whether the hypothesis holds and determine the next step. One conclusion, one decision and one sign-off.

    Prioritization · illustrative judgment, not a forecast

    3 / 5
    3 / 5
    3 / 5
    60/100 · Prioritization index
    50% potential impact + 30% urgency + 20% evidence confidence

    This score helps structure a decision. It does not establish causation or quantify the actual monetary impact.

    Gate 3 · Evidence Sign-off / Go–No Go

    Optional formal sign-off of collected evidence and the proposed next step; browsing Plan is always available.

    DRAFT

    OUTPUT · Evidence-backed DiagnosisTested hypothesis, logged research, conclusion and confidence, business priority, sign-off and improvement direction.

    PULSE 03 / PLAN

    Design the right improvement.

    Use the diagnosis to choose an intervention, assess its expected value and feasibility, and define a clear product improvement plan before committing resources.

    Awaiting diagnosis
    PRODUCT IN FOCUSSelected product signalLast 3M · illustration

    1. Develop improvement options


    2. Prioritize the intervention

    Use a simple editable demo comparison. These are hypotheses about potential interventions, not measured financial forecasts.

    3 / 5
    2 / 5
    4 / 5
    —
    Illustrative decision index / 100
    Impact, evidence, feasibility, urgency and capability at equal weights. Directional discussion tool, not a causal impact estimate.

    3. Define the Product Improvement Plan

    Make the next move specific enough to execute cross-functionally.

    Sign off the demo diagnosis before approving this action plan.

    03A / IMPROVEMENT PLANNING

    Scope, Feasibility & Impact Scenario

    The suggested interventions above are illustrative. Add a custom option if your research leads to a different recommendation.

    Diagnosis not yet signed

    Define the intervention


    Feasibility & capability

    3 / 5
    3 / 5

    Feasibility includes time, resources and capability. Rate capability separately so cross-functional resource gaps remain visible.

    What could this improvement add to sales?

    Simple example: if current sales are Rp 10 billion and the improvement adds 3%, that is Rp 0.3 billion in possible additional sales. This is an assumption for discussion, not a forecast.

    —Possible additional sales (Rp billion)
    Current sales × assumed uplift ÷ 100. Illustrative only; not a forecast.

    Execution timeline

    Gate 4 · Approve Improvement Project

    Approve the intervention, objective, lead, supporting teams, feasibility, budget, timeline, risks and expected impact before execution. Define success KPIs in Execute.

    DRAFT

    OUTPUT · Signed Product Improvement PlanEvidence-based improvement option, feasibility and business impact scenario, project lead, supporting functions, timeline, budget and risks. Success KPIs are set in Execute.

    PULSE 04 / EXECUTE

    Turn the plan into measurable action.

    The PM coordinates cross-functional delivery, resolves blockers, documents outcomes, and hands results back to Monitor for the next product health review.

    Execution preview · Draft
    PRODUCT IN FOCUSSelected product signalLast 3M · illustration

    1. Cross-functional execution tracker

    You can preview this stage before completing or approving your plan.

    Implementation progress0 / 4 milestones
    Start by completing Diagnose and Plan.

    2. Project control & issue log


    3. Close execution & hand back

    Completing execution does not automatically prove business impact. The next Monitor review compares actual results against the pre-agreed KPI and target.

    04A / CROSS-FUNCTIONAL CONTROL

    Kickoff, Milestones & Resource Links

    Control project delivery and hand off the final outcome to Monitor. PM coordinates improvement projects; BAU commercial metrics remain owned by the relevant functions.

    Awaiting approved project

    Project resources

    Kickoff deck
    Project timeline
    Action tracker
    Research/evidence

    Milestone dates & owners

    Success KPI & outcome review

    No approved project objective yet.

    Record measured outcomes rather than assuming that an implemented project improved sales.

    Gate 5 · Close Project & Return to Monitor

    Confirm completion, recorded results, learning and the next KPI review date.

    DRAFT

    OUTPUT · Executed Improvement + Monitoring HandoffCross-functional delivery, links, milestone ownership, logged results and a follow-up review without assuming growth impact.
    Demo assumptions & KPI definitions

    All figures are illustrative dummy data, loosely sized to represent three different Kahf face-care formats; they are not company results, market research, or performance forecasts. Sales are dummy net sales in Rp billions. MTD = Sep 1–27, 2026 vs Sep 1–27, 2025. L3M / L6M / L12M include the partial Sep MTD and compare with matched months of the prior year. Growth vs Target (pp) = actual period YoY growth minus dummy period growth target; the target is weighted using last-year sales. Availability = average on-shelf availability in selected period; Rating = illustrative consumer rating; Complaint Rate = dummy verified complaints per 10,000 sold units. Thresholds are illustrative and must be calibrated with actual company data. All example hypotheses, research outputs, and proposed interventions in subsequent steps are fictional illustrations, not validated findings. The dashboard detects signals; it cannot establish the cause of an issue.