Involving developers throughout in the process is important because designers come up with the solutions, and developers can check if they are doable.
A good idea is useless if it can’t be done in time, within budget, or with the available resources.
Should designers avoid suggesting foolproof solutions?
Split the solutions into two parts.
Example
| 1. Details out all the possibilities based on feasibility evaluation. | 2. Suggest best solution that is currently not possible due to feasibility constraints. |
|---|---|
| Possibility 1: Enable users to mention or tag team members directly in task comments for smoother and direct communication. Possibility 2: Experiment with various algorithms to enhance the precisions of suggested tasks. | An advanced feature could involve integrating artificial intelligence to automatically prioritise tasks based on the user’s habits. |
Leave a Reply