Typical Problems Solved by
didi’s Interface Design Methodologyg

This list of common concerns may sound familiar. They are not a natural part of the financial technology development process. They are symptoms of an inappropriately low investment in the training and time needed for proper interface design.

Cognitive Engineering leverages the knowledge and practices of a distinct and well-developed discipline that is rarely represented in typical financial user/analyst/developer system specification teams. Plugging that gap directly addresses and solves many problems.

Business-side / IT developer relations are typically improved, allaying these issues

  1. After a financial system is coded it needs major revisions before it can be used by business people (an embarrassingly large fraction of projects are just terminated)
  2. Business people are frustrated because the technology group doesn’t seem to understand the business needs
  3. Developers are frustrated that they are constantly re-writing code based on changing specifications

Mapping cognitive business workflow to system design eases these frustrations

  1. Business people find it hard to switch from another firm’s system
  2. Business people blame the system for errors or inefficiency
  3. Business people feel frustrated that a seemingly simple operation is difficult to execute in the system
  4. It is not possible to accomplish a simple business goal without several systems
  5. It is hard to find where in the system one needs to go to accomplish something

Sophisticated information layering simplifies & clarifies, addressing these problems

  1. Important business events (alerts, errors, opportunities) are missed even though the information is in the system
  2. Screens looks too busy, or complicated; there is “information overload”
  3. It is hard to find certain information on a screen even though it’s there
  4. One needs to go to another screen or system for information in the middle of a task in order to complete it
  5. Unnecessary information is displayed

System complexity can be tamed by combining design and prototype walk-throughs

  1. Clients need help understanding how to use a screen
  2. Clients take business elsewhere because screens are hard to use
  3. Clients ask for “additions” that are already a part of the system
  4. Business people need paper “cheat sheets” to accomplish tasks

At didi we’re happy to meet with you to address these issues with respect to your own specific projects. We can detail exactly how our design methodology can reduce or eliminates them—it is not a mystery, or personality-based talent, but a straight-forward, teachable process.