<?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 Remzi Anıl Cireli on Medium]]></title>
        <description><![CDATA[Stories by Remzi Anıl Cireli on Medium]]></description>
        <link>https://medium.com/@remzianlcireli?source=rss-a76fd5df7d84------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*rVxWSAmPkHEBWzuap1L4mA.jpeg</url>
            <title>Stories by Remzi Anıl Cireli on Medium</title>
            <link>https://medium.com/@remzianlcireli?source=rss-a76fd5df7d84------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 00:19:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@remzianlcireli/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[Do you understand what you are signing up for?]]></title>
            <link>https://medium.com/@remzianlcireli/do-you-understand-what-you-are-signing-up-for-619f69b3b4ee?source=rss-a76fd5df7d84------2</link>
            <guid isPermaLink="false">https://medium.com/p/619f69b3b4ee</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[team-cohesion]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Remzi Anıl Cireli]]></dc:creator>
            <pubDate>Thu, 31 Mar 2022 22:47:11 GMT</pubDate>
            <atom:updated>2022-04-01T10:48:55.723Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mfl1jTARCTdgMyF_" /><figcaption>Photo by <a href="https://unsplash.com/@janesky?utm_source=medium&amp;utm_medium=referral">Antonio Janeski</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>95% of the job interviews where I am the interviewee, I am asked the same question: “Why is your track record for holding a job is too low?” Well, although it is a reasonable question to ask, there is a simple answer: “Because there was only a little knowledge of what a UX /specialist, designer, consultant, architect, insert more here…/ does, and almost no respect to my field or to me in some of the companies I have worked for.”</h4><p>While the term “design” is commonly used to describe UX, and the following statements from NNGroup and Baymard Institute are considered to be the best definitions of what UX is, you’ll notice that neither statement uses the word “design.”</p><blockquote>UX encompasses all aspects of the end-users interaction with the company, its services, and its product.</blockquote><p><a href="https://www.nngroup.com/">-NNGroup.com</a></p><blockquote>User experience (UX) is any interaction a user has with a product. The goal of UX is to meet the user’s needs and create easy, relevant, efficient experiences.</blockquote><blockquote>UX is a broad term that can encompass a massive range of interactions…</blockquote><blockquote>While there is no single definition, the term UX is often associated with websites, apps, hardware, and other technology.</blockquote><p><a href="https://baymard.com/">-Baymard.com</a></p><p>If you are wondering, Donald Norman, the co-founder of NNGroup, is the creator of the term “user experience,” which he defines in greater detail in his book “Design of Everyday Things.” Along with NNGroup, Baymard Institute is one of the most dependable sources in the field of UX.</p><p>I recently read <a href="https://uxdesign.cc/design-is-not-art-and-ux-is-not-design-62c99d138ac1">another essay</a> on what UX is from an author who explained his opinions on UX by presenting examples, essentially clarifying the above concepts in further detail. His essay inspired me to write this article because it contains some really simple examples as well as some points that I agree with.</p><p>While I don’t want to go into explaining what UX is and how it benefits the users and businesses on this article, I just want to copy one point from his article:</p><blockquote>“Good UX is only as good as the sum of its parts. If a website loads too slow, causing frustration for the user, this falls into a developer’s wheelhouse. If the content does not resonate with the user or provide valuable information, this is a writer’s responsibility. And if a user receives too many emails and unsubscribes, this is a marketer’s problem to solve. UX is a broad area that touches many points beyond aesthetic usability factors.”</blockquote><p>-<a href="https://micbuckcreative.medium.com/">Michael Buckley</a></p><p>His statement now includes personas that aren’t just users, as you can see. A Developer, a writer, and a marketer, to name a few. The Product Owner is not addressed here, but in my opinion, is the most important (and possibly the most stressful of them all) character. These are just a few examples of the various jobs that make up a product development team. “Stakeholders” refer to all of these people, as well as the company’s C-level executives and the product’s intended users. The inner stakeholders are those who create and shape the product, whereas the users are the external stakeholders. The most crucial element to remember here is that EVERY stakeholder has a say during the development of a product.</p><p>Instead of trying to describe what UX is and how it benefits users and businesses, I’d like to focus on how it can also promote team cohesion, workflow, processes, collaboration, and, most importantly, active listening and coordination in issue solving, using examples from some of my good and bad experiences.</p><p>First and foremost, the relationship between a Product Owner and a Product Designer is crucial. I’ve worked with some fantastic product owners as well as some less so. However, I’ve found that the greater the relationship between a PO and a Designer, the better the end output will be.</p><p>While your connection may begin with a simple grin and an introductory tour of the office and some of the most key individuals you will be working with, it may also begin with a decent introduction of self and the PO requesting that you prepare for a user interview session on your first day.</p><p>You are now experiencing the work atmosphere, regardless of how your first day goes. The people, the spaces, the dress code, the technology, and everything else that goes into that work environment are all important. As time passes, you get more familiar with all of the elements that contribute to your work-life experience.</p><p>Now comes a crucial question… Are you the type of person who wants your ideas to be heard? Or are you a silent worker who just does what’s asked of you? Do you believe your ideas are important to the business and the product and do you believe you have the skills to assist the team in ways other than a wireframe or UI perspective?</p><p>If you answered yes to the first and third questions, then I’d want to share concrete examples from my own experiences, without naming any names.</p><p>Let’s start with the positive situation, in which a PO greeted me as warmly as possible and welcomed me to the team and work environment on my first day. Although it was not his responsibility to greet me and present me to the rest of the team, he willingly did so. My experience has already been positive, and my first impressions of the PO are positive. By the way, this was early in my career, so I wasn’t used to working in large groups and didn’t have the most up-to-date knowledge of scrum terms.</p><p>During our time together, he taught me a lot about the product, not just from a design standpoint, but also from a management standpoint, and I taught him a lot about certain UX skills I had at the time. We got along swimmingly and produced a good product by asking each other questions, sharing necessary documents with the team, researching and presenting findings together, incorporating others in the decision-making process, and doing everything else that goes into a successful product development process. In the end, the product was a huge hit, with more than 1 million downloads in the first six months. We not only created a positive work atmosphere for the team, but we also maintain contact with some of the people that contributed to the development of the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M-6Bv0S26jdrw2Tz" /><figcaption>Photo by <a href="https://unsplash.com/@tengyart?utm_source=medium&amp;utm_medium=referral">Tengyart</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>On the other hand, at another company where I worked, I was the lead designer for a web app (let’s call the company “X” and the product “Y”). The design team was split into three sections: UX interaction, UI, and UX researchers. My responsibilities as the design lead for the product Y included delegating Research, Design, and UI work at the start of a sprint, opening tasks and tracking the progress of those delegated tasks, doing hands-on UX and documentation work during sprints, and presenting the flows, wireframes, and UI at the sprint’s end.</p><p>While that was a lot of responsibility and included additional management tasks, I was okay with it since my manager told me that all design decisions would go through me before being handed off to development, which also gave me confidence that I was a decision-maker on Y, and would therefore have an important role in the company X.</p><p>However, it was a pretty bad experience from the start. Although the contract said that I would be provided a MAC, I was handed a PC. After that, I had to travel to the post office to return the PC, wait for MAC to arrive, and try to locate the appropriate person within the firm to speak with regarding computer equipment concerns. This carried on for a while, and the terrible part is that it happened to other employees who had been hired within the first six months of my employment. The whole employee experience was sort of unprofessional within the company.</p><p>However, the point of this narrative is not about the equipment or my first day, but rather how good (or not) we worked together as a team after I was set to do some work. We didn’t have a roadmap or any KPIs to run to in the first place. When I first inquired about the vision statement, I was told to hold off and focus on improving the product from a design standpoint, as it had already been designed to a certain extent. I was also told not to make too many changes to the design because this would add to the development time.</p><p>While this was going on, anytime I or some other member of the team requested a vision statement workshop or tried to arrange workshops to better understand our users, senior management urged us to hold off because they already knew who the users and behaviors of those users were. When we politely inquired if we might extract such information from them, it invariably resulted in long calls in which everyone was only interested in seeing things from their perspective, without understanding each other’s roles or the vital work that goes on behind the screens. Most of the time, there was no output of those meetings. All talk, no action. It was also difficult to figure out who did what. Who do I go to for content, for example? Or, who is the most qualified technical expert to answer my inquiry about a backend issue? Most importantly, who is the final decision maker, and what information is used to make those decisions?</p><p>It was a mess; sometimes the product team would create something on Powerpoint and then go straight to UI to deliver it, ignoring me in the process. When I tried to convey to a group of team members that relevant elements should stay together on a separate page independent of the user’s one more click action, I was told that my philosophical concepts were too time-consuming.</p><p>I want to give one more bad experience in the same company since it is my worst so far in <em>any</em> company. Despite proposing a re-design in my early days to start from scratch and get clarity for all team members, I awoke one day to a new UI that I had practically no knowledge of was going on the side, despite being informed that all design decisions would go through me. I was involved in the early stages of this new design since the presentation to the CEO went poorly, and a small team from product and design was asked to rebuild the experience, as well as remove “unnecessary” elements that we included in response to an earlier request from the same CEO. We only had one week (Yes, 1 week, 7 days, and it was already Thursday I believe, so we had to work on weekend full-time) to complete the design and show it to the executives. Or so we were informed, because the CEO had not requested another presentation in the near future, and the CPO had simply instructed us to hurry, as we later discovered. I rapidly generated the wireframes and handed them off to UI based on some decisions I agree and disagree with.</p><p>I was largely done with this redesign at this point since I was stressed out and asked to take a break from this side project. I was already dealing with issues with the produced version, and I couldn’t take the stress that this entire one-week redesign was causing me, even though it could have been done in the previous year, as I had requested in my early days. My assumption was that the UI would take the design components that the team had generated in our design system and turn them into final screens with blue components, a consistent corporate language, and the overall look and feel that our presentations required.</p><p>So, while the UI team was presenting those screens to the rest of the team, I discovered that we now had pink buttons and an overall look and feel that has practically nothing to do with our industry or the users we “think” will use our product. Worst of all, these decisions were irreversible. I had no say in how negatively this new UI could impact the user experience. Even while some problems were evident because they contradicted basic UX principles, there were also new elements that needed to be tested with users to see if they worked or not. However, I was directed to handle the implementation of this new design and redraw my wireframes and flows accordingly, while the product team worked to persuade the rest of the team that this new design has a better experience. They designed the experience. Less work for me. Yay!!!</p><p>While this little side narrative made my article a little bit longer, I wanted you to think about how you would feel if you were put in a position like this. Because this was not only the worst position I was put in in this company but it was the worst experience I had ever had in my career.</p><p>Then this happened: I was invited to bi-weekly, recurring 1-hour sessions that would go for over a month and would focus on creating the product vision statement. This happened around the eighth or ninth month of my work, roughly seven months after I first recommended that we come up with a product vision as a group. Although the team had recently had a very rare and successful retro session, where the most critical issue was the never-ending meetings by individual votes, product management opted to do it this way.</p><p>As a result, I wrote to the product owner to see if we might communicate. I was thinking of recommending a half-day to one-day full-on workshop so we wouldn’t have to spend as much time defining the vision and could extract it as a group in one session and move on. The most depressing response I received. It was deafening how quiet it was. Nothing. There was no response at all from the PO. When the PO doesn’t respond to me in the first place, how can we agree or disagree on anything? How can I respect decisions made by a silo when I was previously ignored by that silo?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zhMjoR634wkhdZyU" /><figcaption>Photo by <a href="https://unsplash.com/@jasongoodman_youxventures?utm_source=medium&amp;utm_medium=referral">Jason Goodman</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This, I suppose, takes me to the main point of this article. Communication. It is the most important skill you can have as an employee, particularly if you work in the IT field, whether you are a developer, manager, designer, or writer…</p><p>My perspective in this article was that of a user experience designer. And, as we all know, design is subjective, and most people believe they have a (decisive) say in design decisions when in reality, the majority of those people still don’t understand that UX is both a business and a design job. Some company executives or product managers may still believe you’re just a rectangle drawer who paints attractive end screens for them, while in reality, as a UX designer, you can provide clarity and solutions to most challenges within the team as well. However, you must demonstrate this and fight for it. Your vocal communication may be overlooked, just as mine was. Please don’t give up. To convey your idea, use your strongest skill, which I believe for most of us designers would be visualization. Create wireframes, a decent prototype, or a simple sketch to visualize your idea and communicate it to the team. It could also be a simple bullet list of reasons why your idea should be considered. If you’re still being ignored, then you’ll know it’s time to look for a new job; don’t spend any more time there if possible.</p><p>Without communication, there is no vision. Without a set vision, there isn’t too much clarity. Without clarity, there is almost no cohesion. And without cohesion, there isn’t too much success, and there is quite a bit of stress. So, would you like to work in a stressful environment where you can’t communicate your ideas is a question you should be asking yourself.</p><p>So, returning to the article’s title… When you’re preparing for a job interview, use your communication skills to communicate your expectations and worries which could occur when you start working for that company. Inquire extensively about the processes, people, culture, values, and atmosphere, as well as whether or not your opinions are important. Inquire about the decision-makers and the process through which those decisions are made. If you’re asked to execute a task that doesn’t seem right to you, ask for genuine data. These are important factors that would help shape your personal life since a stressful work environment can cause problems within personal relationships. We are all human after all.</p><p>Work-life, believe me, is a lot like married life. Despite the fact that I am <strong><em>not</em></strong> married, I am aware of the crucial characteristics that contribute to a healthy relationship. As a result, I’d like to share a quote by a social media account dedicated to mental health:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SM4v8dLOHAPRHkPX" /><figcaption>Photo by <a href="https://unsplash.com/@sandym10?utm_source=medium&amp;utm_medium=referral">Sandy Millar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>Before getting married: Discuss bills, parenting styles, credit, debt, religion, how to deal with family, what beliefs will be instilled in your children, childhood traumas, sexual expectations, partner expectations, financial expectations, family health history, mental health history, bucket lists, dream home, careers and education, political views and whatever comes into mind. Love is not enough.</blockquote><p>-<a href="https://www.instagram.com/thinkingmindspage/?hl=en">ThinkingMinds</a></p><p>Put that quote in your own words in the context of your interaction with the individuals in your workplace. Because your passion for your work is not enough.</p><p>Finally, while I focused on points from the perspective of an employee in this article, I believe the question posed in the headline might be answered both ways. Does an HR representative or a key product decision-maker know what they are signing you up for? Ask the right questions during the interview and see.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=619f69b3b4ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kavramsal Bilim ve Tasarım]]></title>
            <link>https://medium.com/@remzianlcireli/kavramsal-bilim-ve-tasar%C4%B1m-8620a3ec8246?source=rss-a76fd5df7d84------2</link>
            <guid isPermaLink="false">https://medium.com/p/8620a3ec8246</guid>
            <category><![CDATA[tasarım]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[kavramsal-bilim]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <dc:creator><![CDATA[Remzi Anıl Cireli]]></dc:creator>
            <pubDate>Tue, 15 May 2018 09:53:19 GMT</pubDate>
            <atom:updated>2018-05-15T09:53:19.316Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*aex2_Df0curEVxysXaeF-w.jpeg" /></figure><p>Şu anda beyniniz kısa süreli hafızanızı kullanıyor. Bu makaleyi okurken, içinde geçen kelimeleri veya bir bilgiyi idrak edip, otomatik olarak kısa süreli hafızanıza atıp burdan harekete geçiyorsunuz. Üç opsiyonunuz var:</p><ol><li>Kısa bir sürede unutabilirsiniz,</li><li>Bilgiyi daha iyi anlamak için bir aksiyona geçebilirsiniz (örneğin, sözlüğe bakmak veya üzerine daha fazla araştırma yapmak olabilir),</li><li>Üzerine daha da yoğunlaşıp uzun süreli hafızanıza atabilirsiniz. Şunu da belirteyim ki hafıza denince ilk aklımıza gelen uzun süreli hafızadır!</li></ol><p>Şunu aklınızdan çıkarmamanız gerekiyor: Kısa süreli hafızanızın kapasitesi az olduğu için, kısa süreli hafızanızdaki bilgiyi — üzerine yoğunlaşmadığınız sürece — adı üstünde, kısa süre içinde kaybedersiniz.</p><p>Peki bunun tasarımla ne ilgisi var? Sitenize gelen bir kullanıcıya siteniz yüklenir yüklenmez çok fazla öğe (stimuli) gösterdiğiniz zaman, kullanıcının önemli bir bilgiyi gözden kaçırmasına veya bir fonksiyonun nasıl çalıştığını anlamamasına, ve daha da kötüsü tasarımınızı tamamiyle görmezlikten gelip site içinde kaybolmasına neden olabilirsiniz.</p><p>Fakat bu basitliğin her zaman daha iyi olduğu anlamına gelmez. Komplike olması gereken veya içinde bir çok bilgi barındıran sisteminizi gerçekten sistematik ve düzenli bir şekilde tasarladığınız zaman kullanıcılarınızın beyninde İngilizce adıyla “Cognitive Load” — kavramsal yükü — de minimuma indirmiş oluyorsunuz.</p><p>Kısa bir örnekle açıklamak gerekirse, hamburger menü butonu mobil tasarımlarda artık hepimizin görmeye alışık olduğu, ana menüye erişimi sağlayan butondur. Artık bu butonu görmeye o kadar alıştık ki, ekrana ilk bakışımızda bu buton kısa süreli hafızamızda bir yer tutmuyor, onun ne olduğunu hızlıca algılayıp kısa süreli hafızamızı ekrandaki diğer öğeler için boş bırakmış oluyoruz.</p><p><strong>Tasarımda kavramsal yükü nasıl azaltırım?</strong></p><p>Tasarımda kavramsal yükü azaltmak için bazı kurallar var ve iyi tasarımcılar bu kuralları nasıl kullanacaklarını iyi biliyorlar. Aşağıda bahsedeceğim kavramsal bilim prensipleri eskiden genellikle insan psikolojisiyle alakalıyken, özellikle her gün en az iki farklı cihaz kullandığımızı düşünürsek, ekran tasarımlarının çok değerli kuralları haline geldiler.</p><p><strong>Leverage pop-out effect (Ortaya çıkarmak)</strong></p><p>İnsanoğlu bir çok, hemen hemen aynı olan öğeler içinde farklı olanı hızlıca algılamaya programlanmıştır. Örneğin metroya bindiğinizde genel olarak İstanbul halkının bir giyiniş tarzı vardır, genel olarak aynıdır, çok renkli giyinmeyi sevmeyiz. Fakat renkli takımının üzerine artı olarak papyon takmış birini gördünüz diyelim; o kişiyi direkt farkedersiniz. Bu ekran tasarımında da böyledir. Dolayısıyla kullanıcıların dikkatini çekmek istediğiniz butonu ekrandaki diğer öğelerden farklı bir şekilde tasarladığınız zaman kullanıcılarınızın o butonu gözden kaçırması imkansıza yakındır.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*0vIOsK9ACnL7WJD1wWZoHQ.png" /><figcaption>Leverage pop-out effect</figcaption></figure><p><strong>Hick’s Law</strong></p><p>Kullanıcın seçmesi gereken opsiyonları ne kadar arttırırsanız onun üzerindeki kavramsal yükü de o kadar arttırırsınız, bu da seçime kadar olan süreyi logaritmik olarak arttıracaktır. Örneklemek gerekirse, bazı giyim üzerine kurulu e-ticaret sitelerinde neden ilk olarak Kadın veya Erkek diye sadece 2 adet seçenek olduğunu üzerinde kafa yormanız yeterli olacaktır.</p><p><strong>Affordances</strong></p><p>Tam Türkçe karşılığı olmamak ile beraber affordance kelimesinin anlamı: Belirli bir eylemin yapılmasına olanak tanıması amacıyla bir nesnenin/aracın oluşturulması. Yani ekrandaki bir öğe kendi kendine o öğeyi nasıl kullanacağınıza yardımcı olabilir. Bunun ekran tasarımındaki en basit örneği: Bir link öğesini paragraf öğesinden ayırmak için altını çizgili, farklı renkte ve üzerinde gezinirken hover efektli tasarladığınız zaman kullanıcılar bunun bir link olduğunu daha iyi anlayacaktır.</p><p><strong>Gestalt Prensipleri</strong></p><p>Üzerinde ne kadar konuşsak azdır ama Gestalt prensiplerini benimsemeden tasarım yapmak içinde kıyma olmayan mantı yapmakla eş tutulabilir. İçine fazla girmemek ile beraber en çok kullanılan Gestalt Prensip başlıkları şunlardır:</p><p>1. Law of Closure<br>2. Law of Common Region<br>3. Figure / Ground<br>4. Law of Proximity<br>5. Common Fate<br>6. Continuation<br>7. Convexity<br>8. Familiarity<br>9. Symmetry</p><p>Daha fazla detay için: <a href="https://www.interaction-design.org/literature/topics/gestalt-principles">https://www.interaction-design.org/literature/topics/gestalt-principles</a><br>Başlıkların içine teker teker girmeyeceğim fakat en sevdiğim örnek olarak Law of Closure’dan Carrefour logosu gelsin:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YirYJ5O8eE5aRv5sysuE-A.png" /><figcaption>Carrefour Logo</figcaption></figure><p>Logonun ne anlama geldiğini biliyor musunuz? Bilmiyorsanız ortadaki beyaz boşluktaki “C” harfini bu yazıyı okuyana kadar farketmemişsiniz demek ki.</p><p><em>“Bir kullanıcının tasarımınız içindeki bir öğeyi özellikle algılamasını mı istiyorsunuz? O zaman o öğenin gözden kaçırılmasının imkansız olduğundan emin olun!”</em></p><p>Bazı tasarımlar sadece görsellik için yapılıyor, bu doğru. Fakat bir websitesi veya uygulama tasarlarken o tasarımın daha kullanılabilir olması için kavramsal (algısal) bilim hakkında biraz daha fazla bilgi sahibi olmakta kesinlikle yarar var.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8620a3ec8246" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>