01
State the proposed relationship, not just the activity
Write a sentence connecting the intended audience, the proposed activity and the reason it might be useful. In the fictional example, the team might propose short practical workshops for people who want to try a skill before committing to a longer course. That is more discussable than a plan to run events. Keep the sentence narrow enough that a colleague can ask what would support or weaken it. Avoid claiming demand or likely results without evidence. The sentence is a proposal to examine, not a conclusion already established.
02
Separate supporting observations from assumptions
List the reasons behind the idea and identify where each comes from. A conversation with a few interested people is a different kind of support from a completed trial, and neither should be described as something it is not. In the workshop example, the team may know that several people asked about a topic but still be assuming that evenings suit them. Put that assumption in the record. This lets the discussion focus on which questions matter instead of allowing a polished proposal to make every uncertain detail sound settled.
03
Name the question that should be answered next
Choose a useful next enquiry and explain how its answer would affect the proposal. The workshop team might need to clarify the intended participants, the practical constraints or which topic deserves a small trial. Also ask what information would cause the team to revise or abandon the current version. Keep alternatives visible, such as a different format or time. A clear thesis helps people make progress because it can change in response to what they learn, while preserving a record of why the project was proposed in the first place.