GB2358722A - Automated follow through on user goals - Google Patents

Abstract

A system which provides automated follow through on user goals by auto-prompting users via an electronic network. System data is input for defining system operation and user goals, computing one or more goal triggers based on the system data, and linking context sensitive information for assisting users in accomplishing their goals to the goal triggers. The goal triggers linked to the context sensitive information are used to automatically generate user goal prompts which are transmitted over the electronic network to a computer interface for presentation to the users. Qualitative and quantitative user data regarding the user goals are captured from users in response to the user goal prompts presented at the computer interface. The context sensitive information is updated based on the system data and captured user data, and additional goal triggers, user goal prompts and reports are generated based on the system data and captured user data. Prompts may be sent using a voice mail system.

Description

2358722 AUTOMATED FOLLOW THROUGH SYSTEM AND METHOD

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application No.

60/148,035, filed August 10, 1999 entitled "Automated Follow Through System and Method", the contents of which is hereby incorporated by reference in its entirety.

COPYRIGHT NOTICE AND AUTHORIZATION Portions of the documentation in this patent document contain material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and

Trademark Office file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

The present invention relates to a computer-implemented system and method for automated follow through on user goals via an electronic network.

Research shows that only 15% of those who attend training, leadership development, educational programs and conferences, or who have development discussions with their managers and receive structured feedback, put something that they have learned into actions that improve results. The same can be said for many management meetings where goals are often committed to, but not followed by, actions that improve results.

There are several reasons for this lack of follow through of commitments. One reason is that participants shift focus upon return to work when faced with competing priorities. Another reason is simply that good intentions and commitments fade from memory. This is sometimes referred to as the problem of "New Year's Resolutions."

Currently, there is no easy way to stimulate people to take follow up actions on projects or goals after a course or learning event. One solution is to have people motivate themselves to take action. Suggestions include having participants use their calendar, day timer, planner or PDA (Personal Digital Assistants) to prompt a user into taking actions. This solution does not work because people either do not take the time to set up reminders or do not act on the reminders that have set for themselves. Further, individual reminders that are not published and do not require accountability are quickly overlooked as the demands of the day take priority.

A second failed strategy to spur individuals to act is to have participants write themselves a letter or post card at the end of a course. Although the card is mailed to them weeks or months later, it is usually ineffective because participants find that one prompt is not enough to stimulate action.

Another solution is to create a "buddy" system in which participants monitor each other's implementation of ideas or techniques learned in a course. However, due to lack of time, most post course or post meeting "buddy sessions" do not take place.

Another problem faced after a training program is that there is no way to take advantage of what other participants are continuing to learn. The collected wisdom and experience of the group simply evaporates. A solution to this problem could include scheduling additional faceto-face meetings to update progress, to discover barriers, and to provide opportunities to share learning. However, the globalization of business compounds the problem because participants are dispersed all over the world. The time commitment and financial cost of getting people back together often prevents additional meetings. Telephone conference calls can be used as an alternative to face-to-face meetings for individuals who are geographically separated. However, conference calls do not work well with a large number of participants and do not provide an easy way to document progress over time.

Another problem individuals face is that there is no easy way to reach a learning application expert who is knowledgeable in the subject matter and its application as it pertains to accomplishing a goal. Existing solutions include having a presenter give his or her address to each participant. By the time the participant needs to apply what he or she has learned in a course to accomplish a goal, specific information is often lost and the expert is unreachable.

Another problem is that course providers and companies do not know what knowledge or information individuals actually use or apply. One solution includes directly contacting a sampling of course participants to see what actions they had taken after their course. This process is time consuming and expensive, and it does not generate a full picture unless the entire group is reached.

Course providers and companies also face the problem of not knowing how to improve courses based on what does and does not get applied. Course leaders can have participants fill -2- out evaluations at the end of a session (known as smile sheets in the industry), which ask questions about content and delivery. However, these instant evaluations fail to uncover important information such as what each participant did with what he or she learned, and how the course can be improved so that what future participants learn will be easier, faster, and more powerful to apply.

Following through on actions after a meeting poses some of the same problems as does follow through for courses. One problem is that individuals make commitments to take actions at meetings that usually are not recorded in a way that fully captures all of the important details.

This means that individuals do not have a public record to guide individual action or a scorecard to assess future progress. When individuals do not record their own goals, it becomes time consuming and expensive and delays organizational progress. It also creates a disconnect between what the group thinks the individual has signed up to accomplish and what the individual recollects he or she has actually committed to do. In part, this is because no public record exists in the individual's own words.

Another problem is that of communication within a group. Self-initiative, followed by a series of sequential communication steps, is required for a member to check on interrelated actions of other group members. When an individual uses a personal day timer to keep track of progress, that person's progress is not available to others in the group. This is particularly true when the group is geographically scattered after a meeting.

Another problem in following up on goals and tracking progress is that it is difficult to make early and better mid-course corrections because of the delay in finding out what progress is being made. Current methods do not allow a leader to know a program's progress status until a group is re-convened or until a progress report is assembled. Progress reports, however, often rely on bits and pieces of information gleaned from other means.

Another problem is that what is learned at meetings and lessons from post meeting actions are not captured in a way that can be reviewed by members. This means that the next time similar post meeting results are required, best practices cannot be brought forward and problems cannot be avoided. Currently, the only way to capture such learning is to reconvene the group and hold a "post mortem." This method can be ineffective in part because beyond the expense and loss of valuable time, individuals may consciously or unconsciously rewrite the history of their follow through experience.

In considering the performance management systems of most companies, a common process is for individuals to sit down with their managers and agree upon goals for the coming year. In some systems these goals are written down and copies are distributed to the individual, manager, and human resources department. These written goals are then promptly filed away.

Rarely are they looked at again until the end of the year.

One problem with this system is that by the time the goals are reviewed at year-end, they are often obsolete. The business or organization most often has changed direction more than once since the goals were established. The manager and individual must judge performance on goals that are no longer relevant. One solution is to design performance management systems with quarterly or semi-annual update sessions between the manger and individual. Such systems are, however, rarely implemented.

Another problem with existing performance management systems is that an individual's manager may change during the year. A December performance evaluation may not be held with the same manager that the employee had at the beginning of the year. For example, an individual may put in extra effort to complete a critical goal in the first quarter of the year. If he or she changes managers or moves to a new assignment in June, their accomplishment is lost if a contemporaneous record is not kept. Few individuals record their achievements, and even fewer submit their contributions for their manager's comments or confirmation on a scheduled basis.

Another problem with existing performance management systems is that administrators and leaders have no way of judging across an organization the quality of the goals individuals are working towards and the quality of the actions that individuals are taking to meet those goals. One current method is to spot check goals, which is a time consuming process. There is no way to cross check a goal's quality or progress between different organizations within the same company. For this reason, leaders have to make decisions based on historical numbers rather than being able to spot trends earlier by viewing actions in progress. It is therefore difficult to predict future success.

Collectively, companies spend billions of dollars each year on developing their managers and their people. Often, individuals are given feedback through informal development discussions with their manger or through formal feedback sessions. The formal sessions may provide 360-degree feedback from instruments that help an individual identify their strengths and weaknesses. In other cases, individuals go to specialized "assessment centers" where they are given specific tests to determine strengths and weaknesses. The goal of these developmental assessments is for the individual to take action to improve their weaknesses or to better use their strengths.

One problem with such development efforts is that there is no easy and effective method to hold people accountable for actually improving themselves. Some companies hire "executive coaches" to check in with people on a periodic basis, for example, to document progress once a month and to make suggestions for future action. However, this personalized option is often so expensive that it is only made available to the highest paid individuals in a company. Some companies accomplish this process by telephone using one-on- one coaches.

Such one-on-one follow up is too costly and time consuming to be used for all but a few people.

Another problem faced by companies trying to improve efficiency is the inability to collect an entire company's or organization's developmental experiences to create a library of best practices which can be made available to its employees.

Several methods exist for motivating participants in a course or program to act in a consistent way over time. One method includes providing participants withjoumals. However, a problem arises in that participants find the process hard to remember and boring.

Furthermore, journals hamper flexibility in that it becomes difficult to change the questions the user responds to as his or her experience changes.

Other approaches that have been tried include telephone follow up or having an individual come to meetings on a regularly scheduled basis. However, such one-on-one meetings or gatherings of groups are labor intensive in getting people to follow through and be accountable.

Companies and organizations send millions of people to conferences each year.

Individuals attend many more on their own. One purpose of going to a conference is to learn new ideas that can be applied to one's work or life. During a conference, participants will often take notes or create a "to do" list to act upon when they return to home or work. Some companies or organizations will send people as a team so that members of the team will have each other to lean on as a way to gain critical mass for implementation. Despite seeking and finding good knowledge, taking good notes, and even being part of a team, ideas gained at a conference are often not acted upon. Further, conference attendees often come from difference geographic locations. This makes continued collaborative learning difficult. The best notes taken at a conference will not help with post conference collaborative learning because participants will not be aware of their fellow attendees subsequent learning through action. A further problem is that companies and organizations have no way of monitoring how knowledge gained at a conference is implemented. Consequently, there is no way for 5 companies and organizations to gauge their return on investment in conferences.

What is needed is a way to prompt individuals or teams to implement the commitments to actions made while at a conference. Inputting conference commitments into a system that then prompts them to act greatly increases the chance that effective post conference actions will be taken. By having these goals and subsequent actions available in a system that can be seen by conference participants in different geographic locations, the learning and impact of the conference can be greatly extended. A company or organization can track what each individual actually implemented upon returning to home or work after a conference. This can help them judge the value of their investment of time and money.

BRIEF SUMMARY OF THE INVENTION

The present invention is directed to a system and method for improving follow through for goals, objectives and commitments made during meetings or training courses. In one embodiment, the invention is an automated online system which contacts and prompts a participant/user to follow through on goals, objectives and commitments by providing e-mail triggers and on-line access to a system for cataloging and tracking their goals, objectives and commitments. It also provides additional resources to help users attain their goals. The system prompts individuals to take action, to collect information on actions taken and to plan future actions. It compiles the information and makes it available to other members of a group. The compiled information can also be made available to those interested in monitoring individual and group follow through and progress.

The present invention is designed to help users accomplish their commitments by providing reminders on a prescheduled basis or upon request. The present invention is designed to help users remain focused on their commitments, track the progress of their actions, learn from their experiences, and plan for their future opportunities. It also helps groups of users learn from each other, and provides ways to make individual and group progress visible.

The invention also provides other tools and customized information to make it easy to move quickly from commitment to action to valuable results. The invention provides quick, easy follow through to goals, objectives, and commitments made during training courses, leadership development and executive education programs, feedback sessions, meetings and conferences.

In one embodiment, a user is provided with a personalized site that comes to the user on a prescheduled basis. The site enables the user to input goals, actions taken, lessons learned, and opportunities. These are stored for easy retrieval and for sharing with other users. This sharing of information speeds leaming among the members of the user group. User inputs are analyzed in a way that makes public the collective efforts of individual users.

The present invention provides an automated, structured way to stimulate actions and encourage people to reflect on those actions. It also provides a way to collect and analyze who is doing what, and by when. It can identify individuals who need special attention, and provide benefits to an entire organization or company which learn from the information stored in the system.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description of preferred embodiments of the invention, will be better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings embodiments which are presently preferred. It should be understood, however, that the invention is not limited to the precise arrangements and instrumentality shown. In the drawings:

Fig. I is a block diagram showing the four system levels of one preferred embodiment of the present invention; Fig. 2 is a block diagram showing the data structure for the system levels of the preferred embodiment of Fig. 1; Figs. 3 -10 are block diagrams illustrating relationships between system tables in accordance with a preferred embodiment of the present invention; Fig. I I is a high level hardware architecture block diagram of a preferred embodiment of the present invention; Figs. 12-36 are sample input and display screens for use with a preferred embodiment of the present invention; and Figs. 37-43 are process flow diagrams for a preferred embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention is described in the context of a system and method for improving follow through for goals, objectives or commitments by proactively prompting users to act and by providing on-line access to the system which catalogs and tracks the goals, objectives and commitments. The system also provides additional resources to help users attain their goals.

In one embodiment, the invention is a computer-base4 method and system for auto prompting individuals to apply what they have learned during courses or to take actions on commitments made during meetings. Users are proactively prompted to act, document their progress and identify best opportunities for future actions. These prompts preferably come to users on a prescheduled systematic basis over a period of time. Additional context sensitive information in the form of questions, prompts or links to relevant data can be preloaded or scheduled, as the context of users' prompts or answers change. User inputs are displayed individually and collectively to provide a personal historical record of progress and so that learning can take place among users even if they are geographically separated. The system can automatically and flexibly categorize text-based data. User inputs can be parsed and displayed and/or automatically forwarded to a specified manager, coach, or mentor or other user. An auto-reporting system is preferably included to provide context-based assessments of text based and graphical numerical data.

In one preferred embodiment, the invention is designed to provide at least three functions: administrative set up functionality, user functionality, and report generator functionality. The administrative functionality includes the set up of users and/or administrators at four di.fferent levels.

At the system level, the system can be set up for any number of system level administrators who are granted entrance into the system with a unique user name and pass code.

Set up begins by creating administrator profiles at the administrative level, each having a unique user ID and pass code. An administrative level administrator has the ability to set up lower levels including companies, groups and users in the system. Each administrator has control over all levels created beneath it, within the tree structure of the system. Therefore, the administrative level also makes it possible to customize the system to a particular company.

At the company level, an administrative level administrator can set up companies under their administration, each company being associated with the administrative level administrator.

The administrative level administrator can also set up one or more company level administrators.

At the group level, a company level administrator can set up one or more groups and group level administrators. Each group is associated with at least one company. A group level administrator has the ability to turn on or off features of the system including goal categories and dimensions, question attributes which allow for the sharing of answers, common files and contact of users via system generated e-mails.

At the user level, one or more users can be set up by a group level administrator.

Preferably, this includes setting specific trigger dates (the dates that users will be sent user goal prompts including a request for a response) for each user and the questions that each user will be asked during each user goal prompt.

A dynamic table structure is preferably used to allow the custornization of the system to meet the needs of a wide variety of groups. This customization makes it possible to pre-load an individual user's goals to a customized "Tips of the Day" database that can be context sensitive to the time that a particular user goal prompt is triggered.

In an exemplary embodiment of a system incorporating the method of the present invention, a user receives an e-mail prompt to go to their personalized "Follow Through Web site." After completing a login procedure that creates a user ID and password, the user enters their personal site and is greeted by name. A customized prompt including a "Tip of the Day" provides information to speed the implementation of the user's particular application. The "Tip of the Day" can direct users to "Shared Folders" where additional context sensitive information is located. The group level administrator can upload information in "Shared Folders" so that it appears at the most opportune time during a series of goal triggers. For example, additional material on how to set goals can appear early in a series of goal triggers so that a user receives instruction on how to get off to the best start. In a post meeting scenario, the information in the "Shared Folders" can be common documents generated by the participants at a meeting.

If user goals have not been preloaded, the user is preferably able to input his or her goals. The user then identifies the actions they have taken, the actions they intend to take for each goal, and answers to one or more independent question(s). Preferably, a "Private" Option can be set to allow a user to limit other user's access to their responses. The user also preferably has the option to check on the shared answers of other members of the group. Answers are preferably parsed by goal categories so that a user can see one or more relevant responses of other users.

The system can also be designed to allow a user to see pre-sorted goals by accessing data stored in a "Goal Dimension" database. For example, a user could be permitted to see the progress and prospects of other users in their group. A dynamic table structure is preferably used to provide flexibility in making the selection of goal dimensions and to allow custornizable system output.

On subsequent goal trigger dates, the user preferably receives an autoprompted e-mail that includes log on instructions, their previous user goals, and updated input from their previous goal trigger. The user then logs on to their personal site and completes the questions that their group administrator has loaded in the program. User prompts may also be delivered by telephone and using voice recognition to translate voice input to text input.

The system makes it possible for progress to be monitored and for other users to see the steps that individual users take over time. Users can also receive parsed information that makes it easier to interpret actions that have been taken and lessons that have been learned. Based on a users access status, a user can see inputs at the group, company, or administrative level.

The system can be designed to generate group level reports which can be accessed by the whole group, the group's administrator, or a higher level administrator. Reports can also become prescheduled auto-reports that are sent to designated administrators, leaders, or users.

The system preferably has the ability to add encryption in the transmission of data to and from the user. It also has the ability to encrypt the data that is stored on the server(s).

The system can also include a natural language recognition program to process text based data. The natural language program allows users and administrators to conduct natural language word searches of the system.

The invention preferably incorporates a computer connected to an electronic network such as the Internet or to an Intranet. Inputs and outputs can be received and transmitted using other means such as the telephone (both wireless and wired), in which the input would be translated through a voice recognition program into text-based data. Text based data in the system can be translated into voice reports. PDA's (Personal Digital Assistants), both wired and wireless, or a similar devices may be used to allow for the goal triggers to reach users at any time anywhere in the world.

Fig. 1 is a block diagram of one embodiment of the system of the present invention having four system levels. The top level of Fig. 1 is an administrative level containing an administrative table 612, followed by a company level containing a companies table 614, the groups level containing a groups table 616 and a user level containing a user table 618. The system was designed so that one administrative level can support as many companies as desired. Each company can perform its own administration in the creation and management of groups and users from any place in the world that has an Internet or similar electronic network connection.

Fig. 2 is a diagram showing a data structure for the system of Figure 1. The structure of the system enables the system to create as many administrators as desired (i.e., administrator A 1, A2,... An) by creating administrator profiles or records in the administrative table 612. Similarly, as many companies, groups, and users may be created by creating company, group or user profiles/records, respectively. In an alternate embodiment, the system can provide a recursive algorithm that allows for the creation of as many administrators, companies, groups or users as desired through a single level table. This permits users to enter the system at any level and create goals linked to other users' goals located at any level within the system.

Fig. 3 is a block diagram illustrating the relationships between the group table 616 and other tables of the system. A trigger dates table 664 may be set up by a group administrator for each group. A group can, for example, be set up to be automatically prompted every Friday for three weeks and then every other Friday for the next eight weeks by creating an appropriate record in the trigger dates table 664.

The system is designed to be able to include one or more questions with user prompts. The questions can be context sensitive based on a user's prior responses (i.e., if a user indicates that he or she is behind schedule on a goal, questions may include "What are the main obstacles you have encountered in attaining your goal?" or 'Yould you like assistance from an expert or manager?"). A monthly calendar can also be displayed to allow a user (or group administrator) to select a goal trigger date. A trigger date question match table 666 canbe used to specify which question(s) from a question table 642 will be asked on which goal trigger date.

The system is preferably designed to allow an administrator to designate what 3 0 question(s) are linked with which goal trigger dates. The question table 642 can contain a variable list of questions, which allows a group administrator to ask any number of different questions. Forexample, an administrator may routinely ask "What actions have you taken?" and "What actions will you take?" With specific goal triggers, the administrator can ask a unique question for that goal trigger such as, "What is slowing your progress?" Questions contained in questions table 642 can have multiple question attributes, contained in a question attributes table 644, associated to the question. An attribute can include whether the users response will remain private or whether it will be public so that other users in a group will be able to see the user's response. The question attributes may also be linked to one or more attribute categories. These attribute categories are stored in an attribute categories table 646. For example, if users in a group attend a management development course, categories for this course could be communication, delegation, or team building. As will be described below with reference to Fig. 4 and Fig. 5, by attaching the question attribute and categories to a specific question in the Questions table 642, answers to the question can be categorized (e.g., by communication, delegation, or team building). The system can then display user answers by category. This promotes learning among users by allowing users to quickly find useful information input by other members of a group.

Each group preferably has its own goal categories available for all users in the group. A goal category preferably operates as a data tag to allow searching of data input by users. For example, categories for a course on management development might include communication, delegation, and team building. The group administrator can input the specific goal categories that users will use to categorize the goals they input into the system. This makes it easy for other users and group administrators to see what kind of goals members of a particular group are working on. Goal categories are preferably dynamic (i.e. the group administrator can choose as many categories as desired and give each category any name desired).

Each group preferably has its own goal dimensions stored in goal dimensions table 624. The goal dimensions are preferably dynamic and can be selected by the group level administrator. There may be an unlimited number of dimensions created. For example, an administrator can choose goal dimensions that relate to progress a user has made or to the future prospects for goal accomplishment. Goal dimension values, stored in a goal dimensions values table 626, are the metrics or values assigned to each goal dimension. For example, the Goal dimension values relating to progress could include that the user is ahead of time, on time or behind time in accomplishing a user goal. The value or metrics for future prospects can include indicating whether the user "will accomplish, " "may accomplish" or "won't accomplisW' their goal. In this way, users have a common and simple way to indicate their current progress and future prospects. By combining the goal value inputs of multiple users of a group, a representation of group progress can be shown. In a preferred embodiment, a matrix can be used to list each value and the number of user goals indicated as having each value. For example, a matrix could have progress (ahead of time, on time, and behind time) on one axis and prospects (will, may, won't accomplish the goal) on the other. If twenty users are included in a group, each with two goals, each goal trigger will fall within one of the nine cells of the matrix (e.g. will accomplish the goal, ahead of time). This allows users to see the progress and prospects of the group.

When a common group goal is created and stored in a common group goals table 632, a replication of the common group goal is created for each user in that group and linked to the group's common group goal table 632. This link permits any change made to a common group goal to be reflected to all applicable users. An example of a common group goal in the context of a sales meeting is a goal to achieve a certain percentage sales increase. This increase can become a common goal for each user. If, for example, there were members of both a sales and a manufacturing organization in a meeting, the system, through common group goals, makes it possible for sales users to be given their common sales goal and the manufacturing users to be given a common quality goal even though the sales and manufacturing users are part of the same group.

Fig. 4 is a diagram showing how the goals and answers of a user are linked to specific goal trigger dates stored in a goal trigger dates table 664, and are tagged with specific goal categories and goal dimensions. Users preferably have one or more user goals which they can input, edit, modify, or archive. When the user logs into the system and inputs or edits their goals, a weeks table 634 is created to assign which goal trigger date the goal has been edited for. Goal dimensions answers stored in a goal dimensions answers table 694 specify the goal dimension value of a goal dimension a user has selected on a specific week that matches the usr goal with the user goal trigger date. For example, a group administrator may choose on time, behind time and ahead of time as goal dimensions. At one point, a user might indicate their goal dimension as being on time. At the next user goal trigger, the user might indicate that their goal progress is now behind time. An answers table 692 stores the answer to a question for a given goal trigger. If the question has a question attribute attached, then an attribute answers table 693 is used to store the answer provided to the question attribute for that given answer.

Fig. 5 is a diagram showing the use of the questions table 642 for storing questions which are independent of user goals. The questions table 642 created for a group preferably contains questions in two distinct forms: Dependent and Independent. Dependent questions have the ability to be answered by the user for specific user goals on each goal trigger date.

Independent questions are not linked to specific goals and are answered by the user on each goal trigger date. For example, the user may have three goals they are working on, but the group administrator may want to know what the barriers are to implementation that users in the group are experiencing in general and irrespective to any specific goal. If the independent question in question table 642 has a question attribute attached, the attribute answers table 693 is used to store the answer provided to the question attribute for that given answer.

Fig. 6 is a diagram of some of the collaborative communication tools which may be made available for users. Users can provide feedback (stored in a feedback table 697) to other users for any goal, common group goal, answer, or feedback, which exists in the system. The system preferably allows a user to give feedback on feedback (illustrated in Fig. 6 as a recursive loop). This collaborative communication tool is important because people are often spread out geographically after a course, meeting, or conference. Using this tool, a user can easily give feedback to another user by, for example, displaying the user inputs to other users with an email link to that user. This allows user A to communicate with user B using a comment or a question transmitted to user B via e-mail. The ability to send real-time audio/video/text communication between users fosters collaboration within the system.

A manager reports table 698, stores the evaluation(s) given by a manager/user for inputs a user has submitted into the system. For example, in a user's set up, the name and e-mail address of the user's manager, mentor, or coach may be included. When the user completes the answers, the system sends the designated person an e-mail with a URL link to the users input.

The manager, mentor, or coach can then see the user's input and give the user feedback. The manager's feedback is then stored in the manager reports table 698, and the user is alerted to the fact that the manger has responded. The manager reports table 698 preferably includes a unique report ID for each report sent by the users, a symbolic ID which generates a unique and secure URL for the outside party to enter the system, review the work and offer feedback, a user ID, a trigger date ID, the actual text of the report, and an indication of whether the report and feedback had been viewed by both parties.

Fig. 7 is a diagram showing some of the system resources which may be included in the system to provide tools and information to help users to better follow through on their goal commitments. Weekly tips, stored in a weekly tips table 678, can be created and edited at the administrative, company, or group levels and displayed to the users.

Uploaded documents stored in an upload documents table 676, are documents that can be uploaded into the system at the admin, company, or group levels and transmitted as context sensitive information linked to the goal triggers and displayed to the users. Uploaded documents may include digital documents, graphs, pictures, charts, audio and video files. The upload documents table 676 preferably includes an ID for each document, an ID for the Owner who uploaded it (designating the level within the system that it should appear), the type of document it is, whether it is classified with a category, title and description, the time the record was made, and an indication of whether it has been set as inactive.

The related links table 674 can be used to store related links to other site and sources which can be posted at the administrative, company, or group levels and displayed to the users, A link can be used to direct users to areas of interest on the Internet and can be organized into helpful categories. The related links table 674 preferably includes a unique ID for each link within the system, an owner ID and owner type that identifieswhere the link was added within the system, a link category, a URL for each link, whether the link had been set inactive, and the time that the link had been added.

The contact/expert table 672 can be used to store contact/expert names and e-mail addresses that can be inserted at the administrative, company, or group levels and displayed to the users.

The e-mail types table 652, shown in Fig 8, contains templates of e-mails created at the administrative, company, and group levels. The user filters table 656 contains information which describes the criteria that the users must meet in order to receive e-mail as defined in the e-mail types table 652.

The token library table 669 stores symbols, definitions and values for system tokens.

The tokens can be used by an administrator or user as shortcuts for entering user input. For example, tokens can be used in e-mails for replacing a defined symbol with the appropriate text, thereby allowing the system to appear to be sending unique e-mails to each user when it is automatically sending a list of users the same e-mail and customizing it specifically to each user. The token library table 669 preferably includes an ID which uniquely identifies each token, a definition which describes what text will replaces the symbol for each token, the actual token symbol, the token SQL (data base query that the e-mail generator runs to get a corresponding value from the user's profile), a sample of the text replaced into the token, an entry time, and an indication of whether it has been set as inactive.

The e-mails sent table 658 can be used to store e-mail sent by an administrator and to record which type of e-mail a user received.

The message board table 675 of Fig. 9, can be used to store the messages that are posted at the administrative, company, group, or user levels. Each message is preferably available for viewing by users. The message board table 675 preferably includes an ID for each message, an ID for the Owner which inputted it (designating which level within the system it should appear), whether a message is classified with a post-by date, a priority of posting determined by date, an entry time, and an indication of whether it has been set as inactive.

The problems reported table 684 of Fig. 10 can be used to store each problem a user reports related to difficulties experienced with the system. The activity log graph table 688 contains information which specifies when each user logs in and out of the system. The buttons clicked table 682 contains information which specifies which button on which page users clicked during their session activity.

Referring again to Figures 1-10, the following is a description of a table and database structure which can be used with the embodiments described above.

The admin table 612 stores one or more administrator profiles. A system designer creates an administrator profile for each administrator in the system. Each administrator profile contains a unique user name and pass code which permits an administrator to enter the system at the admin level and create, view and edit tables and records associated with that administrator. The admin table 612 preferably includes an administrator id for each administrator, the administrator's first name, last name, phone number, user name and password associated with the administrator, the title of the administrator, and the number of failed logins permitted for that administrator within a minute (for security purposes).

The companies table 614 stores one or more company profiles created by an administrator or system designer. Preferably each company profile is associated with at least one administrator and contains a company name and pass code which permit users to enter tile system at the company level and create, view and edit tables and records associated with that company. The company table 614 preferably includes a company ID, which is tied to each group ID (discussed below), the company name, leader name, phone and fax number, leader e mail address, company URL, maximum number of users the company is permitted to have within the system, a company logo which can be uploaded and displayed, if the company has been made inactive from the system, and a creation time for the company.

The groups table 616 stores one or more group profile(s). Each group profile is associated with one or more companies and contains a group name and pass code which permit users to enter the system at the group level and create, view and edit tables and records associated with that group. The group table 616 preferably includes a group ID which is associated with each company ID, the group name, leader name, phone and fax number, leader e-mail address, whether the user's rights (login ability) have been suspended from the system, whether the group has the privilege to share information (inputs) between users, if the group can receive multipart (HTML... smart) e-mails, whether the group has deadlines for its goals, which version of the user interface is made available (e.g. input all on one page or on separate pages), whether the group has the ability to involve each user's manager in the process by automatically sending e-mail reports, if the group has the ability to have a workspace function where all users can see one another's inputs and provide real-time feedback, a usemarne and password (which is associated with each group), if the group has been made inactive from the system, and the creation time for the group.

The users table 618 stores one or more user profiles. Each user profile is associated 2 0 with one or more groups and contains a user name and pass code which permit users to enter the system at the user level where they can enter their own personalized web site. Once in the site, a user can enter goals, share learning experiences, access content and collaborate with other group members. The users table 618 preferably includes user information such as a unique user ID (which is attached to their Group ID), whether their system privileges have been blocked, their manager's name and e-mail address, and a series of profile information, such as name, e-mail, phone number, address, and the like.

A system user name and pass code table (not shown) preferably stores system designer name and pass code information for entrance into the system level, where administrators are created within this highest point in the system. The system user name and pass code table contains security features which track the number of failed logon attempts into the system so that the gateway is closed upon a predetermined number of failed logons. It preferably includes a user name, a pass code, number of failed logons within the last minute, the time of each failed logon attempt, a locking mechanism that can only be reset at the hardware level, whether the pass code has been deleted from the system and the time that the record was created.

The goals table 622 stores the goals that an individual user inputs into the system. Each goal that is entered into the system is stamped with a unique ID, the goal ID, a common ID (specifying if the goal is a replication of a common group goal), a unique user ID that identifies each user to their specific goal, the actual text of each goal, the category associated with each goal, whether the goal has been set inactive and the time the category was created.

The goal dimensions table 624 preferably contains dimensions which can be applied to a group's goals within the system. The number of dimensions created for each group and the number of metrics or values per dimension are preferably dynamic. The goal dimensions table 624 contains the unique dimension ID, the group ID, the order number, the dimension name, the description, whether the dimension has been deleted from plain view of the user, and the time the dimension was created.

The goal dimensions values table 626 can be used to store goal dimension information, value information and values entered by users (i.e. measurements of user progress on goals).

The goal dimensions values table 626 preferably includes a unique goal dimension value ID, the dimension ID, the order number that the dimension should appear when presented to the user, the dimension value for each dimension, whether the dimension has been set as inactive, and the time the dimension was created.

The goal categories table 628 can be used to store information for categories which can be designated for each group within the system. The goal categories table 628 preferably includes the goal category ID, the group ID, the category, the listing order in which the categories are to be displayed, the time the record was made and whether it has been set inactive.

The common group goals table 632 contains information regarding the linkage of an individual goal to a common goal at the group level which is available to all users or just a subset of users from a particular group. The common group goals table 632 preferably includes the common ID unique identifier, the group ID, the goal, the category, whether it has been archived or deleted, and the time of the last update.

The weeks table 634 can be used to store information on goals that users have edited on particular goal trigger dates. The weeks table 634 preferably includes a week ID which uniquely identifies each week as defined within a group, a goal ID which catalogs responses to each goal, a trigger date ID which uniquely identifies each of the triggers created for a date assigned to each of the triggers, the time the record was made, and an indication of whether a record has been set as inactive.

The questions table 642 can be used to store questions created by a group leader, which can be transmitted to the users along with user goals, or which can be asked independent of the goals. The questions table 642 preferably includes the question ID which uniquely identifies each question in the system, group ID defining which group the question belongs to, the text of the question, the listing order of the question for the user interface, a flag specifying if the question is dependant or independent, a field specifying if the question will be asked at the beginning or end of the session, if the question ID is independent, a field stating whether the question has been made inactive, and the creation time of the question.

The question attributes table 644 can be used to store information on question attributes and how the attributes are associated with each question within the system. Examples of question attributes include categories describing each question, an indication of whether a question should be private or public from your group, or an attribute with a yes/no option. The question attributes table 644 preferably includes an ID for each attribute which links it to the Question ID, whether or not an answer to this attribute is required by the user, the lead text for each attribute (e.g. Categories, Private), the type of attribute (e.g. Radio buttons, categories, text input, colors, default checked text box and default unchecked text box), whether the attribute has been set as inactive, and the time that the attribute was created.

The attribute categories table 646 can be used to store information regarding categories to be defined for each question, which is a subset of the question attribute table 644. The attribute categories table 646 preferably includes a category ID, attribute ID from the question attribute table 644, the actual text of each category, whether the category has been deleted from plain view of the user, and the time the category was created.

The e-mail types table 652 can be used to store data that controls all of the e-mail created through the system's e-mail generator. E-mail can preferably be created at any level within the system and can be sent to all system levels at and below the point of creation. The email types table 652 preferably contains an e-mail type ID which uniquely tags each e-mail created within the system, a filter ID, a title for each e-mail, a subject, from name, from address, the body of the e-mail, the owner type (where it was created within the system), an owner ID, the time the record was created, and an indication of whether it has been made inactive.

The when to run table 654 preferably contains information defining set intervals where a server batch application matches the current system time against a predetermined time interval.

Upon the match in time, a corresponding file would be called to executes a procedure. The when to run table preferably containsan ID which is associated with each interval, beginning time and ending time for each interval, a file name of a program which runs when its corresponding interval is met, a status that documents whether or not the process was successful, and a log of the start and end time for each process.

The users filters table 656 preferably contains filters for sending email. For example, e-mail can be sent to people who have not logged into the system. The users filters table 656 preferably includes an ID for each filter, a filter title, a filter SQL (the database query that the e mail generator is going to use to filter the recipients of the e-mail), the time the record was made, and an indication of whether it has been set as inactive.

The e-mails sent table 658 preferably catalogs e-mail sent within the system. By keeping track of each e-mail generated and cross-referencing against the e-mail sent table 658, the system is able to avoid sending duplicate e-mails. The table can store information relating to each e-mail including recipient address, subject, body, from name and from address, when the e-mail was sent, which user sent the e-mail, and to which user the e- mail was sent.

The today and yesterday e-mails table 660 is used for the creation of email templates, which are automatically sent by the system. The e-mail within this table is automatically sent based on the predefined trigger dates set in the system. The today and yesterday e-mails table 660 preferably includes information including unique e-mail IDs, date and time sent, user ID, type of e-mail (HTML based or plain text), subject, from name, from address, e-mail body, whether it had been successfully sent, time the record was made, and an indication of whether it has been set as inactive.

The trigger dates table 664 can be used to store date information related to user goal triggers. The trigger dates table 664 preferably includes the unique trigger date ID which is tied to the specific group ID, the actual date for the trigger, the time the record was made, and an indication of whether it has been set as inactive.

The trigger date question match table 666 can be used to store information for matching the appropriate questions to goal trigger dates. The system preferably allows a group administrator to assign trigger dates to a group and then attach questions which will be asked for each specific trigger date. The trigger date question match table 666 preferably includes a match ID, which is the unique identifier linking a question to the specific trigger date, a trigger date ID from the trigger date table 664, the question ID from the questions table 642, the time the record was made, and an indication of whether a record has been set as inactive.

The contacts/expert table 672 can be used to store information regarding experts within the system. Experts can be added at all levels within the system and are preferably available to all levels below the creation point within the system. A user can access each expert created within their tree structure allowing them to compose a message to be sent directly from their system to the applicable expert. The contacts/expert table 672 preferably includes a unique ID for each expert within the system, an owner ID and owner type that identifies where the expert was added within the system, an expert title, expert e-mail address, whether the expert had been set inactive, and the time that the expert had been added.

The weekly tips table 678 contains tips or other forms of content, which can be loaded into the system from various administrative levels for users to view. The weekly tips table 678 preferably includes an ID for each tip, an ID for the user who inputted the tip (designating which level within the system it should appear), a post-by date for classification, a priority of posting determined by date, an entry time, and an indication of whether it has been set as inactive.

The buttons clicked table 682 can be used to store data tracking the buttons the user has "clicked" while completing their session within the system (i.e., a click trail). This information can be displayed within the activity log graph 688. The buttons clicked table 682 preferably includes a buttons clicked ID which places a unique ID on each button in the system, a log ID for each user's session in the system, and a goal ID which captures the text of the goal being edited for display through the activity log graph 688.

The problems reported table 684 can be used to store information documenting any technical difficulties experienced by users within the system. The problems reported table 684 preferably includes a problem ID for each occurrence, a time the form was sent, a user ID, computer type, the type of operating system the user was using, browser type and browser version (both automatically detected), type of internet connection, the page where the error occurred, problem description, additional comments, error page detected, an indication of whether the record had been deleted from plain view from the system, and the time that the record was created.

The activity log graph table 688 can be used to store a detailed record of user activity at each level within the system. The activity log graph table 688 preferably includes an ID for each login, a user type, an ID for each user which has logged into the system, the reason for exiting the system (e.g. logged out, timed out), an IP address for each user, the time the user logged in, the time the user logged out, the type of browser, and the date the user was in the system.

The answers table 692 can be used to store user input for questionsassociated with a goal trigger. The answers table 692 preferably includes an answer ID which uniquely identifies each answer to a question, a week ID that associates for which goal the question has been answered and on which goal trigger date the question was asked, the question ID tying the response to the appropriate question, the actual text of the response, the trigger date for independent questions, the time the record was made and an indication of whether it has been set as inactive.

The attribute answers table 693 can be used to store user input for attributes assigned to the questions within the system. The attribute answers table 693 preferably includes a unique ID for each answer for a given attribute, the attribute ID, the answer ID (to which the attribute answer was attached), the time the record was made, and an indication of whether it has been set as inactive.

The goal dimension answers table 694 can be used to store user input for the dimensions for each goal within the system. The goal dimension answers table 694 preferably includes a dimension answer ID which uniquely identifies each answer satisfied for a particular dimension, a week ID that associates the goal, the dimension and the goal trigger date, the dimension ID tying the response to the appropriate dimension, the time the record was made, and an indication of whether it has been set as inactive.

The feedback table 697 can be used to store user feedback information. Users preferably have the ability to offer feedback to other group members through the shared/collaborative features within the system. After viewing another user's goal or input through shared answers, the matrix workspace, etc., the user can offer feedback to another user within their group. This feedback is preferably e-mailed directly to the intended user and is stored in the system for individual and group review. The feedback table 697 preferably includes a unique feedback ID for each feedback generated by the system, a parent ID which designates who is the owner of the feedback, a goal ID so the feedback can be correctly attached to each goal, a common goal ID, an independent question ID so feedback can be attached to independent questions, a title, the text for the feedback, the ID of the post of the feedback, time the feedback was made, and an indication of whether it has been set as inactive.

The following is a description of a representative example of a system incorporating features of the present invention.

As shown in Fig. 11, the system is composed of three main components; a web server 200, 200, an e-mail server 270, and a database server 250. The web server 200 is in the center of the operations and manages the data inflow and outflow. The web server 200 accesses the database 250 for read/write/modify and delete privileges. The web server 200 also processes and sends system-generated e-mails by sending e-mail queues to the e-mail server 270. Basic components of the web server 200 include the memory, hard drive, CPU and the system clock.

The operation of the system clock is important for the success of the system since the e-mail sending part of the system is invoked through the web server 200, which, in turn, relies on the system clock for accurate and timely executions.

Web pages are preferably stored in the hard drive of the web server 200 and compiled and sent to the clients upon request.

A primary step in system operation is the creation of system levels including administrators, companies, groups and users. These system levels make up the backbone of the system. The system levels can be set up by a system designer through administrative interface 300 and modem or LAN 150. After the backbone of the system is created, the users of the system receive e-mail on goal trigger-dates which are sent through the e- mail server 270 with the request of the web server 200.

215 Users who have received e-mails can go into the system via a user interface 400 and web server 200 and access their data on the database server 250. User inputs are delivered to the server through a modem or LAN 120 and any output to the user interface is pulled from the database to be presented to the user.

After the users have provided input, which is now saved in the database 250, the administrators can go in and view the data entered by the users via the administrator interface 300. The requests of administrators are compiled at the web server 200 and the results are printed back to the administrator interface 300 after all of the data requested is pulled from the database 250.

At the point where a user or administrator enters the system (administrative level, company level, group level and user level), rights are granted to view, modify and delete functions at the level of entrance and any level below it. A system administrator can notify and assign leaders to these sublevels and permit them to log into the system and accomplish their tasks within their territories. Preferably, functions conducted at a level are effective at that level and all levels below it.

The system's highest level is the system level. An example of a system level input and display screen is shown in Fig. 12. A system designer preferably logs into the system level. If login fails, security is established to close the entrance when it receives a predetermined number of incorrect user names and/or pass codes within a given period of time. A system designer is capable of creating one or more administrators. The system designer and each administrator (administrative level, company level, and group level) has control over all levels created beneath him within the tree structure of the system. Administrative level administrators are also granted a unique name and pass code to enter the system at the administrative level. An example of an administrative level input and display screen is shown in Fig. 13.

Administrative level administrators are able to create companies, and for each company can determine certain privileges, such as the number of users available to each company and the pass codes which permit access into that company level. Company administrators can also be created by system administrators and are authorized to create groups associated with a company. Each group has a field named "Company ID", that labels which company a group belongs to. An example of a company level input and display screen is shown in Fig. 14.

A company administrator can assign rights to each group such as the type of e-mail the group can receive from the system (HTML, Plain Text, Multipart e-mail, etc). A company administrator can also create group administrators, make available features specific to a group, and assign contact information, a user name, and a pass code to a specific group. An example of a company administrator input and display screen for turning on and off system features is shown in Fig. 15.

A group administrator can create users within their group by manually creating user profiles individually or by uploading a local document which allows the upload and creation of an entire group of user profiles. An example of a group level input and display screen is shown in Fig. 16.

Goal triggers can be created by selecting the desired date in a calendar specific to each group. An example of an input and display screen for setting goal trigger dates is shown in Fig.

17. Each trigger date record preferably has a filed "GroupID" that specifies which group is the owner of this trigger date. Trigger dates can preferably only be created for the current date and for future dates.

Questions are then created for each of the trigger dates as previously assigned. An example of input and display screens for setting specific dependent and independent questions with custornizable question categories is shown in Fig. 18. To achieve matching trigger-dates with questions, the trigger date question match table 666, shown in Fig. 3, is used to store the matching information. Each question can have individual attributes assigned to it. The question attribute table 644 has a field named "question ID" that specifies which question an attribute was assigned to. Attributes can take the form of categories, text inputs, yes/no questions, and single check boxes. Questions can be defined to be associated with user goals or be created independently so that they are asked either before or after a user edits his or her goals. Each question preferably has a Boolean (True/False) field that specifies whether the question should be asked independent from the goals. Questions can be created so that the responses are made public or kept private within the shared communities made available to the users.

A group level administrator can also assign goal dimensions. An example of an input and display screen for creating custornizable goal dimensions is shown in Fig. 19. After dimensions are created, goal dimension values are assigned to each goal dimension. Goal dimensions are preferably attached to each user goal, and the user is expected to satisfy the goal status using these goal dimensions each week. The goal dimensions answers table 694. of Fig. 4, stores information regarding which goal dimension was answered on which week, which, in turn, determines which goal has been edited on which trigger date.

Next, the group level administrator assigns a list of categories that appears to each user as a list which the user can attach for each of their goals within the system. An example of an input and display screen for inputting goal categories is shown in Fig. 20. The group leader now has the ability to create goals which can be applied to one or more users selected from the group. The selected users are expected to satisfy these common group goals just as if they were created by each user. An example of an input and display screen for inputting text of common group goals is shown in Fig. 21.

Shared folders can be used by users/administrators to upload documents (e. g. tips, goal related documents and other context sensitive information) from a local machine onto the server hosting the system. The shared documents are available for viewing by users and can be downloaded by users. An example of input and display screens for shared folders is shown in Fig. 22. A user can access a shared document, which has been uploaded within the tree. structure which the user is a member. This tree may contain all of the groups, companies and administrators above the user.

The contact/expert table 672 is used by system level administrators to upload expert titles and e-mail addresses to the system. A user can compose a message and send it from their system to an appropriate contact/expert.

The related links table 674 is used by system level administrators to upload relevant links onto the system. A user can access links created within their tree structure, opening that link/page directly from the users system.

E-mail sent to users from an administrator is preferably sent through a template. An example of an input and display screen for sending customized e-mail is shown in Fig. 23. Templates can be created at any level within the system and can be accessed at or below any level where it was created. Templates can only be modified at the level it was created. A template is composed of basic fields for an e-mail, which include a from name, address, subject and body. The creator of the e-mail can also specify for which users the e-mail is sent and can use the system to automatically extract users based on predetermined filters. For achieving customization, the creator of the e-mail template can use "Tokens" which are predefined in the system, stored in the token library table 669 and available for administrators to use at each level within the system. When an e-mail is sent to a user, tokens are replaced by the corresponding data from the recipient's profile. For example, if the token was <FirstName>, then that token will be replaced by "Tom" when the e-mail is sent to Tom Sample and "Bill" when it is sent to Bill Example. After these fields within the template are satisfied, the e-mail is saved and then can be sent over and over. To send an e-mail to the users, an administrator can choose presaved templates. An example of an input and display screen for selecting from a library of stored e-mail is shown in Fig. 24.

E-mail reports can be generated to enable an administrator to view reports of all of the e-mails that were system generated or automatically triggered at their level and all levels below.

Administrators preferably have the right to select a record of which emails were sent on a particular date.

An activity log graph can be used to display a detailed record which tracks users' activity within the group, company, and administrative level. Preferably, the graph first displays by day the number of users who have logged in, when each user has logged in, the amount of time they were in the system, the IP address they were heralding from, what type of browser they were using, and their method for closing their session. The activity log can also include a detailed record of what buttons each user clicked while they were in the session, the amount of time between the buttons clicked, and what they have inputted while they were in the system. Each button can be labeled for recording purposes and a table can store each of the buttons clicked by the user during their visit to the site. An example of input and display screens for the activity log is shown in Fig. 25 The group administrator is also able to view a snap shot set of statistics for users within their group including the number of times users have responded to user goal prompts and the activity and inputs for each user for each of their desired trigger dates.

Users who receive goal prompts as e-mail in either plain text or html form are directed to a login screen for admittance into the system. The login page requires a user name and pass code to be inputted by the user and matched against these fields in the user table 618. If a match is found, the ID of the user is redirected to the system's home page. When the user clicks on the entrance button a check is made if the user has inputted goals into the system. Examples of a user goal prompt e-mail, a login screen, and a system home page are shown in Figs. 26-28, respectively.

If a user has not input goals into the system, the user is asked to input one or more goals. An example of an input and display screen for inputting user goals is shown in Fig. 29.

If a user has goals input into the system, the user is asked to satisfy the input requirements for that goal which can include one or more questions. An example of a goal input and display screen is shown in Fig. 30.

When the user completes inputting the necessary information and executes the save button, a week ID is created in the weeks table 634, specifying which goal has been edited on this trigger date. The week ID 634 is used to store goal dimension answers selected by the user.

The same week ID is used to save each answer to each question for the goal trigger date, as well as the answers satisfied for each question attribute. Upon satisfying a goal, the user is directed through this same process for remaining goals on the system.

The user can also be asked to respond to one or more questions which are independent of a specific user goal. An example of an input and display screen for answering independent questions is shown in Fig. 3 1.

After the independent questions and the goals have been edited by the user, the user is taken to a page where the inputs are displayed on one page. An example of a display screen for displaying user inputs is shown in Fig. 32.

A user who has logged into the system through the login process can follow a link to go to a shared answers page. On this page, all the questions and answers of a group (not marked as private) that have been asked prior to the cur-rent goal trigger date are displayed. An example of a shared answer display screen is shown in Fig. 33.

A matrix can be used to enable viewing of goals entered by users in a formatted display.

An example of a display screen for viewing goal statistics is shown in Fig. 34. The Matrix is based on the dimensions assigned for a group. User responses determine how the matrix is arranged. User responses can be formatted into quadrants as defined by the dimensions created for the user goals. For example, if one goal dimension has values of A, B and C and another dimension has values of 1, 2 and 3 a nine box matrix is formed with the following quadrants, A I, A2, A3, B I, B2, B3, C I, C2 and C3.

A user who has logged into the system through the login process can follow a link to go to a workspace page. The workspace page has all of the non-private inputs that have been provided by a user/member of the user's group. The inputs can be filtered by goal trigger date and/or goal category. A user can then provide feedback on the inputs displayed on the workspace page. An example of a workspace input and display screen is shown in Fig. 35.

Feedback can then be stored in the feedback table 697 and also sent to the user for whom the feedback was provided.

A group report page is available at the group level and is initiated by the group leader.

The report can be viewed in Excel or in a regular browser window. Reports enable an administrator to view the activity of users for goals by category or by goal trigger date. An example of an input and display reports screen for providing report capabilities is shown in Fig.

36.

Figs. 37-43 are fimctional flowcharts of steps in the system and method of one preferred embodiment of the present invention. These figures are self-explanatory and thus are not described in detail herein.

The present invention may be implemented with any combination of hardware and software. The present invention can be included in an article of manufacture (e.g., one or more computer program products) having, for instance, computer useable media. The media has embodied therein, for instance, computer readable program code means for providing and facilitating tile mechanisms of the present invention. The article of manufacture can be included as part of a computer system or sold separately It will be appreciated by those skilled in the art that changes could be made to the embodiments described above without departing from the broad inventive concept thereof It is understood, therefore, that this invention is not limited to the particular embodiments disclosed, but it is intended to cover modifications within the spirit and scope of the present invention as defined by the appended claims. 15

Claims (33)

1. A computer-implemented method for providing automated follow through on user goals by auto-prompting users via an electronic network, the method comprising:

(a) inputting system data for defining system operation and user goals; (b) computing one or more goal triggers based on the system data, and linking context sensitive information for assisting users in accomplishing their goals to the goal triggers; (c) using the goal triggers linked to the context sensitive information to automatically generate user goal prompts which are transmitted over the electronic network to a computer interface for presentation to the users; (d) capturing qualitative and quantitative user data regarding the user goals from one or more users in response to the user goal prompts presented at the computer interface; and (e) updating the context sensitive information based on the system data and captured user data, and generating additional goal triggers and user goal prompts based on the system data and captured user data.

is

2. The method according to claim 1 further comprising:

(f) automatically generating reports based on the system data and the captured user data; and (g) transmitting the reports via the electronic network through a reports interface to one or more users.

3. The method according to claim 1, wherein the inputting of system data, transmitting of user prompts and capturing of user data of steps a, c and d is accomplished through one or more interfaces adapted for voice activated control.

4. The method according to claim 1 further comprising:

(f) creating one or more user groups based on the system data; (g) designating users as a group member of one or more of the user groups; and (h) granting users access to selected user data of one or more other users.

5. The method according to claim 1, wherein the user goal prompts of step (c) are transmitted to the users using a voice mail system, and wherein the user data of step (d) is captured using voice recognition to translate voice input to text input.

6. The method according to claim 1, further comprising:

(f) tracking user application of the context sensitive information for assisting users in accomplishing their goals.

7. The method according to claim 1, finiher comprising:

(f) providing one or more databases for storing the system data, the user data and the context sensitive information; and (g) granting access to the databases to allow users to share and apply information.

8. The method according to claim 1, wherein the system data includes at least one of the following, administrator profiles, company profiles, group profiles, and user profiles.

9. The method according to claim 1, further comprising:

(f) periodically repeating steps (b) through (e).

10. The method according to claim 1, wherein the context sensitive information includes audio, video or text related to a user goal which can be applied by the user in accomplishing the user goal.

11. The method according to claim 1, further comprising:

(f) capturing feedback input regarding the system data, the user data and the context sensitive information from one or more users and transmitting the feedback over the electronic network to at least one other user to allow interaction between users.

12. An article of manufacture for providing automated follow through on user goals by auto-prompting users via an electronic network, the article of manufacture comprising a computer-readable medium holding computer-executable instructions for performing a method comprising:

(a) inputting system data for defining system operation and user goals; (b) computing one or more goal triggers based on the system data, and linking context sensitive information for assisting users in accomplishing their goals to the goal triggers; (c) using the goal triggers linked to the context sensitive information to automatically generate user goal prompts which are transmitted over the electronic network to a computer interface for presentation to the users; (d) capturing qualitative and quantitative user data regarding the user goals from one or 5 more users in response to the user goal prompts presented at the computer interface; and (e) updating the context sensitive information based on the system data and captured user data, and generating additional goal triggers and user goal prompts based on the system data and captured user data.

13. The article of manufacture according to claim 12 wherein the computerexecutable instructions perform a method furffier comprising:

(f) automatically generating reports based on the system data and the captured user data; and (g) transmitting the reports via the electronic network through a reports interface to one or more users.

14. The article of manufacture according to claim 12, wherein the inputting of system data, transmitting of user prompts and capturing of user data of steps a, c and d is accomplished through one or more interfaces adapted for voice activated control.

15. The article of manufacture according to claim 12 wherein the computerexecutable instructions perform a method further comprising:

(f) creating one or more user groups based on the system data; (g) designating users as a group member of one or more of the user groups; and (h) granting users access to selected user data of one or more other users.

16. The article of manufacture according to claim 12, wherein the user goal prompts of step (c) are transmitted to the users using a voice mail system, and wherein the user data of step (d) is captured using voice recognition to translate voice input to text input.

17. The article of manufacture according to claim 12 wherein the computerexecutable instructions perform a method further comprising:

(f) tracking user application of the context sensitive information for assisting users in accomplishing their goals.

18. The article of manufacture according to claim 12 wherein the computerexecutable 5 instructions perform a method further comprising:

(f) providing one or more databases for storing the system data, the user data and the context sensitive information; and (g) granting access to the databases to allow users to share and apply information.

19. The article of manufacture according to claim 12 wherein the system data includes at least one of the following, administrator profiles, company profiles, group profiles, and user profiles.

20. The article of manufacture according to claim 12 wherein the computerexecutable instructions perform a method further comprising:

(f) periodically repeating steps (b) through (e).

2 1. The article of manufacture according to claim 12 wherein the context sensitive information includes audio, video or text related to a user goal which can be applied by the user in accomplishing the user goal.

22. The article of manufacture according to claim 12 wherein the computerexecutable instructions perform a method further comprising:

(f) capturing feedback input regarding the system data, the user data and the context sensitive information from one or more users and transmitting the feedback over the electronic network to at least one other user to allow interaction between users.

23. An apparatus for providing automated follow through on user goals by auto prompting users via an electronic network, the apparatus comprising:

(a) means for inputting system data for defining system operation and user goals; (b) means for computing one or more goal triggers based on the system data, and linking context sensitive information for assisting users in accomplishing their goals to the goal triggers; (c) means for using the goal triggers linked to the context sensitive information to automatically generate user goal prompts which are transmitted over the electronic network to a computer interface for presentation to the users; (d) means for capturing qualitative and quantitative user data regarding the user goals from one or more users in response to the user goal prompts presented at the computer interface; and (e) means for updating the context sensitive information based on the system data and captured user data, and generating additional goal triggers and user goal prompts based on the system data and captured user data.

24. The apparatus according to claim 23 further comprising:

(f) means for automatically generating reports based on the system data and the captured user data; and (g) means for transmitting the reports via the electronic network through a reports interface to one or more users.

25. The apparatus according to claim 23, wherein the inputting of system data, transmitting of user prompts and capturing of user data of steps a, c and d is accomplished through one or more interfaces adapted for voice activated control.

26. The apparatus according to claim 23 further comprising:

(f) means for creating one or more user groups based on the system data; (g) means for designating users as a group member of one or more of the user groups; and (h) means for granting users access to selected user data of one or more other users.

27. The apparatus according to claim 23, wherein the user goal prompts of step (c) are transmitted to the users using a voice mail system, and wherein the user data of step (d) is captured using voice recognition to translate voice input to text input.

28. The apparatus according to claim 23, further comprising:

(f) means for tracking user application of the context sensitive information for assisting users in accomplishing their goals.

29. The apparatus according to claim 23, further comprising:

(f) means for providing one or more databases for storing the system data, the user data and the context sensitive information; and (g) means for granting access to the databases to allow users to share and apply information.

30. The apparatus according to claim 23, wherein the system data includes at least one of the following, administrator profiles, company profiles, group profiles, and user profiles.

3 1. The apparatus according to claim 23, further comprising:

(f) means for periodically repeating steps (b) through (e).

32. The apparatus according to claim 23, wherein the context sensitive information includes audio, video or text related to a user goal which can be applied by the user in accomplishing the user goal.

33. The apparatus according to claim 23, further comprising:

(f) means for capturing feedback input regarding the system data, the user data and the context sensitive information from one or more users and transmitting the feedback over the electronic network to at least one other user to allow interaction between users.