<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:yandex="http://news.yandex.ru" xmlns:turbo="http://turbo.yandex.ru" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Blog</title>
    <link>https://gorgona.uz</link>
    <description/>
    <language>ru</language>
    <lastBuildDate>Mon, 04 May 2026 18:02:18 +0300</lastBuildDate>
    <item turbo="true">
      <title>How We Tamed AI for HR and Started Generating Individual Development Plans in Minutes</title>
      <link>https://gorgona.uz/en/blog/ai-performance-review</link>
      <amplink>https://gorgona.uz/en/blog/ai-performance-review?amp=true</amplink>
      <pubDate>Mon, 04 May 2026 17:48:00 +0300</pubDate>
      <category>Case studies</category>
      <enclosure url="https://static.tildacdn.com/tild3439-6336-4138-b561-636361313564/ChatGPT_Image_23__20.png" type="image/png"/>
      <description>Learn how AI automates Individual Development Plans (IDPs), reducing time, improving personalization, and boosting employee retention.</description>
      <turbo:content><![CDATA[<header><h1>How We Tamed AI for HR and Started Generating Individual Development Plans in Minutes</h1></header><figure><img alt="" src="https://static.tildacdn.com/tild3439-6336-4138-b561-636361313564/ChatGPT_Image_23__20.png"/></figure><div class="t-redactor__text">In IT teams, Individual Development Plans (IDPs) often look like a formality - until you actually have to create them. On paper, the process seems straightforward: collect feedback, assess skills, define goals. In reality, it turns into a time-consuming task of consolidating fragmented inputs into a coherent, non-generic development plan.</div><div class="t-redactor__text">In this case study, we explain how we automated IDP creation and trained a system to generate personalized development plans in minutes based on HR data and performance evaluation results.</div><h2  class="t-redactor__h2">The Previous State</h2><div class="t-redactor__text">The HR department regularly conducts performance reviews - a comprehensive employee assessment process that includes feedback collection, skill evaluation, and tracking development over time.</div><div class="t-redactor__text">This process gathers input from peers, clients, and team leads, while evaluating both hard and soft skills. Based on this data, an IDP - an Individual Development Plan - is created to outline growth areas and improvement priorities.</div><div class="t-redactor__text">The main bottleneck appeared at the IDP creation stage.</div><div class="t-redactor__text">Previously, team leads compiled these plans manually. Each IDP took 30-40 minutes, and even longer with extensive feedback. Every time, they had to restructure scattered notes into a coherent plan, often facing the “blank page” problem - when everything is clear conceptually, but difficult to articulate quickly into a structured document.</div><h2  class="t-redactor__h2">How AI Changed the Process</h2><div class="t-redactor__text">The turning point came when we seriously explored generative AI. We avoided simplistic approaches like “generate a development plan for a mid-level developer.” It became clear that generic prompts wouldn’t deliver meaningful results.</div><div class="t-redactor__text">Instead, we leveraged the company’s internal data assets: feedback, performance reviews, and employee development history. This became the foundation of the solution and its key competitive advantage.</div><h2  class="t-redactor__h2">Inside the System: How IDPs Are Generated</h2><div class="t-redactor__text">We built an AI-powered tool that automatically generates Individual Development Plans based on hard and soft skill assessments from performance reviews. Each plan is tailored to the employee and focuses on specific growth areas rather than generic templates.</div><h3  class="t-redactor__h3">How it works</h3><div class="t-redactor__text">Each employee accumulates a structured history over time: evaluation results, peer feedback, leadership notes, and previous development plans. This data is consolidated into a unified context, which the system transforms into a master prompt - a comprehensive input hidden from the end user.</div><img src="https://static.tildacdn.com/tild3335-3130-4364-b739-613766363566/IPR_1.png"><div class="t-redactor__text">The user flow is intentionally simple: select an employee and click “Generate IDP.”</div><h3  class="t-redactor__h3">Behind the scenes, the system:</h3><div class="t-redactor__text"><ul><li data-list="bullet">Retrieves employee data, including hard and soft skill assessments</li><li data-list="bullet">Aggregates it into a structured context</li><li data-list="bullet">Builds a master prompt focused on strengths, growth areas, and team context</li><li data-list="bullet">Sends it to the model for generation</li><li data-list="bullet">Produces multiple IDP variations</li><li data-list="bullet">Saves the result in an editable format for further refinement by the team lead</li></ul></div><img src="https://static.tildacdn.com/tild3434-6664-4330-a662-356361333039/IPR_2.png"><div class="t-redactor__text">In essence, the system handles data aggregation, structuring, and the initial draft. At the same time, the output remains fully controllable: managers can refine wording, add comments, and finalize the plan before sharing it with the employee.</div><h2  class="t-redactor__h2">Business Impact</h2><div class="t-redactor__text">The implementation of the IDP generator significantly improved how development plans are created - making the process faster, more consistent, and more personalized without sacrificing expert control.</div><h3  class="t-redactor__h3">Results:</h3><div class="t-redactor__text"><ul><li data-list="bullet">Time spent on IDP creation reduced from 4-6 hours to 15 minutes</li><li data-list="bullet">IDP completion rate increased from 65% to 90%</li><li data-list="bullet">Employee turnover decreased by 15%</li><li data-list="bullet">The “blank page” problem was eliminated</li><li data-list="bullet">Plans became more personalized благодаря учету полной истории развития сотрудника</li><li data-list="bullet">Flexibility was preserved - IDPs can be edited and adapted to real-world needs</li></ul></div><div class="t-redactor__text">Overall, the process shifted from manual document creation to a model where AI handles data processing and initial structuring, while humans focus on content quality and final decision-making.</div>]]></turbo:content>
    </item>
    <item turbo="true">
      <title>Unified AI Platform for Citizen Requests: From Fragmented Tickets to a Single Workflow</title>
      <link>https://gorgona.uz/en/blog/omnichannel-ai-support</link>
      <amplink>https://gorgona.uz/en/blog/omnichannel-ai-support?amp=true</amplink>
      <pubDate>Mon, 04 May 2026 17:53:00 +0300</pubDate>
      <category>Case studies</category>
      <enclosure url="https://static.tildacdn.com/tild6332-3561-4663-a362-623262303038/ChatGPT_Image_22__20.png" type="image/png"/>
      <description>AI platform centralizes citizen requests, reduces processing time, and automates responses with RAG and sentiment analysis.</description>
      <turbo:content><![CDATA[<header><h1>Unified AI Platform for Citizen Requests: From Fragmented Tickets to a Single Workflow</h1></header><figure><img alt="" src="https://static.tildacdn.com/tild6332-3561-4663-a362-623262303038/ChatGPT_Image_22__20.png"/></figure><div class="t-redactor__text">City services process a continuous stream of citizen requests every day, coming from dozens of channels - public portals, chatbots, social media, and written submissions. A significant portion of these requests are repetitive or require standard responses, yet they are still handled manually.</div><div class="t-redactor__text">We developed an AI-powered platform for a large metropolitan municipality that consolidates all incoming requests into a single system and accelerates processing through a knowledge base and sentiment analysis.</div><h3  class="t-redactor__h3">The Challenge</h3><div class="t-redactor__text">During request processing, recurring patterns consistently exposed weaknesses in the system.</div><div class="t-redactor__text">For example, the same incident - such as a fallen tree in a courtyard or uncleared snow - could be reported simultaneously via the city portal, chatbot, and social media. As a result, it would be registered multiple times and routed to different departments, where it would be processed in parallel.</div><div class="t-redactor__text">Another common scenario: a user submits a request through an “official” channel and then duplicates it via another service, unaware that it is already being handled. The system could not correlate these cases, so they continued to exist as separate tickets.</div><div class="t-redactor__text">There was also the opposite issue: operators often received requests without full context. To understand the situation, they had to manually check multiple systems and coordinate with other departments.</div><div class="t-redactor__text">Additionally, the system was overloaded with standard inquiries such as:</div><div class="t-redactor__text"><ul><li data-list="bullet">where to report housing and utilities issues</li><li data-list="bullet">how to submit a request</li><li data-list="bullet">expected processing timelines</li></ul></div><div class="t-redactor__text">These consumed operator time despite being easily resolved with predefined responses.</div><div class="t-redactor__text">Ultimately, the problem was not the volume of requests itself, but the system’s inability to consolidate, classify, and respond efficiently where answers were already known.</div><h3  class="t-redactor__h3">From Fragmented Requests to a Unified Flow</h3><div class="t-redactor__text">We designed a system that aggregates and standardizes request processing across all channels into a single operational framework.</div><div class="t-redactor__text">The core idea is that requests no longer exist in isolated tools or departmental systems. Instead, all incoming data is centralized in one platform, regardless of its source - city portal, chatbot, social media, or internal services.</div><div class="t-redactor__text">The platform acts as a unified processing hub: it ingests requests, normalizes them, and distributes them based on predefined responsibility logic.</div><h3  class="t-redactor__h3">How the System Works</h3><div class="t-redactor__text">A user submits a request through any available channel - portal, chatbot, social media, or internal system. The platform then converts it into a structured request within a unified data model.</div><img src="https://static.tildacdn.com/tild6465-3265-4133-b731-393833366566/HD_1.png"><div class="t-redactor__text">All incoming requests pass through a single entry point, where they undergo initial processing and classification. At this stage, the system determines the topic and automatically routes the request to the appropriate domain:</div><div class="t-redactor__text"><ul><li data-list="bullet">urban infrastructure (roads, maintenance)</li><li data-list="bullet">housing and коммунальные services (housing &amp; utilities)</li><li data-list="bullet">emergency incidents</li><li data-list="bullet">other categories</li></ul></div><div class="t-redactor__text">Once routed, the request is assigned to the responsible department and processed through an end-to-end workflow: intake → assignment → resolution → response.</div><img src="https://static.tildacdn.com/tild6631-3465-4630-b639-313461653033/HekpDesk_2.png"><div class="t-redactor__text">A transparent status model is maintained at every stage, showing exactly where the request stands and what actions are being taken. This eliminates lost tickets and reduces uncertainty for all stakeholders.</div><h3  class="t-redactor__h3">Where AI Adds Value</h3><h4  class="t-redactor__h4">Sentiment Analysis for Request Understanding</h4><div class="t-redactor__text">The first layer is sentiment analysis.</div><div class="t-redactor__text">Each incoming message is automatically analyzed to determine both emotional and operational context:</div><div class="t-redactor__text"><ul><li data-list="bullet">neutral request</li><li data-list="bullet">negative or conflict-driven message</li><li data-list="bullet">potentially urgent situation</li></ul></div><div class="t-redactor__text">This allows operators to instantly assess the nature of the request, while enabling the system to prioritize processing accordingly. In practice, it serves as an early signal of urgency and required response mode.</div><h4  class="t-redactor__h4">RAG-Based Knowledge Layer for Fast Responses</h4><div class="t-redactor__text">The second layer is an intelligent knowledge base built on a <strong>Retrieval-Augmented Generation (RAG)</strong> approach.</div><img src="https://static.tildacdn.com/tild6466-6164-4665-b432-333435666565/HekpDesk_1_3.png"><div class="t-redactor__text">When the system or an operator encounters a standard query, the platform retrieves relevant articles, instructions, or policy-based responses.</div><div class="t-redactor__text">This is applied in scenarios where:</div><div class="t-redactor__text"><ul><li data-list="bullet">a standardized answer already exists</li><li data-list="bullet">no involvement from a specialized department is required</li><li data-list="bullet">the request can be resolved quickly without additional routing</li></ul></div><div class="t-redactor__text">In essence, RAG reduces manual information lookup and significantly speeds up handling of repetitive requests.</div><h3  class="t-redactor__h3">Outcomes</h3><div class="t-redactor__text">The platform significantly transformed request processing - from a manual, fragmented workflow to a centralized and predictable system.</div><div class="t-redactor__text">Key results:</div><div class="t-redactor__text"><ul><li data-list="bullet"><strong>23% of requests</strong> are now resolved automatically using standard responses powered by the RAG knowledge base</li><li data-list="bullet"><strong>Average processing time</strong> reduced from <strong>4 hours to 25 minutes</strong> due to automated routing and fewer manual operations</li><li data-list="bullet"><strong>15% of requests</strong> identified as duplicates, enabling automatic merging and reducing workload</li></ul></div><div class="t-redactor__text">Overall, the system not only accelerated request handling but also reduced operational redundancy by eliminating duplicate work and balancing load between automation and human operators.</div>]]></turbo:content>
    </item>
    <item turbo="true">
      <title>From Interview to Report in Minutes: AI for Candidate Assessment</title>
      <link>https://gorgona.uz/en/blog/automate-hr-reports</link>
      <amplink>https://gorgona.uz/en/blog/automate-hr-reports?amp=true</amplink>
      <pubDate>Mon, 04 May 2026 17:57:00 +0300</pubDate>
      <category>Case studies</category>
      <enclosure url="https://static.tildacdn.com/tild6266-3534-4335-a330-623337313437/ChatGPT_Image_23__20.png" type="image/png"/>
      <description>AI automates interview analysis and report creation, helping HR teams generate structured competency-based assessments faster and more accurately.
</description>
      <turbo:content><![CDATA[<header><h1>From Interview to Report in Minutes: AI for Candidate Assessment</h1></header><figure><img alt="" src="https://static.tildacdn.com/tild6266-3534-4335-a330-623337313437/ChatGPT_Image_23__20.png"/></figure><div class="t-redactor__text">An hour-long interview - followed by several more hours to prepare a report. Traditionally, this meant extensive manual work: refining wording, aligning expert opinions, and consolidating final conclusions.</div><div class="t-redactor__text">Today, AI handles the initial processing and structuring, allowing experts to focus on analysis and decision-making.</div><div class="t-redactor__text">In this case study, we explain how we built a service in just three weeks that automatically processes interviews, maps responses to competencies, and accelerates the creation of expert reports.</div><h2  class="t-redactor__h2">Why This Solution Was Needed</h2><div class="t-redactor__text">In talent assessment workflows, interviews are only the starting point. The real workload begins afterward: experts analyze candidate responses, map them to competencies, and produce final reports to support hiring decisions.</div><div class="t-redactor__text">For the client, this process was heavily manual. Each report took an average of 2–3 days and involved expert discussions, documenting observations, filling templates, and multiple approval cycles. Even with a standardized structure, every report had to be built from scratch for each candidate.</div><div class="t-redactor__text">Over time, it became clear that most effort was spent not on analysis itself, but on formatting and repetitive tasks. This is where the core objective emerged - accelerate report preparation without compromising the quality of expert evaluation.</div><h2  class="t-redactor__h2">Key Requirements</h2><div class="t-redactor__text">Through discussions with the client, it became clear that the goal was not just speed. Experts rely on their judgment and experience, so the system had to augment - not replace - human expertise.</div><div class="t-redactor__text"><ul><li data-list="bullet">Automate routine report preparation tasks so experts can focus on analysis</li><li data-list="bullet">Structure interviews and analyze responses without losing important details</li><li data-list="bullet">Highlight overlooked insights and identify strengths and weaknesses across competencies</li><li data-list="bullet">Provide recommendations and supporting arguments to inform expert decisions</li></ul></div><h2  class="t-redactor__h2">Augmenting, Not Replacing Experts</h2><div class="t-redactor__text">The core principle behind the solution was simple: speed up report creation while preserving analytical quality. The goal was not to offload the entire process to AI, but to eliminate routine tasks and provide experts with a structured foundation for analysis.</div><div class="t-redactor__text">In this workflow, AI acts as an assistant. It handles data processing, structuring, and initial interpretation, while the expert reviews, refines, and makes final decisions.</div><div class="t-redactor__text">The result is a service built on our platform that transforms interview recordings into structured competency-based assessments.</div><h2  class="t-redactor__h2">How the Process Works</h2><div class="t-redactor__text"><ol><li data-list="ordered">The expert uploads the interview audio and selects competencies for analysis</li><li data-list="ordered">The system transcribes the recording and segments it into meaningful parts</li><li data-list="ordered">AI maps responses to competencies and generates an initial assessment</li><li data-list="ordered">The output is a structured report with arguments and identified strengths and weaknesses</li></ol></div><div class="t-redactor__text">The entire workflow is handled within a single interface. Users can review transcripts, run analysis, switch between competencies, and edit the final report. Competency models are fully configurable and can be adapted to different assessment methodologies without changing system logic.</div><img src="https://static.tildacdn.com/tild3066-3863-4137-b933-343763643630/HTLAB_1.png"><div class="t-redactor__text">An AI-powered chat is also integrated as a refinement tool. Experts can clarify interview segments, rephrase conclusions, and explore alternative interpretations.</div><img src="https://static.tildacdn.com/tild3161-3663-4931-a635-653965313235/HTLAB_2.png"><div class="t-redactor__text">Data processing is implemented with security in mind: interviews are anonymized before analysis and are not transmitted to external services.</div><img src="https://static.tildacdn.com/tild3535-6536-4964-b162-366336333630/HTLAB_3.png"><div class="t-redactor__text">As a result, experts receive not raw data or empty templates, but a structured draft report that can quickly be finalized.</div><h2  class="t-redactor__h2">Results</h2><div class="t-redactor__text">The system delivered two key outcomes: faster report generation and an additional analytical layer that improves both speed and accuracy.</div><div class="t-redactor__text"><ul><li data-list="bullet"><strong>“Second opinion” in minutes</strong> - experts receive a structured AI-generated assessment within 5–7 minutes and use it as a foundation instead of building reports from scratch</li><li data-list="bullet"><strong>Reduced routine workload</strong> - a significant portion of time previously spent on formatting and wording is now automated</li><li data-list="bullet"><strong>Flexible configuration</strong> - competencies can be added and customized for different methodologies without changing system logic</li><li data-list="bullet"><strong>AI chat as a working tool</strong> - used to refine conclusions, improve wording, and generate development recommendations that are directly included in the final report</li></ul></div><div class="t-redactor__text">As a result, experts can focus on the substance of evaluation, while reporting becomes a natural extension of the analysis process rather than a separate, time-consuming task.</div>]]></turbo:content>
    </item>
    <item turbo="true">
      <title>When GenAI Steps In: Generating Test Cases and Automated Tests</title>
      <link>https://gorgona.uz/en/blog/aqa-ai-service</link>
      <amplink>https://gorgona.uz/en/blog/aqa-ai-service?amp=true</amplink>
      <pubDate>Mon, 04 May 2026 18:00:00 +0300</pubDate>
      <category>Case studies</category>
      <enclosure url="https://static.tildacdn.com/tild3039-3261-4763-b430-613061326132/ChatGPT_Image_23__20.png" type="image/png"/>
      <description>Discover how generative AI automates test case and autotest creation, reduces QA workload, and accelerates release cycles with high-quality outputs.
</description>
      <turbo:content><![CDATA[<header><h1>When GenAI Steps In: Generating Test Cases and Automated Tests</h1></header><figure><img alt="" src="https://static.tildacdn.com/tild3039-3261-4763-b430-613061326132/ChatGPT_Image_23__20.png"/></figure><div class="t-redactor__text">Previously: every release meant dozens of tasks, hundreds of scenarios, and a large volume of test documentation that the team had to manually create, review, and keep up to date.</div><div class="t-redactor__text">Now: you upload requirements and UI designs, and AI generates test cases, suggests automated tests, and captures interface details with high accuracy.</div><h3  class="t-redactor__h3">Context</h3><div class="t-redactor__text">As the product evolved and release frequency increased, the team faced a common scalability challenge in QA: the volume of tasks, scenarios, and test documentation was growing faster than the team’s capacity.</div><div class="t-redactor__text">Each release included dozens of tasks, requirements, mockups, comments, and corresponding test cases and automated tests - all of which required manual coordination and maintenance. This significantly extended release preparation time and slowed down the team’s ability to respond to changes.</div><div class="t-redactor__text">Routine work became the primary bottleneck: preparing test documentation and continuously synchronizing scenarios. At the same time, regression testing expanded, and validating both new and existing scenarios required increasing effort.</div><div class="t-redactor__text">Eventually, it became clear that scaling this process manually was no longer viable. The choice was either to expand the team or to optimize the process itself. This led to a focus on automating test case and test automation generation while reducing manual effort.</div><h3  class="t-redactor__h3">Objectives</h3><div class="t-redactor__text">At the start of the project, we aligned with the client on the desired outcomes:</div><div class="t-redactor__text"><ul><li data-list="bullet">Automate routine tasks so that test cases could be generated from requirements and documentation almost instantly, with minimal manual input</li><li data-list="bullet">Make automated testing more accessible, ensuring tests are generated alongside test cases rather than weeks later, and can be quickly integrated into workflows</li><li data-list="bullet">Achieve “expert-level” quality, ensuring that generated test cases match the quality of manual work, with a target of at least 80% alignment with outputs from experienced QA engineers</li><li data-list="bullet">Ensure transparency, allowing any team member to understand how a test case was generated and easily trace all related artifacts</li></ul></div><h3  class="t-redactor__h3">Solution</h3><div class="t-redactor__text">We developed a service that automatically generates test cases and automated tests based on requirements and project documentation. At its core is a generative AI model that analyzes input materials, identifies user scenarios, and structures them into test cases.</div><img src="https://static.tildacdn.com/tild6332-6530-4365-b366-616538316565/XT_1.png"><div class="t-redactor__text">The system processes not only textual data but also visual inputs. UI mockups and screenshots are analyzed via a Vision API, enabling more accurate representation of real user behavior and interface interactions.</div><div class="t-redactor__text">The entire architecture is centered around scenarios as the primary entity. Each scenario stores its full context: requirements, test cases, automated tests, and change history. PostgreSQL is used for storage, ensuring data integrity and scalability across large volumes of scenarios.</div><img src="https://static.tildacdn.com/tild3765-6266-4533-b138-633231646363/XT_2.png"><div class="t-redactor__text">The output is a standardized set of test cases in AAA format (Arrange–Act–Assert), including steps, preconditions, and expected results. The system also supports prioritization and traceability to source artifacts, making the results production-ready and easy to maintain as the product evolves.</div><div class="t-redactor__text">On top of this, automated test generation is implemented based on the test cases. The system converts scenarios into executable code, taking into account the programming languages and frameworks used by the team, allowing immediate integration into existing QA pipelines.</div><img src="https://static.tildacdn.com/tild6565-3665-4930-b662-306234326231/XT_3.png"><div class="t-redactor__text">The result is a unified tool that connects requirements, test cases, and automated tests into a single workflow - reducing manual effort, accelerating release cycles, and making the QA process more structured and transparent.</div><h3  class="t-redactor__h3">Results</h3><div class="t-redactor__text">Initially, the goal was to validate a simple hypothesis: can AI generate test cases of sufficient quality to be used with minimal adjustments?</div><div class="t-redactor__text">To test this, real project documentation and requirements were fed into the system, and the output was compared against test cases previously created by experienced QA engineers.</div><div class="t-redactor__text">Key outcomes:</div><div class="t-redactor__text"><ul><li data-list="bullet">Most generated test cases were used without modification, significantly reducing the time required to prepare test documentation</li><li data-list="bullet">Automated tests were generated alongside test cases, accelerating the transition from requirements to test execution</li><li data-list="bullet">Manual effort in the QA process decreased substantially, making testing faster and more predictable</li><li data-list="bullet">The system consistently handled diverse input formats and large volumes of documentation, maintaining stable generation quality and adapting well to feedback-driven improvements</li></ul></div><div class="t-redactor__text">Continuous collaboration with the team enabled rapid iteration: duplicate scenarios were eliminated, test case structuring logic was refined, and readability of outputs improved.</div><div class="t-redactor__text">As a result, the solution evolved from an experimental tool into a production-ready workflow. Test cases are now generated automatically, automated tests appear almost instantly, and the team can focus more on product development rather than routine QA documentation.</div>]]></turbo:content>
    </item>
  </channel>
</rss>
