Initial proposal creation via a CTA in the workspace.
Description
A modal that users can access by clicking 'start proposal'. Users can choose to start a proposal with the base template for the campaign only, or they can make a category selection that appends additional questions. Users can modify their category select until the point of submission.
User Value
As a proposer, I want to start a proposal from the workspace, so that I can start building my ideas.
UX Story
If no proposals exist, then present CTA to 'start proposal' as main content in the page.
If proposals exist, then show my proposal inventory, along with a CTA to 'start proposal'.
Clicking the CTA launches a modal. This modal gives some education about the proposal submission process, and the difference between the campaign vs category questions. I can choose to start with base template only, or make a category selection.
When I click confirm, the workspace loads the selected questions and I can start editing responses.
Design Guidance
Workspace / Home Page - align with Niels interaction patterns
Action to do on proposal
Open
Duplicate
Delete
Archive (define archiving - what’s diff between draft and archive?)
Backup
Link Team (Out of Scope)
Move (to new brand / campaign) [out of scope]
User must be able to change categories. Need confirmation before changing, with education about what will happen and what user will need to do next. Previous category question responses should be hidden in editor, but saved to backend and restored if user re-selects category later
We want to educate users about what will happen when they make a change. Need to discuss how this happens. Better UX, more complex - store answers to previous category questions, but hide them, and if user re-selects that prior category, their answers are restore. Worse UX, less complex - warn users they’re about to remove some questions and add others, and that previous responses will be lost if they proceed. Let’s come up with ideal UX from design perspective, then discuss with arch to find sensible MVP approach.
Consider: Visually move old one into Inventory Manager? Bring in some sort of Category Stack / Idea stacks.
Summary
Start proposal from workspace
Description
Summary
Initial proposal creation via a CTA in the workspace.
Description
A modal that users can access by clicking 'start proposal'. Users can choose to start a proposal with the base template for the campaign only, or they can make a category selection that appends additional questions. Users can modify their category select until the point of submission.
User Value
As a proposer, I want to start a proposal from the workspace, so that I can start building my ideas.
UX Story
If no proposals exist, then present CTA to 'start proposal' as main content in the page.
If proposals exist, then show my proposal inventory, along with a CTA to 'start proposal'.
Clicking the CTA launches a modal. This modal gives some education about the proposal submission process, and the difference between the campaign vs category questions. I can choose to start with base template only, or make a category selection.
When I click confirm, the workspace loads the selected questions and I can start editing responses.
Design Guidance
Workspace / Home Page - align with Niels interaction patterns
Action to do on proposal Open Duplicate Delete Archive (define archiving - what’s diff between draft and archive?) Backup Link Team (Out of Scope) Move (to new brand / campaign) [out of scope]
User must be able to change categories. Need confirmation before changing, with education about what will happen and what user will need to do next. Previous category question responses should be hidden in editor, but saved to backend and restored if user re-selects category later
We want to educate users about what will happen when they make a change. Need to discuss how this happens. Better UX, more complex - store answers to previous category questions, but hide them, and if user re-selects that prior category, their answers are restore. Worse UX, less complex - warn users they’re about to remove some questions and add others, and that previous responses will be lost if they proceed. Let’s come up with ideal UX from design perspective, then discuss with arch to find sensible MVP approach.
Consider: Visually move old one into Inventory Manager? Bring in some sort of Category Stack / Idea stacks.