I am starting the development of an distributed team management product, called TeamCheckin, and I would love some opinions before I start spending lots of time and money on it!
Here are my thoughts on some features:
- Will consist of both a website and downloadable software
- Conceptually the product will have a Team, TeamLeader, TeamMembers, Projects and ProjectTargets, Alerts
- Any Team can invite other Teams to work on a specific Project
- Any Team can contain a TeamLeader, a number of TeamMembers, and a number of sub Teams
Benefits of TeamCheckin:
- TeamLeaders will be able to see the current state of any outsourced Project
- TeamLeaders can set and agree ProjectTargets with any outsourced Team
- TeamLeaders will be able to view Projects easily on a left-to-right timeline
- TeamLeaders will be sent an Alert if a TeamMember's computer is idle for a really long period of time, when they should be working
- TeamMembers can add in holiday days, sick days, post work statuses, giving TeamLeaders all this info in one place.
- All the above functionality will be inside the downloaded software, accessible from the system menu bar.
What are your thoughts? Am I inventing a solution to a problem that doesn't exist?
Any thoughts on badly needed features?
What, exactly, is the problem you're planning to solve with this program?
How do teams/managers work around this problem now?
Will information, once added here, become contractually binding in ways that wandering into someone's office for a chat wouldn't be?
How will you address privacy concerns?
Personally, I am amused by the time management device I use when it asks me where I've been because I haven't typed anything for 20 minutes. I would object to a Team Leader, or a Team Leader's Computer doing the same. It smacks of Big Brother.