(Sorry for the cross-post, but...)
As part of my job search (plug), I'm writing case studies for my
portfolio, but the case studies inevitably run long. Too long.
The length answers complex interview questions like "walk me through
your process" and "how did you overcome an obstacle" and "how do you
communicate with non-designers".
Is it better to offer a bare bones case study with frequent links to
deliverables? Or is something more fleshed out better?
A list of deliverables gets me the interview, but I need something to
walk through with phone interviewers... kind of a web presentation.
Any advice? Tips? Best or worst practices?
Thinking & Making: IA, UX, and IxD
austin.govella at gmail.com
Austin Govella said:
> As part of my job search (plug), I'm writing case studies for my
> portfolio, but the case studies inevitably run long. Too long.
[snip for brevity ;-)]
> Any advice? Tips? Best or worst practices?
Write Case Studies That Sell
http://guerrillaconsulting.typepad.com/guerrilla_marketing_for_c/2005/05/tip_5_writing_a.html(or, in short: http://tinyurl.com/d667k)
Peter Boersma | Consultant User Experience
Koggestraat 10A | 1012 TA | Amsterdam | The Netherlands
phone: +31(0)206245641 | mobile: +31(0)615072747
mailto:peter at peterboersma.com | http://www.peterboersma.com