information design

Good ideas need structure. Good structure needs an interface.
Good interfaces are transparent.

How do you intend to use knowledge?
How will data be entered?
In what ways will it be retrieved?

Who is your audience?
What level of interaction is required?
Is style more important than usability?
What are the key elements being communicated?

What volume of traffic are you expecting?
Are you supporting agent traffic?
How do you want to update your system?
Will you have distribution channels?

What statistics will you need?
What user behavior interests you?
What data are you capturing?

interactive narrative

Start with writing that works, then play with its variables.

What is your story?
Do we care?

Who are your main characters?
Are they real?

Where are we?
How does it look?

What kind of story is this?
Where does it fit?

production processes

Creative and technical direction are merging.

Is this system built to last?
How scalable are the components?

Is rapid development appropriate?
Are you using middleware effectively?
Is there an open source solution?

How should your team communicate?
Does your intranet serve the business?

event management

Take advantage of rapid development, flexible pre-made structures, and enjoy the show.

What is achievable?

What connectivity do you need?

goal-based learning

If you want to learn maths by Pokemon, do it. Just learn.

Where is the source data?
How do you make use of it?

Can you automatically extract value from available knowledge?

Does your audience want to learn?
How should you package your offering?

personalisation

Sites have character. Some have characters. Some will make an effort to know you.

Do your visuals support the concept?

You have the audience, what feedback can you give them?

How do you support community?
What do your users need?

muzak | books | pics | flics | about