small_Fcsqb5pWQAAzPIK.jpeg

thumbnail_Fcsqb5pWQAAzPIK.jpeg

Adobe acquires Figma, cue the memes 🤪

large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

Still can’t get a UX job? Give up.

large_featuredImage

medium_featuredImage

small_featuredImage

thumbnail_featuredImage

Sticking to UI/UX trends is a losing strategy

<p>Published on <a href="http://ift.tt/2ptItVK">| Prototyping: From UX to Front End &mdash; Medium</a> Harshad Kulkarni </p>
<p>Recently, I have observed many designers start solving the problem using Sketch software. Not that there is something wrong with this approach, I find this process to be extremely inefficient and super slow. Focusing on Sketching and not Sketch will help you to be more efficient and find better solutions.</p>
<p><img alt="" src="http://ift.tt/2oGO5ZT"></p>
<h3>1. It helps to carry your mistakes as you grow</h3>
<p>The problem with Command+Z is, it treats the errors and constraints the same way. Aligning the elements is way different than turning on and off layers because of technical limitations.</p>
<blockquote><p>Referring to earlier mistakes and constraints helps to connect the dots when solving new problems.</p></blockquote>
<h3>2. It helps to reduce noise</h3>
<p>When solving a user problem aka designing you need to focus on what users are thinking, saying, behaving and feeling. Your sketchbook or whiteboard will allow you to concentrate on these users problems by removing the interface from the equation. <a href="http://ift.tt/2nXSoTs">Read my previous article about UX and UI.</a> Solving UX problems earlier in phase will help you to design efficient and beautiful interface later.</p>
<h3>3. It helps to paint the picture at high level, quickly</h3>
<p>Designing is like painting to me. Grasp the moment with drawing, colors and then get into capturing details. My Sketchbook allows me to paint the high-level picture (super fast). It means I can quickly capture how the flow is going to be, what open questions I have, where I need to align with my stakeholders etc. The alignment with the parties concerned is critical early on in the process for the efficient and elegant solution.</p>
<p><img alt="" src="http://ift.tt/2oGZWXS"></p>
<h3>4. It helps focusing better on an interface detail</h3>
<p>Yes! Sketching helps to design efficient and beautiful interfaces because you are not spending time thinking about metaphors, flows, errors when using a computer software. Ideally you have solved these before jumping into Sketch. When using a software, you should totally focus on pixels and layout.</p>
<blockquote><p>A computer software should be used to compile user story and not to write it.</p></blockquote>
<h3>Bouns 🙂</h3>
<h3>It will build confidence when you’ll browse your old work</h3>
<p>Browsing my old sketchbook plays a recap of my overall journey as a designer. It helps me to understand the depth of design problems I was solving earlier in my career, and now, ultimately my sketchbook is my graphic novel picturing my growth a designer.</p>
<p><img alt="" src="http://ift.tt/2nXKSrY"></p>
<p>Let me know your thoughts, would love to hear your perspective.</p>
<p><iframe src="http://ift.tt/2kZ4o5P" width="800" height="400" frameborder="0"><a href="http://ift.tt/2lIYHWK">http://ift.tt/2lIYHWK</a></iframe><img src="http://ift.tt/2oGYPax" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="http://ift.tt/2nXLAoZ">Focus on sketching and not Sketch</a> was originally published in <a href="http://ift.tt/2cAqCpx">Prototyping: From UX to Front End</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


Focus on sketching and not Sketch

Focus on sketching and not Sketch

Top Stories