The starting point
You are helping someone take on a piece of work. You know how to break it down, but you also want to let them learn to understand the need and propose an approach.
The move
Share the goal, the context, the limits and the means. Agree together how much of the framing they will take on and what help is available.
Why it works
A precise task can be a good way in to learning: it gives a bearing and caps the difficulty. Explaining why it exists already builds judgement. Handing over a wider problem becomes useful when the person can explore options with enough context and backing.
In a community group, you are supporting someone preparing the welcome for new members. Instead of just giving them the list of messages to send, you look together at what new members have to understand. They propose an approach on a small remit. You can show an example, or think it through with them, if that helps, without turning your own plan into the required answer.
Learning takes time and may need several rounds of feedback. The person may find a better option, or may need a more guided breakdown. Neither of those on its own tells you anything about their motivation. Agree what they can decide, what needs an approval, and how to flag a difficulty.
Do not hold back important information to make the exercise instructive. A demonstration or a prepared question can help without taking the other person’s place. With a tight deadline or serious consequences, cut the exploration and explain that choice. Between peers, you can propose this approach with everyone’s agreement, without claiming authority you do not have.
Try this
Choose a bounded problem. Write down the expected result, the context you know, the constraints, the time available, and the decisions they may make.
Ask what backing would help: an example, a first breakdown together, a check-in, or access to another person. Set that check-in by the need, not by imposing two days of silence. Stay available for an important question.
At the check-in, look at the reasoning and at what the attempt produced. Tell requirements apart from your personal preferences. Agree what they want to take on next and what support is still needed.
From where you sit
- Product: explain the need and the constraints before proposing a solution.
- Management: set aside time for exploration and for the agreed check-ins.
- Support: share a case and accompany a peer’s first analysis.
- Design: offer an example as backing, not as the only acceptable answer.
To discuss
Which small remit would let someone propose their own approach, and what backing are they missing?