This is the celebrated journal of Mr. Simon Collison A.K.A Colly

Process Toolbox, part nine: Narrative

22nd March 2010

At last, we reach the final transcript from The Process Toolbox presentation. Over the previous eight posts, we’ve looked at backbone, collaboration, audience, methodology, roadmap, creativity, convention, and prototyping. To conclude, we’ll look at a method for pooling all of this together to reduce noise and leave only the finest signals to present a project narrative - a single, focused design path.

Following a direction to reach our goal

If everything has gone to plan throughout the process, then we’ll have arrived at a superbly functional system with strong visual design, arrived at in an iterative manner.

Many of you will agree that the days of offering up three or four polished designs are long gone, and frankly a waste of time. We can save money and work smarter here.

We should educate our clients that a website will be designed along a specific path. Our research and processes equip us to follow a certain direction, offering up rough sketches, basic wireframes, more complex wireframes, a prototype and so on. We can then do some colouring in as we evolve the suggested design. All the way through, we’re exploring a single, focused design path.

With a solid understanding of the intended audience, and as a result of a well-honed process, we should be confident enough to explore a single path and ultimately result in a successful, stunning product.

Deliverables sheets

I like to give a client a sheet linked to Basecamp that acts as an ongoing Table of Contents for the process. It’s a one-stop-shop for actual deliverables. The noise is all in Basecamp, whereas here what we have just the real signals; all are deliverables -  pure output.

Move through each batch one-by-one and the process is clear. There is a narrative - a journey. The path page is proof of concept - it backs up all the promises we made to the client at the beginning.

The deliverables the sheet links to (sitemaps, wireframes, batches of comps or prototype files, experiments) are all in chronological order. There is a progression - a path. It is one single focused design path, and acts as a repeatable framework for future releases.

This is another tool I couldn’t be without. It’s just a few HTML files and links to the deliverables uploaded, but this works very hard and provides a constant focus throughout the project cycle.


Over this and the other eight posts, I’ve outlined a number of tools and methods that you can twist even further, and mix with your own process. Along the way, we’ve explored tools that help create empathy, simplicity, flexibility, creativity, quality and relevancy.

So, you might be a designer, a developer, a creative director; a freelancer, or part of a team. Maybe you represent a communications team, or are looking to commission a major web project. Whatever your stake in the web, I’d hope that some of the ideas that I have presented give you some measurable value, and fresh ideas to take back to your colleagues and assist with devising your own flexible tools.

Most of the budgets we work with need to cover our responsible processes. These figures are often called into question by potential clients who might not initially appreciate the inherent value. Every time we explore and illustrate the merits of a good process we hopefully help those new to web commissioning understand why its so valuable.

And with that, I’m closing my toolbox.

*Note:* Slides designed by Gregory Wood.

Full series…

This article was originally posted on Erskine Labs, September 2009.


# Gonzalo González Mora responded on 22nd March 2010 with...

I just finished reading the whole series… it was really impressive and inspiring. I especially loved the prototyping insight (designing in-browser, feedback forms and overlays in prototypes, etc.). Thank you very much for this posts! Cheers from Argentina!


# Simon Collison responded on 22nd March 2010 with...

Hi Gonzalo - and thank you for your very kind comment. I’m delighted you got so much from the series.

# Tony responded on 22nd March 2010 with...

Hello , I’ve read the book ‘beginning css web development’, and learned a lot from your book. Do you have any other ways to contact with you ? such as Skype or messenger ...... I have a lot of questions to discuss with you .

# Simon Collison responded on 22nd March 2010 with...

@Tony: Thanks for reading the book. I’d be happy to answer any questions you have, but time is never on my side. Feel free to email me on simon[@]colly[dot]com

# Stanley Wood responded on 22nd March 2010 with...

Really enjoyed this series, and was wondering what the “sheet linked to Basecamp that acts as an ongoing Table of Contents” was (ie. was it an online html file, pdf with predefined links, a message within Basecamp)?

Thanks again for all the help your giving back,

# resume responded on 22nd March 2010 with...

I’m currently reading this book, I just came across your Web site and started it. Anyway, as soon as I started reading it I couldn’t stop. It’s one of those books that you can’t put down.

It’s not a very large book. But definitely useful! Thank you Simon!

# Natasha Maria Fernandez-Fountain responded on 30th March 2010 with...

Wow, these are just great. I’ve just finished with the entire series and I feel like I’ve learned so much. As a designer, it’s always an eye opener to hear about another process in depth like this. Thank you for sharing this!

# Shane responded on 8th April 2010 with...

Nice post, I think I definitely need to see all the other ones in the series. Very uselful, Thanks.

Responses are now disabled Your ability to respond is disabled automatically some 30 days after articles are published, or manually much sooner if spamming guttersnipes target a particular article.

Prev 802 Next

Superfluous Aside

Archived in Design & Web, Writing & Speaking

Written in Nottingham

There are 8 responses

External References

Copyright © Mr. Simon Collison 2003-2017. Protected and licensed under a Creative Commons License. Grab the RSS feed

Engineered in Nottingham, scaffolded by ExpressionEngine, steam-pumped by United & kept alive with tea and hugs.