Thanks, but in our case Design Readme documents will not cover the need of documentation. But I will sleep on it and see if I can adapt or use in some way.

Thanks, This is a good flow and some good insights for me. For the moment I need for a better integration of the documentation / notes with stories and epics.

Hi George, Thanks. This is what I am actually doing, talking, but not just with the developer. I'm talking also with the BA's, PM's and other Designers. And here on DN I'm trying to see how others tackled this problem. And sure, we will use the solution/s that works for the entire team, not just design.

Hi Thomas,

Thanks for the feedback, it does help me. Seems that we have a similar pain point. I know that what we need is an ideal tool that does not exist, but I needed to understand if other designers have this problem and how they resolved it.

We have a similar process with yours, just that we use Invision Sync for versioning and Invision Inspect for specs, but still is not enough. I'm trying to make the switch to Abstract but it will take some time.

Figma is not an option for the moment and when I had a look at the Zeroheight it looked that it will not be able to manage our DS. But I will have a better look.

Thanks again

Thanks, really good article on the best practice. But I need to document the design and the flows architecture. And the handover of the documentation. The .sketch design files can be provided to developer using the Invision Inspect or Zeplin. But this should be possible to refer in the documentation.

Thanks, but in my case is not an option to switch to Figma for this project. An i think is not enough how you can document in it. But i will make a research on how Figma integrates with Jira.

But I totally agree. And this is what I hoped to achieve with my article - to start a conversation regarding the confusion in this industry and the need of having an unified process. And with the Experience Design, just because I feel that it is more than the User term.

I find this conversation very informative and constructive.

Exactly, this is also what we are trying to do, at my company. But we understood that we need to define career paths so they can have an overview of what else is there.

Well, I find your point of view really constructive. I feel that is about everything you mentioned. In my article I'm just saying that is to much confusion and that we don't have an "unified approach to the UX Process" as JB Ong said in his comment. And I agree that we are not designing an experience but actually a "desired contextual experience".

You are so true. But I feel that the real problem is that we design the experience of other beings as we, as humans, want to be :(