We use groups for high level organisation, i.e.:
- Solutions
- Tools
- Visuals
- Archive
- Others
Inside of each of those groups we create projects for things such as product functionalities, internal tools, etc...
🧐 How do you organize your UXPin projects in your organisation?
It's all a little messy at the moment. However, we use Jira for dev tickets using scrum and kanban. I've started using a prototype for each story in Jira with the same name as the ticket. I've not adopted this for long enough to say how well it works but it certainly makes trawling through old prototypes and pages a lot simpler!
I work at an advertising agency. Projects in UXPin are our "Client" folders. Prototypes in those folders are then individual projects for those clients.
Same here.
Most companies have their own working culture and has tendency preference to use multiple tools. They are exporting visuals to cloud services like Sketch Cloud or Adobe Cloud for preview / comments while developers will require the designs assets in Zeplin as visual or functionalities groups. Normally they will reference based on the design filenames and request further implementation needs through emails. Sound familiar? If the final working prototypes does not come with well documented interactions, additional communication and documentation will be created as internal group.
With UXPin, many unnecessary process are eliminated. Everyone have the flexibility to create any folders types according to their process / needs. These visuals can be grouped using project folders and color tagging.
For example, I can have a folder of design system components and a folder of layout templates. Another team can move their prototypes into a "For review" folder which is maintained by the design system folder. Everything just worked so seamless.