OpCo Product Team - December 2023 Update

A summary of design & development activity and KPIs for the OpCo product team in December 2023.

Team updates

  • Anastas has returned from paternity leave.


In December most of the team took the last two weeks of the month as holidays, so the majority of the work was done in the first two weeks. The focus was primarily on the V3 app pool action flows, i.e. adding and removing liquidity. We are re-architecting these flows to be as flexible as possible so that they support v2 and v3 pools. The new architecture should also allow us to easily adapt and support any future pool types that result from Balancer protocol v3. Additionally, further work was completed on the pool list and pool detail page bringing them closer in line with designs.


Below is a high-level list of design activities in December.

  • Theme exploration for the new V3 web app.
  • Refining the UX/UI design for core pages and flows.
  • Setting up new master Figma file with local variables, styles and components to work across light and dark modes.
  • Collaborating with frontend devs to implement new UI designs.


= 1 - (‘fatal’ errors / total successful txs)

Where ‘fatal’ is a label applied to errors recorded in a transaction flow, and total successful txs are recorded via analytics events.


  • Ad blockers prevent error recording and analytics.
  • Some % errors are user/wallet-controlled errors that we haven’t excluded yet.
  • Total fatal errors: ~7,838 (prev. 6,222)
  • Total successful txs: ~109,374 (prev. 109,697)

This KPI has worsened slightly since last reported in November at 94.3%. This decrease can be attributed to an issue with the swap UI causing higher than usual “UNPREDICTABLE GAS LIMIT” errors. We are investigating this issue and will hopefully have it fixed or greatly reduced in early January. We will continue to monitor and fix failed transaction issues to get this KPI as close to 100% as possible.

Avg. time on site (30d): 1:58 (-0.02s)

Note, that the Average Time on Site metric can be influenced by market conditions. For instance, we observe an increase in time spent on the site when the market is on the rise.

Taken from this article about what makes a good NPS score: “If your NPS is higher than 30, that would indicate that your company is doing great and has far more happy customers than unhappy ones.”.

As can be seen in the general trend chart above the NPS score has remained fairly constant at around the 50-60 level with a slight drop in December which could also potentially be attributed to the swap UI issue explained in the previous KPI.

Full results:

Lighthouse is reporting a slight improvement in our performance metric, up from 80 in November. We don’t believe this is the result of any significant changes we have made and must be related to a change in how Lighthouse is measuring performance. The performance of the home page is similar or exactly the same as last month.

Note, Lighthouse scores can be relatively unreliable. However, for our purposes, they serve as useful benchmarks by highlighting any significant issues or improvements that may have been introduced.