Here we go in week eight of project community course. After this 8 weeks I learned a lot and have a enough experience in using and talking about online communities. The research we made with my group was about the Indonesia Mengajar ( an Indonesian NGO) which main purpose is to reach the uneducated children in the rural areas.
And when we should talk about design principles I found 10 really important principles in design doesn’t matter for what kind of work we are going to use them. The following:
- Start with needs
- Do less
- Design with data
- Do the hard work to make it simple
- Iterate. Then iterate again.
- Build for inclusion
- Understand context
- Build digital services, not websites
- Be consistent, not uniform
- Make things open: it makes things better
The design process must start with identifying and thinking about real user needs. We should design around those — not around the way the ‘official process’ is at the moment. We must understand those needs thoroughly — interrogating data, not just making assumptions — and we should remember that what users ask for is not always what they need. If you research about our NGO you can see how they work with the same structure or with most of the steps.
Something really important when you want to reach a huge amount of people is to make it simple and working. Making something look simple is easy; making something simple to use is much harder — especially when the underlying systems are complex — but that’s what we should be doing. This part is the key to the success. When we have simple and easy to use design people have easy access and they can spend more time on it. Accessible design is good design. We should build a product that’s as inclusive, legible and readable as possible. If we have to sacrifice elegance — so be it. We shouldn’t be afraid of the obvious, shouldn’t try to reinvent web design conventions and should set expectations clearly. We’re not designing for a screen, we’re designing for people. We need to think hard about the context in which they’re using our services. Are they in a library? Are they on a phone? Are they only really familiar with Facebook? Have they never used the web before?
We’re designing for a very diverse group of users with very different technologies and needs. We need to make sure we’ve understood the technological and practical circumstances in which our services are used. Otherwise we risk designing beautiful services that aren’t relevant to people’s lives.