2 ms·
Agreed. The demo is a top-down management wet dream. A meeting where people get instructed in details to do specific tasks? No deadline, no ambiguity? Those guy
by pi-err 12y ago
Agreed. The demo is a top-down management wet dream. A meeting where people get instructed in details to do specific tasks? No deadline, no ambiguity? Those guys never attended a meeting.
UX wise, I'm not ok with the "red/orange/green" codes and "fail/done" tags. Even for a small startup, communication is not that blunt, for a reason. Red in the demo seems to stand for postponed, canceled, rejected or badly executed. Yet "red" means bad in most cultural contexts. The color code implies too much and would really harm any group using such a basic code.
- bujatt 12y agoHi pi-err, you make really good points. Also, if every team member could assign tasks, send requests and questions using this syntax, would that change your perception of this being a top-down management tool? Because our intention is to build a tool that allows a more horizontal communication among team members - but that's more difficult to visualize in a single video. We are also aware of the cultural-contextual association of colours. This is one thing we are actually struggling with. While colors are a very easy and effective way to communicate status of tasks, especially to give a quick overview of many tasks - they have severe limitations, just like you say, red evoking associations with something as being "bad".
- bujatt 12y agoDeadlines are on our roadmap. What do you mean by "no ambiguity"?