What you are asking for
You want the team to understand real use better. Someone asks for an example or a customer conversation, but the route to getting one is unclear.
What the system hears
If every request means rebuilding the agreements, the preparation and the access, learning from the field becomes hard to plan.
What that produces
Useful access takes means and a frame. The people who own the customer relationship can arrange the conversations, explain the context, and avoid repeated approaches. They are not an obstacle to route around. Some access has to stay limited: files can hold personal or confidential information, or information with no bearing on the question. Opening the whole support queue to the whole team is not the only way to learn. Prepared cases, suitable access, or an accompanied observation may be enough.
Direct contact needs people’s consent and preparation time. Make clear the purpose, the duration, what will be recorded, and what can be promised. How much support is needed depends on experience and context; one first call does not guarantee that all help becomes unnecessary afterwards.
To grow the team, make that route understandable and plan the time of the people who organise it. If you back the project without deciding on access, you can help shape the request, or offer an introduction both sides accept.
Do not read a lack of curiosity off the number of calls made. A person may be getting good feedback by other routes, or meeting real constraints. What counts is knowing which question was informed and what is still uncertain.
The decision
→ With customer relations, choose a useful question and the least demanding way to inform it: a prepared case, an observation, or a voluntary conversation.
→ Say who organises it, the agreements needed, and the time set aside. Give beginners suitable support.
→ After a first attempt, check what the team learned, the effort asked of the participants, and what to adjust.
If access is not possible, name that limit in the decision rather than replacing it with a certainty. Agree another source, or a more cautious choice.
From where you sit
- Customer relations: prepare access that is useful, accepted, and compatible with the commitments.
- Design: state the question and the information needed before asking for access.
- Management: set aside time for the organising as well as for the conversation.
- Support: offer cases with their context and the limits of what they represent.
To discuss
Which route lets us inform a question about use today, and where do we need time or an agreement?