<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aiseosa Uyi-Idahor on Medium]]></title>
        <description><![CDATA[Stories by Aiseosa Uyi-Idahor on Medium]]></description>
        <link>https://medium.com/@aiseosauyiidahor?source=rss-3cdf10d6ad9e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DsYw9IWZZBMjGFutedZIzA.png</url>
            <title>Stories by Aiseosa Uyi-Idahor on Medium</title>
            <link>https://medium.com/@aiseosauyiidahor?source=rss-3cdf10d6ad9e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:36:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aiseosauyiidahor/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Five needed habits for builders who ship with AI]]></title>
            <link>https://medium.com/@aiseosauyiidahor/five-needed-habits-for-builders-who-ship-with-ai-b7240fe23b2d?source=rss-3cdf10d6ad9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7240fe23b2d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Aiseosa Uyi-Idahor]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 14:09:26 GMT</pubDate>
            <atom:updated>2026-09-07T14:09:26.285Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zzmeb5P_lUWZjXGOnUqsCA.png" /><figcaption>The creators touch</figcaption></figure><h3>I build with AI every day. These are the checks I keep so the tool never gets ahead of me.</h3><p>Almost everything I ship now has AI in the loop. Front-ends, flows, whole features. I am a designer by default, not an engineer, and for most of my career the gap between what I could picture and what I could ship was the thing that defined my work. That gap is mostly gone now. I can take an idea from a sketch to a working product on my own, in days, and the result is better than what I used to get from a team.</p><p>That is not the problem. The problem showed up on a project I still think about.</p><p>Earlier this year I built an approval inbox for an AI agent. The agent drafted customer replies and social posts for a team I work with, and my job was the human layer, the screen where a person reads what the agent wrote, edits it, approves it or kills it, and the agent learns from what got changed. It is the kind of product everyone wants right now, an agent that does the work and a person who stays in charge of it. I designed it and shipped the front-end myself, with AI writing most of the code.</p><p>The brief the client gave me was one line. “We want to see what the agent says before it goes out.” The obvious build is a list of drafts with an approve button, and that is what the first version was. I killed it after a week of watching the team use it. They were not approving, they were rewriting. Almost every draft got edited before it went out, which meant the screen was in the way of the real work, and worse, the agent never found out what had been changed, so it kept making the same mistakes.</p><p>So the second version made three decisions that the first one had skipped. The agent’s draft and the person’s edit sit side by side, not as a code-style diff, because the people using it run sales and social, not engineering, and a red-and-green diff means nothing to them. Kill is a first-class button, as visible as approve, because a draft that promises something we have not confirmed is worse than no reply at all, and I wanted killing to feel normal rather than like a failure. And under every edit there is one line, the thing the agent learned from it. Shorter opener. No exclamation marks. Lead with the answer. That line was the whole product. Without it you have a queue. With it you have an agent that gets closer to the team’s voice every week without anyone writing a prompt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dqz2u5cRyq5d6_Lnq27B3w.png" /></figure><p>Here is what got under my skin. Every week the agent’s drafts needed fewer edits. Every week the tool I was building with needed fewer corrections from me. The product was getting better on both ends and I was sitting in the middle of it, approving things, and one evening I caught myself asking the question I had been dodging.</p><p>Am I getting better too, or is it only the work?</p><p>This is not an anti-AI post. I think these tools make us more capable and I am not interested in the version of this conversation where designers pretend they are not using them. But there is a version of the next few years where builders hand over so much of the thinking that we stop growing, and the output keeps improving while the person behind it quietly stays the same. I do not want that version. So I keep five habits. None of them slow me down much. All of them are there to make sure the person is still in the loop, not just the tool.</p><h3>1. Write the brief yourself</h3><p>Before I open the tool, I write the feature in three plain sentences. Who it is for. What it does. What done looks like.</p><p>It sounds basic, and that is the point. Most of the bad work I have shipped came from a brief I skipped. The one I still think about was a promoter dashboard for an event ticketing product I build for. I had a rough idea, opened the tool, and typed something like “build the organiser analytics page.” What came back was plausible. Charts, a table, filters, the lot. I iterated on it three times before I admitted the real problem. A promoter in Miami on the night of a show does not want analytics. I only worked that out because I stopped iterating and asked one. What are you actually looking at on your phone at 11pm? Her answer took ten seconds. How many people are in, how much money is in the account, and is the scanner at the door still working, because if it goes down the queue turns into a fight. Everything else on my dashboard was for the morning after, on a laptop, with coffee. Three numbers, big enough to read in a dark venue with one hand, and a button to log a door sale. That was the page. Then the analytics went to a separate morning-after view where it belonged.</p><p>I had asked for a dashboard because I had not decided what the page was for, and the tool had no way of knowing that. The tool cannot fix a decision you have not made. It will happily build the wrong thing beautifully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yc9NSWDs-JNjRiDkH9I2pg.png" /></figure><p>The brief is the thinking. The prompt is just the delivery.</p><h3>2. Approve the decisions, not just the output</h3><p>I do not read every line the tool writes. I am not going to pretend otherwise, and I do not think reading every line is the point.</p><p>What I do read is every decision. The big calls, the direction, the structure, what we are building and what we are leaving out, all of that gets agreed before anything is built. Then, on the technical choices, the ones where I am relying on the tool’s judgment more than my own, I do two things. We weigh the trade-offs out loud, so I understand why one option beat the other. And I ask a second AI to argue the other side before I say yes.</p><p>That second step matters more than it sounds. On a drinks distribution platform I build for, the client needed a way to track what sales reps were owed. The first model proposed calculating commission on the fly from the orders table, clean and simple. I handed that plan to a second model and asked it to argue against it. It came back with one question. What happens when a rep’s rate changes mid-month, or an order is refunded after payout? The first plan would have quietly rewritten history every time someone edited a rate. We ended up storing each commission as its own record at the moment it was earned, which is more work and completely boring, and it is the reason I can trust the number today. When the two models disagree, that gap is exactly where the real decision lives, and it is where I actually learn something. When I skip that step, I am not making a decision. I am just watching one get made.</p><p>Speed is fine. Blind is not.</p><h3>3. Own the feel, even if you do not write the code</h3><p>I do not hand-write my CSS anymore. I want to be honest about that because a lot of designers who build with AI are quietly embarrassed about it, and I think the embarrassment is misplaced.</p><p>Here is what I actually do. I collect references for months. Screenshots, interactions, a transition I noticed in someone else’s app, a button that felt right. When it is time to build, I hand the tool the exact sample of what I want, not a description of it. The ticket checkout is the example I use when people ask. The moment you tap “pay” and the ticket appears should feel like something was handed to you, not like a page reloaded. I had a reference saved from a banking app that got that feeling right. I gave the tool the recording and the numbers behind it, and the first version came back technically identical and somehow wrong. Too fast. It arrived before you had finished tapping. So we went back and forth. Slower at the end. Let the ticket settle before the confetti. Kill the confetti, actually, it is doing too much. Move the receipt up so your thumb is already on it. Eleven rounds for one screen, and I did not write a line of it. I do not stop until it feels right.</p><p>People assume that if you did not type it, it is not yours. I think that is backwards. The tool does the typing. The standard is still mine, and the standard is the part that makes the work look like a person made it. Every AI-built app looks the same until someone with taste refuses to accept the first version. Taste does not ship itself. Someone has to hold the bar.</p><h3>4. Check the date on the advice</h3><p>A model will recommend a package that was retired last year, with total confidence. It has happened to me more than once. The time that made it a rule, I was wiring up sign-in on a Next.js and Supabase build for a client and the model reached for the auth helpers package it had clearly seen a thousand times in training. Confident, tidy, wrong. That package had been retired in favour of a newer one, and the newer one handles sessions differently in ways that would have broken the moment the app hit production. I only caught it because something in the import name looked dated to me, and I went and checked.</p><p>The tools are trained on a snapshot of the world, and the world of software moves faster than the snapshot. A library gets deprecated. An API changes. A best practice from two years ago becomes the thing everyone warns you about. The model does not know this, and worse, it does not sound any less sure when it is wrong.</p><p>So before anything technical lands, I check the date. Current docs, the changelog, one more opinion from a second tool with fresher context. It takes minutes and it has saved me days of building on something that was already dead. Confident is not the same as current.</p><h3>5. Ship what you can defend out loud</h3><p>If a teammate, a client or a recruiter asks why, the answer cannot be that the model suggested it.</p><p>Every screen I put out, I can walk through the reasoning without opening a chat. Why this layout, why this flow, why this and not that. I got tested on this once without warning, on a call with a client I was building an ops dashboard for. They pointed at a table and asked why the overdue invoices were sorted the way they were. I could answer it, because I had made that call myself, out loud, two weeks earlier. But I remember the half second where I checked whether I actually knew or whether I was about to say “the model suggested it.” That half second is the whole post. If I cannot explain a decision, I did not make it, and the point of the first four habits is that I am still the one making them.</p><p>This is also, honestly, the one that matters most for your career. The people who will hire you or work with you in the next few years are not going to be impressed that you can produce output. Everyone can produce output now. They are going to want to know whether you understand what you produced. If you need the chat to explain your own work, you skipped a rep somewhere.</p><h3>What the next phase of work looks like</h3><p>I think about this a lot, because I am a designer who builds, and the tools have changed what that means faster than most people expected.</p><p>Here is what I believe. The floor is rising for everyone. A person with no design training can get a decent-looking screen out of a tool in minutes. A person with no engineering background can ship a working feature. That is real, and it is not going away, and pretending otherwise is a waste of energy.</p><p>But the floor rising does not raise the ceiling. The ceiling is still judgment. Knowing what to build, knowing when the output is wrong even though it looks right, knowing which of the five plausible options is the one that will still make sense in six months. The tools do not have that. They have confidence, which is a different thing.</p><p>So the next phase of work for designers and builders is not people who refuse the tools, and it is not people who disappear behind them. It is people who let the tool carry the load and keep the reps that raise the ceiling. The brief, the decisions, the feel, the date on the advice, the reasoning you can say out loud. Hand off everything else.</p><p>AI raises the floor. Your judgment is the ceiling. Protect the ceiling.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7240fe23b2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Web3 CX Problems We Underestimate When Designing]]></title>
            <link>https://medium.com/design-bootcamp/the-web3-cx-problems-we-underestimate-when-designing-e461b1381a4c?source=rss-3cdf10d6ad9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e461b1381a4c</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Aiseosa Uyi-Idahor]]></dc:creator>
            <pubDate>Tue, 20 Jan 2026 08:16:06 GMT</pubDate>
            <atom:updated>2026-01-20T09:58:43.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QGC7b_2L4Pg1VdvVaQI83g.png" /></figure><p>Web3 has an onboarding problem. Wallet connections are confusing, terminology is unfamiliar, and the first few minutes often decide whether a user stays or leaves. That reality is well understood, widely discussed, and actively being worked on.</p><p>But once a user is past onboarding, once they are connected, funded, and ready to interact, another set of problems begins to surface.</p><p>These are not the kinds of issues that show up as broken buttons or failed transactions. Everything works. The interface responds. The system does exactly what it is supposed to do.</p><p>And yet, users do not feel at ease.</p><p>They double-check actions that already went through. They second-guess the steps they just took. They feel unsure even when nothing has technically gone wrong. The product is functioning correctly, but confidence begins to slip.</p><p>This is the part of the experience most teams do not spend enough time with.</p><h3>When the system is right, but the user is not sure</h3><p>It often starts quietly, around something as simple as chains and networks.</p><p>A user connects their wallet and lands on a dashboard. They swap, stake, or mint. Later, sometimes hours later, sometimes the next day, they come back and notice their balance looks different. Maybe it is missing entirely. Maybe it is lower than expected.</p><p>Nothing has actually disappeared. The asset lives on a different chain, or the wallet is now pointed at another network.</p><p>From the product’s perspective, this is obvious. From the user’s perspective, something feels wrong.</p><p>I have seen users jump straight to the worst conclusion. They assume they have been hacked. They assume funds are gone. The wallet technically knew where the asset was. The protocol behaved exactly as designed. The interface even had a network selector visible somewhere on the screen.</p><p>I ran into this while working on a product that allowed users to receive funds both from other users on the platform and from external wallets.</p><p>From a user’s perspective, receiving money usually means one thing. Your main balance goes up. That expectation was already deeply ingrained.</p><p>In this case, funds received from internal users were routed to a funding balance rather than the primary balance users checked by default. Technically, nothing was wrong. The funds arrived, were owned by the user, and were fully accessible.</p><p>But users would receive a confirmation, navigate to their main balance, and see no change. At that moment, confidence collapsed and support tickets spiked. Not because money was missing, but because the product broke the user’s expectation of where received funds should appear.</p><p>The issue was not infrastructure. It was explanation. An explanation that could have happened in an email, a push notification, or another well-timed surface. A simple signal at the moment of receipt that clarified where the funds landed and why would have prevented most of the confusion.</p><p>The system was consistent. The experience was not.</p><p>A clear explanation of why something is not visible right now, where it actually lives, and what needs to change for it to appear can be the difference between reassurance and panic.</p><h3>When signing becomes a leap of trust</h3><p>Another place this breakdown shows up is when users are asked to sign something.</p><p>A wallet pops up with a wall of technical language, truncated descriptions, and a single Confirm button. Most products treat this as a wallet concern rather than their own. Users do not make that distinction. To them, this is still part of the product they are using.</p><p>I have watched users pause at a signature request, skim nothing, and click confirm simply because they assume the product would not ask them to do something dangerous without explaining it first.</p><p>When the outcome later is not what they expected, the trust break does not land on the wallet. It lands on the product.</p><p>The flow was technically correct. The action succeeded. But at the most critical moment, when meaning mattered more than mechanics, the product stepped aside.</p><p>The strongest products do not leave this explanation to the wallet layer. They prepare the user before the pop-up appears. They explain what is about to happen, what will change, and whether it can be undone, in plain language, inside the product itself.</p><p>The wallet confirmation becomes the final step, not the first explanation.</p><p>When users sign blindly, it is rarely because they are careless. It is because the system trained them to trust without context.</p><h3>Irreversibility should feel different before it happens</h3><p>The most expensive moments in Web3 tend to involve actions that cannot be reversed.</p><p>In many products, these moments look deceptively ordinary. The same neutral language is used everywhere. Confirm. Proceed. Continue. The buttons look identical whether the action is harmless, temporary, or permanent.</p><p>From a protocol perspective, irreversibility is expected. From a user’s perspective, it often is not.</p><p>I have seen users burn NFTs by clicking a button labeled Confirm Burn, without a clear indication that the asset would be destroyed immediately and permanently. I have seen permissions revoked with a single Proceed click, without making it clear that the connected app would lose access entirely. I have seen funds locked into contracts behind buttons labeled Stake or Deposit, where exit conditions were buried elsewhere.</p><p>In each case, the user did not ignore information. They followed the interface.</p><p>The language suggested a normal step forward, not a point of no return.</p><p>This is usually where regret enters the experience, not instantly, but later. When the user tries to undo what they just did and realizes there is no undo. No reversal. No support path that can help.</p><p>At that point, the product stops feeling like an interface. It becomes something the user associates with loss of control.</p><p>Traditional finance learned early that irreversible actions need to feel different before they happen. Closing a bank account does not look like transferring money. Cancelling a card does not look like checking a balance. The system signals weight through language, pacing, and structure.</p><p>The same principle applies here.</p><p>A button that says Burn this NFT permanently lands very differently from Confirm. A flow that pauses to restate, in plain language, that an action cannot be undone creates reflection without relying on fear. Even a second confirmation that shifts the tone from neutral to explicit forces the user to re-engage their intent.</p><p>This is not about adding warnings everywhere or scaring users away from powerful features. It is about making consequences visible at the moment of commitment.</p><p>In Web3 today, too many irreversible actions feel effortless. The product optimizes for speed, and the user pays for it later.</p><h3>CX does not end when the screen changes</h3><p>What connects all of these moments is not bad design or careless teams. It is incomplete ownership of the experience.</p><p>Web3 products are often designed for correctness in the moment of interaction, but not for confidence over time. They assume that once onboarding is complete, users understand chains, wallets, and permanence well enough to navigate everything that follows.</p><p>Real usage tells a different story.</p><p>Experience continues when users leave and come back later, when they switch devices, and when they try to remember what they did and why. It lives in the continuity between moments.</p><p>For founders, these gaps show up as support tickets, churn, and quiet drop-offs that analytics struggle to explain. For designers, they represent some of the most impactful work left to do in this space.</p><h3>What we are still underestimating</h3><p>Web3 does not need less power. It needs more clarity around power.</p><p>The products people trust most will not be the ones that add the most features, but the ones that help users understand where they are, what they are agreeing to, and what cannot be undone without forcing them to become experts.</p><p>Those moments rarely feel dramatic. They feel small. Easy to miss.</p><p>But over time, they shape whether people feel safe using what you have built.</p><p>And that is the part we are still underestimating.</p><h3>Further Reading</h3><p>Nielsen Norman Group — Visibility of System Status<br><a href="https://www.nngroup.com/articles/ten-usability-heuristics/">https://www.nngroup.com/articles/ten-usability-heuristics/</a></p><p>Don Norman — <em>The Design of Everyday Things</em><br><a href="https://jnd.org/the-design-of-everyday-things/">https://jnd.org/the-design-of-everyday-things/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e461b1381a4c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-web3-cx-problems-we-underestimate-when-designing-e461b1381a4c">The Web3 CX Problems We Underestimate When Designing</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Products for People Who Are Busy, Not Curious]]></title>
            <link>https://medium.com/design-bootcamp/designing-products-for-people-who-are-busy-not-curious-458602d8f0e2?source=rss-3cdf10d6ad9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/458602d8f0e2</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Aiseosa Uyi-Idahor]]></dc:creator>
            <pubDate>Fri, 09 Jan 2026 07:26:12 GMT</pubDate>
            <atom:updated>2026-01-10T10:53:44.130Z</atom:updated>
            <content:encoded><![CDATA[<p>I used to think users were curious and believed they would click it; if it were findable when they looked around, they would see it.</p><p>Not in a naïve way, but in the subtle, professional way designers assume curiosity. The kind where you believe someone will pause long enough to read helper text, hover long enough to notice a tooltip, or explore long enough to understand why you made a particular interaction choice.</p><p>If you ask me, does it make sense, I’ll always answer yes then because, common, it’s there, it’s placed for a reason, it’s only logical you check it out (Same way people always read instruction manuals right 😏, but it’s always in each new purchase).</p><p>That belief didn’t come from theory. It came from designing in quiet rooms, with time, good internet, and a full mental tank. Well, real life corrected that assumption very quickly.</p><p>The moment you start watching how people actually use products, especially products they need rather than want, you realize something uncomfortable: most users are not curious, especially when dealing with delicate products like Fintech or SaaS. They are busy and want to get on with their lives; they are distracted, and they are probably already late for something. And your product is just one more thing competing for their attention.</p><p>They are not here to admire your system. They are here to finish a task and leave.</p><figure><img alt="An image of a designer in his full thinking space and a user just going about daily lives" src="https://cdn-images-1.medium.com/max/1024/1*k_G5JhCGowDPCbLgbA4OYw.png" /></figure><h4>Reality came with a quick blur</h4><p>The first time this really hit me wasn’t during a usability test this is where we miss it, we can’t really get 100% real world usage in a usability test (not usability insights tho, we would talk about that in a different article😌) especially the scheduled ones, as the users are somewhat mentally prepared to embark on the journey with you and are abit more curious than a regular day. It was when I watched a friend use a product I had worked on and completely ignore the part I was most proud of.</p><p>There was a subtle intro page cue for a feature that led to user verification for the app’s savings aspect, carefully worded and positioned just right, with all hints and guides. It explained everything. I watched the user open the app, scan the screen for less than a second, tap the first thing that looked clickable, and begin setting his details. The tool tips and hints felt like fancy and seemed just the titles of the fields were enough to get him to engage.</p><p>They never saw the explanation. Not because it was bad, but because they didn’t have the patience to look for it and felt confident in their knowledge. What followed were complaints and support tickets to help undo actions taken when some after-effects began to occur.</p><p>That moment reframed how I think about design.</p><p>Busy users don’t explore. They scan. They don’t read. They skim. They don’t learn systems. They form assumptions and act on them. And when those assumptions fail, they blame the product, not themselves.</p><p>This is why so many “well-designed” products quietly fail. They are coherent, elegant, and thoughtfully structured, but they are built for users who have time and mental space. <em>That user is rare</em>.</p><p>Steve Krug captured this reality years ago when he wrote “Don’t Make Me Think.” What often gets missed is that the phrase isn’t anti-intelligence. It’s anti-friction. Thinking takes energy, and busy users are already spending that energy elsewhere.</p><p>When someone opens your product, their mental budget is low. Every extra decision you ask them to make is a withdrawal.</p><figure><img alt="Image of a user with low attention span" src="https://cdn-images-1.medium.com/max/1024/1*p3IgsLGSB3LmK9uFJk-iig.png" /></figure><h4>So what do we do</h4><p>Once you accept that users are busy, many design instincts start to change.</p><p>You stop designing for discovery and start designing for completion.</p><p>You begin to care less about whether something is clever and more about whether it is obvious. You start removing choices instead of adding them. You realize that clarity beats flexibility far more often than designers like to admit.</p><p>This is where many products go wrong. They assume more options equal more power. In reality, more options often equal more hesitation.</p><p>Hick’s Law explains this: the more choices a person has, the longer it takes to make a decision. In practice, this means a screen with five “useful” actions often performs worse than one with a single clear primary action.</p><p>Busy users don’t want to decide. They want the product to decide for them, or at least strongly suggest the right path, and they just click the buttons.</p><p>This is why defaults matter so much. A good default is silent design leadership. It says, “We’ve seen this before. This is probably what you want.”</p><p>Bad defaults push cognitive work back onto the user. And busy users feel that immediately.</p><figure><img alt="A login page of poor hierarchy and good hierechy" src="https://cdn-images-1.medium.com/max/1024/1*3CqoSgF3Uy7P-L-jn2FgDQ.png" /></figure><h4>Another hard pill</h4><p>There’s another uncomfortable truth here. Delight is overrated if it slows people down.</p><p>Design culture often frames delight as animations, playful copy, or clever interactions. Those things can be great, but only when they sit atop a fast, predictable core experience.</p><p>A busy user will tolerate a boring product that works. They will not tolerate a delightful product that delays them.</p><p>Think about the products you rely on under pressure. Banking apps. Ticketing platforms. Ride-hailing apps. You don’t want a surprise. You want certainty. You want to know exactly what will happen when you tap a button.</p><p>This is why predictability is a design virtue that doesn’t get enough respect. Predictable interfaces reduce anxiety. They allow users to act without second-guessing. And for busy users, that sense of control is the real delight.</p><p>I’ve seen teams argue passionately about micro-interactions while ignoring the fact that the main task takes six steps instead of three. Busy users don’t always notice your animation curve. For those who do, it’s delightful the first few times, then fades, but the friction introduced by animations that aren’t carefully done remains, and users are forced to live with it now that they notice the extra step, not the excitement. By the way, I love animations when they are used properly.</p><p>Designing for busy users also changes how you think about errors and high-impact actions.</p><p>Curious users might experiment and recover. Busy users hit an error and panic. Or worse, they leave.</p><p>Error states are not edge cases in busy-user products. They are core moments. A vague error message that forces someone to think, interpret, or guess is, in effect, a failure.</p><p>When a busy user encounters an error, the product should do most of the work. It should explain what happened in plain language, tell them what they can do next, and ideally prevent the error in the first place.</p><p>This is where constraints become acts of care.</p><p>Now, for high-impact actions, adding an extra confirmation step with a retractable action is always better than letting them make the mistake and explaining afterward via support tickets. Designers sometimes resist constraints because they feel limiting. In reality, this friction protects users from themselves, especially when they are rushed. What all of this adds up to is a shift in mindset.</p><figure><img alt="Proper error state UX" src="https://cdn-images-1.medium.com/max/1024/1*9uVHZ4ZYIBdNKmyxUOKkZg.png" /></figure><p>You stop asking, “Is this understandable if someone spends time with it?”You start asking, “Is this usable if someone is impatient, distracted, and slightly stressed?”</p><p>That question is humbling. It forces you to remove ego from the work. It pushes you to design less for Dribbble and more for real life.</p><p>And ironically, products designed this way often feel more polished, not less. They feel calm. They feel respected. They feel like they were made by people who understand what it’s like to be human in a hurry.</p><p>I think this is one of the most important shifts designers can make as they grow more senior.</p><p>Junior designers often focus on how things look. Mid-level designers focus on how systems work. Senior designers focus on how people behave when no one is watching.</p><p>Busy-user design lives squarely in that last category.</p><p>It’s not flashy. It’s not loud. But it’s deeply intentional. And in a world where attention is scarce and patience is thinner than ever, it’s the difference between products people admire and products people actually use.</p><p>If you design for curious users, you will impress designers. If you design for busy users, you will ship products that survive.</p><p>And survival, quietly, is the highest compliment a product can earn.</p><h3>Further reading</h3><p>Don’t Make Me Think — Steve Krug<br><a href="https://sensible.com/dont-make-me-think/">https://sensible.com/dont-make-me-think/</a></p><p>Hick’s Law and UX<br><a href="https://www.youtube.com/watch?v=pbbTOzArcWQ">https://www.youtube.com/watch?v=pbbTOzArcWQ</a></p><p>Cognitive Load Theory in UX<br><a href="https://www.nngroup.com/articles/minimize-cognitive-load/"> https://www.nngroup.com/articles/cognitive-load/</a></p><p>Principles Of Error States<br><a href="https://cxl.com/blog/error-messages/">https://cxl.com/blog/error-messages/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=458602d8f0e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/designing-products-for-people-who-are-busy-not-curious-458602d8f0e2">Designing Products for People Who Are Busy, Not Curious</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A complete overview of Venus finance to a web3 rookie]]></title>
            <link>https://medium.com/design-bootcamp/a-complete-overview-of-venus-finance-to-a-web3-rookie-933a0b91712d?source=rss-3cdf10d6ad9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/933a0b91712d</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Aiseosa Uyi-Idahor]]></dc:creator>
            <pubDate>Mon, 03 Apr 2023 13:10:56 GMT</pubDate>
            <atom:updated>2023-04-04T04:26:12.125Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the biggest pillars of Web3 is the financial aspect of it, called Defi. Its one that users of web3 interact with the most and thus a good experience here would set a pace for all of web3, so let’s approach this like a regular person and see what we experience</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*_ROwpjjvuFw6G50ado-5Jg.png" /></figure><h3>Starting with a little intro</h3><p>Venus is a DeFi platform on the Binance Smart Chain that offers a variety of financial services, including collateralized loans, stablecoin minting, and liquidity provision. Users can borrow different assets by using other cryptocurrencies as collateral, with varying interest rates.</p><p>By providing liquidity, users can also earn interest and rewards in the form of the platform’s native token, XVS. Overall, Venus is a popular platform for DeFi services and earning rewards on cryptocurrency assets.</p><h3>Getting started with the landing page</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*VlGeHkV2DKG7n2WaeeFPEQ.png" /></figure><p>My first touch point into Venus was the landing page, because I do not know the exact URL I had to search for Venus web3 on Google and the link was the first that popped on my feed</p><p>After opening the website, I could say the website seemed straightforward, but it was failing to give a proper explanation of the core value proposition of the platform. I see Earn, Lend, and Borrow, but I don&#39;t know what they do, and it takes me straight to the web app. I see a table, but I am not sure what it’s for. Honestly, I felt the design of the landing page entirely had a low quality compared to its top competitors so I decided to completely redesign it</p><h3>The Redesign of the Landing page</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PQN13yH7hrnvJN3DqPZQag.png" /></figure><p>The first step was to give the landing page a modernized look to compete with and surpass its rivals.<br>Next, important parts of the landing page were highlighted, including metrics. Metrics are a crucial component of any platform, and properly displaying them can increase user trust. Previously, Venus was not leveraging this powerful element to build trust.</p><p>The next major redesign was adding a section to the landing page that explains the platform’s core value propositions: lending, borrowing, and earning.<br>Finally, the website was given a complete makeover to enhance its aesthetics and make it a world-class platform.</p><h3>Well Let&#39;s Proceed to the product</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*qE72LrJ6b4yaJpgBqvwFJg.png" /></figure><p>The dashboard looked simple and easy to navigate. The layout was easy to understand and identify the various aspects of the platform that we needed to interact with.<br>I loved how there was a red indicator on the borrowing limit to let you know that once you get above this point, things get risky.<br>I also loved how you could see your supply balance, borrow balance, daily earnings, and net APY in one place.</p><h3>Taking a stab at minting some VAI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*yxkVRt8ihQYVnmravkrHOw.png" /></figure><p>The first investment touchpoint I came across was Minting, probably because it’s the most prominent feature on the dashboard. Since I’m here to make some side cash, I decided to give it a try. 💃🏽</p><p>I clicked on “enable” to get started, but I couldn’t seem to do anything. The text field to enter a VAI amount wasn’t working, the CTA wasn’t working, and the Safe Max option wasn’t working either. Everything seemed buggy or unresponsive, without any feedback or solutions offered. This killed my mood for using this feature, especially since I didn’t have any VAI.</p><p>To be honest, VAI isn’t the most common token, so you can’t expect a lot of new users on your platform to have it. However, from what I understand, minting a protocol’s token helps the token grow and improves its treasury. So why not give more people a chance to improve your protocol’s treasure and be rewarded for it? It’s good business, and I’ll do everything in my power to get people to improve my protocol. So why not provide the means?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*5uteaokKyz50JCwHTV1b6A.png" /></figure><p>This can easily be achieved by allowing users to swap out existing tokens in their wallet for VAI or purchase VAI from a third-party protocol that deals in on-ramp transactions. From there, users can mint on your platform. It’s that simple. Boom!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*s7rWKOhJSohfHhO47EJKRA.png" /></figure><h3>Ok let&#39;s get more into familiar features</h3><p>After selecting a token as collateral, I clicked on the token to supply some of those tokens to the platform. This would allow me to have some funds to use as collateral to borrow.</p><p>The modal looked pretty straightforward. The information displayed wasn’t overwhelming or difficult to understand. I also loved the fact that they gave me a glimpse of what my earnings would be daily and how much my borrowing limit would be depending on the amount that I selected to supply.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*4g3yKx0jCbzphzrUazgRjA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*KNElEIXE_3TtZIx5XzUGXQ.png" /></figure><p>It gives a good overview of what to expect if you make such supplies, which I thought was amazing.<br>As for the buggy UX writing, the CTA says, “Enter a valid amount to supply.” The amount I inputted is valid, but I have no money. 😂. So the CTA can read “Insufficient Funds.” It depicts the situation more clearly.</p><h3>Let&#39;s try borrowing some tokens🎊</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ZsG6ru0UkCtahpxEDzNeDw.png" /></figure><p>Venus tries to make users aware of what is needed at every step, which is very important for a platform like this. For example, the card that indicates that you need to have supplied to Venus and activated the token as collateral before you can borrow is an amazing addition as it keeps users informed.</p><p>Then, the restriction on users from borrowing to a maximum amount is also a major improvement in the user experience for two main reasons. Firstly, it prevents users from making errors and running into problems, as there is a liquidation clause in most lending and borrowing protocols that can liquidate your funds if your borrowed funds exceed a percentage of your collateral.</p><p>Users are used to having the max feature in the text fields that deal with adding tokens for transactions, so out of haste, they can click max, and the moment they borrow, they stand a high chance of losing their funds, which can be disastrous.<br>Preventing users from making errors of their own doing was an amazing addition. Then, letting users know that we are constraining their maximum to 80% keeps users informed and, in turn, improves their experience.</p><h3>How about if I want to repay</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*WP9_51WCJHZDrj2AwxBrYw.png" /></figure><p>Repaying was also a very simple model. I love how Venus takes a more simplistic approach to not overwhelm users.</p><p>Giving me the ability to see my current borrowing spelled out and how much I have in my wallet to pay it back improves my experience a lot.<br>Also, the ability to select not just the maximum but various percentage points of my available balance was a good addition.</p><h3>Exploring more of Venus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*G_X-lYIskmX1adas-L6JHw.png" /></figure><p>I went through the rest of the Venus platform and found that they did a good job conveying necessary information in an easy-to-digest yet detailed manner. However, I came across the XVS page and was completely lost. It seems neglected and out of place.</p><p>Firstly, the address at the top assumes that we all know it refers to the token address. A little explanation would be helpful. Additionally, it would be beneficial to have an indicator or explanation of what we would use the token address for.</p><p>Regarding the table of tokens with XVS per day, I am confused about how the XVS is calculated. Is it based on the token supply and its associated reward, or is it from the distributed APY? This information is unclear and leaves me feeling lost.</p><h3>Let&#39;s take a look at the vault page</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*DYbVc0_Yk5XxJ7DUyr94sw.png" /></figure><p>The vault page is simple and easy to understand. The calls to action are clear, and the hierarchy is obvious, showing users what the most important actions on the platform are.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*fo0ifFuuVxGLLKalS7GffA.png" /></figure><p>However, we are facing the same issue as with the minting modal on the dashboard page. Staking is a vital way for protocols to improve their token treasury. If a user doesn’t have VAI or any other protocol token and gets stuck without a solution to invest in, it reduces their user experience. This ultimately leads to a lower number of users contributing to the protocol’s treasury, which is bad for business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*wkR_Rg-prysSO2DFKFcfbw.png" /></figure><p>This problem can be solved by introducing the ability for users to swap any existing token in their wallet for the specified vault token. Another alternative would be to provide users with a means to purchase these tokens instead of leaving them stuck without being able to do anything.</p><h3>Overall experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eP2qU89NAesSctEzIRsSOQ.png" /></figure><p>The experience of Venus is quite simple and straightforward, yes it has a semi-old feel but the features are simple and easy to navigate, tho some bumps in experience in some places overall it requires little effort to understand what to do, and had expected and this is very key for new users and for the overall user experience of your product</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=933a0b91712d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/a-complete-overview-of-venus-finance-to-a-web3-rookie-933a0b91712d">A complete overview of Venus finance to a web3 rookie</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A UX walkthrough of Aave protocol]]></title>
            <link>https://medium.com/design-bootcamp/a-ux-walkthrough-of-aave-protocol-52241dd7b0c3?source=rss-3cdf10d6ad9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/52241dd7b0c3</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Aiseosa Uyi-Idahor]]></dc:creator>
            <pubDate>Mon, 13 Mar 2023 13:05:17 GMT</pubDate>
            <atom:updated>2023-03-14T08:27:52.374Z</atom:updated>
            <content:encoded><![CDATA[<p>Aave is one of the strong pillars of web3 and its one that has millions of users all over the world and is setting standards in the ecosystem, so let’s approach this like a regular person and see what we experience</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iy95dbg1NzE-UIFzOPb_9w.png" /></figure><h3>A brief introduction to Aave</h3><p>AAVE is a DeFi platform that enables users to borrow digital assets with security or earn interest on deposits. It provides a secure and transparent lending and borrowing system without intermediaries.</p><p>AAVE has a liquidation mechanism that protects lenders if the value of the collateral falls and a governance system that enables token holders to vote on important decisions. With AAVE, users can easily participate in decentralized lending and borrowing,</p><h3>Aave: beginning your journey</h3><p>What I usually do when I get a website I want to use but am not 100% sure of the URL is just type it out on Google and hope it does the rest of the work by giving me an accurate URL. Well, it worked 💃🏽</p><p>I must admit that Aave&#39;s landing page is very straightforward and attractive; it gets right to the point and the layout is organized so that it doesn&#39;t feel overwhelming.</p><p>Well there are some improvements that can be done on this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QnZzgEf3_OGTDu2I7mIcNA.png" /></figure><h3>Some pointers for the landing page</h3><p>Information is everything when it comes to a landing page, so it is crucial that it can be passed along easily.</p><p>A web layout, especially on a single view, moves from a top-left to a bottom-right hierarchy, where the items on the bottom-right have the least importance in the hierarchy due to eye movements.</p><p>But this landing page contains a set of useful product explanations in the bottom right, which I believe can be properly optimized in the landing page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cH02r7m4Thp1rM3wChwzsQ.png" /></figure><h3>Let&#39;s help you provide more value</h3><p>So the first step was to maintain the brand feel as this isn’t a complete redesign but the aim is to optimize the user experience and provide as much value as quickly as possible</p><p>So the layout was retouched a bit and I got rid of unnecessary info like the Aave liquidity protocol and the logo, I already kinda know I am on Aave 👀</p><ol><li>So then I made the page header bigger and more immersive then brought upwards the slider that explains what the product does beneath it to serve as a more dynamic kind of subtext that covers the major aspects of Aave which was placed in the least hierarchy part of the web view and that was reducing the experience of users and making it more stressful to digest</li><li>Then we all love money and numbers so why not make the liquidity locked in Aave more immersive and bigger, this draws our attention more and instills confidence in the platform, you do not want to be shy about your numbers, do you💃🏽</li><li>Another touch point was the Aave markets, so not everyone knows what they are so how about we do a little explanation on them a bit so as to not leave any unanswered questions in the eyes of your potential users</li><li>Lastly reworked the CTA, its meant to be part of the landing page that stands out for a reason, to convert, we don’t want people to just read and not know how to start or be searching for it, so the old CTA (Call to action) was small and not calling our attention, so I changed the color to black to give it a more distinct feel and make it stand out better and still contrast well with the image and retain the design feel but now it stands out enough to call your action (damn I could be a rapper 😂)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q-dbJrng2McJe9NYKrMUzA.png" /></figure><h3>Curiosity almost killed this cat</h3><p>So one thing that I do and most people do is when they get into your landing page they try to explore the landing page a lot before making up your mind</p><p>So this often leads me to try out the nav links</p><p>So a lot of them are quite straightforward, the Docs, the Security, the FAQ, The Governance so I say I guess it’s straight forward but what with this Aave Protocol link, I am already on Aave protocol right🤔, oh maybe it’s a link to take me into the protocol itself that nice</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UNolNgtsOxWQMzhFyYYP7A.png" /></figure><p>I proceed to click on it, and boom, I am in a whole new confusing universe, 🥲. Oh boy, where am I? Did I click on the wrong button by mistake? This looks nothing like Aave😭. Oh, I am on Github, but why did they say AAVE protocol? My expectations and the outcome were completely different. This is a major problem with UX fundamentals. a simple clarity with the words would have made this a whole lot better and probably make the text (Open Source, or Preferably Our Github🤷🏽)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OO5uyRriUCLNdToPHX7TZg.png" /></figure><h3>Well Let&#39;s Proceed into the product</h3><p>Time to explore the dashboard, so far it looks really beautiful, and not overwhelming, I feel a bit relaxed</p><p>I get to see my Net worth, my supplies, my borrows, and the assets I can supply and borrow in one view</p><p>This is so nice, and they even guide me with information cards to tell me what to do. This I must say has some good level of thought put into it</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3wgp7tfpidB7BC9pasMyVg.png" /></figure><h3>First confusion sets in</h3><p>So in my quest of getting to familiarize myself with the platform before I take my first action so I can see all that the platform has to offer me, I came across an E-mode, so I’m curious and say for them to bring it for me to see it definitely has to be important, so I click on it</p><p>Oh boy, I love Aave. They seem to be big on communication. My spec is 🥰. But oh, this communication went south quickly. Aave is speaking, but I do not understand. 😢 I am curious now. I am confused. What’s LTV now?</p><p>Yeah, I know there is more to learn, but why do you want me to click away from your platform to go read a whole article to let me know just enough to fuel my curiosity? I don’t want to know the full concept, just a little 😭.</p><p>Well it turns out the Learn more was a whole article on E-mode and this explained a lot but I still have no idea what LTV is</p><p>One thing I know is when you don’t know something goes to your most informative friend Google, so I storm on there</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DjL6oOCjNDySqIzEWKl8Dg.png" /></figure><h3>Good use of information icons</h3><p>One thing I am loving is the fact that Aave is big on communication; the explanation icon on the Net APY helped in explaining what that&#39;s all about, and this helps me know better.<br>This is a very good way to educate and guide new users without obstructing the flow of your designs. I love it</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LaA_OyUnySFVQeXGEZDPQA.png" /></figure><h3>Google to the rescue</h3><p>Soi typed in quickly &quot;LTV,&quot; and the first response I get is &quot;Lagos Television.&quot; I know I don’t know what LTV is but I sure do know it can never be Lagos Television😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBLVyFOUYUVmSLaULefHTQ.png" /></figure><p>Something must be wrong so I refine my search to LTV in Aave and now I get something more informative and I think I get the concept of LTV better</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Qq4NYQiq6wkJASeDJiaTQ.png" /></figure><h3>Well All that would have been avoided</h3><p>So I took at least 15 minutes away from my goal of using Aave to lend and borrow crypto because I wanted to learn more, and this would have been solved with clearer communication. Sufficient information would have satisfied my curiosity and answered my questions and I would have never had to leave the product</p><p>Leaving a product is dangerous anyways, I might in my quest for research, come across a product that gives me a better offering, you just lost a user😕</p><p>Reduce my leaving your platform or its environment till I have been converted</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TIKXXA9mJkXC13mjhgPVNA.png" /></figure><h3>So let&#39;s try our hands on the E-mode</h3><p>I get to see an error that I am on the wrong network, that’s fair, so I see it is also a link, beautiful this saves me a lot of time but I click on it and it does nothing, I’m guessing this is a bug from the dev end tho, but still it affects my overall experience now I have to open my wallet and switch manaually😭</p><p>Well, I tried doing the E-mode but I saw some juicy gas fees to pay, so I fled 💃. I’ll be ready to commit more money to it later when I feel I need it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBHR8AhnyGjlMjzcJa5Jog.png" /></figure><h3>Exploring other markets</h3><p>So there was a dropdown in front of the Markets and I found that beautiful and intuitive as it’s very accessible and its placed in such a way that it’s easy to tell what this affects</p><p>So I clicked on it. Maybe I will be able to see what other markets provide and if they have better APYs for me, but I am welcome with the version thing. I am honestly not sure why this is there again, why does protocols do this without really explaining what the versions are or how they make things better for me, or why I should care about it as a new user, ok I switch to see what is in version 2, I still see similar markets like in version 3, then why are they separated, confusion sets in</p><p>Well, if there is a version 3, it has to be the most updated release (at least in my head of assumptions because this wasn’t clearly explained by Aave). So I&#39;ll stick with the latest update version 3 all the way. 🎉.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bRbmW4kNhFgaEUUF7m_g0Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vi3kibZSlXwVbBSGlNPCKw.png" /></figure><h3>What market should I work with</h3><p>I’m very careful how I spend my money, and I would love to know what I am heading into before I commit my money, so I would love to know more about the markets.</p><p>I searched for a while to see if there was a way to know more about this Avalanche market I was on, but I found none. After a while of searching, I got to realize there was a market tab at the top, so I made the switch.</p><p>Now it’s beautiful that they thought of giving me the ability to see information about a market to help curious investors. As much as this is good, it can be better, so for a user who is engrossed in your product, his field of vision is maintained on the body of the platform (that is, everything under the navigation), so my focus to find anything is usually in that body, except I am ready to change attention completely to another section of the platform before my head goes to check the navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j2VuZnHYYCsskvqjJqXURQ.png" /></figure><p>So a way to have helped me find access to the market information and optimize my experience was to give me a way to access it in my field of vision and make it accessible and easy to recognize.</p><p>So I placed a little component that says market details this is enough hint to know clicking this would let me know more and this can lead me to the Market tab and at the same time it&#39;s in my field of focus</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S3fqd_ARd9cqJjaVSAbUTA.png" /></figure><h3>The market info</h3><p>This seems very easy to understand and conveys the message to me in a straightforward manner. I get to see the market size, the funds available to trade, and the total borrowing. With this data, it is easy for me to decide if this is a good market to trade or now</p><p>And in addition, I get to see the tokens involved in this market and can access details about them. I must say Aave understands how to ease the minds of their users</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yDIkQN4l_VwDtKghtBmc2A.png" /></figure><h3>Time to know more about the assets</h3><p>So I click on more details to see more info on the assets on the Avalanche network, and I must say this is very comprehensive and detailed, and inclusive for the users who just need surface data and the experts who want to know deeper about studying the charts</p><p>Also, they give me access to buy the token this saves me a lot of stress in wondering how I would purchase the token, this just made life a whole lot easier for me</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qnuzXR03ETtBJGksDYWRdw.png" /></figure><p>But one little thing: though I am buying with Fiat, what is Fiat🤔? (Just kidding, I know what it is, but I sure as hell know a lot of people don’t) so how about we keep things simple, sometimes fewer words can be more explanatory than more words, so how about we just try to Buy Some ETH</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w8Qa7QfUYmfSGHNARp0agw.png" /></figure><h3>Supplying some tokens</h3><p>Well, after my exploration, I decided to supply some ETH as I felt more comfortable with the APY, so I clicked the supply button. The interface was clean, easy to digest, and very informative at the same time. This was beautifully done</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p86oWUcBXSf1_DX7NhnVUw.png" /></figure><h3>Completing my supply</h3><p>Well, ETH scared me with their gas prices, hurray ETH, but nevertheless, I found a good token to supply, and that was MATIC. But that’s not what I loved here; what I loved was Aave giving us the ability to add the token to our wallet. Now, a lot of times most tokens involved in a protocol lending might be a wrapped version, and this might not be immediately available in my wallet, and you would not be able to know how well your token is performing if it’s not in your wallet.</p><p>You always have to be going to the platform you supplied to, but seems Aave has us in mind and saves us the stress, and provides us a way to track the token directly in our wallet 🔥</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xSpOHBSr8ef-tp_BGV1Kcw.png" /></figure><h3>Supply works, let&#39;s try borrowing</h3><p>So after a successful supply, as a happy user right now I decide to try my hands on borrowing it works smoothly and like the supply modal it gives the necessary information and keeps it simple and not overwhelming.😍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZX5E2pvm_TDW3f5I0F-Fjw.png" /></figure><h3>Overview of my actions so far</h3><p>After supplying and borrowing, the first set of cards shown to me are my supply and borrow tokens, along with the necessary details about them and actions that can be taken on each.</p><p>I don’t need to start trying to scan through a list of tokens to see the one I have taken actions on, it displayed as what whats most important to me first before seeking to make other actions on other tokens</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I0YEVuzGlGETCq0zJBno0Q.png" /></figure><h3>Some hidden gems</h3><p>One hidden gem I love about Aave is the ability to switch wallets. Most protocols I know just tell you to disconnect, then you get to reconnect again to a new wallet; that extra click has been taken away by Aave.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tz31RECD37KrbeR_e4iMTg.png" /></figure><h3>Test mode</h3><p>The fact that this is provided lets me know that this is a platform that aims to earn my trust. First, I might not be willing to stake my money in something I am not sure of, and I might want to see the value it has to offer before investing in it.</p><p>The test mode helps with that and provides tokens with which fake money can be given to me for testing purposes only; if I am comfortable with it, I can switch to the live mode and use real funds.</p><p>This is a good business tactic by showing me the real version first so I can invest and also gives me the ability to switch to test in case you want to trust us first that this works</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f9ZmCn22c3HV3d8dwRV6VQ.png" /></figure><h3>Getting me some fake money</h3><p>Another thing I loved was the fact that to obtain the test tokens I was not redirected to a third-party website to get them I could access them from the dashboard on the Aave protocol</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r8ML3tF-AqKjyzZN93_q_w.png" /></figure><h3>Language support</h3><p>Another hidden gem is the language support which would make the product accessible to people in other parts of the world</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vQg78NB5RxD9cp7hQyuDAw.png" /></figure><h3>Overall experience</h3><p>From the landing page to the app, the user experience was very warm and aesthetic. With a few touches in some places, the user experience, especially for Aave, would be golden. The overall compound is an amazing app and its top tier in my books so far compared to its counterparts</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jdI11sOTmHZmlzt4B522vg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52241dd7b0c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/a-ux-walkthrough-of-aave-protocol-52241dd7b0c3">A UX walkthrough of Aave protocol</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The perception of Compound finance to an everyday user and web3 rookie]]></title>
            <link>https://medium.com/design-bootcamp/the-perception-of-compound-finance-to-an-everyday-user-and-web3-rookie-5b689e0e448d?source=rss-3cdf10d6ad9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b689e0e448d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Aiseosa Uyi-Idahor]]></dc:creator>
            <pubDate>Mon, 06 Mar 2023 09:50:44 GMT</pubDate>
            <atom:updated>2023-03-08T05:17:39.234Z</atom:updated>
            <content:encoded><![CDATA[<p>The world of web3 is one that still holds some mystery to the conventional users of web2 and holds at times a different experience from what they are used to, so let&#39;s approach this like a regular person and see what we experience</p><figure><img alt="Compound Hero Section" src="https://cdn-images-1.medium.com/max/1024/1*pehVG91LpvUUGPuLP8FI0w.png" /></figure><h3>Starting with a little intro</h3><p>Compound Finance is a web3 protocol that gives users a way to lend and borrow digital money like Bitcoin and Ethereum without going through traditional banks. It’s like a digital version of borrowing money from a friend or family member.</p><p>People who lend their digital money can earn interest on their deposits, while people who borrow digital money have to put up something else as a guarantee.</p><h3>First entrance</h3><p>My first touch point into Compound after searching for it on Google. I wasn’t 100% sure if wasn’t sure of the URL so I just typed compound web3. And boom the first pop-up was their website, I must say the SEO team is not playing 🔥</p><p>And oh wow the site looks beautiful, simple clean, and straight to the point, I’m loving this. 🥰</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*knJZmFQ9GRGivAoZ8TNqjA.png" /></figure><h3>But is this overconfidence I perceive</h3><p>The most important aspect of your website is the call to action (CTA), Its proper placement and visibility will determine how much your landing page would convert.</p><p>In Compound the CTA has a very unclear description (App) why app, I am on a website, does that lead me to download an app? 🤔, and why is it in a secondary outline state, are you deliberately not trying to draw attention to it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5n8CoJpUWEwAGsfp3i8b7A.png" /></figure><ol><li>The CTA which is the most crucial action on the landing page has been redesigned from being a secondary button to being a primary one to call more attention to it and the black font color instead of white as it passes better on accessibility, and it has been reworded to be more specific on what you are doing</li><li>The cards beneath the borrowing stats looked like they were just visuals and non-interactable. So the CTA on them have been reworked as well to make them standout with the APP word reworded to show the result of the action to be taken</li><li>Also, the market has been made clearer again to make the result of the action clearer and this became a tertiary button as it is an action but in the hierarchy the least we want the users to take</li></ol><h3><strong>Well let us Proceed to the product</strong></h3><p>First, the dashboard looks as beautiful, simple, and clean as the landing page. I’m loving the product even more</p><p>But what’s that Looking for V2? I didn’t even know there was a V1, and besides, I know products update a lot, why are they retaining their V1 when there is a V2 now, what exactly is V1 and V2🤔</p><p>Let me take a look at the V2 out of curiosity</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*uOTMyLZ9StADKDiCGys2EQ.png" /></figure><h3>Yoo chill a bit, let me take a look around</h3><p>I honestly came here out of curiosity to see what the V1 is all about, and now I’m being forced to connect my wallet. This gives off the vibe of making me create an account before having access to the platform. Let me surf around a bit and let me experience the product a bit, and then if I want to carry out any actions, it can trigger the connected wallet.</p><p>I tried clicking on the overlay background, expecting the modal to close, but it didn’t. Well not all of us love the x button on the modal to close it sometimes clicking outside is faster on the web, but well well, I clicked the x but well well let me just connect my wallet anyways</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*2p0Hyif2ntZGK9YlcZhXPQ.png" /></figure><h3>Damn the Reds have taken over my screen</h3><p>So after connecting my wallet, I ran into a giant red banner, so I know there is an error. Now reading the error to know what’s wrong I see please switch to Mainnet, Oh that’s the problem</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*jP1Pj-ae2aqjR7I6Q3YYQw.png" /></figure><p>So I head straight to my meta mask to make the switch but I see that I am already on a Mainnet 😕 so why the error?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*_bJ1InnBPrPhfSg_SCRiJQ.png" /></figure><p>Is there another Mainnet, so I begin switching from all the Mainnets in my wallet and finally Ethereum Mainnet works🎉</p><h3>The Mainnet issue would have been solved easy</h3><p>Remember that your experience isn’t just in the components or in the functionalities working, your language also helps makes things more understandable for everyone and in turn, improves the overall experience</p><p>Just specifying the switch to the Ethereum Mainnet would have solved all these confusions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*EhTgsj3bE9gpxJ8eQm83uw.png" /></figure><p>Now let’s make this even better, how about we make the Ethereum Mainnet a link so when the error shows you can click on the link and it triggers your metamask to pop up so you do not have to manually open metamask. 😉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*XulwfgJaEStwFNlgVNG_xw.png" /></figure><h3>Well everything is working now</h3><p>So I click on a token I want to supply, and I like the fact that the supply activities are grouped, the ability to supply and withdraw</p><p>There is a lot of information I do not understand but I guess these are necessary to understand my supply and borrow standings</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*e5SNMEhHwYWfYpP0mWgVkQ.png" /></figure><p>But to supply, do I know how much I have so I can supply? Based on hierarchy my eye attention is at the top where I can type in, and my Balance is very vital to know what to type in, so why not just show me what I have where I want to type how much to supply, it eases my gaze</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*O3B8NPZrrTLhHzuCQ_1yNw.png" /></figure><h3>Borrow market</h3><p>Well for starters I love how they separated the Borrow market Modals with a change in CTA color, since the contents are very similar it’s easy to make a mistake, especially on smaller screens when you might not easily differentiate by color 🎉</p><p>But like identifies, the contents look similar with little explanation. Why am I having a distribution APY separate from the borrow APY, and what is it for? Would they both contribute to my final APY?</p><p>Well, this is easy but a bit complicated still, maybe that&#39;s why its the V1, I’m sure over there would be clearer. It was a nice time with you V1, bye 👋🏽</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*3CFEgB3H5IMoSWFD0AIaVA.png" /></figure><h3>Let&#39;s dive right into V2</h3><p>The simple layout makes it less overwhelming, and it’s easy to navigate due to the good use of hierarchy. The amount I have called my attention and the actions of supply and borrow and placed in a simple-to-find place making it easy to carry out. This has a simple and less overwhelming feel than V1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*pIzMY1UmpAWFNTjlHRXgaA.png" /></figure><h3>Let&#39;s take a look around a bit</h3><p>So out of curiosity, as this is my first time exploring the platform, I would love to see what it has to offer, so I scroll downwards.</p><p>What do I notice I see some collateral assets, but with a protocol balance of 0</p><p>Is that my wallet balance or the balance I have on the platform? I’m getting confused. Ok that’s fair let me try to add money to the protocol, I click on it and shocker none of the icons works, hmm is it disabled, the color contrast between it and the background gives me that impression but if disabled, why, what do the buttons do anyways what exactly are they</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FQexGqLR8AfWv0fsA_XRDQ.png" /></figure><p>A simple tooltip would have gone a long way, and an alert communicating to me why I can&#39;t add funds, probably I have no funds in my wallet would be better than keeping me in the dark.</p><p>Let’s try the other assets the color of the button looks different from the above maybe this isn’t disabled, I click and shocker it does nothing, and frustration increases.</p><p>Well well let’s keep exploring</p><p>I see a light mode switch and click it, why it’s at the bottom of the screen baffles me, that’s like a footer environment, well maybe they don’t want us switching. But I switch anyways hehe, then the buttons become even less visible to see, they are so blended with the background, this fails accessibility for some folks with bad eyesight</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*klGNFTlE2MqLtIGx-UCc5A.png" /></figure><h3>Ok enough snooping around</h3><p>I kinda preferred the dark theme, it felt more accessible so I stuck there</p><p>Now let’s try the actions that brought me here. I see that I have the ability to Supply or Borrow.</p><p>So let’s try borrowing, oh it doesn’t work, we probably need to supply first as collateral, ok ok makes sense so I try to supply instead</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*z_5kAVR31Daix9tGrXU1QA.png" /></figure><h3>Taking a swing at supplying</h3><p>So I try to supply, I input my amount to supply then click ok, and behold my supply becomes a pending request, huh, why I was expecting a transaction call on my wallet for me to confirm or something</p><p>Hmm, maybe I can chain a lot of supplies then so I try to add a new supply, but I can&#39;t it only enables me to edit my supply. So if I can only have one supply at once, then why the extra step, what use is it to me, ill confirm the transaction in my wallet anyways so the fear of error request isn’t the case here, so why make me have unnecessary clicks</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*PG7zkR4qU8lJNVwNybsUJA.png" /></figure><h3>Supply done, let&#39;s move on</h3><p>After supplying now, I guess I can borrow now, but what happens next, is my borrow button turns to withdraw. Oh that’s good, my money isn’t locked, and I can take it when I need it, I love this, but still, I came here to borrow, where is the button so I can get started</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*j3FFRlyJscuvAoxUavkICA.png" /></figure><p>The supply and withdraw buttons can be merged on one drop down button since they are both of the same function, then the Borrow and repay can also be merged</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*_s-XV9UzkjrVBkKP9xWVjw.png" /></figure><h3>Let me try the withdraw button</h3><p>So after searching for the borrow button and not finding it, I try the other assets and collateral again; maybe that’s what I can borrow now (i know the labels say otherwise, but I’m a man in need here and I’m willing to try everything). And not shockingly, the actions don’t still work, so how do I borrow, please?</p><p>I tried the withdraw, maybe it would have a tab that I can withdraw from the protocol (that may be their borrow slang 😉). Nah it doesn’t work, I can only withdraw what I put in, common</p><p>Well, I’m tired of this, probably i need someone who uses the platform to explain better to me what to do, I’m obviously struggling here 🚶🏽</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*1kIXf7EBTv451kWRhwSJlA.png" /></figure><h3>Overall experience</h3><p>From the landing page to the app was very warm and aesthetic, it&#39;s an amazing project with a fantastic real-life solution. But some valuable touches to the functional experience were a bit rough from the perspective of a beginner. The beautiful feel of the app could be forgotten with the little frustrations here and there which can easily be adjusted. The overall compound is an amazing app and I can’t imagine how much more it’ll grow in the coming years</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZUfbqOwb1BSzvG_uzuDAoQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b689e0e448d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-perception-of-compound-finance-to-an-everyday-user-and-web3-rookie-5b689e0e448d">The perception of Compound finance to an everyday user and web3 rookie</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a DAO and how does it affect us?]]></title>
            <link>https://medium.com/@aiseosauyiidahor/what-is-a-dao-and-how-it-affect-us-31a9e986ee92?source=rss-3cdf10d6ad9e------2</link>
            <guid isPermaLink="false">https://medium.com/p/31a9e986ee92</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Aiseosa Uyi-Idahor]]></dc:creator>
            <pubDate>Thu, 18 Aug 2022 22:06:03 GMT</pubDate>
            <atom:updated>2022-08-19T08:10:22.024Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2DJSEVdZSifRfUIfP6xNWA.jpeg" /></figure><p>The topic of DAOs has been one that has been on the lips of a lot of people especially when it comes to the web3 space with the uprising of various DAOs leaves the questions in people&#39;s minds, what are DAOs and how do they affect us.</p><h3><strong>What is a DAO</strong></h3><p>A DAO stands for Decentralized autonomous organizations. Think of them like an internet-native business that’s collectively owned and managed by its members who operate under a shared goal, giving each member equal say in making decisions. They operate without a central leader or company dictating any of the decisions. They are built on a blockchain using smart contracts (digital one-of-one agreements). The beauty of DAOs is the autonomy that enables them to function on their own.</p><h3><strong>What does a DAO do?</strong></h3><p>Each DAO has a different mission, whether it is single-purpose or part of a larger project, and can be associated with any number of industries.</p><p>Unlike traditional organizations, there is no hierarchy in DAOs. Rather, to align the organization&#39;s interests with that of its members, DAOs incentivize a distributed network of users to achieve their goals.</p><p>By owning and locking cryptocurrencies into a voting contract, users gain the ability to vote on proposals, with the voting weight being proportional to the amount of cryptocurrency locked, and voters are rewarded with additional cryptocurrency for participating.</p><h3><strong>How do DAOs work?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*FM81HqHke1I2gWW3" /></figure><p>The backbone of a DAO is its smart contract. The contract defines the rules of the organization and holds the group’s treasury. Once the contract is live, no one can change the rules except by a vote.</p><p>If anyone tries to do something that’s not covered by the rules and logic in the code, it will fail. And because the treasury is also defined by the smart contract, no one can spend the money without the group’s approval either.</p><p>You can’t just edit the code (the DAOs rules) without people noticing because everything is public.</p><h3><strong>Why do we need DAOs</strong></h3><p>DAOs have a ton of use cases with the majority surrounding organizational management because starting an organization with someone that involves funding and money requires a lot of trust in the people you’re working with.</p><p>Here are a few examples of how you could use a DAO:</p><p><strong>A charity</strong> — you can accept membership and donations from anyone in the world and the group can decide how they want to spend donations.<br><strong>Crowdfunding</strong> — DAOs can help in crowdsourcing funds to support specific goals<br><strong>Ventures and grants</strong> — you could create a venture fund that pools investment capital and votes on ventures to back. Repaid money could later be redistributed amongst DAO members.</p><h3>Examples of DAOs</h3><p>Here are the categories that a DAO can fall into, depending on its structure, modus operandi, and technology:</p><p><strong>Operating Systems</strong>– Standalone platforms that allow organizations to create their DAOs. Key projects include Orca and Colony.</p><p><strong>Protocol DAOs</strong>– Common DAOs are decentralized autonomous organizations that use tokens as a voting metric to implement the protocol and financial changes. Key projects include Uniswap, Maker, Yearn, Synthetic, Curve, and more.</p><p><strong>Investment DAOs</strong>– Supports capital pooling for various DeFi operations and investments. Key projects include The LAO, BitDAO, and more.</p><p><strong>Grants DAOs</strong>– More like decentralized Venture Capitalists with communities, where governance tokens are used to vote on capital allocation. Key projects include Audius Grants, MolochDAO, and more.</p><p><strong>Collector DAO</strong>s– Meant for NFTs and artists to support fractional or complete ownership of art and content. Key projects include Flamingo.</p><p><strong>Service DAOs</strong>– Talent hunting and acquisition model for agencies and individuals. Key projects include MetaverseDAO, DaoHaus, and more.</p><p><strong>Social DAOs</strong>– Decentralised platform for interactions like social networking. Key projects include Seed Club, FWB, and more.</p><p><strong>Media DAOs</strong>-More likes a decentralized news aggregator that is transparent and works in the consumers’ common interest. Key projects include Mirror.</p><h3><strong>Steps to creating a DAO</strong></h3><p>There are three steps to creating and launching a DAO:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OI2c_9Qw52CcgSP6.jpg" /></figure><p><strong>Creating the smart contract:</strong> The developers of the DAO code the smart contract(s) that will dictate the rules of the group and decide on the group’s purpose.</p><p><strong>Raising funds:</strong> DAOs run on their funds, which have to be raised from their members. It’s here that people buy into the group if they support its mission, agreeing to purchase a certain amount of tokens in exchange for a stake. Governance rules can also be established in this phase.</p><p><strong>Launch:</strong> The DAO’s code is deployed onto the blockchain. From here on out, it can only be changed via collective voting by the stakeholders.</p><h3><strong>DAO membership</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/0*L2W_p1fFXCSNC5hl.jpg" /></figure><p>There are different models for DAO membership. Membership can determine how voting works and other key parts of the DAO.</p><p><strong>Token-based membership</strong><br>Usually fully permissionless, depending on the token used. Mostly these governance tokens can be traded permissionless on a decentralized exchange. Others must be earned through providing liquidity or some other ‘proof-of-work’. Either way, simply holding the token grants access to voting.</p><p><strong>Share-based membership</strong><br>Share-based DAOs require more permission but are still quite open. Any prospective members can submit a proposal to join the DAO, usually offering a tribute of some value in the form of tokens or work. Shares represent direct voting power and ownership.</p><p><strong>Reputation-based membership</strong><br>Reputation represents proof of participation and grants voting power in the DAO. Unlike token or share-based membership, reputation-based DAOs don’t transfer ownership to contributors. Reputation cannot be bought, transferred, or delegated; DAO members must earn reputation through participation.</p><h3><strong>Problems with DAO’S</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*XMkhL4l6dj2541vyLks4Iw.png" /></figure><p><strong>Poor Infrastructures</strong><br>Since DAOs are purely digital and decentralized, they often lack a well-developed and efficient infrastructure their traditional counterparts enjoy. Many DAOs have to design the right tooling and infrastructures by themselves before launch, and a bulk of these tools are quite ‘quirky’.</p><p>DAOs suffer from having the right infrastructures for reporting, treasury management, governance, payroll, communication, identity management, etc. Without the right infrastructure to handle these duties, many DAOs may lose members and eventually fail to gain traction.</p><p>However, the increased rate of innovations and collaborations in the Web3 space is gradually helping to solve some of these problems.</p><p><strong>Legal Battles</strong><br>DAOs share similarities with many organizations of today like corporations, non-profits, partnerships (both general and limited liability), and cooperatives. But these organizations are all regulated and governed by the rules of the different countries in which they are founded</p><p>DAOs, on the other hand, are purely decentralized without a particular location, and the rules governing them are not specific to any existing legal structure. Hence, DAOs battle with regulatory issues such as taxation of DAO tokens, treasuries, and investments, how to get insurance on investment, and who takes responsibility for a DAO’s actions. Without a clear system to solve these legal challenges, it’ll be hard for DAOs to gain ground in the physical world.</p><p>Some other firms have proposed some legal approaches for regulating DAOs. However, for now, DAOs can only operate freely within the crypto environment, as attempts to push beyond can lead to serious legal issues.</p><p><strong>Risks &amp; Un-immutability</strong><br>Blockchains may be impossible to hack but the smart contracts that run on them do not completely share the same level of security.</p><p>Many smart contract networks have faced a series of attacks with some protocols drained of millions of dollars sometimes. For example the $120 million hack of BadgerDAO.</p><p>Division within a DAO can lead to fragmentation and result in splits which we have seen with popular crypto networks:</p><p>Additionally, DAOs can stand against the “code is law” crypto ethos many enthusiasts project. An example is the JUNO Network DAO which voted to revoke the tokens of a whale. While the decision was to safeguard the future of the project, it breaks the foundation of immutability on which Web3 is built.</p><p><strong>Complete Decentralisation</strong><br>While this structure has many advantages, it’s not the best way to actively manage corporations especially when decisions that need to be taken require expertise.</p><p>Traditional organizations function with certain hierarchies because getting every employee or member to vote on decisions is highly ineffective and can prove disastrous. Imagine if everyone in an organization needs to vote on the code base a developer needs to use. A large token holder without adequate experience can negatively influence decisions.</p><p>People with experience are needed to make complex and technical decisions. However, many DAOs didn’t anticipate the challenge.</p><p><strong>Purely Profit Mindset</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*OTAm3q6jM8v8pihh.jpeg" /></figure><p>This is a situation where a bunch of rich folks combines to increase their earnings<br>Even with the possibilities, DAOs are bringing to the web3 space, some critics argue that many DAOs are just a bunch of average rich folks combining wealth to increase their earnings without any regard for the fundamentals of decentralization and community.</p><p>But the minimum capital that qualifies one for membership in some DAOs serves as a barrier for many average individuals. Some days set the requirements for membership at $100,000 or more as the case may be. And such figures may be quite expensive for some people to afford.</p><h3><strong>Conclusion</strong></h3><p>There are a lot of questions and unknown futures when it comes to DAOs and what the future holds for it. A lot of newbies face the issues of understanding what DAOs are, how to contribute, and how to even find the DAO that they share like minds.</p><p>These challenges show that DAOs are not all rosy as they seem to be on the surface. While the governance tokens of some DAOs have given investors good profits, you should know that DAOs are not typically investment properties. Rather, they are means of effective coordination in a decentralized environment without the need for many trusts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31a9e986ee92" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>