当涉及到你的长期项目时,你如何保持以用户为导向?

发布于 2024-08-09 23:11:07 字数 245 浏览 7 评论 0原文

我已经从事一个长期项目一年多了,并且喜欢其中的每一分钟。然而,我发现自己与用户越来越脱节,因为我对同一个项目的看法截然不同。

就我而言,我知道如何通过 5 种不同的方式快速离开 AB。但是,如果我和一个典型的用户处于同样的情况,我担心我不会有足够的同理心来理解用户体验或功能方面的困难。

我怎样才能保留对用户的同理心,同时仍然了解怪物的内部运作?

我正在寻找开发人员可以使用的任何提示/技巧,而不是与第三方进行硬核用户体验测试。

I've been working on a long-term project for over a year now and love every minute of it. However, I find myself getting increasingly out-of-touch with my users as my perspective of the same project is drastically different.

In my case, I know how to get from A-B very quickly in 5 different ways. But, if a typical user and I were placed in the same situation, I fear that I would not empathize enough to understand struggles with the user-experience or functionality.

How can I retain this empathetic view of my users whilst still knowing the inner-workings of the monster inside and out?

I'm looking for any tips/tricks that developers can use rather than hard-core UX testing with 3rd parties.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

只是我以为 2024-08-16 23:11:07

在我们的例子中,我实际上是在“跟踪”用户以了解他们实际做了什么。

这不是他们声称想做的事情。或者认为要求应该说什么。

但他们实际上做了什么。这比无休止的需求会议要好。

In our case, I'm actually "shadowing" the users to see what they actually do.

Not what they claim they'd like to do. Or what the think the requirements should say.

But what they actually do. It's better than endless rounds of requirements meetings.

丘比特射中我 2024-08-16 23:11:07

我们遵循 scrum 开发流程,其中包括每次开发后的“演示”会话周期(通常为 3-4 周)。我们邀请公司的每个人以及一些精选的客户来看看我们在做什么。这使我们能够快速获得新功能的反馈,并在最终用户的开发人员之间保持持续的关系。

We follow the scrum development process, which includes a "demo" session after each development cycle (typically 3-4 weeks). We invite everyone across the company, as well as a few select customers, to see what we are up to. This enables us to get quick feedback into new features, as well as keeps an ongoing relationship between the devs at the end users.

并安 2024-08-16 23:11:07

我建议:-

  1. 与您的用户一起坐一天,让他们使用您的应用程序。你会看到他们做各种各样的事情,并立即列出一长串改进的想法。
  2. 与他们讨论他们的问题,而不是他们为您的应用程序提出的解决方案。你应该比他们更擅长软件设计;他们应该更好地理解自己的问题。
  3. 考虑一下您可以为客户的客户做些什么,让他们的生活更轻松。

I would suggest:-

  1. Sit with your users for a day as they use your application. You will see them doing all sorts of things, and immediately have a long list of ideas for improvement.
  2. Talk to them about their problems, not their proposed solutions for your application. You should be better at software design than them; they should be better at understanding their problems.
  3. Consider what you can do for your customer's customer to make their life easier.
萌面超妹 2024-08-16 23:11:07

轻量级用户体验测试,即使是大厅里的人只尝试做一件事,也是摆脱自己的头脑并以新的眼光看待界面的好方法。 (只是好奇,为什么不这样做?)

我知道您正在寻找非用户体验测试答案,所以我提出的一个建议是通过将自己想象为特定类型的最终用户来模拟该结果(例如,选择一个合适的职业,第一次或第n次使用你的软件,试图实现一些合适的——或不合适的但合理的——目标)。如果您可以足够详细地想象它(特别是如果您想到了一些第三方用户),您就可以开始以他们可能的方式查看界面。令人惊讶的是,它确实有效。

Lightweight UX testing, even if it's with the person down the hall trying to do just one thing, is a great way to get out of your own head and see the interface with new eyes. (Just curious, why not do this?)

I know you're looking for non-UX testing answers though, so one suggestion I'd make is to simulate that outcome by imagining yourself as a particular type of end-user (for example, pick an appropriate career, first time or nth time using your software, trying to accomplish some appropriate - or inappropriate but plausible - goal). If you can imagine it in enough detail (esp if you have some 3rd party user in mind), you can start seeing the interface the way they might. Astonishingly, it actually works.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文