Hey everyone 
Thanks to everyone who joined our design-dev collaboration session during coworking week! It was great to be in the same room, having honest, unfiltered conversations about what’s working, what’s not, and what we need to improve.
Here’s a summary of where we landed:
- Both design and development teams should review client briefs
- Update our terminology to match the Product Review Process - for example, use “Proposal” instead of “Discovery”
- Designers will write product design proposals; developers will write technical proposals
- Consider mirroring the dev workflow by allocating 5 hours per sprint for “design proposal duty”
- Design must be looped in before anything is shown to a client - that means before code review and before merging
- Don’t be afraid to tell clients: this is how we work, and it aligns with community standards, ie. product-first
- All product proposals must be written in the open on Confluence
- We’ll rewrite our workflow - from product idea
proposal implementation - once the community process is finalised - which we’re actively helping to drive forward. Also smaller changes shouldn’t require a full product review 
- We also need to audit the handbook and remove anything outdated or irrelevant
So if there’s any product component - no matter how small - loop in design early. Ping @Ali or @cassie whenever needed. Developers shouldn’t be left making design decisions for clients.
Keep an eye on this space as we work on improving how we work. And if I’ve missed anything, feel free to add your thoughts to this thread 
