Issue

What it means

Issue is a business problem or unresolved point that blocks a better decision. It is not the same as an action, a task, or a broad initiative. A good issue statement names what is happening, who is affected, why it matters now, what evidence supports it, and what decision depends on resolving it. In YogoQ textbook work, issue is the starting point: first clarify the issue, then choose the action plan, owner, and review signal.

What counts / what does not

Issue has a narrower boundary than a goal, initiative, or task. Include | Unresolved problems, risks, questions, contradictions, or blockers | These require clarification before action Exclude | The chosen action, owner assignment, or final target | Those belong to action plan, initiative, task, or goal Document | Evidence, affected scope, decision dependency, and urgency | Makes the issue actionable

What moves the number

The strength of an issue depends on clarity, evidence, and consequence. Clarity | The issue can be explained in one sentence | Reduces scattered discussion Evidence | The issue has observable support | Prevents opinion-only escalation Consequence | The issue blocks a decision or result | Helps prioritize which issue to handle first

When it helps

Issue improves decisions by turning a vague concern into a named problem. Problem framing | States what is wrong or uncertain | Prevents jumping to solutions before the problem is clear Evidence | Names observable facts, examples, or signals | Separates a real issue from a preference or complaint Decision dependency | Shows what cannot be decided until the issue is resolved | Makes next action and ownership clearer

• Problem framing | States what is wrong or uncertain | Prevents jumping to solutions before the problem is clear
• Evidence | Names observable facts, examples, or signals | Separates a real issue from a preference or complaint
• Decision dependency | Shows what cannot be decided until the issue is resolved | Makes next action and ownership clearer

How to use it

• Write the issue as a problem or question, not as the solution you already prefer.
• Name the affected customer, process, team, or metric so the scope is visible.
• Record the evidence and the assumption separately so the team can test them.
• Connect the issue to the decision that must be made next.
• Close or reframe the issue when evidence changes, instead of letting it become a permanent label.

Example

A team says, 'activation is low.' As an issue, they rewrite it as: 'New managers do not complete the first workflow because the setup step is unclear; this blocks the onboarding target for the month.' The statement names the affected user, the observed problem, the suspected cause, and the decision it blocks. Only after that do they choose an action plan: revise the setup copy, assign an owner, and review activation data next week.

Compare with

Compare Issue with the terms it is often confused with. Issue | Problem or unresolved question | Use before selecting the response Action Plan | Chosen set of actions | Use after the issue is clear Initiative | Broader effort or program | Use when several actions must be coordinated over time

Common mistakes

• Misconception | Any topic is an issue | A real issue has tension, uncertainty, or a decision dependency
• Misconception | Naming the issue is the same as solving it | Resolution still needs an action plan and owner
• Misconception | Bigger wording creates a better issue | Narrower wording usually makes action easier

Frequently asked questions

Sources

Related topics