<?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 Feyza Nur Khassanov on Medium]]></title>
        <description><![CDATA[Stories by Feyza Nur Khassanov on Medium]]></description>
        <link>https://medium.com/@fndemirci?source=rss-88724e492370------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8t9-LQee6z82qh44MvrEZA.jpeg</url>
            <title>Stories by Feyza Nur Khassanov on Medium</title>
            <link>https://medium.com/@fndemirci?source=rss-88724e492370------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 08:11:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fndemirci/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[Our Efficiency Journey in Trendyol Customer Services Products]]></title>
            <link>https://medium.com/trendyol-tech/our-efficiency-journey-in-trendyol-customer-services-products-57642101e933?source=rss-88724e492370------2</link>
            <guid isPermaLink="false">https://medium.com/p/57642101e933</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[data-driven]]></category>
            <dc:creator><![CDATA[Feyza Nur Khassanov]]></dc:creator>
            <pubDate>Fri, 26 Dec 2025 06:18:40 GMT</pubDate>
            <atom:updated>2025-12-26T06:18:40.097Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Efficiency is not just about speed; it is the ability to provide the right answer to the right question at the right moment.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*gp7Q32eU2ooEZ7SXFfbPag.png" /></figure><p>Authors: <a href="https://medium.com/@ecemreyavuz">Cemre Yavuz</a>, <a href="https://medium.com/@fndemirci">Feyza Nur Khassanov</a></p><p>At Trendyol, we raise the bar a little higher every year. For 2025, one of the company’s key strategic priorities is <strong>efficiency</strong>. This focus aims to create significant impact through small but meaningful improvements, make processes more agile, and ensure operational excellence remains sustainable.</p><p>This strategic direction becomes even more tangible within the Customer Services (CS) organization. Every enhancement in the daily workflows of our agents directly influences speed, accuracy, and customer satisfaction. Completing tasks with fewer clicks, reducing error rates, accessing information quickly, decreasing manual workload through automation, and shortening training periods; all these improvements create a ripple effect from the agent experience to the end customer.</p><p><strong>As the UX team, we play a critical role in this journey.<br></strong> As one of the teams responsible for designing the products that support the CS ecosystem, our role goes far beyond creating interfaces. We act as a bridge between agents, team leaders, quality teams, and back-office users; understanding their needs clearly and aligning them with the company’s efficiency goals. Knowing that every improvement in CS products impacts the quality of service delivered to the customer, we treat this domain not as a one-off project but as a continuous area of responsibility.</p><p>In this article, we explore our efficiency journey through three core themes:<br> • <strong>Where were we?</strong> — How did we analyze our current state, strengths, and challenges?<br> • <strong>What did we do?</strong> — How did we test our assumptions and initiate transformation?<br> • <strong>Where are we going?</strong> — What roadmap have we designed to make efficiency sustainable within the CS ecosystem?</p><p>Together, these three sections offer a holistic view of both the strategic and operational aspects of our journey.</p><h3>Why Is Efficiency So Important?</h3><p>At Trendyol, efficiency is not just about speeding up work; it means directing the right resources to the right tasks, reducing errors, and improving both employee and customer experience. For this reason, efficiency is more than a part of our company strategy; it is one of the core pillars of our customer-centric culture.</p><p>When evaluated specifically within Customer Service, the impact of efficiency becomes even more visible. The improvements we make in daily workflows directly contribute to:</p><ul><li><strong>Agents completing tasks with fewer steps</strong></li><li><strong>A reduction in errors and repetitive follow-up processes</strong></li><li><strong>Shorter response times to customer requests</strong></li><li><strong>Easier access to information</strong></li><li><strong>Lighter workloads through automation</strong></li><li><strong>Faster onboarding and adaptation of new agents</strong></li></ul><p>These effects create a chain reaction that ultimately reaches the end customer and elevates service quality. That is why efficiency, for us, is not just a performance metric; it is a cultural approach that operates within the triangle of users, agents, and customers.</p><h3>What Was Our Plan?</h3><p>At the beginning of the process, we started with a simple but essential question: <strong><em>What does efficiency mean for Customer Service teams?</em></strong> While searching for an answer, we did not rely solely on our own domain knowledge. Instead, we held brainstorming sessions with different stakeholders. We created an initial plan, but we did not move forward without testing it with agents.</p><p>To understand the efficiency potential, we examined our core products under four main categories: <strong>Trendyol Assistant, CX-Core, CX-GO, </strong>and<strong> Connect.</strong></p><p><strong>Trendyol Assistant (Chatbot): </strong>This is the customer’s first support point before reaching an agent. It enables customers to solve many basic issues on their own and provides fast routing. As a result, it reduces agent workload and speeds up the customer experience.</p><p><strong>CX-Core:</strong> This is the main product where customer issues are fully resolved, including comprehensive and multi-step operations. Agents can access order history, campaign information, address data, and action permissions from a single screen. This allows even complex customer needs to be handled quickly and holistically.</p><p><strong>Connect:</strong> This is the main interface where agents manage operations and initiate live chats with customers. Critical information such as performance metrics, status management, and contact reasons is tracked from a single dashboard. It is also the center where team leads monitor performance and run quality processes.</p><p><strong>CX-GO:</strong> This is the most agile CS product, used to handle real-time issues in food and grocery orders. It acts as a bridge between the customer, restaurant, store, and courier, directly impacting both experience and agent performance.</p><p>With these four main products in mind, we conducted a detailed analysis focusing on efficiency and usability, and created the first version of our roadmap.</p><h3>Our Productivity Journey: Where We Were, Where We Are Going</h3><p>Our productivity journey began not with the question <em>“What can we do?”</em> but rather <strong><em>“What did we do wrong?”</em></strong> Of course, it’s not as if we had never taken action before. We had been collecting feedback through monthly surveys to understand our agents’ product satisfaction and the effort required in their workflows. However, these efforts lacked the depth required to address systemic problems at their core. Our biggest challenge was the absence of<strong> micro-level data tracking</strong> that would allow us to measure the impact of our improvements.</p><p>For instance, when a “defect” occurred in the system, we couldn’t quantify its operational impact, which made it difficult to secure the resources needed to fix it. This pushed us beyond being a team that simply delivered designs; it encouraged us to see productivity as a complete <strong>framework</strong>.</p><p>At every step of this journey, we centered the question: <strong><em>“Does this improvement make the agent’s job easier?”</em></strong> First, we listened, then we measured, and only afterward did we design.</p><h4>1. We Tested Our Assumptions and Listened to Users</h4><p>The most critical step in our efficiency journey was identifying the <strong>right assumptions</strong>. As a UX team, we first came together to define what efficiency meant to us and how it could be measured. However, we were aware that these definitions needed to be grounded in real usage rather than remaining theoretical.</p><p>To validate our assumptions, we closely collaborated with <strong>product managers</strong> and <strong>business teams</strong> who best understood the daily dynamics of <strong>CX-Core</strong> and <strong>Connect</strong>. We shared surveys focusing on where agents lose time, which steps increase the risk of errors, and which parts of the flow create friction. This allowed us to approach efficiency not only in terms of speed, but also through dimensions such as reduced repetition, lower cognitive load, and fewer mistakes.</p><p>We then conducted a large-scale survey with our primary users, <strong>the agent</strong>s. We reviewed hundreds of comments one by one, grouped recurring problems, and identified the most urgent productivity challenges. These insights revealed consistent pain points such as interrupted workflows, excessive manual steps, lack of flexibility in return and cancellation processes, and limited visibility into critical information at the right moment.</p><p>In addition to these studies, we conducted separate focus group sessions with the <strong>CX-GO</strong> team. Rather than validating existing assumptions, these sessions were designed to explore the question <strong><em>“What does a productive day mean to you?”</em></strong><em> </em>from the agents’ own perspective. Hearing their daily struggles, workarounds, and expectations firsthand helped us uncover operational realities that surveys alone could not reveal. These insights played a complementary role, grounding our efficiency efforts in concrete user scenarios and real-world constraints.</p><h4>2. We Redesigned Training Processes and Shortened the Learning Curve</h4><p>The first step in an agent’s productivity journey is <strong>training</strong>. For Trendyol, onboarding each new agent represents a significant cost and investment. Trainers traveled to different cities, providing 7–8 days of in-person sessions. To optimize this process and achieve cost efficiency, we held one-on-one meetings with trainers to analyze the current <strong>onboarding flow</strong>. We learned that the lack of access to real screens during training was a barrier. It prolonged the learning curve and made system adaptation more difficult.</p><p>To solve this, we created <strong>prototype simulations</strong> of the most commonly used CX-GO flows. These simulations enabled trainers to provide an experience that closely reflected real screens. As a result, we reduced both travel and training time while helping agents adapt more quickly. The impact was measurable: in 2022–2023, the average satisfaction score of new agents during their first two months was <strong>4.0.</strong> After introducing simulation-supported training in 2024, this increased to <strong>4.2.</strong></p><p>We also collaborated with product managers and developers to work toward building a full test environment that would strengthen this new training model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5SvX9PFO6D8_fdO6bBDaog.png" /><figcaption>CX-GO Simulation Prototypes on Figma</figcaption></figure><h4>3. We Focused on Solving Customer Problems at First Touch</h4><p>Trendyol Assistant is the first stop in the customer service journey, making it a core part of our productivity strategy. Our goal is to solve customer issues without requiring transfer to an agent. This not only creates a smoother customer experience but also reduces repetitive customer traffic and lightens agent workloads.</p><p>We regularly review flows and analyze all performance indicators each month. By doing so, we identify where customers need the most help and where they get stuck. Based on these insights, we optimize menus and navigation so customers reach the information they need faster. Every action we take aims to reduce agent load and prevent customers from entering a repetitive support cycle.</p><p>To learn more about Trendyol Assistant, you can read the article I’ve linked below:</p><p><a href="https://medium.com/trendyol-tech/better-customer-experience-trendyol-assistant-journey-659a5b1e84e1">Better Customer Experience: Trendyol Assistant Journey</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PTeX4vXWkmT7Icg7VCSwDw.png" /><figcaption>Flow Review</figcaption></figure><h4>4. We Started Tracking Efficiency by Making Data Measurable</h4><p>To address our biggest gap, which was the lack of measurable data, we took action. Although we had certain business KPIs and user experience metrics such as CSAT and CES, we could not measure the direct impact of our designs on agent efficiency. We had no data infrastructure that would allow us to understand whether a feature we launched actually made processes faster.</p><p>To solve this, we built dedicated data tracking infrastructures in the <strong>CX-Core</strong> and <strong>Connect</strong> domains, enabling us to monitor user behavior. We can now clearly see how long it takes an agent to complete a task and at which steps they experience difficulty.</p><p>For example, one of the most frequently performed actions in <strong>CX-Core</strong> was the ticket creation process. Customers could create requests under different ticket types such as “The branch is not delivering my package.” We identified the most frequently opened ticket types with data and then mapped the user flows of these actions. Thanks to the data infrastructure we built, we measured the average time all agents spent on these flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k4-wH7u_A86HoHVyVBjJ2w.png" /><figcaption>User Flows and Durations of Most Opened Tickets</figcaption></figure><p>Together with the business team, we identified unnecessary steps and made design improvements to simplify these flows. As a result, when comparing May and September, we observed the following time-based changes for the top three most opened ticket types:</p><ul><li><strong>“The branch is not delivering my package”</strong><br> Ticket volume increased by <strong>28%</strong>, while opening time decreased by <strong>11%</strong>.</li><li><strong>“My package has been on the way for too long (estimated delivery date passed)”</strong><br> Ticket volume increased by <strong>37%</strong>, with a <strong>5% reduction</strong> in opening time.</li><li><strong>“Return from address / pickup return request”</strong><br> Ticket volume increased by <strong>36%</strong>, while opening time decreased by <strong>16%</strong>, representing the highest improvement.</li></ul><p>This work not only shortened a process but also significantly reduced the daily workload of thousands of agents. With this success, we are determined to continue our data driven improvements that enhance agent efficiency.</p><p>Similarly, we took steps to increase measurability for <strong>CX-GO</strong> as well. Since this product operates on the Delphoi platform, teams were initially hesitant about the cost and effort associated with a potential platform shift. Instead of focusing on limitations, we prioritized making the best use of the tool we had. For this purpose, we collaborated with the business and technical teams to explore Delphoi’s capabilities. We discovered that new features added to the platform had not been sending events for a long time, and we addressed this gap by creating and documenting prioritized event lists.</p><p>We can now track agent activity on CX-GO screens with data and shape new design decisions based on both user feedback and <strong>real behavioral insights</strong>. Ensuring every new feature goes live with event tracking allows us to clearly see its successes and failures. This enables us to support our design decisions not only with hypotheses and agent comments but also with direct behavioral data.</p><h4>5. We Integrated Artificial Intelligence Into Our Processes</h4><p>To move our efficiency journey forward, we integrated artificial intelligence (AI) into our workflows. This integration not only increased our operational speed but also improved consistency and quality in both customer and agent experiences.</p><p>On the <strong>CX-GO</strong> side, <strong>AI powered guidance</strong> modules within the help center enabled agents to quickly access the right information and shorten resolution times.</p><p>At the same time, we launched the <strong>AI powered Automatic Quality Assurance</strong> project for the <strong>Quality Tool</strong> within <strong>Connect</strong>. By automating quality control processes, this project provided our quality specialists with both speed and consistency. As a result, our quality scores increased from <strong>88 in 2024 to 90 in March 2025</strong>. If you would like to learn more about this project, you can read the article linked below:</p><p><a href="https://medium.com/trendyol-tech/quality-assurance-supported-by-ai-in-customer-services-07f07fd229c7">Quality Assurance Supported by AI in Customer Services</a></p><p>Alongside this major project, we also introduced small but impactful AI enhancements that simplify daily workflows:</p><ul><li><strong>Previous Chat Summary:</strong> For customers who contact agents multiple times for the same issue, we began summarizing previous chat sessions using AI. This allows agents to understand the situation quickly without reading every past message and helps them save time.</li><li><strong>Contact Reason Recommendation: </strong>We reduced agent workload by enabling AI to automatically suggest the contact reason based on conversation content, instead of agents selecting it manually.</li><li><strong>AI Assisted Guidance: </strong>To help agents provide accurate guidance about customer orders, we built an AI based recommendation system. The model analyzes knowledge base documents together with the customer’s contact and delivery information and suggests the most appropriate action based on documented rules.</li></ul><p>All of these steps are clear evidence that artificial intelligence has significantly elevated the quality of our operations.</p><h4>6. We Made Customer Feedback Meaningful</h4><p>Another area where we leveraged the power of artificial intelligence was the analysis of customer feedback. Reviewing hundreds of thousands of feedback entries manually each day was time consuming and resource intensive. To solve this, we developed <strong>TrendTopic</strong>, an AI powered text analysis tool that transforms customer comments into meaningful insights.</p><p>With this tool, our goal was to analyze approx<strong>imately 1.3 million open ended comments and more than 26 million call and chat interactions per year,</strong> while also detecting real time crisis topics at an early stage.</p><p>The results we achieved were highly impressive:</p><ul><li>Across analysis, quality, and other teams, we saved approximately <strong>1,440 hours</strong> of manual analysis per year.</li><li>The platform allowed us to <strong>identify emerging trend topics</strong> early by using insights generated from chat and call center data.</li><li>We enabled UX researchers to upload their own datasets and perform fast and scalable analyses.</li><li>Thanks to the <strong>“Summarize with AI”</strong> feature, the system scans all main categories and automatically generates summaries from comments. With this capability, our teams will save approximately <strong>14,000 hours of analysis time annually</strong>.</li></ul><p>This tool not only provides a technological solution but also responds strongly to one of Trendyol’s key priorities this year. By automating manual processes, we gained both speed and efficiency, allowing us to use our resources more strategically. As a result, we established a systematic approach that helps us take faster and more effective actions to improve customer experience while also optimizing costs.</p><h4>7. We Improved Our Auto-Fill and Suggestion Systems</h4><p>Using insights from our data analyses, we identified the areas where agents were losing the most time.</p><p>For example, in return processes within <strong>CX-GO</strong> and <strong>CX-Core</strong>, agents previously had to select the return reason and add notes for each product individually. We automated this repetitive task so agents can now make bulk selections for all products and complete the process much faster. This simple improvement significantly reduced agent workload and contributed greatly to operational efficiency.</p><p>We also conducted a<strong> User Acceptance Test (UAT)</strong> for CX-Core ticket flows. During this session, we noticed that some fields agents were filling manually (such as the shipping company) already existed in the system and could be auto-filled. We implemented this enhancement, and as a result, agents gained substantial speed in completing their tasks.</p><p>In <strong>Connect</strong>, agents select the main and sub contact reasons for why a customer reached out, and there is also an additional description field. With the improvement we made, this description field is now automatically filled when specific main and sub contact reasons are selected. Agents can still edit the text if needed, which eliminates the need to write the explanation from scratch every time.</p><h4>8. Supported Team Development Through Coaching Programs</h4><p>We knew that supporting productivity required not only technological tools but also <strong>human-centered approaches</strong>. Within this scope, we launched a new<strong> coaching program</strong> aimed at investing in the development of our agents.</p><p>This program is designed to identify individual development areas for agents and provide them with tailored support. If a agent’s performance evaluation (e.g., quality scores) indicates the need for coaching by authorized quality specialists, the agent is enrolled in the program.</p><p>This approach helps prevent repeated errors and ensures that each agent can reach their full potential. This personal and goal-oriented method not only boosts agents’ motivation but also continuously enhances overall team productivity and service quality.</p><p><strong>The results clearly demonstrate the impact of this approach</strong></p><p>After implementing the coaching program, we observed a noticeable improvement in quality scores within just two months.</p><ul><li>During this period, a total of <strong>497 evaluations were conducted</strong>, with <strong>111 agents</strong> receiving coaching support.</li><li><strong>EU Chat Quality Score:</strong> 88,6 → 91,1</li><li><strong>EU BO Quality Score:</strong> 88,9 → 97,3</li></ul><p>Most importantly, <strong>we doubled our evaluation volume</strong> with the same headcount. At the beginning of the year, there were around <strong>2,500 quality evaluations</strong>; by August, this number had reached <strong>5,500</strong>.</p><p>These numbers clearly show that human-centered development programs have a strong impact not only on quality but also on scalable productivity and sustainable team growth.</p><h4>9. Ensuring Continuity by Staying on the Field and Collaborating with Stakeholders</h4><p>We knew that understanding the realities on the ground was critical in our efficiency journey. Our previous surveys and data analyses showed us <strong>what</strong> was happening, but to understand <strong>why</strong>, we needed to go into the field. Therefore, we visited our agents in <strong>their workspaces to observe working conditions and workflows firsthand</strong>. These one-on-one meetings and field studies provided us with deep insights based on real experiences that data alone could not capture. This allowed us to better understand our products and the daily challenges faced by our agents, shaping our designs around this reality.</p><p>At the same time, instead of managing the process alone, <strong>we involved all our stakeholders in this transformation</strong>. In periodic meetings, we reviewed our designs, development items, and feedback together. In these sessions, we focused less on <strong><em>“how does it look?”</em></strong> and more on <strong><em>“how does it work and how do we measure it?”</em></strong> ensuring everyone could contribute to and take ownership of the process. This collaborative culture not only increased the success of our efficiency projects but also helped us establish a shared goal across the entire ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jYALV4TQqCWoPTQgh3CKmQ.png" /><figcaption>Field Research — İzmir</figcaption></figure><h3>Efficiency: A Journey from Today to Tomorrow</h3><p>Throughout this process, we’ve learned that efficiency is not just about saving time — it’s about creating the right experience.<br>On this journey, we reduced our agents’ daily workload through thoughtful designs while directly contributing to the company’s strategic goals with data-driven decisions.<br>Quantitative data, combined with feedback from the field, guided us beyond screens and into the heart of the experience.</p><p>This approach has produced tangible results:</p><ul><li>🎓 <strong>Training Process:</strong><br>With prototype (simulation)-supported onboarding, agent satisfaction scores in the first two months increased from <strong>4.0 → 4.2.</strong></li><li>🕒 <strong>CX-Core Ticket Handling Time:</strong><br>Average processing times for the <strong>top 3 most opened ticket types</strong> decreased by <strong>5% to 11%</strong>.</li><li>⚙️ <strong>Auto-Filled Fields and Suggestions:</strong><br>Repetitive actions were reduced; for example, carrier and description fields are now automatically populated.</li><li>🤖 <strong>AI-Supported Automations:</strong><br>We enhanced agent experience along <strong>speed, accuracy, and efficiency</strong> dimensions.</li><li>💬 <strong>Quality Program and Coaching Impact:</strong><br>Following AI-supported quality automation and the coaching program, quality scores improved significantly:</li><li>EU Chat: <strong>88,6 → 91,1</strong></li><li>EU BO: <strong>88,9 → 97,3</strong></li><li>Additionally, <strong>we doubled our evaluation volume with the same headcount </strong>; quality assessments rose from around <strong>2,500</strong> at the beginning of the year to <strong>5,500 by August</strong>.</li><li>🧠 <strong>TrendTopic AI tool:</strong><br>We saved approximately <strong>1,440 hours</strong> of manual analysis annually.<br>With the <strong>“Summarize with AI” feature,</strong> the system scans all main categories and automatically generates summaries from comments, giving our teams roughly<strong> 14,000 hours of annual automation gains.</strong></li></ul><p>All these developments prove that efficiency is not just about speed — it’s about getting to the right information in the shortest time. But we know this is only the beginning.</p><p>In the coming period, we plan to take steps to further deepen our efficiency focus. Our primary goal is to make micro-interactions and user flows in our existing products smarter, maximizing the value of every second for our agents.</p><p>We aim to expand<strong> automation efforts </strong>and <strong>support decision-making processes</strong> with recommendation systems.</p><p>Furthermore, we will use AI not only to accelerate operations but also as a tool to personalize experiences and provide predictive insights. This will allow agents to access needed information instantly, with the system continuously improving based on user behavior.</p><p>At the same time, by regularizing field observations and agent feedback, we will integrate more human-centered insights into our product development cycles. Efficiency will therefore be shaped not only by technology but also <strong>by the voice, observation, and contribution of our agents.</strong></p><p>In short, our goal is to optimize today while unlocking the potential of tomorrow. For us, efficiency is not a finished goal; <strong>it’s a continuously evolving journey.</strong></p><p><strong>Thanks 🧡</strong><br>The successes we’ve achieved on this journey were not the result of a single team, but the collective effort and collaboration of all our stakeholders.<br>At the heart of this transformation, which centers both efficiency and people, were our <strong>agents</strong>. Their contributions and feedback laid the foundation for every step we took.</p><p>I would like to sincerely thank <strong>Cenk Yılmaz, Saba Merc, Burcu Tan, Çağla Bayrak, Belgüzar Damat Keskin, Merve Çolak Özkan, Çağrı Gürkan, Merve Dolmacı, Elif Yaraman Ayten, Eda Yarıcı, </strong>and<strong> Hesna Merve Kahraman</strong> for their invaluable contributions and support throughout this process.</p><p>Additionally, although not mentioned by name here, we extend our gratitude to all our <strong>product managers, business teams, engineering teams, and the customer experience teams</strong> who stood by us at every step.</p><p><a href="https://careers.trendyol.com/?source=post_page-----a42ea069f696---------------------------------------">Home - Trendyol Careers</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57642101e933" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trendyol-tech/our-efficiency-journey-in-trendyol-customer-services-products-57642101e933">Our Efficiency Journey in Trendyol Customer Services Products</a> was originally published in <a href="https://medium.com/trendyol-tech">Trendyol Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Understand Customers for Trendyol B2B Portal: User Interviews]]></title>
            <link>https://medium.com/trendyol-tech/how-to-understand-customers-for-trendyol-b2b-portal-user-interviews-96b9ff218116?source=rss-88724e492370------2</link>
            <guid isPermaLink="false">https://medium.com/p/96b9ff218116</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[b2b]]></category>
            <dc:creator><![CDATA[Feyza Nur Khassanov]]></dc:creator>
            <pubDate>Wed, 15 Nov 2023 11:34:04 GMT</pubDate>
            <atom:updated>2023-11-15T11:35:28.641Z</atom:updated>
            <content:encoded><![CDATA[<h4>We would like to share with you our process of how we planned user interviews at Trendyol B2B Portal, what we learned in this process, and how we created a backlog.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZ9O4mQcagweChF3mYrGWw.png" /></figure><h3>What is the B2B Portal?</h3><p>One of the products that our team has collectively worked on is the Trendyol B2B Portal. This platform serves as a wholesale portal for global buyers for wholesale product purchases. It is not a public website at the moment, so it is easier to interview since we have certain customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wT5BaFf_IY2Z1cDfLsYs0w.png" /><figcaption><strong>List &amp; Product Detail Page</strong> <strong>of Trendyol B2B Portal</strong> (Prices do not reflect the real values.)</figcaption></figure><h3>What We Need for Portal</h3><p>Our primary objective with this product is to step beyond the familiar realm of B2C user experiences and craft a UX process tailored to unique needs and expectations.</p><p>In light of this goal, the evaluation of screen usability has become a pivotal aspect of our UX Research flows. During feedback sessions, we identified certain pain points on the pages we delivered/designed. Now, our focus is on delving deeper into the process, accurately analyzing user behavior, and formulating effective solutions to address these pain points. This marks the next crucial step in our journey of enhancing user experiences.</p><h3>Why Did We Choose User Interviews?</h3><p>To gain a precise understanding of the pain points we encountered, we recognized the vital importance of real-time observations of our customers’ experiences and their reactions. We believed that this went beyond the scope of a static survey. As a result, we made the strategic choice to engage in user interviews with our target audience, whom we categorize as ‘power users’ due to their high digital literacy and usage of other B2B platforms. These interviews were designed not only to validate our initial findings but also to unearth potential pain points within the platform.</p><p>Some of these pain points we anticipated were:<br>- Category tree structure that differs from other platforms for filtering,<br>- Mega menu usage,<br>- Understandability of the product in the cart,<br>- Whether “Decreased in Stock” is visible in the cart or not and if it is clear what the filter does.</p><p>We started planning meetings to clarify and resolve these anticipated pain points.</p><h3>Planning the User Interview</h3><p>Before commencing our user interviews, we took the essential step of defining our objectives in writing and began our preparations.</p><h4>Creating a Question Plan</h4><p>We collaborated with our Product Manager and Business team to establish a clear plan for soliciting feedback on our platform. This plan served as a crucial resource for the Researcher who would be working with us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wgyGvlF9WO3mUCVVxuaEig.png" /><figcaption><strong>Plan of User Interview</strong></figcaption></figure><p>To gather comprehensive feedback, we meticulously documented all the pages and features that users interacted with during their purchasing journeys. On these pages, we specifically pinpointed the features we anticipated users might encounter difficulties with.</p><p>Additionally, we identified sections where we could gain insights into the features they found valuable and those they didn’t. This comprehensive approach ensured that we covered all aspects of the user experience, from potential pain points to areas of improvement, and provided a robust framework for our research efforts.</p><p>After finalizing our planning, we conducted a meeting with the Researcher. The Business team provided a detailed platform overview and discussed the research plan. This meeting ensured that the Researcher had a clear understanding of our platform and the objectives of our research, setting the stage for productive user interviews and valuable insights.</p><h4>Creating a Scenario</h4><p>After the meeting, the Researcher crafted a set of interview questions. This streamlined the interview process, ensuring that no key questions were missed and contributing to its overall efficiency.</p><p>When creating these questions, the primary focus was to make sure they did not guide or influence the users’ responses. We aimed for neutrality, allowing users to share their genuine feedback without any leading prompts.</p><p>During the user interviews, our Design, Business, and Product teams collaborated via Zoom Webinar. We discreetly observed users, noting their interactions and issues without their knowledge to minimize potential stress due to a large audience presence.</p><h3>Talking About the Findings</h3><p>All teams convened to discuss the issues observed during meetings, using a file prepared by the Researcher as a reference.</p><p>It showed that some of the pain points we found matched our predictions before we even started the user interview, some were not a problem at all, and some items we had never thought of required reconsidering.</p><p>For example;</p><ul><li><strong>Many customers </strong>faced challenges navigating the category filter on the listing page due to its tree structure,</li><li><strong>Some</strong> <strong>customers</strong> quickly found the mega menu and effortlessly accessed the topics they needed.</li><li>Although we used a cart icon on listing page cards to signify a product in the user’s cart, this wasn’t clear to <strong>most customers</strong>,</li><li><strong>Half of the customers</strong> want to search for the code of the product in the cart, although we never thought of needing it,</li><li>It was observed that the “Decreased in Stock” filter was challenging for <strong>new customers</strong> to discover.</li></ul><h4>Creating a Backlog</h4><p>After our discussions, we documented the relevant items in the Backlog file. We prioritized tasks based on their ease and impact, with some already implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5xXT-RbVfKnSh7uVAW5EQ.png" /></figure><p>After we move our items from the backlog to a live environment, we will either receive one-on-one feedback or meet with our customers again after some time. This approach will allow us to test the changes we’ve made.</p><h3>Conclusion</h3><p>The journey of planning user interviews at the B2B Portal has been a collaborative and enlightening experience. Through these interviews, we’ve gained invaluable insights that are instrumental in shaping a more user-friendly and efficient platform. Our commitment to continuous improvement remains steadfast, and we’re excited about the positive changes we’ve already implemented.</p><p>As we move forward, our focus will be on testing these improvements with our users and further enhancing the customer experience. We’re dedicated to meeting the evolving needs of our expanding user community and ensuring that the B2B Portal continues to be a valuable resource for our customers.</p><p>I would like to thank Feryal Erkoçak, Meray Yağmur Can, Saba Merc, Nisan Özdilli, and Cenk Yılmaz for helping me on this journey.</p><p>If you want to be part of a team that tries new technologies and want to experience a new challenge every day, come to us.</p><p><a href="https://jobs.lever.co/trendyol?source=post_page-----179ed9e1f8b3--------------------------------">Trendyol jobs</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96b9ff218116" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trendyol-tech/how-to-understand-customers-for-trendyol-b2b-portal-user-interviews-96b9ff218116">How to Understand Customers for Trendyol B2B Portal: User Interviews</a> was originally published in <a href="https://medium.com/trendyol-tech">Trendyol Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>