Resultra is a relatively general purpose, collaborative application for gathering, tracking and analyzing itemized business information. Such information can include action items, project tasks, customer leads, customer surveys, customer issues, employment applications and the like.
Resultra originates from the concept of “rule-based, discretionary” (RBD) trading; yes, RBD is actually a term from stock market trading. RBD is a type of trading where traders generally follow a consistent set of rules, but there is also discretion to override and supplement these rules with personal priorities, biases, observations, experience and intuition. Many RBD traders also start with similar rules, but inevitably customize and add to these rules to match their own trading style.
So what does RBD have to do with tracking project tasks, customer issues, and other non-trading information? When managing a RBD stock market trade, traders are really just making a sequence of business decisions from the start to finish of the trade. These decisions can be supported and driven by any combination of:
If you think about it, the same type of information needs to be gathered and tracked for many other types of business information and a similar type of workflow can be used. In other words, RBD is really just a way to organize and track information, and RBD gives Resultra a consistent look and feel.
Many other project tracking and similar applications organize and present information in a fixed or pre-defined manner. With Resultra, you'll typically start with a basic template, then customize tracking to your own preferences. For example:
Resultra's settings pages provide a great deal of flexibility. However, once the settings are configured, they are hidden from view and will not distract you during day-to-day use of the application.
Secondly, the application can also be configured differently for different tasks or people who collaboratively use the application. Depending on the different roles a given tracker uses for different collaborators, different users will see more or less information. Similarly, depending on the task at hand, different forms or table views can be used to view and edit items' information.
Preventing information overload and minimizing clutter for day-to-day usage of the application is important. The goal is to “stay in the pocket” and focus on the data itself, rather than settings and buttons to configure the application or information which is irrelevant to the task at hand.