Seventeen days ago I saw Joe Karlsson and Edward Ecker speak on UX and engineering trying to get along at the Norwegian Developers Conference.

Joe Karlsson sports the hairbun at the left in the photo here, but he is not UX. He is engineering. Edward Ecker at right is UX. UX is user experience. They both work at Best Buy. Don't try to make mockups perfect. They just need to be good enough. Get engineering onboard. Try to catch design bugs early. Don't hoard designs. Try to have something to show every other day. Premature optimization is the root of all evil. When someone else comes out of a meeting (perhaps a product owner, not UX) with a wireframe, then UX is behind working on a story they don't want to work on. Try to have UX and product owners coplan features. In design thinking we are all working together and we need to speak the same language. The first pillar of design thinking is to empathize. The second is "define" and therein pick the worst problem the customer is facing that you can control. Ideate is third. Ideate involves tackling the said worst problem the customer is facing that you can control. Get development involved sooner instead of later. Fourth, remember to make others think they are contributing ideas. Start with a developer in the room, whiteboarding and talking about what is possible. Fifth, review. Sixth, prototype. InVision, Framer X, Axure RP, and Adobe XD are prototyping tools. (X for experience, RP for rapid prototyping, and XD for experience design) InVision Inspect and Zeplin were also namedropped as tools. Seven, test your favorite ideas in user testing. Eighth and last, it might be helpful to have microhackathons to get design and development together for a week to see what is possible. This eighth item isn't really eight on the list of seven. Devs need to pull the design team in early. Keep it Lean. Review tickets before you code. Engineering doesn't have to consult design for every nitpicky decision. Don't silo yourself and try not to be siloed. Not being a part of the team camaraderie is going to affect your ability to collaborate negatively. Sometimes we need to disconnect to do deep work but try to be available. TLDR stands for Too Long, Didn't Read and when you share your knowledge you should try to be concise to avoid that reaction. How is that possible if there is a large number of business people and devs of engineering and UX parties? How do you collaborate without everyone collaborating and it being too much? Someone will have to be the representation from a faction to a seat at the table.