An insight, does not always need to framed as a statement. Posting an insight in the form of a question may spark a dialogue that leads to greater learning. The insight may come later as the community responds to the question. If you do post a question, here are some guidelines that I think will enhance learning.

• try to pose open ended high level questions (to spark dialogue)
• state the question in the title
• add additional clarification or context in the body of the post
• add `question` as a tag on your post

While there are no bad questions, certain questions are more appropriate off the platform. For example: I think that time sensitive technical questions and questions directed at one team member should be avoided. If someone finds that these sorts of questions are being asked frequently, then they might reframe the question and post it as an insight or they could summarize the problem in an insight for the benefit of the group.

Example: Jane Doe keeps getting asked mundane questions like "How do I fill out this form?" or "Who do I contact to get this done?". She may eventually decide to reframe these questions as insight like "Permitting is quicker when you work in this way!" then describes her process in an insight post. Jane adds the tag `permit` `efficiency` to the post. Alternatively if Jane doesn't know the answer perhaps she post an insight title: "Why do we struggle with permitting?".

I am curious to hear the team's thoughts on using the insights tool to pose questions.