- Think from the angle of user but not developer or designer
- Minimize learning curve for user
- Reduce user brain burden
- Interface should be easy to understand and convenient to use
- Common Operation
- Consider 2 factor authentication, e.g., sending verification codes via email
- Prevent multiple logins at the same time to protect user account
- Show outstanding task not finish to user in inbox after login
- Alert user for tasks that near deadline
- Remind time could be set on user own for task start, 3/4, middle, 1/4 and due date
- User’s daily, most use and important function should be placed at most notable place
- Ensure all use case are handled and no missing
- Consider the most efficient and effective operation for user
- Keep everything simple and avoid too complicated steps
- Streamline the work flow between different parties and not miss important one
- Fine tune, change, delete or add additional function or flow if able to facilitate user daily work
- Message convey to user should be immediate, nearby, standout, understandable and no jargon
- Provide help and assistance if need
- Provide contact point for error and it could be saved as record with screen capture
- Technical Concern
- Responsive to different device, platform and browser use especially resolution
- Loading, response time and performance
- Maximum number of transactions
- Maximum number of user support
- Concurrency: prevent dead lock and no overwrite for multiple user access on same record
- Multilingual support
- Detailed logging on user, date time, operation, value before and after change
- Enable maintenance debug log by administration interface setting to trace problem
- Ensure security and privacy protection
- Flexible for future change
- Discuss earlier and check OK with user before submit document for confirmation
- Update skill set and reconsider the design approach with reference to latest trend or solution
- Don’t direct apply old method & practice to current problem without suitability consideration
- Security considerations for external interfaces
- Discuss design with architect, database administrator, project manager, programmer or other system analyst and most importantly user but not to disclose information to outsider
- Ask in public forum for advice on specific problem or design
- Loose coupling: less depends on other components and one change won’t affect the others
- Highly cohesion: modularize design in a way that encourage reuse of components and one module change does not require changes in other modules
- Ensure design to consider the followings: loading and response time (performance), maximum connection and transaction (scalability), support how many users at same time (concurrency), easy and convenient to use (useability), always available and able to recover (reliability), easy to maintain and extend (extendibility), encrypt data, block loophole, prevent penetration and attack (security), able to solve the problem (effectiveness) with minimum effort (efficiency).
- Concept proof by pilot test if necessary
- Prevent under or over design due to unrealistic estimation and insufficient evaluation
- Careful evaluation and consideration of design, approach and tools used before implementation
- No matter how good an idea or design is, success or not depends on actual implementation
Categories:
No responses yet