site de rencontre arabe pour mariage Teams create a physical box that sells their idea, whether or not their idea is a tangible product.
lithuania dating site free By imagining the package for their idea, the teams make decisions about important features and other aspects of their vision that are more difficult to articulate.
faire des rencontres en ligne This exercise is commonly attributed to Bill Shakelford and Jim Highsmith, creators of the agile method Agile Software Development.
annУЉe du film quand harry rencontre sally The exercise is typically run in the ideation phase of a project (as a kickoff). The general idea is that the box is used as a focusing device: it constrains the conversation and wraps up a lot of otherwise intangible information into a nice physical object, prompting teams to make decisions along the way.
advantage of online dating site The primary goals of this product vision exercise are:
- how long does dating scan last Get a design team focused on what’s really important about their idea, in particular, its features and benefits.
- opcje binarne bdswiss opinie Get a team thinking about the product from the consumer’s point of view as they are thinking about buying it: who are they? What is important to them? What will make them desire the product? What makes the product different from the others competing for their attention?
Details of Exercise
learn this here now Duration: Minimum of 1.5-2 hours, but it could take from a half-day to a full day.
* Duration also depends on the number of teams and depth of the presentation / discussion phase.
http://www.cordes-beregnung.de/pinochet/2689 How many can play / configuration of players: no real limit, although teams should generally be made up of 4-6 participants.
Facilitator and small groups (participants).
- Although the exercise may be done with one small group, multiple teams working in parallel on different boxes will result in a more robust discussion during the “selling phase.”
- The exercise works best with multi-disciplinary teams across units.
If this exercise is deployed during the ideation phase (which is typical), inputs can be any product knowledge that exists at that time, from an identified product need, the results of initial product brainstorming exercise, your current product name and logo, to whatever customer knowledge you have at the time.
- A plain box for each team. A “family size” cereal box will work well for most projects – the important part is that it be big enough to contain the required elements (see Part 2 of “Running the Game,” below), and that it not be too big (think furniture box) to overwhelm or give teams too much room.
- Big markers (to discourage detailed essays), coloured paper, old magazines, glue sticks, scissors, stickers, etc. Make sure you bring enough so that teams aren’t wasting time waiting for a pair of scissors or other tool / material.
- Some physical examples or images of really creative retail packaging (boxes) can be a good idea to inspire the teams before they get started.
- Consider bringing a video camera as it can be a good idea to record the “Sell the Box” part of the exercise to use in the debrief and/or keep as documentation. It can also serve to heighten people’s performance.
Running the Game 1
Part 1. Introduction / “Filling the box”
Before teams can begin designing and making their box, they need to brainstorm on what could go in it.
Give them a set amount of time to discuss some key questions:
- Possible names of the idea
- Possible customers, end users, or buyers
- Possible features, functions, or other important defining details.
You can adjust the introduction phase of this exercise depending on how familiar the teams are with the product / idea they are designing the box for.
The prep time before teams actually make their box isn’t meant to be exhaustive – the core of this exercise is parts 2 and 3 (below). The important part of this introductory step is that teams have “just enough” information to get started.
Part 2. Make the Box.
Ask the teams to imagine coming across the box on a retail shelf, shrink-wrapped and ready for sale.
Be clear that it does NOT matter if the project they’re working on won’t result in a tangible product actually sold in a box. This exercise is meant for product teams, applications, services, and can be used to facilitate any vision-oriented discussion.
Give them a set time to create a box for their idea.
Some questions to throw out to the groups to get them thinking about their box:
- What’s the tone?
- What’s it called?
- Who’s it for?
- What’s its tagline or slogan, the short hook on the front to entice someone to pick it up?
- What are its most compelling features? Benefits?
- What about system requirements?
- What imagery would make it stand out to you?
Typical elements that the teams should include in their box are:
- A product name
- A graphic
- A couple of key bullet points to “sell” the product
- Key features described on the back + any operating requirements.
Make sure you have ample supplies for them to create their box, and make sure they know that there is no wrong way to create their box.
* You can get teams to design the box on paper, or create a digital rendering of the box, although using simple materials to create a physical box is recommended.
A visible stopwatch set to the allotted time can be a good device to set limits and spur creativity.
Part 3: Sell the Box (aka “Sharing by selling”)
Time: 3-5 minutes per group + discussion after all of the selling has taken place
Each team is given an opportunity to sell their box to the larger group.
If you have time after the teams have finished creating their box, set aside 5-10 minutes for the teams to practice their sales pitch before selling their box to the larger group. Individual team members can take turns selling the box to their own teammates as a way to develop a coherent pitch to the group.
Things to look for / draw out from the group’s presentations:
- Look for a naturally occurring breakthrough as they present back their boxes. People typically put features on the box, but when they sell them, they translate those features into benefits.
- Listen for the phrases “so that” or “because,” which bridge otherwise mechanical features into living benefits.
* See below for suggested discussion points.
End of Game
- A better understanding of the project’s core value proposition
- A list / better understanding of key product features
- A vision statement and an elevator pitch: a short statement/pitch that allows the team to concisely explain or pitch the project to others
- A physical artifact that can be a real touchstone for the project – a concise expression of what the project is really about
Suggested discussion points:
- Get groups to respond to other teams’ pitches (“selling of the box”): what caught your attention, what would make you buy the product?
- Examine the artifacts from the process: what were some of the ideas that didn’t make it on to the box and why? If you had a second box, what changes would you make? Are there any ideas you would carry forward in your design process?
After the presentations by each group (the “selling the box” part of the exercise), you can start a discussion on how the multiple focal points can be reduced to a few key ones that everyone agrees on. Note that the idea isn’t to necessarily finalize anything at this point.
- Get groups to talk about their own internal process: what was it like to work within a limited form (the physical box) to articulate your idea? What worked well in your process and why? What were some of the challenges?
- Talk about the usefulness of the exercise as part of the design process, specifically the idea behind it: “Before you begin, focus on the end.” By imagining the package for their idea and then “selling it,” were teams able to start to make decisions about important features and other aspects of their product/service that are harder to articulate?
- Are there any traps in this exercise? Does anyone believe that this is NOT a useful exercise for interactive design teams? If so, why?
* As a backgrounder to this discussion point, read the article “<u>Don’t Design the Box</u>” – which questions the value of this exercise, particularly with teams of interactive designers.
The author believes in the value of merchandising, but questions “the idea of worrying about it too early in a design process, because when you do so you are engaging more in a marketing exercise than a product design exercise.”2
He also states “the ‘design the box’ exercise can be a powerful tool for generating ideas and for getting into the mind of the consumer. It is also, I fear, a trap insofar as it refocuses the designer from user experience to salesmanship.”
Next Steps after Exercise:
- Gather and record the brainstorming results and any drafts that were prepared in the making of the boxes as these can be a useful list of features, functions, benefits, etc. that your team can take forward.
- The completed boxes can also be used as inputs for vision statements or the crafting of elevator pitches.
- Using the record / notes from their discussions (and even the video recording of their pitches), the group can construct a good outline for a complete product vision document.
- Consider displaying the boxes around the office / workspace after the exercise as these can sometimes become touchstones for the project and can more useful than any of the documentation that comes out of the exercise.
“Even though it’s a playful output, it’s highly practical; one client kept a box on his shelf for six months, and would toss it over anytime someone asked what his team was doing with the new intranet. People understood the core of the product immediately, and enjoyed the break from reading yet another document describing an initiative.”
Final Notes from Facilitator
Consider running a second or multiple rounds: the exercise works well as an open-ended, divergent process, but if you’re aiming for agreement, you can repeat the exercise so that teams converge on an agreed-upon, shared box.
Variations on the Game
Instead of designing the box, teams can design the movie poster, the press release, or the trailer.
The key is to constrain the form so that teams are forced to focus in, from the user’s point of view, on what really matters about their idea, and to chose a form that leaves behind a tangible artifact that can serve as a touchstone for the project as it moves forward.
Resources and References
* All links accessed November 10, 2011
“Gamestorming: A Playbook for Innovators, Rulebreakers, and Changemakers” by Dave Gray, Sunni Brown, James Macanufo; O’Reilly, 2010 | http://www.gogamestorm.com/
(PDF) “Making the Vision Solid: Design-theBox and the Elevator Test” (no authors listed): http://goo.gl/fv51V
An article by Jim Highsmith – generally credited with coming up with this exercise – originally published in the 23 August 2001 issue of Cutter Consortium’s Agile Project Management E-Mail Advisor “reprinted with permission” on http://www.joelonsoftware.com/articles/JimHighsmithonProductVisi.html
Blog post: “Product Box, Discover what your customers really want through collaborative play,” http://innovationgames.com/product-box/
Blog post: “Don’t Design this Box”, http://www.graphpaper.com/2008/09-14_web-20-merchandising-dont-design-the-box