If you're working in an Agile environment, you already know that it'snot easy for UXand there is a lot to get done in a short amount of time. Sometimes, you may be lucky enough to have multiple UX professionals on your team, but other times you're飞行独奏。如果你发现自己dreading your UX to-do list, considerbringing other members of your development team into your design process。Doing so not only will lighten your workload, but it will also introduce multiple perspectives and ease further collaboration processes (for example, if you need signoff from other departments).


6 - 升级1

If you're working with a large team or you want to get a lot of ideas for a particular feature, try the 6-up 1-up sketching method for brainstorming designs. It is best used with a larger team on a feature that is further out in your backlog, as part of a future sprint. This method allows team members to sketch out multiple quick ideas for one feature, come together as a group to discuss the proposed solutions, and then finesse one solid idea. It is a great method if your team members are particularly shy or new to each other, because individuals get a chance to work on their own design before bringing it to the larger group. This activity is similar to the疯狂8s.方法。

Steps for this activity:

1. 6 - 上:5分钟的单独绘图。每个团队成员都有6个部分的一张纸,应该为一个特征绘制最多6个想法。他们可以是6个完全不同的想法或较少的想法,每个想法都有多个屏幕或相互作用。只需5分钟即可鼓励人们在一个解决方案上花费太多时间,或者由于他们无法绘制的事实而陷入困境。使用标记来阻止图纸上的精细细节。

6 up


3. 1-up: 5-minute individual refinement。每个团队成员选择一个选择,详细绘制。该解决方案可以是该人的原始想法之一的扩展或基于组讨论的混合。

1 up

4. Final discussion.The group reviews the individual solutions and picks one idea or creates a hybrid design based on several of the ideas that came up. Since the group has already walked through the original ideas in step 2, this discussion should focus on improvements or new ideas, rather than on an entirely new concept.

6-UP阶段是一个版本并行设计, but done in a much shorter time frame than when designing multiple variants of a bigger user interface.

Whiteboard Session

A whiteboard session works well for small groups, exceptionally collaborative teams, or crossdepartmental teams looking to compare design ideas. It is best suited for features that need to be implemented soon (in the current sprint). In this type of informal session, multiple people contribute to one design on a whiteboard.

This session starts out with clear goals that will be accomplished, such as which feature is going to be designed, which persona(s) and/or journeys must be represented, or any acceptance criteria that need to be accounted for. From there, volunteers can start drawing out an idea. Team members can then build up on that idea, propose alternatives, and discuss potential difficulties.

Start with clear goals listed on the whiteboard. One person starts drawing an idea, then the team works collaboratively towards accomplishing the goals.

What you'll end up with is a common understanding of what will be implemented for that feature. Developers can call out potential issues with the scope or technical feasibility, product owners and business analysts can add their own perspective, and designers can make sure consistency is maintained, all in one meeting. If you're working one-on-one with a developer for this activity, make sure both sides leave satisfied with the solution, as it will be implemented in the current sprint and there is not as much time available for iteration.


Remember the telephone game? Kids sit in a circle and one whispers a message to her neighbor, who then passes it on until the message gets back to the source. You can do a similar ideation activity to help your team collaborate or even create completely out-of-the-box solutions. This activity is geared for larger teams focusing on one or more features that are further down the backlog in priority.

telephone activity
Pass along a design or wireframe from one person to the next to build on ideas. This technique is great for getting your team comfortable drawing and building on someone else's ideas. Just like with the telephone game you played as a kid, you may end up with something good or with a Frankenstein design.

Start with a single piece of paper for each concept. Each person draws his idea out for 1–2 minutes, and then passes it to the next person. The next person adds her ideas to the drawing for another 1–2 minutes, then passes it along. Continue with each team member or until the concept(s) can't go any further. If you're working with multiple concepts in one session, stagger the pieces of paper every few people. For example, if your team has 12 people and you're working through 4 concepts, start the activity with a piece of paper every third person, as illustrated below.

telephone example layout
每隔少数人在做这个活动时令人惊讶的概念有助于保持 失败时间 to a minimum.

Timing: When to Use Collaborative Activities

A successful UX process in Agile is all about timing. When you work in sprints, you have to support your teams in a timely manner with the right design input. However, not all needs are equally urgent.

Think of these needs like the beam of a flashlight, as illustrated below. The narrower the light is, the more focused you should be on that specific task. Work directly with the person needing the output on focused tasks to help speed up the process. The wider the light is, the less defined the task will be, therefore the less time you should spend on it immediately. When there is a lull in your UX to-do list, bring your larger team together to brainstorm ideas that you have more time to narrow down.

UX tasks at any moment flashlight
Gauge your collaborative activity needs based on where your task falls in the flashlight beam, involving fewer people on items needed sooner and more people on those that are further off.

The current sprint's design tasks typically come up because you discovered something new or ran into a potential issue when developing a feature. When that is the case, invite your developer(s) in your design process — either after a daily standup or in a separate one-on-one meeting at a whiteboard. For example, if your team is working on user login in the current sprint and a technical issue comes up that affects the design, work directly with your developer to create a new design together.


Introducing Activities to Existing Teams

When introducing any new technique to an existing team,start small。Consider carving out a minor amount of time from an existing scrum ceremony (planning, backlog refinement, etc.) where the team members you need will already be present. Gaining buy-in from your team members to help with design may be the hardest part, so get them to participate without adding additional meetings to their calendars. As you gain interest and trust, you will be able to set aside some design-collaboration time and even create a recurring meeting that can be added to the team's routines.

As with any technique, customize the steps until they meet your needs. For example, it is perfectly acceptable if your team wants to cut out the second round of the 6-up 1-up exercise and go straight to the larger group hybrid design. You may also find that your entire large team isn't as productive as a smaller group, so you may only want to include certain people. Iterate often on your process until you find what works best for you.



了解更多关于用户体验专业的蓬勃发展an Agile environment in our full-dayLean UX and Agilecourse. And many more ideation methods in our full-dayEffective Ideation Techniques for UX Designcourse.