I have become a fan of getting it wrong. Deliberately.
Ultimately it saves me a lot of time.
To explain: currently we are modelling how education.au intranet could be structured. All my preparations for this - content management, portal home page, security model mock-ups have been put up with the proviso that it’s probably totally wrong (requires only a pinch of courage).
What I find out quickly:
- People actually state their opinion on what’s been presented
- What’s wrong with it
- What people want
- What the big picture really should be
Informed by this, I can then model what’s really needed and then go do it.
By simply spending a little time in turning an idea into a picture - it gives other people something to kick against.
A slight twist on this is simply having a go and seeing it it works or not. Proof of Concepts are a case in point (without the deliberately getting wrong bit). It is geared to see if we can create something innovative and useful. The best way to see if we have got it either right or wrong is to visualise it with a rapid prototype.
Makes me think of the Sir Ken Robinson TED Talk nativity story (at 4m30s) where kids are not afraid of being wrong - but have a go anyway. Through this, they learn and grow.
It’s very useful - give it a go.
The proof of the pudding is in the eating as they say.
Post a Comment