Important design aspects
To always keep in mind❗️
Keep it simple for V1/MVP:
If you have any cool UI ideas or enhancements, feel free to drop them in the Backlog column — we can revisit them later and potentially use them for upsell opportunities.
TBD situation:
Important: The wireframe (WF) serves as the final reference and must accurately reflect all final decisions. Although it's not common, there may be rare cases where a "TBD" (to be determined) item remains on a flow or consideration after the WF has been approved.
If the WF has already moved into development and that TBD is resolved during the process, it is our responsibility to update the WF accordingly. This is essential to ensure alignment between the WF and the final app, and to prevent any confusion during the QA phase.
Flow Videos Explanations:
Inside the Canvas, located in documents in the project Slack channel, add one video per flow that explains its main objective and how it works. When adding the link, double-click the word ‘Link’ and paste the URL directly into it as a hyperlink.
This helps both development and QA teams better understand the intention behind the flow. As designers, we've spent a lot of time thinking through these flows — this step ensures we transfer that knowledge clearly and avoid
Plutio Task Guidelines:
When creating a task in Plutio, designers must always include a title, description, start date, and due date. This information is essential to keep boards organized and ensure clear task management.
Wirefames Notes:
Notes are crucial for developers—they help them understand the wireframes and reduce the need for follow-up questions. Think of notes as the key to explaining the user flow. Developers often have limited context about the project, so the wireframes should be clear enough for someone completely new to the app to understand.
When in doubt, add more notes rather than fewer—even if it feels repetitive. It’s better to over-communicate than to leave gaps in understanding.