July flash sale
The month after ICP-ACC matters because classroom insight fades quickly when normal work returns. The goal is not to perform a dramatic coaching transformation. It is to build a repeatable loop: contract, practise one behaviour, collect feedback, reflect without exposing confidential material, and try again.
Use this plan after ICP-ACC certification training or as preparation for a class. Keep the practice within your competence and role. Consent matters: colleagues should know when you are coaching, mentoring, facilitating or observing rather than becoming unwitting practice clients.
Week 1 — make your stance visible
- Review three recent conversations and mark where you coached, mentored, taught, facilitated or directed.
- Notice one default stance you use when anxious or rushed.
- Contract explicitly for two short conversations.
- Ask the other person what helped them think and where you took over.
Do not try to eliminate advice. Practise asking permission before giving it and naming the switch: “I have an example from a similar team. Would mentoring be useful, or would you prefer to keep exploring your options?”
Week 2 — listen before you design the question
Run three 12-minute practice conversations. For the opening three minutes, only reflect, summarise and clarify. Notice how often your mind creates a solution. Record the trigger and return attention to the client's words.
| Practice evidence | Healthy signal | Warning signal |
|---|---|---|
| Contract | Client names the useful outcome | Coach supplies the agenda |
| Listening | Questions follow client meaning | Coach waits to insert a prepared question |
| Ownership | Client chooses the next step | Coach assigns action through a question |
| Feedback | Specific behaviour can be retried | Feedback labels personality |
| Confidentiality | Notes contain learning, not private detail | Practice log becomes a client dossier |
Week 3 — work with a team pattern
Choose one observable pattern with the team's agreement: decisions return to the Scrum Master, risk appears late, one role dominates refinement, or retrospectives avoid a recurring issue. Share the observation tentatively and invite the team to decide whether it matters.
Help the team design one small experiment. Do not promise that coaching alone will change a condition controlled by staffing, incentives, architecture or leadership. Escalate system constraints through the appropriate route while preserving team agency where it exists.
Week 4 — integrate and choose the next edge
- Repeat one conversation from week one with the new behaviour.
- Ask a trusted observer for feedback against a single criterion.
- Review the team's experiment and separate evidence from your preferred story.
- Choose one capability for the next 30 days.
- Arrange peer practice, mentoring or supervision rather than learning alone.
Keep a reflection log that protects people
Record the situation type, your intention, the stance used, an observable moment, feedback received and what you will test next. Remove names, company identifiers, customer data, health information and performance allegations. Reflection should improve the coach without creating a shadow personnel record.
What success can look like after one month
You may notice fewer disguised suggestions, clearer agreements, longer listening, more deliberate stance changes and better feedback. The people you support may make more of their own decisions or surface a hard issue earlier. Do not expect thirty days to prove that you caused delivery outcomes across a complex system.
Use the active listening practice lab during week two and the team versus individual coaching guide during week three. The plan becomes valuable through repetition, not completion marks.
