— Olympus is a protocol on the Ethereum blockchain with the goal of establishing OHM as a crypto-native reserve currency. It conducts autonomous and dynamic monetary policy, with market operations supported by the protocol-owned Olympus Treasury. OHM serves a need in the market gap between fiat stable coins and volatile crypto assets, providing relative stability and scalability underpinned by the protocol’s Range Bound Stability (“RBS”) system. RBS is the flagship system of Olympus’ autonomous monetary policy.

Project site:
2 wireframes facing inward. Left is the home screen. Right Profile page

Year / Platform

2022 / web3

Team Role

Design Lead

Team steward - 0xtutti
Developer - Girth
Project manager - Emon



Navigating the intricate framework of Olympus, I encountered the challenge of simplifying the Bonds feature while assuming the role of the Internal Bonding Design Lead. With previous contributions scattered and limited communication channels with the lead developer, I had to overcome hurdles to streamline the Bonds dashboard. The task included refining processes such as bonding, asset visualization, distinguishing between fixed and variable bonds, and optimizing fund withdrawals. Balancing the intricacies of Olympus' abstract structure with the need for user-friendly functionality posed a significant design challenge that I was determined to conquer.

Value Proposition

Enabling the seamless onboarding of the first billion individuals into the realm of web3 is a shared aspiration, yet achieving this milestone remains elusive. Within the Olympus ecosystem, the foundation's financial sustenance is rooted in users staking their assets within bonds.

By optimizing and simplifying this process, value is bestowed upon both users and the protocol itself. The impressive trajectory of Olympus since its inception is evidenced by its remarkable growth within the cryptocurrency domain. Notably, the OHM Token has yielded substantial returns for its early backers throughout the dynamic landscape of 2021.
Seamless Bonding
Large Community
web3 based

User Profile

Introducing the (3,3): A dedicated member of the global Olympus protocol community, this individual embodies the values of hodling and envisions Olympus (Oly) as the quintessential reserve currency for the web3 era. Balancing financial gains with enjoyment, their primary objective revolves around profitable investment while relishing the journey. Possessing a solid understanding of the crypto realm, the intricacies of inverse bonding remain a puzzle, much like for many others. While not actively seeking withdrawals, they eagerly seek opportunities to contribute further and remain at the forefront of Olympus DAO's upcoming developments.

Notably, their investment strategy is centered on accumulating OHM (the token), reflecting a preference for OHM acquisition over direct bonding. This user paints a vivid picture of Olympus' global community: passionate, forward-looking, and committed to the principles of accessibility and inclusivity.
Upon delving into our research, a striking revelation emerged: a staggering 80% of Olympus's user base had yet to venture into the realm of bonding. This discovery was a wake-up call, highlighting a significant gap between user awareness and actual engagement. Not only were users refraining from bonding, but many were oblivious to its very existence within the ecosystem.



Addressing this challenge, I embarked on streamlining the bonds dashboard while recognizing the need to collaborate with the marketing department to illuminate this hidden gem. Yet, this endeavor faced headwinds due to the volatile nature of the crypto landscape, causing substantial shifts within the organization.

Navigating this intricate landscape, the pillars of our design efforts—Bonding, Grants, External Bonds, Design Systems, and Homepage—stood as the cornerstones, each entrusted to a dedicated lead. Amid this multidimensional orchestration, I stood at the helm, coordinating the symphony of strategies. Amidst this, a critical migration from sOHM to gOHM was underway, encapsulating the dynamic nature of our mission and the tumultuous currents of innovation shaping the backdrop.

Original Bonding Dashboard (Below)
Upon my initiation into the realm of V2 bonding, I was presented with a pivotal task – to delve into two enlightening Medium articles that would serve as my guiding star. Articles below:
Introducing V2 Bonds
Olympus V2 Migration - Explained

Equipped with the insights garnered from these resources, I embarked on an intricate journey of assembling a comprehensive catalog of essential features and potential upgrades. This compilation stood as a roadmap, charting the course for our evolutionary design voyage.

The next phase saw a crucial convergence between my vision and the mastermind behind the V2 bonding experience, the lead designer and creator. In a pivotal meeting, we engaged in a meticulous exploration of the feature landscape. It was here that the art of prioritization came to the forefront, as we thoughtfully evaluated each feature's potential impact. Recognizing the significance of a coherent user experience, we arrived at the strategic decision to deprioritize certain features. Our rationale was rooted in the desire to ensure that the core functionalities were robustly established before venturing into the realm of additional enhancements.

List after meeting (Below)
With the agreed-upon feature list in hand, the transition from the discovery phase to the ideation phase was fluid and purposeful. Armed with a comprehensive understanding of user pain points and aspirations, I embarked on the journey of generating innovative solutions.


Version 1-2

Following a series of engaging discussions with the team, we collectively unraveled numerous challenges that had surfaced. The iterative process of hashing out these issues underscored the value of collaborative dialogue, where diverse perspectives from various departments converged to shape a comprehensive solution. This back-and-forth exchange of insights not only bolstered our problem-solving capabilities but also fostered a culture of cross-functional understanding and cooperation.

With meticulous attention to detail, we diligently tackled every item on the list of concerns. However, in our pursuit of perfection, a few nuanced aspects beckoned for further refinement. I seized the opportunity to contribute my insights and recommendations, advocating for adjustments that would elevate the overall user experience. By expressing these observations, I aimed to ensure that the final design not only addressed immediate pain points but also anticipated and mitigated potential obstacles that users might encounter. We addressed all the issues on the list but still needed to tweak things a bit.

I expressed a few below:

Blue Banner Idea

In the first version the idea of just indicating bonds as a banner was a success across the team. However the colors for blue was being used for other purposes.

Modal Bonding Debate

The previous designer of the bonds dashboard expressed some concerns about the limited space for modals. We settled on not lengthening past a certain height.

Too Many Steps

There we're at least 4 steps in the bonding process. Identify, Review, Authorize, Bond. We reduced to 3 but we're brainstorming how to cut down more.
Within the realm of bonding, my focus centered on simplifying the user journey. At this point we'd only addressed the teams concerns but not the users.

This involved a strategic reduction in the proliferation of authorization widgets, coupled with the incorporation of a new section above available bonds – a space dedicated to showcasing users' ongoing active deposits. This initiative directly addressed a significant user pain point, eliminating the uncertainty surrounding the status of their bonds and the absence of visibility on when, where, and the number of active bonds.


Final Version

Ultimately, our journey led us to a pivotal juncture where the transition of assets into the newly introduced gOHM demanded meticulous consideration. To streamline this process, we took the decisive step of eliminating the "Get Started" prompt, replacing it with a seamless feature enabling users with multiple bonds to effortlessly claim all associated assets. This enhancement not only simplified user interactions but also brought us closer to a more cohesive and user-friendly experience.

Within the organization, a spirited debate ensued surrounding the dilemma of sOHM versus gOHM, casting a significant shadow over our progress. The discourse revolved around the retention of older V1 bonds, as preferences were deeply divided. After careful deliberation, a consensus emerged that the inclusion of these legacy bonds would cater to diverse user needs. This strategic decision marked a critical turning point, showcasing our commitment to embracing versatility and catering to users' evolving requirements.

As the discussions matured and the design direction solidified, my role transitioned to the design migration team. The culmination of our design efforts paved the way for the adoption of these refined designs by the development team. This harmonious convergence of design and execution underscored the collaborative spirit and collective dedication driving the Olympus DAO project forward.
My core contributions revolved around these 4 concepts:
1. Instantaneous Profitability Insights: Enabling users to swiftly identify the most profitable bonds in real-time, providing a clear path to optimized decisions.  
2. Effortless Active Bond Monitoring: Offering users an intuitive means to monitor active bonds and gauge their completion timeframe, facilitating informed decisions.  
3. Streamlined Bonding Pathway: Recognizing the value of seamless experiences, I identified the need to minimize the number of screens between initiation and the culmination of the bonding process.  
4. Completion Indication: Recognizing the inherent need for assurance, I aimed to introduce a clear visual indication of the bond completion status, bolstering user confidence and satisfaction.

Due to the scarcity of designers with a profound understanding of the intricacies between sOHM and gOHM, a strategic decision was made to refocus my efforts. As a result, I transitioned away from the final designs and shifted my efforts toward crafting the migration interface designs. This task loomed as a monumental undertaking, as the responsibility entailed catering to the needs of over 120,000 OHM holders during the asset transition to gOHM, all underpinned by the designs I meticulously developed.
Feel free to ask me any questions or just say hi! camren.m.browne@gmail.com