Use the GROW model to give practical and technical support and guidance
What's a current challenge you have?
Say things like "tell me more or in what way or because"
Say back what the person has said
Get them to Yes in either words, tone or body language
Alright, thanks for sharing, so let's set a GOAL?
Can you think of something more SPECIFIC (give two options) (SMART)
Is that REALISTIC/ACHIEVABLE? (SMART)
Can you put a TIME on it? (SMART)
Throughout the whole process, open-ended questions, positive, honest and reflecting back what's been said?
After we set a goal, ask, what is your current REALITY/SITUATION?
Any OBSTACLES
What is the WAY FORWARD (make some choices/decisions)
*No giving advice or leading questions.
Suggested assessment
role play supported by video recording or observation
GROW model (Whitmore, 1992):
• goal setting: agreeing and understanding the goals for the task
• reality checking: identifying the current situation, what resources are required
• options/obstacles: exploring the options, solutions or barriers to help resolve the task
• will/way forward: defining actions and agreeing timescalesThan
S.M.A.R.T Goals
Specific
Measurable
Achievable
Realistic
Time - bound
The GROW (Goal - Reality - Obstacles - Will) model is a structured way to tackle problems and challenges.
Let's break it down into each of its four stages:
Practical Support: Make sure you clearly understand the goal. Is the goal to improve customer service response time? Reduce software bugs? Increase sales? Have a one-on-one discussion with the person needing support to make sure you're on the same page.
Technical Guidance: If the goal involves a technical task like deploying a new software update, specify metrics. For example, "We aim to reduce the downtime during updates by 50%."
Practical Support: Take stock of the current situation. Do you have enough staff? Is your technology up-to-date? Are there any budget constraints?
Technical Guidance: Evaluate the technical resources at hand. Do you have the necessary hardware and software? Is additional training needed for the team? Are there any security considerations?
Practical Support: Discuss possible paths to the goal. Maybe you could offer staff training, update hardware, or streamline processes. Also, identify any roadblocks like financial limitations or resistant team members.
Technical Guidance: In tech terms, could automating a process be a solution? Or maybe using a different coding methodology? Point out any technical barriers like incompatible software or lack of technical skills in the team.
Practical Support: Decide on a plan and timeline. Who is responsible for what, and by when should it be done? Make sure everyone involved knows their role.
Technical Guidance: Set up technical milestones. For example, "We'll complete the first stage of the software upgrade by next week." Assign technical tasks to team members based on their skills and expertise.
In summary, the GROW model helps you to set clear goals, understand your current resources and limitations, explore possible solutions and their pitfalls, and finally, create a concrete plan of action with deadlines. It's like a roadmap for solving problems!