US20130095929A1

US20130095929A1 - System and method for progressive relationship development

Info

Publication number: US20130095929A1
Application number: US13/275,840
Authority: US
Inventors: Elizabeth Wilson
Original assignee: Match com LLC
Current assignee: Match Group LLC
Priority date: 2011-10-18
Filing date: 2011-10-18
Publication date: 2013-04-18

Abstract

A computer system and computer implemented method to develop a relationship according to a multi-step process. The computer system may define a workflow having multiple stages, each stage having one or more game sessions to develop the relationship between participants. The games in successive stages of the workflow may be designed to encourage increased communication between the participants. A workflow may comprise at least three stages including a connect stage, a play stage, and a meet stage. An initial communication may include a written or asynchronous communication. Increased communication may include a voice, video, or real-time communication.

Description

BACKGROUND

Aspects of the present invention relate generally to the field of digital communications, and more specifically to networked computer systems that manage social interactions among users in a structured manner.
Conventional relationship development systems often provide opportunities for members to ‘virtually meet’ other users and to engage in activities that allow the members to get to know one another, but often such systems allow the introduction stages to linger without encouraging efficient progress in developing the relationship to achieve the end goal of an in-person meeting in a timely manner. Additionally, such conventional systems do not often manage expectations so that members may receive an unpleasant surprise when it comes time to meet in person. This often results in feelings of disappointment, having been deceived, and having wasted time working towards a relationship that was not going to be successful.
Accordingly, there is a need for a system that facilitates interactions to progressively develop a relationship while managing expectations to avoid disappointment.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other aspects of various embodiments of the present invention will be apparent through examination of the following detailed description thereof in conjunction with the accompanying drawing figures in which similar reference numbers are used to indicate functionally similar elements.

FIG. 1 is a functional block diagram illustrating components of an exemplary system according to an embodiment of the present invention.

FIG. 2 illustrates an exemplary support system according to an embodiment of the present invention.

FIG. 3 illustrates exemplary records for relationship development information according to an embodiment of the present invention.

FIG. 4 illustrates an exemplary interface displaying user profile options on an exemplary client device according to an embodiment of the present invention.

FIG. 5 illustrates an exemplary interface for accessing a progressive relationship feature on an exemplary client device according to an embodiment of the present invention.

FIG. 6 illustrates an exemplary method for progressively developing a relationship according to an embodiment of the present invention.

FIG. 7 illustrates an exemplary interface for a connect stage game on a client device according to an embodiment of the present invention.

FIG. 8 illustrates an exemplary interface for a play stage game on a client device according to an embodiment of the present invention.

FIG. 9 illustrates an exemplary interface for a meet stage game on a client device according to an embodiment of the present invention.

FIGS. 10( a)-10(b) illustrate exemplary systems facilitating participation in a game according to an embodiment of the present invention.

DETAILED DESCRIPTION

A computer system for developing a relationship according to a multi-step process is disclosed. Relationship development may occur in small steps, each step designed to get to know the other person a little better and to encourage more meaningful communication. A computer may store a data object that defines a workflow having multiple stages to assist in the progressive development of a relationship between multiple system users. Each workflow stage may include one or more games such that the games each stage are designed to encourage increased communication between the participants. A workflow may comprise at least three stages including: a connect stage having games that may be designed to introduce the workflow participants, a play stage having games that may be designed to determine if the relationship has the potential to continue developing, and a meet stage having games that may be designed to manage expectations if the relationship is to continue. Initial stages may include games encouraging written or asynchronous communication. Subsequent stages may include encouraging voice, video, or real-time communication via interactive sessions managed by the computer system.
FIG. 1 is a functional block diagram illustrating components of an exemplary system 100 according to an embodiment of the present invention. As shown in FIG. 1, the system 100 may include one or more clients 110 accessing at least one server 120 via a network 130. The server 120 may be a network server connected to the client 110 via the network 130. The server 120 may manage operation of a relationship development system for progressively developing a relationship between users, the users connected to the relationship development system via the clients 110. Server 120 may be a single, stand-alone server, it may consist of multiple servers wherein each server performs a specific function in the system, or it may consist of redundant servers that provide reliability for multiple individuals accessing multiple aspects of the system at one time. The network 130 may be a wired or wireless network that may include a local area network (LAN), a wireless area network (WAN), the Internet, or any other network available for accessing the server 120 via the client 110.
A user may access the relationship development system from the client 110 via a user interface 111 capable of accessing and displaying the relationship development system. The client 110 may be any device that facilitates a user accessing the server 120 via a user interface 111, for example a personal computer, laptop, tablet device, Internet accessible gaming system, mobile handheld computing device, or other network accessible device. The user interface may be a program or application or may comprise middleware that acts as a frontend to or otherwise facilitates access to the relationship development system. The user may interact with the user interface 111 through an input device, such as by inputting a selection as with a mouse, a keyboard, a handheld controller, or a screen tap. The user may observe the response to the selection on an output device or display. In accordance with an aspect of the invention, the user interface 111 may run in a browser window controlled by the user, the browser window connected to and receiving instruction from the server 120. In another aspect of the invention, the user interface 111 may run in an application window for an application installed on the client 110 and controlled by the user.
When a user accesses the interface 111, the client device 110 may communicate with the server 120. The server may return information to the client device 110 to facilitate the user's interaction with the relationship development system. The client interface 111 may display one or more modules, each module supported by one or more databases accessible by the server 120.
FIG. 2 illustrates an exemplary support system 200 according to an embodiment of the present invention. As shown in FIG. 2, several servers 220 manage access to the support storage 225, including a user records store 225.1, workflow store 225.2, and a game store 225.3. Each store 225.1, 225.2, 225.3 may be a database or other memory storage device for organizing relationship development system records 226. According to an embodiment, as shown in FIG. 2, multiple data stores 226 may each be accessed and supported by a network server 220. Alternatively, one or more data stores may be accessed from a single network server, or the communication of information from each data store and individual support server may be managed by a separate communications server (not shown).
FIG. 3 illustrates exemplary records for relationship development information according to an embodiment of the present invention. As shown, a user record 310 may store information for individual system users. Each user record 310 may include profile information, such as user name or ID 311, contact information, and a user status 314. The user status 314 may indicate whether the user is active or inactive, may reflect the user's current availability (e.g. online or logged in), or may reflect some other status used by the system. A user record 310 may additionally include pointers to the records of other system users with whom they have been matched 312 as having potential to develop a relationship, as well as one or more active workflows 313. Each workflow may be initiated by a user to begin developing a relationship with another user with whom they have been matched. A user record 310 may contain other information not listed, for example a user record may include one or more photos of the user.
A user registered with the progressive relationship system, and with a valid user record 310, may utilize the features of the relationship system to develop a progressive relationship with another user. In accordance with an embodiment, a user may be a registered user of a relationship system that encourages or facilitates communication between users. Then, a progressive development feature may be implemented as part of the relationship development system. Any registered user of the relationship system may have access to the progressive development feature and begin progressively forming relationships with other users.
According to an embodiment, the progressive development feature may be implemented as a self-contained application of the relationship system. Then the users may access the relationship system and the progressive development feature with separate interface modules or applications. A progressive development interface module may be downloaded onto a user's client device as an individual application, accessed via a browser window running on the client device, or accessed from a third party application or website utilizing a feature Application Programming Interface (API) of the relationship system.
In an embodiment, access to the progressive development feature may be restricted to a subset of all users registered with the system. For example, access may be limited to users that have completed an extended user profile or as a reward, for example, for reaching a milestone in terms of length of membership with the system, for highly active users, or as part of a promotion. An exemplary extended user profile may include one or more photos of the user, for example a head shot, a head-to-toe shot, a photo of the user with friends or family, a photo of the user participating in a favorite hobby, a voice caption or commentary on one or more of the user's photos, a short video, or short personal statement about the user's likes and dislikes. The user's status 314 or other status information associated with the user record 310, may reflect the user's permissions for accessing system features, for example, the user status 314 may indicate that the user is in good standing and may access the progressive development feature of the relationship system.
As shown in FIG. 3, a workflow record 320 may include a unique workflow ID 321, pointers to the users that are participants in the workflow 322, pointers to games the users are participating in as part of the workflow 323, and the status of the workflow 324. The status of the workflow 324 may indicate how far into the progressive development process the participating users 322 have progressed, for example a workflow status 324 may reflect that the workflow is ‘complete’ if the participants 322 have successfully completed each step in the workflow, ‘in progress’ if the participants 322 have completed only a portion of the steps in the workflow, or ‘closed’ if the users have not completed the workflow but have declined to complete all the steps of the workflow. The workflow record 320 may contain other information not listed, for example a count of the number of games the participants have played, a history of the communication exchanged between the participants, or a personal rating or comment submitted by one participant about the experience of participating in the workflow or developing a relationship with the other participant.
A game record 330 may include a unique game ID 331, a game status 332, and pointers to the users that are participating in the game 333. A game record 330 may additionally contain game parameters 334 utilized by the relationship development system in implementing the game. Game parameters may include, for example, the participant who will have the next ‘turn’ in the game, the method the participants 333 have chosen to exchange communication where applicable, for example through an in-game messaging service or a third party instant messaging service, or other relevant information. The game record 330 may also contain other information not listed, for example a time or turn limit either predefined by the system or selected by one or more of the participants.
FIG. 4 illustrates an exemplary interface 400 displaying user profile options on an exemplary client device according to an embodiment of the present invention. A user may access the profile interface 400 to set up or edit a user profile. Registration may be required to access the profile interface and to gain access to the progressive development feature of a relationship development system. As shown in FIG. 4, a profile interface 400 may display a profile update module 411 that may provide options for the user to update their profile in order to complete registration for the progressive development feature. A status module 412 may indicate the number of matches and workflows an active user has pending, or the number of messages waiting for the user, or other information relevant to the user's activities in the relationship development system. An information module 413 may provide identification of the user's registration status and the steps necessary to proceed, an option to install and test any real-time communication options, including, for example, a secure instant messaging service or a video chat application, or any other information to assist the user in utilizing in the progressive development feature.
Additionally, as part of the registration process, or through a profile edit interface, the user may identify third party sites or social networking applications that they may use with the relationship development system, or that they may want to grant access to their user profile information. A relationship development system user may share his workflow status or game results by selecting links from their general profile interface or progressive development feature profile interface that may make a post to a social networking site, facebook for example. A user may additionally have the option to automatically post updates to the third party site, for example a twitter message may be published upon completion of a game or upon advancing to a new stage in a workflow of the progressive development feature. Similarly, the user may also receive a notification, for example by email, through a message in a pop-up window, or via a message received in a local mailbox as part of the relationship development system, summarizing the workflow status upon completion of a stage in the progressive development feature.
FIG. 5 illustrates an exemplary interface 500 for accessing a progressive relationship feature on an exemplary client device according to an embodiment of the present invention. As shown in FIG. 5, a progressive relationship interface 500 may include a workflow module 511, a status module 512 and an ID module 513. An ID module 513 may identify the user and provide information and links to a user profile interface or links to access other aspects of the progressive relationship feature. As previously described, a status module 512 may indicate the number of matches and workflows an active user has pending, or the number of messages waiting for the user, or other relationship information relevant to the user's activities on the relationship development system.
A workflow module 511 may provide access to any progressive relationship workflows in progress and links to continue the workflow by engaging in games that advance the progressive relationship. As shown in FIG. 5, the workflow module 511 may identify the workflows in progress, including the status of each workflow. For example, a progressive relationship workflow may include multiple stages. Each stage may advance the relationship development and encourage and increase communication between the participants. From the progressive relationship interface 500, a user may view the status of each pending workflow, may initiate a next stage of an active workflow, or may terminate an active workflow.
FIG. 6 illustrates an exemplary method 600 for progressively developing a relationship according to an embodiment of the present invention. As shown in FIG. 6, a user may preliminarily log into the relationship development system and access a general user profile interface (block 605). In an exemplary embodiment, from the user profile interface a user may view or update the profile information, may retrieve or send messages, and may access available features of the relationship development system. One of the accessible features of the relationship development system may include a progressive development profile or workflow status page (block 610). As previously noted, a registered user may access the progressive development feature directly, without first accessing the relationship system user profile, for example, with a progressive development feature specific interface or application, or from a third party application. Additionally, an application using the provided API may display and provide access to the functionality of the progressive development feature without directly accessing either the general user profile or the progressive development profile.
A progressive development profile or workflow status page may provide access to the workflows the registered user has pending and options to create a new workflow or to terminate an active workflow. The user may then request access to an active workflow (block 615). If the requested workflow is in progress, the user may then access that workflow (block 620). If the user requests a new workflow with another user of the relationship development system, then a participation request may be sent to the identified user (block 625). If the identified user declines participation in the workflow (block 630), then the workflow may be terminated (block 655). However, if the identified user accepts the request to participate in the workflow (block 630), a new workflow may be created for the two users.
The progressive development feature of the relationship development system may then facilitate the stages of a workflow initiated by the user, each stage implemented to improve and encourage communication between the participants. Encouraging greater communication in progressive stages of a workflow may include encouraging lengthier or more meaningful communication. Exemplary stages of a workflow may include a connect stage (block 635), a play stage (block 640), a meet stage (block 645), and a date stage (block 650). As will be understood, different or additional stages may be implemented while maintaining the goal of the workflow to progressively develop a relationship by encouraging increasing and more meaningful communication between participants.
According to an aspect of an embodiment, the stages of the workflow may only be accessed in order. Then the users cannot participate in a meet stage game without first participating in a connect stage game. In other embodiments, participants may access the stages in any order. In some embodiments a participant may access each stage of the workflow only once while in other embodiments the users can participate in multiple games for each stage multiple times.
A user may terminate the workflow at any time (block 655). Access to the workflow may then be restricted for all users of the workflow upon termination by any one user. The workflow may additionally be automatically terminated, for example upon completion of all stages of the workflow. Each game in any stage of the workflow may continue for a predetermined number of game turns, a predetermined length of time, or until a participant exits the game.
Connect stage games may be intended to establish communication and determine if the participants have enough in common to pursue a closer relationship. The connect stage may include one or more interactive games to introduce the players and break the ice between matched participants. Users may participate in connect stage games in an asynchronous manner, sharing responses and reactions when convenient, over a period of time. When it is a user's turn, the user may receive a notification prompting them to play. Notifications may be received as a message displayed in a relationship system mailbox, a pop up message that activates when the user accesses the relationship system, an external email message or SMS message, an application alert or badge, or other method of communicating an appropriate notification to the user. The time for response in a connect stage game may be restricted, for example, such that the user cannot immediately reply or cannot reply within the hour, or such that the user may be required to reply within a predetermined number of days before the game or workflow is terminated. Exemplary connect stage games may include a fortune cookie game, a card sorting game, a category listing game, a rating game, or a short answer game.
In an exemplary rating game, a participant may rate one or more images, items, quotations, or other objects. For a given image, the participant may first decide whether they like the depicted image or not, then share their decision or a group of decisions with the other participants. Upon comparing the ratings or decisions for each image, the participants may then discuss why they decided an image a certain way or ask questions about the other participant's rankings. Alternatively, given a topic or a category of a personal characteristic that is meaningful for a successful relationship, a participant may identify the characteristics that are important to them, share their identified characteristics with other participants, and compare the identified characteristics. Such ranking style games provide participants an opportunity to quickly and easily identify things they have in common or significant incompatibilities.
For an exemplary fortune cookie game, a user may select or be assigned a fortune. The user may then share an interpretation, understanding or impression related to the fortune with the workflow participants, compare interpretations, or describe how the fortune applies to them. In an exemplary card sorting game, the game may present to the participants multiple cards in a category or theme, each participant may then put the cards in an order or ranking that has meaning for them. The participants may then share and compare their sorted order. Additionally, in an exemplary category listing game, a participant may choose a topic from a list of potential topics and then list four things responsive to the topic, and then share and compare their list with the other participants.
Any one of these games may also serve as a short answer game in which the card or category and the resultant responses, orders and lists may serve as talking points that inspire the exchange of a series of questions between the participants. Similarly, in an exemplary stand-alone short answer game, a participant may choose a question from a list of predetermined questions, may choose a topic of potential interest, may come up with their own questions, or may be provided a question to answer or discuss. Then the participant may ask another participant the selected question and respond to their questions in turn.
FIG. 7 illustrates an exemplary interface 700 for a connect stage game on a client device according to an embodiment of the present invention. As shown in FIG. 7, a connect stage interface 700 may include a game module 711, a workflow status module 712, and a participant ID module 713. The workflow status module 712 may identify the progress of the workflow, for example, whether the current game is part of the connect stage, the play stage, or the meet stage of the progressive development feature. A participant ID module 713 may identify the workflow participants for the game and their current status or other biographical information.
An exemplary fortune cookie game is illustrated in FIG. 7. The game module 711 may be an interface provided by the progressive development feature, displayed on a client device for participants to interact with a game. For example, a game module 711 may include an input module 715 to receive commands or comments or other input from the participant. The effects of the input may then be displayed in the game module, may advance the game, or may otherwise be shared with the other participants. The game module 711 may additionally contain one or more display modules 714 that illustrate aspects of the game to the participants, including, for example communications exchanged between the participants.
The play stage may include asynchronous and real time interactive games to allow the participants who have identified common interests or otherwise wish to know each other better, to determine if they want to continue to develop the relationship. Users may participate in asynchronous games as part of the play stage, sharing responses and communications when convenient, over a period of time. Users may additionally participate in play stage games in a natural, real-time manner, sharing responses and reactions to the games as they occur. Play stage games may be intended to encourage greater communication and allow the participants to determine if they are interested in pursuing a closer relationship. Exemplary play stage games may include a storyline game or a debate style game.
In an exemplary storyline game, given a portion of a story, the participants may take turns continuing and developing the story. Similarly, for a given storyline, the participants may take turns describing their thoughts and reactions, or may even engage in a friendly debate. Such games may require a more detailed answer or otherwise encourage more communication than the connect stage games.
FIG. 8 illustrates an exemplary interface 800 for a play stage game on a client device according to an embodiment of the present invention. As shown in FIG. 8, a play stage interface 800 may include a game module 811, a workflow status module 812, and a participant ID module 813. The workflow status module 812 may identify the progress of the workflow and the status of the workflow participants, for example, whether they are currently connected to the relationship system or not. A participant ID module 813 may identify the workflow participants for the game.
An exemplary play stage game is illustrated in FIG. 8. The game module 811 may be an interface provided by the progressive development feature, displayed on a client device for users to interact with a game. For example, a game module 811 may include an input module 815 to receive commands or comments or other input from the participant. The game module 811 may additionally contain one or more display modules 814 that illustrate aspects of the game to the participants, including, for example communications exchanged between the participants. Participants may be encouraged to exchange real time communications as part of the game, or engage in a conversation aside from the game. Such communication may be facilitated by the game as part of the play stage interface 800 or may occur by instant messenger, email or other live, written communication method.
The meet stage may include one or more real time interactive games that include a video or other ‘face-to-face’ style communication to allow the participants to get to know each other better and to determine if they want to continue to pursue the relationship. Users may participate in meet stage games in an interactive, real-time, face-to-face manner, visually or vocally sharing responses and reactions to the games as they occur. Meet stage games may be intended to encourage real-time, face-to-face communication in order to introduce the participants visually, to help participants manage expectations about the other participants, to avoid the obligations that may necessarily accompany a first, in-person, meeting and limit the interaction to avoid awkwardness, and to determine if the participants are interested in pursuing a closer relationship.
Exemplary meet stage games may include a conversation starter game or other game designed to get the participants to engage in a video conversation. In an exemplary conversation starter game, a topic is displayed or selected and a live video conversation between the participants is initiated. A meet stage game may be limited by the number of steps performed in a game, or by time such that after a predetermined period of time, e.g. 10 minutes, the game will automatically end.
FIG. 9 illustrates an exemplary interface 900 for a meet stage game on a client device according to an embodiment of the present invention. As shown in FIG. 9, a meet stage interface 900 may include a game module 911 and a workflow status module 912. The workflow status module 912 may identify the progress of the workflow and the status of the workflow participants.
An exemplary meet stage game is illustrated in FIG. 9. The game module 911 may be an interface provided by the progressive development feature, displayed on a client device for users to interact with a game. Participants may interact with the game and each other via an input module 915 that may receive commands or comments or other input from the participant. The game module 911 may additionally contain one or more display modules 914 that facilitate face-to-face communication between the participants. Participants may engage in a video conversation as part of the game or engage in a conversation unrelated to the game. Such communication may be facilitated by the game as part of the meet stage interface 900 or may occur by other video communication service, for example, a mobile to mobile video chat, to engage in a face-to-face conversation.
The date stage may include setting up, arranging and evaluating an actual in-person meeting. The progressive development feature may facilitate setting up a date by encouraging the participant to leave a voicemail for or send a message to another participant, or by assisting in organizing tickets or reservations. Additionally, the participants may set parameters for a date, for example a date, a time, a place and a type of activity. Then the relationship development system may query affiliated systems on the network to identify an available setting for a date meeting those specified parameters. The relationship development system may additionally automatically make an appropriate reservation with or reserve the appropriate tickets from an affiliated system and notify the participants of the scheduled event. The progressive development feature may also encourage the participants to rate the date, thereby confirming it took place and indicating completion of all the steps in the workflow.
FIGS. 10( a) and 10(b) illustrate exemplary systems 1000, 1030 facilitating the participation of users in a game and communication between the participants according to an embodiment of the present invention. As shown in FIG. 10( a) users using client devices 1010.1 and 1010.2 may access a games server 1020 to participate in a game supported by the progressive relationship development system. Then, the games server 1020 may pass game play information 1021, including an interface with which the users can view and participate in the game and display any actions taken by a user during game play. According to the system 1000, the users may additionally engage in direct, real-time communication 1022 through a connection separate from the games server 1020 while playing the game. The real-time communication 1022 may include a written exchange in a real-time play stage game or a video chat that may occur during a meet stage game.
As shown in FIG. 10( b) users using a client devices 1010.3 and 1010.4 may access a games server 1020 to participate in a game supported by the progressive relationship development system. Then, the games server 1020 may pass game play information and facilitate interaction between the users during game play. According to the system 1030, the users may engage in communication 1031 via the games server 1020, while playing the game. The game server facilitated communication 1031 may include an asynchronous written exchange in a connect or play stage game, or real-time communication such as a written exchange in a real-time play stage game, voice communication exchanged in a real-time game, or a video chat during a meet stage game.
The foregoing discussion identifies functional blocks that may be used in relationship development systems constructed according to various embodiments of the present invention. In practice, these systems may be applied in a variety of devices, such as personal computing systems and/or mobile devices. In some applications, the functional blocks described hereinabove may be provided as elements of an integrated software system, in which the blocks may be provided as separate elements of a computer program. Some embodiments may be implemented, for example, using a computer-readable storage medium or article which may store an instruction or a set of instructions that, if executed by a processor, may cause the processor to perform a method in accordance with the embodiments.
In some applications, the modules described hereinabove may be provided as elements of an integrated software system, in which the blocks may be provided as separate elements of a computer program. Other applications of the present invention may be embodied as a hybrid system of dedicated hardware and software components. Moreover, not all of the modules described herein need be provided or need be provided as separate units. For example, while the exemplary data stores in FIG. 2 are illustrated as embodying multiple different storage devices, the relevant information may be stored in a single memory storage device. It is also noted that the arrangement of the blocks in FIG. 6 does not necessarily imply a particular order or sequence of events, nor is it intended to exclude other possibilities. For example, the operations depicted at blocks 605 and 610 may occur substantially simultaneously with each other or blocks 605, 610 and 650 may not occur at all. Such implementation details are immaterial to the operation of the present invention unless otherwise noted above.
While the invention has been described in detail above with reference to some embodiments, variations within the scope and spirit of the invention will be apparent to those of ordinary skill in the art. Thus, the invention should be considered as limited only by the scope of the appended claims.

Claims

What is claimed is:

1. A method for progressively developing a relationship, comprising:

in a computer system, instantiating a workflow for a first user and a second user, the workflow comprising a plurality of stages for developing a progressive relationship; and

for each stage in the workflow:

selecting a game to be played between the connected users, and

managing a game session between the connected users;

wherein the game sessions of successive stages provide successively increased communication between the users.

2. The method of claim 1, wherein communication for a game session in a first stage of the workflow includes asynchronous communication and communication for a game session in a subsequent stage of the workflow includes real-time communication.

3. The method of claim 1, wherein communication for a game session in a first stage of the workflow includes written communication and communication for a game session in a subsequent stage of the workflow includes voice communication.

4. The method of claim 1, wherein communication for a game session in a first stage of the workflow includes written communication and communication for a game session in a subsequent stage of the workflow includes video communication.

5. The method of claim 1 wherein a topic of communication in a subsequent stage of the workflow is more complex than communication in a first stage of the workflow.

6. The method of claim 1 wherein the connected users cannot play a game in a subsequent stage until they have played a game in a first stage.

7. A method for progressively developing a relationship, comprising:

initiating at a server, a first communication between a plurality of users by moderating a connect style game having a first level of communication;

after a connect style game has been played, initiating with the server a subsequent communication between the plurality of users by moderating a play style game having a second level of communication; and

after a play style game has been played, initiating with the server a communication between the plurality of users by moderating a meet style game having a third level of communication.

8. The method of claim 7 wherein the first level of communication includes asynchronous communication.

9. The method of claim 7 wherein the first level of communication includes written communication.

10. The method of claim 7 wherein the second level of communication includes asynchronous communication.

11. The method of claim 7 wherein the second level of communication includes real-time communication.

12. The method of claim 7 wherein the second level of communication includes voice communication.

13. The method of claim 7 wherein the third level of communication includes real-time communication.

14. The method of claim 7 wherein the third level of communication includes video communication.

15. A non-transitory computer readable medium storing instructions that when executed by a processor implements a method comprising:

instantiating a workflow for a first user and a second user, the workflow comprising a plurality of stages for developing a progressive relationship;

for each stage in the workflow:

selecting a game to be played between the connected users; and

managing a game session between the connected users;

16. A non-transitory computer readable medium storing instructions that when executed by a processor implements a method comprising:

17. A system for facilitating progressive development of a relationship, comprising:

a memory that stores a workflow for a plurality of users, the workflow comprising a plurality of stages for developing a progressive relationship;

a server connected to a network, said server configured to manage a game session between the connected users for each stage of the workflow;

wherein the game sessions of successive stages provide successively increased communication between the users

18. A system for facilitating progressive development of a relationship, comprising:

a memory that stores interactive games for a plurality of users developing a relationship;

a server connected to a network, said server configured to:

initiate a first communication between the plurality of users by moderating a connect style game having a first level of communication;

after a connect style game has been played, initiate a subsequent communication between the plurality of users by moderating a play style game having a second level of communication; and

after a play style game has been played, initiate a final communication between the plurality of users by moderating a meet style game having a third level of communication.