<?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 Line Karkov on Medium]]></title>
        <description><![CDATA[Stories by Line Karkov on Medium]]></description>
        <link>https://medium.com/@LineKarkov?source=rss-ac34961b5b9f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YuSSY7twx1Hd_cr11P803g@2x.jpeg</url>
            <title>Stories by Line Karkov on Medium</title>
            <link>https://medium.com/@LineKarkov?source=rss-ac34961b5b9f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:31:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@LineKarkov/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[Ohno and Ehn: Constraints for innovation, and quality as a virtue]]></title>
            <link>https://medium.com/analysts-corner/ohno-and-ehn-constraints-for-innovation-and-quality-as-a-virtue-883cf2f485ee?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/883cf2f485ee</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[participatory-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Sun, 01 Nov 2026 23:30:10 GMT</pubDate>
            <atom:updated>2026-11-01T23:30:10.899Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ohno and Ehn: Constraints for innovation, and quality as a virtue, in the age of accelerated digitalisation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_WiB5T_htrZEPuE3UoR72A.jpeg" /><figcaption>Illustration by author</figcaption></figure><p>At school, when I was 18, I wrote an analysis of one of Bertolt Brecht’s plays, and in working on it I made the acquaintance of his use of <em>Verfremdung</em> — making the familiar strange — and of dialectics. Both are techniques for getting an audience to relate critically to the action on stage and to believe that the world can be changed. The point of <em>Verfremdung</em> is to render the familiar strange by means of unconventional effects; dialectics is a method in which contradictions are laid bare, so that we can explore what happens in the field of tension between them. At the time, I hadn’t the faintest idea that these two notions would come to matter to me many years later, in my day-to-day work with digital transformation as a business analyst and product owner.</p><p>In the spring I was in Japan with my family, and we had booked a full-day excursion by bus, guide included. The group had settled into their seats, departure was two minutes away, and two passengers were missing. “We don’t wait for people who arrive late,” the guide announced in a tone that brooked no discussion. Fortunately, they made it. The guide looked after his group well — as long as they stayed within the constraints he had set: constraints not in the sense of limits, but in the sense of what allows a group of strangers spend a good day together. He made sure everyone sat with their own family at lunch, checked that everyone knew when the bus was leaving and was aboard before it did, saw to it that we knew where to find him while we wandered around the museum, and kept the group from spilling too generously across the pavement and becoming a nuisance to others. And even as all this was managed with a firm hand, I also noticed that if you were part of the group, you were seen and you were heard. I had heard about Japanese collectivism and wondered whether that was what I was experiencing. In my corner of the world, collectivism is often taken to be a limit on free will, but that wasn’t quite how it felt to me.</p><p>Back at the office in Copenhagen, our union representative had called the staff in my department to a meeting about the forthcoming negotiations to renew our collective agreement. A little while earlier she had sent round a questionnaire to map out what mattered to people, so it could be carried into the negotiations; and on this late afternoon, in the meeting room on the fourth floor, she wanted to hear our department’s view of the questionnaire results. That would serve as input to a consolidated negotiating position. I knew the routine, having been through it before. The negotiations with management would get under way, and would most likely drag on a bit, but they would arrive at a result that the union representative would recommend we vote yes to. We would hold a general meeting, where she would highlight what we had won, and add that it wasn’t perfect, but that it could have been considerably worse. Some would think it a terrible deal; most would think it perfectly fine. When it went out to a vote with five working days to respond, the majority would end up voting for it, and it would be adopted. As for me, I would follow the union representative’s recommendation, trusting that she had done her best under the circumstances. Just as on our day trip in Japan, everyone in the group was seen and heard — as long as they stayed within the constraints.</p><h3>So I followed the trail</h3><p>There was something fundamental I recognised across the two experiences. But I was also aware that a random day’s excursion is a very different thing from situations where something is actually at stake. The visit to Japan was fleeting, and I knew the culture only superficially. And yet: might there be a clue here to a more considered, more collaborative way of approaching digitalisation? In any case, I needed a counterweight to all the breathless headlines I kept seeing — not only on LinkedIn, but also in my old-fashioned paper newspaper — about the revolutionised world of work, the jobs that would disappear, and the demented gains in efficiency. I needed thoughts on how we might digitalise in a way we can ourselves live with over the long run. I knew that agile (via Lean) shares intellectual ancestry with ideas that emerged at Toyota in Japan, and that Design Thinking, which is kin to Participatory Design, grew out of a collaboration with Scandinavian trade unions. So I followed the trail from my two experiences and went back in time to understand the origins of the Toyota Production System and of Participatory Design more deeply. Could these two traditions — born in wildly different environments on opposite sides of the earth — have something in common that might tell us how to get past the cliché and actually digitalise with people as the starting point? I watched Pelle Ehn’s lectures from 2018 on the history of Participatory Design: <a href="https://youtube.com/playlist?list=PLjF3DI5gKgutm9hZpZoWvOXxgr-tvrzSQ&amp;si=SnGijZdQenA2wRiu"><em>Design, Democracy and Participation: Exploring the Scandinavian Participatory Design Tradition</em></a>. And I read the first two chapters of <a href="https://www.lean.org/store/book/the-birth-of-lean-conversations-with-the-founders-of-tps-2/"><em>The Birth of Lean</em></a>, where Taiichi Ohno and Michikazu Tanaka recount the development of the Toyota Production System. What follows is based on those two sources.</p><h3>The Toyota Production System: kaizen as an answer to post-war scarcity</h3><p>At Toyota’s factories after the Second World War, a new way of organising work emerged. Toyota had no choice but to fundamentally change how work was organised in order to produce more cars without expanding the production apparatus or hiring more people. Taiichi Ohno (who worked his way up from engineer to top management) was responsible for what became the Toyota Production System. He implemented kaizen and developed kanban, both of which have been carried forward in, for example, Lean. Kaizen is about small, continuous improvements. And to identify possible improvements, you have to observe how the work is actually done and talk with the people who do it. They are the ones who can put their finger on the heart of a problem, and who therefore have the insight needed to propose solutions. Alongside the reduction of waste, quality is utterly central to Ohno’s approach to production. It is quality in each sub-process that allows the next sub-process to run efficiently too, and that prevents work flowing backwards. It makes for a quality product, and in the long run that is what leads to improvements in productivity. The foundation for improvement is transparency about how the work is carried out, and standardisation of it. That is how problems become visible.</p><h3>Participatory Design: when the workers shape the technology</h3><p>Pelle Ehn researches Participatory Design and is among other things known for his contribution to the UTOPIA project in the 1980s, which developed a computer program for graphic designers. Participatory Design is rooted in Scandinavia and in the 1970s ideas about workplace democracy — the notion that workers should contribute to the decision-making process at their workplace, which would thereby be democratised. The trade unions realised that they had to involve themselves in how new technology was designed, in order to ensure that it led not only to greater efficiency but also to benefit for the people working with it. They entered into this work actively, because they wanted technology to be used in a way that amplified the workers’ skills rather than stripping them away. This democratisation, the designers wanted to build into the design process itself, as the processes of the workplace were being automated and digitalised.</p><p>he practitioners of Participatory Design worked from the principle that the design should take as its starting point the the existing professional tradition. That could only be done by observing the work and involving the workers. They focused on designing IT systems that supported products of high quality, because quality in the product and quality in working life are bound together.</p><p>You may object that the changes we face today are completely different and cut far deeper into the way we organise work than ever before. To that I would draw your attention to the fact that the pioneers of Participatory Design designed together with people who had never used a computer. They didn’t know what a mouse was. Close your eyes for a moment and imagine what a radical change that must have been.</p><h3>If Ohno and Ehn had met…</h3><p>Suppose we imagine that Ohno and Ehn had actually met — how might it have gone? What if one could invite them to Västra Hamnen in Malmö, Sweden on a long, light midsummer evening, with nobody in a hurry? On their little stroll around the district, they would have passed the small boats in the packed marina. Ohno would have remarked how a crew in many ways practises kaizen on its journey. And Ehn would have followed up with the observation that a journey by boat is in many ways like a design process that can never quite be predicted, where you have to adapt as you go. They would have found somewhere to eat where they could get matjes with new potatoes, dill and crème fraîche. Over the meal, they would have had plenty of time to tell each other about their experiences and the thinking behind them. Sadly, it would not have been possible to invite either a worker from Toyota or a member of the graphic designers’ union, since my sources contain no first-hand accounts. But Ohno and Ehn would have talked their way to agreement on the importance of firm constraints for innovation, transparency about the work, observation of the work, and participation from the workers. They would also have agreed on quality as a virtue. That despite the fact that Ohno’s work sprang from the post-war scarcity of the factory floor, while Ehn’s sprang from the welfare state’s growing prosperity among educated specialists. But the differences would also have stood out plainly. Ohno’s starting point was efficiency to secure the company’s survival, even if a good working environment is a precondition for employees being able to contribute to kaizen. Ehn’s starting point, by contrast, was a meaningful and sustainable working life, even if efficiency gains would have been a welcome side effect. I don’t imagine this meeting would end in any new, shared insight; rather, they would have appreciated getting to know each other’s perspectives better, and their own work would have stood out more sharply for them through this new prism. In my optimistic fantasy, they would agree that quality was the place where their starting points met.</p><h3>What if the conversation began with quality?</h3><p>There is, precisely, a dialectical relationship between efficiency gains and meaningful work. I see it often in my work with digital transformation. And like Brecht, I wish we dared to put that relationship into words and see what turns up in the field of tension between them. Perhaps that is exactly what is needed for us actually to begin talking about which qualities the digitalisation initiatives we set in motion are meant to bring forth — instead of starting with minutes saved, full-time equivalents, or job titles. That is what is needed for the conversation to become about what we would like to create, rather than what we don’t want. For that is precisely where the users’ professional expertise becomes indispensable, and there is no alternative but to involve their professional capacities from the moment the initiative’s first headline is written.</p><p>To think that a trip to the other side of the earth had the <em>Verfremdung</em> effect that set this whole story in motion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=883cf2f485ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/ohno-and-ehn-constraints-for-innovation-and-quality-as-a-virtue-883cf2f485ee">Ohno and Ehn: Constraints for innovation, and quality as a virtue</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Foresight and the Question of Where I’ll Be in Five Years]]></title>
            <link>https://medium.com/analysts-corner/foresight-and-the-question-of-where-ill-be-in-five-years-990a0e9469d6?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/990a0e9469d6</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[foresight]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[future]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Sat, 20 Jun 2026 06:24:19 GMT</pubDate>
            <atom:updated>2026-06-20T06:24:19.069Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZakKnoFzbNC3P5k6SJ6hGQ.jpeg" /><figcaption>Business analysis seen through a Futures Cone. Illustration by author.</figcaption></figure><p>Recently, I took part in organising the <a href="https://ba-beyond.eu/">BA &amp; Beyond</a> conference in Copenhagen. It was a day fully focused on business analysis — covering idea generation, product strategy, problem framing, user needs, and connecting business goals and solutions in software development. On this day, we took a step back to gain a broader and longer-term perspective beyond the daily office routine. And, of course, to connect with peers across industries and experiences.</p><p>One of the final presentations, by <a href="https://de.linkedin.com/in/natalie-petryshak">Nataliia Petryshak</a>, focused on foresight. She introduced the <a href="https://thevoroscope.com/publications/foresight-primer/">Futures Cone</a> through which we see the scenarios of the future. It illustrates how the path to these scenarios is paved with increasing uncertainty as the cone widens. The wider the cone, the harder it is to “hit” the scenarios the future may hold. So which ones should we pursue, and how do we get there?</p><p>The key is to “feel our way forward” step by step, taking the future one step at a time while always keeping the goal in sight. In the long run, this approach is better than laying out elaborate plans years in advance. That’s why we put effort into creating product roadmaps. Here, we define what we want to achieve and organise the prioritised sequence of deliverables. And we continuously evaluate and adapt the roadmap to stay aligned with the goal.</p><p>How do we gain insight into these scenarios? By picking up signals, that is signs that something is changing. Not opinions or undocumented claims, but concrete actions. Both internally within the organisation and externally. Externally, these signals come from existing customers, potential customers, competitors, and partners. When viewing the future through the Futures Cone, we use these signals to point the way toward the desirable scenarios.</p><p>As it happens, I’ve been in my current position for five years. And the classic question has long been (and seemingly still remains) “Where do you see yourself in five years?”</p><p>It reminded me of an experience from five years ago, when I was interviewing for a product owner position. I was being interviewed by a product manager and a release train engineer. It was a large company, where multiple teams delivered different parts of a vast ecosystem of IT applications. Because of this, they had both a product manager to coordinate strategy and goals, and a release train engineer responsible for detailed cross-team planning. As a product owner, I would have been working with one of those teams.</p><p>“How do you see your career developing? Is becoming a product manager your next step?” the product manager asked me.</p><p>“I see myself as a business analyst and product owner. New methods and tools are constantly emerging, and the environment we work in is always changing. It requires an active effort to stay relevant in my role, and I hope to still be doing that in the future.”</p><p>I think that answer actually surprised them, but they seemed to accept it. Hindsight is such a wonderful thing. Five years later, at BA &amp; Beyond, as I reflected on that experience, I was struck by the product manager’s naivety. They were undoubtedly fully equipped to ensure their portfolio of IT applications was foresighted. But what about foresight when it came to future competences and skills?</p><p>In the meantime, many organisations have dramatically changed how they structure work in their IT development departments. At the same time, numerous companies have streamlined their business models. Maybe, five years on, that company I interviewed with no longer even has product managers? Or product owners, for that matter.</p><p>When no one knows what the business world will look like in five years, how can anyone realistically expect employees to answer where they see themselves in that same timeframe?</p><p>Before BA &amp; Beyond in Copenhagen officially wrapped up, I had decided to take a more analytical and systematic approach to my career. Even though my answer about where I saw myself in five years had surprised the product manager, it, too, was marked by a certain naivety. A belief that I would figure it out along the way, as long as I stayed curious and observant. Maybe a slightly more systematic and methodical approach wouldn’t hurt.</p><p>After Nataliia’s talk, I now knew how.</p><p>On the bus ride home, I pondered how I could construct a Futures Cone for my own carrier. I had already gathered several relevant scenarios throughout the conference that day. For example: the tension between compliance and innovation; the growing availability of off-the-shelf software products; the demand for processes where AI and users collaborate in a sustainable and responsible way; and the strong political interest in European digital sovereignty.</p><p>What signals could I immediately access? Once I was back in the office, I could start mapping out the past five years to identify what I had learned, how, and why. I don’t know what I will gain from this, but I hope to find signals that can point toward the scenarios most relevant to me in my current environment and role. And, possibly, it will give me further ideas about where else to look for signals.</p><p>The next time I’m asked where I see myself in five years, I think my answer will still be: “I see myself as a business analyst and product owner, remaining relevant in the environment I’m in.” And this time, it will be followed by a qualified take on how I’m orienting myself toward the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=990a0e9469d6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/foresight-and-the-question-of-where-ill-be-in-five-years-990a0e9469d6">Foresight and the Question of Where I’ll Be in Five Years</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Beauty of Structure and the Charm of Disorder]]></title>
            <link>https://medium.com/analysts-corner/the-beauty-of-structure-and-the-charm-of-disorder-4ff8118b40a9?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ff8118b40a9</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[liberating-structures]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Mon, 04 May 2026 07:05:14 GMT</pubDate>
            <atom:updated>2026-05-04T07:05:14.213Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*rEHuvG05X0hhm8VliXVbUw.jpeg" /><figcaption>Images by author. Left: A busstop in Nagoya. Right: Howl’s Moving Castle in Ghibli Park</figcaption></figure><p>When my family and I travelled around Japan for two weeks, the travel organiser had pointed out more than once: <em>“In Japan, you’re on time when you arrive ten minutes early.”</em> It was only when we were there that I understood what he meant.</p><p>On our trip, we visited <a href="https://ghibli-park.jp/">Ghibli Park</a>, an experience park dedicated to Studio Ghibli’s animated films, which elegantly blurs the lines between reality and fantasy. After a long day in the park, we arrived at the bus stop early to ensure we got a seat. We neatly lined up in the queue behind the passengers already waiting. We had learned this that morning when we took the bus from Nagoya to the park, where the queue was clearly marked on the floor at the bus stop. Fifteen minutes before departure, the bus pulled up to the stop. This gave the driver time to answer all the tourists’ questions about where the bus was going, ensure the tickets were in order, that all seats were filled, and that passengers had their seatbelts on. That way, he could depart exactly on time. And when the driver made an effort, I, as a passenger, also made a little extra effort to be polite and ensure I didn’t leave my empty water bottle behind when the driver set a good example. It was the least I could do!</p><p>This stood in stark contrast to Wizard Howl’s moving castle, which we had just seen inside the park. Here, apparent disorder reigned in a world of magic, comprehensible only to the charismatic and brilliant wizard himself. The first room you entered was a living room, kitchen, and workshop all in one. The doorknob could be turned, and with each of its four settings, the door led to a different place. The kitchen table also served as a workbench, cluttered with books, notes, and breakfast dishes. On the first floor lay his bedroom, where it was nearly impossible to walk across the floor due to magical trinkets, and the ceiling was densely hung with colourful odds and ends. Was it for decoration, or did it serve a purpose? Only the wizard knew.</p><p>During the 40-minute bus ride back to Nagoya (arriving precisely on schedule), with cherry blossoms and bamboo blending into the concrete of the motorway, I let my thoughts wander. I wondered whether my work meetings resembled a bus ride or a visit to the enchanted castle more. I was genuinely unsure.</p><p>On an entirely ordinary bus ride (where the only purpose was to get from A to B safely and on time) I could see what clear structures did for the experience and my overall state of mind. As we approached the bus station, I promised myself I’d follow up on this when I returned to the office — and then promptly forgot all about work again.</p><p>On my first day back at the office, I arrived early. As expected, I’d forgotten my PC password, and of course, my phone was dead. I had to wait for my work phone to charge enough so I could call IT support and reset my password, just to get started on my inbox.</p><p>After two weeks away from the office, I saw it with fresh eyes. How my workspace, in a way, resembled the wizard’s workshop. There were notes and half-finished presentations I was working on or wasn’t sure if I’d need later. Markers in different colours, pencils, a compass, a ruler. New and old visualisations, both hand-drawn and printed from digital files. Post-its in various shapes (including bird-shaped ones). A stress ball shaped like a lightbulb, a hippopotamus carved from soapstone, paperclips shaped like dolphins. And, of course, books.</p><p>One of the books on the shelf was <a href="https://www.liberatingstructures.com/"><em>Liberating Structures</em></a>. The bus driver’s approach to everything reminded me most of all of <em>Liberating Structures</em>. So when I saw the book on the shelf, I remembered my promise to myself. Maybe it was the key to holding better meetings?</p><p>Between two meetings, I pulled the book from the shelf and flipped through it while sipping my coffee. <em>Liberating Structures</em> is an approach to collaboration that focuses on creating a space where everyone has the opportunity to contribute equally.</p><p>I opened the book to refresh my memory of the principles behind it, and the first three were:</p><ol><li>Include and unleash everyone</li><li>Practice deep respect for people and local solutions</li><li>Never start without a clear purpose</li></ol><p>I can’t ask participants to arrive 10 minutes before my meeting starts. But I can choose to prioritise these three principles when I run meetings. I can do this with two simple steps:</p><ul><li>Ensure everyone has the chance to settle in before the meeting begins, even if it takes time away from the agenda itself.</li><li>Check in with participants about what they expect to gain from the meeting.</li></ul><p>I’m curious to see what will come from more meetings where shared understanding is valued over getting through the agenda. Hopefully, it will lead to better relationships, less rework, and, ultimately, better solutions.</p><p>In the middle of the afternoon, a colleague came down to the office to discuss a task we needed to follow up on. <em>“What a mess this is!”</em> she exclaimed spontaneously. Yes, maybe it looks messy. But that very disorder is a prerequisite for the space that is just as important as the inclusive and structured conversation — namely, the space where what emerges from meetings and discussions needs to be processed. It’s also necessary to be able to place old ideas in new contexts, to connect existing knowledge in new ways, to categorise and group information from different perspectives, and to experiment with alternative visualisations of the same information.</p><p>Disorder and unpredictability have their place. However, they must be guided and restrained by openness, transparency, and structure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ff8118b40a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/the-beauty-of-structure-and-the-charm-of-disorder-4ff8118b40a9">The Beauty of Structure and the Charm of Disorder</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI4BA: Business Analysis of Business Analysis — The Interplay Between Intention and Pattern…]]></title>
            <link>https://medium.com/analysts-corner/ai4ba-business-analysis-of-business-analysis-the-interplay-between-intention-and-pattern-9dce0435c092?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dce0435c092</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 06:19:00 GMT</pubDate>
            <atom:updated>2026-03-02T06:19:00.302Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>AI4BA: Business Analysis of Business Analysis — The Interplay Between Intention and Pattern Recognition</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*V_udUwj302HeMXmkgy611g.png" /><figcaption>Wordcloud created by AI based on the dataset</figcaption></figure><p>Last spring, I co-founded a local chapter of the International Institute for Business Analysis (IIBA) in Denmark with a group of fellow business analysts. As part of this process, we used business analysis to develop a strategy for the chapter and prioritise initiatives. This was essential during a phase when we were still establishing ourselves and getting to know the professional community and its unique characteristics in Denmark.</p><p>This story is about how I conducted the analysis and what I learned along the way about how generative AI works and can be applied to business analysis. As presented here, the analysis is structured according to the domains outlined in IIBA’s <em>Guide to Business Data Analytics</em>.</p><p>They are:</p><ul><li>Identify the research questions</li><li>Source data</li><li>Analyse data</li><li>Interpret and Report Results</li><li>Use results to Influence Business Decision-making</li></ul><p>The domains ensured that the analysis was conducted with a focus on purpose and the decisions that needed to be informed by data — not based on whatever data happened to be available.</p><h3><strong>Identify the research questions</strong></h3><p>I lacked concrete knowledge of how business analysis is practised in Denmark beyond my own office walls. The aim of the analysis was to gain insight into how consistently the role is perceived across companies, what commonalities exist, and where differences lie. These are important insights for us as an association, as they help us tailor our activities to the right audience with the right content.</p><h3>Source data</h3><p>How could I obtain knowledge about how business analysis is actually practised? The best source of information I could think of, was job advertisements. If I were to conduct interviews or a survey, it would, to a large extent, be limited to the reach of my personal network, and I would want to expand my horizons beyond that. So, I collected 58 job advertisements from LinkedIn over a five-month period in 2025. I simply copied the texts into a document. With generative AI, it would be possible to examine what skills Danish employers are seeking in business analysts.</p><p>I removed everything in the listings that wasn’t related to the actual job content (such as terms, recruitment processes, and company culture). I did this to simplify the analysis by ensuring the generative AI only analysed information relevant to the study.</p><p>I began by anonymising all the advertisements, removing names of people, products, or anything else that could identify the company. I did this to ensure the analysis results didn’t contain information that could identify a specific company and to avoid sharing non-anonymised details with an AI model.</p><p>Then, I had the AI convert the texts into bullet points to make the content easier to overview. After that, I compiled everything into a single document.</p><h3>Analyse data</h3><p>I wanted to analyse whether the Danish job advertisements aligned with the content of IIBA’s standard for business analysis, <em>A Guide to the Business Analysis Body of Knowledge (BABOK®)</em>. The rationale for using a framework was to employ a definition of the profession that is both developed and widely recognised.</p><p>BABOK consists of these core knowledge areas:</p><ul><li>Strategy Analysis</li><li>Requirements Analysis and Design Definition</li><li>Solution Evaluation</li></ul><p>These are supported by the following knowledge areas:</p><ul><li>Business Analysis Planning and Monitoring</li><li>Elicitation and Collaboration</li><li>Requirements Lifecycle Management</li></ul><p>Additionally, BABOK defines six underlying competencies:</p><ul><li>Communication Skills</li><li>Analytical Thinking and Problem Solving</li><li>Business Knowledge</li><li>Behavioural Characteristics</li><li>Interaction Skills</li><li>Tools and technology</li></ul><p>My idea was to have a generative AI analyse the content to assess how the job advertisements fit within the six knowledge areas, the underlying competencies, and what fell entirely outside these categories.</p><h4><strong>Reducing bias</strong></h4><p>Some of the job advertisements were written in Danish, while the rest were written in English. Some of the English‑language adverts included words that I do not believe are commonly used in English — for example “sparring” and “self-driven”. But how could I ensure that this Danish‑influenced English would not be misunderstood, and that the Danish expressions would be correctly interpreted in relation to BABOK’s English terminology?</p><p>Naturally, I asked the AI agent about this. It recommended translating the Danish into English in order to minimise any potential bias. So I had the AI agent translate the Danish into English and then revised the results to ensure they were properly understood.</p><h4>One step forward and two steps back</h4><p>I asked a generative AI to categorise the content according to BABOK’s six knowledge areas, the six underlying competencies, and what fell outside BABOK’s scope. However, the results were either so general that they provided little insight, or so detailed that they were difficult to make sense of. It was also hard to get a clear impression of what featured most and least.</p><p>Some of the results were also rather odd. General follow-up on the team’s tasks and management of the sprint backlog were categorised under <em>Business Analysis Planning and Monitoring</em>. Everything related to testing was categorised under <em>Solution Evaluation</em>, which I wasn’t convinced was correct.</p><p>So I tried running the results through IIBA’s business analysis AI agent instead. But it couldn’t accept attachments, and there were limits to how much text I could include in a single prompt. It was clear that it hadn’t been designed for this purpose — but I decided to give it a try anyway.</p><p>I split the text and ran the first part through. Task management was categorised under <em>Requirements Life Cycle Management</em> in the first partial analysis. But when I submitted the next part of the text, it categorised it under <em>Business Analysis Planning and Monitoring</em>. So its answers were not consistent. Testing activities were categorised under <em>Requirements Analysis and Design Definition</em> — again, a different answer from the first AI agent.</p><h4>Time to bring out the heavy artillery</h4><p>I needed someone who could relate to the intention and meaning behind BABOK — not just its wording. So I contacted <a href="https://be.linkedin.com/in/stefboss">Stefan Bossuwé</a>, who has run many BABOK study groups for the <a href="https://brussels.iiba.org/">IIBA Brussels Chapter</a>, to get his assessment of how BABOK should be correctly understood.</p><p><strong>Stefan:</strong> “It becomes too unspecific when you categorise the content based on the knowledge areas. The knowledge areas are essentially just collections of tasks, but the real substance lies in the tasks themselves. So you should probably categorise based on the tasks instead. That will give you a more detailed result.”</p><p><strong>Me:</strong> “That would definitely give a more nuanced picture! But I don’t think it will change the categorisation of the tasks that involve managing the team’s work on the sprint backlog. Is that really business analysis?”</p><p><strong>Stefan:</strong> “No, that’s project management, not business analysis. Task management within the scope of business analysis only concerns the management of the tasks within the business analysis work itself.”</p><p><strong>Me:</strong> “Thanks for confirming that! My final question is about testing. Is it really part of solution evaluation? I thought solution evaluation was about follow-up after implementation.”</p><p><strong>Stefan:</strong> “Well, BABOK doesn’t include testing at all! Defining acceptance criteria and ensuring that requirements can be tested is included, but nothing beyond that.”</p><h4>That’s when I fell down the rabbit hole</h4><p>There are 30 tasks across the six knowledge areas. I quickly realised that it was far too cumbersome to run everything through an AI agent that only outputs plain text. Instead, I tried using an AI agent specialised in data analysis. I processed all the job adverts through the analysis agent, and it generated a CSV file as output.</p><p>For the 58 job adverts, this resulted in more than 1,000 rows in a spreadsheet. Perfect! The advantage of having the data in a spreadsheet was that I could load it into a data‑visualisation tool, count the frequency of the different tasks, and group them into knowledge areas. That way, I could also visualise the relative size of each area.</p><p>The result wasn’t completely off, but it wasn’t spot‑on either. Much of the content was too unspecific to be categorised at task level. A single sentence could relate to two different tasks as well as an underlying competency.</p><p>The analysis agent asked: <em>“Would you like me to generate a refined keyword mapping for better accuracy?”</em></p><p>Why not? And it turned out to be b… brilliant! The agent generated a table indicating which keywords should determine which task the content belonged to. For example:</p><blockquote><em>“Communication skills”: [“communication”, “writing”, “verbal”]</em></blockquote><p>I could refine the mapping table myself and tried running the analysis again. But now the problem was that the analysis agent stuck far too rigidly to the keywords and didn’t account for things that were obviously close in meaning but not exact matches. I ran the analysis with an updated table three or four times, but time and again things fell outside the categories. I had to add more and more words. On the positive side, I could more precisely control how the specifically Danish phrasing should be handled, and in that way reduce bias.</p><p>Again, I needed Stefan’s input. At this point, the agent was placing testing activities under the verification and validation activities (included in <em>Requirements Analysis and Design Definition</em>).</p><p><strong>Me:</strong> “You said that testing is not included in BABOK, but there are activities for verification and validation — isn’t that quality assurance?”</p><p><strong>Stefan:</strong> “Yes, it is. But when we’re talking about BABOK, it only concerns quality assurance of the requirements themselves — not of the solution the requirements apply to.”</p><p>Too much fell outside the scope, and more and more keywords had to be added. The prompt kept growing. It would be an endless task to create a sufficiently good mapping table. On top of that, I somehow needed to build in the understanding required to ensure that planning‑related testing activities were placed within the context of business analysis, not within the broader context of software development. A new question also emerged: how much of my own unconscious bias had I built into the mapping table?</p><p>Categorisation at task level became too random, because too much content was too ambiguous to be placed confidently under a specific task.</p><p>I was close to giving up. It began to feel almost as laborious to create a sufficiently good keyword table as it would have been to review everything manually.</p><h4>The light at the end of the tunnel</h4><p>And then I remembered what I had so often heard about generative AI: that its strength lies in recognising patterns and connections, but that it struggles with calculation and has limited contextual understanding. From the results, I began to suspect that I was undermining the generative AI’s strengths by trying to control it too tightly. Perhaps the highly constrained mapping table was inhibiting its ability to detect patterns and relationships?</p><p>So I decided to try a different strategy: to write a long text prompt asking the analysis agent to categorise the content according to knowledge areas, underlying competencies, and whatever fell outside BABOK. I also added some text describing the types of organisations business analysts typically work in — in other words, the context in which business analysis is practised.</p><p>Here’s an example of that:</p><blockquote>As business analysts we are usually part of a delivery team, often an agile team. It is not unusual for us to be the only business analyst on the team, and agreements about our deliverables are made with a project manager or a product owner.</blockquote><p>For each knowledge area, I defined its boundaries both by the tasks it includes and by those it does not include. In other words, what does not fall under that knowledge area. I also clarified what common IT development terms mean in the context of business analysis.</p><p>Here’s an example from the prompt I wrote:</p><blockquote>Verification and validation refer solely to ensuring the quality of the requirements themselves, not the quality of the solution. This means that test is not included. Architecture refers to the structure of the requirements, not to solution architecture-</blockquote><h3>Interpret and Report Results</h3><p>I could now quite easily import the results of the analysis into a data‑visualisation tool. This resulted in the article published on the association’s website:</p><p><strong>Danish version:</strong> <a href="https://denmark.iiba.org/page/forretningsanalyse-i-tal-hvad-eftersp%C3%B8rger-danske-virksomheder">Forretningsanalyse i tal: Hvad efterspørger danske virksomheder? | Denmark</a><br><strong>English version:</strong> <a href="https://denmark.iiba.org/page/business-analysis-in-numbers-what-do-danish-companies-expect">Business Analysis in Numbers: What Do Danish Companies Expect? | Denmark</a></p><p>The article provides business analysts in the Danish job market with valuable insight into how business analysis is practised.</p><h3>Use results to Influence Decision-making</h3><p>As an association, the analysis gives us insight into what is relevant for both the broader and more specialised parts of our target group. We will use this to plan relevant content for events and for the website.</p><p>The analysis has also made me reflect on whether the context we operate within is perhaps so implicit to those of us who have been in the profession for many years that it becomes difficult for others to grasp. If a generative AI doesn’t understand it, will a recent graduate or someone new to the field? Perhaps that should be the topic of the next article on our website.</p><h3>Model vs design</h3><p>For me personally, using AI in an area I understand in depth has strengthened my understanding of how generative AI actually works.<br> I have gained a clearer sense of how much business‑specific knowledge it requires, both from a theoretical and a practical perspective. You probably don’t care about the details of BABOK’s structure (and I genuinely understand why!), but I’ve included them here to illustrate what it took to carry out even a tightly scoped analysis on a small dataset.</p><p>I have also come to realise that even general‑purpose generative AI agents are designed with a specific purpose in mind. It isn’t only the model that influences the result, but also the design of the agent.</p><p>Regardless of the tool, the intention, meaning and context must be defined by me as the user and communicated to the generative AI agent I am working with.</p><p>Business analysis of business analysis not only contributes to the strategic focus of our association. It is also a playground where we can experiment with new approaches and methods within our profession.</p><p><strong>Stefan</strong>: “Are there any job ads for business analysts related to the implementation of AI?”</p><p><strong>Me</strong>: “Yes, there are two ads looking for business analysts to join teams developing AI applications. By the way, where would those roles fit into my analysis?”</p><p><strong>Stefan</strong>: “That’s a good question! But as I often say when I speak: It depends…”</p><p><strong>Me</strong>: “Hmm… I guess the context that business analysis is practised in, and how BABOK is applied, is constantly changing. That’s exactly why we need a strong community: so we can help each other answer that type of questions and grow as professionals”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dce0435c092" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/ai4ba-business-analysis-of-business-analysis-the-interplay-between-intention-and-pattern-9dce0435c092">AI4BA: Business Analysis of Business Analysis — The Interplay Between Intention and Pattern…</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Perspective, Focus, and the Balance Between the Near and the Far]]></title>
            <link>https://medium.com/analysts-corner/on-perspective-focus-and-the-balance-between-the-near-and-the-far-e3e4d5351102?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3e4d5351102</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[perspective]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[focus]]></category>
            <category><![CDATA[henry-heerup]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Sun, 04 Jan 2026 08:55:15 GMT</pubDate>
            <atom:updated>2026-01-04T08:55:15.927Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*_y7_15fiyzzq4f7e3oWf8Q.jpeg" /><figcaption>Picture by author: “Perspektiv” by Henry Heerup</figcaption></figure><p>I have a lithograph by Henry Heerup hanging on my wall. The piece depicts a man with a bird perched on his head and is titled <em>“Perspective.”</em> The man and the bird view the world from two different perspectives: the man from a grounded, near-sighted vantage, and the bird from a far-sighted one. The man sees what is close, observing the richness of detail in his immediate surroundings. When the bird takes flight, it can survey the external world and see it from a broader perspective. In this way, the bird brings the man insights that help him understand his immediate world and the possibilities for action in new ways.</p><p>Lately, I have begun to pay more attention to the lithograph again.</p><p>I have worn glasses since I was nine, and it has always been something I have simply accepted as a natural part of me. But recently, I have had to start switching between two pairs: one for reading and one for distance. As I have grown older, I have become both short-sighted and long-sighted at the same time.</p><p>Where I once effortlessly shifted focus between the distant and the near, I now have a heightened awareness of it, because I have to physically change my glasses. This has given me a deeper consciousness of whether my focus is directed at what is immediately in front of me or at the broader world around me. Am I using the man’s gaze or the bird’s? For example, I can no longer multitask with something on my computer while the TV is on, because I can’t switch screens without switching glasses.</p><p>One of the challenges of being a product owner and business analyst is the need to shift focus constantly. Balancing the short-term details of the sprint, where the devil is in the details, and the long-term roadmap, which so easily succumbs to analysis paralysis, can be tricky. Mastering this balance actually feels a lot like switching between reading glasses and distance glasses. And just as I can’t wear two pairs of glasses at once, I can’t focus on both the sprint and the roadmap simultaneously as a product owner.</p><p>Often, it is the immediate, short-term tasks that demand my attention. They drive progress in the here and now or help a colleague move forward with their work, offering immediate rewards. Yet, I still need to be mindful of shifting my focus (just like changing glasses) so I can make time to work on what needs to go into the sprint two months from now. And in fact, when I have that broader perspective, it becomes easier to sort and prioritise the short-term tasks.</p><p>I have become even more aware of these shifts in focus. The hardest part is actually when I am in a meeting. It is almost impossible for me to take notes while also following what is being presented on the screen in the room. I end up having to choose: Do I listen to what is being said and take notes, or do I follow along with the presentation? It makes me wonder: Was I ever truly capable of listening, writing, and reading all at the same time?</p><p>When I am the one presenting in a meeting, it forces me to focus on what is being shown on the big screen — the same thing everyone else is seeing — instead of looking at my own screen. Fortunately, I am no longer physically able to check my email while others are presenting. It is actually a relief to be free from that temptation and to be forced to listen.</p><p>Lately, I have had a period in the office where my focus was primarily on the short-term. Putting out fires, keeping deliveries on track, and balancing competing needs. That is just how it has to be sometimes. The week before Christmas, I finally had a Monday with very few meetings and no tasks with deadlines due that same day. I was actually making good progress structuring the content of the roadmap for upcoming deliveries.</p><p>Then an email popped in: <em>“Can you quickly help with some data for an important case?”</em> Of course I could! And just like that, my calm workflow was shattered, and I was back in fire-fighting mode. It really takes a conscious effort to make space for the slow and steady rhythm of work, that it required for focus on the long term.</p><p>That is why I have set aside the first two days back in the office in the new year for exactly that. I have also prepared a week plan for the first week that can serve as a parking lot for everything that might come crashing in and has to wait until later in the week.</p><p>Am I sick and tired of being dependent on two pairs of glasses? Absolutely! And that is precisely why it gives me even more reason to let it serve as a reminder of one of the most important skills in my profession: the ability to navigate effectively between the near and the far.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3e4d5351102" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/on-perspective-focus-and-the-balance-between-the-near-and-the-far-e3e4d5351102">On Perspective, Focus, and the Balance Between the Near and the Far</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From convergence to divergence: Can AI help us ask the right questions?]]></title>
            <link>https://code.likeagirl.io/from-convergence-to-divergence-can-ai-help-us-ask-the-right-questions-9516732ffc4e?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9516732ffc4e</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[denmark]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Wed, 22 Oct 2025 00:28:03 GMT</pubDate>
            <atom:updated>2025-10-22T00:28:03.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oFyGd_tMqV6mjbt_h8Ee7w.jpeg" /><figcaption>Illustration created by author</figcaption></figure><p>Recently, I attended what was billed as a conference on AI agents and I signed up expecting a high-level overview of what’s happening in the field here in Denmark. Apart from an opening and closing keynote, however, it was little more than a billboard for the event’s many sponsors and partners. Held in the city’s largest cinema, the venue could seat around 1,000 attendees, ensuring the sponsoring companies got their money’s worth.</p><p>Most of the day consisted of one 10-minute case presentation after another, with no opportunity for dialogue. I quickly gave up on taking notes. There was no network on my mobile phone, so I had no way to check my work emails. Sitting there in the cinema seat, listening, my thoughts had plenty of room to wander and reflect on my own experiences with generative AI.</p><p>Many of the presented cases focused on AI agents designed to handle the tedious work for customer service employees. Namely, responding to complaints from dissatisfied customers. Apparently, Danish companies have a lot of those.</p><p>My immediate thought was that it would be better for everyone if companies instead invested the same energy into eliminating the root causes of customer dissatisfaction as they do in developing an AI agent to reply to emails. That way, more would be gained. Have corporate services become so complex with digitalisation that we no longer understand how to improve them? The alternative, it seems, is to just let generative AI write an endless amount of emails to angry customers.</p><p>After lunch, there was a panel debate with the tech giants. Microsoft sang the praises of their own products, IBM advocated for independence from American language models (I think they might be co-financing a Danish-developed language model), and no one could really remember what Meta said.</p><p>It was a bit unclear what any of this had to do with my own work as a business analyst. Whether in terms of application strategy, software requirements, or the concrete design decisions businesses have to make on a daily basis. So, I had plenty of time to think further.</p><p>My thoughts turned to the many methods I’ve used over the years to describe requirements. Each one promises to be the format that will finally give stakeholders a shared understanding and describe requirements with the user at the centre: From use cases to user stories, Gherkin scenarios, and Jobs-to-be-Done.</p><p>They say, that when women live together, their menstrual cycles eventually synchronise. That hasn’t been my experience with software requirements formats. None of them automatically creates the same kind of synchronisation between me, the project managers, and the developers I’ve worked with. None of the above formats comes with a built-in shared understanding among all stakeholders. A template alone doesn’t cut it. Even if it provides space for the user and allows all aspects of the requirements to be described, it makes no difference if the right stakeholders haven’t contributed to the content poured into the template.</p><p>My early experiences with generative AI in my work have led me to consider another possibility. With generative AI, I can easily use a well-written use case and Gherkin scenarios (drafted by generative AI from the use case) to draft an initial version of user stories with acceptance criteria.</p><p>It takes a quarter of the time it would take to do it manually. So, if the development team prefers redundancy, so be it. It works. The redundancy arises because Gherkin scenarios and acceptance criteria contain the same information, requiring double the maintenance. Generative AI can also help identify inconsistencies, thereby reducing auditing efforts.</p><p>I’ve always thought developers are spoiled because they often can’t be bothered to look anywhere beyond a user story. That’s not a luxury a business analyst can expect. Actually, I can see it from the developers’ perspective. Their deliverables are different from mine, and so their worldview must also have a different structure.</p><p>Now it was time for yet another panel debate, this time on responsible use of AI. A lawyer stated that you simply need to comply with the law and that you <em>can</em> do so, if you just make a bit of effort. A representative from the business community claimed that the EU’s purpose is to make life difficult for Danish companies and stifle innovation. I wonder if they borrowed Microsoft’s CoPilot chatbot during the lunch break to write their speeches?</p><p>Listening to these simplistic takes, I found myself reflecting on why my role even exists in the first place. In fact, I’ve often thought that the very reason my job exists is the high complexity of the organisations I’ve worked in. Just think: it takes a specialist role to translate business needs into requirements and then into implementation strategies.</p><p>This might be because the structures are so complex that business specialists can’t simultaneously be business specialists <em>and</em> oversee IT development work. They’re also too complex for business specialists to focus on both operations and development. And they’re too complex for any leader to orchestrate collaboration among all the business specialists that would be needed.</p><p>Just like in development teams and with our services, this is a sign that the structures we’ve built around ourselves are too complex. And once again, we’re choosing to fix it with advanced technology.</p><p>And then keynote speaker <a href="https://maya-ackerman.com/">Dr. Maya Ackermann</a> took the stage. She blew me away with her perspectives on what generative AI is and the role it <em>should</em> play. According to her, it’s in the very nature of AI to open up possibilities, not to provide definitive answers. It is, by design, divergent rather than convergent, meant to help us humans become more creative. Her fundamental question was: <em>“Have you become more competent and creative by using AI. Competent and creative even if you never use AI again?”</em></p><p>If I follow Dr. Ackermann’s line of thinking, we can use generative AI to expand and explore possibilities for reducing complexity in teams, businesses, and services. In the near future, I’ll continue to use AI in a convergent way when I draft acceptance criteria from Gherkin scenarios. But at the same time, I want to deepen my understanding of how to use AI in a divergent way, to explore opportunities for improving how our team collaborates.</p><p>Tech giants and software vendors would love to convince me they have all the answers. I just don’t think I know yet which questions I want to ask.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9516732ffc4e" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/from-convergence-to-divergence-can-ai-help-us-ask-the-right-questions-9516732ffc4e">From convergence to divergence: Can AI help us ask the right questions?</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ants, analysis and advocacy]]></title>
            <link>https://medium.com/analysts-corner/ants-analysis-and-advocacy-c02f5d440f69?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c02f5d440f69</guid>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[ants]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Tue, 26 Aug 2025 01:39:31 GMT</pubDate>
            <atom:updated>2025-08-26T06:34:59.622Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w9h0DHwZ6TdMfO2kUC8lLA.jpeg" /><figcaption>Illustration by author</figcaption></figure><p>For 14 days, along the wall of a fourth-floor balcony in Vienna’s 2nd district, Leopoldstadt, ants followed the same route every day. Their path led them up the wall just below the roof, arched across past the folded umbrella, and back down to the edge near the floor. Then, they would disappear. Beneath the floorboards? Down to the balcony below? Some ants went up, others down.</p><p>When it rained, nearly all the ants were gone, but slowly, more and more would reappear once the rain stopped. I was staying in that apartment on holiday, and whenever I had had enough of the city’s heat and crowds, I would go to the balcony to read, solve sudoku, and watch the ants. I had seen ants countless times before, but removed from the daily routine, I finally had the presence of mind to truly observe them. Why did they tirelessly follow the same path day after day? How did they remember the route?</p><h4><strong>How Ants Communicate</strong></h4><p>That is why I downloaded <a href="https://ca.linkedin.com/in/pamelapaterson">Pamela Paterson</a>’s book, <a href="https://www.amazon.ca/Science-Ant-Communication-Discussion-Other/dp/1479174416?ref_=ast_author_dp&amp;dib=eyJ2IjoiMSJ9.zUP5saHtBDLMkvMxnHWYrJ2ixDlQHLTiyednHBJbnr073Nw8ycwTcJR5lH9kwpJTDtGGTN6PDCmgO0ItZ_n-Rizor6XjVSG56uRe31WZd9e8kg08zMPAeR9WxlTKOl5Y.EfbmZikeHJVUtXztMx5NNbij5568BFjQZa1o43jkOvU&amp;dib_tag=AUTHOR"><em>The Science of Ant Communication: A Discussion of How Ants Talk to Each Other</em></a>, in a digital edition. I read it on the balcony, occasionally glancing up to follow the ants’ endless procession.</p><p>I learned about the multimodal ways ants communicate:</p><ul><li>They release pheromones, which influence the behaviour of other ants. Using their antennae, they detect these chemical signals, which can indicate food sources, the way back to the colony, danger, or territorial boundaries.</li><li>They exchange hydrocarbons through touch, sharing information about themselves with fellow ants.</li><li>They create vibrations and sounds to summon others.</li><li>Experienced ants can guide less experienced ones, effectively showing them the way.</li></ul><p>This explained to me how the ants on the wall could follow the same path day in and day out.</p><h4>Business analysis across borders</h4><p>Pamela Paterson, like me, is a business analyst. We both work broadly with software application strategy and requirements for digital solutions. She is Canadian and works as a freelance business analyst, author, and speaker. In other words, a thought leader in our field. This spring, she travelled across Europe with her husband, balancing remote work for a client with speaking engagements at conferences in various countries. She reaches out to local business analysts wherever she goes, not just to experience different cultures but to understand how business analysis is practised and what topics are top of mind. She is deeply passionate about fostering a professional community for business analysts and generously shares her expertise to advance our field.</p><p>I was one of the business analysts Pamela met when she visited Copenhagen. I have a standard nine-to-five job in a mid-sized Danish company, working in a digitalisation team. Digital solutions are becoming increasingly critical to our business, which means my skills are relatively new, and often unfamiliar, to colleagues in other departments. Sometimes, I feel like an ant on that balcony wall: my colleagues can see the path I am on, but they don’t understand the journey itself. Just as I could not grasp the purpose of the ants’ endless march up and down the wall, I sometimes sense that my colleagues don’t fully understand what I do or why.</p><p>What struck me is that, despite our very different work lives, the core of what drives us is the same: enabling change that creates value for organisations and users.</p><p>This shared focus is what sustains a strong, vibrant international community of business analysts, even though we work under different conditions.</p><p>When I experienced Pamela’s commitment to our professional community, it occurred to me that it’s no coincidence she wrote a book about ants.</p><p>Around the same time I met her, I was reading a novel about a society modelled on ant colonies.</p><h4><strong>Stories Create Realities</strong></h4><p>The novel, <a href="https://www.gyldendal.dk/produkter/fremtidsspejl-9788702304206"><em>Fremtidsspejl</em></a> (<em>Future Mirror</em>) by Svend Åge Madsen, tells the story of a man named Mithya who returns to the village where he grew up. In his absence, the village has transformed into a moneyless society where doors remain unlocked, inspired by the organisational and communicative habits of ants. Mithya observes the villagers exchanging signals through touch and tasks being distributed in ways he can’t decipher. He is working on a project exploring how stories can be self-generating, revealing the infinite interpretations of the world. In the village, he realises how the residents’ way of life enables them to tell new stories that shape their desired future.</p><p>I revisited these thoughts on another balcony (my own in Copenhagen) on the last day of my holiday, as I pulled <em>Future Mirror</em> from my bookshelf.</p><h4><strong>Sustaining and Developing the Professional Community</strong></h4><p>Unlike ant colonies, business analysis communities cannot thrive in isolation. We are part of teams and organisations that need to understand how we contribute to the bigger picture. That’s why we must tell the story of our profession, as Pamela does through her books and lectures, and as <a href="https://medium.com/u/60e0df675f87">Igor Arkhipov</a> does with the Medium publication <em>Analyst’s Corner</em>.</p><p>Every day in the office, our behaviour helps sustain this “ant society.” But to keep it alive, that’s not enough. We must also share stories about business analysis. This is what enables others to not only see but also understand the path that we walk.</p><p>I was trained at university to think like a researcher, convinced that to write or speak about something, I needed to say something original. But experience and reading Svend Åge Madsen has convinced me that that is not true. I am a practitioner, not a researcher.</p><p>Writing on Medium has primarily been for personal reflection for me. I have however, come to realise that even repeating what is already known — placing it in new contexts and telling it in new ways — has value. It reaches people who may not have heard it before or who find themselves in situations where the message resonates more deeply. Just like ant colonies did not catch my attention until I had time to watch ants.</p><p>By speaking of the business analysis community as strong and vibrant, my story helps ensure it remains sustainable in the future. Because both my readers and I will act accordingly. So, this is my contribution to keeping the professional community of business analysts alive and thriving.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c02f5d440f69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/ants-analysis-and-advocacy-c02f5d440f69">Ants, analysis and advocacy</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Uncovering my voice on Medium with data analytics]]></title>
            <link>https://code.likeagirl.io/uncovering-my-voice-on-medium-with-data-analytics-f033fdb9f2e5?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f033fdb9f2e5</guid>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Mon, 14 Jul 2025 09:02:57 GMT</pubDate>
            <atom:updated>2025-07-14T09:02:57.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JKP4VVZCs46F-ti0o6UNjg.jpeg" /><figcaption>This is the basic, conceptual information model for the analysis I did on my Medium stories. Illustration by author.</figcaption></figure><p>For some time, I have been the product owner of the data platform within my organization. In this role, I continually promote data-driven decisions to reduce bias and increase inclusivity and transparency in decision-making.</p><p>To achieve this, I refer to <em>The Guide to Business Data Analytics</em> published by the <a href="https://www.iiba.org/">International Institute of Business Analysis (IIBA)</a>. The guide comprises these five domains:</p><ul><li>Identify the research questions</li><li>Source data</li><li>Analyse data</li><li>Interpret and report results</li><li>Use the result to influence business decision-making</li></ul><p>While working at my day job, I wrote 17 Medium stories about my experiences with business analysis and product ownership. Some time ago, I contacted a writing coach to get some feedback on my writing and define a clearer direction. One of his main pieces of advice was to identify my brand.</p><p>I had never considered what my brand might be, so I decided to use data to inform my decisions about the direction of my Medium writing.</p><p>Could data about my writing reveal possible voices to refine and amplify?</p><h3>Identify the research questions</h3><p>My initial hypothesis was that by analyzing my stories, I could identify patterns in terms of which themes most appealed to readers, as well as the strengths and weaknesses related to these themes.</p><h3>Source data</h3><p>The data I needed for this analysis included metadata about the stories, which is structured data. I also needed the texts themselves, which are unstructured data, so I had to treat these two types of data differently.</p><h4>Collecting structured data</h4><p>I created a spreadsheet for the structured data and added metadata about all the stories I had written. This included ID, the title, publication date, view count, and read count.</p><p>However, structured data alone wouldn’t give the insights I was seeking, as it didn’t reveal anything about the substance of the stories. I needed to understand the themes, qualities and areas of improvement in each story. As a consequence, I needed to create structured data out of unstructured data.</p><h4>Creating structured data from unstructured data</h4><p>For this, I used generative AI. Essentially, I pasted the full text of each story into a general-purpose generative AI application and prompted it for these three things:</p><ul><li>The five main themes</li><li>The three best qualities of the story</li><li>The three main areas of improvement</li></ul><p>I chose to use Mistral AI’s <em>Le Chat</em> for this purpose, which is developed in France. I picked it because I wanted the result to reflect an European perspective on what constitutes a good text. Although I am Danish, I intentionally refer to European values because our standards regarding everything except pork derive from broader European values.</p><p>To reduce bias and create consistent data for analysis, I developed a standard prompt that I used for all the stories. I made this prompt by asking Le Chat what characterizes a good text. I incorporated its response into a new prompt and also added links to <em>Medium’s Tips and Tricks for Medium Writers</em> and <em>Become a Code Like A Girl Writer.</em> The result was a list which also used input from those two guides. This was then used as my standard for prompting all the stories.</p><p>Using a standard prompt that described 15 characteristics of a good text, ensured that I knew the criteria Le Chat used to evaluate my stories and that the results were comparable.</p><p>I added tabs to the spreadsheet for themes, qualities and areas for improvement.</p><h3>Analyse data</h3><p>Now that I had the data I needed, I had to prepare it for analysis. I grouped the number of reads into five intervals, which allowed me to analyze the characteristics of the most-read and least-read stories. I also grouped the 80 different themes into twelve categories to identify patterns.</p><p>I then applied a tip that a data engineer once gave me. The problem with my data was that it contained many-to-many relations, as several themes, qualities and areas for improvements related to more than one story, and a story had five themes, three qualities and three areas of improvement. Many-to-many relations are considered bad practice, so I created three mapping tables to avoid this.</p><h3>Interpret and report results</h3><p>Now the data was ready to be visualized using a data visualization tool, which allowed me to gain insights into the most predominant themes, qualities and areas of improvement. I could also identify the themes of the most-read stories.</p><p>I could quite easily create a visualization showing which qualities and areas of improvement are related to which themes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ydG9lVqrsfTUMBwPIi1Q7w.png" /><figcaption>Screen dump of the report I created about my Medium stories</figcaption></figure><p>The three main themes were:</p><ul><li>Business analysis</li><li>Culture and collaboration</li><li>Using data</li></ul><p>The three main qualities were:</p><ul><li>Practical applications</li><li>Unique insights</li><li>Storytelling</li></ul><p>The three main areas of improvement were:</p><ul><li>Interactivity</li><li>Clarity, structure and conciseness</li><li>In-depth analysis</li></ul><h4>The main insights I gained</h4><p>The most interesting insight I gained from the analysis is that there was a correlation between the stories that were strong on storytelling and weak on structure. While anecdotes add context, it can be challenging to ensure they fit correctly into the flow of the story and that their relevance to the main message is clearly understood. This will be a focus point going forward.</p><p>I also discovered how instrumental business analysis is to how I approach my job. Stories about my work as a product owner are also themed with business analysis because the basic frameworks I apply as a product owner are rooted in business analysis.</p><h3>Use the result to influence business decision-making</h3><p>I have decided that my brand is to write stories using storytelling, rather than being instructional, about my personal experiences as a business analyst. As a practitioner, rather than a researcher, I am in a position to write stories centered around practical applications, rather than in-depth analysis.</p><p>To operationalize this, I have defined two hypotheses:</p><h4>Hypothesis 1: Stories that engage through storytelling will achieve a higher number of reads if the structure is well-defined and consistent</h4><p>I now intend to make storytelling part of my brand as a business analyst, allowing me to write and illustrate requirements with stories. Practicing storytelling on Medium will also give me the opportunity to enhance my storytelling skills further.</p><h4>Hypothesis 2: I will become a better business analyst by telling stories about the business analyst I want to become</h4><p>Writing about my experiences gives me the space to reflect on my practice. Through reflection, I can explore different versions of myself as a professional and assess what makes an impact over time.</p><h3>The evolving Medium voice</h3><p>Using data analytics allowed me to see my writing from a bird’s-eye view and to uncover patterns that have evolved over the 18 months I have been writing on Medium.</p><p>I now intend to focus on the two hypotheses I have defined when writing future stories. Next year, I can then perform the same analysis to see what the result of sharpening my focus and writing with greater intent is. I hope that new patterns will emerge, inspiring me to form new hypotheses and allowing my writing to evolve from there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f033fdb9f2e5" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/uncovering-my-voice-on-medium-with-data-analytics-f033fdb9f2e5">Uncovering my voice on Medium with data analytics</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The day I finally embraced the silos]]></title>
            <link>https://medium.com/analysts-corner/the-day-i-finally-embraced-the-silos-2439fb597bb6?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2439fb597bb6</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[silos]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Wed, 18 Jun 2025 03:13:34 GMT</pubDate>
            <atom:updated>2025-06-18T03:13:34.754Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8kOIHbhaN0-iTD3hQUE2A.jpeg" /><figcaption>Illustration by author</figcaption></figure><p>As a business analyst I have been involved in transforming a strategy into product deliverables over the last period of time. The goal of the strategy is to improve the member experience using digital tools in a Danish labour union advising members on matters related to employment and career.</p><p>Business stakeholders have been impatient, and my colleagues and I in the team IT &amp; Digital Solutions have been waiting for some objectives and a plan for refining ideas into deliverables. Earlier this week we held another meeting where the primary stakeholder expected a sign off on steering committee material, and I insisted on commitment to further qualifying ideas. To break the deadlock, I had prepared a speech about how my colleagues and I see the world, what we needed from our stakeholders and why. Here follows what I said.</p><p>Before we dive into the specifics of the strategy initiatives, I’d like to introduce you to the way we work in IT &amp; Digital Solutions, how we are organised and why. At the end of this speech, I hope you will see why this is important.</p><p>To understand how we manage complexity, I would like to briefly introduce the Cynefin framework. The framework divides situations into five domains: clear, complicated, complex, chaotic, and disorder. In our organisation, we primarily operate within the clear and complicated domains.</p><p>In the clear domain, cause and effect are obvious. We know what needs to be done and how to do it. For example, when we need to automate an additional step in an existing process that remains unchanged. In these cases, we know who is responsible for the process, which team member knows best how it is implemented, how to test it and which user guides to update. This is what we call best practice.</p><p>In the complicated domain, there is still a cause and effect relationship, but it requires analysis or expertise to understand. Much of the work we do within this strategy falls into this domain. Instead of one correct solution, there are several possible ones, that is what is called good practice. In these domains, we work with guiding constraints, such as principles for advisor responsibility, data protection laws, and the Danish Agency for Digital Government’s principles for responsible AI.</p><p>We apply this approach in the development of an AI agent that can assist in advising the members. We can work with hypotheses such as: “Simple enquiries can be answered faster and with fewer hand-overs”. To verify these hypotheses, we need to conduct experiments. Not to discover the unexpected, but to confirm or revise our assumptions. This might involve simulations, prototypes, or pilot projects.</p><p>Working with hypotheses and frequent deliveries encourages reflection and adaption of what we learn to revise following deliveries. However, in my personal opinion, we sometimes make the mistake of treating complicated initiatives as if they were clear. This results in delayed delivery plans and sometimes lower quality.</p><p>Our organisational culture is characterised by silos, and IT &amp; Digital Solutions is no exception. We’ve chosen an agile mindset because we often work in complicated domains where we need to gain some experience with new processes or technology before we can envision the final result. This allows us to try out things and adjust the scope. It’s a way of organising that is more flexible and better suited to handling change than traditional project structures.</p><p>As a result, we have organised ourselves into five product teams, which function as our silos. We can only develop deliveries that can be managed by our product teams. What we refer to as a project is either a major delivery within a single product team or a coordinated effort across two or three teams.</p><p>To place an initiative in the correct product team, we need to understand why something needs to be done. For instance, why should we implement our own digital career guidance tool? Is it to integrate it into our advisory processes, or to tailor guidance to the job types of our members? The answer to that question can lead to very different solutions.</p><p>To effectively execute any strategy, we maintain ongoing dialogue across our silos, involving the right stakeholders to determine where an initiative belongs. We also need to understand what is required from us in IT &amp; Digital Solutions so we can plan properly and ensure a healthy work environment.</p><p>That is why we are here today. We in IT &amp; Digitalisation need from you that we agree on how to continue working with your ideas until we understand why we need them and know enough to place them in the right silo.</p><p>We left the meeting with a plan that was acceptable to all. Once again, I was reminded of the importance of context understanding and to impact of providing it, even to those who didn’t know they needed it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2439fb597bb6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/the-day-i-finally-embraced-the-silos-2439fb597bb6">The day I finally embraced the silos</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Visual Thinking and Improv Shaped My Path]]></title>
            <link>https://code.likeagirl.io/how-visual-thinking-and-improv-shaped-my-path-65798d96a4fc?source=rss-ac34961b5b9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/65798d96a4fc</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[improv]]></category>
            <category><![CDATA[visualization]]></category>
            <dc:creator><![CDATA[Line Karkov]]></dc:creator>
            <pubDate>Tue, 10 Jun 2025 12:44:53 GMT</pubDate>
            <atom:updated>2025-06-10T12:44:53.937Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>How Leaving My Comfort Zone Sparked New Confidence and Creativity</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*bqWw5CTHcdY4zUvru1YcOg.png" /><figcaption>Image by author</figcaption></figure><p>As a business analyst, I have spent the past 18 years defining problems and opportunities and how to solve them with IT. I gather and consolidate information about the current situation and visions for the future from different types of stakeholders and sources. I use this information to create proposals for management, describe problems and solutions using not only text but also various diagrams. Sometimes I write about it on Medium.</p><p>Recently, I contacted a writing coach. I had sent a draft of a story to him to get some help in understanding what makes a good and engaging Medium story. When the reply arrived in my inbox, I looked at it a couple of times a day for four days before I finally opened it and read it.</p><p>If it was that difficult, why did I reach out to a writing coach in the first place? And what made me open that email after all?</p><p>To answer these two questions, I first need to go back to my journey with visual thinking and improv. On this journey, I found the motivation, courage and collaboration skills that were key to finding those answers.</p><h3>What I Learned From Visual Thinking</h3><p>About eight years ago, I started taking visual thinking seriously and bought the book <em>UZMO — Thinking with your pen</em> by Martin Haussmann. I had often used visualizations, as they were part of the standards for business analysis I had worked with. However, I felt that the standard formats were quite abstract and difficult for those outside of the IT organization to understand.</p><p>One day, I was searching for round post-it notes, and landed on a website that sold Haussmann’s books. I read about visual thinking as a method for thinking in pictures and drawing them to make knowledge visible. This was the beginning of incorporating pen-and-paper visualizations into my practice as a business analyst.</p><p>At the time, I was working in an open office environment with about 30 people sitting at desks in groups of four. No one had a designated desk, and we were all supposed to remove all personal belongings at the end of the day and stow them away in a locker.</p><p>Sometimes, the information security team would patrol the office after hours to check if confidential information had been left out. They would leave a LEGO mini-figure thief if they found any, as a hint to the risk of confidential information being stolen. This was not an office environment designed for storing knowledge on paper.</p><p>Working with software development and implementation, the team I worked with tended to favour digital tools over analogue tools because they were considered more efficient. After all, providing others with digital tools was what we did.</p><p>Sitting in an open office space, working with pen and paper to create a third draft of an IT platform strategy, was seriously out of my comfort zone. I could not help but wonder if team members looked at this thinking, “What a waste of time!” I would not think that about a developer who was struggling with a piece of code and had to rewrite it several times to get it to work.</p><p>I learned to be courageous. What surprised me the most about this was how much courage it took.</p><p>I learned to make space for reflection. Having to practice how to draw things and not being able to copy and paste from one context to the other, or from other people’s work, forced me to slow down. This gave me space to reflect. I realized that it gave me a better understanding of the problems we were trying to solve and allowed me to think them through. The time I had previously spent on redoing things, I now spent reflecting. Every detail of that IT platform strategy was carefully considered. The actions the verbs were intended to reflect, the roles the nouns represented and the meaning of colours, icons and metaphors. I could present it with confidence to an audience because I could account for every line and letter.</p><h3>What I learned from improvisation comedy</h3><p>The courage I had found when working with visual thinking was needed when I joined a class in improvisational comedy right after the lockdown. For 16 weeks, every Monday evening, I would go to practice improv, much like one would practice chess or badminton.</p><p>Most of the other students spent their days in an office like mine; one was a teacher, and another was an MMA fighter. The teacher was a professional actress and a real improv nerd. Together, we explored how improv is a form of theatre where nothing is scripted but developed on stage by the players based on predefined rules or principles.</p><p>I learned to say “Yes, and..” and to trust that no matter what I did in a scene my fellow players would also say “Yes, and…”. This basically means that whatever comes up in a scene is acceptable, and the scene develops from there.</p><p>I once played a scene that my fellow player opened in New Zealand. I had never been to New Zealand; how can I make a story about that? I had, however, been on an all-inclusive resort in Mallorca. So, we were in an all-inclusive resort in New Zealand. Improv required me to listen and to let go of whatever did not serve the scene.</p><p>I learned that I did not know my voice through working with the concept of status. A player in a scene can play low or high status, and it is the tensions and shifts between the two that help make a scene interesting. We did an exercise with status, and the feedback I got from the teacher was: “You naturally play high status”. I was surprised, and I had never thought of myself that way. At the time, I had a manager who spent much of his time engaging in power struggles over budget and head count and fighting the CIO’s plans for a cultural shift that would limit his power. Was I getting this feedback from my improv teacher because I was mirroring this kind of behaviour?</p><h3>Then I opened the e-mail</h3><p>After having written several stories on Medium, I started to consider the direction the writing was taking. Some stories were relatively well-read; others were not.</p><p>But what made the difference?</p><p>How could I use writing in my search for an authentic voice that advocates collaboration and innovation?</p><p>Could writing provide a way to create new space for reflection?</p><p>These were some of the questions I was searching for answers to. Not knowing anyone else who writes on Medium, I had no one to share knowledge with. I wondered what I could learn from someone with greater ambition than myself. That is why I sent the draft of a story to a writing coach.</p><p>It felt a bit like how I imagine skydiving must feel. Out of my comfort zone, though I had prepared well.</p><p>When I did open the e-mail, it was because I trusted that he would play “Yes, and…” And guess what? He did.</p><p>My skydive was rewarded with a new perspective on my writing. Among other things, I was advised to include more personal anecdotes and reflections based on my own experiences. And so, that is what I am attempting to do with this story.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65798d96a4fc" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/how-visual-thinking-and-improv-shaped-my-path-65798d96a4fc">How Visual Thinking and Improv Shaped My Path</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>