Co-Preneur on Tuesday mornings

What are you doing on Tuesday mornings, between 9am and 12pm? Are you in Richmond around that time? Fancy doing some Co-Preneuring?I’ve recently been working on starting a business, called Indy Socks. You can see some Mission Reports that we’re posted on Ross’s site talking all about the concept. I won’t go into detail here (for the moment). I’m pretty excited about launching this little business and can’t wait to be ‘live.’

Indy Socks Mission Status from Ross Hill on Vimeo.

However, one of the things I have struggled with is how to find the consistent time required to make progress on the business. I’m pretty bad at scheduling in ‘work time’ when it’s my own to schedule and I had small epiphany recently.  I realised that, in my calendar, the things which are prioritized most are meetings with people. (duh). But why is this the case? Shouldn’t I be more committed to blocking out time to myself to just get stuff done? Easier said than done!

So, to counter this I’m going to borrow from some of the ideas that circulate in the programming/IT world. Particularly, the concept of pair-programming. I think there are a heap of organisation/productive tools programmers use today which we will see as standards in the business world in a few years time. Agile DevelopmentTest Driven DevelopmentMVCand REST methodologies.

But for the moment, I’m going to see if pairing up with someone, between the hours of 9am and 12pm every Tuesday at Inspire9 will help me get more traction towards getting the business launched. I’m going to call this Co-Preneuring. It’s not about finding a business partner, or sharing equity or any of the other messy things that come with sharing a business with someone. I’m asking that, if you have a few spare hours and would like to sit together and work towards launching a business, then swing by and we can crank it out together. Of course, I’d only be to happy to repay the favor and sit with you whilst you ‘got it done’ in the afternoons or at other times.

You don’t need any special skills, just the ability to ride shotgun and work together getting whatever needs to happen, done.So, if you’re keen to come along and co-preneur with me, then leave a comment below about the date you can come along and i’ll see you there!

How to Prototype: The Awesome Guide

This is a guest post from Lindsay Gordon, prototyping genious from South East Water. Lindsay attended Olin College in Massachusetts, got a degree in engineering and most importantly, got taught by IDEO. She now works here at South East Water’s Recycled Water program and helps me be inspired through her ideas about how to Prototype. If you want to get in touch with Lindsay, she will be answering comments on this post or email: lindsaygor@gmail.com.

At its simplest, a prototype is a representative model used to test a design concept. Prototypes can be built out of paper and tape or machined using advanced materials and techniques. Regardless of the level of detail, prototyping is a very valuable exercise during the design phase of any project. This quick overview provides an explanation of why prototyping is important, how to do it and why engaging users is vital.

Why is prototyping useful?

1. ‘Proof of Principle’/Exploration
o Making a physical model can be a source of creativity to get the juices flowing before you have all the answers
o Gives you an opportunity to test the ‘proof of principle’ of your most basic idea and find unexpected problems
o Allows you to explore design alternatives, improve the design and allow your team to appreciate the experience of the end user

2. Communication of your idea
o Internal: Words leave room for misinterpretation, simple 3-D models can communicate ideas to team members and convince them of your design concepts
o External: A slightly more sophisticated model can be very useful in pitching/selling your idea to stakeholders. Shows a good understanding of the product/service and facilitates visualisation of your idea

3. User Involvement
o Giving your user something tactile requires user involvement in the design process (easier to understand users and their experiences, behaviours, perceptions and needs with a physical object)
o User feedback is delivered in real time while they’re experimenting with the prototype

iVend

Quick-and-Dirty Prototyping

Rough prototyping involves using any materials available to make a quick, simple and cheap 3-D model of your product or service.

The scale will depend on what product/service you’re modelling: actual size may make sense for some items (telephone) but others may require larger (medical devices) or smaller (buildings) scale. Use any materials you can find: straws, cardboard, fabric, wood, foam core, hot glue, rubber bands, post it notes, polystyrene, toothpicks etc. It also may be useful to take apart existing products to find materials.

Tips:
1. When involving users don’t worry about creating a professional looking model but make it refined enough that it won’t distract them. You want them to take you seriously but if the prototype has too much detail users may focus on the wrong things (e.g. a button is too big)
2. Early models should invite improvement! Inspire your audience to assess the service through the eyes of a customer and imagine the concept evolving into something they would enjoy using

How to model a service

Vending Machine opperators and service patterns

Modelling a service is a bit trickier than modelling a product. A service model needs to focus on the interaction between the user and the service and highlight all the key players involved in the duration of the service.

o Visual: Storyboards, vignettes, cartoons and amateur videos are all good tools to model your service. Focus on service scenarios: physical elements, interactions and action sequences with various key players
o Where applicable, create 3-D models of any interfaces between customers and service components
o Find an initial group of a few key customers that are willing to help with the prototyping, will brainstorm possible service scenarios, look over storyboards, interfaces, etc.
Above info taken from this interesting article about service prototypes

Why human focused design?

Designing WITH the user and not FOR the user takes the guesswork out of whether your final product will be useful. Products and services should be designed to fit in with a user’s current behaviours and values rather than force them to change to accommodate your new design.

“User Oriented Design = Subway (now I’m doing the cheese, which kind would you like) instead of “I made you a sandwich, hope you like what I put in it”

Working closely with users provides opportunities for feedback at each step of the design process. Spend time with people in your intended user group and try to witness them in their natural habitat; you can learn a lot from observing specific activities and putting yourself in your user’s shoes.

Another way to test your model is to engage individuals who are completely unfamiliar with the product or service and ask them to evaluate their experience with your prototype. This can provide valuable feedback about whether your design is intuitive and easy to use. Jan Chipchase runs an amazing blog where he researches people’s habits with mobile phones accross cutlures for this purpose.

Next Steps

If you’ve had success with rough prototyping and are looking for a more sophisticated prototyping method you may want to check out 3-D modelling software (such as Google’s SketchUp which is free, has great video tutorials and is quite intuitive). There may also be opportunities to create a working prototype or more advanced models using rapid prototyping companies.

Leave me a comment or flick me an email if you have any other questions about prototyping!