<?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 Dominic Sebastian on Medium]]></title>
        <description><![CDATA[Stories by Dominic Sebastian on Medium]]></description>
        <link>https://medium.com/@dominicsebastian?source=rss-4263b29c2c26------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XKNyLe24hKmzM9OO_cuVeQ.jpeg</url>
            <title>Stories by Dominic Sebastian on Medium</title>
            <link>https://medium.com/@dominicsebastian?source=rss-4263b29c2c26------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:41:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dominicsebastian/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[The rhythm of our weeks]]></title>
            <link>https://dominicsebastian.medium.com/the-rhythm-of-our-weeks-804ce6400f66?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/804ce6400f66</guid>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Mon, 21 Dec 2020 20:18:55 GMT</pubDate>
            <atom:updated>2020-12-21T20:18:55.263Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve found myself in a familiar place recently. Opening Slack at sunrise, responding to emails at dinner, doing busy work before bed. The bookends of the 9–5 have drifted, blurring the boundaries of life and work. Days slip by like this. My weeks are busy but unvaried, a wall of white noise.</p><p>For many of us work is always at hand, with always more to do. Ticking off a todo here and an email there helps us feel like we’re being useful, we have a purpose. Weeks like these are fine if they are rare. A big push to get a project over the line, starting something new on the side. It’s easy for this white noise work week to become the white noise work month, and before long you’re on a slow road to burn out.</p><p>Overworking like this puts all my identity and self esteem into one vessel, and it becomes how I define myself. It has an outsized impact on my mood, which makes me feel too reactive, and to be frank, uninteresting. When this happens I need to look at my week with a different lens. To spot how I can make space for things I want to nurture, and amplify the things I enjoy in life.</p><h3>Reflecting on my ratios</h3><p>So, I could work less (which would have made for an even shorter post), but this is only part of the problem. Working is a default state when I’ve got nothing to displace it, but the white noise work weeks is also a reminder of all the things I’m not doing. I want my weeks to have rhythm and variety, that help create months with balance and fulfilment. Easy and enjoyable things to aim for, but to help be more specific I sketched out a goal of sorts. Things I want to be doing less of, things I want to do more of, and things I need to make space for. All to set a new, more fulfilling balance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W9RtV9S_VpgwI-cu.png" /></figure><p>Some need to happen in a particular location, some can happen anywhere. Some need a lot more energy and focus, others are a way to relax. The art of fulfilling weeks is finding the right balance between these things, and defending their time against the white noise work week.</p><h3>Taking stock of how much time I have</h3><p>Over the years I’ve been a little obsessive over how other people spend their days. Little tidbits of how they find balance and time for the things they are trying to maximise in their lives. I’ve tried Jessica Hische’s Ultra-Schedule, borrowed bits from My Morning Routine, and the simple wisdom of Mr Bingo. For a brief period whilst dating someone in a tax bracket I’ll never be in, even anecdotes from Lunch with the FT. Between artists and financiers, there is a common thread that connects them all. They are very intentional with what they spend their time on, and at which part of their day they do it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DppJxttLXD_QI9Vi.png" /></figure><p>Looking at my days, after a good night’s sleep and other hard commitments, I have about 4 hours free a day. This all falls into one space after dinner, divvied up between work and Netflix. This isn’t my prime time brain time, but is a great home for “make space for” things like reading and creative practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5ft0GTl6kxKm9TMY.png" /></figure><p>Surprisingly, willing these to happen has not helped. For these to actually take root I’ve had to put them where the bad habits start. Leaving a book in progress on top of the TV remote, or making sure the iPad and Pencil charged and ready to use. The more intentional I can be with this, the harder it is for the white noise work week to creep in.</p><h3>Starting my days better</h3><p>I’m most creative, productive and receptive first thing in the morning. The earlier the better. Knowing this, and testing it’s limits, I moved my day back to the unholy hour of 5am. My new “selfish space”. I can work on whatever I want, and not feel like I’m displacing family time or sacrificing other spaces to work on them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CbD3XjPFbmZ7E3Bl.png" /></figure><p>Again this isn’t perfect. Am I thinking and writing with perfect clarity at 5:06? Deeeeeefinitely not. For writing and side projects, these two hours are more than the energy and focus I have in the four after dinner. Like the “hour of sleep before midnight is worth two after”, but in reverse. Selfishly, spending time on myself first makes it much easier to focus and be present in the other spaces in my day.</p><h3>Reflecting on how the week feels</h3><p>The most important space in my week is time to reflect. A handful of simple prompts, it let’s me think about how the rhythm of the week has been. What went well, what didn’t, and what should I change. As with most things in life, it’s far more about the feeling of how things contribute than the exact amounts. This used to be on Sunday night, but I’ve found this more easier first thing Friday morning. That way my weekends are obligation free.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*beKjI7ZCxn-FeS_Z.png" /></figure><h3>Fulfilling years start with fulfilling days</h3><p>I had a CEO once who had a mantra for hitting goals that went “daily, makes weekly, makes monthly, makes yearly”. A former statistician, he thought of this as a numbers game, but the compounding nature of it stuck with me. The time we spend in our days is how we’ll spend our lives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q-icGHl86BawfTip.png" /></figure><p>What I’ve been trying to “maximise” in my life has changed a lot over the years, especially since becoming a parent. The joy is being comfortable with that change, and re-scaffolding my week to support it. For now though, my white noise work week has faded. My weeks have their rhythm back, and I have a process to keep that on course.</p><p>This was originally published on my personal site, <a href="http://considered.design/rhythm-of-our-weeks/">Considered Design</a>. Signup there to get new notes &amp; posts like this in your inbox ✍️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=804ce6400f66" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The necessary exercise in writing]]></title>
            <link>https://dominicsebastian.medium.com/the-necessary-exercise-in-writing-6f812d242e51?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f812d242e51</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[running]]></category>
            <category><![CDATA[practice]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Mon, 10 Aug 2020 21:22:25 GMT</pubDate>
            <atom:updated>2020-08-10T21:22:25.810Z</atom:updated>
            <content:encoded><![CDATA[<p>I was talking to a close friend recently, someone who I think is a very good writer, who helps edit my excessive use of commas in sentences (he didn’t have time for this post), when he said he’s started to think of writing like exercise. A process that feels arduous and unpleasant, but once it’s all done, you just feel better for having done it. Another run under your belt. Another post out in the world.</p><p>It was funny because to me his writing seems effortless. Clever and witty opinions on a wide range of interesting topics. He’s got a nice balance of long and short posts, and for him, doing this on an increasingly regularly cadence is what’s keeping his writing skills in shape.</p><p>My own writing, personal or published, happens very rarely. My personal best is I think is maybe 5 posts in a single year. My signature style is to find a topic I initially find interesting, hash out a first draft, then let it wither and decay in my drafts over the course of several months. Like a neglectful plant owner, apologetically watering a dry twig in a pot once a month, at the same time wondering why it’s not in full bloom.</p><p>Thankfully for my health, I do manage to do slightly more exercise in a year. Current habit is a few runs a week, but a habit I’m happy to break, because as you’ll know if you’ve ever tried it — running is awful. Aside from listening to Off Menu during it, to convince myself through association running is fun, the only thing that has helped it be slightly less awful is varying the types of runs I do in the week. A mix of short runs, long runs and intervals.</p><p>Mondays are my short run days. Running loops around the local oval, it’s a bumbling 5k to ease me into the week. Purely and horribly pragmatic, this morning run is really just for two things. To signal to my weekend brain that it’s time is up, and to condition myself for the longer, more challenging run on Friday. The small joy of this shorter Monday run is I don’t need to think about it. No excessive stretching, no prep, just put my gear on and head out the door.</p><p>My writing never gets these short runs, and it shows. When I’m stumbling through a frustrated attempt at a longer post, it’s not reading about how to be a better writer that’ll help, or give me the stamina to finish it. It’s the habit of getting a few miles on the clock here and there. Small opportunities to get a post out, however long, to break the cycle and release the pressure of finishing something.</p><p>I enjoy writing, so much more than I’ll ever enjoy running, so I’m wary of putting too much structure around it as a habit. Thinking of it like exercise though is the perfect way to quiet the thinking that every post has to attempt to break some personal PB, or be the best exercise I can get. Sometimes a brisk morning 5k is just enough to feel content.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f812d242e51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Hamish, Qwilr’s new Senior Product Designer]]></title>
            <link>https://medium.com/kaleidoscope/introducing-hamish-qwilrs-new-senior-product-designer-dfd5addae385?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfd5addae385</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[sydney]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Tue, 25 Feb 2020 06:17:35 GMT</pubDate>
            <atom:updated>2020-02-25T20:23:56.376Z</atom:updated>
            <content:encoded><![CDATA[<p>For our third post in our meet-the-team series, I’m veeeerry excited to introduce Hamish Williams, who I worked with at a previous startup in Sydney a few years ago.</p><p>As a Senior Product Designer &amp; Front End Engineer, Hamish is able to prototype and explore novel interactive concepts at speed, and directly shape how Kaleidoscope — Qwilr’s Design System—is contributed to and leveraged across the entire product process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WL1RLGBjYcrFQpuR-ilERA.jpeg" /></figure><h3>Tell us about yourself…</h3><p>I’ve always enjoyed making things ever since I was a kid. I think that’s what gravitated me towards design. A natural progression of this was learning how to code, which allowed me to explore not only how a design looks, but how it functions too. I studied Computer Graphic Design at university, which was a combination of graphic design and computer science. After moving to Sydney from New Zealand I worked as a product designer at Smart Sparrow (where I met Dom) for almost 6 years before joining Qwilr.</p><h3>What’s a core value you like to practice in your work?</h3><p>I try to be humble, mindful, and open to change.</p><h3>Horcruxs are a longstanding Qwilr tradition, to symbolise a memory, experience, or value we care about. What’s your Horcrux, and what does it symbolise?</h3><p>I chose a pentapus as my horcrux (as reluctant as I am to reveal one of my horcruxes lest I be defeated in wizard combat). A pentapus is a fictional creature similar to an octopus, but with five arms instead of eight. This one is made by my partner — she likes to make cephalopods (like octopuses, cuttlefish, and squids) as a hobby. Cephalopods are highly intelligent creatures, they use chromatophores in their skin to actively blend with different environments, and are incredibly flexible. When solving design problems I think we should strive to develop solutions that are smart and flexible to change like a cephalopod.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GDaXlF4hYTDCDuaEn0Jv_A.jpeg" /></figure><h3>What’s in your personal toolkit?</h3><p>Excessive amounts of caffeine.</p><h3>Where are you based?</h3><p>The Sydney HQ</p><h3>What do you like to get up to outside of Qwilr?</h3><p>I like to practice Brazilian Jiu Jitsu as a way to clear my mind and keep active. Usually I have a side project or two that I’m working on to explore cool tech or learn something new. Other than that I enjoy playing video games, reading, and watching movies.</p><h3>What are you most looking forward to working on at Qwilr?</h3><p>Exploring ways to push forward the quality of interaction design in the product and working with the team to make some sick design tooling.</p><h3>What advice would you give to someone who wants to do what you do?</h3><p>Just make things. Actually jumping into a project and not necessarily knowing how to solve everything can be a really good way to learn.</p><h3>How can people find more of you online!</h3><p>My website is <a href="https://hamishw.com/">hamishw.com</a>. There are a few social links and contact details there if you want to stalk me.</p><p>As a growing team, we’re always on the search for thinkers, creators, and people ready to make a difference. Take a peek into life at Qwilr and explore <a href="https://qwilr.com/jobs/">our open roles</a> ✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfd5addae385" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kaleidoscope/introducing-hamish-qwilrs-new-senior-product-designer-dfd5addae385">Introducing Hamish, Qwilr’s new Senior Product Designer</a> was originally published in <a href="https://medium.com/kaleidoscope">Kaleidoscope — Qwilr’s Design System</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shortcuts for automated bliss]]></title>
            <link>https://dominicsebastian.medium.com/shortcuts-for-automated-bliss-b11ccf9a0997?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/b11ccf9a0997</guid>
            <category><![CDATA[focus]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[shortcuts]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Mon, 27 Jan 2020 03:13:27 GMT</pubDate>
            <atom:updated>2020-01-27T03:14:04.780Z</atom:updated>
            <content:encoded><![CDATA[<p>Well everyone, I’ve finally done it. I’ve cemented Shortcuts in my life, and I’m happy to say I’m well on my way to automated bliss. I’ve attempted to find this bliss a few times — with IFTTT, with the previously named Workflow, with the rarely working smart bulbs — but after getting the Apple Watch last year, setting complex things like laundry timers was easier, and the need for Syndrome like power ebbed away.</p><p>As 2020 rolled in though, I saw someone using a Shortcut to revert one of the most annoying behaviours in iOS (low battery mode being turned off after it hits 85%), and I started playing around with it again. Maybe in part because I can’t really code, but it’s both empowering and exciting to create Shortcuts, and there is a tinkering aspect to it which is deeply enjoyable. A feeling mirrored by Khoi Vin in <a href="https://www.subtraction.com/2019/12/04/shortcuts-and-screenshots-on-ios/">his recent post on Shortcuts</a> — it’s also easily possible to spend far more time on them that they could possibly ever save you.</p><p>I’ve made a handful I’m using daily now, and think they’re at a place that others might find them useful now too. The music one below was even enough to make me switch from Spotify to Apple Music (currently not possible to automate or shortcut anything with Spotify), and having artwork again to browse through without being pushed to their own discovery sections, I’ve really enjoyed. Once I figure how to host these I’ll include the iCloud links so others can use them too.</p><h3>Focus work &amp; approachable work</h3><p>Getting the right conditions to do focus work is really important to me, and it’s always boiled down to two things; removing as many distractions as I can, and and giving others the signals that I’m doing focus work so I won’t be disturbed. The more clear and repeatable the prompts and routine are for me, the more pavlovian my response is, and the easier I find it to get into that focus state.</p><p>This sounds silly (maybe even sad knowing I come from London), but the best focus prompt I have is rain in noise cancelling headphones. Combining that with no notifications flying into my view, and I’m as distraction free as it’s possible to get (handled by 1–3 in this shortcut).</p><p>Wearing big noise cancelling headphones is a good physical signal you’re doing focus work (although as we know, not aaaalways respected), but at Qwilr we also have distributed teams, so I wanted to be able to signal it clearly on Slack to everyone is most useful to me. I’ve tried this a few different ways before (using a combination of IFTTT &amp; Glitch), but it was really unreliable, and after a few maiden voyages just stopped working altogether. This new setup works perfectly, but to do the Slack shortcuts it runs you’ll need to <a href="https://api.slack.com/custom-integrations/legacy-tokens">create your personal Slack token</a> to replace mine, and <a href="https://api.slack.com/methods/users.profile.set/test">use their methods here</a> to spit out the url with your token.</p><h4>Shortcut steps</h4><ol><li>Select a playback device (useful if I’m wearing headphones or not)</li><li>Plays my Focus playlist (rain track)</li><li>Turns on do not disturb on all my devices</li><li>Updates my Slack status, sets me away, and puts on DND</li><li>Let’s me select a timer for how long I want to do focus work for</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUmfipYKxgcQl5F2kKaIuQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jX_XVVkAYvfkedeJmeKKA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HTBe8MrrZt81DDcxw8-Hiw.png" /><figcaption>The steps to run the Focus work Shortcut, including the Slack api call for setting presence</figcaption></figure><p>To set my slack status was a little more complicated (for some reason I couldn’t get it to work through the same url schemes as above), but found <a href="https://routinehub.co/shortcut/2443">this Shortcut from Jake Bathman really useful</a> (he also has an <a href="https://medium.com/@jakebathman/setting-up-a-slack-app-for-use-with-ios-shortcuts-e8e16b15d0f3">accompanying post here too</a>). His Shortcut let’s you put in a custom text status each time, but as I just wanted to set a specific one each time, I cut a few of the steps out, and now mine looks like this, with a step above this which uses text to set my SlackOAuthToken.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SOq2f9BvWSmbLLMm6YZkZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_B1qYjWqoq57RCrVRwxcQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c5-4o8aC90MI7pZ-ZH2s4A.png" /><figcaption>Using variables and dictionary to set a specific slack status</figcaption></figure><h3>Adding to my Discovery playlist</h3><p>My memory iiiiiis not great, and to help with that I’ve always had a habit of writing down songs I like as I hear them. A personal torture for me is waking up after being somewhere, remembering very clearly I heard a new/great/nostalgic song I liked, but having only maybe a melody of it I will never, ever be able to google and find. The problem before is I’d have this huge list of songs in Things, which I then had to look up in Spotify to play them. With this Shortcut, I’m able to bypass that list and add songs I hear directly to a Discovery playlist. I then have another Shortcut to play this playlist, ordering songs by oldest to newest, so I’m not just replaying the same songs.</p><h4>Shortcut steps</h4><ol><li>Let’s me enter a search query</li><li>Shows me a list of matching song results</li><li>I can select as many matches as I want</li><li>Selected songs are added to my Discovery playlist</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cECQ2WJxFPIOrNDQ.PNG" /></figure><h3>Facetime Roulette</h3><p>Important background context on this one — I find staying in touch with people I don’t see regularly really challenging. I’ve never been great at it, but living in a timezone 11 hours ahead has made it much harder. Part of it is I detest anything that makes something that’s not work feel like work. So the idea of putting a call with a close friend in the calendar so we don’t forget to do it I avoid like the plague. Facetime Roulette is actually an idea for an app I had ages ago, and although it doesn’t have everything (ideally I’d want to bias the roulette to people I hadn’t called in ages etc), this shortcut gets me most of the way there. I’m going to use this for a few months, and if it hold the magical appeal I think having a roulette layer to staying in touch with friends will have, I’ll develop the concept out more into an app.</p><h4>Shortcut steps</h4><ol><li>Grabs a specific contact group</li><li>Orders it by random</li><li>Limits the selection to one</li><li>FaceTimes that lucky roulette winner</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nh3yZigudYKt3iG7.PNG" /></figure><h3>Further play</h3><p>There’s a few other Shortcuts I’m playing with at the moment, but haven’t got quite right yet. All solving the big problems in life — fade out the nursery light and fade in white noise, triggering the office logo to do a rainbow loop on a launch — but I’ll keep tinkering and share them when they’re done. If you’re interested in creating your own, the best places I found were the <a href="https://www.reddit.com/r/shortcuts/">Shortcuts subreddit</a>, and this <a href="https://shortcutsgallery.com/">Shortcuts Gallery</a>. Both buzzing with hobbyist creators, and also very eager to answer questions — enjoy 🙂.</p><p><em>This was </em><a href="http://considered.design/shortcuts-for-automated-bliss/"><em>originally published on my personal site, Considered Design</em></a><em>. To hear about posts first, signup to the newsletter there, at the bottom of any blog post.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b11ccf9a0997" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick wins—Battling designer bias with design components]]></title>
            <link>https://medium.com/kaleidoscope/quick-wins-battling-designer-bias-with-design-components-c3ae07fe0533?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3ae07fe0533</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[components]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Mon, 17 Jun 2019 07:18:20 GMT</pubDate>
            <atom:updated>2019-06-17T07:18:20.310Z</atom:updated>
            <content:encoded><![CDATA[<p>Last month we were getting ready for a new feature to be launched for our enterprise customers. It’s a significant change, and just before getting a final walkthrough from one of the engineers, we were eagerly prepping the red carpet. Halfway through the demo though, we saw something that spooked us. It was just a scrollbar — a windows scrollbar, which has no variant for dark backgrounds — and on our dark UI, it was sticking out like a some horrible Franken-thumb.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*riYgHRTLkfX_bWEww0RWZg.png" /></figure><p>Why was this so unexpected to see? As designers we had a bias to think everyone is using the thing we use, which in our team (<a href="https://medium.com/kaleidoscope/introducing-annie-kuang-qwilrs-new-designer-ff5e6df7509e">until the arrival of Annie!</a>), was exclusively Macs. Mac scrollbars show and hide as needed, and are much more of a background element visually. Because they are normally so invisible to us, most of the time we were just adding vague scrollbar shapes to <em>imply</em> the container was scrollable. Not being the real styling they also weren’t the correct width, and it was forcing another small wedge between intent and execution.</p><p>There is of course a long list of designer biases (assuming everyone has their browser window at the full width and height of their device, short and concise length names and titles, perfectly placed images and profile pictures) but the scrollbar bias at least has one <em>seemingly </em>obvious solution — just build your own custom scrollbar, and it’ll look exactly how you want on every device and operating system. Of course! What’s <em>not</em><strong><em> </em></strong>obvious about this solution though is it’s a very small superficial win, at the huge expense of something much more important. Accessibility and familiarity for the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hUlYenMgObxk0DzVmcY-TQ.png" /><figcaption><a href="https://css-tricks.com/the-current-state-of-styling-scrollbars/">https://css-tricks.com/the-current-state-of-styling-scrollbars/</a></figcaption></figure><p>There are lots of resources on how to create custom scrollbars (the above by CSS Tricks maybe the best up to date example), but they all assume people changing the default scrollbar for personal blogs or websites. Changing that default behaviour in products though, which contain unique UI and containers of all shapes and sizes, and you’re removing an anchor of familiarity. As for accessibility, each change you make is undoing years of work on native OS scrollbars, which are designed to work with different keyboard inputs, spacebars, trackpads, mouse wheels and more. Firmly in the camp of not creating custom scrollbars, we needed a way to include the real scrollbars for both operating systems in our design work.</p><p>After some digging, and through the help of a <a href="https://twitter.com/kitgrose">great person</a> in a <a href="http://aussiedesigners.slack.com/">great slack group</a>, I had the official design UI kits created by Apple and Windows. They are a fantastic resource, but for our use case we needed the components created slightly differently. After a bit of playing around, we’ve now got them as components in our design system, with added states for different scroll positions. Now whenever we design scrollable areas, we’re balancing our designer bias, and are aware of exactly how it’ll look in reality, for all our users. Bonus ball! The states are also named to help us communicate the core states of a design using scrollable areas, in a much clearer way — beginning, middle and end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C05ZPPCqJfBwrzzWLt36Gw.png" /></figure><p>Although we create everything in Figma, we wanted this to be a little resource everyone can get quick value from. <a href="https://dribbble.com/shots/6640381-Desktop-Scrollbar-components?utm_source=Clipboard_Shot&amp;utm_campaign=dominicsebastian&amp;utm_content=Desktop%20Scrollbar%20components&amp;utm_medium=Social_Share">You can download them all here for Figma, Sketch and XD too</a>. We keep things like this in the foundations part of our design system, but rename them to fit wherever makes sense in yours. It’s a small thing, but hopefully with this there’ll be no more getting spooked by scrollbars in the wild, and one less designer bias in the process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3ae07fe0533" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kaleidoscope/quick-wins-battling-designer-bias-with-design-components-c3ae07fe0533">Quick wins—Battling designer bias with design components</a> was originally published in <a href="https://medium.com/kaleidoscope">Kaleidoscope — Qwilr’s Design System</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building the Kaleidoscope]]></title>
            <link>https://medium.com/kaleidoscope/building-the-kaleidoscope-acea8d84ae65?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/acea8d84ae65</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Wed, 12 Dec 2018 03:11:02 GMT</pubDate>
            <atom:updated>2018-12-20T02:23:09.882Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our first step towards a shared product language</h4><p>I feel like we’re in quite a privileged situation at <a href="https://qwilr.com/">Qwilr</a>. We’re an experience led product company, driven by <a href="https://pages.qwilr.com/Qwilr-Principles-gTndRdDyT7mY">principles</a> that we actually live by. Not faded slogans on the wall, or memos circulated by a distant CEO, but something everyone working on the product has direct and shared accountability over. No arbitrary deadlines, unnecessary standing meetings, or processes applied blindly because “FancyCorp” did it. I think most importantly for us, if we’re approaching a launch and it isn’t going to deliver the value we want for our users, we decide not to release it. As a team we care about shipping things we’re proud of — things that we believe are “<a href="https://pages.qwilr.com/Qwilr-Principles-gTndRdDyT7mY">undeniably best</a>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCMhjMiT6IsMzUVNf6Udew.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/VKxWJlA_q6I?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Frida Aguilar Estrada</a> on <a href="https://unsplash.com/search/photos/kaleidoscope?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This luxury is afforded by lots of things. Putting aside the obvious — having founders who created the direction and environment for these principles to take root — a significant factor is the current size of the company. We’re 30 people, nearly half the company work remotely, but most of our product team are based in Sydney. While principles help guide our direction and what we focus on, they become harder to keep a firm grip on in the day to day design and development, as our product velocity is increasing with growing headcount. New perspectives join, the demands of the product change, and defining what feels like “Qwilr” is harder to articulate clearly in what we’re building.</p><p>Our first hurdle towards Undeniable Bestness was the consistency of our most basic UI building blocks, our colour use and buttons. As more engineers joined, more features were worked on, and more buttons were being rebuilt inconsistently, creating a compounding double up of work. It can be hard to argue the business value at this stage of the work, but we know consistency creates better expectations around how our product works, and it’s the difference between something feeling polished and patchwork.</p><p>I know what you’re thinking. Problems with consistency? Time spent on rebuilding? Scaling a growing team? Ahh of course, the answer is obvious. The solution to all of our past, present and future product scaling problems — a design system! Seems like everyone’s <a href="http://danmall.me/articles/distinct-design-systems/">thinking about them</a>, <a href="https://dribbble.com/overtime/2018/11/27/lyft-s-vp-of-design-katie-dill-on-helping-others-unlock-their-potential">talking about them</a>, <a href="https://airbnb.design/building-a-visual-language/">making them</a>, we just need one of those right? In part yes, as we’ve never had a centralised place with all our various code and design components for others to re-use easily. Our first step towards this was in design only, as a Sketch file hosted in Invision, which detailed all of the UI and states as a source of truth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lwD6ykj4kJiNKc457weM0g.jpeg" /><figcaption>Our initial design components—a Sketch file hosted in Invision</figcaption></figure><blockquote><strong>Initial goals</strong></blockquote><blockquote>— make it easy to find during live projects</blockquote><blockquote>— make it clear what all the states of the UI are</blockquote><blockquote>— make it easy to inspect those details, so engineers have the values they need</blockquote><h3>Building a two sided system</h3><p>Having the system in design helped clarify what our UI was <em>intended </em>to look like, but it was divorced from the reality of the development process. Having this system living purely in design meant it wasn’t integrated into the full product process, and taught us something important — we’re solving a much bigger problem than efficiency. We’re scaling our thinking and approach, well beyond just a UI library. We’re embodying our principles in the product and making them accessible for everyone working on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3hXLM48Fs1O89_Q4DCHoKQ.jpeg" /><figcaption>Our updated live design system — live and searchable code components</figcaption></figure><blockquote><strong>Revised goals focusing on </strong><a href="https://pages.qwilr.com/Qwilr-Principles-gTndRdDyT7mY"><strong>clarity through collaboration</strong></a></blockquote><blockquote>— make our core components consistent and up to date across Design and Engineering</blockquote><blockquote>— understand how principles are embodied in different practices(icons, tone, launches)</blockquote><blockquote>— in turn, make it easier to live by our principles in the product</blockquote><h3>Naming our design system</h3><p>With these revised goals, it feels like a lot to try and encapsulate in a name, and as an aside, I am truly <em>horrible </em>at naming things. I have zero imagination for it, and every single cool or creative project name has always been born elsewhere. But, after chewing it over with the team, we’ve decided to call our design system <strong>Kaleidoscope</strong> — as our intent is to allow everyone building the product to contribute their small pieces, which in turn form a kind of magic for the user. All with ease, experimentation, and fun. We want to contain everything from how we generate ideas, to framing feature narratives, to the actual building blocks in code that make them.</p><h3>Sharing as we learn</h3><p>Over the coming months, we’ll be sharing what we learn as we’re building the Kaleidoscope, focusing on how Design and Engineering work together to create value for us and our users. From the broader engineering concepts of <a href="https://medium.com/kaleidoscope/from-idea-to-code-sometimes-it-really-does-take-a-village-153736c345fc">idea to code</a>, <a href="https://medium.com/kaleidoscope/scaling-ssl-certificates-with-kubernetes-and-lets-encrypt-6a683b87cd32">practical solutions we’ve found along the way</a>, and how we’re scaling this system for everyone.</p><p>It’s just the start, but we wanted to start this blog to highlight what I think is a unique benefit of working on the Qwilr product. Design and Engineering collaborating in a meaningful way throughout the process. Particularly as someone managing design, having a space for us to share openly and from multiple perspectives the struggle of marrying intent and execution, I think could be really valuable for others as well.</p><p>You can follow this publication by clicking <a href="https://medium.com/kaleidoscope">here</a>, or follow me on Twitter <a href="https://twitter.com/dominosebastian?lang=en">here</a>. If you’re based in Sydney and want to chat design, systems, or startups, drop me a message and we can grab a coffee ☕️</p><p>️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acea8d84ae65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kaleidoscope/building-the-kaleidoscope-acea8d84ae65">Building the Kaleidoscope</a> was originally published in <a href="https://medium.com/kaleidoscope">Kaleidoscope — Qwilr’s Design System</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The quest for undeniable bestness]]></title>
            <link>https://dominicsebastian.medium.com/the-quest-for-undeniable-bestness-5153832463a?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/5153832463a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[proposal]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Fri, 19 Jan 2018 01:32:13 GMT</pubDate>
            <atom:updated>2018-01-19T01:32:13.160Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wc0uH-4DETd-gI7p2RytQw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/7psXKRl2amU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Matthew Kalapuch</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>To help frame this post, I want to begin by sharing a snippet from <a href="https://pages.qwilr.com/gTndRdDyT7mY">Qwilr’s driving Principles</a>, written by our Founder &amp; CEO, Dylan:</p><blockquote>We succeed not by taking hack shortcuts, not by social engineering or political machination, or short-term hot-air strategies, but by working resolutely and systemically to become the best. And not just the best, but the Undeniable Best, a superiority which once experienced, cannot be argued with.</blockquote><p>In early June this year, my first project as Head of Design was to improve the way you create and manage custom project styles in Qwilr; to discover and design what Undeniable Bestness for this set of features might be. In the past 6 months we’ve completely redesigned how we think about and manage styles, and built an entirely new approach for our users. We’ve tested it internally, have beta users running through it as I type this, with some even using it on their live projects. The problem is it’s still not right — it simply does not meet our standard of Undeniable Bestness. So while I’d love to announce today our amazing and clever new solution, there’s a little more to it, and I wanted to be as transparent as possible as to why we are not launching this feature this year.</p><h3>The starting point</h3><p>Before the redesign, every project you had on Qwilr came with a handful of preset styles to choose from. These presets managed the alignment and colour of that section, the available colours being whatever was set as the global brand colours on your account. What worked really well with this approach was being able to quickly browse styles to see which one was best suited to your content, with minimal decision tax. The main problem, though, was that anything you wanted to edit (either font size, individual item colour or alignment), all had to be done with CSS. It looked something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*saDViXP0pqEV66siUsTHcA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YCH6yid-n8TpvhI4.png" /><figcaption>Menu for browsing style presets</figcaption></figure><p>For a large group of our users, having just a few preset styles without needing to edit anything worked great — you choose Qwilr specifically because it helps to enable better design outcomes with minimal decision making. But for another growing group of Qwilr users, not being able to directly edit and customise styles is limiting. You want it to feel like a natural extension of their brand, and to do this you need better style controls. In this case, Qwilr is likely being used across a larger team, which also introduces the idea of design or brand owners, who want to create styles their team uses without being able to edit.</p><p>A long story short, our users had simply outgrown how we’d thought about custom styles. We needed to rethink how we could create something better: something that empowered the growing variety of teams using Qwilr for their work.</p><h3>Revisiting the core experience</h3><p>Starting this redesign was a good opportunity to understand the mindset users have when starting to use Qwilr. The tools people are most familiar with before switching to Qwilr range from Microsoft Word to Adobe Indesign — and they both act as important framers for how people expect Qwilr to work. Both give very different expectations of how styles are created and managed, and our approach had to meet and leverage that familiarity to how Qwilr does things. For this, we needed a guiding question to help navigate uncertainty throughout the design process, and get us as close as possible to what users really needed. After a few brainstorming and unpacking sessions, we arrived at this:</p><blockquote>How can we make creating and managing custom styles a fast and empowering experience?</blockquote><h3>Rethinking the style editor</h3><p>Our guiding question in place, we started at the hardest area first — the editor used to create new styles. After speaking with a bunch of users, our initial design work focussed on having controls for every element in the block, to expand what could be controlled. This included controls for styling the heading, and separate controls the subheading etc. It made what should feel like a quick thing to change actually feel overwhelming with the choices available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJI_q8GoXJWW3--mu0zTsw.png" /><figcaption>Early UI designs for the style editor</figcaption></figure><p>In some ways this was great, because it surfaced all the controls a user needed to edit style, really minimising the dependency on CSS. In other ways though, it was quite far removed from Qwilr’s design principles. For lack of better wording, it just didn’t feel right to use, and was overcomplicating the process. To help highlight this a bit better, here’s a little insight into our design process, for how we order our ideas when we create new features:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*CRSju2lQVo0cjObk3Ip1vg.png" /></figure><p>Bearing this in mind, we thought about how we can reduce the number of UI controls, without loosing any style control. We started experimenting with how we could group multiple controls into one, so creating styles could be faster, and easier to get good design outcomes. This is quite close to how we as designers think about creating designs for documents and websites, and was a way to keep all the text as part of the same size relationship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h7vcQcBkkRPRi8JH-qbgGg.gif" /><figcaption>Style controls manipulating text</figcaption></figure><p>After testing this round with users, it seemed like a good compromise between good outcomes without going overboard on controls. The feedback at this stage though made it clear we’d still need to expand on our style controls going forward, and being in the same view didn’t give it much room to grow over time. To tackle this, we moved everything into a style editor overlay, which gave the editing experience a little more focus, and gave us important space to grow the feature down the track as and when we needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ypX3Xv1hi9EA8iZAHOtDYA.png" /><figcaption><em>Style editor overlay</em></figcaption></figure><h3>Upgrading the style browser</h3><p>A great (although not unexpected) side effect of being able to quickly create more expressive styles, was a need to improve how we preview those styles, so you can quickly find the one you’re looking for. The previous design had a small thumbnail about half the size of a stamp, which used little blocks to represent the colours and alignment of the heading, subheading and body text. The problem with our design ideas, was we were introducing new sizes for all the text, which made using this mini preview harder to distinguish between similar styles. Here’s an example to highlight the difficulty:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EvKKUIV6tQTqo0zPVVmPHw.png" /><figcaption>Although similar outcome, differentiating between styles at a glance is difficult</figcaption></figure><p>After <a href="https://medium.com/@dominosebastian/introducing-our-all-new-image-carousel-e428d5547849">releasing the new Image Carousel</a>, we thought the carousel would also fit well to browse your styles. Initially we were using mini previews of the block, using demo text shrunken down so you could see how the style might be applied.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dYeHWuNCM2qXABTCP2_URA.png" /><figcaption>Earlier design iteration of the carousel with text</figcaption></figure><p>While this was quite an effective preview, it actually looked really messy and overwhelming when it was open. It felt like a slow, burdened choice, and wasn’t particularly fun to use — it was ignoring our guiding principle of being empowering and fast to use.</p><p>In the end, we settled on re-using the block visualisation, just at a bigger scale to see the differences, with their style names. While it feels visually simpler, and in theory should work well for our varied (and growing) block types, we still think we can do better. Creating a visual shorthand for blocks is challenging, especially when you don’t want to overwhelm with details and choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7PlCg6xKHGY0br0jb32CGw.jpeg" /><figcaption>Latest working iteration of the carousel with blocks</figcaption></figure><h3>Lessons learned</h3><p>The style editor is in a much better place than when we started this project, but along the way while grouping some of the actions, it’s lost a little of the directness users need. The part that’s really missing for it to be it’s Undeniable Best, is this should feel like a superior and faster editing experience, regardless of what users are familiar with. At the moment, it’s not there yet, and releasing this now would be a disservice to those that need it in their workflow.</p><p>While the style carousel feels visually simpler, it’s also still not quite where we want it to be, and has the added complication of needing these previews for all our new (and growing) block types. Once you’ve created your styles, this is the part you interact with the most frequently, so we’re still working on this being a really smooth, enjoyable experience. Something we’ll be putting into the back of our brains over the next few months to chew over, and come back to the problem with fresh eyes and minds.</p><p>To bring us back to the point that started all this reflection, I want to share another snippet from our Principles:</p><blockquote>Undeniable Bestness means being hard on ourselves and have strong personal benchmarks of quality. It means accommodating to a permanent state of dissatisfaction. This dissatisfaction is a good thing. It keeps us productive. It keeps us pushing ourselves forward. Whenever we reach a summit, we’re already looking to the next one.</blockquote><p>I read a great book recently which had an apt analogy about what makes a great artist. They need to be able to hone in and focus on the details of each brush stroke, whilst being able to step back and see how each stroke fits into the larger composition. Internally at Qwilr, the process of designing this feature to meet our principles has helped our ability to take that step back to see the larger view. It’s highlighted areas of our process we’re actively improving, such as prototyping our ideas more thoroughly early in the process, and unpacking the problem with a more user-centred mindset. It’s also helped us design a more meaningful approach to large features like this, so we can turn around and deliver the best solutions to you all, in a way we’re proud to say has achieved it’s true, Undeniable Best.</p><h4>A very special thanks to our users</h4><p>Something I won’t ever get tired of saying is how great our users are. Personally, I want to say a huge, huge thank you to everyone that has helped and continues to help us beta test not just custom styles but all our features. Taking the time and risk of using something new on your live projects, whilst being open and transparent about what’s not working and what could be improved is exactly what guides us in delivering the best solutions we can. Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5153832463a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing our all-new Image Carousel]]></title>
            <link>https://dominicsebastian.medium.com/introducing-our-all-new-image-carousel-e428d5547849?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/e428d5547849</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[unsplash]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Wed, 13 Sep 2017 23:34:30 GMT</pubDate>
            <atom:updated>2017-09-13T23:45:46.554Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*92of_660q6YBS_APXIEMbw.jpeg" /></figure><p>At it’s core, <a href="https://qwilr.com/">Qwilr</a> is a communication design tool. Whilst we began as a way for people to create proposals as beautiful web pages, it’s grown to be used for case studies, landing pages, online brochures and much more. All things that rely on great imagery to be persuasive. The trouble was our image browsing experience hadn’t grown with these new use cases, and needed a lot of love and improvement.</p><p>Well, after wrapping up testing with our <em>fan-tastic</em> beta group, I’m very excited to announce an all new image browsing experience, called the Image Carousel. From today in Qwilr, you’ll now have access to thousands of high-quality and free to use images, without leaving your project, to make your proposals even more beautiful.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYRaBDsNjonU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYRaBDsNjonU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYRaBDsNjonU%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0d4bb222d0f16937b0463641f6ffe76a/href">https://medium.com/media/0d4bb222d0f16937b0463641f6ffe76a/href</a></iframe><h4>How we used to handle images</h4><p>Before, when you needed to add in an image to your project, you’d be presented with an overlay, where you could select one of the images we had in our collection, or upload your own. It looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Oqpz44UU8JsipX0BktvXg.png" /></figure><p>There were a handful of issues with this design. A few were well understood functional gaps, like not being able to search the library, or view images you’d recently used or uploaded. This can really affect repeated use, because each time you wanted to use an image in your project, it felt like you were starting from scratch again.</p><p>These well understood issues aside, there was also a much larger and harder to define issue remaining; exploring the library and playing around with different image options felt like a long, burdened decision process. In any creative work, the longer the design decision takes, the more doubt will start to creep in over the outcome—and that’s the last thing we wanted. We want Qwilr to help facilitate fast, empowered design decisions that users love and are excited to share. As soon as we realised this, choosing great images with speed became the core focus in our design process. Below are a few key parts I’m very proud to share of the new design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQKWnybtuKxLtjqgo2UI8Q.jpeg" /></figure><h4>Collections in context</h4><p>After exploring a few different directions, we found the fastest way to find great imagery was to never leave the project itself. Instead, we could bring up the image library in context, exactly where you were working. With this we could present images grouped by a theme or collection, so trying alternatives is easier. We could cut finding an image down to two clicks, rather than the previous 5. Most importantly though — you could play with variations faster without losing momentum in your work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aqo94LZQLPNCt_ejAYCUsA.jpeg" /></figure><h4>“Shuffle” to find something new</h4><p>Sometimes you don’t know what image will work until you see it, and getting momentum in that early discovery phase is important to get past creative block. With the “Shuffle” button, clicking it puts a new collection at random into the carousel, so you can cycle through different themes faster when you’re stuck on what would work best with your content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GFv2UZhdwrOXKaZiF-5HfA.jpeg" /></figure><h4>Fullscreen overlay for exploring themes</h4><p>Finally, we completely redesigned the fullscreen overlay experience, so it could house your recently used and uploaded images, and allow you to browse images and collections with a little more screen real estate. From here you can also add in any collection you find interesting to the carousel, to see how the images feel in the context of your project.</p><h4>A huge, huge thanks to Unsplash</h4><p>The best part of this announcement is all these images are free, all thanks to our <a href="https://community.unsplash.com/partners/qwilr-unsplash">partnership with Unsplash</a>. In order to know how much this partnership means to us, I think it’s important to understand our mission as a company. The following is taken from <a href="http://blog.qwilr.com/why-qwilr/">Why Qwilr</a>, written by our Founder &amp; CEO, <a href="http://dylanbaskind.com/">Dylan Baskind</a>:</p><blockquote>Qwilr’s mission is to liberate the web from this complexity. To make it a “speakable” language by anybody, anywhere. Rather than going to the web only for very special occasions, to build big complex websites that we expect to last for years, what if we could dash off a beautiful website in just a few minutes?</blockquote><p>For the above to happen, the question we constantly ask ourselves in design is how can users enjoy this speed without sacrificing quality? So far how we’ve achieved this at Qwilr is by starting with the best design defaults, and using simple but guided design controls to quickly achieve the desired outcome. Partnering with Unsplash is really a further commitment to giving our users the best design defaults we can, so they can create something better and faster than they thought possible.</p><h4>What’s next</h4><p>Although this feature is now live for everyone, this doesn’t mean we are done with it. Through beta testing and early rounds of feedback, there’s a few things we are going to be improving over the coming months. And if you have any ideas or feedback around how we could make this better for you, you can <a href="/service/mailto:help@qwilr.com">email us here</a>—we’d love to hear from you.</p><p><em>Qwilr lets you create business documents as beautiful, mobile friendly websites, that are quick to create and impressive to receive. To find out more </em><a href="https://qwilr.com/"><em>check out our website</em></a><em>, and if you want to try Qwilr yourself, you can </em><a href="https://qwilr.com/signup/"><em>signup here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e428d5547849" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Purging my Pocket]]></title>
            <link>https://dominicsebastian.medium.com/purging-my-pocket-b3e81c453f1e?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3e81c453f1e</guid>
            <category><![CDATA[pocket]]></category>
            <category><![CDATA[readinglist]]></category>
            <category><![CDATA[reading]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Mon, 06 Mar 2017 10:26:31 GMT</pubDate>
            <atom:updated>2017-03-06T10:26:31.129Z</atom:updated>
            <content:encoded><![CDATA[<h4>The burden of never completed reading lists, and the products that enable them.</h4><p>Before writing this I had 412 items in my Pocket list. A tiny handful of them I’d actually read. A few just misplaced bookmarks. The remaining? Literally hours and hours worth of neglected reading material.</p><p>I signed up for Pocket late in 2012, soon after it changed from Read it Later. Long after I had iPad apps that delivered RSS feeds in quaint little faux newspapers, and Pulse was ruined for me by LinkedIn — Pocket looked like it had <em>finally</em> solved my reading list problem.</p><p>It was simple to use, elegantly designed, and had feature parity with everything else. I think what swung it for me was the cleverness of the brand. “When you find something you want to view later, put it in Pocket.” I loved it. With my new iPad accompanying me on an hour commute each way to work, it was also the first app I installed that actually did anything useful. The promise of a simple way to manage my reading list.</p><p>Fast forward 4 years, and the problem is I still can’t manage my reading list. A problem that’s not with Pocket at all really. It’s with me, and my terrible link hoarding talents. It’s with my private delusion that just by saving something to read later, I am somehow closer to having read it. Closer to being well informed. Closer to knowing who the latest whoever is.</p><p>The problem that <em>is</em> with Pocket though, is the same problem with every read it later service. Their primary focus is optimising the speed of adding links, so they can surface links similar to that one I’ve saved. None of them have ever focussed on the retrieval side, and obviously couldn’t care less I’m not making any progress on my reading list. Saved a link in Pocket? Here, have an email that contains similar articles. Saved 412 links in Pocket? Here, have an email that contains similar articles.</p><p>So inevitably, I’ve arrived at this point of defeat in my reading list. I have hours and hours of articles I’m never going to get to, and piling on more daily. I have this overwhelming amount of reading obligations nagging away at me, making me feel bad for ignoring them. So I’ve decided to close my account.</p><p>In fear that one of these is so valuable I might regret not reading it forever (a classic symptom of pathological hoarding), I decided to have one final glance through my list. Half of the articles were already dated, expired either in meaning or content. Half were just repetitions of the same article said a slightly different way, presumably because I never got round to reading the original. Clearly not loosing much in the purge, but I wish there had been a way to not have added so much crap in the first place. Then I could have spent more time reading things that mattered.</p><p>Open Chrome.</p><p>Right click extension.</p><p>Remove “Save to Pocket”?</p><p>Confirm.</p><p>Zero reading obligations.</p><p>Peace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3e81c453f1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Personalization starts with empathy]]></title>
            <link>https://dominicsebastian.medium.com/personalization-starts-with-empathy-c295bb90b87d?source=rss-4263b29c2c26------2</link>
            <guid isPermaLink="false">https://medium.com/p/c295bb90b87d</guid>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[instructional-design]]></category>
            <category><![CDATA[learning-design]]></category>
            <dc:creator><![CDATA[Dominic Sebastian]]></dc:creator>
            <pubDate>Wed, 09 Mar 2016 04:22:37 GMT</pubDate>
            <atom:updated>2016-03-09T04:22:37.380Z</atom:updated>
            <content:encoded><![CDATA[<p>In my first year studying Industrial Design at University, we were given a cautionary tale about the cost of not understanding who we were designing for. Meet the <a href="http://www.telegraph.co.uk/technology/news/9951876/Sinclair-C5-voted-biggest-innovation-disaster.html">“biggest disaster in innovation”</a>, the Sinclair C5:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/1*LaNbCLTe-RXqGFkwKu0GnQ.png" /></figure><p>In 1988, the Sinclair C5 went from drawing board to prototype without any market research. Driven only by the founder’s endless optimism rather than by what the public needed, it sold only 5,000 of the 17,000 manufactured. The company went into receivership just few months after the launch.</p><p>Had there been any real thought given to who might have used it, any empathy at all for what they might actually need, this <a href="https://en.wikipedia.org/wiki/Sinclair_C5#cite_note-Cross-4">“notorious example of failure”</a> could have been easily avoided. My lecturer’s final slide on User-Centered Design read “know thy user,” and this tenet has stayed with me ever since, through everything I’ve designed. When I design Learning Experiences, the first questions I ask are, “Who is the Student I am designing for?” and “How can I feel empathy for what they need?”</p><h3>Building off Personas</h3><p>The first practical tool for building empathy in the design process was introduced <a href="http://www.cooper.com/journal/2008/05/the_origin_of_personas">by Alan Cooper in 1998</a>, in his bestseller The Inmates Are Running the Asylum. Personas, as he called them, became a staple in design deliverables, after their effectiveness was proven project after project.</p><p>They’ve gone through various iterations since then, but their purpose has remained consistent. With details such as names, ages, competencies, and brief back stories, personas act as a constant reference of the different types of people you are designing for. As an example, a traditional approach to a persona for a student might look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rtQF1Y2SooRfWr9H.png" /></figure><p>While this traditional type of persona is great for creating surface-level empathy for someone, a persona needs to feel realistic in order to serve as a useful reference to the designer. It’s easy to include too much information without giving thought to the overarching structure. Personas are a great start, but to make them a more effective tool for creating empathy, we need to include more about the Learner’s context.</p><h3>Understand the Learner’s context</h3><p>David Kelley, founder of the Stanford Design School <a href="http://dschool.stanford.edu/">Stanford Design School</a> and <a href="https://www.ideo.com/people/david-kelley">IDEO</a> — both world leaders of human centered design practices — offers <a href="http://dschool.stanford.edu/wp-content/themes/dschool/method-cards/empathy-map.pdf">Empathy Maps</a> as a way to help round out the picture of what our Learners might need. These questions help shift our mindset to who our Learners are, and they provide great insight into what you can create that will help inform the learning design process. The questions are broken down into four categories:</p><ol><li><strong>Says</strong> — What are some quotes your Learner’s have said?</li><li><strong>Does</strong> — What actions and behaviours have you noticed?</li><li><strong>Thinks</strong> — What might your Learners be thinking?</li><li><strong>Feels</strong> — What emotions might your Learners be feeling?</li></ol><p>Even just spending a few minutes answering these questions will give us a clearer, more realistic picture of our Learner than we had with traditional personas. Applying these questions to our previous example might look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FR8MTYaFC24dxkPk.png" /></figure><h3>Design for the extremes</h3><p>Of course you can’t create personas and empathy maps for everyone in the class, and you also don’t need to. Generally speaking, 3–5 will capture the majority of Learners, but you should be conscious of what’s best for your Learning Design project. Too few and you’re probably generalizing the traits too much and losing out on valuable details. Too many and you’re casting too wide a net, and you will lose the ability to produce an effective learning experience. Generally speaking, all Learners will fall somewhere on the spectrum between struggling to understand and struggling to stay engaged:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a2ApgxCVbOzPug28.png" /></figure><p>By designing your learning experience to address these extremes, you’re able to focus on your most at-risk Learners. Although there is no ‘average’ student, creating a few empathy maps for the Learners that fall within these extremes will result in a better Learning Experience for everyone in the class.</p><p>We can’t personalize learning in any meaningful way without having empathy for our learners. Personas and Empathy Maps are simple, practical ways to build this understanding into our projects, and they greatly benefit our ability to design effective Learning Experiences. Reference throughout your Learning Design process to put yourself in the shoes of your Learners, and don’t let your project be the next Sinclair C5.</p><p>To receive our Persona and Empathy Map Template PDF that will help you kickstart you on your next project, head over to <a href="https://www.smartsparrow.com/2016/03/01/personlisation-starts-with-empathy/">the original post on Smart Sparrow</a> and sign up to our new Learning Design Newsletter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c295bb90b87d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>