Rapid Prototyping

In one day you learn to turn an idea into something people can pick up and try out: a draft that someone can actually use, rather than a description. The workshop is for people who have something in mind and do not yet know whether it will hold up.

Group
2-8 people
Duration
7.5 hours
For
Practitioners
Focus
Build prototypes
Scope
1 person-day

Description

Schedule of the day

The sequence follows what you bring with you, but the underlying pattern stays the same. We start with the question the prototype is meant to answer. We then sketch quickly and in several variants, rather than working out one idea straight away. The sketches become a draft that can be used, the draft goes into a test, and the test leads to a revision.

That last loop is where most of the learning happens. Once you have seen how quickly an assumption falls apart with the first test user, you work differently afterwards.

Result

At the end you have wireframes, mockups and at least one prototype that can be experienced: clickable on screen, or as real hardware with a user interface. Instead of a concept paper or a slide deck, you hold something you can show the next day to a colleague who was not in the room.

Rapid or experimental?

Both workshops run for a day and have almost the same name, but they answer different questions.

Rapid prototyping finds out whether an idea works for the people meant to use it. It is about ease of use, clarity and usefulness. You can experience the prototype, but its functions are only simulated.

Experimental prototyping finds out whether something can be built at all. It is about feasibility. The draft performs the basic functions but looks unfinished while doing so.

The choice depends on what is unclear in your case. If you do not know whether people will cope with it, take rapid prototyping. If you do not know whether it works technically, take the experimental workshop.

Requirements

You should be able to think visually and get your thoughts onto paper. This is not about drawing in the artistic sense; boxes and arrows will do. You also need good powers of observation: you only learn from a prototype if you see what actually happens in a test rather than what was supposed to happen.

You should also be willing to try an unfamiliar method. You need no prior knowledge of software, design or development.

Not suited for

If it is already settled what the result should look like, the prototype only confirms what had been decided anyway, and the day is wasted.

The same applies when the certainty is only a feeling. Anyone convinced they know how it must look grows impatient rather than curious at the first user test. The method only works if you are ready to experiment.

Related

Request this workshop

Scope: 1 person-day on site. Preparation and follow-up are additional and depend on the format. I will tell you what they involve in our preliminary talk.

Let us talk about your project.

Call +49 228 629 380 60 I can be reached on working days. If I cannot pick up, I will call you back. Book appointment Take a free slot in the calendar A short conversation clears up a lot.