Peak Recurrence

How do I find the problems that keep coming back?

Open Peak Recurrence. Peak reads customer feedback, tasks, blockers and leaks from the last 90 days and shows patterns in the radar from at least three similar incidents, with evidence and confidence. You confirm what's real and dismiss the rest.

1. 01Open Peak Recurrence. The radar shows what Peak found.
2. 02If something is missing, record incidents via “Record incident”. As you type, Peak shows similar known problems.
3. 03On a pattern, expand “Why Peak considers this a pattern” and check the incidents.
4. 04“Is a real problem” creates it and assigns the incidents.

What do I enter when recording an incident?

Only “What happened?” is required. Then come date, area, severity (minor, noticeable, severe), product from Peak Products, client, known costs and hours of rework. With “Assign”, you let Peak look for the pattern, attach the incident to a known problem or create a new one.

1. 01Open Peak Recurrence → “Record incident”.
2. 02Briefly describe what happened. If “We may already know this.” appears, check the suggestion.
3. 03Add what you know. Costs and hours make the score more accurate.
4. 04Click “Record incident”.

How do I set up a fix and measure whether it works?

On the problem's page under “Fixes”. You describe the structural change, the reduction at which it counts as a success and over how many days it's measured. Approving records the decision in Peak Log, and “Start measurement” with the implementation date begins the comparison with the period before.

1. 01Open the problem → Fixes: enter the change, type, expected effect, “Success from reduction (%)” and “Measure over (days)”, then click “Propose fix”.
2. 02Click “Approve”.
3. 03Choose “Implemented on” and click “Start measurement”.
4. 04After the measurement window: “Record result”. If the fix does harm, “Roll back”.

How do I merge two identical problems?

Open one of the two problems, choose the other one at “Is the same as …” and click “Merge”. Peak also shows possible duplicates in Radar. You reassign individual incidents by detaching them from the problem and assigning them elsewhere. Splitting one problem into two isn't possible yet.

When does Peak detect a pattern, and can I change that?

The default is 3 similar incidents in 90 days; severe incidents count sooner. In Radar under “Detection settings”, you change “From how many incidents” (2 to 20), the “Period in days” (30 to 365) and the “Rework hourly rate” (default €60), which Peak uses to convert hours into costs.

When is a recurring problem considered solved?

Only once a fix has been implemented, its measurement window has passed, recurrence is below the fix's threshold and there has been no serious incident in the last 14 days. The problem then goes under observation; only after the whole observation period without a relapse is it considered permanently eliminated.

How is the recurrence score calculated?

From six parts with fixed weights: frequency 25, impact 25, cost 20, persistence 15, acceleration 10 and breadth 5. If a part is missing (such as cost), the score calculates with the rest only and says what's missing. The breakdown is shown on every problem.

Can I turn a fix into a task, commitment or experiment?

Yes. Under “Task, commitment or experiment for this” on the fix, you create a task in Peak Work, commit to the fix by a date as a commitment, or link an experiment from Peak Experiments. There's one commitment per fix.

How does Peak Recurrence find the cause of a problem?

Peak suggests hypotheses from product, area, weekday, shared terms and changes in Peak Log, and counts live which incidents speak for and against them. You record your own hunches under “Patterns and causes”, along with how you'll test them. A change shortly before the incidents is a hint, not proof.

What does “The problem recurred after it was resolved” mean?

A resolved or watched problem was reopened, and you're the owner. Compare the new incidents with the old cause: did the fix only address a symptom, or has something new happened? You set how many new incidents reopen a problem on the problem itself at “Reopen from (incidents)”.