Describe the problem in the user’s words
Explain briefly who a solution is for and which task it makes easier. The user’s device, language, internet access and daily habits should inform the design.
Learn from a small pilot
Feedback on an initial prototype can help a team understand how an idea works in practice. Define the scope of a pilot, participation conditions and any information collected in advance.
Start a collaboration conversation
If you have a local solution for a social need, send CHARE a short introduction. Describe the intended user, the problem you address and the collaboration you propose. Do not share personal user information in your initial message.
Accessibility starts with the first version
A service is useful when people can use it, not simply when it contains many features. Check text on a small screen, understandable buttons, keyboard navigation and behaviour on a slow connection. Clear Azerbaijani copy should be supported by equivalent information in other offered languages. Consider why each form field is necessary. An unfinished application may reflect a confusing or difficult step rather than a lack of interest in the service.
Test a simple journey first
A first test may not require a complete platform. Can someone describe their need, find the relevant information and understand what to do next? A limited trial with a few participants can help clarify these questions. Explain the purpose and information to be collected beforehand. Seek permission, make room for honest feedback and avoid overstating the findings. These practices matter as much as the technical implementation when a service is intended to support people.
Collecting less is a design choice
Every additional field asks for time and trust. If an introduction only needs a short description and a contact channel, avoid requesting sensitive records at that stage. Explain who will receive the information, why it is needed and what happens after submission. Make transitions to third-party registration and messaging services visible. Privacy is not only a long policy: it also depends on understandable choices throughout the everyday experience of using a service.
Present a local solution
When writing to CHARE, include the solution’s name, intended users, the task it makes easier and its current stage. Distinguish a concept from a working prototype or an established product. You can include a short description or demonstration link containing no personal user information. Consider maintenance, supported languages, device compatibility and future support. A useful first conversation connects a clearly described need with a proposed solution, without claiming impact that has not yet been demonstrated.