Design Principles

Our philosophy, principles and practices govern and guide every experience designed by Taskmonk. The design at Taskmonk believes in familiar, meaningful, simple and comprehensive solutions achieved via focus on jobs to be done (JTBD).

Taskmonk Design revolves around 4 main attributes:

1.  Familiar - The design should be relevant and familiar to the users. Either existing labelling applications or any other applications that our Personas are using.  

2.  Simple - Less is more - The design should be clear and simple to convey the intended purpose clearly. It should be easily understood. No “frills”, embrace simplicity achieved through complexity of thought and design.

3.  Functional - Our product is meant for repeated daily use. Keep the design meaningful to ensure that the needs are met.

4. Learn-able - The design should facilitate the ease of learning. This can be measured by a learn-ability quotient

Taskmonk Document Template

How to use:

1. Open the Document shared in Zoho Writer

2. Go to File > Save as Template >

3. Name it “Taskmonk Document Template”

4. Save the template to “My Templates”

How to use:

1. Add it to your Templates if this is not yet available to you.

2. Always make a copy to create a new document.

3. Enter the details of the first page for purpose and intended target users of the document

4. Name the file. The template will automatically pickup this file name as the title of the document

5. Last modified is also automatically picked up.

Personas

Heuristics

Also known as Nielsen’s Heuristics (This can become a checklist we adhere to... we can add to this and create our own list):

 Visibility of system status: 

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

 Match between system and the real world: 

The system should speak the user's language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

 User control and freedom: 

Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

 Consistency and standards: 

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

 Error prevention: 

Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

 Recognition rather than recall: 

Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.

 Flexibility and efficiency of use: 

Accelerators—unseen by the novice user—may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

 Aesthetic and minimalist design: 

Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

 Help users recognize, diagnose, and recover from errors: 

Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

 Help and documentation: 

Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Design Artefacts