<?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 Adrian Y Roessler on Medium]]></title>
        <description><![CDATA[Stories by Adrian Y Roessler on Medium]]></description>
        <link>https://medium.com/@adrianysan?source=rss-92335455578b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kBb6E08_TJ812EmwumwlIA.png</url>
            <title>Stories by Adrian Y Roessler on Medium</title>
            <link>https://medium.com/@adrianysan?source=rss-92335455578b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:54:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adrianysan/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[Imagine: AI technology to pioneer patient-led healthcare]]></title>
            <link>https://medium.com/leoilab/imagine-ai-technology-to-pioneer-patient-led-healthcare-40c04de1106e?source=rss-92335455578b------2</link>
            <guid isPermaLink="false">https://medium.com/p/40c04de1106e</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[smartphones]]></category>
            <category><![CDATA[health-technology]]></category>
            <dc:creator><![CDATA[Adrian Y Roessler]]></dc:creator>
            <pubDate>Thu, 13 Dec 2018 17:51:36 GMT</pubDate>
            <atom:updated>2019-03-21T12:06:24.458Z</atom:updated>
            <content:encoded><![CDATA[<h3>AI technology to pioneer patient-led healthcare</h3><p><strong>As the number of patients in need of specialist care rises, the skin tracking app Imagine seeks to empower patients and augment doctors in their work.</strong></p><p><em>By </em><a href="https://medium.com/@adrianysan"><em>Adrian Young-san Roessler</em></a><em>, Head of Imagine, Aleksander Eiken, Medical Advisor, &amp; </em><a href="https://medium.com/@melanie.bourlioux"><em>Mélanie Bourlioux</em></a><em>, Product Manager of Imagine</em></p><p>It’s no secret that the healthcare landscape of tomorrow will be drastically different to that of today.</p><p>As the burden of chronic diseases rapidly increases worldwide alongside a growing shortage of healthcare professionals, patients who need ongoing support to manage their health condition will be forced to look to other means for their care. In fact, by 2035, there will be an estimated shortage of <a href="https://www.who.int/mediacentre/news/releases/2013/health-workforce-shortage/en/">13 million healthcare workers</a> to meet the needs of patients living with chronic diseases.</p><p>The future of healthcare, therefore, calls for patients to take on a more active role in the care of their own disease. It calls for more patient-led healthcare.</p><p>In <a href="https://leoinnovationlab.com/">LEO Innovation Lab</a>, we took on the challenge of meeting this demand by developing the mobile application Imagine: a ground-breaking tracking tool to help patients monitor and track changes in their skin condition.</p><h3>Bridging the gaps in patient care</h3><p>Because of the time it usually takes to see a dermatologist, the skin issue a patient has at home may not be the same as the skin issue they present during a consultation. Flare-ups and rashes don’t wait for a specialist. They fluctuate and may be gone when a patient finally goes in for a consultation, only to return later. The human brain can also be all too prone to relativising the past, meaning a patient might not be able to recall the state of their condition some weeks earlier accurately.</p><p>What patients need is a tool they can integrate into their everyday lives — something to bridge the gap between consultations with quality data from which doctors can get a better overview of the skin condition that goes beyond the immediate contact with the patient.</p><p>This is where <a href="https://getimagine.io/">Imagine</a> comes in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/369/1*elFlU3A5eli8ZeGpPum9KQ.jpeg" /></figure><p>By empowering patients with a systematic means of monitoring their skin disease, it allows both patients and doctors the ability to track and see changes that are often gradual, correlated to symptoms and triggers. This is powerful because people living with chronic skin conditions now have a single ecosystem for their information.</p><p>From the physician’s point of view, Imagine enables a better evaluation of patients based on a more holistic overview of their condition. Instead of relying on the patient’s own recollection of the progression of their skin condition, Imagine allows for more objective and aligned comparisons, and helps patients to better structure and share information about their disease and overall well-being. This, in turn, makes the consultation process more efficient, by establishing a platform where doctors and patients have the relevant imaging and patient data gathered in one place.</p><p>The impact of this is already manifesting itself among patients. Our initial findings indicate that when people use Imagine, there’s an uplift in their well-being, simply from not having to worry so much about their condition because of the personal insights they gain from the app. Imagine takes on a number of burdens such as remembering what the skin looked like at a specific point in time, how the symptoms have changed and when to take photos to document the condition. This means that the patient, from a more informed standpoint, can focus on maintaining a lifestyle to improve and take back control of their skin disease.</p><h3>From tracking to AI-driven diagnostics</h3><p>Though the first phase of Imagine was to create an effective tracking tool for patients, our ambitions have always been much bigger. That’s because tracking alone won’t tell you what triggers your symptoms, or how certain interventions are working. That still requires some detective work.</p><p>And so, to take the burden of analysis off the patients, we’ve since used our data to work towards developing machine learning algorithms, that will eventually be able to accurately diagnose skin diseases, first time around.</p><p>Due to the complexity of dermatology with the existence of more than 2,000 different diseases, there’s currently up to 50% misdiagnosis rate for dermatological conditions among general practitioners during the first consultation. In contrast, for the pictures users of the Imagine app have been sending in, our AI-powered diagnostic tool was capable of diagnosing psoriasis with 91% accuracy, which is on par with experienced dermatologists remote-diagnosing based on the photos.</p><p>As this technology becomes more sophisticated, we foresee a future where Imagine works in unison with doctors to accurately diagnose the patient that steps into the consultation room. This will not only enable doctors to provide better patient outcomes early on, but also to make better use of their time, by removing the burden of unnecessary follow-up consultations due to initial misdiagnosis or by avoiding that patients end in a limbo of treatments that don’t work.</p><p>Following Imagine’s success with psoriasis, we’re now working to improve our diagnostic accuracy with other skin diseases including prevalent chronic conditions such as atopic dermatitis, rosacea, and acne but also mimickers that are important to distinguish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BahzEh-9sdu8haWYiX_TIA.png" /></figure><h3>What does the future hold?</h3><p>In the short-term, Imagine will support doctors not only to diagnose patients but also to triage prior to a consultation taking place. The effects of this will be two-fold:</p><p>Firstly, rather than having to wait several weeks (or months) for an appointment, we foresee a future where textbook cases of skin diseases are immediately diagnosed and funnelled into a data-driven care plan.</p><p>Secondly, it will help to optimise the available time within a consultation where dermatologists can work with the predicted diagnosis data in the Imagine app, and spend more time on ensuring that the patient understands the implications of their disease and the importance of treatment adherence. Quality of life of the patient thereby becomes a more central area of focus for the physician to evaluate not only the progression of the disease but also patient well-being — an area which requires time.</p><p>In the long-term, we hope to establish a platform to connect patients and doctors in a more seamless way. This would facilitate quicker feedback loops with physicians to determine whether a treatment is actually working but also allow doctors to postpone, cancel or replace redundant follow-up visits for well-treated patients.</p><h3>Paving the way to inclusive healthcare</h3><p>The goal of Imagine is ambitious. We see the future of the Imagine technology as having the potential to increase the accuracy of diagnosing skin diseases and predicting treatment outcomes. Ultimately, our goal is to implement Imagine to reduce the cost of chronic diseases, while improving patient care for all people, irrespective of their socioeconomic background or access to healthcare.</p><p>Central to our work is the ambition to empower patients to become active participants in their healthcare plan rather than passive healthcare recipients — and to make expert-level dermatological disease management available for everyone.</p><p>The future’s bright, if you dare to Imagine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tuNO_ESpayZvUYm4P_lbJQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MmwZAKGHwJQVfNn3_7Tc4A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4XuOhKkhFxqE9ASQ9-vQtA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*36nqw1R1oOO21WaX-PedMA.jpeg" /><figcaption>Adrian, Aleksander and Mélanie work on Imagine in LEO Innovation Lab to help patients suffering from skin conditions take back control of their disease.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40c04de1106e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/leoilab/imagine-ai-technology-to-pioneer-patient-led-healthcare-40c04de1106e">Imagine: AI technology to pioneer patient-led healthcare</a> was originally published in <a href="https://medium.com/leoilab">LEO Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should good HealthTech make itself redundant?]]></title>
            <link>https://medium.com/leoilab/should-good-healthtech-make-itself-redundant-f46f7036f0e3?source=rss-92335455578b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f46f7036f0e3</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[healthtech]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[Adrian Y Roessler]]></dc:creator>
            <pubDate>Fri, 23 Nov 2018 10:41:20 GMT</pubDate>
            <atom:updated>2019-02-05T11:35:46.727Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is the part 1 of a series about how health technologies impact our lives and seek to change the way patients interact with the healthcare system. In this post, we explore the question: Should good HealthTech make itself redundant?</em></p><h3>Can a business’ mission be to eradicate its business?</h3><p>Many years ago, upon seeing Novo Nordisk’s mission statement printed on a messenger bag, I got into a discussion with the person carrying it. Back then, the statement read something along the lines of “Defeat diabetes”. My question to him was: How committed could a company be to erasing the sole purpose of its very existence?</p><p>Since then, diabetes has only manifested its pandemic-like rise but interestingly, Novo has also rephrased its mission statement to “Changing diabetes”.</p><p>A similar question could be posed to an increasing amount of HealthTech: How committed should and can those technologies (and the products and companies behind) be to making themselves redundant?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1PQuqoy80kQlLs_9SwcG9g.jpeg" /></figure><h3>Is success to become useless?</h3><p>Try to think of one of the earliest inventions to assist us for health reasons: the crutch. It’s a brilliant example of a health tool becoming successful through redundancy. On one hand, a person with a broken leg would be completely immobile without it but on the other hand, it’s such an annoying tool to rely on. You hate walking with it and being dependent on it to perform even the most basic everyday tasks, and its design and functionality really hasn’t evolved radically over the past centuries — maybe for the reason that it would have long-term negative consequences if you kept relying on it. The crutch is simply designed to make itself redundant. But what about healthtech?</p><p>For the annual <a href="https://www.hightechsummit.dk/">High Tech Summit</a> at the Technical University of Denmark, I had a conversation on stage with a person living with a chronic skin condition who used to be a user of the <a href="https://itunes.apple.com/us/app/imagine-psoriasis-tracking/id1133071282?mt=8">Imagine skin tracking app</a> we develop here in LEO Innovation Lab.</p><p>He was 20 years old when he first discovered that something was awry with his skin. A year passed before he went to the doctor and received his diagnosis: psoriasis.</p><p>Throughout our talk, he shared how using the app to document the development of his psoriasis through photos and then comparing them had helped him becoming more self-aware. However, once he had derived that benefit from the app, he stopped using it.</p><p>Part of me felt like we had failed. Our app hadn’t provided the necessary value for him to keep using it to document his flares over longer periods, so we could eventually automate even more helpful insights. He was another drop in our measure of retention.</p><p>And yet, as we continued to talk, I came to appreciate his point: The app had helped him manage his condition on his own. It had empowered him to strengthen his coping mechanism and identify his primary trigger: stress. It had been successful and as a consequence had made itself redundant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pOuSHUWRhOnBJ61jIlvzmA.jpeg" /><figcaption><em>Adrian Young-San Roessler discussing healthtech solutions with a psoriasis patient during High Tech Summit at the Technical University of Denmark</em></figcaption></figure><h3>Can redundancy be an aim for all HealthTech?</h3><p>The WHO defines Health Technology as “the application of organised knowledge and skills in the form of medicines, medical devices, vaccines, procedures and systems developed to solve a health problem and improve quality of life.”</p><p><strong>Medicine</strong>, especially in the areas of long-term conditions, is mainly focused on alleviating the symptoms in lack of available cures, the main advances of medicine are aiming to make it more effective, less costly, more accessible — and of course to cover more diseases. In the US alone, an estimated 30 million people are affected by about 7,000 rare diseases. 80% of these diseases are thought to be genetic in origin but only 5% have treatments available.</p><p>So healthtech in the form of medicines isn’t really looking at making itself redundant anytime soon.</p><p><strong>Vaccines</strong> are probably one of the most vigorously debated topics in the past years. Just when we thought the vaccines for polio and measles were so successful they had made themselves almost redundant, <a href="https://ecdc.europa.eu/en/news-events/measles-outbreaks-still-ongoing-2018-and-fatalities-reported-four-countries">outbreaks</a> reminded us that it likely takes a <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5745928/">global, coordinated and well-timed effort</a> if we want to eradicate those diseases as successfully as smallpox. Such important vaccines are here to stay.</p><p><strong>Medical</strong> devices have until recently mostly taken the form of hardware with varying degrees of complexity and with or without integrated software. Think of your fever thermometer but also x-ray scanners, blood pressure monitors or Novo’s insulin pen.</p><p>However, following the “software is eating the world” megatrend, a magnitude of <strong>procedures and systems</strong> are already software-based and digitised. Medical devices are also more and more purely software-based. We’re even seeing the first digital therapeutics clinically validated and <a href="https://www.mobihealthnews.com/content/pear-therapeutics-gets-de-novo-fda-clearance-reset-digital-therapeutic-substance-abuse">approved by regulators</a>.</p><p>Smartphone-based healthtech apps have made enormous inroads the past years. In 2017, 325,000 mobile health, fitness, and medical apps were available for download on Android or iOS. <a href="https://www.nature.com/articles/s41746-018-0021-9">However, only a tiny fraction of those can point to solid, science-backed proof</a> such as having gone through randomized controlled trials.</p><p>And given an increasing body of research around the negative effects of smartphone usage (exposure to <a href="https://www.nature.com/articles/srep11325">blue light</a>, <a href="https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0180094">behavioural changes</a>, etc.), combined with a dominant mindset of many technology companies to make products as addictive as possible, the question here becomes even more relevant: Should good HealthTech make itself redundant?</p><blockquote>“You’re spending a lot of time trying to make your products as addictive as possible. — <a href="https://www.cnbc.com/2018/10/15/facebook-early-exec-sean-parker-why-he-left-consumer-tech-for-health.html">Sean Parker on why he left consumer tech for health</a></blockquote><p>One example of health apps that defy the purpose of becoming redundant is also one of the most widespread: meditation apps.</p><p>In this category, you’ll find more than 1000 apps. From a product, design, and branding perspective, I personally find Headspace extremely inspiring. But is the criticism valid that this app exploits a weakness in people making them dependent on the app?</p><p>There is a growing body of scientific research pointing to positive effects of using the app. Headspace itself claims 65+ independent research studies to be in <a href="https://www.headspace.com/science">progress</a>. From current studies, smartphone-based mindfulness intervention has shown a number of benefits including <a href="https://link.springer.com/article/10.1007/s12671-018-0905-4">stress reduction</a>, improvements in <a href="https://www.ncbi.nlm.nih.gov/pubmed/29723001">wellbeing</a>, and increases in <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5770479/">psychological, social, and environmental quality of life</a> to mention a few. One study even showed a measurable impact on <a href="https://www.researchgate.net/publication/320365584_Acceptance_lowers_stress_reactivity_Dismantling_mindfulness_training_in_a_randomized_controlled_trial">blood pressure reactivity and cortisol levels</a>.</p><p>For meditation purposes, these apps are strictly speaking unnecessary. People have been meditating for thousands of years to achieve clarity of mind and improve mental wellbeing — and all you really need is yourself. But what these apps offer is convenience and insight as they meet you where you are — with your smartphone. Research suggests that self-monitoring has a positive <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3683566/">impact on your health behaviours</a> promoting awareness and self-efficacy — and potentially improving <a href="https://jamanetwork.com/journals/jama/fullarticle/189437">objective clinical evaluations</a> and boosting one’s <a href="https://www.ncbi.nlm.nih.gov/pubmed/15039514">immune</a>. Where the problems arise is when you can’t manage your health without an app and depend on it to understand yourself.</p><h3>Developing towards HealthTech making itself redundant</h3><p>So where does this leave us? Should good HealthTech make itself redundant?</p><p>Dependency is never a good thing in the long run — neither for development aid nor for HealthTech. When I talked to a psoriasis patient during High Tech Summit, he expressed:</p><blockquote>Technology can teach you a lot of useful things but you want to be able to absorb it and make it part of yourself rather than becoming dependent on an app.</blockquote><p>I believe that technology can play a strong initiating and facilitating role, lowering access barriers and increasing self-awareness. I also believe technology should empower people to use it as an enabler and catalyst; however, without becoming dependent on it. Therefore, technology should remember to consider itself a temporary crutch and make itself redundant. And where this cannot be the case, technology has to become non-intrusive and almost invisible — and only surface when it truly is needed and can make a difference.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f46f7036f0e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/leoilab/should-good-healthtech-make-itself-redundant-f46f7036f0e3">Should good HealthTech make itself redundant?</a> was originally published in <a href="https://medium.com/leoilab">LEO Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Into metrics]]></title>
            <link>https://medium.com/@adrianysan/into-metrics-7188403eea4d?source=rss-92335455578b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7188403eea4d</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-metrics]]></category>
            <dc:creator><![CDATA[Adrian Y Roessler]]></dc:creator>
            <pubDate>Wed, 14 Mar 2018 13:46:42 GMT</pubDate>
            <atom:updated>2018-03-14T13:55:12.544Z</atom:updated>
            <content:encoded><![CDATA[<h4>Some pointers around the topic of metrics for aspiring product managers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eWft9em6ugr_233mxXIgQw.png" /><figcaption>Not one of my best skills…</figcaption></figure><p>Why this post? I’m trying to work with someone on my team to develop him from helping manage projects into more of a product manager.</p><p>We’ve listed out a few topics he’d like to broaden his horizon on or which I think are essential to product management and one of them is our beloved topic of metrics!</p><p>He’s got an interesting background with a degree in philosophy and psychology which makes for a great base to empathise with people — both internally and the users and customers of products. So combining this with a sound understanding of and take on metrics sounds like a potentially great combination to me.</p><p>We agreed to take one topic at a time and that as a starting point I’d share some good reads for him to get into, reflect on and hopefully put into practice, so we can then work on that topic together applied to the real product.</p><h3>My metrics</h3><p>When trying to remember memorable reads and going through my “PM toolbox”, this of course made me think: What’s my own take on metrics? Do I have one? What are my key learnings from having optimized towards and battled with them in the past 8 years — for metrics, KPIs and targets both others and for the past many years mainly I, myself, had set. From work across B2B SaaS, consumer marketplace/eCom, and now for an AI-powered consumer app in the health space.</p><p>Here’s at least an incomplete bullet point list. Hopefully it can serve as reminder for me to write up a more memorable post:</p><ul><li><strong>ask the right questions in the beginning</strong></li><li><strong>imagine you have a certain type of data you’d like: ask yourself “so what?” — would you be able to have a meaningful insight?</strong></li><li><strong>ask yourself “so what” again — would you actually be able to or willing to act on that insight?</strong></li><li><strong>start tracking early</strong></li><li><strong>but don’t track for the sake of tracking</strong></li><li><strong>data — insights = 💩</strong></li><li><strong>garbage in — garbage out</strong></li><li><strong>data is dirty: there’s always smh that’s hidden in totals, averages, percentages, even cohorts if not broken down — but the more you break down, the less meaningful and actionable</strong></li><li><strong>be aware of local maxima, this post stuck with me for many years: </strong><a href="http://52weeksofux.com/post/694598769/the-local-maximum"><strong>http://52weeksofux.com/post/694598769/the-local-maximum</strong></a></li><li><strong>be aware of pre-mature optimization</strong></li><li><strong>make your KPIs to track meaningful numbers — and keep redefining them to be more meaningful as you increasingly learn more</strong></li></ul><p>Now on to some hopefully good and helpful reads around the topic.</p><h3>Good reads</h3><p>When I started my self-education in online marketing 7 years ago, I didn’t have a clue. Thanks to the guru of analytics, Avinash Kaushik (<a href="http://twitter.com/avinash">@avinash</a>), who gave me a lot to think about through his many fantastic posts. Here is an old post from 2010 but still a good starter — it goes to the basics of what a metric is: <a href="https://www.kaushik.net/avinash/web-analytics-101-definitions-goals-metrics-kpis-dimensions-targets/">https://www.kaushik.net/avinash/web-analytics-101-definitions-goals-metrics-kpis-dimensions-targets/</a></p><p>Knowing now about metrics and KPIs, we want to be ever grateful to <a href="https://medium.com/u/d2f31bf094c6">Eric Ries</a> for calling out a special metric, the vanity metric: <a href="https://tim.blog/2009/05/19/vanity-metrics-vs-actionable-metrics/">https://tim.blog/2009/05/19/vanity-metrics-vs-actionable-metrics/</a></p><p>A more recent post, takes the vanity vs. clarity metrics into even more practical territory and examples: <a href="http://firstround.com/review/im-sorry-but-those-are-vanity-metrics/">http://firstround.com/review/im-sorry-but-those-are-vanity-metrics/</a></p><p>So how do you end up measuring things that actually matter? By asking the right questions. The guys over at Intercom remind us about that: <a href="https://blog.intercom.com/finding-the-metrics-that-matter-for-your-product/">https://blog.intercom.com/finding-the-metrics-that-matter-for-your-product/</a><br>Looking for more product management wisdom? Intercom usually have really great posts around product — or at least used to when co-founder Des Traynor was still writing them himself.</p><p>A lot of my experience with metrics comes from working in startups but regardless whether big or small companies, cutting through the bullshit and focusing in on what matters applies anywhere.</p><p>The infamous Dave McClure of 500Startups coined the AARRR startup metrics for pirates: <a href="https://www.slideshare.net/dmc500hats/startup-metrics-for-pirates-long-version">https://www.slideshare.net/dmc500hats/startup-metrics-for-pirates-long-version</a><br>Even better, watch him passionately present the slides in just 5 minutes with very low curse/minute ratio for Dave:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FirjgfW0BIrw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DirjgfW0BIrw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FirjgfW0BIrw%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/694f51b864ef587877810739f67e1fae/href">https://medium.com/media/694f51b864ef587877810739f67e1fae/href</a></iframe><p>Here is another good slideshare on startup metrics from one of the early lean startup community builders of the Vienna startup scene <a href="https://medium.com/u/ac19e2880d0c">Andreas Klinger</a>:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2Fg8xnQxPD6E0JPp&amp;url=https%3A%2F%2Fwww.slideshare.net%2Fandreasklinger%2Fstartup-metrics-a-love-story&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2F20130812-icatapult-130812090501-phpapp02-thumbnail-4.jpg%3Fcb%3D1376628488&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/057fabe6bf58c7c4806b3c0db00bf2f2/href">https://medium.com/media/057fabe6bf58c7c4806b3c0db00bf2f2/href</a></iframe><p><a href="https://medium.com/u/b8a4e5ae7490">Julie Zhuo</a>, VP product design at Facebook once in a while posts a great article around design or product on Medium. Here is one on how she sets metrics: <a href="https://medium.com/the-year-of-the-looking-glass/how-do-you-set-metrics-59f78fea7e44">https://medium.com/the-year-of-the-looking-glass/how-do-you-set-metrics-59f78fea7e44</a></p><p>And having entered the realm of design and UX, people often wonder how they can or should measure those aspects meaningfully.</p><p>Google’s answer is the HEART framework to measure the quality of the customer/user experience of a product or feature: <a href="https://library.gv.com/how-to-choose-the-right-ux-metrics-for-your-product-5f46359ab5be">https://library.gv.com/how-to-choose-the-right-ux-metrics-for-your-product-5f46359ab5be</a></p><p>Assume you’ve found your metrics — how much importance should you give them in your decisions? This is a good write-up by <a href="https://medium.com/u/4f6994e706c8">Des Traynor</a> on the problem with data-driven decisions and why all the data in the world doesn’t necessarily mean anything: <a href="https://blog.intercom.com/the-problem-with-data-driven-decisions">https://blog.intercom.com/the-problem-with-data-driven-decisions</a></p><blockquote>For example if Apple were driven by data points, they would release a €400 netbook or shut down their Genius Bar after years of no activity. If Ryanair were customer driven they’d remove all their sneaky fees &amp; charges. If Zappos were driven by margins, they’d abandon their generous returns policy. They’re all just perspectives. Just because data is objective, it doesn’t mean that it guides you to the right decision. Just because it’s precise, it doesn’t follow that it’s valuable.</blockquote><p>And the bigger you get, the deeper such data-driven decisions can affect the culture. See this example happening at the “most innovative” company in the world back in 2009: <a href="http://stopdesign.com/archive/2009/03/20/goodbye-google.html">http://stopdesign.com/archive/2009/03/20/goodbye-google.html</a></p><p>And then of course it’s always good to look what the always provocative, always rebel (or just sane and sensible?) guys <a href="https://medium.com/u/c030228809f2">Jason Fried</a> and Daniel Heinemeier Hansen <a href="https://medium.com/u/54bcbf647830">DHH</a> have to say on the topic. In my quick search I could only find a tweet and medium comment:</p><h3>DHH on Twitter</h3><p>Holy shit! I just realized that we don&#39;t have any established KPIs for Basecamp 😱. I don&#39;t even understand how we are still in business?! It&#39;s like the bumblebee that&#39;s not supposed to be able to fly 😂</p><p><a href="https://medium.com/@jasonfried/no-okrs-no-metrics-b79cd1753c06">No OKRs, no metrics.</a></p><p>Lastly, I couldn’t find anything online in my quick search but something <a href="https://medium.com/u/9ec802199956">Tom Hulme</a> from IDEO once said at a conference stuck with me. It went something like this:</p><blockquote>Be careful what you set out to track as your main metric. Eventually, you [your product] will become what you track.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7188403eea4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to handle hack week as a product manager]]></title>
            <link>https://medium.com/@adrianysan/how-to-handle-hack-week-as-a-product-manager-dcee8da4bade?source=rss-92335455578b------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcee8da4bade</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Adrian Y Roessler]]></dc:creator>
            <pubDate>Thu, 28 Jan 2016 18:41:04 GMT</pubDate>
            <atom:updated>2016-01-28T18:41:04.688Z</atom:updated>
            <content:encoded><![CDATA[<h4>Learnings and observations from participating in a recent hack week</h4><p>Not everything sucks about being acquired by a big company. In fact, there are quite a number of cool things. A great example is an internal hack week, taking place once a year. You’re basically free to hack away on anything you like for an entire week instead of your regular work.</p><p>Sounds pretty cool, eh? Now people might argue at a hack week there is no need for a product guy or girl to bring in the customer angle, provide and interpret metrics, write up user stories, or do mundane PM duties. Apart from bringing in the doughnuts and RedBull, what can a product manager contribute?</p><blockquote>… ? That much?</blockquote><p>I’m a marketing turned product guy with minimalistic html/css/mysql knowledge and design skills ending at mockups or wireframes. So I was a bit unsure what to expect from a hack week but wanted to test out a few things. So here’s what I learned.</p><h4>The power of naming</h4><p><em>People submit ideas. People express their interest. People form teams. Teams hack away.</em> So the official plan. Well, at least theoretically. Turns out people have difficulties choosing and making a decision between 40+ different hack ideas. So what to do to get people to make a decision and join you on one of the ideas?</p><p>I’d like to believe that my simple action of changing the name of an existing hack idea from<em> “usage statistics”</em> into <em>“kicka.ss”</em> and writing up a little vision story around it, suddenly got a bunch of designers and developers interested. Some visual mockup would have probably also worked.</p><p>Sometimes little actions can start initial movement. And: Standing out simply works.</p><h4>Give it an identity</h4><p>And that needs to be continued throughout the project. Even though it’s only a hack week, just as any other project, you have to repeat the story, the bigger reason for whom and why we’re building it and what it will allow people to do.</p><h4>Owning it</h4><p>So we ended up being a team of a designer, three frontend devs, a QA guy, and not only one but <em>even two product managers</em>. And we wanted to do smth around usage statistics of our product. Without a backend guy. Duh.</p><p>It was fantastic to have everyone involved from the very beginning. Typically, the product manager and designer would start looking ahead, discuss a certain direction and only involve the developers in some more concrete planning, estimation or technical risk assessment phase. Too late!</p><p>Now, of course you don’t want to bother developers with too many direction meetings and endless discussions but if you can find a good way to involve them from the very start, that’s an immensely important step for everyone to feel real ownership of whatever you want to ship.</p><h4>It’s in the details</h4><p>Having everyone involved from the very beginning also causes a lot of possible directions, tons of idea input, and bears the danger of inaction — before someone just starts running off just to do something.</p><p>It was rewarding to see some of the classic PM techniques to come in handy. For example wireframes. Quickly drawing things up that we had talked about was a great help to re-align. Was that really what we had talked about and everyone of us had also meant and understood? Plus, it’s a great orientation help.</p><p>Pay attention to the details, though. You draw in a little detail just for fun, don’t communicate about it, and whoops — your designer or developer might just pick up on it, even though you agreed on a totally different direction in talks.</p><h4>Communicate</h4><p>Communicate. Communicate. Communicate. And: you cannot not communicate. We all know this and yet we get trapped up in it again and again.</p><p>Here’s an example from that hack week. We were building an app, ‘Moments’, to track your work-related achievements and best moments and then produce a cool graphic containing your achievement and a snapshot of that moment— and obviously we wanted it to be shareable on Instagram! We talked about …”and then you share it to Instagram”.</p><p>The problem: while some of us just thought of it as those words, our developers thought about it in all the tricky, technical details. Catching up a couple hours later, they had investigated really deeply how a possible, complicated API integration could work. In reality, all we needed was to just send the picture from one app into another app on iOS.</p><h4>PMs do matter</h4><p>As PMs we often are unsure about the concrete impact we’re having. Are we more in the way than actually helping?</p><p>During the condensed and intense hack week, I really could see what even mundane PM tasks do matter. A lot.</p><p>Without some simple PM techniques and tasks, things would just spiral into completely different directions, communication would die, motivation would drop, and shipping a product become less and less likely.</p><h4>2 PMs and one…</h4><p>Too much? Maybe. Looking back, however, I really appreciated bouncing off ideas really early with the other PM. Not reflecting too much about them and trying to formulate them out too much into something ‘actionable’ for the team, was quite liberating. We should do that more often. Just talk to the other PMs outside of our own teams at a really early stage.</p><p><em>Note: this post was started as a draft 2 years ago, never finished or published until now, where I’m sitting at a ‘blogathon’ of the newly started Blogging Copenhagen meetup group. Getting the shipping goggles on (thanks Jason) and… out it goes! My opinions might have changed since then:)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcee8da4bade" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>