document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2025-02-03 23:40:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

translated

Browse Source
This commit is contained in:
geekpi 2023-05-29 09:04:19 +08:00
parent c1afc2a816
commit 5712c966a6
2 changed files with 69 additions and 69 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

69
sources/talk/20230426.0 ⭐️⭐️ 5 open ways to help UX designers and developers collaborate better.md
View File

@ -1,69 +0,0 @@
[#]: subject: "5 open ways to help UX designers and developers collaborate better"
[#]: via: "https://opensource.com/article/23/4/designers-developers-collaborate"
[#]: author: "Katie Riker https://opensource.com/users/kriker"
[#]: collector: "lkxed"
[#]: translator: "geekpi"
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
5 open ways to help UX designers and developers collaborate better
======
Ideally, designers have a good relationship with their product team and users. However, the relationship between designers and developers is more difficult to build and maintain. The lack of a close relationship makes it difficult to solve problems or improve.
In my experience, the open source [Open Decision Framework][1] can overcome many of these obstacles.
The Open Decision Framework asserts that [open decision-making][2] is transparent, inclusive, and customer-centric. It involves clearly sharing problems, requirements, and constraints with affected parties. It enables collaboration with multiple stakeholders to secure diverse opinions and comprehensive feedback. Most importantly, it manages relationships and expectations across competing needs and priorities.
These principles probably resonate with anyone involved in the many decisions around designing a product, feature, or service. For a designer, developers are key stakeholders in making the best design decisions. If you're a designer, it's time to embrace the opportunity to get diverse opinions.
### The backend and the user experience
Developers are key stakeholders because a user's product or service experience is more than just the pixels on the screen or the workflow designs. It encompasses the service's performance, the speediness of [API][3] calls, the way user data is treated, and even the design of the data for scalability. When they're considered full stakeholders in the design, developers can contribute their expertise on the backend and architecture of services to assist the overall design of the experience.
A user experience (UX) designer is a stakeholder for the items the dev team is responsible for. A performance deficit, or the effects of an architecture on what data is available, can hinder the user experience. An open, [collaborative relationship between dev and design][4] allows for trust and transparency in all areas.
### Make space for collaboration
An open and transparent relationship between developers and design is not as common as it should be. This way of working may be new to both sides. Here are my top five tips for making collaboration a success:
- **Designers**: A coding foundations course, such as the open source [Odin Project][5], can be helpful for learning the fundamentals of how a service is constructed and built.
- **Developers**: An understanding of UX principles can help guide questions and feedback. You can find a good overview at UX design principles or in various books and articles.
- **Set up a recurring time to collaborate**: Establish a recurring time for design and development to meet between once a week and once a month. The invitation should at least include UX, lead engineering, and quality engineering. Ideally, all developers on the team should be invited to attend as schedules permit.
- **Make sharing the main agenda:** UX should share the current use cases and features they are working on, along with any relevant user research data. UX designers should demonstrate workflow designs, wireframes, and high-fidelity mockups to the development team. Development should share any design decisions made on their side that may affect how the user experience works.
- **Encourage questions:** Collaboration is the ideal scenario. Encourage all attendees to ask questions and give feedback. Answers to questions and responses to feedback are opportunities to discuss design and direction, as well as a chance to learn from one another.
- **Embrace a learning mindset**: Avoid lecturing or "telling." Instead, aim to learn from each other. Use mutual expertise to design and build a great experience for users and customers. Ask for explanations of unfamiliar technology or concepts.
- **Consider formal learning**: A collaborative relationship can be easier when groups speak the same language. Consider formal learning paths, such as:
### An example of open collaboration
In an early design review with a developer on my team, I showed a specific interaction for displaying more data about an object. I communicated the user's need and demonstrated the interaction when the developer asked, "Does it need to be done in exactly this way?"
He mentioned that with a few minor design changes, the effort to develop it would be significantly lower. We agreed that the changes would not negatively affect the user experience, and the user would still be able to achieve their goals.
This feedback saved the development team time, leaving more opportunity to address bugs, build additional features, and preserve a healthy work-life balance. The user experience remained strong, and the team was even stronger. This result would not have been possible without the early feedback from a developer with whom I had a strong working relationship.
### Your next steps
Creating an experience is a series of decisions made by a collaborative team. Product, design, and development need to work together as experts in their respective fields and stakeholders in the others. I encourage you to engage development and design for more collaborative feedback and work together to create the best product with the best user experience.
--------------------------------------------------------------------------------
via: https://opensource.com/article/23/4/designers-developers-collaborate
作者：[Katie Riker][a]
选题：[lkxed][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/kriker
[b]: https://github.com/lkxed/
[1]: https://opensource.com/open-organization/resources/open-decision-framework
[2]: https://opensource.com/open-organization/20/6/open-management-practices
[3]: https://www.redhat.com/en/topics/api/what-are-application-programming-interfaces?intcmp=7013a000002qLH8AAM
[4]: https://www.redhat.com/architect/keycloak-ui-architecture?intcmp=7013a000002qLH8AAM
[5]: https://www.theodinproject.com/

69
translated/tech/20230426.0 ⭐️⭐️ 5 open ways to help UX designers and developers collaborate better.md Normal file
View File

@ -0,0 +1,69 @@
[#]: subject: "5 open ways to help UX designers and developers collaborate better"
[#]: via: "https://opensource.com/article/23/4/designers-developers-collaborate"
[#]: author: "Katie Riker https://opensource.com/users/kriker"
[#]: collector: "lkxed"
[#]: translator: "geekpi"
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
帮助 UX 设计师和开发人员更好地合作的 5 种开放方式
======
理想情况下，设计师与他们的产品团队和用户有良好的关系。然而，设计师和开发者之间的关系更难建立和维持。缺乏密切的关系使得问题的解决或改进变得困难。
根据我的经验，开源的[开放决策框架][1]可以克服许多这样的障碍。
开放决策框架宣称，[开放式决策][2]是透明的、包容的、以客户为中心的。它包括与受影响的各方清楚地分享问题、要求和限制。它能够与多个利益相关者合作，以确保不同的意见和全面的反馈。最重要的是，它能在相互竞争的需求和优先事项之间管理关系和期望。
这些原则可能会引起任何参与设计产品、功能或服务的决策的人的共鸣。对于一个设计师来说，开发人员是做出最佳设计决策的关键利益相关者。如果你是一个设计师，现在是时候接受获得不同意见的机会了。
### 后台和用户体验
开发人员是关键的利益相关者，因为用户的产品或服务体验不仅仅是屏幕上的像素或工作流程的设计。它包含了服务的性能、[API][3] 调用的速度、处理用户数据的方式，甚至是数据的可扩展性设计。当他们被认为是设计中的完全利益相关者时，开发者可以贡献他们在服务的后端和架构方面的专业知识，以协助整体的体验设计。
用户体验（UX）设计师是开发团队所负责的项目的利益相关者。性能上的不足，或者架构对可用数据的影响，都会阻碍用户体验。一个开放的、[开发和设计之间的合作关系][4]允许在所有领域的信任和透明。
### 为合作留出空间
开发者和设计之间的开放和透明的关系并不像它应该的那样普遍。这种工作方式对双方来说可能都是新的。以下是我为使合作成功而提出的五大建议：
- **设计人员**： 编码基础课程，如开源的 [Odin项目][5]，对于学习服务的构造和构建的基本原理是有帮助的。
- **开发人员**： 对 UX 原则的理解可以帮助指导问题和反馈。你可以在 UX 设计原则或各种书籍和文章中找到一个很好的概述。
- **建立一个经常性的合作时间**： 为设计和开发建立一个经常性的时间，在每周到每月一次之间进行会面。邀请的对象至少应该包括 UX、主导工程和质量工程。理想情况下，如果日程安排允许，团队中的所有开发人员都应该被邀请参加。
- **使分享成为主要议程：**UX 应该分享他们目前正在进行的用例和功能，以及任何相关的用户研究数据。UX 设计师应该向开发团队展示工作流程设计、线框图和高保真模拟图。开发应该分享他们这边做出的任何可能影响用户体验的设计决定。
- **鼓励提问：**合作是最理想的情况。鼓励所有与会者提出问题并给予反馈。对问题的回答和对反馈的回应是讨论设计和方向的机会，也是一个相互学习的机会。
- **拥抱学习的心态**： 避免说教或“告诉”。相反，目的是互相学习。利用彼此的专业知识，为用户和客户设计和建立一个良好的体验。要求对不熟悉的技术或概念进行解释。
- **考虑正式学习**： 当群体说着相同的语言时，合作关系会更容易。考虑正式的学习途径，例如：
### 一个开放合作的例子
在与我团队中的一个开发人员进行的早期设计审查中，我展示了一个具体的交互，以显示关于一个物体的更多数据。我传达了用户的需求并演示了这个交互，这时开发者问道：“是否需要完全以这种方式来完成？”
他提到，只要在设计上稍加改动，开发的工作量就会大大降低。我们同意，这些改变不会对用户体验产生负面影响，而且用户仍然能够实现他们的目标。
这种反馈节省了开发团队的时间，留下了更多的机会来解决错误，建立额外的功能，并保持健康的工作和生活的平衡。用户体验依然强劲，而团队则更加强大。如果没有一个与我有深厚工作关系的开发者的早期反馈，这个结果是不可能的。
### 你的下一步
建立体验是由一个合作的团队做出的一系列决定。产品、设计和开发需要作为各自领域的专家和其他人的利益相关者一起工作。我鼓励你让开发和设计参与进来，以获得更多的合作反馈，并一起努力创造出具有最佳用户体验的最佳产品。
--------------------------------------------------------------------------------
via: https://opensource.com/article/23/4/designers-developers-collaborate
作者：[Katie Riker][a]
选题：[lkxed][b]
译者：[geekpi](https://github.com/geekpi)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/kriker
[b]: https://github.com/lkxed/
[1]: https://opensource.com/open-organization/resources/open-decision-framework
[2]: https://opensource.com/open-organization/20/6/open-management-practices
[3]: https://www.redhat.com/en/topics/api/what-are-application-programming-interfaces?intcmp=7013a000002qLH8AAM
[4]: https://www.redhat.com/architect/keycloak-ui-architecture?intcmp=7013a000002qLH8AAM
[5]: https://www.theodinproject.com/