🔶 This is to make your onboarding process as the new designer easier. Because mostly onboarding is only about the product's knowledge and how we work in general. Here are the habits and facts you probably better know earlier specifically as the Product Designer here, so hopefully less confusing in the future:

  1. Customers are NOT a PERSON/PEOPLE. Instead, they are building names. Before this, the icon on the app was ‘people’. Hence many tables created on Customer Label were people’s names as well, but this was misunderstood. However, we’re fixing it now.
  2. ‘Topic’ could be meant here as a Feature or feature as a task, or just literally a topic, though
  3. Share the Figma Link to Tom after we are ready or finish the design in the ‘Work in Progress’ phase, unless when…in case you have a call with the team and Tom about it until finish it.
  4. Tom is not using Figma but is able to open it using Prasad’s account, so Tom will comment on it or check around when having a call, using Prasad’s name with “Tom:…….(comment here).” text, but usually, this happens when we present it or after ‘Work in Progress’ phase.
  5. We have ‘design’s debt/issues’ especially on UI elements and the wrong data value in the mockup like on the tables, more than we imagined, but we’re now working on it, so it might be decreased or fixed when you’re joining.
  6. In case we forgot in our early times joining, move the task cards progress on Clickup every time we have progress
  7. Figma’s Comment as ‘illustration’ about the UI, means UI dummy (to ‘illustrate’ it). Not always about real illustration drawing.
  8. Figma’s comment as ‘real estate’, means width, but if you have a coding background, you might be familiar
  9. Use MUI components and styles as much as possible for SM and PM UI. Also for mobile, use NativeBase. And use some of the customized versions of our own Mainteny’s design system where it’s already provided.
  10. Remove/Resolve Figma’s comments where the edit/revisions are done, if there is something important inside comments (such as the list of values, flow explanation, etc), copy-paste it into text format beside its artboard/frame, so we won’t forget it and easier for new other designers to know the product on onboarding even after we deleted the comments
  11. Add Handoff Developer Note in every interaction detail, this can be harmful to the other designers (if any) if we don’t add it, especially when they work on a tight deadline and need to copy it. It’s okay if we forgot, just add it asap when we remember it.
  12. To publish a component or edit it to publish it, try to always write down the description, about what to be changed
  13. Try to always use AutoFlow plugin Figma (with the red arrow, for multiple interactions can use not only read) for certain interactions, it will help new designers onboarding and developers, not just flow page by page as before
  14. Always try to remember to edit any designs directly from the original/parent components themselves if it’s supposed to be applied to all children’s components, -if any- to make it easier and faster. If not to be applied to all children's components, of course, you can edit it on your own child component.
  15. Better read this before you start designing on your first journey 😃 >>
  16. When we created dropdown field elements on Figma, please also put the text what’s inside the dropdown options besides the artboard, so all people will understand and make onboarding for new employees easier
  17. Let me know if you want to use a specific component but then it has NOT been updated yet to the current guideline, so that we may edit the component first or create a new one, and NOT BY EDIT the child/copied component, UNLESS you can edit it on the child/copied component + detach it. So when we need to update the original component later, it won’t distract the copied versions on the design because it’s detached already.
  18. Feel free to suggest anything if you find something wrong/unusual/weird anywhere, including from what I’ve made.