<?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 Giel on Medium]]></title>
        <description><![CDATA[Stories by Giel on Medium]]></description>
        <link>https://medium.com/@giel?source=rss-b7cf374f053------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ucZFnZIW68D3e4ilf10uzA.jpeg</url>
            <title>Stories by Giel on Medium</title>
            <link>https://medium.com/@giel?source=rss-b7cf374f053------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:27:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@giel/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[On Design Workflow]]></title>
            <link>https://medium.com/mollie-payments/on-design-workflow-a76061c3e4f0?source=rss-b7cf374f053------2</link>
            <guid isPermaLink="false">https://medium.com/p/a76061c3e4f0</guid>
            <category><![CDATA[dashboard]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[sidebar]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[how-to]]></category>
            <dc:creator><![CDATA[Giel]]></dc:creator>
            <pubDate>Thu, 15 Mar 2018 15:06:26 GMT</pubDate>
            <atom:updated>2018-05-16T10:45:46.157Z</atom:updated>
            <content:encoded><![CDATA[<h4>An in-depth look into how Mollie’s Dashboard navigation was designed.</h4><p><strong>Last month, Mollie released a redesigned Dashboard. To accompany the release, we published an </strong><a href="https://blog.mollie.com/introducing-the-new-dashboard-4832bdce8df0"><strong>article</strong></a><strong> about the new product and how we designed it to give our users an intuitive experience while also maintaining scalability for future features. In this article, I’ll go into more depth about the workflow I use and the design choices I made. I’ll show you everything from coming up with what you need, all the way to the final design.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p9vWsQanMvKP48hxXyZSUg.png" /></figure><h3><strong>The Situation</strong></h3><p>As an absolute design geek, I love seeing how a design came together. Checking out a finalised product is awesome but seeing the work that went into the design is something that I can learn a lot from. Seeing this process and being able to follow along from early decision-making, through design iterations, all the way to the final designs, gives you several great insights. It allows you to follow the reasoning of a designer. You can see how a product’s structure came about. It shows you which avenues were explored but dropped. Which darlings were killed, and why.</p><p>Recently, Mollie launched a redesign of Dashboard. This redesign was accompanied by a little article that introduced the new design and talked a little bit about how we tried to make it intuitive, scalable, and clean. The response to both the article and the redesign was very positive. Because of this, I felt this project might be a good one to base a first article about my own flow on.</p><p>In this article, I’ll go into a lot more depth concerning a single, particular point of the recent design, the sidebar navigation. I’ll start with the decision of using a sidebar, then go through all the versions I created, all the way through to the final design. By showing you exactly what I did, in what order, and with what considerations you’ll be able to get an insight into my personal workflow which, hopefully, will either teach you a thing or two, or allow you to give me tips on how to improve it.</p><h3><strong>The Process</strong></h3><p>So, when the decision was made to redesign the old Dashboard, we made an inventory of what needed to be fixed. The main problem we had, was navigation. Over the years, Dashboard hadn’t scaled well with the many features we added to it. Many times, when a feature was done, we still had to find a spot for it in the navigation and we just put it in a dropdown. Eventually, this made Dashboard feel cluttered and disorganised.</p><p>When we had identified the navigation as a main problem, I started exploring the possibilities. There’s several navigation types that could work in our situation. I tried out a top bar, bottom bar, side bar, and a nav bar. Out of all these attempts, the best solution turned out to be a dynamic side bar. We made it dynamic to be able to switch items depending on the organisation that’s selected or available. The account profile is static. But I’m getting ahead of myself. When it was decided to go for a sidebar, I started trying things out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ViTmQRlBicDbaW7u6TREoA.png" /></figure><p>My exploration of the sidebar began with this. At this point I was trying to figure out what our structure should look like and which elements should go into the sidebar. At first, I figured there were 3 essential parts: 2 menu links (Payments and Statistics) and an organisation switcher. The organisation switcher would be able to have submenu items. To start it off (see version 1 above), I put them in the sidebar and tried to find a way to group them, at first trying to separate the organisational items from the payments-related items.</p><p>In version 2 you can see that I realised that I forgot about the account viewer and tried to add it to the sidebar. At this point, I reasoned that because organisations, technically, belong to an account, I put the account viewer above organisations visually as well. This created a problem with the Customers and Item submenu links which I had previously grouped with Organisation. To fix this issue, I moved these submenu links into the main part of the sidebar together with other menu links.</p><p>Because the main part of the sidebar was now getting filled with menu links, I figured I needed to try and see if it was scalable. To do this, I added some more menu links to it. I also tried to find a way to show that there’s a hidden dropdown menu behind the account viewer. The obvious choices to show this are either icons, which look good but aren’t that clear, and text, which is clear, but takes up a lot of space. At this point, neither option seemed worthwhile. When I get stuck on something like this, instead of spending hours trying to find the perfect fit, I just remove them and move on. This allows me to keep up the pace and try out more things.</p><p>I moved on and tried out something else. Perhaps, I thought, logging out in a single click is more important than adding a dropdown menu (see version 6 above). I noticed quickly that that would give me the same problem: should I use text, which is long and might not scale when the name is long, or an icon, which might not be clear enough. Again, I decided to move on and check back later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JIez5Rdx2WmvJibC2A5ssA.png" /><figcaption>One of the early versions of the sidebar, put into the context of Dashboard.</figcaption></figure><p>At this point, I’ve made a couple of versions and tried a bunch of different things. It’s time to contextualise. Generally, I do this whenever I’ve fixed a certain issue or found something that seems to work. Because I’m pretty confident by now that a sidebar is the best option, this is a great time to check it out in context. By doing this, I can check whether a sidebar still works when positioned next to a list of payments, or next to other tabs and screens within Dashboard. Contextualising also gives you the opportunity to check other things. In this case, I checked things like whether black is the right colour, perhaps it should be white or some other colour? The sidebar held up to this test, and black definitely seemed to work, so I moved on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ps0dV51CMSpE-6sv5oNkuw.png" /></figure><p>When I was looking at the sidebar in context, I realised that placing the organisation switcher below the account viewer didn’t make all that much sense, even though it was technically logical. A user account is a static thing, every user only has one, but organisations are dynamic, a user can be connected to just one or multiple. Because of this, having the organisation switcher at the bottom wouldn’t be scalable. In the next iteration, I placed the account viewer at the bottom and it seemed to work (see version 1 above). Again, I tried to work out the icons for the account viewer but left it once more to place it into context (above).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QMiIGMpnzE8o5ezNi_23HQ.png" /></figure><p>This time, placing it into context helped me see that a simple dropup menu might work for the account viewer as well, with two triangles to indicate its hidden state. This felt right so I tried out some more states. I even tried out a white version (in version 2 above), but quickly returned to black. Because it seemed to work for the account viewer, I tried a dropdown menu for the organisation switcher as well. This too seemed like an option that improved clarity without becoming cluttered.</p><p>In the next few versions I tried to find a structure for the tabs: which links should be main navigation and which could be placed out of sight in another dropdown menu. There was also the difference between a website profile and an organisation. A single organisation can have multiple website profiles, should they all be visible in the main navigation? I’m also trying out icons to accompany the links. This would make the list easier to scan and would eventually open up possibilities for a smaller, collapsed navigation.</p><p>Now, in the last version here (version 6 above), I went back and tried to play around with the account viewer again. It’s important to keep trying things, keep moving parts around, see what works and what doesn’t. This is one of those things that didn’t work, so I put everything back as it was and moved on, placing it into context once more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BCMZqjPT4_UxDxE84oROmg.png" /><figcaption>Clean up.</figcaption></figure><p>At this point I was feeling pretty confident about what I had, and I did a little clean up. I revisited all the previous versions, looked at what worked and what didn’t. I put it all in a single mock-up and locked in the structure as well: organisation viewer first, all menu links below that with icons to accompany them, and the account viewer at the bottom. We killed the idea that different website profiles should be visible in the main nav and decided that it would be better to make them filters in the lists. This allowed us to show only the organisations and the account in the sidebar which made for maximum clarity while keeping clutter to a minimum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BhWLOc7jSQP1Fv5XYfs4Fg.png" /></figure><p>Because we’re pretty much locked in now, it’s time to do a real clean-up: revisit your versions, make sure the icons are good, and create all the states, hover, active, dropdown/dropup menus opened and collapsed, organisations switched, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1-fx6MIQCia-vax8HNihpQ.png" /></figure><p>By now, I was basically done but there were still some options I wanted to explore. In particular, I was wondering whether or not I could fit subnav items into the sidebar as well, because some of the pages have tabs. For instance the Administration screen: it’s divided into Balance, Invoices, and Settlements. But how do you make it clear, visually, that some links can be expanded to show subnav items, while others can’t? And how do you do that without creating too much clutter? I tried a bunch of things: icons, no icons, little triangles, a vertical line, colours, dots, etc. In the end, I decided to kill my darling because I felt it would clutter up the navigation too much. Instead, we decided to add a tab bar to the main content screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E3eNW5IW6cedP7XmS4ycug.png" /><figcaption>The final design.</figcaption></figure><h3><strong>Conclusion</strong></h3><p>30+ iterations farther and we’ve ended up with something that feels sturdy, intuitive, and scalable. To sum up the workflow: try to fix a single thing and make a new version for every change you make. Place your work into context often. Keep momentum going instead of getting stuck on a single aspect that doesn’t work, just take it out and work on something else. And remember to revisit your past versions, perhaps there’s something in there that works better than you expected.</p><p>I hope you enjoyed this write-up. Let me know what you think and whether I should do more of these for future projects.</p><p><em>If you already have an account you can check out </em><a href="https://mollie.com/dashboard"><em>Dashboard</em></a><em>.<br>Read our other articles </em><a href="https://blog.mollie.com/"><em>here</em></a><em>.<br>Follow me on </em><a href="https://dribbble.com/giel"><em>Dribbble</em></a><em> for more design work.<br>Sign up at </em><a href="https://www.mollie.com/"><em>our website</em></a><em>, or find us on </em><a href="https://twitter.com/MolliePayments"><em>Twitter</em></a><em>.</em></p><figure><a href="https://mollie.com/features/dashboard"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4wdmCQXASFFJlvzzhBaNfQ.png" /></a></figure><figure><a href="https://www.mollie.com/features/multicurrency/"><img alt="" src="https://cdn-images-1.medium.com/max/706/1*yx3eKGqyRWp8rHcH_oxQEA.png" /></a></figure><figure><a href="https://mollie.com/"><img alt="" src="https://cdn-images-1.medium.com/max/706/1*OPOKlAJMo12MQcDrdttS0g.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a76061c3e4f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mollie-payments/on-design-workflow-a76061c3e4f0">On Design Workflow</a> was originally published in <a href="https://medium.com/mollie-payments">Mollie</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the new Dashboard]]></title>
            <link>https://medium.com/mollie-payments/introducing-the-new-dashboard-4832bdce8df0?source=rss-b7cf374f053------2</link>
            <guid isPermaLink="false">https://medium.com/p/4832bdce8df0</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Giel]]></dc:creator>
            <pubDate>Tue, 16 Jan 2018 13:29:05 GMT</pubDate>
            <atom:updated>2018-05-16T10:16:56.843Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we designed a more consistent and intuitive experience for 40.000+ users.</h4><p><strong>Mollie has a clear focus on fixing the online payment space through better tech and intuitive design. If you’ve ever used our API, I hope you’ve found the experience agreeable. We’ve tried hard to make it as efficient as possible. Now, we’re releasing an entirely redesigned Dashboard, to deliver that same experience. In this story, I’d like to introduce you to the new design and I’ll talk about how we’ve tried to add value for our customers through design that inspires a logical workflow while maintaining scalability. Come take a tour around the design highlights of the new Dashboard.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Z4-iBXekThlTBaCK71Zkg.png" /><figcaption>The new Dashboard.</figcaption></figure><h3>The Situation</h3><p>We firmly believe that providing our users with a calm, intuitive, and efficient working environment is essential. By building a product that is neatly arranged and makes sense, we can help our users be more productive. The less thought that goes into <em>how</em> you’re achieving something, the more focus, there is on <em>what</em> you’re doing. And since there’s so much data in Dashboard, it’s important that we present that in a clear way, to help our users navigate it all easily.</p><p>We felt, however, that over the years, Dashboard had lost some of that clarity. For years, we’ve been adding features and tweaking its design to make it all fit. By now, we got as much out of the old design as we were going to get. That’s why we decided it was high time we took a step back and looked at how it all fit together.</p><p>Of course, before starting out, we decided on our needs and demands: the new Dashboard had to fit in with the new identity we established in 2017 and form a consistent whole with our other touch points, like the marketing website. We also needed a design that doesn’t just hold our current features and functionalities, but one that will also hold any future features we might come up with. This scalability is extra important now, because we’ll be releasing new features and updates at a higher pace than before. The design also had to be familiar enough to be usable by users who’ve grown accustomed to the old design, without too much guidance. Another thing we had to keep in mind: our users range from single-person webshops to Fortune 500 enterprises, and they all use the same Dashboard. You can probably guess that finding a way to encapsulate all of this, was quite a challenge. But as I look at the final product, I think we rose to that challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m5ksUK2Y-BmlWA8Uo0lbDQ.png" /><figcaption>Sidebar, content, and optional inspector in the new and much calmer Payment Detail screen.</figcaption></figure><h3>The Design</h3><p>There it is. As you can see, we’ve made it fit in nicely with our other touch points. To achieve this, we used recognisable colours, typefaces, and icons. We used the same solid colour backgrounds and loads and loads of white space that we also use in the website. This also gives the whole a clean look and feel. And the layout mirrors our website as well.</p><p>Next to making it recognisable, we had to make it scalable. We realised this by dividing the screen into two distinct parts: the sidebar and the content. Let’s dive into those a little deeper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9N21jyFZz5fLqRgjbLG-Nw.png" /><figcaption>Designing the new navigation.</figcaption></figure><h4>Sidebar</h4><p>The introduction of the sidebar is the biggest change we’ve made. This sidebar is always visible on larger screens and turns into a hamburger menu on small screens. It holds the main navigation, the organisation switcher, and the account options. All these elements used to be at the top of the screen, but this positioning had some serious flaws. For one, it really wasn’t scalable. We ran out of space and had to find some creative ways to fit things in, which in some cases resulted in some counter-intuitive manoeuvring to achieve something simple. Changing organisations, for instance, you’d have to go to the dropdown menu below your personal account to get an overview of the organisations you work for and then be able to switch around. It works, but it’s not great. By giving this a dedicated place, we hope to improve the way you navigate around the different organisations. In the same way, navigating around the different parts of Dashboard has been made more efficient.</p><p>Having set up Dashboard with a sidebar, we’ll also be ready for future features. For instance, we’re working on implementing more extensive team management and role dividing settings, at some point in the future. We’ll be able to easily integrate that into the design of Dashboard now.</p><p>Something else we think will help: because the sidebar is always visible, it’ll be easier to block out when you’re working within the content screen. This creates a calmer working environment. On to the content.</p><h4>Content</h4><p>The content portion of the screen is obviously the biggest, and because we’ve moved the navigational options away from this portion, we’ve freed up quite a bit of screen space. We love white space because we think it makes for a peaceful and calm experience and we made sure to keep a lot of it. We cut all this free space up into three distinct parts. The first two parts are the header and the content, these are always visible. The third part is optional: an added inspector within the content part. We think working becomes easier because these parts are used consistently. The header always holds the page title on the left and page actions on the right. The content always has enough room. If the content requires anything in particular, like filters or detailed information, the added inspector is there to provide it.</p><p>Throughout Dashboard, the actions in the header control the entirety of the content. They refresh the data, show a different data set, export the data, etc. The actions in the inspector always manipulate the shown data, they filter it, search through it, or provide extra information. By making this distinction between page actions and data actions consistent throughout Dashboard, we believe using them becomes a more intuitive experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rWFwo1B4Yn9PE43Xmt0Khg.png" /><figcaption>Dashboard for mobile.</figcaption></figure><h4>Mobile optimisation</h4><p>While we were at it, we also took the opportunity to optimise Dashboard for mobile screens. As much as 20% of our customers use Dashboard from a mobile device and we wanted to give them an equally great experience. I already mentioned how we change the sidebar into a hamburger’d menu when your screen gets narrow. In addition to that, at this point the header, the content, and the optional inspector get restructured. The title and page actions are stacked vertically. Below them, whenever visible, comes the optional inspector. Finally, the tables are structured differently to better fit the dimensions of a smaller screen. We think these changes give our users an optimal mobile experience while maintaining clarity and usability.</p><h3>Wrapping it up</h3><p>That, in a nutshell, is how we redesigned Dashboard and how we used a sidebar, consistently recurring elements, and a lot of whitespace to create a clearer, a more consistent, and more intuitive UI. I hope you got something out of this write-up. If there’s anything else you’d like to know, or if you have any comments, don’t hesitate to reach out to me here or on <a href="https://twitter.com/gielcobben">Twitter</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BaEuD_ghWcyxBksdZsF4ag.png" /><figcaption>A sneak preview of the Dashboard marketing page.</figcaption></figure><h3>Next up</h3><p>We’ll continue to fine-tune Dashboard and our other features for clarity and ease-of-use. The design team will ship a new page on the website about Dashboard and its most important features. We’re also working on a page that highlights how our products and features can help global corporations and Fortune 500 enterprises. Our developers are working on some interesting things too, but we’ll let you know about those when they’re ready.</p><p>Do <a href="https://www.mollie.com/contact">get in touch</a> and let us know what you think of the new Dashboard. If you’re looking for an interesting job building the future of payments, have a look at our <a href="https://mollie.homerun.co/">Jobs page</a>.</p><p><em>If you already have an account you can check out </em><a href="https://mollie.com/dashboard"><em>Dashboard</em></a><em>.<br>Or you can sign up at </em><a href="https://www.mollie.com/"><em>our website</em></a><em>, or find us on </em><a href="https://twitter.com/MolliePayments"><em>Twitter</em></a><em>.</em></p><figure><a href="https://www.mollie.com/features/dashboard"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4wdmCQXASFFJlvzzhBaNfQ.png" /></a></figure><figure><a href="https://www.mollie.com/features/multicurrency/"><img alt="" src="https://cdn-images-1.medium.com/max/706/1*yx3eKGqyRWp8rHcH_oxQEA.png" /></a></figure><figure><a href="https://mollie.com/"><img alt="" src="https://cdn-images-1.medium.com/max/706/1*OPOKlAJMo12MQcDrdttS0g.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4832bdce8df0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mollie-payments/introducing-the-new-dashboard-4832bdce8df0">Introducing the new Dashboard</a> was originally published in <a href="https://medium.com/mollie-payments">Mollie</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>