-
Notifications
You must be signed in to change notification settings - Fork 3
Design projects, process and communication
hesterbruikman edited this page Jan 29, 2020
·
2 revisions
Every project is different, the table below shows a rough distinction between project types, their related effort and process.
| Type | Size | Example | Tech review | Design review | Design > Dev | Dev > Design |
|---|---|---|---|---|---|---|
| New feature | XL | Teller Network / TTT / Stickermarket / DApp store | x | x | x | x |
| Improvement isolated UI component | S | Additional message status | x | x | ||
| Improvement contextual UI component | M | Snackbar | x | x | x | x |
| Improvement isolated flow | L | Onboarding | x | x | x | x |
| Improvement across touchpoints | XL | Profile settings / Navigation | x | x | x | x |
Ball park legend: S - hours, M - day, L - few days, XL - weeks
Note
* Design is never done.
* A design project follows the same tradeoff as any other. There is no magic. https://fastgood.cheap/
Design process is iterative and differs depending on the design ask. The process outlined below describes the most common process within Status.
- Designer, PM or team lead creates a design epic and story(-ies); including order of use cases to be covered.
- Designer works on concept designs in Figma.
- Designer collects feedback from design team, and others when relevant, on concepts. Either 1:1, in a call or by tagging in Figma.
- Designer, PM or team lead updates design story to use cases covered by the design
- Designer, PM or team lead organizes a review with the relevant technical team lead, and others if necessary. Tech reviews are needed for new features, and any M-XL sized features.
- Designer updates design if needed.
- Designer, PM or team lead organizes Design Review. Objective depends on state and complexity of design; Can be OK for handoff or collecting feedback in Research phase. Attendees: Designer, Developer, Nabil, Rachel, Hester.
- Designer updates design if needed (includes coordination of final copy).
- Designer, PM or team lead organizes a Design > Dev handoff call if needed.
- Designer adds himself to relevant GitHub issue and shares the design files
- Designer continues to monitor implementation activities
- Designer follows up to troubleshoot any questions during development and provide any additional specifications, components, screens if needed.
- Designer reviews implementation; Dev > Design
- Design story is closed after PR is merged or further UI changes are highly unlikely.
The design team has a weekly call with last week/this week updates and any other business. All communication follows a format where possible to limit reliance on individuals.
Chat channels
- Design internal + - Early feedback on designs, design topics, venting and chit-chat
- Design external - Q&A that is not product specific or about projects that don't have a dedicated channel (yet)
- OOO-vacation - Ping to inform each other when out or otherwise unavailable
Meetups
- The team aims to hold dedicated design meetups 2-3 times a year. Where possible as extension or before product team meetups.
Requirements for other projects flagged in design weekly. Relevant designer will champion and prioritize with PM and circle back to the requester.
We invite other CC's for study calls/sessions.
- Communication protocols - Yenda
- Smart contracts - Richard
- Account contracts and Secret multisig - Ricardo