# How to Propose Changes
# Needs Analysis
A framework for capturing the needs of a stakeholder.
# SCQH (Situation, Complication, Question, Hypothesis)
A framework for identifying the root causes of an adverse situation, and to propose solutions.
A framework for proposing significant changes. It gives everyone the opportunity to voice their opinions.
The key goals of this method are:
- Give people the opportunity to propose significant changes.
- Give people the opportunity to voice their opinions – positive or negative towards the solutions proposed.
- Enable people to act fast – but not too fast.
- Provide a standard method for asking feedback intra and inter-projects.
We store Datopian RFCs in the form of issues in https://gitlab.com/datopian/tech/rfcs/-/boards.
This is a recommended process, not necessarily a format. Sometimes, you might want to even complement it with a Needs Analysis, or an SCQH.
Remember to give time for people to give feedback – and be explicit about the deadline. Sometimes, given to adverse and external deadlines, the time for collaboration may be quite tight. In those cases, authors should be accountable for the implementing without full collaboration.
# Recommended sections
In this section, you should give enough context for people to understand why you are proposing these changes. Consider that not everyone will be working in the same project as you.
In this section, you should describe what you are proposing. Talk about how it addresses the points in “Needs.” Here, you are describing a design proposal, so be objective. The idea is not to share opinions (“The communication happens via RPC”, not “RPC is better because […]”)
In this seciton, feel free to add all the subjectiveness. Why do you believe this solution is the best one for the problems?
First, describe what happens if we don’t do nothing. Sometimes, this could be a reasonable alternative. Only later, consider other options.