文件存档/Documentation

从设计一个文件归档方式开始

文件归档是一个听起来与“策略”或“执行”相关联的字眼。在我们的设计工作中，最重要的一个资产是我们的设计思维方式，而文件归档是记录下设计思维的瞬间，方便存取团队存取。

很多设计团队会同时使用多种工具进行文件传输和交流：使用Dropbox传输文件，Jira安排任务，而用slack沟通和交流。在这些互不相通的工具中发生着千万条沟通行为，而这不叫文件归档，顶多算是交流。尤其对于远程的设计团队而言，这是远远不够的。为了创造对团队有价值的文件归档方式，以下是几项建议：

1. 一旦你决定存储的位置，所有的文件和对话都放在这里。不停地更换不同的存档方式只会导致更多的混乱。去创建一个中心化的解决方案，使得团队所有人都可以轻松存取文件。
2. 使数据可信。为了使得归档的文件可用并且可信，团队中的所有人都有责任去定期维护它。
3. 保持透明。文件归档只有在容易存取的时候才有价值。使得团队成员积极主动地去维护文档的关键就是使得所有人有相同的存取权限。
4. 归类与工作相关的文档。存取永远不会被使用的文件是没有意义的。文档的存储方式要清晰合理，可以帮助团队成员快速找到，并用来为日后可能的争议作参考。
5. 确保这种存档方式可以扩大到更大的团队。
6. 将每天的决策记录下来。很多时候团队浪费了很多时间不断将既有的决策推翻重来。创建一个地方用来存储每日的决策结果有助于减少不必要的团队争议。而对于远程团队而言，则可以确保决策的透明和可见性。

以下为英文原文：
link

Start with where: designing a documentation strategy

Documentation is one of those words that’s thrown around like “strategic alignment” and “executive sponsorship.” One of the most valuable assets produced through the design process is our design thinking. Documentation is a way to capture that thinking in the moment, and store your team’s design artifact as an easily-accessible reference for all who come after.
Most design teams rely on some combination of Dropbox Paper, Jira ticket comments, and Slack threads to document their design process. In this scenario, there are an infinite number of conversations that happen across tools that aren’t connected to each other. This isn’t documentation, it’s conversation. And in a remote and/or distributed environment, it’s simply not enough.
To make documentation invaluable to your team and cross-functional stakeholders, there are a few things to consider:

• Once you’ve chosen where to document, go all in. Waffling back and forth over different documentation solutions drains everyone and leads to more chaos. Relieve your team’s confusion by investing in a centralized solution that designers will contribute to and stakeholders can view.
• Make it trustworthy. For documentation to be useful _and _used, it’s critical that everyone on the team commits to maintaining it. So the first step to setting up a source of truth is getting commitment from the team to regularly maintain it.
• Make it transparent. Documentation is only as useful as it is accessible. The key to empowering your teammates to make better and more informed decisions is to give them access to all the things.
• Connect your documentation to the work. The point of documentation is transparency and utility. Documentation fails miserably when it’s not used. Connecting documentation to the work files increases the likelihood that it will improve clarity and help alleviate decision fatigue.
• Make sure your documentation solution can scale with you. A lot of the solutions you choose when you’re a 5-person design team don’t work when you’re a 100-person design team. The tipping point isn’t even that high: Collaboration really starts to break down around anytime you have more than 1 designer. Choose a solution that can grow with you.
• Make a daily habit to document decision-making. A lot of teams waste a lot of time reinventing the wheel, over and over again. Establishing a daily habit to document decisions (even if you start today) will ultimately save you and your developers time in meetings rehashing the why. Especially for a newly-remote team, it’s more critical than ever to bring visibility to how and why we make decisions.