The document describes an idea-to-action workflow platform that allows users to: 1. Add ideas privately and then convert them to discussions or projects. 2. Discuss ideas and add comments as a discussion progresses. 3. Create projects from discussions and assign tasks with status levels of backlog, todo, and done. 4. Collaborate on tasks in real-time with notifications of updates. 5. Administrators can customize the workflow and user interfaces.

1. IDEAS - DISCUSSIONS - PROJECTS
A process based user platform to
convert ideas to action and results

2. ROLES & OWNERSHIP
Capabilities - who sees and can do what is controlled either by
role or by ownership.
The following step-by-step illustration uses a single role while
ownership follows through from idea to discussion to project.
Different roles like product owner, client, project lead, team
member, supplier and so forth can be had.

3. Dennis is logged on and can see all in one place:

4. Dennis will add a new idea to his private ideas collection:

5. Idea title, the idea itself, and even files can be added:

6. Dennis’ idea nursery could also be populated from external
sources, like one’s favorites at Twitter or similar:

7. Dennis can add notes to his ideas, delete them or convert them
at any time - nursing his ideas (click green text to expand):

8. Here he is converting an idea to a discussion - a logical next
step for mature ideas. The conversion carries over all notes:

9. The initiator of a discussion is also requested to set who shall
see and engage in the discussion:

10. Choosing all members of one or more teams, or one or more
individuals:

11. Email notification is up to discussion/message initiator:

12. The chosen few sees this on their screen:

13. And can add comments at any time, like James here:

14. Comments are displayed with the newest on top:

15. Dennis decides the discussion is ready to be acted upon:

16. Converting the discussion carries over all former notes and
comments - keeping full context with the project forever:

17. Dennis adds full project description and even more files:

18. A project needs a (virtual) team:

19. So Dennis can reactivate on old, use an active or create a new:

20. Then add members (Dennis the team owner can remove or
add members to his teams at any time):

21. And James, who has been added to a new team is notified and
have a choice:

22. Back to Dennis who has an automatic task to add the first task
to his new project (which is fully visible in his task):

23. Adding a task title, full description and instructions and files if
relevant:

24. When Dennis has added a task he will always be prompted:

25. All users can see all the projects they’re engaged in, in real time:

26. The system knows who you are. Here the user is inspecting a
project (and it’s tasks) where he’s a team member only:

27. And here the user is inspecting a project (and it’s tasks) where
he’s the owner - now allowed to do much more:

28. The system notifies all team members of important events:

29. NOTE: THE TASK STATUS
Tasks have three status levels which controls what can be done
with them, and by whom:
1. Backlog. The beginning of a task’s life, not yet actionable. The
project owner controls this level and can even delete tasks.
2. Todo. The project owner fills this up with tasks from his
backlog. Now team members can pick them up and do
them. The todo list has a limit to ensure continuos prioritizing.
3. Done.

30. When a task has been moved to the todo list any team
member can pick it up (sorted by project) :

31. Or add a comment to any task or project. This allows all team
members to engage in all aspects of the project at any time:

32. James has picked up a task. All pertinent information is delivered
in the same interface (green text expands the content):

33. Including the fields to fill in or files to be added:

34. When James has done his, Dennis the task adder, will be asked
to review - and send back for more if required:

35. Same interface but with expanded task information field:

36. When it makes sense the system will prompt you: You have
accepted a done task, would you like to add a follow up task?

37. Or when a task has been picked up, would you like to move
another task from backlog to todo list?

38. The list of green links to the left allows you to keep an eye on
everything, and act if required, in real time - here my teams:

39. Or the ‘Who’s doing what’ overview - real transparency:

40. Any user can add a new user:

41. Setting username (email), name and password:

42. And quite important, if the new user shall see any existing
discussions:

43. If yes, then choose what discussions:

44. When the new user logs on for the first time he’ll be asked to
update and add more of his details:

45. Including location and more:

46. THANK YOU
FOR YOUR TIME!
A demo to play with, a video and more can be found on
thingamy.com

47. ADDENDUM
Admin interfaces

48. Semantics and fields can be changed on the fly:

49. Flow paths can be changed by drag and drop - which means
new functionality can be added at any time as well:

50. What the user can see, what shall she/he fill in, can be changed
at any time:

51. View of what’s going on can be added, changed or hidden:

52. Or details can be edited:

53. And roles can be set: