<?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 Chamara Silva on Medium]]></title>
        <description><![CDATA[Stories by Chamara Silva on Medium]]></description>
        <link>https://medium.com/@chamarasilva?source=rss-674b922c3f7c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_hsx3n1DZp-38Y09RsQMvA.png</url>
            <title>Stories by Chamara Silva on Medium</title>
            <link>https://medium.com/@chamarasilva?source=rss-674b922c3f7c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:49:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chamarasilva/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[Is AI Quietly Fading Your Technical Depth?]]></title>
            <link>https://medium.com/@chamarasilva/is-ai-quietly-fading-your-technical-depth-23b3bd4c461a?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/23b3bd4c461a</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Wed, 11 Mar 2026 06:36:31 GMT</pubDate>
            <atom:updated>2026-03-11T06:36:31.176Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>“Amplify Your Expertise, Don’t Replace It”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8CGkwxfmmSPdeH_2Kc_iTw.png" /></figure><p>Artificial intelligence (AI) tools are reshaping organizational IT teams&#39; utilization of them, such as writing and debugging code, drafting documentation, and analyzing technical problems. With that, AI has become a mantra in day-to-day work life now.</p><p>As the AI-centric futuristic engineers, there are two questions that should have clear answers.</p><p><strong><em>Should I learn AI tools or become an expert prompt engineer?</em></strong></p><p><strong><em>Am I relying on AI too much, slowly eroding my technical depth?</em></strong></p><p>According to my view, this is an orthogonal question. Let&#39;s explore them honestly. Because the answers will shape whether AI makes your team genuinely stronger or quietly more fragile.</p><h3><strong>1. AI Tools vs Prompt Engineering—A False Choice</strong></h3><p>While I have multiple discussions with team leads, architects, technical leads, and the IT industry, their most common discussion point is whether the staff should “learn AI tools” or “become prompt engineers. &quot; That is a common false choice. My view is both are the answers. but in quite different ratios.</p><p>The real goal isn’t to create prompt engineers. It’s to build AI-fluent professionals who multiply their existing technical expertise with AI tools.</p><p><em>What Actually Moves the Needle?</em></p><h4>Develop an AI-First Mindset (Most Important)</h4><p>Before any tool or technique, the team needs a habit shift. As an example, before I spend 30 minutes on this, could AI do 80% of it in 2 minutes?</p><p>This mindset change has more ROI than any technical skill. It costs nothing to adopt and starts paying dividends from day one.</p><h4>Go Deep on Few Relevant Tools</h4><p>It is not needed to master every AI platform. Only need a clear idea of which tools fit your actual workflows. For most IT teams, that’s known as the <strong>Focused Toolkit.</strong></p><p><strong>Some well-known focused toolkits.</strong></p><ul><li>GitHub Copilot for coding and code reviews</li><li>Work with Claude, ChatGPT and Gemini for day-to-day technical-oriented work, write-ups and communication</li><li>Perplexity for technical or academic research</li><li>Is AI-native features in your existing stack (<a href="https://www.datadoghq.com/blog/datadog-ai-innovation/">Datadog</a>, <a href="https://wso2.ai/">WSO2</a>, etc.)</li></ul><h4>Prompting is a craft skill, not a specialty.</h4><p>Everyone should be a <strong>good enough prompter</strong>. It is not mandatory to have the dedicated prompt engineer. The trick is four main practical habits, which gain 90% of precise AI results.</p><ul><li>To give context, describe your role, the goal, and any constraints.</li><li>Provide examples when format or tone matters.</li><li>Break complex tasks into steps rather than one giant request.</li><li>Ask it to critique its own output before you accept it.</li></ul><h4>Build a Prompt Library</h4><p>Nothing accelerates adoption faster than contextual knowledge. My suggestion is a shared prompt library or internal wiki makes it faster for others to do effective prompting. Otherwise, everybody should tune the prompt from scratch all the time.</p><blockquote>Example: Use AI for software application issue tracing and code reviews, which beats individual skill-building every time. One person’s breakthrough becomes the whole team’s baseline.</blockquote><h3>2. The Dependency Trap — When AI Becomes a Crutch</h3><p>The uncomfortable truth is yes. Excessive AI reliance can slowly fade the technical skill sets. And it can happen gradually, without anyone noticing until it’s already a problem.</p><h4>The GPS Problem</h4><p>Think about GPS navigation. People who rely on it 100% have lost the ability to read maps or build mental models of cities. They can get from A to B, but they can’t reason about routes when the signal drops. AI dependency also works in the same way. The symptoms are subtle but compounding.</p><p><em>Some symptoms...</em></p><ul><li>You stop debugging by reasoning, and you just paste errors into Claude.</li><li>You stop remembering syntax and you wait for Copilot to suggest it.</li><li>You stop designing solutions, and you may ask AI to architect them for you.</li><li>Over time, your mental models atrophy from lack of use.</li></ul><h4>Who Is Most at Risk?</h4><p>Junior and mid-level engineers are especially vulnerable because they risk skipping the struggle phase of learning, which is exactly where deep technical understanding forms. The compounding effect is dangerous. Finally, it becomes dependent but not competent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDPT1ceA6Uz4eJxAmrAbVw.png" /></figure><h4>Healthy vs. Harmful AI Use</h4><p>The distinction isn’t about how often you use AI. It’s about how you engage with it. Healthy use means leveraging AI to accelerate work you already understand which is drafting faster, exploring options and catching blind spots. Harmful use is when AI becomes a shortcut around thinking itself pasting errors without reasoning, shipping code you can’t explain or letting AI design solutions because thinking feels slower.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u5v0_iBkYE6J4U_A0VD4ng.png" /></figure><h3>3. What IT Teams Actually Should Do</h3><p><strong><em>The Golden Rule:</em></strong><em> “</em><strong><em>Use AI to amplify your knowledge, not replace the process of building it.”</em></strong></p><p>Let&#39;s see the following practical example to understand the situation better.</p><p>Ex: A senior engineer using Copilot is like a master chef using a food processor as the tool to speed up the work. But the expertise still drives every decision.</p><p>A junior engineer using Copilot without understanding the output is like a student using a calculator without knowing math. They get answers, but no understanding. The impact of this situation will be felt after a few years. Because these junior engineers will become senior engineers in the future but like slaves of AI.</p><p>By considering those factors, I strongly believe following practical recommendations should work, especially for the IT-centric teams.</p><h3>4. Practical Recommendations for IT Teams</h3><p>You may already know some of these recommendations, but they are worth making as a norm.</p><p><strong>Set a ‘understand before you ship’ norm</strong></p><blockquote>Don&#39;t copy-paste AI output or results if you can’t explain them. If you can’t describe what the code does line-by-line, it’s not ready to deploy.</blockquote><p><strong>Run deliberate AI-off exercises</strong></p><blockquote>Regular whiteboard sessions, manual debugging exercises, and code reviews without AI assistance. It keeps mental models sharp.</blockquote><p><strong>Make learning visible for junior staff</strong></p><blockquote>Junior team members should still be expected to struggle through problems. Struggle is the mechanism of learning. Don’t shortcut it.</blockquote><p><strong>Create a team prompt playbook</strong></p><blockquote>Document what works. A shared library of high-quality prompts for common IT tasks (incident reports, runbooks, code reviews) is a force multiplier.</blockquote><p><strong>Treat AI like a senior colleague</strong></p><blockquote>You would consult a senior colleague for ideas. But you should verify their suggestions and apply your own judgment before acting. Do the same with AI as well.</blockquote><h3>Closing Thought</h3><p>Treat AI like you treat Google. Everyone should be good at it. Nobody needs to specialize in it and the best way to improve is to use it constantly on real work and share what works.</p><p>The IT professionals who will thrive aren’t those who use AI the most. They’re those who use AI <strong><em>intentionally</em></strong>. They bring their own expertise to every AI interaction. They verify before they trust, and they never stop doing the hard thinking that makes them genuinely valuable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23b3bd4c461a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“The Ghost in the Cloud” Why Your Servers are Burning Cash?]]></title>
            <link>https://medium.com/@chamarasilva/the-ghost-in-the-cloud-why-your-servers-are-burning-cash-680b6c7cd9a8?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/680b6c7cd9a8</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[data-center]]></category>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 19:20:34 GMT</pubDate>
            <atom:updated>2026-03-16T05:38:37.728Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2QVfEKZYSHsgT-1XTk16dw.png" /></figure><p>Imagine a massive, high-end restaurant. The lights are blazing, the ovens are preheated to 500 degrees and a full staff is standing at attention. But throughout the entire dinner rush, only <strong>two tables</strong> are occupied.</p><p>This isn’t a failing business? This is the current state of global cloud computing.</p><p>Today, data centers swallow <strong>1.5% of the world’s electricity</strong>. By 2030, that number is projected to double. We have the most advanced cloud infrastructure in history. But the logic we use to run it hasn’t changed in ten years. We talk a big game about efficiency, but under the hood these ‘digital cathedrals’ are actually too wasteful of energy.</p><h4>The 13% Ghost Town</h4><p>As per the global term, cloud platforms would be the ultimate optimizer, paying only for what we use. According to my experience, reality is a staggering disconnect. Even though cloud platform providers talk about the “Power Usage Effectiveness,&quot; the actual machines inside are barely breaking a sweat. It proves how these vendors are heavily investing in power management, renewable energy, etc.</p><ul><li><strong>The Reality Check:</strong> Average CPU utilization across major cloud clusters sits at a measly <strong>13%</strong>.</li><li><strong>The Waste:</strong> Roughly <strong>30% of cloud spend</strong> is tossed into the void, paying for resources that sit idle.</li><li><strong>The Silent Killer:</strong> An idle server still drains about <strong>two-thirds</strong> of its peak power. It’s burning electricity, generating heat, and emitting carbon to do absolutely nothing.</li></ul><p>The culprit is the <strong>scheduler.</strong> The scheduler is working as the air traffic controller of the cloud. It decides which digital task lands on which physical server. These schedulers are blind to the &quot;context.&quot; They don’t know if a server is running dangerously hot, if network latency is spiking, or if that specific region is currently drawing power from a coal plant instead of a nuclear power plant. They allocate resources based on how the world was configured, not how it actually <em>is</em>.</p><h4>The solution is the context-aware revolution</h4><p>We are moving away from “rule books&quot; and toward &quot;real-time reasoning.&quot; This is known as &quot;<strong>Context-Aware Workload Optimization.</strong> Instead of a fixed table of rules, a modern scheduler acts more like a high-frequency trader. It ingests a constant stream of “Live Signals” such as,</p><ul><li><strong>Energy Efficienc : </strong>Which node is currently the “greenest” or lowest carbon emission?</li><li><strong>Network Health :</strong> Where is the path of least resistance right now?</li><li><strong>SLA Urgency :</strong> Which tasks are minutes away from a deadline?</li><li><strong>Thermal Data :</strong> Is this rack overheating?</li></ul><h4>Conclusion of Real-Time Workload Optimization</h4><p>The cloud has never been more powerful and arguably never more wasteful. Context-aware workload optimization is not a futuristic concept or an academic nicety when it comes to the efficient cloud platforms. It is the missing layer that transforms a cloud from a static grid of overprovisioned servers into a living, reasoning system that knows which node is the greenest right now, which task is taking less execution time, and which rack is quietly cooking itself while billing you for the privilege. The ghost in the cloud is that invisible torrent of wasted watts, idle CPUs, and carbon emitted to do nothing.</p><p>When schedulers stop looking backward at rules and start reading the room in real time, the restaurant finally stops heating empty tables. That is not just better engineering. That is the only sustainable path forward. How about your experience?</p><h3>References</h3><ol><li>Lawrence Berkeley National Laboratory (2024).<em>2024 United States Data Center Energy Usage Report</em>. U.S. Department of Energy.<a href="https://www.energy.gov/articles/doe-releases-new-report-evaluating-increase-electricity-demand-data-centers">energy.gov</a></li><li>International Energy Agency (2024).<em>Energy and AI: Energy Demand from AI</em>. IEA.<a href="https://www.iea.org/reports/energy-and-ai/energy-demand-from-ai">iea.org</a></li><li>Cast AI (2024). Kubernetes Resource Utilisation Report 2024, as reported by Data Centre Dynamics.<a href="https://www.datacenterdynamics.com/en/news/only-13-of-provisioned-cpus-and-20-of-memory-utilized-in-cloud-computing-report/">datacenterdynamics.com</a></li><li>Shah, S. (2024). Optimised Load Balancing Techniques in Cloud Computing Environment: A Systematic Literature Review. <em>Towards Excellence</em>, 16(3).</li><li>ScienceDirect Topics. Server Utilization overview.<a href="https://www.sciencedirect.com/topics/computer-science/server-utilization">sciencedirect.com</a></li><li>Flexera (2024).<em>State of the Cloud Report</em>, as cited in Faddom Cloud Statistics.<a href="https://faddom.com/29-cloud-computing-statistics-you-must-know-in-2025/">faddom.com</a></li><li>Edinger, J. (2019).<em>Context-Aware Task Scheduling in Distributed Computing Systems</em>. Inaugural dissertation.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=680b6c7cd9a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the Team Potential from Leadership Perspective]]></title>
            <link>https://medium.com/@chamarasilva/understanding-the-team-potential-from-leadership-perspective-19d4cee655fb?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/19d4cee655fb</guid>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Mon, 17 Feb 2025 19:43:34 GMT</pubDate>
            <atom:updated>2025-02-17T19:45:20.971Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ATsu7QSH8hn5OkgrDbv3ow.jpeg" /></figure><p>Throughout my journey as a team lead in the tech industry, I am privilege of working with a wide range of team members. Some are dependable, simply getting the job done. while others go above and beyond, truly driving success and innovation.</p><p>So what sets these high-potential team member apart?</p><p>It’s not just about the work they do, but the mindset and qualities they bring to the table. Recognizing and nurturing these individuals can be a game-changer, boosting both team performance and the overall culture of excellence. Here’s how I spot them according to my experience.</p><h4><strong>Confident, Not Arrogant</strong></h4><p>High-potential team members carry a quiet confidence. They’re aware of their strengths. but they always open to feedback and ways to improve. Instead of shying away from tough situations, they tackle them head-on with a calm and constructive approach and showing they’re not afraid to step up when needed.</p><h4><strong>Take Ownership, No Questions Asked</strong></h4><p>These team members don’t wait for instructions. they just take charge. Whether it’s solving a target problem, improving a process, or stepping in to help a colleague by instinctively taking responsibility. Their proactive nature ensures work keeps moving forward, even when things get tough.</p><h4><strong>Collaboration Comes First</strong></h4><p>Rather than getting into the unhealthy competition, high-potential member prioritize collaboration. They create win-win situations not just for themselves. but for the whole team. Making the work environment more productive and enjoyable.</p><h4><strong>Communicate Proactively</strong></h4><p>These individuals understand the importance of keeping leadership in the loop. They don’t wait until problems arise. they always share updates and potential challenges ahead of time. Because they have clear understanding about how the transparency prevents roadblocks and keeps everything running smoothly.</p><h4><strong>Focus on What Truly Matters</strong></h4><p>High-potential team members respect own time and others. They know when to say ‘no’ to unproductive activities or distractions like gossip. they usually focus on tasks that actually move the needle to ensure their time and energy are well-spent.</p><h4><strong>Fairness is Key</strong></h4><p>They treat everyone with respect, regardless of titles or positions. This mentality promotes inclusivity, creating a workplace where merit and hard work are truly valued and celebrated.</p><h4><strong>A Passion for Learning and Growth</strong></h4><p>These individuals have a natural curiosity. They seek out opportunities to learn, whether through mentorship, shadowing top performers, or just being open to new ideas. They take charge of their own development, constantly growing instead of waiting for formal training.</p><h4><strong>Goal-Oriented and Data-Driven</strong></h4><p>High performing team members set clear, measurable goals and stay focused on achieving them. They track progress using key performance indicators (KPIs), ensuring they’re constantly improving and staying on course to achieve long-term success.</p><h4><strong>They Know How to Protect Their Well-Being</strong></h4><p>Even though they’re high achievers, these team members understand the importance of work-life balance. This allows them to maintain their productivity while also avoiding burnout.</p><h4><strong>They Embrace Change and Innovation</strong></h4><p>Rather than resisting change, high-potential team members see it as an opportunity. They embrace new technologies, processes, and strategies with open arms, always looking for ways to innovate and make things better.</p><h4><strong>Final Thoughts</strong></h4><p>As leaders, identifying and supporting high-potential team members is crucial for the long-term success of the team and the organization. By encouraging their growth and providing them with the right opportunities, ensuring they have an environment where they can thrive, you’re not just helping them. you’re strengthening your entire team strategically.</p><p>Fostering these traits within a team isn’t just about being productive. it’s about creating a workplace where everyone is inspired to bring their best.</p><p>According to my experiance these qualities show who are the high potential team members in the team. Are you taking the time to identify and nurture the high-potential team members in your team? Open for the discussion….</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19d4cee655fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unexpected Lessons from My MSc Story]]></title>
            <link>https://medium.com/@chamarasilva/unexpected-lessons-from-my-msc-story-80b65b4877d4?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/80b65b4877d4</guid>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Tue, 28 Jan 2025 17:36:47 GMT</pubDate>
            <atom:updated>2025-01-28T17:36:47.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0Sd7Y5QcIyzMWhXG" /></figure><p>Embarking on an MSc is a big decision. It’s filled with excitement, anticipation, and, honestly, fear. I&#39;m bringing this post because I’ve lived it. My journey toward earning an MSc in Computer Science at the <a href="https://www.staffs.ac.uk/">University of Staffordshire</a> was filled with challenges, but it also turned out to be one of the most rewarding experiences of my life.</p><p>I want to share not just my story but also the lessons I learned along the way, in the hope that they inspire and guide you on your journey.</p><h4><em>Doubts vs Dreams</em></h4><p>When I started my MSc, I wasn’t entirely confident. Because I was in uncertainty whether the rigorous coursework disturbed my work responsibilities, etc. My approach was to jump into whatever the challenges were and win the challenge somehow. I believe it worked well, and here’s the first lesson I learned.</p><p><strong>Lesson 1: Start, even if you feel unprepared.</strong><br>Perfection is the enemy of progress. Waiting until you feel “ready” can hold you back. Taking that first step sets everything in motion.</p><h4>The Struggles vs Overcoming Challenges</h4><p>Balancing work, studies, and life wasn’t easy. Late nights were spent on understanding the theories, not memorizing theories. I often felt overwhelmed, especially when things didn’t go as planned. But with the guidance of my supervisors and the motivation of my peers, I realized that challenges are part of the process.</p><p><strong>Lesson 2: Seek support and don’t hesitate to ask for help.</strong><br>You don’t have to do it alone. Professors, peers, and mentors are there to guide you. Building a network of support can make a world of difference. Importantly, doing MSc alone and isolated never works. You need the right network!!</p><h4>The Breakthrough : Finding Purpose in the Process</h4><p>A turning point came when I presented my research paper, <strong>“Adaptability of Cloud Platforms for Model Neo Banks,”</strong> at the AIRC conference. It was then that I realized that my work could have a real-world impact. It wasn’t just about passing a course or earning a degree. It was about contributing to a larger conversation in technology and business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AgBEjWvhnJOx40lvtADH7g.png" /></figure><p><strong>Lesson 3: Focus on the impact of your work, not just the grade.</strong><br>When you see the bigger picture, your motivation skyrockets. Think about how your work could help others or solve real-world problems.</p><h4>The Success: It’s About Growth, Not Perfection</h4><p>Finally, I completed my MSc with distinction. I looked back at the journey with a deep sense of gratitude. It wasn’t perfect, and I certainly made mistakes along the way, but I grew in ways I never expected. My expertise in <strong>cloud computing, data science, project management, and machine learning</strong> expanded, but more importantly, I learned resilience, perseverance, and how to overcome self-doubt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3G5nhDfmkRG6nOjhaR_ow.png" /></figure><p><strong>Lesson 4: Growth is more valuable than perfection.</strong><br>Success isn’t just about the final result. It’s about who you become during the journey.</p><h4>Final Thoughts: Advice for Future MSc Friends</h4><p>Considering pursuing an MSc, here’s my advice,</p><ol><li><strong>Embrace the challenge.</strong> It will be hard, but the rewards far outweigh the struggles.</li><li><strong>Stay curious.</strong> Use every opportunity to explore new ideas and technologies.</li><li><strong>Celebrate small wins.</strong> Every step forward, no matter how small, is progress.</li></ol><p>Finally, success often comes in the most unexpected ways. If I could do it, so can you. Start your journey today. You&#39;ll be amazed at where it takes you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80b65b4877d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Competitive Advantage of Data Warehousing for Franchise Businesses —  A Case Study Overview —]]></title>
            <link>https://medium.com/@chamarasilva/the-competitive-advantage-of-data-warehousing-for-franchise-businesses-a-case-study-overview-70dd8c4a8457?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/70dd8c4a8457</guid>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Sun, 08 Sep 2024 06:34:09 GMT</pubDate>
            <atom:updated>2024-09-08T06:34:09.508Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Competitive Advantage of Data Warehousing for Franchise Businesses — A Case Study Overview —</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R9_arLoLGHpgiuk20Zd1Dg.png" /></figure><p>In today’s data-driven business landscape, <strong>data warehousing</strong> has emerged as a vital tool for businesses looking to optimize their operations, enhance decision-making, and drive growth. This blog delves into the <strong>competitive advantage</strong> data warehousing provides, particularly for franchise businesses, by focusing on a case study of the Foodad franchise chain. We will explore the key components of data warehousing, its business impact, and the methodologies involved in implementation.</p><h4>1. The Importance of Data-Driven Decision Making</h4><p>In the modern business environment, <strong>data is a crucial asset</strong>. Organizations rely heavily on data to drive informed decisions, forecast trends, and make strategic moves that improve competitiveness. For franchise businesses, data is essential for managing multiple outlets, monitoring performance, and ensuring consistency across locations.</p><p>Data warehousing enables businesses to collect, process, and integrate large amounts of historical data from various sources, including sales reports, inventory levels, and customer feedback. By providing a <strong>single version of the truth</strong>, data warehouses help decision-makers gain actionable insights that can steer the business toward sustained growth.</p><h4>2. Data Warehousing and its Role in Franchise Businesses</h4><p><strong>Data warehousing</strong> refers to the technology and processes involved in creating a centralized repository for large volumes of data from different sources. This repository is designed to be stable and efficient, offering both summarized and raw data to facilitate <strong>in-depth analysis</strong>.</p><p>For franchise businesses, managing data can be challenging due to the numerous outlets spread across different regions, each generating distinct datasets. Data inconsistencies and integration issues can hinder the ability to analyze trends, identify growth opportunities, and improve efficiency.</p><p><strong>A Foodad</strong> franchise case study is taken as an example case study to explain the importance of the data warehouse. for the franchise business. <strong>Foodad</strong> franchise, managing the outlets became a significant challenge due to <strong>data complexities and inconsistencies</strong>. As a result, expansion and business growth were slow. Recognizing this problem, a new investment company, <strong>JAVAMASTERMIND</strong>, sought to centralize Foodad’s data, streamline analysis, and develop growth strategies based on accurate data.</p><h4>3. Case Study: Foodad Franchise Chain</h4><p>The <strong>Foodad</strong> franchise faced considerable hurdles in managing its outlets due to inconsistent data. To solve these issues, <strong>JAVAMASTERMIND</strong> initiated a data warehousing project aimed at centralizing and analyzing the franchise’s data. The goal was to identify the key factors limiting business growth and implement strategies to overcome these hurdles.</p><p>The following methodologies and components were crucial to the success of this project:</p><ul><li><strong>Design Methodology</strong>: A <strong>mixed-mode approach</strong> was selected, combining both qualitative and quantitative data to ensure comprehensive insights.</li><li><strong>Data Collection</strong>: Monthly reports and outlet database structures were used for modeling.</li><li><strong>Fact and Dimension Modeling</strong>: Fact and dimension tables were modeled to organize the data and ensure accurate insights, focusing primarily on sales aspects.</li><li><strong>Snowflake Schema</strong>: The <strong>Kimball approach</strong> was followed, with the Snowflake schema used to structure the data warehouse.</li><li><strong>Data Security and Governance</strong>: Security measures were embedded at both the schema and data model levels to ensure data integrity and privacy.</li></ul><h4>4. The ETL Process: Ensuring Data Quality</h4><p>One of the most critical steps in data warehousing is the <strong>Extract, Transform, and Load (ETL)</strong> process. ETL ensures that data from disparate sources is cleaned, processed, and transformed into a unified format before being loaded into the data warehouse.</p><p>In the <strong>Foodad case study</strong>, ETL was carried out through <strong>SSIS (Microsoft Integration Services)</strong>. This process was tailored to extract data from the outlets (D-1), transform it according to business specifications, and load it into the data warehouse for analysis. The ETL process guarantees that only relevant and cleaned data is used for analysis, ensuring accuracy in decision-making.</p><h4>5. The Role of OLAP in Data Analysis</h4><p>Once the data is stored in the warehouse, it must be processed and analyzed to extract valuable insights. <strong>OLAP (Online Analytical Processing)</strong> plays a pivotal role in this process by allowing users to analyze data from multiple perspectives. OLAP models help in understanding the relationships between different data points and generating detailed reports.</p><p>In this case study, OLAP models were created using <strong>Visual Studio Analysis Service Tabular Projects</strong>, aligning with the business requirements set by JAVAMASTERMIND. These models enabled analysis on various aspects of sales, such as <strong>sales per outlet</strong>, <strong>menu sales</strong>, and <strong>monthly sales</strong>. The results from the OLAP analysis were then deployed to <strong>Microsoft SQL Server Analysis Services (SSAS)</strong> for further visualization.</p><h4>6. Data Visualization with Power BI</h4><p>Visualization is essential for understanding complex data. Using <strong>Power BI</strong>, the Foodad team could create visually compelling reports that allowed them to interpret data quickly and effectively. By visualizing the data in graphs, charts, and dashboards, decision-makers could easily track:</p><ul><li>Sales by outlet</li><li>Monthly revenue</li><li>Sales per menu item</li></ul><p>The ease of visualization allowed the team to identify underperforming outlets and products, adjust strategies accordingly, and monitor the results of those changes in real-time.</p><h4>7. The Competitive Advantage of Data Warehousing</h4><p>Data warehousing offers several <strong>competitive advantages</strong> for franchise businesses:</p><ul><li><strong>Centralized Data</strong>: By consolidating data from multiple outlets, franchises can gain a clearer picture of their operations and performance.</li><li><strong>Enhanced Decision Making</strong>: Accurate data allows franchise owners to make informed decisions that align with business objectives.</li><li><strong>Improved Efficiency</strong>: A data warehouse simplifies reporting and analysis, reducing the time and effort needed to manage multiple data sources.</li><li><strong>Scalability</strong>: As the business grows, a well-designed data warehouse can accommodate increasing data volumes and complexity.</li><li><strong>Data Security</strong>: Implementing security measures at the schema and model levels ensures that sensitive data is protected and accessible only to authorized personnel.</li></ul><h4>8. Conclusion: Transforming Business with Data Warehousing</h4><p>The <strong>Foodad case study</strong> illustrates the transformative power of data warehousing for franchise businesses. By centralizing data, improving data quality through the ETL process, and leveraging OLAP and visualization tools like Power BI, the Foodad franchise was able to overcome its data challenges and position itself for future growth.</p><p>Data warehousing enables businesses to harness the power of their data, transforming it into a valuable asset that can drive success in today’s competitive market. For franchise owners, investing in data warehousing can provide a significant advantage by enhancing operational efficiency, driving strategic decisions, and enabling scalable growth.</p><p><strong>Thank you for reading!</strong> Related presentation published in the <a href="https://www.researchgate.net/">ResearchGate</a> link <a href="https://dx.doi.org/10.13140/RG.2.2.13464.61443">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70dd8c4a8457" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Consumer Data Right (CDR)? -Open Banking Australia-]]></title>
            <link>https://medium.com/@chamarasilva/what-is-consumer-data-right-cdr-open-banking-australia-c68ea0e2b8e9?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c68ea0e2b8e9</guid>
            <category><![CDATA[banking-technology]]></category>
            <category><![CDATA[consumer-data-right]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[open-banking]]></category>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Thu, 05 Nov 2020 19:10:11 GMT</pubDate>
            <atom:updated>2020-11-06T02:11:30.154Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is Consumer Data Right (CDR)?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*5wa61grGNACcx7p__CHJIA.png" /></figure><p>Many organizations all over the world are collecting, managing, and consuming data for different business requirements. Old days organizations are exchanging and collecting data through manual interventions. However, data is more sensitive and want to handle carefully. Due to that reason, many government entities are taken up to consideration and come up with the regulatory standards to manage, maintain, and secure the data accordingly.</p><p>According to that consideration, the Australian government came up with a set of regulations to control and ensure consumer data. In order to do that, on the 26th of November 2017 Australian government introduced Consumer Data Right (<a href="https://www.accc.gov.au/focus-areas/consumer-data-right-cdr-0">CDR</a>) in Australia. CDR gives guidance for consumers to control their own data, including the ability to securely share the data with the trusted parties.</p><p>As a critical consumer data holder, the Australian government determined to apply CDR standards to the banking sector, and then it expands to the Energy and telecommunications sectors. Under the CDR, you can expose your data through the secured online systems to accredited parties. All data are exposing along with your consent and it is allowed to revoke your consent at any time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*wx_IiQu3h4Key72vd1l2SQ.png" /></figure><p>When it comes to the standard development, <a href="https://data61.csiro.au/">CSIRO’s Data61</a> has been appointed as the Data Standards Body (DSB) for the CDR regime. These standards have been prepared by the DSB. However, there are two main parties are involving in the close consultation for implementing CDR standards. <a href="https://www.accc.gov.au/focus-areas/consumer-data-right-cdr-0">Australian Competition and Consumer Commission (ACCC)</a> a lead regulator of the Consumer Data Right and <a href="https://www.oaic.gov.au/consumer-data-right/about-the-consumer-data-right/">Office of the Australian Information Commissioner (OAIC)</a> is supporting the ACCC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/267/1*zxAPWl-CjO-nreUPszQtTA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c68ea0e2b8e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essence of Go-Live]]></title>
            <link>https://medium.com/@chamarasilva/essence-of-go-live-ecada1cd6f40?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecada1cd6f40</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Thu, 23 Jul 2020 11:37:50 GMT</pubDate>
            <atom:updated>2020-07-23T11:37:50.615Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vKZ8orqkABhc08ShrnC9Iw.png" /></figure><p>Projects are consist of planning, Implementations, testings, and many activities. The project which is related to the software implementations ended up with Go-Live process. So the Go-Live phase will be the last stretch of the project.</p><p>Go-live is a combination of tasks and procedures. Therefore, Go-Live needs to be plan along with project planning as a practice. The go-Live event can target the following areas.</p><ol><li>Go-Live date</li><li>Live Time Window (LTW)</li><li>Planing Stakeholders</li><li>Cut-Over time</li><li>Go-Live Checklist</li><li>Testing and Verifications</li><li>Dependency Checks</li><li>Rollback Plan</li><li>Rehearsal Execution</li></ol><p><strong>Go-Live Date</strong></p><p>Fixing a day for a Go-Live is an important task while planning the project. When confirming the date, project implementation readiness, align with the End-user/Client requirement, practical risk factors can be considered. Because of unexpected issues, roadblocks need to be considered as a part of the risk analysis and add some buffer time for the Go-Live date.</p><p><strong>Live Time Window (LTW)</strong></p><p>Once the Go-Live date is fixed, Live Time Window (LTW) needs to be fixed. Some of this is known as a Change Window Time. In LTW, a specific time slot will be defined to make the application go live and handover to the live traffic. The most important thing is Before fixing the LTW, folks who involving the project, need to go under deep analysis on the live traffic patterns, application usage patterns if the end-user applications or systems are integrating with that. These analyses may do a month or a similar time. LTW needs to be confirmed based on the targeted time based on the lowest traffic pattern or external use time frame which is analyzed.</p><p><strong>Planing Stakeholders</strong></p><p>Before the planning, the Go-live dates and times, ensure about all parties need to be listed, invited, and involve in the project planning, implementation, and end-users. There it will be easy for everybody to be on the same page how the project moves from the first stage of the implementation.</p><p><strong>Cut-Over time</strong></p><p>The cut-Over time known as freezing time. When the project moves with the implementation, Freezing all implementations can be a plan before a fair amount of time to the Go-Live date. There all project implementation will be freeze and changes or any amendments to the existing project could not be accepted and only stabilizations and grooming can be done to the project. Therefore beginning of the implementation finalizing and notify project members cut-over dates will be an advantage.</p><p><strong>Go-Live Checklist</strong></p><p>Having a comprehensive checklist on the Go-Live will be the most important document in which the entire Go-Live keeps on the right track. Detail components of the project/application, changes need to be done on each component (configurations, security certificates, etc.), verification criteria will be included in the checklist.</p><p><strong>Testing and Verifications</strong></p><p>When it comes to the testing and verification phase under Go-Live, make sure to entire application/project is gone under full and comprehensive testing cycles. This includes comprehensive Functional, Security, Performance testing types. During the Go-Live time set of Pre-agreed tests known and <a href="https://en.wikipedia.org/wiki/Acceptance_testing#User_acceptance_testing">User Acceptance Tests</a> will be triggered to verify the final stability checks. Apart from that, all configurations changes need to be aligned with the live usage (Security <a href="https://en.wikipedia.org/wiki/Public_key_certificate">certificates</a>, Live endpoints, and configurations) that need to be verified under this phase. Optionally those can be tracked from the Go-Live Checklist also.</p><p><strong>Dependency Checks</strong></p><p>An application that is developing in the project may connect with third-party applications or systems to full fill the client requirement. Ensure all stakeholders and parties related to the dependant applications beforehand for the resiliency of application problems on Go-Live time.</p><p><strong>Rollback Plan</strong></p><p>There should not be a Go-Live plan without a Rollback plan. Because of many of the projects (Especially IT projects) become a disaster without having proper rollback plans. If something goes wrong and not work as expected during the Go-Live, There would be a proper process of rollbacking all changes and data to the previous stage and recover the application/system to the previous stage without any hassle. If any errors occurred during the Go-Live time especially on the Live Time Window, It is more dangerous to try to fix that on the ground. So the executing Rollback plan will be the safest and healthiness option. Therefore Rollback plan is the most vital part of the Go-Live.</p><p><strong>Rehearsal Execution</strong></p><p>Once all aforementioned phases are planned and applications are on the position to Go-Live, It will be an advantage to execute one or more Rehearsal/Dry run sessions to make sure the feasibility and check the practicality for the Go-Live. There, capture any missing points of-Live process and identify problems or issues proactively, and fixing those will be carried out. All of those will be helpful to the smooth Go-Live on the project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecada1cd6f40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting into the Open Banking]]></title>
            <link>https://medium.com/@chamarasilva/getting-into-the-open-banking-1b5b04f295bb?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b5b04f295bb</guid>
            <category><![CDATA[open-banking-systems]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[psd2]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[open-banking]]></category>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Thu, 29 Aug 2019 16:22:58 GMT</pubDate>
            <atom:updated>2019-08-29T16:22:58.036Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*oX9m4ziduQK1zGMS2KJzLg.jpeg" /></figure><p>When it’s getting into the open banking concepts, We would need to understand WHY open banking needed and what we are trying to achieve open banking. This post will help get some understanding of open banking landscape.</p><p><strong>Traditional Bank</strong></p><p>Wikipedia says, “A <a href="https://en.wikipedia.org/wiki/Bank"><strong>bank</strong></a> is a financial institution that accepts deposits from the public and creates credit. Lending activities can be performed either directly or indirectly through capital markets. Due to their importance in the financial stability of a country, <a href="https://en.wikipedia.org/wiki/Bank"><strong>banks</strong></a> are highly regulated in most countries.”</p><p>So the traditional bank is established according to the rules and regulations which are assigned by the country law or the region law. Most of the people use banks for their financial needs. In traditional banking expect users of the bank need to come physically and do the financial operations in the bank. financial transactions, security checks, and all operations are done physically in the bank.</p><p>Evolution of public civilization, people started finding ways to do their financial operations in easy manner rather than continuing the traditional ways. Open banking concept is came, as a result, overcome that problem. With that people are able to do all financial operations effectively by using the latest technology. EU region financial sector known as the most evolved Open Banking enabled financial sector. But, other countries such as Australia, Poland, Singapore, South Africa etc, are catching up very fast.</p><p><strong>Open Banking Regulatory Bodies</strong></p><p>As noted in the above section, all banks are bound to follow the set of rules and regulations. Mainly in the EU region, there are a number of regulatory bodies who conduct and verify whether the banks precisely follow the regulations. Those regulatory bodies we called as a “National Competent Authority” (NCA) and most of the time those are established country-based or region based.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y5zatsEh0g9dJPTRZ3ozmw.png" /></figure><p>Especially in the EU region, there are multiple NCA’s are established according to the sub-region. Like the UK has one NCA (<a href="https://www.fca.org.uk/">Financial Conduct Authority</a>) and berlin has one etc. When it comes to the Open banking concepts, the EU wanted to streamline all NCA’s because there were independent rules and regulations according to the NCA’s and it was difficult to establish open banking concept with independent NCA bodies.</p><p>However, the EU comes up with another main body called <a href="https://eba.europa.eu/">EBA</a> (Europian banking Authority) to streamline all EU NCA’s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vjn_qsT33s1dlMTRtFYjjA.png" /></figure><p>EBA published one centralized regulation set and those given to each NCA’s which is pushing their banks in respective regions. This low regulation set we call as PSD (Payment Services Directive)and now it evolved to the 2nd version and we called as PSD2.</p><p>PSD2 is a set of regulations and it is not having any technical information which can be used to implement open banking solutions. Therefore several entities started making technical guidelines which achieve the PSD. This technical guidance we are known as open banking specifications. Especially, In the UK region setup the entity called “Open Banking Implementation Entity” known as <a href="https://www.openbanking.org.uk/about-us/">OBIE</a>. OBIE produced multiple specifications which are focused on functional, security, monitoring and usability aspects. Please refer [specification] section for lean more about OB UK specifications. Same as that there is another specification written by “<a href="https://docs.wixstatic.com/ugd/c2914b_4a9b0db8c35841adb91531ef0faba4c2.pdf">Berlin Group</a>”. It is mandated as a “Berlin Specification”.</p><p>I hope this article gives you basic information about open banking landscape. Future articles will focus on Open Banking specifications and implementations of OB solutions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b5b04f295bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customer Support via LAST]]></title>
            <link>https://medium.com/@chamarasilva/customer-support-via-last-c37eaacdbb42?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c37eaacdbb42</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[support]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Wed, 10 Oct 2018 07:32:53 GMT</pubDate>
            <atom:updated>2018-10-10T07:39:56.391Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TAFwoF1g_Wn-26_ANXKijQ.jpeg" /></figure><p>The customer support is an art. As a customer support engineer or the representative, we keep on learning how to work with customers effectively to solve their matters. End of the day, we always need to be customer happy.</p><p>I have read many articles and books about this subject and found the good model to follow when working with customers.</p><p><strong>The LAST model </strong>is the practical working model. I always follow and it gives me 100% successful results.</p><h3>L — Listen</h3><p>In the practical world most of the time customer support engineer, engaging with customers when customer getting into any problem or critical situation. There, As the support engineer, it is vital to understand the customer’s problem 100% correctly in order to provide the accurate solution.</p><p>There, <strong>Listen </strong>is the important factor. listing to the customers always helps you to understand the actual situation and impact which had to the customer. When you listing to the customer find the problem and understand the depth of the problem. Same as that, show customer to you are listing to him. It always helps you to handle the customer and it will build a good first impression of you.</p><p>If you are dealing with the frustrated or angry customer, Don&#39;t be overreacting. be calm down and sign them you are helping them to solve their problem. “I understand the inconvenience and I am trying to help you to solve the issue”these kinds of words will help you to calm down the customer.</p><h3>A-Apologize</h3><p>Mainly don&#39;t mention it is your fault. It is impacting to build up the negotiation power. The best approach is to say apologize for the situation which customer has faced. There are some edge cases situation the actual problem is on our side. In such situation, you should handle it tactically.</p><h3>S- Solve</h3><p>Solving customer issue is the important part. your solution should be more accurate. Otherwise, the customer will come back again with followup questions. As a rule of thumb, let the customer know what you are going to do to solve the problem and how it solved. It will be you and customer on the same page and cut down counter questions in future. If you are not sure about the solution, don&#39;t give any guessing solutions. There, do not hesitate to tell the customer to you are not sure about the solution and come back again after discussing with your manager or expert.</p><h3>T- Thank</h3><p>Thanking is the most important thing to continue the good relationship with the customer. It will show your kindness and politeness while handling such situations. “Thank you for letting us know the problem” kind words will help you to keep the customer connected and make the customer happy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c37eaacdbb42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Common mistakes are doing in customer support]]></title>
            <link>https://medium.com/@chamarasilva/4-common-mistakes-are-doing-in-customer-support-1b8d766c2ef6?source=rss-674b922c3f7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b8d766c2ef6</guid>
            <category><![CDATA[support]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[customer-service]]></category>
            <dc:creator><![CDATA[Chamara Silva]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 12:09:59 GMT</pubDate>
            <atom:updated>2018-10-03T12:13:03.770Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ak7T_6KLGN_IL9D6bNniQ.png" /></figure><p>In day to day customer support operations we win the customers and sometimes we lose them due to the various reasons. According to my experience, I would like to note, what are the common mistakes we do for lost the customers.</p><p><strong>“Not a listener”</strong></p><p>Listing is a major fact when it comes to the effective customer support. The human brain can listen 500–550 words per minute. But can talk only 200–250 words. That mean brain always set to listen more than the talking. But most of the customer support engineers tend to talk to the customer what they know rather than listening to the customer. Sometimes they talk much to defend the problems rather than solving it.</p><p><strong>“Not understanding customer”</strong></p><p>Did you understand your customer always before solving their problems? Most of the time answer is “No”. When you talk or solving customer problems, It is vital to understand the real situation of the customer, need to feel the pain of the customer. This we call as “Empathy”. It always easy for you to drive you to the perfect solution.</p><p><strong>“Stupid customer mindset”</strong></p><p>Some customer support engineers think like”this customer doesn’t know anything !!”, “customer always wrong !!”. This is a dangerous attitude for support engineer as well as the organization. Because Customer always tried something and come up with some experience. They get into the problem after doing something with your product or the service. because of that, If you think like above your customer, It always drives you into the wrong answer or the incorrect solution. The bad impact is, It may end up with frustrating your customer.</p><p><strong>“Thinking customers are depending on you”</strong></p><p>This attitude always presents you as an impolite person in front of the customer. If you are working with traditional customer service and if customer frustrates because of above reason, they will tell their 500 friends about you. It will lose only 500 potential customers. But if you working with internet world they will tell you 5 million people. It can be effective to completely close your business. Customers always have many alternatives. Because they do not always depend on you. You depend on them.</p><p><em>Originally published at </em><a href="http://chamaras.blogspot.com/2017/08/4-common-mistakes-are-doing-in-customer.html"><em>chamaras.blogspot.com</em></a><em> on October 3, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b8d766c2ef6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>