issues-ids

issues-ids — Identify, Discuss, Solve

The loop runs in order. Skip a step and the loop doesn't close.

1. Identify — one line, the symptom, not the solution

Write the issue as one sentence of the symptom. Not the solution. Not the cause. The symptom.

• Good — "Our discovery-call show rate is 40 percent."
• Bad — "We need to switch calendar tools." (That's a solution, not the issue. May not even be the right one.)

If you start at the solution, the discussion argues the solution. If you start at the symptom, the discussion finds the right solution. Most failed issues blocks were misidentified at step one.

2. Discuss — 5-15 minutes, every voice, facts forward

• Time-box. Issues don't get more solvable past 15 minutes; they get more emotional.
• Loudest does not win. Round the room if needed.
• Facts on the table. Emotions are allowed and named — "I'm frustrated by this" — but they don't drive the call.
• Sharpen the question if the discussion drifts. "What are we actually deciding right now?"

3. Solve — one concrete to-do, one owner, one deadline

Every solve ends in one of these:

• A to-do — verb + noun + owner + deadline. Lands in the to-do recap.
• A decision logged — "We're not solving this now. We accept the trade-off of X." That's a real solve; write it down.
• A re-scope — "This is bigger than the issues block; it's a project. Owner takes it offline, reports back next week."

The point — never re-discuss the same issue

If the same issue shows up in five weekly syncs, the prior solve was wrong. Don't keep discussing the symptom. Admit the solve missed; address the root.

A recurring issue is signal that step 1 was wrong (you identified the symptom of a deeper symptom) or step 3 was weak (no real owner, no deadline, no follow-through).

Anti-patterns

• Discuss without identify — people argue at cross-purposes because they're solving different problems.
• Identify without solve — talk shop; no movement.
• Same issue 5+ weeks — the prior solve was wrong; stop re-litigating, address the root.
• Solution disguised as identification — "We need to hire a designer" is not an issue; it's a proposed solution to an unstated issue.
• No deadline on the to-do — it won't happen.

Triggers

Weekly sync issues block. Recurring problem. Two people who can't agree on a path. "We keep talking about this."

Pairs with weekly-sync (the meeting this loop lives inside) and decide from cklph-os (when a solve requires a one-way-door decision).