Solution wall

Share a design or a proposal with your team and track the implementation and evaluation process.

Steps
5
Last edited
Sep 25, 2026
Created by
Nova

About this process

Share a design or a proposal with your team and track the implementation and evaluation process. Share your design with the team. Provide a list of resources and keep all the resources and links in one place. Track implementation. Test the final solution and provide feedback.

The process in detail

5 steps
  1. 1

    User story & Acceptance criteria

  2. 2

    Design/Solution

  3. 3

    Estimate the timeline and effort required for implementation.

  4. 4

    Implementation & Review.

  5. 5

    Package the design notes and scope into an engineering brief covering the initiative summary, user stories, technical requirements, and design details.

Read the full text
1. User story & Acceptance criteria

User story

•As a [user type] I want to [functionality] so that [benefit].
•As a [type of user], I want to [perform some task] so that I can [achieve some goal].

Acceptance criteria

•Given [how things begin] when [action taken] then [outcome of taking action]
•Given that [some context], when [some action is carried out], then [a set of observable outcomes should occur].
2. Design/Solution

Designers or managers add the solution here.

•Here, the designer or manager shares the solution/design with the team. ✔ Once you have shared the information with your team, mark this step as complete.
•The engineering team and other stakeholders will add questions and go over the resources section to find all the related documents and files. ✔ Once you have reviewed the design/solution, and you understand the project mark this step as complete. Contact the designer or manager if you have questions.
4. Implementation & Review.

Here, the engineer or execution team marks the step as completed so that the team can provide feedback.

•As soon as the design/solution is implemented and is ready to be tested or done, the engineering team or project manager will mark this ✔step as complete.
•During the session, the design team, managers, and stakeholders could review the solution, test it, and provide feedback to the engineering and execution team. When the team has provided a review, they can mark this ✔step as complete.

If the team needs to provide feedback to the execution team or engineers, they will use blue sticky notes to add general feedback to the board, and red whenever they are requesting changes.

5. Package the design notes and scope into an engineering brief covering the initiative summary, user stories, technical requirements, and design details.

Keep the document under two pages to highlight key points without overexplaining. Ensure the requirements, user stories, and specifications remain concise yet clear enough for an AI to build a prototype from them.

New Board
  • Review & Feedback
  • Feedback. Request changes.
  • Design/Solution
  • Introduction & Brief
  • Add feedback
  • Request changes
  • User story & Acceptance criteria
  • As a [user type] I want to [ functionality] so that [benefit]. Given [how things begin] when[action taken] then [outcomes X & Y should occur] As a [user type] I want to [ functionality] so that [benefit]. Given [how things begin] when[action taken] then [outcomes X & Y should occur]
  • Add a note here to describe a key milestone or important phase
  • Timeline/Roadmap
  • < MONTH
  • < MONTH
Use this process
Capabilities
Fully editableAdapts as work changesAdd more sessions anytimeAI can be assigned
N
Created byNova·Official process
Last edited Sep 25, 2026·5 steps