<?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 Dor Tal on Medium]]></title>
        <description><![CDATA[Stories by Dor Tal on Medium]]></description>
        <link>https://medium.com/@dortaldt?source=rss-7eb366d4f218------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zGlOdcJQNFJp_uGA7Em89w@2x.jpeg</url>
            <title>Stories by Dor Tal on Medium</title>
            <link>https://medium.com/@dortaldt?source=rss-7eb366d4f218------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 08:52:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dortaldt/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[Improving our agile process leveraging Jira boards and flows]]></title>
            <link>https://medium.com/booking-product/improving-our-agile-process-leveraging-jira-boards-and-flows-677ea48887a6?source=rss-7eb366d4f218------2</link>
            <guid isPermaLink="false">https://medium.com/p/677ea48887a6</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Dor Tal]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 14:30:34 GMT</pubDate>
            <atom:updated>2019-06-26T14:30:34.604Z</atom:updated>
            <content:encoded><![CDATA[<p>Struggling to fit design work into your agile process, using Jira? Lacking visibility of status for stories (especially after implementation is done and before they’re rolled)? This note might be for you.</p><h3>TL;DR</h3><p>By adjusting our Jira flows to better suit our workflows, we gained higher visibility and better tracking of our development process.</p><h3>What we used to do and why we needed to refine our process?</h3><p>Until a while back, we were using our Jira board to help us manage our agile process (Scrum in our case).</p><p>We were using the classic 3-columns board: “Todo”, “In progress” and “Done”. Simple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/514/0*qYobYeATG6PYH5EX" /></figure><p>Since then, the team has grown — another developer has joined, as well as another designer, and we started experiencing some issues that suggested some improvements were needed:</p><ol><li><strong>Lack of visibility on the status of tasks that are completed but not yet live</strong><br> As some stories were being completed toward the end of a sprint, but were not yet rolled out, we saw that many stories had finished the actual development work, but weren’t yet live. So in the following sprint, we were risking missing to pick those up, since there was nothing left to do with them. The result was us trying our best to remember which features and experiments needed to be started.</li><li><strong>Storing and refining ideas</strong><br>On one hand, we didn’t want our backlog to start getting too packed and messy, so we tried to avoid creating stories that are half baked (e.g. abstract concepts about a new partner feature). On the other hand, when a new idea that is not relevant to the epics that we’re currently working on, nor to the roadmap, would pop into our minds, we didn’t have a specific place to store it — which led us to create several docs for capturing those ideas. Creating all those docs here and there, simply doesn’t scale.</li><li><strong>Merging design into the development workflow</strong><br>Since we have stories (most of them) that need design work before the technical implementation can take place, we needed a streamlined way to document the flow of a story between the two stages (design-dev), with its status at all points in time.</li><li>The way we initially did it was to add a prefix to a ticket name (e.g. “D_user form”), meaning that the ticket would go through the “todo-inProgress-done” flow for the design process. Then, when the design is ready, we would take the ticket back to the backlog and just remove the “D” so we would know that we don’t need any more design work for this ticket. But this is a “hack” and not a real solution to the issue. (In addition, it changes the title, scope and “nature” of a Jira story/ticket throughout its lifetime, which can get a little messy.)</li></ol><h3>Adjusting the tools and process to our workflow</h3><p>After a few iterations and learnings, we have now reshaped our Jira and workflow in a way that supports our needs better:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*VUa4UfE5ybgmS9u0" /></figure><ol><li><strong>Increase visibility for “Done” tickets</strong><br>As pointed out above, we used to use the “traditional” 3-column board. In order to increase the visibility of the state of each ticket in its final stages (when the development work is done), we broke down the “done” into 3 columns (statuses) that reflected better the actual process we’re following in the team: 1)“QA/Code review”: this is quite clear, as this is the stage of the QA process. 2) “Ready for rollout”: after the QA process is over and the code has been merged to trunk. 3) “Live”: meaning the experiment is running or the feature is active on production.<br>By breaking down the “done” status into more specific statuses, we increased the clarity and reduced the chances of a ticket being forgotten.</li><li><strong>Refinement board and idea-box status</strong><br>We created a new flow for a ticket: Every ticket is being created as an “Idea”. Ideas are not shown in the backlog but only on the brand new “Refinement” board. The refinement board is the board that we’re using during our refinement sessions and it has only two columns: “Ideas” and “Ready for Refinement”. The point is that the “ideas” are all in one column where we can store all our ideas and stories without worrying too much about the order or the content of the tickets.<br> Before the refinement session, every team member can nominate ideas for refinement by adding the missing details and moving them to teh “Ready for Refinement” column. Then, during the refinement process, we’re reviewing only the “Ready for Refinement” column. If a ticket is well defined, we’re moving it to our backlog. If not, we move it back to the “Ideas” column until we have enough information.</li><li><strong>Better reflecting the design process within a sprint</strong><br>The last step we did, and we’re still refining it these days, is merging the design process into the whole dev process. Instead of recycling a ticket after the design work is done, we now have a dedicated board where a ticket can move throughout the design process before moving forward to the dev board.</li></ol><h3>Main learnings</h3><ul><li><strong>One step at a time</strong><br>We introduced these steps one at a time, instead of all at once, which would have made it quite overwhelming and made it look like lots of overhead.</li><li><strong>Your tools should support your workflow</strong> (not the other way around)<br>Although the agile process should be kept simple and, well, as agile as possible, there is much room for adjusting it to the way that your team is working. Make sure that you’re adjusting your management tools as well.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=677ea48887a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/booking-product/improving-our-agile-process-leveraging-jira-boards-and-flows-677ea48887a6">Improving our agile process leveraging Jira boards and flows</a> was originally published in <a href="https://medium.com/booking-product">Booking Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why UX designers should code (and when they shouldn’t)]]></title>
            <link>https://uxdesign.cc/why-ux-designers-should-code-and-when-they-shouldnt-1293650e139e?source=rss-7eb366d4f218------2</link>
            <guid isPermaLink="false">https://medium.com/p/1293650e139e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Dor Tal]]></dc:creator>
            <pubDate>Wed, 28 Feb 2018 05:12:01 GMT</pubDate>
            <atom:updated>2018-02-28T13:11:10.416Z</atom:updated>
            <content:encoded><![CDATA[<h4>Learning how to influence the final product through coding</h4><p>For the last few years, I’ve been working with many software development teams, from small startups to big companies, building great products. At some point, I realized that if I wanted to stay relevant as well as have influence on the product’s development and the end result, I would have to learn how to code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5WR2jEWO93xu0wqzTmz0DA.png" /></figure><h3>The developer magician</h3><p>I remember the first mockup I created for a commercial product. I just graduated from design school, and it was the first time I worked closely with a developer.</p><p>“What are my limitations regarding the app’s layout?” I naively asked her.</p><p>“Do whatever you want — I’ll make it work eventually,” the poor developer answered.</p><p>“Great!” I thought. “I can toss anything I want into this magician’s top hat, she’ll do her magic, and then poof, she’ll pull our brand-new app out of the hat.”</p><p>I soon discovered the developer would be able to make the app look and behave as I design, but it would be complicated and would push the code to its limit.</p><blockquote>“Photoshop is the most effective way to show your clients what their website will never look like.” — Stephen Hay, author of<em> Responsive Design Workflow</em></blockquote><p>That experience made me realize that if I want to design and create new, innovative, efficient, and kickass products, I must understand how those products work — inside and out.</p><h3>Know your raw materials and mechanism</h3><p>Maybe now it’s a good time to mention that I started out as an industrial designer — instead of apps, I designed chairs and plastic products. When planning new, physical products, picking the right materials can make the difference between a successful and failed product. The weight, strength, durability, and cost of the product’s material greatly influences the overall usage experience and quality of the product.</p><p>Let’s take an example from the software world, specifically the web development field. On the front-end (aka the client-side — whatever works for you), the basic raw materials we use are <strong>HTML</strong> (Hypertext Markup Language), <strong>CSS</strong> (Cascading Style Sheets)<strong>,</strong> and <strong>JavaScript</strong>.</p><p>Let’s focus for a second on CSS, the markup language or “code,” responsible for determining the style of a web page.</p><p>The most common tools for creating mockups and other visual representations of digital products, usually used by designers, are graphic editing software such as Sketch, Adobe Photoshop, and Adobe Illustrator. The nice thing with these tools is that they let users create visual images as easy as possible. Rich effects, complex shapes, and free positioning are a single mouse click away — your creativity is the only barrier. However, styling with CSS is a different story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*lCQ--yDN25ZIICPzFvfoHg.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*wnwWe4wDiwHG8gt6KBb6JA.png" /><figcaption>Left: An example of a circle being created using Sketch. Right: The same circle created with HTML and CSS.</figcaption></figure><p>Until CSS3, the latest evolution of CSS, visual effects, keyframe animations, and transformations could only be implemented using JavaScript — CSS3 has these features baked right in. Still, these are very limited compared to the ones which are provided by the graphic editing software mentioned above.</p><p>Another important aspect that CSS is responsible for is the responsive behavior of the page — for example, how the layout will be displayed on different display types and sizes or which elements will shrink, enlarge, move or just won’t be shown in a relation to the screen size and the CSS values (viewports, percentages, breakpoints, etc.). If you don’t know CSS, your control on the appearance and behavior of the product is limited.</p><p>Until now, we’ve discussed what many consider as declarative languages and not a “real code.” This is an interesting discussion for another time. Right now we need to look at why JavaScript and other programming languages are also essential for designers to know.</p><p>I hear many designers saying that knowing HTML and CSS is enough. Well, it’s better than nothing for sure, but to really be able to design and control your products behavior (aka ”experience”), you should understand how the product mechanism is built. Logic, data structure, and network communication are the building blocks of any digital product. If you don’t know how to use these elements, you’ll end up to being like a makeup artist who can make a face prettier but can’t draw out a person’s unique characteristics.</p><h3>Working with developers</h3><p>You’ll need to collaborate closely with your dev team to bring your designs to life.</p><p>At the foundation of your daily workflow, you’ll need to communicate your design — how the elements interact with the user’s inputs, how the layout responds to different screen sizes, etc. More than the basic description of the planned design, you’ll also need to make decisions in real time together. When things keep on changing during the developing process, you’ll need to exchange ideas, suggest solutions, and discuss the effect of each possible solution on the overall behavior of the product. In these cases, if you don’t understand what the technical solutions mean, it would be difficult for you to participate in the decision-making process — which might result in choosing a solution that doesn’t enhance user experience but rather damages it.</p><p>As mentioned, the foundation of a good collaboration is the ability to communicate, using a common language, with your developer colleagues. You wouldn’t want your conversation with a developer to contain sentences such as “just make it pretty” or “I don’t know anything about design — just tell me how you want it to look and behave”. It works the same when you communicate with your developer colleagues — they would understand you much better when you use terms such as “loop” instead of explaining them you want the program to run over and over and “variables” when describing a value that should change depending on the user’s data.</p><p>More than being clear about your wishes, using the right terminology will increase the <strong>trust</strong> between you and your dev team — they’ll know that the person who’s planning the product is familiar with the work that should be carried out to build it.</p><h3>Deliver full product elements and better mockups</h3><blockquote>“For quick design experiments on existing components/screens, I find myself using dev tools way more often than Sketch.” — <a href="https://twitter.com/stephenhay/status/964522221849935879">Stephen Hay</a>, author of <em>Responsive Design Workflow</em></blockquote><p>Fail fast, iterate, improve — in many agile development processes, velocity has a huge impact on the product’s chance for success. In some cases, explaining what you want, waiting for it to be ready, and only then taking it for a test could take much more time than just building it to figure out how shitty your concept really is (or isn’t!).</p><p>In addition to the ability to create features by yourself, using code for prototyping can help you create elements with a more precise behaviour — clickable screenshots can reflect the main flow; however, for instance, if you wish to test the layout’s behaviour response to dynamic screen resizing, writing a quick HTML and CSS can bring you much more insight.</p><p>Here is a simple example of how you can quickly test a responsive layout using simple HTML and CSS:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2FCheesetoast%2Fembed%2Fpreview%2FKFAaq%3Fheight%3D600%26slug-hash%3DKFAaq%26default-tabs%3Dhtml%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io%26embed-version%3D2&amp;url=https%3A%2F%2Fcodepen.io%2FCheesetoast%2Fpen%2FKFAaq%3Fq%3Dresponsive%2Blayout%26limit%3Dall%26type%3Dtype-pens&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F7129.KFAaq.small.9744471d-12f8-4ffa-b6f8-41acfc2b430f.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/499166b114303aa7fe660c177396d18c/href">https://medium.com/media/499166b114303aa7fe660c177396d18c/href</a></iframe><h3>Part of the team, part of the conversation</h3><p>The last point I want to discuss here touches a subject that many people don’t usually consider but is a large part of daily working environment : <strong>code culture</strong>.</p><p>In the IT industry, which as a UX designer you’re a part of, not knowing code means not only not knowing the programming language, but also not knowing the “spoken” language. No, I’m not trying to say that people in IT companies actually speak to each other using “if/else” statements (though sometimes they do). Rather, what I want to say is that in environments populated mostly with developers, there are going to be many debugging jokes and a lot of jargon containing code and programming references. If you want to stay a part of the culture and participate in the social dynamics, you should get some experience in coding.</p><h3>When shouldn’t designers write code?</h3><p>Don’t get me wrong — designers are not software engineers. Although there are many cases, as I mentioned before, where it makes sense for designers to code, I still think that coding isn’t their main job. Code for a designer should be used as a <strong>tool</strong> for enabling better expression and communication. Yet, writing a good, secure, and stable code is still a craft which takes years to master. Designers have too many other skills to master, so when things get complexed and need to be delivered at production level — when you are talking about software architecture and building scalable performing products — developers are still the professionals.</p><h3>Let’s start!</h3><p>So you are convinced that you should learn a bit more coding, but where to start?</p><p><strong>Don’t be afraid</strong>: The first step is to understand that coding, like spoken languages, is something that anyone can learn, especially if you’re already inside the industry and exposed to programming daily.</p><p><strong>Learn</strong>: There are some awesome online courses for learning code out there. My recommendation is to start from the basics—HTML and CSS—then move to basic JavaScript. From there you can start and focus on popular frameworks such as <a href="https://jquery.com/">jQuery</a>, <a href="https://getbootstrap.com/">Bootstrap</a>, and <a href="https://angular.io/">Angular</a>.</p><p>Here is a list of great online resources:</p><ul><li><a href="https://www.codeschool.com/">Code School</a> — great online courses for kind.</li><li><a href="https://www.codecademy.com/">Codec Academy</a></li><li><a href="https://stackoverflow.com/">Stack Overflow</a> — your new best friend, this is the main resource for Q&amp;A regarding code and programming.</li><li><a href="https://css-tricks.com/">CSS-Tricks</a> — excellent how-to guide for CSS.</li><li><a href="https://codepen.io/">CodePen</a> — online, real-time, code editor. You can also find tons of nice examples and projects.</li></ul><p><strong>Basic tools</strong>: Here is a list of basic tools you can use for starting:</p><ul><li><a href="https://www.sublimetext.com/">Sublime Text</a> — this free (trial) code editor is simple and has great plugins. My advice is to try several editors and to see which one works the best for you.</li><li><a href="https://github.com/">GitHub</a> — Git is a distributed version control system that can make your project version management much easier. Here is a link to <a href="https://github.com/dortaldt">my repository</a>.</li><li>Browser DevTools</li></ul><p><strong>Get your hands dirty</strong>: Ask your team lead for small code tasks within your team. Start with some code parts that doesn’t have high visibility — that way, it will be easy for them to give you some room for learning.</p><p><strong>Ask your colleague developers for help</strong>: Get for tips and tricks. I find this is a huge benefit for designers who are already on a development team. The break area is a great place for some “when should I use a div?” questions.</p><p>Good luck! And remember, code is a <strong>tool</strong>, not a goal. Adding code to your professional toolbox can make your role as a UX designer more impactful to your team and your company.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1293650e139e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/why-ux-designers-should-code-and-when-they-shouldnt-1293650e139e">Why UX designers should code (and when they shouldn’t)</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>