Do we need to know the cause before contacting SG?
No. Finding the cause is part of the evaluation. One recent example is enough to begin the conversation.
Understand the problem
SG follows the work from beginning to end, identifies where and why it breaks down, and gives leadership a clear basis for deciding what should change.
This can help: Organizations dealing with a repeated delay, breakdown, or workaround without a clear explanation of why it keeps happening.
When this can help
A repeated delay, missing decision, unreliable file, or avoidable follow-up can provide enough context for the first conversation.
How the work proceeds
Clarify what the work is supposed to accomplish and what a successful result should look like.
Listen to the people involved, observe real examples, and review the information used to complete the work.
Separate the visible problem from the conditions causing it and document the effect on customers, staff, time, cost, or delivery.
Explain what should change, what should happen first, and whether implementation support would be useful.
Common questions
No. Finding the cause is part of the evaluation. One recent example is enough to begin the conversation.
No. SG explains what the facts support. The next step may be a small correction, a defined implementation, further observation, or no additional work.
Find the gap. Build the fix.
Describe what is happening in everyday language. SG will determine whether operational evaluation or another next step fits the situation.