Learning Journal Week 19

Features table – I find the prioritisations very difficult to review.

I’m struggling to properly refer back to the storyboard.

Or, indeed, to the document we did on synthesising all our thoughts.

Haven’t we just skipped all that and gone for our prototype?

Also, haven’t we prototyped everything?  The prioritisation of elements hasn’t really worked. It has felt quicker and simpler just to write out the whole thing.

Are we missing something?

The ‘work it out on your own!’ rubric of activity 18 feels a tad unhelpful.

Cohort-wide call 9 June 2013

What an enjoyable call this was.

It was my first time to connect with many of the other people in the tutor group – Nuala, Nicola, Paige.

We should define the user of our product quite narrowly – the narrower the better.

The focus of the TMA is primarily about our learning on the block, not about the excellence of the website itself.

The purpose of a design narrative is to capture the design process so that in the future you don’t repeat the same mistakes.

‘Prototyping’ is most effective if you are testing whether something specific ‘works’ – maybe this helps address my confusion from last week about which bits to prototype.

It would be good to have a look at how design narratives are used in architecture, if there is time.