Posts for: #Note

至少找三个方案

至少找出三个解决方法,而不是只依赖直觉,接受第一个冒出来的点子。

The 3+ principle: Force yourself to explore at least three possible solutions to a problem. If you find yourself considering only two options, force yourself to find at least one more.

解决根因而非症状

很多解决方案,只想一步,不考虑后果。理想的方案,应该能用较低的成本,比如预期的 20%,解决掉 80% 的问题,且问题不会春风吹又生。

Use the test of time. Test whether you’re addressing the root cause of a problem, rather than merely treating a symptom, by asking yourself whether it will stand the test of time. Will this solution fix the problem permanently, or will the problem return in the future? If it seems like the latter, then chances are you’re only treating a symptom.

保持设计的湿泥状态

邀请其他人参与你的早期设计思考,简单直接地拉到白板前讨论好过给出详细的文档。

Try to keep the clay wet. Rather than writing up a document or creating a slideshow, invite them to a whiteboard and redraw the elements as you worked them out earlier, building up the concept from the beginning.

Stick completely to the concept you already worked out to get feedback on the work you’ve already done. Then once you’ve covered the work you already did, open it up and invite them to suggest revisions. Having seen this concept, do they have any insights about how to drastically simplify or approach the problem differently?

[阅读全文]

需求文档五要素

写一份需求说明,shape up 需要具备五点。问题、胃口、方案、坑、不做。

There are five ingredients that we always want to include in a pitch:

Problem — The raw idea, a use case, or something we’ve seen that motivates us to work on this

Appetite — How much time we want to spend and how that constrains the solution

Solution — The core elements we came up with, presented in a form that’s easy for people to immediately understand

[阅读全文]

当自己已死而活

Think of yourself as dead. You have lived your life. Now take what’s left and live it properly.

—MARCUS AURELIUS, Meditations, Book 7

人人都在瞎子摸象

Everyone has an incomplete view of the world. But we form a complete narrative to fill in the gaps.

这个说法很有意思。每个人都是瞎子摸象,但每个人都自己脑补了似乎能自圆其说的信息,其他人看来,可能会觉得傻逼。

工程师主导迭代实验

两周前的记录:今天跟 T 和 Zhendan 聊起一个项目时,Zhendan 说,回头请设计师出了设计稿,然后他快速拿一个版本出来上手体验。

T 的意见是:干脆别等设计稿,而是自己琢磨一下,直接出一个“工程师版本”。

这突然让我想做个实验:

我们目前挺想对网页版做调整的,但是现在设计资源捉襟见肘,是不是可以试一试,由研发主导,产品和设计相对轻度配合,快速地对当前网页版做迭代?

这种做法,会不会引出什么问题?

以及,或许回头值得再重读一两遍 37signals 的那本 shape up,再思考和感受他们的协作思想,争取能给同事们更强的自主权。

二月阅读清单

2 月阅读清单,这个月太忙了,实在没抽出多少时间看书。

  • Are your lights on?
  • 跨越鸿沟
  • 创新公司:皮克斯的启示
  • The psychology of money