A guide to building prototypes

(and maybe how to do some other kinds of development)

Tristan FerneBBC R&D Prototyping team

!what

Not really about what a prototype is, or what bits of a system you should prototype

!why

Nor is it about why you should build prototypes

how

It's about how you go about building them, particularly in teamsAnd it's not definitive in any way, just some things I've learnt

Ideas are easyBuilding things is

harder

So start off by prototyping something

Build it to understand and

surface problems

Because until you build it you won't truly understand it

Research your area

There aren't many new ideas so you must know about the area you're going into

Don’t chase shiny things

It will distract you.And similarly, don't get hung up on particular technologiesYou should support people's passions, but be pragmatic

Make it simple

simple

...then simpler still

Embrace {constraints}

They are there to help you and make you more creative

Define some scope

Even if you're not given any, create some limits yourself to what you're going to build. You can change the scope later but you'll have something to work to.

Know when to stop

Make up a deadline if necessary, and then reduce scope if you're not going to make it

Itera

Iterate to make it betterAll of this is a way of saying use agile development...deliver working software, respond to change, use sprints.But I'm not going to argue with you about methodologies, there are lots out there, just be prepared to be flexible

Iterat

Iterate

T-shaped people

That is, people who have broad interests in many directions but have deep knowledge and skills in one particular area

Work together

Ideally you want engineers and designers to work closely to explore problems from many perspectives simultaneously. I believe that the best things come from a fusion of design and engineering.

Work togetherAnd talk a lot

Talk a lot within the team and make sure everyone knows what everyone else is doing.

Sketch

On envelopes or napkins or with code. Creating quick low fidelity prototypes helps communicate problems and create a shared understanding of what you're doing.

Lowest resolution

Make it good enough to work and look good enough to interest people, but don't spend time on optimisation or making it too polished.

Tell people about it

Talking about, or presenting, your project helps you form and develop your ideas, and obviously gets other people thinking and engaged

Make it fun

Make it fun(but not frivolous)

START

Once you get going it will get easier. But be ready to iterate or even fail.

Tristan FerneBBC R&D Prototyping team

http://www.cookinrelaxin.com/2010/04/guide-to-building-prototypes.html

One last thing I just thought of. Don't be afraid to ask questions.

Those are some things I think are important when building prototypes. I hope you might find them useful in some part of your work.

You can read more at this url:

http://www.cookinrelaxin.com/2010/04/guide-to-building-prototypes.html