<aside>

When to use a two-way write-up, inspired by Coda. The five stages of a proposal are as follows.

• Wallow — the team is early, exploring, and/or uncertain of the the problem and solutions.
• Frame — the team has framed the proposal, discussion, or decision.
• Propose — the team has a specific proposal they'd like feedback on.
• Close — the team is actively trying to close a big decision.
• Act — the team is executing & wants to communicate the plan to get final questions or feedback.
• Toggle for examples </aside>

<aside>

Background

What context does someone need to understand what you mean? Why does it matter now?

<aside>

Your text here

</aside>

</aside>

<aside>

Proposal

What changes have you made and why?

<aside>

Your text here

</aside>

</aside>

<aside>

How do you feel about this plan?

Add your name and thoughts in a new row. Rate the proposal on a scale of 1–10, where 1 indicates strong opposition or serious concerns, and 10 indicates complete approval with no additional feedback.

Untitled

</aside>

<aside>

Questions & discussion

Add a question or concern. If no person is named in the question or prompt, the proposal authors are responsible for replying. Replies should occur within [insert time frame].

[Insert any specific questions or prompts for your reviewers]

</aside>

<aside>

Review Questions

Untitled

Question Form

</aside>

After completing the two-way proposal, the authors should refine it if significant changes are required.

• BACKEND: Do not edit below line

  feedback-tbl

  qaTable