<?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 JP Carrascal on Medium]]></title>
        <description><![CDATA[Stories by JP Carrascal on Medium]]></description>
        <link>https://medium.com/@jpcarrascal?source=rss-c8796193accf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tSkZmjt-lDHapfzxWC_nog.jpeg</url>
            <title>Stories by JP Carrascal on Medium</title>
            <link>https://medium.com/@jpcarrascal?source=rss-c8796193accf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:14:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jpcarrascal/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[My first foray into astrophotography]]></title>
            <link>https://jpcarrascal.medium.com/my-first-foray-into-astrophotography-c20443989207?source=rss-c8796193accf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c20443989207</guid>
            <category><![CDATA[catalunya]]></category>
            <category><![CDATA[spain]]></category>
            <category><![CDATA[astrophotography]]></category>
            <category><![CDATA[photography]]></category>
            <category><![CDATA[photo-essay]]></category>
            <dc:creator><![CDATA[JP Carrascal]]></dc:creator>
            <pubDate>Mon, 24 Jul 2023 11:04:35 GMT</pubDate>
            <atom:updated>2023-07-24T11:04:35.405Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ryp_hIFA2K3SWKNPkWJVBQ.jpeg" /></figure><p>This summer I went camping with my partner to a lovely campground called <a href="https://terradelcongost.com/">Terra del Congost</a>, located in the beautiful Montsec mountain range, which crosses from Catalunya to Aragón. The Montsec is known as a the best place in the area for watching the night sky because of its low light pollution. It even features an “<a href="https://www.parcastronomic.cat/?lang=en">Astronomic Park</a>”.</p><p>We arrived, had lunch and set the tent. After spending the afternoon and early evening exploring the campground and its surroundings, we sat on a couple of flat rocks to drink <a href="https://en.wikipedia.org/wiki/Ratafia">ratafía</a> and to enjoy the last glimpse of daylight. We expected the evening to be quiet, but were surprised by the constant, piercing buzz of the cicadas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DCiBfbhkKscIUgFodGCvRw.jpeg" /><figcaption>Exoskeleton of a noisy cicada.</figcaption></figure><p>At about 10pm, after a long summer dusk, the darkness finally seemed to soothe the restless insects, convincing them to go to sleep along with most of the camping visitors.</p><p>I set up my camera (a Sony A7III with the new Viltrox 18mm f/1.8 prime) and tripod, capturing a few test shots to find the best settings. The first few tests showed more stars than those visible with the naked eye, even with not-so-long exposure time (15 seconds in the example below).</p><p>However, even at 11pm, the dim light of the sun was still getting amplified by the long exposure time, preventing me from getting the bright-stars-over-black-sky look I wanted. I was also increasingly worried about the cloud front that threatened to cover a big part of the sky during the rest of the night.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TVVwkq61InNmz8lQ3je1gg.jpeg" /><figcaption>Test shot: Sony A7III, Viltrox 18mm f/18, ISO1600, 15 seconds, f/1.8</figcaption></figure><p>I was lucky and the clouds quickly vanished. The images got progressively darker, revealing more layers of stars with every shot, as I enjoyed the warm summer breeze of the Montsec and hated the almost nonstop mosquito bites. A few more tests later, I increased the exposure time to 30 and settled to ISO 2500 and an aperture of f/1.8.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ISt4ocuL-ZwY2tR6TEODw.jpeg" /><figcaption>Sony A7III, Viltrox 18mm f/18, ISO 2500, 30 seconds, f/1.8</figcaption></figure><p>I always thought getting the dramatic view of the night sky that I’ve seen in other people’s photos would be more difficult to obtain from a technical standpoint. However, the fast wide lens and the settings I used made it easy to capture well defined stars and to reveal the cloudy smear of the milky way. Not much tweaking was necessary, not even a much post-processing.</p><p>Even focusing was quite easy. I followed advice from <a href="https://medium.com/@nikkehmiller/astrophotography-for-beginners-fdf813de8087">this article</a> and set the camera to manual, then made sure a reference star or planet (I think it was Venus, in my case) was in focus. After that, I think I didn’t move the focus ring for the rest of the night.</p><p>In contrast, it was way harder to get the right framing, as all you see on the camera’s visor or screen when composing the shot is a few of the brightest stars. It is not easy to predict what you will get in the final image!</p><p>It didn’t help that I was using a small GorillaPod tripod instead of a normal-sized one; the camera was always close to the ground, so I found myself kneeling to see the small screen while shooing the stubborn mosquitos away.</p><p>It took me a lot of crooked and blurry shots, but I love the few ones I nailed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nm0Xe6ZXVGX6Y26FwBIDNQ.jpeg" /><figcaption>Sony A7III, Viltrox 18mm f/18, ISO2500, 30seconds, f/1.8</figcaption></figure><p>I don’t like the airplane trail in the one below, but I appreciate the well-defined view of the Ursa Major, near the middle of the frame.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQ_bziFUE0t8iGh9MPiSFg.jpeg" /><figcaption>Sony A7III, Viltrox 18mm f/18, ISO2500, 30seconds, f/1.8</figcaption></figure><p>In the end, I was happy with the result. I took 60+ long-exposure photos, of which there were about 5–6 that I really liked. I think 10% is not a bad success rate.</p><p>From capturing these images I learned first hand that astrophotography is not so much about having the right equipment (although a fast lens and a large sensor help), but about finding the right location away from light pollution, and having a lot of patience.</p><p>Most important, experiencing a quiet place so far away from urban centers is worth the trip.</p><p>I just need to remember to bring bug repellent next time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c20443989207" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you’ll love GitHub Copilot X as a creative coder]]></title>
            <link>https://jpcarrascal.medium.com/why-youll-love-github-copilot-x-as-a-creative-coder-7d28706186d0?source=rss-c8796193accf------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d28706186d0</guid>
            <category><![CDATA[creative-coding]]></category>
            <category><![CDATA[interactive-systems]]></category>
            <category><![CDATA[music-technology]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-assisted-coding]]></category>
            <dc:creator><![CDATA[JP Carrascal]]></dc:creator>
            <pubDate>Tue, 23 May 2023 17:50:46 GMT</pubDate>
            <atom:updated>2023-06-06T06:41:01.348Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ieO5o6Rn5IJhhXhsWhm26w.jpeg" /><figcaption>Doing “creative stuff”</figcaption></figure><p>If you don’t write software for a living but you enjoy piecing together bits of code to create beautiful art pieces or interactive experiences, you are a “creative coder”.</p><p>I consider myself a creative coder as well. I create hardware and software controllers for music, as collaborative applications, interactive art, etc., and to do so, I use whatever programming language is better suited for each piece. This means I have experience with a variety of languages, from Web (JavaScript, HTML, CSS) to microcontrollers (Arduino/C++, Python), but I am not an expert in any of them. The code I write is far from being ready for deployment to users at scale, in production scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PA8Fr3fih2Ti95NqcqIJ_g.jpeg" /><figcaption>Typical messy creative coding environment.</figcaption></figure><h3><strong>Getting into The Zone</strong></h3><p>The frequent switch of context and the lack of daily practice keeps me out of shape with all of those languages. When I want to build a new thing, I may have a clear idea of what I want to make, but I need to check tutorials, Stackoverflow or even my own old code to get started.</p><p>Usually getting initial “boilerplate” code is the most frustrating part of building something. From that point on, I get in “<a href="https://en.wikipedia.org/wiki/Flow_(psychology)">the zone</a>” and things flow in a much quick and pleasant way.</p><p>Let me give you an example.</p><h3>Just a simple MIDI light</h3><p>I fiddle around a lot with Web, <a href="https://en.wikipedia.org/wiki/MIDI">MIDI</a>, and <a href="https://www.adafruit.com/category/168">RGB LED</a>s. I’ve built a couple of projects on top of these technologies. A couple of days ago, I wanted to start a new proof-of-concept that required a LED ring that responded to MIDI controls coming from a Web-based dashboard. I had already written and tested the code for the hardware. All I needed was to put together the dashboard app.</p><p>I knew I needed to incorporate some Web MIDI code into a web application, a Web form, and some glue code to put it all together. But I don’t know the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Web_MIDI_API">Web MIDI API</a> by heart, so I knew I would have to google related examples, check the docs, and probably pay a couple of visits to Stack Overflow when debugging my code. I also needed to write the basic HTML code to contain the app and the HTML form. Because of my lack of expertise, that was going to take me at least 1–2 hours of boring work.</p><h3>Enter the Copilot</h3><p>Just as I opened my editor to start typing code, I remembered I have access to the <a href="https://github.blog/2023-03-22-github-copilot-x-the-ai-powered-developer-experience/">GitHub Copilot X</a> (full disclosure: I work for Microsoft, so we get to play with cool software before it is released).</p><p>Copilot X is a chat-like assistant within the Visual Studio Code editor. GitHub promotes it as an “<em>AI pair programmer</em>”, and you can ask it to write code for you, to answer technical questions, to create unit tests, etc.</p><p>So I opened the Copilot X chat and typed the following prompt:</p><blockquote>Create a simple web app that does the following:<br>- It lists the available MIDI output devices in the system in a dropdown<br>- It lets you select one device from the list as the default output<br>- It uses two buttons to send MIDI controller number 110 to the default output. One button sends value 0 and the other value 127</blockquote><p>Here’s the code it produced for me:</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br>  &lt;head&gt;<br>    &lt;meta charset=&quot;UTF-8&quot;&gt;<br>    &lt;title&gt;MIDI Output Selector&lt;/title&gt;<br>  &lt;/head&gt;<br>  &lt;body&gt;<br>    &lt;h1&gt;MIDI Output Selector&lt;/h1&gt;<br>    &lt;label for=&quot;midi-output&quot;&gt;Select MIDI output device:&lt;/label&gt;<br>    &lt;select id=&quot;midi-output&quot;&gt;&lt;/select&gt;<br>    &lt;br&gt;<br>    &lt;button id=&quot;cc-0&quot;&gt;Send CC 110 value 0&lt;/button&gt;<br>    &lt;button id=&quot;cc-127&quot;&gt;Send CC 110 value 127&lt;/button&gt;<br>    &lt;script&gt;<br>      // Get the MIDI output devices<br>      const midiOutputs = [];<br>      const midiOutputSelect = document.getElementById(&#39;midi-output&#39;);<br>      navigator.requestMIDIAccess().then(midiAccess =&gt; {<br>        midiOutputs.push(...midiAccess.outputs.values());<br>        // Add each MIDI output device to the dropdown<br>        midiOutputs.forEach(output =&gt; {<br>          const option = document.createElement(&#39;option&#39;);<br>          option.value = output.id;<br>          option.text = output.name;<br>          midiOutputSelect.add(option);<br>        });<br>      }, () =&gt; {<br>        console.log(&#39;Could not access your MIDI devices.&#39;);<br>      });<br><br>      // Send MIDI controller number 110 to the default output with the specified value<br>      function sendCC(value) {<br>        const outputId = midiOutputSelect.value;<br>        const output = midiOutputs.find(output =&gt; output.id === outputId);<br>        if (output) {<br>          output.send([0xB0, 0x6E, value]);<br>        }<br>      }<br><br>      // Add event listeners to the buttons<br>      const offButton = document.getElementById(&#39;cc-0&#39;);<br>      const onButton = document.getElementById(&#39;cc-127&#39;);<br>      offButton.addEventListener(&#39;click&#39;, () =&gt; {<br>        sendCC(0);<br>      });<br>      onButton.addEventListener(&#39;click&#39;, () =&gt; {<br>        sendCC(127);<br>      });<br>    &lt;/script&gt;<br>  &lt;/body&gt;<br>&lt;/html&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IXvYR3qM7-Z1WNu2JSM6yQ.png" /><figcaption>The resulting app. It doesn’t look like much, but it saved me a bunch of time.</figcaption></figure><p>It worked perfectly, right away, with no modifications! My jaw dropped as my LED ring turned on and off in response to clicking the buttons.</p><p>Thanks to that initial code, I didn’t have to go and check the API to remember how to check whether MIDI is available in the browser, how to list devices, hot to send data to them, etc. This is exactly what I needed, and it saved me at least an hour of non-creative, tedious work!</p><p>At that point, I started making changes to the code, adding other controls for adjusting brightness, modifying the MIDI functions to smoothly fade the light in and out, making the dashboard prettier with some CSS, etc. Because I already had all the fundamental bits in place, it was super easy to move on with the actually interesting stuff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*njND4nXRe4g8QZmO7WazWA.jpeg" /><figcaption>It works!</figcaption></figure><p>I can also see how this would be super useful for other folks with no Web MIDI API experience. As Copilot added comments, it is easy to follow what each code section does. And as the code was written according to the specs (prompt), it is easier to relate the code to the result than it would be with some sample code obtained from somewhere else.</p><h3>I’m a creative coder, too. Why should you use it?</h3><p>There is a huge debate on whether AI may be a threat to a number of jobs, including software development. However, I am not discussing professional programming here. Instead, I believe that, for creative coders, AI-assistance is going to be a positive game changer.</p><p>Even more than in other software development contexts, in creative coding, writing code is a means to an end. We deal with prototypes more often than with finished products. We need to come up with quick proofs-of-concepts to be able to build upon them, to connect disparate systems, and to create beautiful interactive experiences that stimulate not only the brain, but the heart.</p><p>Creative coders have the <em>specs</em> clear in mind, and technical details are often obstacles to that end. AI assistants like GitHub Copilot X can help bridging these obstacles, allowing non-expert programmers, creative coders and artists to focus on the fun part: turning their ideas into reality.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d28706186d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The difference between music and noise]]></title>
            <link>https://jpcarrascal.medium.com/the-difference-between-music-and-noise-9fe2ca8b4e53?source=rss-c8796193accf------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fe2ca8b4e53</guid>
            <category><![CDATA[noise]]></category>
            <category><![CDATA[music]]></category>
            <dc:creator><![CDATA[JP Carrascal]]></dc:creator>
            <pubDate>Sun, 24 Apr 2022 19:13:02 GMT</pubDate>
            <atom:updated>2022-04-24T19:13:02.709Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Original article: </em><a href="http://blog.jpcarrascal.com/2015/11/the-difference-between-music-and-noise/#more-2251"><em>http://blog.jpcarrascal.com/2015/11/the-difference-between-music-and-noise/#more-2251</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kSzrX3YmH5Xh3ffq.jpg" /></figure><p>(This post is based on <a href="https://www.quora.com/Whats-the-difference-between-music-and-noise"><strong>an answer I wrote to a question in Quora</strong></a>)</p><p>What is the difference between music and noise? There are multiple ways to answer this question.</p><p>From an aesthetics point of view, the difference is hard to tell. In fact, it could be said that there is no difference — it depends on the taste of the listener. Any sound could be considered music or noise, as long as the listener draws pleasure from the listening activity.</p><p>According to the online <a href="http://www.britannica.com/art/music"><strong>Encyclopædia Britannica</strong></a>, music is the:</p><blockquote>“art concerned with combining vocal or instrumental sounds for beauty of form or emotional expression, usually according to cultural standards of rhythm, melody, and, in most Western music, harmony.”</blockquote><p>If we are willing to accept this more strict definition, the biggest difference between music and noise is periodicity. Music tends to have repetitive structures that allow us to know, to a certain degree, what to expect. This happens at several levels. For instance, a single instrument note sounds like, let’s say, an A4 note, because it has a repetitive pattern that occurs 440 times per second. If such pattern wouldn’t exist, we would perceive it as noise.</p><p>The same happens at rhythmic level. A monkey bashing a drum kit sounds like noise because it doesn’t have a minimum degree of repetition that could be perceived as rhythm. Rhythm is by definition a repetition of a sound (or a set of sounds) at periodic intervals. Without such repetition, there is no rhythm.</p><p>An explanation of why repetition is so essential to music might be in its origin as a social activity. For a group of people to engage in such activity, i.e., for the participants to develop a connection based on sound and silence, it is necessary for them to be <em>synchronized</em>. And the best (or only) way to be synchronized is to have a certain degree of expectation of what is about to come. If a participant of a social music session is playing a single drumming sound, she needs to know <em>when</em> to hit it. If he is “in-sync” with the activity, he can predict when is the right time to do so. By having certain repetitive patterns, this can be accomplished.</p><p>All this does not mean that music should be predictable. At all the aforementioned levels (melody, rhythm), changes are introduced to avoid making the listening (and performing) experience boring. It is precisely the delicate balance between what we expect and what surprises us what makes good music so valuable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fe2ca8b4e53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Control your Meris pedal from your Zoia (via MIDI on CPort), no extra devices needed]]></title>
            <link>https://jpcarrascal.medium.com/control-your-meris-pedal-from-your-zoia-via-midi-on-cport-no-extra-devices-needed-8f473aa0eb40?source=rss-c8796193accf------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f473aa0eb40</guid>
            <category><![CDATA[music-technology]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[guitar-pedals]]></category>
            <category><![CDATA[music]]></category>
            <dc:creator><![CDATA[JP Carrascal]]></dc:creator>
            <pubDate>Sun, 24 Apr 2022 08:00:30 GMT</pubDate>
            <atom:updated>2022-04-24T11:46:06.537Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Original post: </em><a href="http://blog.jpcarrascal.com/2022/04/control-your-enzo-from-your-zoia-via-cport-no-extra-devices-needed/"><em>http://blog.jpcarrascal.com/2022/04/control-your-enzo-from-your-zoia-via-cport-no-extra-devices-needed/</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9Ti3mgT4b3zeVVgI.jpg" /></figure><p>The Empress Zoia is the brain of my pedalboard. However, I was frustrated by not being able to use it to control my Meris Enzo via MIDI, as apparently an extra device (<a href="https://www.meris.us/product/midi-i-o/"><strong>Meris MIDI I/O box</strong></a>) was needed. Meh. No way I am going to pay an extra 100 bucks for that, not to mention waste precious pedalboard space.</p><p>I started wondering if the control input in the Meris used some some proprietary protocol produced by their MIDI I/O box or just plain MIDI. I did some research and ran into the DisasterArea’s <a href="https://www.disasterareadesigns.com/shop/p/midi-box-4"><strong>MIDI Box 4 page</strong></a>. In the compatibility section, it says it supports the Enzo using a mono TS cable, and apparently the signal goes on the tip of the cable:</p><figure><img alt="Screenshot from DisasterArea’s MIDI Box 4 compatibility section explaining that Meris uses a TS connector for MIDI, with data coming in through the tip of the connector." src="https://cdn-images-1.medium.com/max/1024/0*MceQTpVO_hvtR-ox.png" /><figcaption>Screenshot from DisasterArea’s MIDI Box 4 compatibility section</figcaption></figure><p>Then I went to the Zoia <a href="http://assets.empresseffects.com/manuals/ZOIA.pdf"><strong>manual</strong></a> to see what options I had on that side. I had my Zoia’s MIDI connectors already busy controlling other stuff, so I looked into the CPort section in page 28 and found this:</p><figure><img alt="Screenshot from the Zoia manual, page 28, explaining that MIDI out is available on the ring of a TRS connector of the CPort even if the MIDI ports are being used." src="https://cdn-images-1.medium.com/max/1024/0*HY9qmc7UBxivM_J6.jpg" /><figcaption>Screenshot from the Zoia manual, page 28.</figcaption></figure><p>Interesting. It seemed that Zoia’s CPort could be used as a second MIDI output, which would come through the ring.</p><p>So a custom cable TRS cable that bridges the ring on the Zoia side to the tip on the Enzo side should work. Right? I decided to give it a try. I went and built that cable and voilà! <strong>It works!!!</strong></p><p>The cable should look like this:</p><figure><img alt="Zoia to Enzo cable. It is a TRS cable, with the ring at the Zoia end connected to the tip at the Enzo end." src="https://cdn-images-1.medium.com/max/1024/0*L8238N3DXU8QNfgG.png" /><figcaption>Zoia to Enzo cable</figcaption></figure><p>It works like a charm! Just make sure you configure your CPort for MIDI and you use the same MIDI channel in your MIDI output modules and in your Enzo. I use this cable along a Zoia patch/page I created that includes all of Enzo’s MIDI parameters. It allows me to store a preset for the Enzo along with each of Zoia’s patches. You can find the patch in Patchstorage <a href="https://patchstorage.com/meris-enzo-preset-storage-on-zoia/"><strong>here</strong></a>. And here you can see it in action:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpuFdwr6uVFk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpuFdwr6uVFk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpuFdwr6uVFk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8fec9614e5af2479fac69c9d24e0dd5c/href">https://medium.com/media/8fec9614e5af2479fac69c9d24e0dd5c/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f473aa0eb40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the Opportunity Score? (And how to calculate it) — Part II]]></title>
            <link>https://medium.com/uxr-microsoft/what-is-the-opportunity-score-and-how-to-calculate-it-part-ii-59bbadbdd2ad?source=rss-c8796193accf------2</link>
            <guid isPermaLink="false">https://medium.com/p/59bbadbdd2ad</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[research-tools]]></category>
            <category><![CDATA[gap-analysis]]></category>
            <dc:creator><![CDATA[JP Carrascal]]></dc:creator>
            <pubDate>Fri, 27 Aug 2021 02:47:16 GMT</pubDate>
            <atom:updated>2021-08-27T02:47:16.228Z</atom:updated>
            <content:encoded><![CDATA[<h3><a href="https://medium.com/uxr-microsoft/what-is-the-opportunity-score-and-how-to-obtain-it-bb81fcbf79b7?source=user_profile---------0----------------------------">What is the Opportunity Score? (And how to calculate it)</a> — Part II</h3><p>In <a href="https://medium.com/uxr-microsoft/what-is-the-opportunity-score-and-how-to-obtain-it-bb81fcbf79b7">my previous post</a> I summarized what the Opportunity Score is and provided a tool to put it into practice. The tool I proposed, <a href="https://github.com/jpcarrascal/OppScore">an R script</a>, allows to calculate the Opportunity Score and also to generate the Opportunity Landscape/Map. It is relatively simple to use, but you still need to install R to run it, and some basic R knowledge if you want to customize it.</p><p>After discussion with some of my teammates, I realized the R approach creates more trouble than it solves, and that we needed an easy-to-use tool for people interested in applying the method. So without further fanfare, here is <a href="https://jpcarrascal.github.io/OppScoreWeb/">OppScoreWeb</a>:</p><figure><img alt="OppScoreWeb screenshot" src="https://cdn-images-1.medium.com/max/1024/1*39ZsdId5zpnbnqy7Qr1wqA.png" /><figcaption>OppScoreWeb: <a href="https://jpcarrascal.github.io/OppScoreWeb/">https://jpcarrascal.github.io/OppScoreWeb/</a></figcaption></figure><p>OppScore is an open-source Web application (here’s the URL: <a href="https://jpcarrascal.github.io/OppScoreWeb/">https://jpcarrascal.github.io/OppScoreWeb/</a>) that allows you to calculate the scores, generate the map/landscape, and export the data so you can use them in your report, all from a Web browser.</p><p>When you open the tool in your browser, it will load a sample dataset. You can play around with it to see how the tool works: click on <em>Map Data</em> to generate the scores and map; the <em>Copy Scores</em> button copies the scores as a tab-separated text table to the clipboard (so you can easily paste it into Excel); and hit <em>Export landscape/map</em> to download a PNG file with the map. Start fresh by clicking the <em>Clear data</em> button.</p><p>To import your own data, you have two options:</p><ul><li>Paste your scores from a CSV or TSV file (including Excel). Make sure the data contains 3 columns, first one with Outcome labels, second with Importance values, and third with Satisfaction values. The tool will remove incomplete rows and most garbled data, but it behaves best if your data is consistent.</li><li>Import a CSV file with headers. It doesn’t matter how many columns it has, as long as it has the 3 required ones (again, Outcome, Importance and Satisfaction).</li></ul><p>This is an open-source tool (currently in beta), and here is the GitHub repository: <a href="https://github.com/jpcarrascal/OppScoreWeb">https://github.com/jpcarrascal/OppScoreWeb</a>. It uses these external packages:</p><ul><li>D3.js</li><li>Save SVG as PNG: <a href="https://github.com/exupero/saveSvgAsPng">https://github.com/exupero/saveSvgAsPng</a></li><li>CSV parser: <a href="https://github.com/d3/d3-dsv">https://github.com/d3/d3-dsv</a></li></ul><p>It might still have some bugs (thank you <a href="https://medium.com/u/364c35f86efa">Irina Smoke</a> for alpha-testing it), so do get in touch with me or file issues in GitHub if you find bugs. Questions and suggestions are also welcome.</p><p>I hope you find it useful!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59bbadbdd2ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxr-microsoft/what-is-the-opportunity-score-and-how-to-calculate-it-part-ii-59bbadbdd2ad">What is the Opportunity Score? (And how to calculate it) — Part II</a> was originally published in <a href="https://medium.com/uxr-microsoft">UXR @ Microsoft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the Opportunity Score? (And how to calculate it)]]></title>
            <link>https://medium.com/uxr-microsoft/what-is-the-opportunity-score-and-how-to-obtain-it-bb81fcbf79b7?source=rss-c8796193accf------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb81fcbf79b7</guid>
            <category><![CDATA[opportunity-score]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[market-opportunity]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[JP Carrascal]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 13:03:47 GMT</pubDate>
            <atom:updated>2021-09-24T13:38:32.312Z</atom:updated>
            <content:encoded><![CDATA[<p><em>NOTE: In this article I present an R script for calculating the Opportunity Score. In </em><a href="https://medium.com/uxr-microsoft/what-is-the-opportunity-score-and-how-to-calculate-it-part-ii-59bbadbdd2ad"><em>a follow-up article</em></a><em>, I introduce a Web app to accomplish the same in a simpler way.</em></p><p>The Opportunity Score is a tool that helps (among other things) to estimate market opportunity, to prioritize efforts in product development and to conduct competitive analysis. It is part of the <em>Opportunity-Driven Innovation</em> framework created by Anthony W. Ulwick, that aims at “making innovation predictable”. This article focuses specifically on the Opportunity Score calculation. Bear in mind it is not a silver bullet, and if you want to use properly, you should probably read a bit more on the Opportunity-Driven Innovation process to get the whole picture. To help with that, I have included a few links in the “Further Reading” section at the end of the article.</p><h3>Background</h3><p>Ulwick’s work on Opportunity-Driven Innovation (ODI) is based on the idea that customers mainly pay to get a <em>job-to-be-done</em>. This means people do not actually care about tools, features or specs, what they care about is achieving a goal (this is nicely explained by Prof. Clayton Christensen in <a href="https://www.youtube.com/watch?v=Q63PZR7mG70">this video</a>**). If a product of service helps customers to achieve the goal (to get a job done), they will pay for it. Ulwick says that deeply understanding the customers’ job-to-be-done is necessary to predict whether a product will be successful, that is, people will pay for it. The ODI framework is a systematic approach towards analyzing jobs-to-be-done to decide whether to invest on a certain design space, and how to prioritize such investment. Analyzing a job-to-be-done is usually the result of deep qualitative research with customers (e.g. interviews). BTW, according to Ulwick, jobs-to-be-done generally don’t change across time. This might be suggested by the example below.</p><p><em>**Bear in mind that Ulwick’s and Christensen’s definitions of jobs-to-be-done diverge. There is an interesting discussion on this divergence in this article: </em><a href="https://jtbd.info/know-the-two-very-different-interpretations-of-jobs-to-be-done-5a18b748bd89"><em>Know the Two — Very — Different Interpretations of Jobs to be Done | by Alan Klement | Jobs to be Done (jtbd.info)</em></a><em>. Here we focus on Ulwick’s Opportunity Score, the discussion between Ulwick’s and Christensen’s perspectives are out of the scope of this article.</em></p><h3>The Opportunity Score</h3><p>The main metric used in the ODI framework is the Opportunity Score. This is the result of an <a href="https://en.wikipedia.org/wiki/Gap_analysis">analysis of the gap</a> between the importance that customers assign to the expected outcomes of a job-to-be-done, and how satisfied they are with their current solutions.</p><p>Once a job-to-be-done has been understood, it should be broken down the into smaller job steps, and for each step, a series of <em>outcomes</em> (as expected or desired by customers) should be enunciated. For instance, a job-to-be-done could be:</p><blockquote><em>Surviving grad school.</em></blockquote><p>And the steps and outcomes of this job-to-be-done and their outcomes could be:</p><figure><img alt="List of outcomes for “Surviving grad school”" src="https://cdn-images-1.medium.com/max/625/1*WqFSIP9HKPrzyxnGTkralg.png" /><figcaption>List of outcomes for “Surviving grad school”</figcaption></figure><h3>Collecting the data</h3><p>To obtain the Opportunity Score for each outcome, you first need to collect data from your customers about the desired outcomes. You should ask customers two questions:</p><ol><li><strong>Importance:</strong> <em>When [job step], how </em><strong><em>important</em></strong><em> is it to you that you are able to [outcome]?</em> (1 to 5 scale, 1 = “Not at all important”, 5 = “Extremely important”)</li><li><strong>Satisfaction:</strong> <em>When using [solution], how </em><strong><em>satisfied</em></strong><em> are you with your ability to [outcome]?</em> (1 to 5 scale, 1 = “Not at all satisfied”, 5 = “Extremely satisfied”)</li></ol><p>Where [solution] is the solution that the customer currently uses to get the job done.</p><h3>Computing the score</h3><p>This is pretty easy:</p><ol><li>Compute the <em>percentage of respondents who answered 4 or 5</em> to both <strong>importance</strong> (that is those who said the outcome is “Important” or “Extremely important”) and <strong>satisfaction</strong> (those who said they are “Satisfied” or “Extremely satisfied”).</li><li>Insert these percentages in the Opportunity Score formula:</li></ol><blockquote><em>OpScore = Importance + max(Importance - Satisfaction, 0)</em></blockquote><p>I made up some answer values for the “surviving grad school” example:</p><figure><img alt="(Mock) values for Importance, Satisfaction and resulting Opportunity Score" src="https://cdn-images-1.medium.com/max/979/1*CfFdRhlXYx87es81BpKUDw.png" /><figcaption>(Mock) values for Importance, Satisfaction and resulting Opportunity Score</figcaption></figure><p><em>NOTE: Ulwick normalizes the percentages to 10 instead of 100. I’m not sure why, but this sometimes leads to confusion as the first impulse is to normalize the 1–5 question scale to 10 (by multiplying by 2).</em></p><h3>Interpreting the results</h3><p>To interpret the OpScore results, data is usually plotted on a graph like this one:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/0*XUXwvOUcLumehgfN.jpg" /><figcaption>The Opportunity Landscape for “surviving grad school”.</figcaption></figure><p>The graph illustrates how well customers’ needs are satisfied with current solutions. It helps to indicate prioritization strategies for improving existing products or creating new ones. The <em>Overserved</em> area suggests there is not much room for innovation and the way to compete there is mainly by offering a lower-priced solution. On the opposite side, the <em>Underserved</em> area indicates there are stronger opportunities to innovate as there are a lot of important unsatisfied needs. People will be willing to pay more to have these needs solved. The upper right corner area represents needs that are important but are currently well satisfied. Ulwick indicate that these are “table stakes” that necessarily must be be served if one considers developing a competitive product.</p><p>Another interesting application of the opportunity score is for conducting competitive analysis. Breaking down features of two competing products (which are meant to lead to expected outcomes) and comparing their opportunity scores is a good way to compare how well they satisfy a customers’ job-to-be-done.</p><p>Ulwick also suggests conducting regression and clustering analyses to discover market segments with latent opportunities. This is out of the scope of this article (see the Further Reading section below for more information).</p><h3>A word on sample sizes and other uses</h3><p>For the type of market and innovation research that his original book aims for, Ulwick recommends asking the Importance and Satisfaction questions to a sample of at least 180 participants. To reach this sample sizes, a survey is probably the best method. At the DevDiv UX Research team we sometimes adapt Ulwick’s method when conducting Concept Value Testing (CVT) during 1 to 1 sessions with customers. In those cases, the OpScore allows us to get an idea of how critical a problem or outcome is. Later on we present the features and conduct the actual CVT to assess whether the proposed solutions might help solving the problem or obtaining the desired outcome for the customer. In this kind of studies, sample sizes are usually lower (20+ participants), hence, although results can help guiding product development (e.g. for prioritizing engineering efforts), caution is needed before considering them significant.</p><h3>R script for calculating the Opportunity Score</h3><p>Here is an R script I wrote that will calculate the Opportunity Scores and generate an Opportunity map: <a href="https://github.com/jpcarrascal/OppScore">OppScore: yet another R script for calculating opportunity scores and plotting the Opportunity Map / Landscape.</a></p><h3>Further Reading</h3><ul><li>You can buy Ulwick’s original book from Amazon: <a href="https://www.amazon.com/What-Customers-Want-Outcome-Driven-Breakthrough/dp/0071408673/ref=sr_1_1?ie=UTF8&amp;qid=1542985754&amp;sr=8-1&amp;keywords=What+Customers+Want%3A+Using+Outcome-Driven+Innovation+to+Create+Breakthrough+Products+and+Services">“What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services”, by Anthony W. Ulwick.</a></li><li>Ulwick’s talk on ODI in the 2018 <a href="https://frombusinesstobuttons.com/">From Business to Buttons</a>, a Scandinavian conference on UX and Service Design. <a href="https://www.youtube.com/watch?v=2ecwXEnQ6xY">Video.</a></li><li><a href="https://jobs-to-be-done.com/">Jobs-to-be-Done + ODI</a>, a Medium blog by Ulwick. This is probably the most relevant post in that blog: <a href="https://jobs-to-be-done.com/outcome-driven-innovation-odi-is-jobs-to-be-done-theory-in-practice-2944c6ebc40e">Outcome-Driven Innovation: JTBD Theory in Practice</a></li><li>This article is a nice and short summary of the main topics in the book: <a href="https://medium.com/@AlexJupiter/outcome-driven-innovation-3377252aec15">Outcome-Driven Innovation</a></li><li>Discussion on the Ulwick’s and Christensen’s definitions of jobs-to-be-done: <a href="https://jtbd.info/know-the-two-very-different-interpretations-of-jobs-to-be-done-5a18b748bd89">Know the Two — Very — Different Interpretations of Jobs to be Done | by Alan Klement | Jobs to be Done (jtbd.info)</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb81fcbf79b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxr-microsoft/what-is-the-opportunity-score-and-how-to-obtain-it-bb81fcbf79b7">What is the Opportunity Score? (And how to calculate it)</a> was originally published in <a href="https://medium.com/uxr-microsoft">UXR @ Microsoft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>