Posted by jc-Qualitystreet on 2011/10/17
Speed Boat is one of the « Innovation games« , one of those games that, like Product Vision Box , Remember the future or Buy a feature, is very useful during our Agile and UX workshops.
Speedboat is an interactive, collective and funny way to identify constraints, obstacles, problems with our product or our project, then to prioritize actions in order to remove them!
Speed boat, a boat with many facets…
The advantage of the Speed Boat metaphor is that the game can be very useful in a lot of contexts. Indeed, our boat is appropriate to represent our development project (which does not advance for some reason…), our product, subject to criticisms and comments of its users or the team in charge to bring agility to the organization.
Result of our Speedboat WorkShop ...The goal is the Agile Enterprise
The rules of the game
- Draw a speed boat on a whiteboard or poster
- The boat is our system, our product, our project or our team, so name it (Here, the boat is our Agile transition team)
- Of course, the objective of the Speed boat (our product…) is to go fast (for best performance). So I first ask the participants to describe us precisely what characterizes the optimal performance, the desirable conditions (yellow notes attached to the port or on the island that the boat needs to reach)
- The boat position represents today and the distance between the boat and the island can be seen as an indicator (not in our case)
- The anchors represent the obstacles slowing the movement of our boat: impediments or things that our customers or users do not like about our product and affect its optimal functioning. The more they are low under the water, the more they are strong (well, up to you to follow this rule!)
- The green arrows represent positive elements that push our boat
Several variations exist. Here is mine
- Steps 1 & 2 After the opening and introduction of the game, I usually ask participants to work individually or in pairs (depending on group size) on the goal (desirable conditions) and the positive factors then to present their work to others.
- Step 3: Then, individually or in small groups it is time to characterize the anchors (obstacles, constraints, things we don’t like)
- Step 4: The work done, I ask the participants to post their anchors on the wall.
- Step 5: Collective consolidation and anchors prioritization
- Step 6: I usually close the game with an action plan to set up to remove the major anchors!
In short, we generally have a good time playing that game: enjoyable, useful but also very effective!
Posted by jc-Qualitystreet on 2011/04/20
Activity #3 of the Agile UX practitioner…
The Agile UX practitioner shares with the team his knowledge of the design principles and User Interface patterns …
This is a daily activity for the AGILE UX PRACTIONNER. It consists in fostering learning on users’ cognitive processes (learning, perception, memory, problem solving…), design principles… and continuously making the focus on User Centered Design, via deliverables and above all collaborative workshops, both with development and business teams.
This list of 11 principles of interface design is a good starting point:
Leading users through an interaction, guiding them through the accomplishment of specific tasks, indicating the possible actions that can be taken or just informing them about their context
Enabling easy reading and fostering a good understanding of what is displayed on the screen: the physiological process of reading but also the understanding of what is read.
Principle # 3: Grouping
Establishing and visually reinforcing structure and relationships, providing functional groupings of associated elements.
Principle # 4: Direct Feedback
Giving immediate and appropriate feedback, keeping the user informed of what’s happening.
Principle #5: User Control
Always enabling the user control over the actions of the system, the dialogue and interactions.
Principle #6: Simplicity
Ensuring conciseness, minimizing interface complexity, offering the proper amount of information and relevant functionalities.
Principle # 7: Error Management
Preventing user errors, helping to manage when they occur (reduction and recovery), providing good error messages.
Principle # 8: Flexibility
Adapting to the characteristics or specific needs of the users (views, preferences…), providing accelerators and allowing interface customization.
Principle # 9: Consistency
Providing the user with a stable framework – navigation, interactions, language, styles, appearance, procedural usage… – in similar contexts.
Principle #10: Significance & Meaningfulness
Speaking the user language, fostering simple and natural dialogue, using meaningful illustrations.
Principle #11: Compatibility
Adapt to the procedures, activities or characteristics of the users, designing for mental models, but also taking into account standards and conventions of identical contexts and situations.
Posted by jc-Qualitystreet on 2011/03/08
Activity #2 of the Agile UX practitioner…
(See the Activity#1: Vision)
The Agile UX practitioner creates Personas collaboratively…
A persona is a user-archetype, a fictional representation of target users you can use to help guide decisions about product, features, navigation, visual design…
Persona "Sophie" (for a french banking project) Contexts-Goals-Implications in an agile way. Personas workshop
Personas are an essential element of the product Vision envisioned at a strategy level. They represent the first sections of our Vision formula (from Geoffrey Moore): FOR (target for the product) …WHO (users’ needs), a key element of the famous elevator pitch.
The persona approach provides a team with a common and shared understanding of the users of a service or product (but also what they want, their behavior, their needs and expectations) in a very engaging format, easily linked to Agile User Stories.
In short, personas are a fantastic way to integrate real User Experience all along the product development project.
And this is the role of the Agile UX practitioner to be the Personas promoter and to initiate their creation in collaboration with the Product Owner and the Team.
Create the Personas with Agile Teams
Everything starts at the beginning of the project, before sprint 1 (a sprint 0 or short exploration is an appropriate period for doing it). But, the persona approach requires mobilizing the entire team around it and should be envisioned collaboratively.
- Organize one or two workshops with the Product Owner and various stakeholders in order to be aligned to the objectives and the approach, to identify data sources, to determine categories of people to interview (for example the core roles)
- Inform the entire team of the process
- Then collect data from various sources including user interviews.
2 Construct collaboratively
- Analyze data (facts) in collaborative workshops using affinity diagram and identify variables then patterns
- Create the Personas skeletons
- Give birth to the personas (including storytelling, writting and visual design) using the format you prefer (formal or not)
- Validate the results with various stakeholders
A Persona Template (more formal)
3 Communicate & Use
- Include the Personas on the Information Radiator within the team environment
- Link the Personas to User Stories
- Use them as a prioritization tool (in the Product Backlog) and a designing tool (related to specific user stories)
- If necessary, make a communication plan for marketing and sales activities: make a buzz!
Personas Ericsson Life in 2020: Make the Buzz!
Posted by jc-Qualitystreet on 2011/03/04
Activity #1 of the Agile UX practitioner…
The Agile UX practitioner helps to define the product Vision…
Agile or not, the Vision is crucial
At an organization level, the vision helps to appreciate and believe in the company. On a daily basis, and from a team and employee point of view, it’s a good way to create meaning in work.
One product, One Vision…
At any product is necessarily associated with a Vision, setting the course, giving meaning and describing what is envisioned for the product in the short, medium or long term. The product Vision and the Personas form the foundations of the entire user experience of the product (Strategy element).Vision is also the highest level of agile planning (Daily-> Sprint -> Release -> Roadmap -> Vision)
« Fits in a shirt pocket, syncs seamlessly With PC, fast and easy to use, No more than $ 299 « …
like the vision of Hawkins for the Palm Pilot, the product vision is often short, goals driven and related to a problem.
But to be meaningful, effective and to federate individuals around it, the product vision must be shared with the team. In Scrum, that is the job of the Product Owner, and that should be completed before the team starts working its first sprint.
Building and sharing the product vision is a huge challenge for the Product Owner. And the Agile UX practitioner has an important role to play (as a workshop facilitator or input provider based on user research) to help him in such difficult task. Again, collaboration is the key and the most effective techniques to define and share the vision are collaborative. Here is a focus on the main activities and facilitation techniques I use during the Vision workshops with my clients.
PRODUCT VISION BOX (my favorite)
From Highsmith (2004). The « Product Vision Box » is a very appropriate technique when starting a project to create the vision and share it with the team responsible to design the product (and why not, those in charge of the sale).
One product = One Vision = One Product Vision Box
The all team creates a visual, concrete image of the software, product or service which it is supposed to develop. They build together their own product vision BOX. So, the final result is always a single box, although in the context of the workshop, several intermediate boxes can be created by sub-groups.
This final box is built collectively in the consensus and collaboration. It represents the shared vision, and includes the following elements:
- Front: Name – Picture or drawing (if possible) – Slogan – 3 / 4 Bullets arguments for Sale
- Back: A more detailed view with more functionality, the pre-requisites …
The workshop has a playful side. It promotes discussions, collaboration and requires participants to go straight to the point and set priorities.
Front: Product Vision Box of this blog!
Back: Product Vision Box of this blog!
PRODUCT BOX (the most UX)
From Hohmann (2006). The Product box is one of the most useful and popular « innovation games ». The technique is both very close to the previous format and different (due to its strong « UX » connotation »). With the product box we really have the VOICE of THE CUSTOMER.
One Product = n Visions = n Boxes
The « Product Box » workshop is above all customer-oriented. Its purpose is to collect the maximum users’ feedbacks about an existing product. So users are invited to participate to the « game »: designing the box that they would buy, and then to imagining that they’re selling the product at a trade show or at the supermarket (represented by the facilitator and the other customers).
The cereal box is a good example to introduce the game to the participants.
Example of a cereal box
Customers can work individually or form sub-groups (3 persons). The box (the customer vision) includes the same elements as above (and more …)
- Front: Name – Picture or drawing (if possible) – Slogan – 3 / 4 Bullets arguments for Sale
- Back: View more detailed with more functionality, the pre-requisites…
The « Product box » technique is highly relevant to innovation. It is very useful in view of improving the product, or to explore and collect users’ needs. My objective as a facilitator is to get the maximum of boxes, even if at the end of the workshops, an important work of analysis has to be planned.
How does it work?
- 40 minutes to design the box (individually or in groups of 3 persons)
- And 5 minutes by box to sell it to other groups or individuals.
The Product box can guide a final vision by drawing what customers want, how they envision the product, what they expect, what they find most interesting, what they focus on, and also what arguments they use to sell it. If I took the example of my blog , I would invite 16 passionate readers of agile-ux a Saturday afternoon, to create several AgileUX Vision boxes and sell it to the others… 🙂
Vision Statement (a must!)
From Moore (1991). It is also called « the statement of position » or « Elevator Pitch ». Actually it’s a formula to pass the famous elevator test (explain your product in the time it takes to ride up in an elevator).
The model is really efficient: I use it consistently with my clients. It is a precious facilitation tool useful to explore, create and share a product vision.
The Vision formula applied... On the wall, with the team, from the beginning to the end of the project
The vision statement is structured into 6 sections that summarize in less than two minutes (elevator pitch) the vision of the product.
FOR (target for the product)
WHO (users’ needs)
OUR PRODUCT IS (the product category)
THAT (major benefit, key functionalities)
UNLIKE (current practice, competition)
OUR PRODUCT (major differentiator)
A two-column presentation is a good practice but a linear version (elevator pitch format) works well too…