Great piece! And an overall great reminder of timeless design principles.

P.S. love the small detail in the header photo with the animated Braun watch, nice touch.

work with the team ... and the more involved you can be ...

+1 on embracing cross-functional design reviews. I find discrepancies tend to happen when there is either a lack of or ineffective communication of the expected design. I would assess what discrepancies there are, and make time to actually sit down with the developer(s) to see what was mis/undercommunicated, to inform could have been better communicated for future reference.

Where I work, our UI/layout related tickets are normally separated from more UX/functionality tickets. From a process standpoint, the first batch of visual layout/UI related issues are typically flagged by our designers during a 'creative review' pass that they do, before it goes into QA–from there, the UX/feature stuff get flagged. Although they're filed 'separately', both design-dev (and QA) have full visibility on these issues to avoid duplicates and overlaps.

In terms of where they live, they currently get logged within our project management platform.

This is an all or nothing decision though. You will need to migrate all of your workflow to this to maximize impact and potential for success.

Curious to know, what's your team's use case for using Confluence? Would you say that you use it mainly for technical documentation/knowledge sharing, or do you also use it for non-product related docs like HR/Admin/Ops?

We're currently exploring options for where our employee handbook can live (all things onboarding). We're thinking of factors such as accessibility and collaborative editing so that anyone can potentially contribute. We're also thinking of the potential for it to also house process documentation. Any other considerations we should take into account?

So far I've liked the sound of Nuclino (lightweight, user friendly), but Confluence has also been another option to look into - though my assumption is that Confluence would make for a better place for technical documentation to live, plus it helps if other Atlassian products are being used. Thoughts on this?

Big fan of stuff created on Society6 - lots of variety in terms of different artists and types of styles to browse through (by colour, pattern, aesthetic, theme, etc.)

Check out Zeplin - helpful for designer-dev hand-offs, and also helpful from a testing standpoint as well!