Patent Publication Number: US-11392865-B1

Title: Systems and methods for accessing a decision tree

Description:
CROSS-REFERENCE TO RELATED APPLICATION(S) 
     This application is a continuation of U.S. patent application Ser. No. 15/838,209 filed on Dec. 11, 2017, which is a division of U.S. patent application Ser. No. 14/248,889 filed on Apr. 9, 2014 (now U.S. Pat. No. 9,875,449), which is a continuation of U.S. patent application Ser. No. 11/828,982 filed on Jul. 26, 2007 (now U.S. Pat. No. 8,744,891), all of which are hereby incorporated by reference in their entirety. This application is also related to U.S. patent application Ser. No. 11/829,003, filed Jul. 26, 2007, and U.S. patent application Ser. No. 11/829,016, filed on Jul. 26, 2007, all of which are incorporated herein by reference in their entirety. 
    
    
     TECHNICAL FIELD 
     Various embodiments described herein relate generally to computer systems, and more particularly, but not by way of limitation, to systems and methods for dynamic business decision making. 
     BACKGROUND 
     Wide-area networks, including world-wide networks, such as the Internet, have become essential tools for personal and business use. As consumers continue to gain familiarity and comfort using online tools, such as Internet browsers, email, and real-time communication tools, business can continue to expand services. For example, using the Internet to supplement traditionally human-supplied services, such as customer support and order processing, businesses can provide goods and services at lower costs and consumers can gain certain advantages, such as 24-hour accessibility or multi-lingual capabilities. As technology increases in complexity, more intelligent systems become possible. 
     SUMMARY 
     Systems and methods for dynamic business decision making are described. In an embodiment, a system comprises a first module configured to access a business rule; a second module configured to deconstruct the business rule into a condition and an associated action; a third module configured to determine a set of questions relevant to the condition; a fourth module configured to place the set of questions into a question queue; a fifth module configured to order the question queue; and a sixth module configured to present the question queue to a user. 
     In an embodiment, a system comprises a first module configured to receive a request from a user; a second module configured to determine a subject of the request; a third module configured to use the subject to obtain a set of relevant questions; a fourth module configured to determine, for each question in the set of relevant questions, whether an answer to a current question is available in a storage area; and a fifth module configured to present the current question to the user when the answer to the current question is not available in the storage area. 
     In an embodiment, a system comprises a first module configured to access a decision tree, wherein the decision tree is organized using a first question as a root node and a plurality of terminal questions as leaf nodes; a second module configured to determine a current node of the decision tree, wherein the current node corresponds with a current question being presented to a user in a user-interface; a third module configured to determine an estimated number of nodes between the current node and a leaf node; and a fourth module configured to present a representation using the estimated number of nodes in the user-interface. Other embodiments are described. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a schematic view of a computer network system according to various embodiments. 
         FIG. 2  is a block diagram of processing modules of the online document system shown in  FIG. 1  according to various embodiments. 
         FIG. 3  is a flowchart illustrating a method according to various embodiments. 
         FIG. 4  is a block diagram of processing modules of the online document system shown in  FIG. 1  according to various embodiments. 
         FIG. 5  is a flowchart illustrating a method according to various embodiments. 
         FIG. 6  is a block diagram of processing modules of the online document system shown in  FIG. 1  according to various embodiments. 
         FIG. 7  is a flowchart illustrating a method according to various embodiments. 
         FIG. 8  is a block diagram illustrating a machine in the example form of a computer system, within which a set or sequence of instructions for causing the machine to perform any one of the methodologies discussed herein may be executed, according to various embodiments. 
     
    
    
     DETAILED DESCRIPTION 
     The following detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, example embodiments. These embodiments, which are also referred to herein as “examples,” are described in enough detail to enable those skilled in the art to practice aspects of the inventive subject matter. 
     In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one. In this document, the term “or” is used to refer to a nonexclusive or, unless otherwise indicated. 
     System Overview 
       FIG. 1  is a schematic view of a computer network system  100  according to various embodiments. The computer network system  100  includes a business decision management system  102  and a client computer  104 , communicatively coupled via a network  106 . In an embodiment, the business decision management system  102  includes a web server  108 , an application server  110 , a messaging server  112 , a database management server  114 , which is used to manage at least a decision management database  116 , and a file server  118 . The business decision management system  102  may be implemented as a distributed system, for example one or more elements of the business decision management system  102  may be located across a wide-area network from other elements of the business decision management system  102 . As another example, a server (e.g., web server  108 , file server  118 , database management server  114 ) may represent a group of two or more servers, cooperating with each other, in providing a pooled, distributed, or redundant computing model. 
     The network  106  may include local-area networks (LAN), wide-area networks (WAN), wireless networks (e.g., 802.11 or cellular network), the Public Switched Telephone Network (PSTN) network, ad hoc networks, personal area networks (e.g., Bluetooth) or other combinations or permutations of network protocols and network types. The network  106  may include a single local area network (LAN) or wide-area network (WAN), or combinations of LAN&#39;s or WAN&#39;s, such as the Internet. The various devices coupled to the network  106  may be coupled to the network  106  via one or more wired or wireless connections. 
     The web server  108  may communicate with the file server  118  to publish or serve files stored on the file server  118 . The web server  108  may also communicate or interface with the application server  110  to enable web-based presentation of information. For example, the application server  110  may consist of scripts, applications, or library files that provide primary or auxiliary functionality to the web server  108  (e.g., multimedia, file transfer, or dynamic interface functions). In addition, the application server  110  may also provide some or the entire interface for the web server  108  to communicate with one or more of the other servers in the decision management system  102 , e.g., the messaging server  112  or the database management server  114 . 
     The application server  110  may also include a business rules application platform to create, manage, and administer business rules. The business rules application platform may include commercial packages, such as ORACLE BUSINESS RULES of ORACLE CORP. of Redwood Shores, Calif. 
     The decision management database  116  may include data to manage business rules, manage question templates, manage decision trees, or manage users&#39; answers or other user data. The document management database  116  may be implemented as a relational database, a centralized database, a distributed database, an object oriented database, or a flat database in various embodiments. 
     In an embodiment, a user (not shown) at a client computer  104  may interface with the decision management system  102 , such as by using the web server  108 , to initiate an activity. The activity may include financial activities (e.g., loan approval or pre-approval, insurance coverage or changes, investment account changes, or banking services). The activity may also include other types of customer relations activities, such as order processing, account activation, account access, routine security checks, or surveys. The user may be presented one or more questions with relevant options for answers using user-interface elements, such as drop down lists, check boxes, radio buttons, text input fields, or the like. The user-interface may be implemented using a variety of programming languages or programming methods, such as HTML, VBScript, JavaScript, XML, XSLT, AJAX, Java, and Swing. 
     In various embodiments, the decision management system  102  may use a business rule, which may be defined using the application server  110 , to develop a set of relevant questions to query a user and obtain information needed to resolve the business rule.  FIGS. 2 and 3  generally describe systems and processes that may perform such tasks. In some embodiments, processes are implemented as instructions on computer-readable medium. 
       FIG. 2  is a block diagram of processing modules  200  of the decision management system  102  shown in  FIG. 1 , according to various embodiments. The processing modules  200  include a first module  202  to access a business rule, a second module  204  to deconstruct the business rule into a condition and an associated action, a third module  206  to determine a set of questions relevant to the condition, a fourth module  208  to place the set of questions into a question queue, a fifth module  210  to order the question queue, and a sixth module  212  to present the question queue to a user. 
     The first module  202  accesses a business rule. In an embodiment, the business rule is accessed via the application server  110 . For example, a user (e.g., a business rules administrator) may use a software application to define and manage business rules. In general, a business rule may be constructed using one or more conditions and one or more resulting actions. For example, in an insurance underwriting context, a business rule may be “if applicant age&gt;18 and applicant smoker=no, then pre-approve=true”. This example includes a compound condition (e.g., the applicant&#39;s age must be over eighteen and the applicant must be a non-smoker), which must evaluate to TRUE for the resulting condition to occur (e.g., the applicant is pre-approved for insurance). Business rules may vary in complexity. For example, rules may be dependent on each other, rules may be nested, or rules may use advanced comparison operations, such as selection from lists, sub-string searches, or regular expression tests. 
     The second module  204  deconstructs the business rule into a condition and an associated action. In an embodiment, the condition comprises a compound condition. One or more conditional statements may be used to describe a business rule (e.g., if-then constructs, if-then-else constructs, if-then-elseif constructs, switch or case constructs, or the like). The business rule may be deconstructed into several conditions and/or several associated actions. 
     The third module  206  determines a set of questions relevant to the condition. As a continuing example, a question relevant to the business rule illustrated above may be “How old are you?” or “Are you over the age of 18?” Additional questions may be “Are you a smoker?” or “Have you ever smoked or used tobacco products?” How the question is phrased may be determined by several factors, such as an anticipated use of the information in the future, for example, a more general question of “How old are you?” or “What is your birth date?” may result in more useful information that can be reused as opposed to a simpler question of “Are you over the age of 18? In addition, the question may be phrased in a particular way to reflect a business policy or risk policy. In the example illustrated, the underwriters may wish to know whether the applicant has ever used a tobacco product as that may provide more insight on the applicant&#39;s insurability than if they are a current smoker, or vice versa. 
     The fourth module  208  places the set of questions into a question queue. The question queue may be a list of questions (e.g., a text file) or an organization of structured data (e.g., a table in a database). The question queue may be implemented in computer memory, such as by using a programmed data structure (e.g., a linked list, queue, array, tree, or other such data structure). As an example, a business rule may contain a conditional statement that is deconstructed into five conditions by the second module  204  and translated to five questions by the third module  206 . Each question may then be stored in a question queue implemented as a linked list by the fourth module. 
     The fifth module  210  orders the question queue. In an embodiment, the fifth module is configured to order the question queue using a dependency between a first question and a second question in the question queue. For example, dependencies may be based on business rules or policies, organizational rules, logical progression, or question scope. As an example, if a particular type of insurance is only offered to senior citizens (e.g., people age 65 and older) then other questions associated with additional conditions in a business rule may be inapplicable once the applicant&#39;s age is determined. Thus, an inherent dependency may exist in a business rule when represented as a compound conjunctive Boolean statement. As an alternative example, in a compound disjunctive Boolean statement, fewer or no dependencies may be present. Other types of dependencies may be used, alone or in combination with dependencies described, to order the question queue. In an embodiment, the fifth module is configured to order the question queue by ordering questions from a generally broadest scope to a generally narrowest scope. For example, when screening applicants for an insurance or other financial product, questions may be ordered in such a manner to dispose of unqualified applicants in the most efficient manner (e.g., presenting questions that may disqualify the largest pool of typical applicants before presenting other questions). 
     The sixth module  212  presents the question queue to a user. The questions in the question queue may be presented one at a time (e.g., from the beginning of the queue and moving toward the end) or more than one at a time. For example, when separate lines of questions may be determined from all the questions in the question queue, multiple questions may be presented to make the inquiry process more efficient. As an example, if the questions in a question queue include questions related to both an applicant&#39;s residence and an applicant&#39;s prior driving record, with several questions associated with each topic, the sixth module  212  may present non-dependent questions for each topic to a user at the same time. 
     In a further embodiment, processing modules  200  may include a seventh module to receive a response from the user, an eighth module to determine a subsequent question using the response, and a ninth module to present the subsequent question. After a user answers a question, the processing modules  200  may validate the answer (e.g., performing a constraint check, a sanity check, or checks based on business rules or expected replies). The eighth module may then obtain the next question from the question queue. As described above, the next question may be dependent on the question asked. In such a case, the business rule (conditional statement) may be evaluated after each question is presented and answered. This type of operation may short-circuit the evaluation process and make the resulting decision available to the user quicker. 
     In a further embodiment, processing modules  200  may include a tenth module to store the question queue and an eleventh module to display the question queue using a tree graph representation. For example, a tree graph representation may incorporate each question as a node in the graph and the possible answers for each question as edges connecting nodes. If there are dependent questions (nodes) then they may be represented as descendent nodes connected by a particular edge that represents the answer to the ancestor node that would navigate a user to that particular question in the descendent node. In an embodiment, the tree graph representation comprises a plurality of tree graphs. For example, when there are multiple independent groups of questions, then these questions may be represented separately. 
       FIG. 3  is a flowchart illustrating a method  300  according to various embodiments. At  302 , a business rule is accessed. At  304 , the business rule is deconstructed into a condition and an associated action. In an embodiment, the condition comprises a compound condition. At  306 , a set of questions relevant to the condition is determined. At  308 , the set of questions is placed into a question queue. At  310 , the question queue is ordered. In an embodiment, the question queue is ordered using a dependency between a first question and a second question in the question queue. In an embodiment, the question queue is ordered from a generally broadest scope to a generally narrowest scope. At  312 , the question queue is presented to a user. In a further embodiment, a response is received from the user, a subsequent question is determined using the response, and the subsequent question is presented to the user. In a further embodiment, the question queue is stored and then displayed using a tree graph representation. In an embodiment, the tree graph representation comprises a plurality of tree graphs. 
     In various embodiments, the decision management system  102  may use a decision tree that reflects a business rule when presenting questions to a user.  FIGS. 4 and 5  generally describe systems and processes that may perform such tasks. In some embodiments, processes are implemented as instructions on computer-readable medium. 
       FIG. 4  is a block diagram of processing modules  400  of the decision management system  102  shown in  FIG. 1 , according to various embodiments. The processing modules  400  include a first module  402  to receive a request from a user, a second module  404  to determine a subject of the request, a third module  406  to use the subject to obtain a set of relevant questions, a fourth module  408  to determine, for each question in the set of questions, whether an answer to a current question is available in a storage area, and a fifth module  410  to present the current question to the user when the answer to the current question is not available in the storage area. 
     The first module  402  receives a request from a user. As an illustrative example, a user may interface with the business decision management system  102  using a client computer  104 . A web page, or other dynamic content, may be presented to the user, for example, via the web server  108 , application server  110 , database management server  114 , or file server  118 , either alone or in combination. The user may be presented with pre-formed questions (e.g., using a dropdown list) or may be enabled to enter a question of their own (e.g., using a text input field). 
     The second module  404  determines a subject of the request. By appropriately parsing a submitted question, the second module  404  may extract the subject of the request. For example, a request of “I would like to add my daughter to my health insurance?” may be reduced to a subject of “adding a minor to a health insurance policy.” In various examples, the request may be a statement reflecting an intent or directive of a user or a question from the user. In some cases, there may be more than one subject in a request or more than one request containing at least one subject. For example, the request may contain “I would like to add my daughter as a beneficiary to my life insurance and increase my policy to $100,000.” Here, the two subjects may be represented as “adding a beneficiary to a life insurance policy” and “changing the coverage of a life insurance policy.” In such cases, the second module  404  may attempt to determine priority of requests or may simply query the user which request they would like to address first. In other examples, the second module  404  may continue processing each request-subject pair and make them accessible to the subsequent modules described below. 
     The third module  406  uses the subject to obtain a set of relevant questions. As an example, a subject of a request may be related to a business rule. To continue the previous example related to health insurance, a business rule may exist that can be represented as: “if health insurance plan=family policy, then dependent coverage”. Other business rules may also exist that reflect the type of policies and their permitted use, the number of dependents in a family health policy, permitted previous health conditions and other conditions for coverage, and the like. To derive an appropriate set of relevant questions, the third module  406  may use related business rules to determine what information is needed to resolve the business decisions reflected in the related business rules. For example, in this situation, the type of policy that the policy-holder currently has is an important piece of information to ascertain. According to other business rules, the age of the person being added, their prior health history, their current health status, and other factors may be needed to fully assess the potential beneficiary before coverage may be offered. In an embodiment, the set of relevant questions is organized as a decision tree. For example, in some situations, such as in an insurance policy approval process, some answers may preclude others from being used or asked. The dependency between questions may be represented as a tree, where each node in the tree represents a question or a terminal state and each edge represents an answer to an ancestor question node to a descendent question node or a descendent terminal node. Terminal nodes (leaf nodes) may represent a final disposition of an initial query, which may be positioned as the root node. 
     The fourth module  408  determines, for each question in the set of questions, whether an answer to a current question is available in a storage area. The determination may be performed in a batch mode, for example, to obtain available answers for every relevant question, or in a series mode, obtaining answers to questions just prior to the question being presented (e.g., using the fifth module  410 ). Each mode may be more efficient or more practical than the other depending on the situation. For example, using the batch mode may only require using a single database connection. Once the data is retrieved, the database connection may be closed and any memory structures may be freed or released. On the other hand, in a series of questions, it may be faster to query a database for each question presented as needed than it would be to obtain results for every possible question to be presented. The design of the access and retrieval may also be a hybrid and use network response conditions, user experience, network load, system load, processor performance, or other metrics to automatically or semi-automatically shift from one mode to the other. 
     The fifth module  410  presents the current question to the user when the answer to the current question is not available in the storage area. In an example, the current question is retrieved from a data store (e.g., the decision management database  116 ). The question may be stored using an index or other identifier. The question may be formatted using a standardized interface language (e.g., eXtensible Markup Language (XML)). For example, a question may be formatted using XML and include the question string in a &lt;question&gt; block and the format of the answer input (e.g., radio button, check box, text input field, dropdown list, or the like) with associated labels or values in an &lt;answer&gt; block. Using a standardize interface language to store questions in a formatted manner may have advantages, such as cross-platform compatibility or dynamic implementation at the presentation layer. 
     In a further embodiment, the processing modules  400  include a sixth module to receive a response to the current question from the user and a seventh module configured to store the response in the storage area as the answer to the current question. As questions are presented and answered, the answers may be stored for later reference. In doing so, during later requests, the business decision management system  102  may perform fewer user-interrogations before ascertaining a final disposition of a user request. 
     In a further embodiment, the processing modules  400  include an eighth module configured to present a subsequent question to the user when the answer to the current question is available in the storage area. Skipping over questions where the answers are already available gains efficiencies in several ways—for example, the user is not burdened answering the same question for different requests and the system is not burdened by having to present redundant questions. In some cases, when the answer is found to be available in the storage area, the user may be presented with the stored answer and an opportunity to confirm or modify the stored answer to correct or discard it. For example, as a later step, the user may be presented with a summary page of information either asked contemporaneously or retrieved from storage to be used to determine the final disposition of the request. 
     In a further embodiment, the processing modules  400  include a ninth module configured to use a set of answers corresponding to the set of relevant questions to resolve the request. For example, after the answers are obtained or retrieved, the conditional statement in the associated business rule may be evaluated. In an embodiment, the request is related to an underwriting decision. For example, the request may be related to life insurance, health insurance, car insurance, or other types of insurance products. The request may be related to adding or removing beneficiaries, modifying coverage amounts, changing the term (e.g., in a term life policy), adding or removing a vehicle or coverage on a vehicle, or the like. 
     In a further embodiment, the processing modules  400  include a tenth module to present a subsequent question to the user by traversing the decision tree, when the answer to the current question is available in the storage area. 
       FIG. 5  is a flowchart illustrating a method  500  according to various embodiments. At  502 , a request is received from a user. At  504 , a subject of the request is determined. At  506 , the subject is used to obtain a set of relevant questions. In an embodiment, the set of relevant questions is organized as a decision tree. For each question in the set of relevant questions, at  508 , whether an answer to a current question is available in a storage area is determined and if not, then at  510  the current question is presented to the user. In a further embodiment, a response to the current question is received from the user and the response is stored in a storage area as the answer to the current question. In a further embodiment, a subsequent question is presented to the user when the answer to the current question is available in the storage area. In a further embodiment, a set of answers corresponding to the set of relevant questions is used to resolve the request. In an embodiment, the request is related to an underwriting decision. In a further embodiment, a subsequent question is presented to the user by traversing the decision tree, when the answer to the current question is available in the storage area. 
     Embodiments using examples of insurance are described, however, systems and methods described herein may be used to dynamically present questions associated with business rules related to any type of business, such as banking services, financial services, customer service, technical support, or other decision support systems. 
     While  FIGS. 2-5  illustrate embodiments in which a user may interact with a decision management system  102 ,  FIGS. 6 and 7  generally describe systems and processes that provide an indication of progression through an automated or semi-automated process, such as those described above. In some embodiments, processes are implemented as instructions on computer-readable medium. 
       FIG. 6  is a block diagram of processing modules  600  of the decision management system  102  shown in  FIG. 1 , according to various embodiments. The processing modules  600  include a first module  602  to access a decision tree, a second module  604  to determine a current node of the decision tree, a third module  606  to determine an estimated number of nodes between the current node and a leaf node, and a fourth module  608  to present a representation using the estimated number of nodes in the user-interface. 
     The first module  602  accesses a decision tree. In an embodiment, the decision tree is organized using a first question as a root node and a plurality of terminal questions as leaf nodes. A terminal question, in an example, may be the last question in a series of related questions. 
     The second module  604  determines a current node of the decision tree. In an example, the default node used is the root node. In an embodiment, the current node corresponds with a current question being presented to a user in a user-interface. 
     The third module  606  determines an estimated number of nodes between the current node and a leaf node. For example, a tree traversal process may be used (e.g., breadth-first or depth-first traversal) and a record may be kept of the deepest leaf node (e.g., the leaf node farthest from the current node or the root node). 
     In an embodiment, the third module is further configured to determine the estimated number of nodes between the current node and the leaf node by: determining a maximum number of edges to a farthest node from the current node; determining a minimum number of edges to a nearest node from the current node; and averaging the maximum and minimum number of edges. The farthest node may be a terminal node. In an example, the farthest node is the farthest node in a particular branch of the decision tree where the root of the branch is defined by the current node. 
     In an embodiment, the third module is further configured to determine the estimated number of nodes between the current node and the leaf node by: determining a most probabilistic path from the current node to a most probabilistic leaf node; and counting the number of edges between the current node and the most probabilistic leaf node. 
     The most probabilistic path may be determined by analyzing previous user responses to determine a most likely answer to each node (question) in the decision tree and obtaining a most likely path through the tree from a given node. In an embodiment, the third module is further configured to determine the most probabilistic path by: accessing a database of user responses to the question corresponding to the current node; determining a most popular response; traversing the decision tree using the most popular response; and performing the accessing, determining, and traversing on subsequent interior nodes until a leaf node is reached. 
     Other information may be used to determine the probability of an answer for a given question (node), such as demographic data of the user. For example, it may be determined that a user of a particular age with a particular income may be more or less likely to be interested in a particular investment product (e.g., an aggressive mutual fund versus a conservative money market account). In an embodiment, the third module is further configured to determine the most probabilistic path by: accessing a database of demographic data; determining a most likely response using the demographic data; traversing the decision tree using the most likely response; and performing the accessing, determining, and traversing on subsequent interior nodes until a leaf node is reached. 
     The fourth module  608  presents a representation using the estimated number of nodes in the user-interface. The representation may include the number of nodes already visited along with the number of estimated nodes. In such a presentation, the user would be aware of how many steps they have completed with an estimate of how many steps remain in a current interview. 
     In a further embodiment, the processing modules  600  include a fifth module to traverse the decision tree to a subsequent node after the current question is answered, a sixth module to increment a counter representing the number of nodes visited, and a seventh module to decrement a counter representing an estimated number of nodes remaining. 
     In a further embodiment, the processing modules  600  include a module to traverse the decision tree to a subsequent node using data from a data source, a module to increment a counter representing the number of nodes visited, and a module to decrement a counter representing an estimated number of nodes remaining. As a user answers additional questions, the number of nodes visited will increase linearly and similarly, the number of nodes remaining may decrease linearly. However, this may not be so in a practice as the user moves through the decision tree. For example, after a user answers a particular question associated with a node, a larger branch of possible nodes may be avoided when a particular answer is obtained, leaving the user with a smaller branch of possible nodes and resulting in a reduced number of possible steps remaining in the interview. To address this type of situation where a user&#39;s answer affects changes the topology of the decision tree that may be subsequently visited, the following embodiments are described. 
     In a further embodiment, the processing modules  600  include an eighth module to traverse the decision tree to a subsequent node using data from a data source, and a ninth module to determine an estimated number of nodes between the subsequent node and a leaf node. For example, when a user&#39;s data is already available in the business decision management system  102 , the question need not be presented and an answer need not be received from the user. The traversal of the decision tree may be accomplished without user assistance (automatically). 
     In a further embodiment, the processing modules  600  include a module to traverse the decision tree to a subsequent node after the current question is answered, and a module to determine an estimated number of nodes between the subsequent node and a leaf node. 
       FIG. 7  is a flowchart illustrating a method  700  according to various embodiments. At  702 , a decision tree is accessed. In an embodiment, the decision tree is organized using a first question as a root node and a plurality of terminal questions as leaf nodes. At  704 , a current node of the decision tree is determined. In an embodiment, the current node corresponds with a current question being presented to a user in a user-interface. At  706 , an estimated number of nodes between the current node and a leaf node are determined. 
     In an embodiment, determining the estimated number of nodes between the current node and the leaf node comprises: determining a maximum number of edges to a farthest node from the current node; determining a minimum number of edges to a nearest node from the current node; and averaging the maximum and minimum number of edges. 
     In an embodiment, determining the estimated number of nodes between the current node and the leaf node comprises: determining a most probabilistic path from the current node to a most probabilistic leaf node; and counting the number of edges between the current node and the most probabilistic leaf node. 
     In an embodiment, determining the most probabilistic path comprises: accessing a database of user responses to the question corresponding to the current node; determining a most popular response; traversing the decision tree using the most popular response; and performing the accessing, determining, and traversing on subsequent interior nodes until a leaf node is reached. 
     In an embodiment, determining the most probabilistic path comprises: accessing a database of demographic data; determining a most likely response using the demographic data; traversing the decision tree using the most likely response; and performing the accessing, determining, and traversing on subsequent interior nodes until a leaf node is reached. 
     At  708 , a representation using the estimated number of nodes in the user-interface is presented. 
     In a further embodiment, the decision tree is traversed to a subsequent node after the current question is answered, a counter representing the number of nodes visited is incremented, and a counter representing an estimated number of nodes remaining is decremented. 
     In a further embodiment, the decision tree is traversed to a subsequent node using data from a data source, a counter representing the number of nodes visited is incremented, and a counter representing an estimated number of nodes remaining is decremented. 
     In a further embodiment, the decision tree is traversed to a subsequent node using data from a data source and an estimated number of nodes between the subsequent node and a leaf node is determined. 
     In a further embodiment, the decision tree is traversed to a subsequent node after the current question is answered and an estimated number of nodes between the subsequent node and a leaf node is determined. 
     Hardware and Software Platform 
       FIG. 8  is a block diagram illustrating a machine in the example form of a computer system  800 , within which a set or sequence of instructions for causing the machine to perform any one of the methodologies discussed herein may be executed, according to various embodiments. In alternative embodiments, the machine may comprise a computer, a network router, a network switch, a network bridge, Personal Digital Assistant (PDA), a cellular telephone, a web appliance, set-top box (STB) or any machine capable of executing a sequence of instructions that specify actions to be taken by that machine. 
     The computer system  800  includes a processor  802 , a main memory  804  and a static memory  806 , which communicate with each other via a bus  808 . The computer system  800  may further include a video display unit  810  (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system  800  also includes an alphanumeric input device  812  (e.g., a keyboard), a cursor control device  814  (e.g., a mouse), a disk drive unit  816 , a signal generation device  818  (e.g., a speaker) and a network interface device  820  to interface the computer system to a network  822 . 
     The disk drive unit  816  includes a machine-readable medium  824  on which is stored a set of instructions or software  826  embodying any one, or all, of the methodologies described herein. The software  826  is also shown to reside, completely or at least partially, within the main memory  804  and/or within the processor  802 . The software  826  may further be transmitted or received via the network interface device  820 . 
     For the purposes of this specification, the term “machine-readable medium” or “computer-readable medium” shall be taken to include any medium which is capable of storing or encoding a sequence of instructions for execution by the machine and that cause the machine to perform any one of the methodologies. The terms “machine-readable medium” or “computer-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic disks, and other temporary, transient, or permanent storage means, such as an executable streaming downloadable program. Further, it will be appreciated that the software could be distributed across multiple machines or storage media, which may include the machine-readable medium. 
     Method embodiments described herein may be computer-implemented. Some embodiments may include computer-readable media encoded with a computer program (e.g., software), which includes instructions operable to cause an electronic device to perform methods of various embodiments. A software implementation (or computer-implemented method) may include microcode, assembly language code, or a higher-level language code, which further may include computer-readable instructions for performing various methods. The code may form portions of computer program products. Further, the code may be tangibly stored on one or more volatile or non-volatile computer-readable media during execution or at other times. These computer-readable media may include, but are not limited to, hard disks, removable magnetic disks, removable optical disks (e.g., compact disks and digital video disks), magnetic cassettes, memory cards or sticks, random access memories (RAM&#39;s), read only memories (ROM&#39;s), and the like. 
     Such embodiments of the inventive subject matter may be referred to herein individually or collectively by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept, if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. For example, one module may be implemented as multiple logical modules, or several modules may be implemented as a single logical module. As another example, modules labeled as “first,” “second,” and “third,” etc., may be implemented in a single module, or in some combination of modules, as would be understood by one of ordinary skill in the art. 
     In the foregoing Detailed Description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the invention require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate preferred embodiment. 
     In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. 
     The Abstract is provided to comply with 37 C.F.R. § 1.72(b), which requires that it allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.