By Alfred Lettang & Jerome Kalumbu

Design Principles

Six simple steps to bring the design principles to life

Design principles are a set of short statement to help designers and stakeholders to make informed decisions during a project.

Design principles move the decision-making process away from personal opinion and provide a robust framework for making informed decisions to achieve business and user goals.

Why do we need design principles?

Design principles serve as guidelines and frameworks that help designers and stakeholders during the design process.

They provide a solid foundation for design decisions, promote consistency and user-centricity, enhance communication and collaboration, streamline the design process, and contribute to the establishment of a strong brand identity.

Design principles are essential for creating meaningful, usable, and delightful experiences.

These checklists and best practices are solutions to issues that we encountered during a 17-year period of designing digital products and collaborating with stakeholders and clients.

The 6 simple design principles steps

Design with purpose, clarity and elegance

  1. Don’t make assumptions
    Do research, analyse data
  2. Design with purpose
    Define brand & user groups
  3. Design for seamless experiences
    IA is users compass and guide
  4. Build products with smart, strategic content
    Content strategy
  5. Design with emotions and context
    Art direction
  6. Make, learn, iterate
    Wireframes, prototypes, visuals
Don't Start With Visuals book cover

Tips: Don't Start with visuals by Jerome Kalumbu - A creative approach with UX design tips to help you design effective and engaging websites. The book provides a step-by-step process for developing and communicating ideas effectively.

Process

Understanding upcoming tasks

1.Research - define problems and goals
Define project roles and responsibilities
Do research, analyse data. Don’t make assumptions
Define user needs, fears, struggles
Define business goals (e.g. drive more leads? signups?...)
Define the context of the project - initial brief
2. Brand and user groups - find solution
Understand user groups, user questions & objections, user tasks
Understand how our brand/product can solve these problems
Understand brand messaging
Create initial brand guidelines
3. Information architecture - define product structure
Understand hierarchy, content organisation, content tags, categories, user journeys, search functionality and features
4. Content strategy - write content draft
Create content draft for each page, based on user questions
& business goals
Start from landing pages
Review content drafts, content prioritities and calls to action.
Use AIDA model and Caveman Grunt Test to verify content
5. Art direction - connect your brand with customers
Define: Design direction, typography, colour palette,
images, iconography, video and animation style
Create a stylescape or design manual
Define the feelings/emotions the design should recall
6. Interface design & prototype - connect all dots
Low fidelity visual - make it easier to evaluate product concepts
High fidelity design closely matches the final result of a product’s design
Working prototype - test and see product in real environment
Stakeholder reviews
Visual, prototype and content iteration based on stakeholder reviews
Finalise your brand manual
Bring your product to life!

What happens if you don't follow design principles

When product fails, you fail too

  1. Iteration hell
  2. Missing  business goals
  3. Targeting the wrong users
  4. Not achieving correct conversions
  5. Communicating the wrong messages
  6. Confusing interface and user experience
  7. Confusion about your brand
  8. Difficult marketing
  9. Information overload
  10. High project costs
  11. Wrong content priorities
  12. Something feels wrong about the design, nobody knows what
  13. Wrong decision making
  14. Increase of micromanagement
  15. Increased workload for dev team
  16. Projects involves lots of risks
  17. Possible project failure
  18. Who is responsible for mistakes?