Equities Dashboard
Evolving a public equities dashboard around the realities of an emerging stock market.
The Dominican Republic's equities market was still taking shape. As new listed companies entered the market, BVRD needed to evolve an existing dashboard into a clearer and more scalable way for investors and market participants to understand prices, trading activity and market behavior.
- Organization
- Bolsa de Valores de la República Dominicana
- Year
- 2024
The current dashboard
A public instrument view bringing together price, market depth, trading activity, participants and historical behavior.
- Price
- Market
- Activity
- History
01 Market context
A dashboard for a market that was still taking shape
The first BVRD equities dashboard emerged alongside the arrival of the first publicly traded stock in the Dominican market. The platform gave the public a dedicated place to follow the instrument, understand its latest price and explore its trading activity.
As the product was used in real conditions, new needs began to emerge. Requirements and feedback received by BVRD from securities brokerages and end users, together with limitations in the existing experience, shaped a second version.
- Market
- Emerging equities market
- Users
- Public + market participants
- Product
- Public market information
- Evolution
- V1 → feedback → V2
02 What V1 taught us
The first version exposed new needs
The first version established the foundation of the product, but real-world use revealed limitations that became more relevant as the equities market evolved.
Some parts of the interface presented fragmented visual hierarchy or inconsistent behaviors. Others dedicated considerable space to information whose value could be limited depending on the actual activity and liquidity of the market.
At the same time, requirements received from securities brokerages and end users created new expectations around what the dashboard needed to communicate.
The challenge was not simply to modernize the interface. It required reconsidering which information deserved attention, what could be simplified and how market data should be organized for a public audience.
Two ways of deciding what to show
-
What we could assume
- More market data
- More indicators
- More information
-
What real use revealed
- Relevant market data
- Clearer priorities
- Information aligned with actual liquidity
What should the dashboard show when more data doesn't necessarily mean more useful information?
03 Product thinking
Designing for the market we actually had
V2 needed to balance incoming requirements with the actual usefulness of each data point within the context of the local market. The question was not how much we could show, but which information genuinely helped users interpret the instrument and its activity.
That meant questioning elements inherited from V1, considering how frequently meaningful data would actually exist and allocating interface space according to information relevance rather than simply its availability.
04 Information hierarchy
The hierarchy needed to answer questions, not show more data
V2 reorganized the experience around a clearer progression from instrument identity to current market state and historical behavior.
Instead of treating every dataset as equally important, the interface establishes layers: security information provides context, current pricing communicates the immediate market state, brokerage activity adds participation context, and historical data helps users understand behavior over time.
- 01
What am I looking at?
Instrument and context
- 02
What is happening now?
Latest price and market status
- 03
How is the market positioned?
Bid, ask and depth
- 04
Who is participating?
Activity and securities brokerages
- 05
How has it evolved?
Price, volume and history
05 V1 → V2
Evolution, not a cosmetic redesign
The second version was not approached as a simple visual refresh. It was an opportunity to reconsider the product after its first stage of real-world use and prepare the experience for a broader equities market.
-
Product
Requirements and real-world feedback helped define what remained, what changed and what could be removed.
-
Information
The hierarchy evolved around the data that genuinely helped users understand the instrument and its activity.
-
Implementation
The experience was implemented as a responsive front end, with visualization libraries evaluated and integrated to appropriately represent market information.
06 Outcome
Designing for the reality of the market
V2 turned the learnings from the first version into a clearer experience aligned with the actual characteristics of the market. Rather than expanding the dashboard by accumulating information, the evolution focused on prioritizing what helped users interpret the instrument, its activity and its context.