Skip to content
← All work
DAO-BConcept work

DAO-B: making a DAO usable for people who aren't crypto-native

An independent university research and product concept that moved from DAO and Ethereum foundations into an admin experience for staff bonuses, voting, wallets, and governance.

Role
Product Designer and Researcher
Year
2020
Platform
Web
original presentation
31 slides
prototype scope
Staff + admin
product scope
Governance + treasury

Evidence note: Independent university concept; it was not commissioned, shipped or outcome-validated, and all visible product data is illustrative.

DAO-B administration platform with governance proposals, team bonuses, voting states, user management, and treasury controls
01 · Pitch brief

What the concept needed to communicate

DAO governance asks people to understand shared decision-making, voting, wallets, and automated rules at the same time. The project explored whether those ideas could feel more familiar when translated into recognisable staff and admin software.

02 · Concept work

The work

From DAO research to DAO-B

The original presentation starts with a critical look at DAOs, Ethereum, and on-chain tradeoffs before introducing DAO-B. That sequence matters because it shows the product as a response to an organisational question, not just a set of screens with blockchain language added later.

Cameron presenting the DAO-B university project beside an exhibition display
Presenting DAO-B at the university showcase, with the research and product concept brought together as one original presentation.

Turning governance into a staff workflow

The staff experience turns governance into a concrete sequence. A person can suggest a bonus, read the shared wallet balance, vote yes or no, and see the proposal move through a visible state. The interface uses familiar tables and account patterns to keep the decision itself in focus.

DAO-B dashboard showing a new company bonus proposal awaiting approval
New requests separate the immediate admin decision from the wider proposal lifecycle.
DAO-B dashboard showing multiple bonus proposals in voting with yes and no controls
Voting keeps the active decision visible, with amounts, percentages, vote counts, and simple yes/no actions.
DAO-B dashboard showing a finished bonus proposal with final yes and no vote counts
Finished proposals show the result without asking people to decode on-chain history.
DAO-B dashboard showing a declined company bonus proposal
Declined proposals get their own state so rejected requests do not disappear or look unresolved.

Giving the owner a separate control layer

The owner-admin view adds the controls needed to run the imagined system. It separates proposal approval from voting, exposes vote totals after completion, and keeps wallet, settings, and status filters in the same operating layer.

DAO-B teams table showing departments, proposal activity, employees, total funds and allocation
Teams translate governance into an organisation structure people already understand.

Keeping wallet mechanics connected to business rules

Wallet funding, recurring deposits, bonus limits, voting periods, and notifications sit beside the governance flow rather than forming a separate technical product. This keeps the blockchain layer connected to the operational rules people would actually need to understand.

DAO-B settings screen with bonus wallet, payout dates, voting day period and notification toggles
Settings make the treasury rules explicit: wallet, bonus limit, payout timing, voting period, and notifications.
DAO-B wallet screen showing overall company wallet balance, deposit history and add funds action
The wallet view makes shared money feel auditable, with balance, deposits, payout tabs, and wallet history.
DAO-B wallet connection modal with Wallet Connect, Metamask, Fortmatic and Portis options
Wallet connection is reduced to a small choice set instead of becoming the whole experience.
03 · Scope

What this concept demonstrates

The project produced a 31-slide research presentation and a staff-and-admin prototype covering proposals, voting, wallets, user management and treasury controls. My contribution covered research, product framing and interaction design.

04 · Reflection

Using familiar workflows to keep governance visible

I translated proposals, voting and shared funds into familiar staff and admin patterns so the organisational decision stayed visible instead of letting blockchain mechanics dominate the experience.

Pitch deck · 31 slides

DAO-B: Original research and product presentation

Cameron Calder's original 31-slide presentation, moving from DAO and Ethereum research into a product concept for staff bonuses, voting, administration, wallets and settings.

Download editable PowerPoint ↓
Scroll through the proposal →01—31
  1. Opening slide titled DAOs or CEOs, introducing research into DAO governance on Ethereum and the development of DAO-B beside a network of cubes around a pound symbol.
    01DAOs or CEOs?
  2. Motivations slide outlining the business and technical questions behind the project, illustrated with a connected network landscape and flag.
    02Motivations for exploring DAOs
  3. Definition of a decentralised autonomous organisation with traditional and DAO structures, advantages, disadvantages and examples including Uniswap, Maker, Aave and Aragon.
    03What is a DAO?
  4. Overview of Ethereum, smart contracts and decentralised applications with an Ethereum logo and concise pros and cons.
    04Ethereum foundations
  5. Comparison of on-chain tradeoffs for a business use case beside a fragmented chain-link illustration.
    05On-chain or off-chain?
  6. DAO-B identity slide expanding the name as Decentralised Autonomous Organisation Bonuses and crediting Cameron Calder.
    06Introducing DAO-B
  7. DAO-B sign-in screen with email and password fields beside the expanded product name on a black panel.
    07Sign in
  8. Black DAO-B section divider introducing the user experience.
    08Users
  9. Explanation of anonymous team voting beside a staff list with proposed bonus percentages and yes or no controls.
    09Voting panel
  10. Staff dashboard showing seven company bonus proposals, vote counts, percentages, yes and no actions, and the shared wallet balance.
    10Company bonuses
  11. Annotated staff dashboard explaining employee totals, anonymous vote counts, bonus suggestions, account controls and shared wallet visibility.
    11Company bonuses, annotated
  12. Staff account concept explaining wallet-based access beside a profile, suggest-bonus action, personal details and bonus history.
    12Staff accounts
  13. DAO-B profile for Cameron Calder with illustrative account details, wallet address, editing controls and a table of past bonuses.
    13Staff profile and bonus history
  14. Annotated staff profile explaining bonus suggestions, notifications, account management and private wallet-linked bonus history.
    14Staff profile, annotated
  15. Black DAO-B section divider introducing the owner and admin experience.
    15Owner and admin
  16. Admin dashboard explanation beside a company bonuses table with proposal stages, amounts, voting controls and approval actions.
    16Admin dashboard
  17. Full DAO-B admin dashboard with proposal filters, staff rows, bonus amounts, vote controls, approval actions and wallet access.
    17Company bonuses admin view
  18. Annotated admin dashboard explaining proposal filters, pre-vote approval, equal voting rights, wallet controls and visible vote totals.
    18Admin dashboard, annotated
  19. Admin approval concept showing a proposed 30 percent next bonus with prominent decline and approve controls.
    19Admin approval
  20. DAO-B admin dashboard filtered to one new bonus proposal with decline and approve actions.
    20New bonus proposals
  21. DAO-B admin dashboard filtered to four bonus proposals currently in voting, each with yes and no controls.
    21Proposals in voting
  22. DAO-B admin dashboard filtered to a finished bonus proposal with final no and yes vote totals.
    22Finished proposals
  23. DAO-B admin dashboard filtered to a declined bonus proposal.
    23Declined proposals
  24. Explanation of recurring company deposits beside a wallet view with a balance, add-funds action and monthly transaction history.
    24Autonomous recurring deposits
  25. DAO-B admin wallet showing a shared balance, abbreviated wallet address, add-funds action and six recurring deposits.
    25Wallet transaction history
  26. Add-funds form with wallet, amount, recurring deposit toggle, frequency selector and submission action.
    26Add funds
  27. Wallet integration concept featuring MetaMask, Frame, Fortmatic and Portis.
    27Wallet integration
  28. Darkened add-funds screen with a modal for choosing an unknown wallet, Frame, Fortmatic or Portis account.
    28Choose a wallet account
  29. DAO-B admin settings for wallet, maximum bonus, payment date, voting period and notification preferences.
    29Settings
  30. Annotated settings screen explaining admin navigation, wallet linking, bonus limits, voting duration and notifications.
    30Settings, annotated
  31. Technical stack slide showing MongoDB, Express, React, Node.js, MetaMask and Solidity with short implementation notes.
    31DAO-B tech stack
Next concept →Connected Matchday: a smart-stadium agency concept