Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX 基于背后的合理化,而非设计 #1903

Merged
merged 2 commits into from
Jul 21, 2017

Conversation

horizon13th
Copy link
Contributor

@horizon13th horizon13th commented Jul 14, 2017

Issue #1831

@CACppuccino
Copy link
Contributor

@sqrthree 校对认领

@linhe0x0
Copy link
Member

@CACppuccino 好的呢 🍺

Copy link
Contributor

@CACppuccino CACppuccino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@horizon13th @sqrthree All good, aware swapping the Itally fronts to bold one.

@@ -6,96 +6,95 @@
> * 译者:
> * 校对者:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

校对者:CACppuccino


Research is super important, but *synthesizing* that information to come up with new opportunities is even more valuable than making products look good or building something which already exists. It also opens up the opportunity to give perspective to other designers working a team and allow them to leverage what they are working on to solve bigger issues aside from a specific solution.
用户研究及其重要,然而,将用户研究所得到的信息与新机遇相*结合*更加重要。相比之下,把产品做好看,或者开发一个已经存在的产品便不那么重要了。用户研究让设计师们协作起来,给大家机会来表达自己的观点,用群众智慧组团解决更大的问题。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[将用户研究所得到的信息与新机遇相结合更加重要] =>[将用户研究所得到的信息结合而得到新机遇更加重要]


![](https://cdn-images-1.medium.com/max/1600/0*Z1s829rQRLCI-GoN.jpg)

connectivedx
I have been talking to a lot of people and writing down everything I learned so far, but *writing isn’t the same as understanding*. I was not using that information to generate understanding about the problem, but instead wrote it down in hopes of understanding it later.
我和很多人聊过,写下每一件我学到的事情,但是*抄写不等于理解*,我并没能够通过写下这些内容而更好地理解问题,反而是想先记下以后再慢慢理解吧。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Itally => bolder

- **Principles** define what the design should or shouldn’t do. These statements are grounded in research, and may be referred to as *implications* when you can tie them to research.
- **Concepts** establish an overall approach for the product, expressed as a central theme or idea.
- **Models** describe the product in an abstract way, showing the underlying architecture, structure, flow, or approach. They offer a sense of how the product will work (without actual functionality)
- **原则** 定义设计能做什么不能做什么,这些叙述是基于研究的,当它们与研究相联结时,可以被引用作为*奥义*。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Itally => bold


I had been learning a lot about my project, as well as talking to many people, but I wasn’t distilling any of that information into something actionable. Instead, I started to get stuck in a plethora of different information, letting myself get stuck in analysis paralysis because I wasn’t connecting that information to how it was going to help me move forward.
在这个项目中,我学到了很多,与很多人聊天谈话,但起初我没能沉淀信息,付之行动。相反,我受阻于多方面冗余的信息,让自己困于麻痹的分析过程,因为我未能将得到的信息与实际生活相结合而进步。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[因为我未能将得到的信息与实际生活相结合而进步。] => [因为我未能学会如何将得到的信息结合而进步。]

@horizon13th
Copy link
Contributor Author

根据校对意见修改

@linhe0x0 linhe0x0 merged commit 58c1166 into xitu:master Jul 21, 2017
@linhe0x0
Copy link
Member

@horizon13th 已经 merge 啦~ 快快麻溜发布到掘金专栏然后给我发下链接,方便及时添加积分哟。

@horizon13th
Copy link
Contributor Author

已经发布了~@sqrthree 求积分~
https://juejin.im/post/5971ce0d51882574623352ca

cdadar pushed a commit to cdadar/gold-miner that referenced this pull request Dec 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants