<?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 Superawesome on Medium]]></title>
        <description><![CDATA[Stories by Superawesome on Medium]]></description>
        <link>https://medium.com/@sprawsmdoo?source=rss-bc871598527------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hIbgjQUeRNW61nL1kvzQmw.png</url>
            <title>Stories by Superawesome on Medium</title>
            <link>https://medium.com/@sprawsmdoo?source=rss-bc871598527------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:51:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sprawsmdoo/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[A Guide to Digital Product Design Roles, Cheat Sheet Included]]></title>
            <link>https://medium.com/@sprawsmdoo/a-guide-to-digital-product-design-roles-cheat-sheet-included-85e6970483e4?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/85e6970483e4</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Thu, 30 May 2019 12:37:45 GMT</pubDate>
            <atom:updated>2019-05-31T06:55:40.243Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on the Heads-Up! blog at </em><a href="https://sprawsm.com/heads-up/working-with-designers/how-i-came-to-understand-the-purpose-of-ui-kits/"><em>https://sprawsm.com/heads-up/working-with-designers/how-i-came-to-understand-the-purpose-of-ui-kits/</em></a></p><p>—</p><blockquote>It can’t be denied that designers have been going through an identity crisis in the past decade or so. Being a designer today is challenging not only because of the job itself, but because of the insecurities that go with it in terms of boundaries of expertise.</blockquote><p>Today, we have people identifying themselves as UI, UX, brand, interaction, visual, product, service, <em>insert-obscure-reference-here</em> designers. There seems to be a need for highlighting all these specializations within what is essentially a single job title — designer.</p><p>So how do we know who does what, and which designer to hire?</p><h3>Activities Required by the Digital Product Design Process</h3><p>In order to make this simple and understandable to the layman, let’s say that the digital product design process assumes the following activities:</p><h3>Understanding Businesses</h3><p>These are processes through which designers learn about the businesses and users they serve, as well as the entire problem space. This encompasses everything from interviewing stakeholders and users, making sense of analytics, studying competition, running workshops, etc.</p><h3>Understanding Users</h3><p>This is the part of the design process focused on creating ways to satisfy user and business needs by identifying challenges, proposing hypotheses, defining user flows, and making wireframes.</p><h3>Interaction Design</h3><p>By defining how things like pages, screens, and elements react and relate to each other, designers are able to make usable, functional flowing experiences which “make sense” to users even without prior usage.</p><h3>Communication</h3><p>Verbal or visual, design’s ultimate goal is to communicate with the subject. Words are powerful, and the less of them there are, the more responsible designers need to be with them. A lot of communication happens non-verbally, and this is where it’s important to be able to command things like form, color, typography, hierarchy, density, etc.</p><h3>Designer Roles Required by the Digital Design Process</h3><p>Now, as far as roles are concerned, going along the same vein let’s limit them to the activities required by the <strong>digital product design process</strong> — so scoping our chart to this design branch only — going from narrow to broad:</p><h3>Graphic Designer</h3><p>Responsible for producing graphic assets from a specification, including icons, illustrations, branding assets, photography edits, etc.</p><h3>Visual/Web/UI Designer</h3><p>Responsible for defining <em>how things look like</em>, and producing visual assets (i.e. screens) used for digital products like apps and websites. These usually come in the form of “mockups” or “comps” (as in “compositions”) where each screen that the user is able to interact with is delivered as an image that the designer produces as a specification for the developers.</p><h3>UX Designer</h3><p>Responsible for understanding how digital products solve user problems and meet their needs, as well as defining how different elements of pages and screens <em>operate</em> in this case, not how they look like.</p><h3>Digital Product Designer</h3><p>Responsible for aligning user needs with business goals, and making a functional digital product. Their job consists of taking both stakeholders’ <em>and the users’</em> interests, and marrying them together in a whole which brings value to both parties.</p><p>Product designers work from a <em>business need or problem,</em> and transform them into <em>opportunities.</em> The output of their work is not necessarily a solid deliverable, and is often realized through other people’s work.</p><p>Now that we have this basic understanding of the requirements we need to satisfy in order to facilitate .a digital product design process, we can create a handy reference chart!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YX2SYvaypduYFhxDKX7zXQ.png" /></figure><p>As you can see, there are design roles that actually encompass other design roles, product design being sort of like an umbrella role. Even though it’s important to note that not all product designers actually partake in what are commonly considered “design activities” i.e. graphic and UI design, many of them do go full circle.</p><p>Lately a role called “service design” has appeared, and it’s scoped even broader, extending its touch-points beyond the product itself, but I have left this out intentionally as I feel it is beyond the scope of this article.</p><h3>So What’s the Difference?</h3><p>It’s really important to be able to tell whether you need a specific kind of a designer for your project. Clients so often come to us requesting “visual” design services — because this is what they consider “design” — <strong>when in fact they need several designers</strong>, or a one-man-show type <strong>product designer</strong>.</p><p>And in case you’re wondering, the difference between e.g. a UI designer, and a product designer can be easily described using a simple analogy.</p><p>Imagine a situation where a scientist is explaining a phenomenon taking place on a massive space and time scale. This thing is something no one could have ever possibly witnessed. The scientist is explaining this to a person whose task is to visualize it, in other words to describe it graphically by producing a deliverable like a painting or a picture, an animated video, or an illustration for a magazine…</p><p>In this dynamic the <strong>scientist is the stakeholder with domain knowledge,</strong> and the <strong>person tasked with the visualization is the UI designer</strong>. Since the scientist has done all the heavy lifting of understanding the phenomenon, and they are able to explain it so the other person can fully understand it, possibly providing examples and analogies along the way — to provide a brief, in design terms — the person with the task of visualizing it <strong>only needs to execute</strong> based on that which is explained. Hence, hiring someone with a broader skillset would not be necessary.</p><p>If you are a stakeholder with domain knowledge you probably need to hire someone for the <strong>execution only,</strong> provided you are able to transfer that knowledge to this person.</p><p>However, consider the situation where the scientist is replaced with a <strong>stakeholder that doesn’t understand the matter</strong>, they are only aware of the phenomenon. They can’t explain it, they just know there’s <em>something.</em> In this case they need a <strong>person that is able to take that which is known at that time, work to completely understand what’s going on,</strong> in order to be able to produce the visualization, educating the stakeholder along the way.</p><p>This time, the stakeholder is coming in with nothing more than a problem, and needs a person with a broad enough skill set, capable of not only executing on a very specifically defined task, but solving the entire problem. <strong>This person is a product designer.</strong></p><p>If you are a stakeholder without or with limited knowledge of the problem space, you need a <strong>product designer,</strong> and possibly other designers depending on the product designer’s abilities.</p><h3>Complexity Necessitates Specialization — A Little Bit of History</h3><p>The design industry was fine, and its roles well defined just a couple of decades ago. Design was a part of advertising and marketing, and its use and place were well known within these industries.</p><p>I personally see the <em>identity crisis</em> starting about the time a designer could find full time work, doing only UI design — designing for screens — which means right about when digital products appeared. Up until this point the word “designer” was simply synonymous with “graphic designer”.</p><p>From this point on, designers working on digital products exclusively started identifying themselves as “web designers” in order to distance themselves from the traditional medium they hail from, and let the world know that even though their profession is <em>rooted</em> in graphic design, their jobs are <em>so different</em> that it requires its own title respectfully.</p><p>On one hand I can understand this need. <strong>People want to communicate very clearly what they do without creating false expectations.</strong> Someone who is heavy on the research and strategy doesn’t want their potential employer or client to think they can do branding just as well — or at all for that matter.</p><p>The field of design has grown so much with the advances in technology, and when we take into consideration that designers finally have a seat at the table — <a href="https://schloss.quora.com/Design-doesnt-deserve-a-seat-at-the-table?share=1">or do they?</a> — we are forced to differentiate and let the world know that <strong>it’s highly unlikely that one person alone can do it all.</strong></p><p>So while I do agree with this sentiment of <em>niching-out,</em> I do take issue with is the naming aspect. Imagine architects — architecture being a highly regulated field, mind you — all of a sudden not being architects, but “facade architects”, or “column architects”. What I’m trying to say is, it’s OK to have strengths, it’s OK to be <a href="https://en.wikipedia.org/wiki/T-shaped_skills">T-shaped</a>, there’s just no need to scope yourself so tight that you niche yourself out of business. <strong>There’s just no need for a role name to be so exclusive.</strong></p><p>If this trend continues we’re going to make people think they need a different person for every different activity in the design process!</p><h3>Design Generalists</h3><p>While this segmentation has been going on, a special strain of a designer formed as a counterculture — <em>the design unicorn</em> that said no to specialization, and decided to focus on doing it all. Vision, strategy, UX, UI, branding, all of it.</p><p>These guys are your typical one-man-show types, and as the name implies consider yourself extremely lucky if you find one, let alone being able to afford to bring one on.</p><h3>Who’s Getting the Short End?</h3><p>The biggest problem that I see here is not with the designers, as they — generally — know what they are talking about. It’s the clients, and the employers that are getting the short end of the stick. <strong>How can we expect them to know whom they should hire? They are not the experts.</strong></p><p>This is a lot of extra work for the client, forcing them to make decisions they may not be equipped to make. Does this project require engaging three different people, or is there one person that can get the job done?</p><blockquote><em>“This candidate says they are an ‘interaction designer and a visual storyteller’, but we’re not sure if we should get in touch, we just need a website. Also, do we need a developer as well?”</em></blockquote><p>Anyone tasked with a simple task of creating a company website has had this cross their mind at least once.</p><p>Segmentation brings another problem to the table apart from confusion, and that’s <strong>increased cost through project management, and knowledge sharing</strong>. It’s a different ball game keeping a team of six in the loop, vs a team of three. Bring remote work into the picture and you have your work cut out for you.</p><p>This is at least one of the reasons why senior positions (i.e. generalists) are so popular with small companies. These companies often don’t have the necessary resources for project management, or established processes in place, so having people that are not just executors of specifications is really valuable.</p><p>Having self-managed people that are able to go in depth on their own in order to solve problems, often gives you a huge market advantage.</p><h3>We Are All Designers, After All</h3><p>We’re all still just designers, but the amount of things that <em>require</em> design today is massive, hence the amount of stuff needed to <em>produce</em> design across different mediums and platforms has grown accordingly. Design is no longer recognized as only the veneer or a finishing touch added as an afterthought (how things <em>look</em>), <strong>but a part of the process which helps people make better things</strong> (how things look, <em>and work</em>).</p><p>It’s not realistic to expect all designers to be competent in all these new aspects of design — hence the specialization — but it’s wise to be educated about which design problems different projects require, and which designers are most suited to solve them if you are the type of person likely to require design services, or work with designers.</p><p>Perhaps our biggest fault is the <strong>lack of authority in the design industry.</strong> There is no <em>milestone</em> one reaches in order to earn a title, so we make them up as we go along.</p><p>Saying you are a product designer just because it’s the new hot thing, when in fact you draw UIs and can stitch them up together, is not doing anybody any favors. You may aspire to be one, but please be sensible about it.</p><p>We need to be honest, up-front and precise regarding our specialization, without sounding obscure and esoteric. We need to do a better job of communicating and presenting our work, so people don’t have to guess what it is that we do.</p><p>Maybe then titles and roles won’t matter as much.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85e6970483e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Came to Understand the Purpose of UI Kits]]></title>
            <link>https://medium.com/@sprawsmdoo/how-i-came-to-understand-the-purpose-of-ui-kits-15796199e064?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/15796199e064</guid>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Fri, 11 Jan 2019 08:49:10 GMT</pubDate>
            <atom:updated>2019-01-11T08:49:10.747Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on the Heads-Up! blog at </em><a href="https://sprawsm.com/heads-up/working-with-designers/how-i-came-to-understand-the-purpose-of-ui-kits/"><em>https://sprawsm.com/heads-up/working-with-designers/how-i-came-to-understand-the-purpose-of-ui-kits/</em></a></p><p>—</p><p>I honestly couldn’t figure out what they were about. I thought OK, they could be used for inspiration or prototyping, but then I realized that even though most of them came fully styled, people were using them as a starting point for their own designs. This is where it dawned on me: they are a shortcut.</p><p>Ever since we started with the practice of creating components within our designs — previously known as style guides, now known as design systems — we would design UIs first, identify patterns, and then create components based on those findings.</p><p>It turns out the prevailing practice today is to start with a full blown library of UI elements, and use them to puzzle together a UI. Than all that’s left to do is to restyle those elements so as they don’t appear to originate from said UI kit, and to fit with the existing branding of the product. Job done!</p><p>I can see how this process can be preferred for MVPs, teams without designers, or prototypes. But to be honest — speaking as a designer — it’s still completely backwards to me.</p><p>I can tell that a lot of designers nowadays are using this approach, because I also think that this practice has much to do with how homogenized the digital product landscape is, visually speaking.</p><p>Few things today seem genuine, meaning that designers rarely start fresh these days, and since there’s so much pressure to ship fast, who could blame them?</p><p>On the other hand, it really bothers me that aids such as these have had such a huge impact on the industry by demonstrating how one can deliver results on a short notice and deadline. This has somehow become the norm and an expectation with employers and clients, and it’s hard to argue over and over again.</p><h4>Have UI Kits Made Everyone a Designer?</h4><p>If the ability to design a usable interface using an UI kit constitutes one being a designer, than sure, we’re all designers. But the truth is that even if anyone can take a UI kit and put together an interface, that doesn’t mean it will be a good interface.</p><p>Unless you know how to design things from scratch you will be severely limited by the number of elements offered by the UI kit, which is a huge issue as you will be shoehorning content into existing elements just because there’s nothing else to use.</p><p>Then it’s things like knowing which UI elements to use for which purpose and in which situation, balancing user needs with business goals, thinking in flows and series of actions and reactions instead of isolated screens, etc. is what separates the professional from the amateur and hobbyist.</p><p>The fact of the matter is, the part of the design process that contributes to the overall user experience is what adds value to the product, while the UI itself is a mere product of that process. UI is a much less valuable — and often overestimated — asset than often thought, especially in designer circles.</p><p>So no, we’re not all designers. But we can all benefit from the tools that exist in these modern times in order to make the most of what we got to work with, and we need to learn and recognize the proper place, and purpose of said tools.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15796199e064" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How “Lo” Can You Go — Let’s Talk Lo-Fi Design]]></title>
            <link>https://medium.com/@sprawsmdoo/how-lo-can-you-go-lets-talk-lo-fi-design-c6bef2a44b1e?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6bef2a44b1e</guid>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 14:59:35 GMT</pubDate>
            <atom:updated>2018-11-27T14:59:35.856Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on the Heads-Up! blog at </em><a href="https://sprawsm.com/heads-up/working-with-designers/how-lo-can-you-go-lets-talk-lo-fi-design/"><em>https://sprawsm.com/heads-up/working-with-designers/how-lo-can-you-go-lets-talk-lo-fi-design/</em></a></p><p>—</p><p>A common deliverable that is expected from a designer would be a mockup of some sort, or a diagram, a site map, a wireframe, etc.</p><p>Now, I look at a lot of design portfolios, and I can’t help but smirk when I see case studies filled with vectorized, polished wireframes or customer journey maps, because I can’t help but notice how utterly fake they are, and how they have clearly been designed for the purpose of the case study showcase itself.</p><p>[div class=”clearfix mt-lg mb-lg”]</p><p>[caption id=”” align=”alignnone” width=”1920&quot;]</p><figure><img alt="Catering demand High Fiderally Wireframe by Masudur Rahman on Dribbble" src="https://cdn-images-1.medium.com/max/1024/0*Mbusf2VIAjMBVZbA.jpg" /></figure><p>Catering demand High Fiderally Wireframe, by Masudur Rahman on Dribbble. Image used only as an illustration, no offense towards the designer.[/caption]</p><p>[end-div]</p><p>Why do I think so, you may ask?</p><p>Well, because I don’t think there are many projects with budgets that allow for such a high fidelity execution on deliverables that are actually very ephemeral in nature.</p><p>Sure, there are valid reasons to up the quality of non-final deliverables, for example when you want to maximize your chances of buy-in from stakeholders higher up, but that’s a whole different case altogether. I am afraid that young designers are starting to believe that they need this level of fidelity in what should actually be their lo-fi design phase, that it’s just ridiculous. Next thing you know, clients will come to expect this as well. At no extra charge, of course because it’s “the industry standard”.</p><h4>Let’s Get it Straight</h4><p>Wireframes, journey maps, site maps, diagrams, those are all thinking tools. They are not deliverables, and you should not treat them as such, unless you have a really valid reason to spend your client’s budget on them.</p><p>These things are not final versions of anything. They are visual aids to our thinking process, and this is why they shouldn’t be considered to be deliverables.</p><p>We’ve never, ever in the history of Superawesome delivered a set of wireframes to a client, and built the final version of whatever it is that we were building to be 1–1 with the wireframe.</p><p>We’ve never created a content map for a new website, that wasn’t changed in some way during the design process.</p><p>The phase during which these things are produced is simply too early in the design process, for a designer to be coming to final decisions on anything. This is why every asset you produce in the lo-fi phase of the design process should be considered <em>an iteration</em> at best. It should simply be an artefact cataloguing your thinking at a certain point in time. Nothing else.</p><p>At Superawesome, we don’t even call, nor consider them a “deliverable”. We don’t even show them to stakeholders unless they are relevant to making a business decision.</p><h4>So, What’s the Problem?</h4><p>Going hi-fi on an asset that’s meant to change is a waste of time. No point in arguing it.</p><p>Let’s take the following scenario as an example. You have onboarded a new client with a new project, and the goal is to design a website.</p><p>You’ve divided the project into phases like so:</p><ul><li>Phase 1: ideation</li><li>Phase 2: UI design</li><li>Phase 3: front-end development</li><li>etc.</li></ul><p>All of the phases have milestones attached to them, and all of them have a set of deliverables that are due.</p><p>The deliverables of the ideation phase include — among other things — a wireframe of each page of the site. You spend days producing these gorgeous assets, delight the client, get sign-off, and move on into phase 2: high fidelity design.</p><p>Now that you’ve dove deeper into the nitty-gritty of the project, you start discovering hidden issues. And not just issues, you discover opportunities you can capitalize on that you weren’t able to foresee! You go ahead and execute on the hi-fi mockups that now differ from the deliverables from phase 1.</p><p>You present your work, and the client tells you that this is not what they were expecting. It doesn’t conform to a previously agreed upon structure and/or layout. Teams down the line are not expecting this, and are working on deliverables of their own, that conform to the wireframes. It is not based on what they have signed off on.</p><p>What do you do in this situation?</p><p>There’s two ways to go about it:</p><ol><li>You go ahead and try to explain how “design is just kind of like that”, and pray to god they have understanding for the hefty chunk of budget you’ve spent on making a pretty deliverable that is now worthless.</li><li>You go back and redo the work according to the deliverables from phase 1, work around the issues, and pass on the opportunity you found out about in the process.</li></ol><p>Which one do you like better? The answer is neither, you shouldn’t be in this position in the first place.</p><h4>The Takeaway</h4><p>Designers should treat products of the lo-fi design phase as temporary, and err on the side of caution if there’s a push to invest a lot of time and effort in them. They are tools to think, and they are meant to be created, thrown away, and created again as needed.</p><p>Lo-Fi design artefacts are an excellent differentiator when you are trying to figure out which kind of a designer you’re dealing with. If it’s too polished the designer is most likely leaning to the visual side of things, so they are playing to their strengths. However if it’s messy, rough, goes deep and covers a lot of scenarios, and it comes on a piece of paper, you are most likely dealing with someone with broader experience in designing things other people are meant to use.</p><p>As an example, here’s how one of the best product designers <a href="https://twitter.com/rjs">Ryan Singer</a> of <a href="https://basecamp.com/">Basecamp</a> ”designs” in the lo-fi phase.</p><p>[div class=”clearfix mt-lg mb-lg”]</p><figure><img alt="lo-fi designs by Ryan Singer" src="https://cdn-images-1.medium.com/max/1024/0*S7S6d7-tNFbxxKQ2.png" /></figure><p>[end-div]</p><p>Feel free to go as <em>lo</em> as you can go with these things. It’s always better to produce three riffs on the same idea, than to get married to one and spend the same amount of time making it look good.</p><p>Use tools that primarily save you time, even if they don’t seem like they belong in a designers arsenal. Spreadsheets? Sure. Notepad? Definitely. Sketchbook. Hell yes!</p><p>Go get ‘em!</p><p>[div class=”text-sm text-quiet mt-lg”]</p><p>Featured image by <a href="https://unsplash.com/photos/tZc3vjPCk-Q?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Hal Gatewood</a> on <a href="https://unsplash.com/search/photos/ux?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>.</p><p>[end-div]</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6bef2a44b1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for Complex Applications, a Case Study]]></title>
            <link>https://medium.com/@sprawsmdoo/designing-for-complex-applications-a-case-study-96934cbc1934?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/96934cbc1934</guid>
            <category><![CDATA[web-design-agency]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Wed, 21 Nov 2018 19:52:44 GMT</pubDate>
            <atom:updated>2018-11-21T19:52:44.752Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a UX/UI case study for a product lifecycle, and manufacturing management web application called <a href="https://aligni.com/">Aligni</a> originally published on the <a href="https://sprawsm.com/work/aligni/">Superawesome website</a>.</p><p>If you are interested in working with us, please don’t hesitate to <a href="https://sprawsm.com/contact/">get in touch</a>.</p><blockquote>Designing a UI for spreadsheet-loving, information-density-obsessed engineers.How bad can it really be?</blockquote><p>When a designer hears the words “product lifecycle and manufacturing management”, they are not exactly overwhelmed with joy. The fact is, they most likely don’t know what you are talking about.</p><p>When we got on board with Aligni, we’ve had quite a lot of research and education on the matter to do ourselves, before we could start redesigning its user interface.</p><p>The most interesting part of this process was getting used to the way engineers are working with user interfaces, and how they value density over clarity. They are information processing machines who call Excel their “happy place”. The mindset switch that we had to make from “making things as obvious as possible” to “we need to fit at least 17 rows into this fold” was quite a new experience.</p><p>Our main takeaway was that Aligni is not a B2C application, and the UI requires people to learn how to use it. And that’s OK.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ffast.wistia.net%2Fembed%2Fiframe%2F7ebvxp0436&amp;url=https%3A%2F%2Fsprawsm.wistia.com%2Fmedias%2F7ebvxp0436&amp;image=https%3A%2F%2Fembed-ssl.wistia.com%2Fdeliveries%2Ff5fcc1d806e853e226b32fe0411b64a14e7cbc1b.jpg%3Fimage_crop_resized%3D960x714&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=wistia" width="960" height="714" frameborder="0" scrolling="no"><a href="https://medium.com/media/422a4b9829b0e9ca41e82e50fde45293/href">https://medium.com/media/422a4b9829b0e9ca41e82e50fde45293/href</a></iframe><p>Once this simple fact clicked, it was like a huge weight fell off our shoulders, and in fact it was a huge revelation for us. We were so used to designing for the lowest common denominator, that we completely disregarded the power users, and power users are standard here. It was a huge relief to allow ourselves certain affordances of advanced UIs.</p><blockquote>The sheer complexity of the application by consequence made the UI itself complex. As soon as we accepted this as a simple fact, we could move the project forward much faster, and deliver a more appropriate, and finally a superior solution.</blockquote><p>We placed a lot of importance on visual consistency in the UI. Considering the target audience, it was only logical for the UI to take the back seat, for the actual data to be able to surface.</p><p>In cases like this it is entirely possible to fall into the trap of overhomogenization of the UI, sometimes to the point of confusing users so much that they lose orientation and can’t figure out quickly which screen they are on. Fortunately we were able to utilize illustrations, and in some cases color-coded iconography in order to make things more visually interesting, and more easily identifiable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xXXGvkWXQQegzZYg.png" /></figure><p>If there is one characteristic UI element in Aligni it’s the tables. They are all over the place, and they are not always used as simple listing grids, but have various functionalities added to them. More often than not they are editable, and sometimes they contain a mix of editable and non-editable content (e.g. calculations).</p><p>This is why in 2017 we kicked-off a rogue project we dubbed “Tables 2.0”. We got an assignment to redesign a new type of table that is to be applied to a very specific corner of the app, but we wanted to see if there was a better way to handle tables throughout Aligni’s UI, both in terms of presentation, and functionality.</p><blockquote>With tables 2.0 we wanted to see if it was possible to propagate a site-wide improvement, instead of acting acutely which would be obviously a much easier route to take.</blockquote><p>A couple of weeks of work, a whitepaper, and a presentation later, we got the stakeholders on board, and with the help of our amazing front-end team, the new table UI is being propagated throughout Aligni, slowly but surely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lb9AREv7_WyIZA9X.png" /></figure><p>This case study was originally published on the <a href="https://sprawsm.com/work/aligni/">Superawesome website</a>. If you are interested in working with us, please don’t hesitate to <a href="https://sprawsm.com/contact/">get in touch</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96934cbc1934" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Be the Client, at Least Once]]></title>
            <link>https://medium.com/@sprawsmdoo/be-the-client-at-least-once-eece28096778?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/eece28096778</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agency]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Fri, 16 Nov 2018 14:33:59 GMT</pubDate>
            <atom:updated>2018-11-21T21:41:27.831Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on the Heads-Up! blog at </em><a href="https://sprawsm.com/heads-up/design-business/be-the-client-at-least-once/"><em>https://sprawsm.com/heads-up/design-business/be-the-client-at-least-once/</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/0*uv0PWTy72NqfrbfE.png" /></figure><p>As an agency specialized in design, which is just one of the aspects that need to be covered in order to get a product to market, we too often find ourselves operating in a bubble, in our own problem space ignorant of the big picture and the problems visible to our stakeholders.</p><p>A couple of years ago I have identified this to be a big hurdle, stopping us from engaging with our customers as true partners, instead of just vendors.</p><p>We knew how to empathize with the people using the products, but we never learned to empathize with our stakeholders.</p><p>This is rather strange when you look at it, as we spend far more time with the stakeholders, compared to the time we spend interacting with users. Yet it simply didn’t occur to us to take their position into consideration, and see things from their angle during the design process and in fact throughout our relationship.</p><h4>It’s the Communication, Stupid</h4><p>I believe that most of relationship issues have their root in communication, or a lack thereof. Whenever we don’t communicate enough, use the right tone, or refuse to put in the time to understand what’s behind the words, we end up in a conflict. This is particularly true with written communication where the subtle nuances of tone, and gesticulation are lost. This has lead us to many hours spent ironing out differences, putting out fires, and making peace.</p><p>Finally, I have realized that we simply didn’t know much about our stakeholders’ positions when we are working together. We saw them as “owners”, entities which are there to pay the invoices and make decisions. So what happened when we didn’t agree with those decisions? We got bitter. We thought they just want to mess with our work. They thought they knew better than us.</p><p>There was conflict.</p><p>Sadly, the fact that we are working with so many first-time founders and stakeholders, they — having no previous experience working with designers — were in the same position as we were. It made design work this weird battle for who gets their way, instead of a collaborative, ordered process.</p><p>So, how do we solve this problem, then? How do we empathize with the founders, product owners, and decision makers? How do we figure this out?</p><h4>Superawesome, the Founder</h4><p>We figured that the best way to learn about our stakeholders’ viewpoint is, of course, to become one. We set out to create a product we were to get to market.</p><p>Yikes.</p><p>While this was primarily “just” an exercise in order to better our agency’s relationships, we went all in.</p><p>This process took all, but not limited to below:</p><ul><li>identify an opportunity we’re able and interested to exploit,</li><li>analyze the market and and the competition,</li><li>design a product according to the market’s needs and predictions,</li><li>employ developers and work with development agencies,</li><li>calculate finances,</li><li>prioritize features according to their business value vs. user needs,</li><li>figure out a go-to-market strategy,</li><li>take the product from MVP to V1, to V2,</li><li>provide support to users,</li><li>do ongoing maintenance.</li></ul><h4>What We Learned</h4><p>Eventually we ended up selling the entire product (long story…), but needless to say this was a massive undertaking, and in the end the value that we were able to extract from the experience was amazing.</p><p>The biggest takeaway was that after doing this, we were far better equipped to understand, and talk to founders we are collaborating with.</p><p>We understand their pains much better, and thus we know how to talk to them and how to process their feedback. We can provide a better service because we now know the ins and outs of getting a product to market and supporting paying customers. We have first-hand experience with aligning business goals with users’ needs.</p><p>We realized that we were doing a disservice to our clients by focusing all our attention to the people using the products and so fiercely advocating for user needs. We now knew that we should take the business requirements into account as well, and advocate to make them work with user needs in unison, instead of them being at odds with each other.</p><p>If we can satisfy the business requirements by designing a product that will in turn satisfy its users’ needs, and we can facilitate this in the form of a painless process between all parties involved, than we are safe in knowing that we are providing the best possible service to our clients.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C3HZCg9hJ0QUKtXR.png" /></figure><p>If you want to read more about this experience, make sure to visit the <a href="https://sprawsm.com/funnel/">product story page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eece28096778" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wicked problems]]></title>
            <link>https://medium.com/@sprawsmdoo/wicked-problems-cb3da34d994?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb3da34d994</guid>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Wed, 07 Nov 2018 09:56:42 GMT</pubDate>
            <atom:updated>2018-11-21T19:39:40.672Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on the Heads-Up! blog at </em><a href="https://sprawsm.com/heads-up/design-business/wicked-problems/"><em>https://sprawsm.com/heads-up/design-business/wicked-problems/</em></a></p><p>—</p><p>We’ve done quite a few projects that were funded by the stakeholders themselves; I mean, projects that weren’t spinoffs of preexisting profitable businesses, but were literally funded by the founders’ personal capital. And we’re happy to do them, they are very interesting to work on as you get amazing involvement from everyone, they are dynamic, and interesting because they are exploratory by nature. People came to us with a budget and a task to explore a certain opportunity and see if there’s potential for business, what’s not to like? It’s almost too perfect in its naiveté.</p><p>And this is where it gets tricky.</p><p>The sheer fact that the founders’ personal capital is used to fund the project makes the team vs. stakeholders dynamic completely different. By default things are much more personal from the start.</p><p>Due to this level of personal involvement from the founders, there is a high chance for the project to suffer from any or all of the following:</p><ul><li>issues with delegation of responsibility and problem ownership,</li><li>trust issues,</li><li>avoiding essential parts of the design process like testing or research,</li><li>inability to commit to a goal, direction, or process,</li><li>etc.</li></ul><p>This is why when a project shows any or all of these signs, I call them <a href="https://en.wikipedia.org/wiki/Wicked_problem">wicked problems</a>. It becomes impossible to make progress due to ever-changing scope or specification so you feel like you’re stuck on a treadmill, frustration levels are high, and there’s that ever present feeling of time passing by, and money being spent. A situation no one wants to be in, yet there we are.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBAomAwIwxm8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBAomAwIwxm8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBAomAwIwxm8%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d4df4f1f25029115ccdae8c072a97188/href">https://medium.com/media/d4df4f1f25029115ccdae8c072a97188/href</a></iframe><h4>How to avoid a wicked problem project</h4><p>Considering it is your task to qualify the project, it is essential for your judgement call to make sure there are no red flags concerning a couple of key factors.</p><h4>Financials</h4><p>Make sure that the stakeholders are financially stable, that’s a given. People don’t handle things the same when they are burning 1% vs. 50%, or 90% of their savings. Ask how are they viewing the project; an investment? An expense?</p><h4>The human factor</h4><p>Obviously, we are not all the same, and we all handle stress differently. Try to find out how important this project is for the stakeholders. Is this something they are doing on the side without putting too much pressure on it, or are they considering it their big break, or God forbid their saving grace? How busy are they? Do they have a full time position somewhere, and how stressful is that job? Because that stress can and will spill over.</p><h4>Experience</h4><p>Are they maker types, or investor types? How entrepreneurial are they? How much experience they have in product design and management? Have they worked with designers before? All this will affect how much hand-holding you will need to do during the project, and it affects everything from your bottom line, to overall team atmosphere and relationships.</p><p>After you’ve gathered all the information you can, in order to make your call try to label the opportunity as <strong>high risk</strong>, or <strong>low risk</strong>.</p><p>An example of a <strong>high risk opportunity</strong> would be something that has to work out, otherwise there will be negative consequences to the stakeholders. If this is the case it’s a good idea to keep these projects on a “tight leash” so to speak, meaning insisting on a bigger advance payment, and a tighter billing schedule if you have any doubts in the health of the stakeholders’ financials.</p><p>A <strong>low risk opportunity</strong> might be a research, exploratory project where any outcome is valuable to the stakeholders; i.e. if it’s a success it validates their assumption and they can pursue the venture, but if its a failure they can still appreciate learning about it so early in the process, so they limit their losses.</p><p>I hope this helps you avoid some complicated situations in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb3da34d994" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Launchpad Back Again]]></title>
            <link>https://medium.com/@sprawsmdoo/google-launchpad-back-again-a4ce5870ab55?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4ce5870ab55</guid>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Fri, 02 Nov 2018 11:51:22 GMT</pubDate>
            <atom:updated>2018-11-02T11:51:22.461Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on the Heads-Up! blog at </em><a href="https://sprawsm.com/heads-up/news-updates/google-launchpad-back-again/"><em>https://sprawsm.com/heads-up/news-updates/google-launchpad-back-again/</em></a></p><p>—</p><p>Technological giant Google in cooperation with <a href="https://www.serbianentrepreneurs.com/">Serbian Entrepreneurs</a> and <a href="https://startit.rs/startap-akademija/#program-sa">StartIT Academ</a>y, Serbia is planning a second five-day event as part of their <a href="https://developers.google.com/programs/launchpad/">Launchpad initiative</a> for startup companies.</p><p>This is another opportunity for the startups in their early phase to learn from the best and meet the experienced entrepreneurs from Google’s extensive network of mentors. In case you missed out on the last event that occurred in Novi Sad, now you have the chance to make things right.</p><p>The accelerator will take place from 5 to 9 November in Belgrade. The second accelerator’s tailored program will now focus on product and market (day 1), UX &amp; design (day 2), marketing (day 4) and business development &amp; growth (day 5).</p><p><a href="https://sprawsm.com/">Superawesome</a> is going to give its contribution by mentoring the UX and design workshops, so we are excited to announce that this time we have our two designers, Tomislava Babic and Dragan Babic, who will be your mentors at this renowned event.</p><p>To have more detailed information about the event, visit the <a href="https://sprawsm.com/">StartIT page</a>. So, we’ll see you there!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4ce5870ab55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Website 2018]]></title>
            <link>https://medium.com/@sprawsmdoo/new-website-2018-6fe184f13bbc?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fe184f13bbc</guid>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Tue, 30 Oct 2018 11:32:41 GMT</pubDate>
            <atom:updated>2018-10-30T11:32:41.216Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on the Heads-Up! blog at </em><a href="https://sprawsm.com/heads-up/news-updates/new-website-2018/"><em>https://sprawsm.com/heads-up/news-updates/new-website-2018/</em></a></p><p>—</p><p>We never redesign the website until we decide it’s no longer doing its job. We may perform some minor cosmetic tweaks over time, but a general overhaul is due when we feel we’re different than how it represents us.</p><h4>The changes</h4><p>In the past two years there was a lot of change for us. And by the way, when I say “a lot” I mean it in the context of the glacial pace we choose to implement change here at Superawesome. So by normal standards it wasn’t turbulent at all, but for us there’s a lot of “new”.</p><p>By far the biggest change is that our <a href="https://sprawsm.com/about/">team grew</a>. Marija joined us as an account manager/COO/project manager of sorts about a year ago, as I personally stepped down from day-to-day operations. I still sort of feel like I’ve handed her a hot potato, but she’s doing an amazing job of learning as she goes, and we’re very happy she’s with us. Another addition to our roster is Tomislava who joined us in order to strengthen our design ranks and we’re lucky to have her.</p><p>The rest of the change was an overhaul of our processes, from the paperwork, to workflows, and the services that we offer and how we offer them. More on this in the future in the newly formed category <a href="https://sprawsm.com/heads-up/design-business/">design business</a>.</p><p>[div class=”clearfix mt-xl mb-xl”]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*gZoexYWNJOw4Xrv2.png" /></figure><p>[end-div]</p><h4>Back to the website</h4><p>The main goal was to take what we have, tone things down, and strip them to the bare minimum. This was not limited to the visual design, but the content as well. Previous website had a main job to be as verbose as possible in order to give the idea to a potential client what they can expect if they were to hire us. This resulted in a lot of content, and the reactions were very polarized — which is in no way a bad thing in my opinion. People either didn’t bother reading it and went on (good, it disqualified a client early saving us time), while other hired us exactly because we went to those lengths and put in the effort to minimize the their unknowns.</p><h4>We are a digital product design agency</h4><p>What our last website didn’t do too well was the positioning. We were <em>designers for anyone and everything</em>. We’ve learned that this generalist approach sort of no longer works for us. This is why we talked a lot about what we want to do going forward, how we want people to see us, and more importantly <em>who</em> we want to work with.</p><p>It was not rare for clients before to come to us saying they need a user interface to be designed, while they actually needed an entire product. Luckily it always worked out because we actually were product designers, we were just misrepresented, and mistook for a UI design shop. With this new website we are consciously representing ourselves as a product design shop, even though we do offer the same services as before.</p><p>We tried to emphasize this new “we’re actually a product design shop” approach by finally publishing a piece describing <a href="https://sprawsm.com/funnel/">our own experience with creating a product from scratch and getting it to market</a> in the hopes to explain that we know the pains of founders, and product owners because we’ve already been there and done that. All good designers possess empathy, but the best ones also have first-hand experiences.</p><h4>Visual design</h4><p>As far as the aesthetics go, we didn’t stray too much from the old website. The color scheme is more-less the same, we kept the gray as our brand color, the purple is there — although in a different shade — and a new accent color for now is the yellow. The entire visual design relies on typography, and this is where we focused the most. Laying out the content in a way that is memorable and inviting — but before all readable — we feel that we are providing a delight to the user, and honestly we don’t feel the need to do much more. Simplicity and minimalism were our goals, and that’s where we went with it.</p><p>[div class=”clearfix mt-xl mb-xl”]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/0*lwPgEtz-o_JzyKKd.png" /></figure><p>[end-div]</p><p>The example above illustrates the kind of typographic layout I am talking about.</p><h4>Portfolio &amp; Case studies</h4><p>Another interesting thing we noticed is that our leads rarely pay much attention to the portfolio, which is sort of baffling. Often we would get a lead get in touch and later ask for work examples stating that they didn’t even look at our portfolio. For this reason — but also because keeping the portfolio up to date is our biggest bottleneck — we decided to go with an overview of our work, by showcasing a list of projects and our contributions we want the potential client to get a solid idea about the work we are interested in doing, and what we have experience with. We found that it’s mostly the designers that are interested in the visuals, so we are now posting those on our <a href="https://www.behance.net/sprawsm">Behance profile</a>. For the rare person out there actually interested in specifics of our work, we’ve pre-selected a couple of our flagship projects, and kept them as case studies explaining what were the challenges, and how we overcame them.</p><h4>The blog</h4><p>Lastly, we’re also introducing changes to the blog. The initial idea was to have the blog as a sort of a hub for all our online activity, and use the social networks as content distribution channels… Yeah, that didn’t work. It turns out that if you turn your social network profiles into automatized channels you don’t get interaction. Who knew! This is why we’re changing our strategy a bit, and keeping the long form content on the blog while posting short form bits directly on social media. We also reorganized the blog categories a bit in order for them to make a bit more sense should someone decide to browse the content that way.</p><p>I am going to wrap it up for now, if you have any thoughts or comments about the new website — and more importantly if you see any bugs — feel free to <a href="https://sprawsm.com/contact/">get in touch</a>.</p><p>✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fe184f13bbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Static vs Dynamic Websites]]></title>
            <link>https://medium.com/@sprawsmdoo/static-vs-dynamic-websites-c3eec1b82a9e?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3eec1b82a9e</guid>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Tue, 28 Aug 2018 10:16:49 GMT</pubDate>
            <atom:updated>2018-11-03T07:14:20.141Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on the Heads-Up! blog at </em><a href="https://sprawsm.com/heads-up/working-with-designers/static-vs-dynamic-websites/">https://sprawsm.com/heads-up/working-with-designers/static-vs-dynamic-websites/</a></p><p>—</p><p>In the early stage of the development you need to make a decision about the technical requirements of the website — meaning, whether you are in need of a static or dynamic one. A static website only uses HTML, CSS, and JS for its functionality and presentation, whereas a dynamic website uses scripting languages executed on the server side such as PHP, Python, Ruby on Rails, etc. Depending on what you expect to do with your website, you should choose the type you need.</p><h4>Static Websites</h4><p>Most of the websites are dynamic these days, but they don’t have to be. Static websites are easy to make, they are more secure than their dynamic counterparts, and are easier to develop. They represent a set of HTML files where each file is actually one page of a website. The downside of it would be that if you want to make changes on your website and that content is identical in several website pages, you would have to make the change for each page separately, which makes it difficult to maintain the site, it’s a tedious work and prone to errors. The maintenance of the site is then in the hands of a professional and the client would have to consider a monthly maintenance fee for the website if they want to have it updated. Moreover, it cannot display dynamic content.</p><p>[div class=”box box-default box-outset mt-md mb-md”]</p><p>[div class=”row”]</p><p>[div class=”col-md-6&quot;]</p><h4>Pros</h4><ul><li>Less complex development.</li><li>Loading time is faster.</li><li>Higher security with this type of sites.</li></ul><p>[end-div]</p><p>[div class=”col-md-6&quot;]</p><h4>Cons</h4><ul><li>Web development expertise necessary to make the changes.</li><li>The content can’t be updated/changed so easily.</li><li>Not for sites such as e-commerce or some forums, as they cannot perform complex functionalities.</li></ul><p>[end-div]</p><p>[end-div]</p><p>[end-div]</p><h4>Dynamic Websites</h4><p>With dynamic sites, on the other hand, you have all the information stored in a database and once the user reaches the site and asks for the information then the server finds the information and collects it while at the same time building a single page for the user, which actually means that each page is generated for each user. It is much easier to make changes or update the content with such sites as they use a CMS like WordPress, which is user-friendly and easy to use. On the other hand, these sites can be slow due to their interaction with the database, insecure as they can get hacked, can be rather expensive to make and are pretty complex since the process for their making requires a longer period of time.</p><p>[div class=”box box-default box-outset mt-md mb-md”]</p><p>[div class=”row”]</p><p>[div class=”col-md-6&quot;]</p><h4>Pros</h4><ul><li>The content generated by the user.</li><li>Easier to update the content using a CMS.</li><li>It has more functionalities and can be used for more complex scenarios (online shops, social media platforms, and so on).</li></ul><p>[end-div]</p><p>[div class=”col-md-6&quot;]</p><h4>Cons</h4><ul><li>More expensive and more complex to develop.</li><li>Greater security risks.</li><li>Loading time may be slower.</li></ul><p>[end-div]</p><p>[end-div]</p><p>[end-div]</p><h4>Which one should I choose?</h4><p>If you still don’t know which type of a website is suitable for you and your business, let me break it down for you and you can finally see where you stand. Try going through these questions and hopefully (if I manage to explain it well) you’ll be able to get your answer.</p><h4>Editing</h4><p>In case you have a smaller website with a couple of pages and you don’t need to change much, you can go with a static website. However, if you want to build up on your site and would like to add additional pages, enable changing and editing or updating your site, you should opt for a dynamic one.</p><p>If you have a static site and you want to make a global change, you need to do it in the code, manually, on each and every page of the website. So if you have a couple of pages, no big deal, but if there are many pages to go through, there is a higher risk you’ll make a mistake or even that you’ll get bored, as it’s time-consuming and mind-numbing. With dynamic sites, this situation is dealt with much faster, as you make the changes in one file — we often refer to this type of file as a “template” — click “save” and the changes automatically spread to other pages as well.</p><h4>User Accounts</h4><p>You want to have a website with the “login” option for your users for whatever reason, the only choice in that case is to have a dynamic site so that the code and the database could communicate properly as static websites don’t have this option at all. So, any kind of “dynamic” or action on the website will determine your choice of the site, there’s no doubt about that.</p><h4>Changing Content</h4><p>Many clients want to be able to change the textual and visual content of the website because they have a lot of things going on since they may have a blog and post regularly or there is a news section on the website which needs constant updating or simply they want to be in control of the activity on the site. The easiest way to do this is through a CMS (content management system) and without ever touching the code and for this you need a dynamic site. If you yourself want to make changes like these on a static website, you definitely need to have a development background or again you can hire a developer to do it for you every time you need something like this to be done. A bit costly, isn’t it? But hey, if it’s not that often, then the safest thing to do is to leave things to the experts.</p><h4>Final Thoughts</h4><p>Not everything is black and white, as I described it. I did it because I wanted to point out the basic division, basic differences, basic characteristics of the websites. However, there is a whole range of static/dynamic hybrid sites in between these two categories, which are neither completely static nor completely dynamic with having elements of both categories. With technological advancement being measured in seconds now, the tendency is towards merging the systems and blurring the once strict lines between something that used to be so clearly defined. Maybe it’s the curse of modern times — the curse of having too many choices, as someone has called it. But I say, at least we have them and thank God for that.</p><p>Anyway, the question you need to answer in the first place is this: do you need a website to be your business card, which will just showcase your digital presence or do you need it to be a tool for growing your business? If the answer is yes to the first one, you need a static website, if the latter is the case, choose a dynamic site. But if you are in the grey zone, where nothing is so clear, talk to your designer and they will have a proper solution for you.</p><p>Cheerio!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3eec1b82a9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Critique Workshop #2: Novi Sad]]></title>
            <link>https://medium.com/@sprawsmdoo/design-critique-workshop-2-novi-sad-91ce63fe19f?source=rss-bc871598527------2</link>
            <guid isPermaLink="false">https://medium.com/p/91ce63fe19f</guid>
            <dc:creator><![CDATA[Superawesome]]></dc:creator>
            <pubDate>Fri, 24 Aug 2018 07:39:01 GMT</pubDate>
            <atom:updated>2018-11-03T07:14:36.654Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post originally appeared on the Heads-Up! blog at </em><a href="https://sprawsm.com/heads-up/news-updates/design-critique-workshop-2-novi-sad/">https://sprawsm.com/heads-up/news-updates/design-critique-workshop-2-novi-sad/</a></p><p>—</p><p>They will question design decisions and give advisory based on business requirements. Get to know their process and learn design techniques by attending this meetup!</p><p>[div class=”box box-invert mb-md”]</p><p>The meetup will take place at the StartIt Center Novi Sad, September 5 2018 at 18:00. Please RSVP at the <a href="https://www.meetup.com/Practical-UX/events/253872674/">official Meetup.com event page</a>.</p><p>[end-div]</p><p>Here is a lineup of UX designers that will lead workshop:</p><h4>Dragan Babić</h4><p>Designing professionally since 2005, doing UX and product design, as well as UI, branding, and front-end. Founder of a small independent design shop called Superawesome headquartered in Novi Sad, Serbia, while servicing clients worldwide.</p><h4>Petar Ačanski</h4><p>Designer with more than 14 years of experience in the industry. He has worked as a developer, as a designer, and as a design lead. He want through freelancing, six years of agency life, and currently working for a SaaS company. Right now he is improving ActiveCollab which is the project management tool used by companies like Nasa, Apple, Nike and many others.</p><h4>Marko Purać</h4><p>Graphic designer and illustrator from Novi Sad. Professionally he’s orientated towards web design which he has practiced within numerous digital agencies for 10 years, for which he has earned multiple awards such as AWWWards, and others. Since 2014 until today his main role is that of a creative director in Themes Kingdom which as of recently operates as an independent design studio as well as a WordPress theme marketplace. Also, he is involved daily in creating products and direction of overall design and photography for the Over streetwear brand, which he has founded in 2012.</p><h4>Arsenije Ćatić</h4><p>Design generalist. I strongly believe in iteration, intuition and hybrid design teams. Honesty, trust, constructive criticism and learning from failure is what keeps me going.</p><p>[div class=”box box-invert mt-md”]</p><p>See you at StartIt Center Novi Sad, September 5 2018 at 18:00. Please RSVP at the <a href="https://www.meetup.com/Practical-UX/events/253872674/">official Meetup.com event page</a>.</p><p>[end-div]</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91ce63fe19f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>