<?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 Clara Schindler on Medium]]></title>
        <description><![CDATA[Stories by Clara Schindler on Medium]]></description>
        <link>https://medium.com/@claraschindler?source=rss-d33575afcef2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OutXtflSX0u8_ffFhwQPrQ@2x.jpeg</url>
            <title>Stories by Clara Schindler on Medium</title>
            <link>https://medium.com/@claraschindler?source=rss-d33575afcef2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:49:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@claraschindler/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[Capturing the ephemeral: Akiko Nakayama and Margaret Watts Hughes’s sound landscapes]]></title>
            <link>https://medium.com/@claraschindler/capturing-the-ephemeral-akiko-nakayama-and-margaret-watts-hughess-sound-landscapes-5977d35388f3?source=rss-d33575afcef2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5977d35388f3</guid>
            <dc:creator><![CDATA[Clara Schindler]]></dc:creator>
            <pubDate>Sat, 25 Jan 2025 17:21:00 GMT</pubDate>
            <atom:updated>2025-01-25T17:21:00.055Z</atom:updated>
            <content:encoded><![CDATA[<p>I always found the sight of milk blending into black coffee or tea to be mesmerising; it’s one of those sights that reminds you can find life and breath in the strangest of places if you just notice. The sight is also a reminder of the ephemerality of life, as the patterns form and disolve in seconds before your eyes. Yesterday, I went to a concert where I was taken by surprise by a very special embodiment of this idea: I discovered Akiko Nakayama, performing together with Floating Points’s experimental electric sounds. Akiko works standing at a table where she sprays and pours oils and paint into a shallow container with water. A camera is placed on top of the container, with the live composition (or “alive painting”, as Akiko calls them) unfolding before the eyes of the spectators on a big screen behind her. She injects the oil into the mix at the rythm of the music, sometimes spinning the water container or letting it pulsate to the beat of the music. The result is a wondrous organic, oozing, at times alien landscape.</p><figure><img alt="Floating Points concert with Akiko Nakayama" src="https://cdn-images-1.medium.com/max/1024/1*A-pNykxCezmCpOE8TOQh4Q.png" /><figcaption>Floating Points concert with Akiko Nakayama</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_xEPLv0hpVEYvctOPv60Sw.png" /><figcaption><a href="https://www.akikopainting.com/photos">https://www.akikopainting.com/photos</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9k6p4C-269fLS1H3a7FdZA.png" /><figcaption><a href="https://www.akikopainting.com/photos">https://www.akikopainting.com/photos</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6X3CohQOXjQMeTafvMt3IA.png" /><figcaption><a href="https://www.akikopainting.com/photos">https://www.akikopainting.com/photos</a></figcaption></figure><p>Unlike dry paintings which aim to crystalise, Akiko’s art is touching precisely because it celebrates the passing moments</p><blockquote><em>through the use of colors and fluidity, and attempts to celebrate the moments of beauty amidst the ephemerality of life.<br></em><a href="https://www.akikopainting.com/statement"><em>https://www.akikopainting.com/statement</em></a></blockquote><p>Akiko is not the first to have experimented with sound landscapes — 140 years ago, Margaret Watts Hughes, a Welsh singer, invented a device which allowed her to test the strength of her voice, and she became the first woman to present a scientific instrument of her own invention at the Royal Society. This device, called <em>eidophone</em>, from the Greek <em>eidō</em> (“to see”) and <em>phōnḗ</em> (“voice, sound”), resembled a sort of megaphone. She started with placing powder on a flat surface and singing into the <em>eidophone,</em> to see how far her voice could displace the seeds.</p><p>But magic happened when instead she experimented with a small amount of wet color paste and placed a glass plate on top of it. As she sang into the <em>eidophone</em>, **the glass plate moved in geometrical shapes and in different directions depending on the pitch and tone of her voice. The results — geometrical shapes forming eery, desolate but beautiful worlds — make you wonder about the secret garden we all hold within us simply by virtue of using our vocal chords. Sound comes into existence then immediately dies, and even if you record it, the moment in which it filled space for the first time will never exist again. But Margaret Watts Hughes’ sound landscapes, just like Akiko Nakayama’s alive paintings, fill us with wonder about the beauty of passing things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0UJyNSD_5e47XHmMJZLQAA.png" /><figcaption>Margaret Watts Hughes and her eidophone. (<em>St. Louis Post Dispatch</em>, 1908.)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gHqZ43KXfzZJTDyG9GXJig.png" /><figcaption><a href="https://www.themarginalian.org/2024/08/08/margaret-watts-hughes-voice-figures/">https://www.themarginalian.org/2024/08/08/margaret-watts-hughes-voice-figures/</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z9g4izpPhuX5Ue3pT3JoHg.png" /><figcaption><a href="https://www.themarginalian.org/2024/08/08/margaret-watts-hughes-voice-figures/">https://www.themarginalian.org/2024/08/08/margaret-watts-hughes-voice-figures/</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8MBclCH-2U-JxpOERO_GjQ.png" /><figcaption><a href="https://www.themarginalian.org/2024/08/08/margaret-watts-hughes-voice-figures/">https://www.themarginalian.org/2024/08/08/margaret-watts-hughes-voice-figures/</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5977d35388f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a good definition, and why should you care?]]></title>
            <link>https://medium.com/design-bootcamp/what-is-a-good-definition-and-why-should-you-care-f788552fbbcd?source=rss-d33575afcef2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f788552fbbcd</guid>
            <category><![CDATA[business-decision-making]]></category>
            <category><![CDATA[definition]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Clara Schindler]]></dc:creator>
            <pubDate>Sun, 28 Aug 2022 16:20:12 GMT</pubDate>
            <atom:updated>2022-08-30T05:59:57.120Z</atom:updated>
            <content:encoded><![CDATA[<p>In my <a href="https://medium.com/pleo/thinking-by-writing-learnings-from-philosophy-to-product-65b936080d4d">previous post</a>, I talked about some of the handy lessons that my philosophy degree taught me that I still use to this day in the business world. Another thing that my background in philosophy gave me is a sensibility and an attention to <em>definitions</em>, and in particular the power of <em>good definitions</em>. I’ve witnessed two cases recently in my company where the lack of a good definition grabbed my attention, which resulted in the reflections shared in this post.</p><p>The first time I noticed the impact of the lack of a good definition in a business context was at a company meeting where a colleague was presenting the work they do at Design Operations to product managers and engineers. In their presentation, they mentioned the use of design tokens and components. From my limited understanding (I also heard about tokens and components for the first time during this session), components are reusable “blocks” that designers use to facilitate easier development, so that the main elements and functionality of for example a website remain consistent. Tokens are used to make sure the interface of the product has the same look and feel everywhere. But in their presentation, the designer didn’t initially explain this, so someone from the audience asked them to define what tokens and components are. My colleague went on to define these two concepts by giving specific <em>examples</em> of them: “components are things like date-pickers, buttons, modals, and other functional elements of an interface” and “tokens are things like fonts, colors, sizes, spaces”. Unfortunately this didn’t seem to answer the question for the person who asked. Then another colleague jumped in, this time with an analogy. This colleague said: “Imagine a Lego brick. The brick itself is the component, whereas the colour, shape and size of the brick are all tokens.” The effect of this definition by analogy was immediate. Everyone, myself included, gained an understanding of what design tokens and components are with this simple yet powerful image. This phenomenon really spiked my curiosity; it seemed this second definition came closer to explaining what the <em>essence</em> of a component and of a token is, which is why it was so effective.</p><p>The second time I realised the power of definitions in a business setting was when I was hosting a worksop about a feature with the french commercial team of my company. The goal of the meeting was to deep dive into the functionalities of this feature and to enable the team to sell it to customers. If you’re curious, the feature is called <a href="https://blog.pleo.io/en/pocket-per-diem">Pocket</a>. The feature is powerful and can do a lot of things, but that means that there is a lot of associated lingo that comes with it (“pocket expense”, “manual reimbursement”, “direct reimbursement”, “personal expense” are a few examples). It’s easy to get mixed up. In fact, that is precisely the reason I organised this workshop. I sensed that the members of the french team were using all these words, but not with the same meaning. I believed we were having entire conversations where we were misaligned because we were talking past each other. I thought this might be getting in the way of them selling the feature properly and with full confidence. To address this, the first thing I did in the workshop was to ask everyone in the room to grab some post-its, and give their own definition of the different Pocket vocabulary, one post-it per word. After everyone was finished, I collected the post-its and read the definitions out-loud. My suspicions were correct: for each of the concepts surrounding the Pocket feature, there were at least 4 different definitions! This of course grabbed everyone’s attention, and we spent a few minutes discussing and aligning on what each word or expression meant. It was a great way to start the meeting, and probably the whole workshop would not have been effective if we hadn’t taken the time to sort this out.</p><p>So why should you care about all this?As the example above shows, good definitions are handy not just in philosophy but also in business. The lack of a shared definition often leads to misalignment and confusion, without people realising that the culprit of the misalignment is the missing common understanding of a key concept. People are talking past each other without even realising it. The worst part is that this can lead to grave and irreversible consequences if people then make important business decisions based on concepts the meaning of which they haven’t agreed on. Making a decision without a clear definition of some important concepts is akin to making a decision without some key information — which is similar to making a somewhat blind decision.</p><p>Therefore, in order to be a better communicator and to make sound business decisions, it’s important to distinguish between a mediocre definition and a good one. In my opinion, Plato’s dialogues are a great place to learn how to make this distinction. Socrates, the main character in most of Plato’s dialogues, cared deeply about definitions. Socrates argued that giving examples of the concept you are trying to define is not a good way to go about definitions. Think of the above attempt to define a “token” with examples of tokens. The problem is, there must be <em>something</em> they all have in common, which is why they are all called tokens. A good definition of a concept should identify this common core or essence. This is why the analogy with the Lego brick was better: although not perfect, it came closer to identifying the <em>essence</em> of a design token.</p><p>At the same time, even if you are successful in identifying this common core, Socrates warned us that you can still go wrong in your attempt to define something if you give too <em>narrow</em> or too <em>broad</em> definitions. For example, defining courage as the act of fighting for your country is too narrow, because it excludes certain cases of courage, as when you take upon yourself to look after a very sick relative. On the other hand, defining courage as overcoming your fears might be too broad, because it encompasses cases that we definitely don’t want to laud as courageous, like a terrorist overcoming their fear of dying when attaching themselves to a ticking bomb in an attack.</p><p>As you can imagine, the goal of giving a Socratic definition is notoriously difficult to achieve. Even Socrates himself fails to give perfect definitions of things most of the time: the dialogue called <em>The Meno</em> starts as an inquiry into what virtue is, but that is never found. <em>The Republic</em> starts as an inquiry into what justice is, and that definition is also never reached. But in my opinion, the whole point of trying to give a Socratic definition is that you are made aware of <em>where you fall short in your knowledge</em>, and in the process you learn more about the concept, and about yourself, then if you hadn&#39;t inquired at all. For example, in <em>the Meno</em>, while Socrates and Meno are trying to give a definition of virtue, they stumble upon a discussion on how in spite of people’s constant talk of virtue, most of them value things like wealth and power more than wisdom and justice. So the practice of giving a Socratic definition (or attempting to) makes you discover more things and learn about your own shortcomings. You become wiser and more humble as a result of it — a combination I’m sure any business would benefit from!</p><p>Sometimes, breaking down a concept and taking the time to define it can even give you a clue to the answer of a gnarly question. Back when I was at university, when I was feeling stuck with a difficult philosophical question, the act of breaking down the key elements of the question often gave me a clue on how to answer it. Let’s see if we can apply this technique to a gnarly business question. Take the question <strong>What is our pricing strategy?</strong> Taking the time to define seemingly obvious concepts like “strategy” and “pricing” can actually help us think and give us a clue to the answer. First, <strong>strategy</strong>: how you differentiate yourself from your competitors to win. Then, <strong>pricing</strong>: the act of monetising your product to reflect the value customers get from it. Just by peeling this question and defining its key words, you now have new concepts to work with that can actually help you answer the question: who are our competitors? How is our value proposition different from theirs? How can we reflect this difference in our pricing? These further questions can then help you formulate the unique way in which your business will monetise its product in order to win against its competitors.</p><p>As for most things, I think that you get better at giving and spotting good definitions by practising. Here are a few things I try to remember to do as often as I can:</p><ol><li>Take the time to stop and make sure everyone is talking about the same thing. A simple question like: “Before we continue, I just would like to make sure we’re talking about the same thing here. When you say “x”, do you mean “y?”; can often reveal where the misalignment lies.</li><li>Don’t take stuff for granted and assume that seemingly obvious concepts don’t deserve the time and effort required for a definition. You won’t lose anything by taking a moment to break down the concept, but you might lose a lot by omitting to do it.</li><li>Use analogies and metaphors to help define concepts. Good analogies like the Lego one above are hard to come up with but even a mediocre one is often insightful. Examples are great to illustrate and prove your point in an argument, but they are often not helpful in a definition.</li><li>Read Plato! You’ll become a better communicator for it and learn from the very best on how to catch vague definitions and spot misalignment. I recommend starting with <em>The Meno</em>.</li></ol><p>Like Socrates, I care a lot about good definitions. I like learning about new things thanks to them, and I like using them as a tool to talk to other people. My hope is that by now you care about them too :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f788552fbbcd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/what-is-a-good-definition-and-why-should-you-care-f788552fbbcd">What is a good definition, and why should you care?</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thinking by writing: lessons from philosophy to product]]></title>
            <link>https://eng.pleo.io/thinking-by-writing-learnings-from-philosophy-to-product-65b936080d4d?source=rss-d33575afcef2------2</link>
            <guid isPermaLink="false">https://medium.com/p/65b936080d4d</guid>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[writing-tips]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Clara Schindler]]></dc:creator>
            <pubDate>Mon, 18 Apr 2022 09:02:59 GMT</pubDate>
            <atom:updated>2022-08-26T07:54:20.933Z</atom:updated>
            <content:encoded><![CDATA[<p>About 10 months ago, I graduated from university with a Philosophy degree. Two months later, I started my first job as an associate product manager at Pleo. I knew it was going to be a completely new undertaking and that I was going to learn a lot from scratch in this new role, but I was also curious to find out if I would be able to transfer any of the skills I picked up while I was studying philosophy to my job in product. Eight months down the line, I reflected on how my background in philosophy has helped me think by writing as a PM.</p><h4>Why is writing an important skill in product management?</h4><p>One thing that has (pleasantly) surprised me about the product management craft is how much writing is involved in the job. Product managers write <em>a lot</em> of documents: vision and strategy documents, memos, (fake) press releases, pre-reads for meetings, documentation on lessons learned, sales and CX-enabling docs, and the list goes on.</p><p>But aside from the sheer amount of time spent writing and volume of documents written by product managers, which by itself is reason enough to want to perfect your writing skills as a PM, I’d argue that the more important reason why PMs should care about writing well is because great PMs are great communicators, and writing is an essential part of effective communication. The reason why PMs write so many documents in the first place is to ensure communication with stakeholders and to drive alignment within the company. I would go as far as to say that without convincing and clear writing, PMs are blocked from going forward with their ideas, no matter how good those ideas are.</p><p>Finally, writing helps to sharpen thought. So many times, I have sat down to write a document or an essay on something I thought I understood reasonably well, only to find out that I couldn’t get my thoughts onto the paper in any intelligible form. That’s because writing exposes any inconsistencies in thought, and forces you to sharpen your arguments, whereas unwritten thought is volatile and it’s easy to fall into the trap of thinking you’ve got something straight if you’ve never attempted to write about it. Kurt Vonnegut said something true:</p><blockquote><em>If you can’t write clearly, you probably don’t think nearly as well as you think you do</em>.</blockquote><h4>Method and lessons from philosophy</h4><p>The course that I studied in university was part of a branch of philosophy called <em>analytic philosophy</em>, which puts a very heavy emphasis on logical connections and valid arguments. It taught me a very solid method for writing philosophical arguments. After 3 years of writing philosophical essays, I have brought some writing principles and methodologies with me, which I think are applicable to product writing:</p><ul><li><em>Always start with the problem</em>. Before the writing process even begins, it is essential to understand what the question is, by defining it and analysing it. Both philosophers and PMs are great at breaking down a problem before offering a solution to it. In your writing you should always have a clear definition of what the problem is, and an explanation for why it’s worth solving (what’s at stake here?).</li><li><em>The introduction is key.</em> To make your writing compelling right from the start, make a brief summary of the problem you are going to provide a solution to and indicate the scope of your answer (what do your arguments prove, and what do they not prove?). Then you state clearly what your answer to the question is going to be and how you’re going to defend it.</li><li><em>Structure is not everything, but it goes a long way</em>. Structure your arguments: use logical connectors, make sure the things you are saying follow from one another. Structure alone is not everything; of course the content has to to be valuable; but having a clear structure makes driving your points home much easier, because it’s so simple for your reader to follow along with you.</li></ul><h4>Things I’m currently doing to improve my writing</h4><p>There are countless ways to improve one’s writing: you can focus on obtaining more vocabulary, you can study logic to help form better arguments, you can read more to get exposure to different writing styles. I also like to read what I’ve written out loud to spot any redundancies or unnecessarily wordy bits. At the moment, I am focusing on three things to become a better writer.</p><p><em>Treating my writing like a product</em>. I firmly believe a piece of writing, be it philosophical or business related, is not supposed to be something fixed, that you write once and never come back to again. I believe that when someone takes the time to write about something, they are always contributing to a larger conversation. A philosophy paper or book about free will, for example, is part of a larger philosophical debate on determinism. Writing a strategy memo in business is an attempt to formulate a thesis on how to move the business forward, and as such it should be the basis for debate and conversation in the company, because that is how you make progress. Written documents should be shared, criticised, tweaked and improved until they are no longer useful. If you write something that is read once and then never engaged with again, <em>that is a bad piece of writing</em>. This is why I have started to treat my writing as a product: I try to work in incremental and frequent releases by sharing what I write with members of my intended audience even before I am confident with what I have written, and I try to never think of a piece of writing as “finished”.</p><p><em>Starting is always the hardest part</em>. Writing can sometimes be a painful process, for two reasons: first, it exposes inconsistencies in thought, which then forces one to take the energy and effort needed to sharpen thought. Second, writing something down is a lot more tangible and in many ways more binding than just speaking about it, as people can always hold you accountable for your thinking further down the line by referring back to what you wrote. The more you are aware of these two facts, the harder it is to actually start writing something. I often find myself pushing back the moment of writing, but once I write the first few words or sketch out a plan, things begin to flow a bit more naturally.</p><p><em>Weaving in a story in my narrative</em>. I want to learn how to appeal to emotions and weave a narrative in my writing. My background in analytic philosophy encouraged me to develop a very to-the-point style of writing, with an onus on valid arguments and logical thinking. But one big limitation of analytic philosophy is that logic and reason are considered the <em>only</em> tools; and it fails to recognise that people are often driven by emotion more than logic.</p><blockquote><em>If you are good at </em>building a logical argument<em> in your writing, you have your reader convinced by the end of your document, because you are spelling out how one points follows from the other, and they just </em><strong><em>have to</em></strong><em> agree with you. However, if you can also </em>tell a compelling story<em>, your reader will connect the dots by themselves, and they will </em><strong><em>want to</em></strong><em> agree with you.</em></blockquote><p>For example, <a href="https://www.bringthedonuts.com/essays/please-make-yourself-uncomfortable.html">in this article</a>, Ken Norton wants to convince his reader that to be a good PM, you have to embrace uncertainty and get used to being uncomfortable. He has many good arguments for why this is true. However, notice how he starts his article by telling the story of jazz musician Ella Fitzgerald, and describes how at one concert she was met with wild applause from the audience when she improvised a song after forgetting the original lyrics to it — an obviously uncertain and uncomfortable situation from which Ella rose successful. When you understand the point of the story, it’s so easy to connect the dots and understand why Ken Norton’s main thesis is true; he almost doesn’t have to argue anymore- that’s the power of storytelling.</p><p><em>Thanks for reading, and stay tuned for more pieces on philosophy, product and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65b936080d4d" width="1" height="1" alt=""><hr><p><a href="https://eng.pleo.io/thinking-by-writing-learnings-from-philosophy-to-product-65b936080d4d">Thinking by writing: lessons from philosophy to product</a> was originally published in <a href="https://eng.pleo.io/">Pleo Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>