<?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 N Chandrasekhar Ramanujan on Medium]]></title>
        <description><![CDATA[Stories by N Chandrasekhar Ramanujan on Medium]]></description>
        <link>https://medium.com/@NCResq?source=rss-39b85dda25e5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eqcuiIZxNFyQxbo_kh40_g.png</url>
            <title>Stories by N Chandrasekhar Ramanujan on Medium</title>
            <link>https://medium.com/@NCResq?source=rss-39b85dda25e5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:05:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@NCResq/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[How A Job Ad’s Language Influences Diversity: A Case Study]]></title>
            <link>https://medium.com/gojekengineering/how-a-job-ads-language-influences-diversity-a-case-study-87ba194e273e?source=rss-39b85dda25e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/87ba194e273e</guid>
            <category><![CDATA[gojek]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[gender-diversity]]></category>
            <category><![CDATA[diversity]]></category>
            <dc:creator><![CDATA[N Chandrasekhar Ramanujan]]></dc:creator>
            <pubDate>Fri, 16 Sep 2022 06:11:36 GMT</pubDate>
            <atom:updated>2022-09-16T06:11:36.118Z</atom:updated>
            <content:encoded><![CDATA[<h4>When a volunteer opportunity turned into a learning experience.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oEEmEWhLYePD8MfpVXFYOg.png" /></figure><p>After having joined as a Product Designer at Gojek, a few months ago, I went on a quest to improve my writing and documentation skills. I got an opportunity to volunteer with our amazing Design Ops team on an interesting project around how language affects our Design team.</p><p>I thought it would be a simple, straightforward project, but boy was I wrong! It was very different from the kind of product design I am used to and I was all set to be pushed out of my comfort zone. Taking up this new project meant that instead of designing digital apps and services, I’d be designing internal team processes. And it turned out to be one of the most complex projects I’ve worked on.</p><h3><strong>What is Gender Coding?</strong></h3><p>Companies are coming to realise the benefits of making the workplace more diverse — from greater creativity and innovation, to being able to better empathise with a wider range of users. In order to improve the diversity of their talent pool, companies have started to try many initiatives. But there is one seemingly simple thing that has a great negative impact if done wrong: The language used to describe job openings.</p><p>You’re probably thinking: “Language? How can that impact diversity?”<br>Let’s zoom out a little.</p><p>Consider the following words:</p><p>Nurse.</p><p>Firefighter.</p><p>Singer.</p><p>What image came into your mind when you read those words? What did they look like? What kinds of associations did they create in your mind?</p><p>Unlike many other languages, English has very few words with a clear gender. However, we can still react to words differently based on our experience, beliefs, and stereotypes. Our language can also change depending on which gender we refer to, with some words used more often to describe men than women, and vice versa. <strong>Over time, these words become linked to a specific gender. This is gender coding.</strong></p><p><a href="https://gender-decoder.katmatfield.com/static/documents/Gaucher-Friesen-Kay-JPSP-Gendered-Wording-in-Job-ads.pdf">Research studies</a> show that women aren’t as likely to apply for jobs that are advertised with masculine-coded language and vice versa (to a smaller extent).</p><p>Take a look at this job ad posted below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-uw4TVbhOyjndezU9U0SxA.png" /><figcaption>In your mind, what is the impression that appears when you read this?</figcaption></figure><p>It’s full of words associated with male stereotypes like competitive, dominant, leader, challenge. And zero words that are associated with female stereotypes like support, understand, interpersonal, co-operate, connect.</p><p>When candidates apply, they end up asking themselves — Am I who they are looking for? Would I fit in? Do I belong in this job? It’s reasonable to assume that male candidates would be more drawn to this job ad than female candidates.</p><h3>How gender coding affects job applicant behaviour</h3><p>It’s important to understand that this is not an explicit/obvious phenomenon — it’s subtle, where the word association happens at a subconscious level due to internalised stereotypes. It’s also not deliberately done by the writer of the job description. Usually they think of the qualities they themselves have, and write a job description to attract more people like themselves.</p><blockquote>This ends up being a vicious circle. Gendered words in job advertisements make a position seem less appealing to a certain gender, and limit the applicant pool for these jobs.</blockquote><p>For example, a strongly masculine coded job ad will have more men than women apply, and that the job will end up being filled by another man, and when it’s his turn to write another job description, he will most likely write another strongly masculine-coded ad and once again, more men will apply.</p><p>So why is this a problem? If a company wants to attract more women applicants, for example, then if the gender coding in their job advertisements could be discouraging them from applying in the first place, then that is a serious concern that needs to be addressed since it is preventing the company from being a diverse workplace.</p><p>I took a look at the numbers for our design opening applications in 2022, and I came across an interesting insight. While most of our job ads are not masculine coded, the more senior the role the more likely it is masculine coded, and that trend is reflected in the applications we receive — where junior roles and a higher ratio of women applicants than senior roles. Basically that means the ratio of women to men applicants went down as the seniority of the job post went up.</p><p>This was a good starting point. But I needed more data.</p><h3>Digging deeper</h3><p>On top of this initial analysis, I did initial qualitative interviews with 4 women designers, 2 in Gojek and 2 outside Gojek. I tried to understand what all were the data points that they paid attention to when applying, and any anecdotes of red flags they encountered.</p><p>I also came across a tweet thread from a woman designer who was applying for the job search and had talked about her experiences</p><h3>Sai on Twitter: &quot;//1 - Take for instance this well-funded startup. For a portfolio round, I was asked to present in front of 4 designers, all-male. I was aware of 5 female designers across multiple levels here. Wonder what was the reason for them not being on this call? / Twitter&quot;</h3><p>1 - Take for instance this well-funded startup. For a portfolio round, I was asked to present in front of 4 designers, all-male. I was aware of 5 female designers across multiple levels here. Wonder what was the reason for them not being on this call?</p><h3>Sai on Twitter: &quot;//2 - Another org had 4 rounds, all were taken by men - similar age groups &amp; backgrounds. Round 1: Senior Designer, then a PM, then Design Lead, and finally Head of Design. //3 - One company outright denied my request to talk to other designers on the team - big red flag 🚩🚩🚩 / Twitter&quot;</h3><p>2 - Another org had 4 rounds, all were taken by men - similar age groups &amp; backgrounds. Round 1: Senior Designer, then a PM, then Design Lead, and finally Head of Design.</p><p>Based on this, I got the following insights. The designers would look at the company page and LinkedIn to see who all were the designers there, and how they had been featured. For example does the team page only have photos of men? That could be a red flag.</p><p>They would also talk to other designers at the company to learn more about what the work environment and atmosphere would be like.</p><p>Finally they would accord maximum weight to the first conversation they had with the company, such as with a recruiter/HR, as well as if they came across any red flag in panelist interactions during the interview process.</p><h3>Creating the problem statement</h3><p>I also analysed all the Gojek job ads that were live as of 27th May, using the “Gender Decoder” tool, and tried to visualise it by specialisation (Interaction Design or Motion design versus Product Design, which is more generalist) and seniority (IC vs manager, years of experience, etc.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mrp-sHh5Dvb6nWk41pYkog.png" /></figure><p>The insights I got was that the JD coding followed the axis of seniority and specialisation — the more senior a role, the more likely it was for the job ad to contain masculine coded words. At the same time, the more specialised the role, the less likely it was to contain feminine coded words.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MQAAZ_3KHZ3p3R9dDnjuTw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C08oUfFBAJX4jCMQCzPdkw.png" /></figure><p>Based on that, I defined the objective now as to<strong> make the Gojek job ads and internal career ladder documents to be as gender neutral as possible.</strong></p><p>I looked into the best practices, and developed a checklist for people to refer to as they are writing the documents, as well as a list of words to avoid using too much.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7X1-FiEIb98mssy7" /></figure><p>One big ask was for help in order to find alternatives to gender coded words.</p><p>I came across an insight that most of the gender coded words are adjectives or qualities, and to bypass that, the writer should use descriptive words where necessary to indicate what candidate does vs. who they should be. For example, do not use adjectives like superior, exceptional, or first rate without additional evidence to back them up as to what you mean. If adjectives are needed, use it to describe the candidate’s actions or skills instead of the candidate themselves.</p><p>Here is an example below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QlhEJXndznun8o-N1lBrLw.png" /></figure><p>I also came up with a few more steps as an SOP:</p><p>1. Pass all ads through a gendered language test such as the “<a href="https://gender-decoder.katmatfield.com/">Gender Decoder</a>” by Kat Matfield</p><p>2. Consider the use of words in senior job ads in particular</p><p>3. Avoid ‘cut and paste’ job ads where the previous job ads are used as the basis to write new ones, thus perpetuating the existing issues</p><p>4. List only the skills that are absolutely necessary for the role</p><h3>What happens next?</h3><p>Now for next steps. Of course, we can’t say that the language of the job ad is the only reason for the lopsided ratio of diversity in organisations. There are a range of factors that influence gender ratio, and the job ads language is one that’s under our control, and an easy one to fix.</p><p>We are also looking at where we advertise jobs (could some job boards more male-focused than others, for instance? And I also recommended a ‘Blind’ panel process to strip out name/gender details to remove any subconscious bias on part of the recruiters.</p><p>As a designer, I also learned a lot about a lot of team-building and HR related topics, and how to apply a designer’s lens to problem areas that we would not traditionally be associated with. This was not a problem I could solve by jumping onto a tool and making a prototype. I had to understand a lot about team dynamics and existing processes which are more implicit and intangible, and figure out how to work within those.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IPWwoozDxeKoXMtXEyrtLw.png" /></figure><p>Find more stories from our vault, <a href="https://www.gojek.io/blog">here</a>.<br>Check out open job positions by clicking below:</p><figure><a href="https://bit.ly/gojekjobsblogs2022"><img alt="" src="https://cdn-images-1.medium.com/max/700/1*c2_eIvR2WDUWnP6YmzcGpQ.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87ba194e273e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gojekengineering/how-a-job-ads-language-influences-diversity-a-case-study-87ba194e273e">How A Job Ad’s Language Influences Diversity: A Case Study</a> was originally published in <a href="https://medium.com/gojekengineering">Gojek Product + Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Team Lightning — Status Update on the way to Mini Challenge 2]]></title>
            <link>https://medium.com/team-lightning/team-lightning-status-update-on-the-way-to-mini-challenge-2-5f97705f1199?source=rss-39b85dda25e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f97705f1199</guid>
            <category><![CDATA[ozchi-design-challenge]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[N Chandrasekhar Ramanujan]]></dc:creator>
            <pubDate>Sat, 17 Aug 2019 13:45:10 GMT</pubDate>
            <atom:updated>2019-08-17T13:46:08.311Z</atom:updated>
            <content:encoded><![CDATA[<h3>Team Lightning — Status Update on the way to Mini Challenge 2</h3><p>It’s been a crazy last 6 hours!</p><p>We went back and forth on a bunch of ideas for our final concept, including all kinds of crazy things, most notably an interactive balloon in the sky that communicates the health of a neighbourhood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SHo9wyuAEz6DJGBg_1WGcA.jpeg" /><figcaption>Our ideations</figcaption></figure><p>We even storyboarded a potential scenario and made a journey map</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DOPxkJZM1_jEQmnPYbwedA.jpeg" /><figcaption>Our storyboard</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zbXAlkJlj5OiXxKS6kH9RQ.png" /><figcaption>How the Balloon service could work</figcaption></figure><p>But we realised that we were holding ourselves back and wanted to explore more possible range of concepts before committing to anything.</p><p>We set on a few design principles we could use to inform our design (from the lit review)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tq7mPZTnSAiWG8uCOV-6Bw.jpeg" /><figcaption>Our design principles for our artefact</figcaption></figure><p>We also tried to use Maslow’s Hierarchy of Needs as a metaphor to try to uncover new opportunity spaces for our design</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Olr7IFUsN3u2y3ykK3ljg.jpeg" /><figcaption>Maslow’s Pyramid as applied to disaster response</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cqfLwBCsoA771QOZZ-MCCw.jpeg" /><figcaption>Possible design directions for community networks</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iBtPo0xfXh47QNRF5IlX3w.jpeg" /><figcaption>Stakeholder map of everyone involved</figcaption></figure><p>And some nice asides</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wgbCXeWb4CTwRx3KHauS6Q.jpeg" /><figcaption>We also played foosball!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*P_6l1EsG1rFNsG1_E5sHdg.jpeg" /><figcaption>It was also Chandra’s birthday! Happy Birthday Chandra!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f97705f1199" width="1" height="1" alt=""><hr><p><a href="https://medium.com/team-lightning/team-lightning-status-update-on-the-way-to-mini-challenge-2-5f97705f1199">Team Lightning — Status Update on the way to Mini Challenge 2</a> was originally published in <a href="https://medium.com/team-lightning">Team Lightning</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mini Challenge 1 — Literature Review]]></title>
            <link>https://medium.com/team-lightning/mini-challenge-1-literature-review-bb4dd616a9de?source=rss-39b85dda25e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb4dd616a9de</guid>
            <category><![CDATA[ozchi-design-challenge]]></category>
            <category><![CDATA[smart-cities]]></category>
            <category><![CDATA[social-capital]]></category>
            <dc:creator><![CDATA[N Chandrasekhar Ramanujan]]></dc:creator>
            <pubDate>Sat, 17 Aug 2019 08:19:41 GMT</pubDate>
            <atom:updated>2019-08-17T08:23:30.835Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mini Challenge 1 — Literature Review</h3><p><em>In this article, we discuss the literature on the topic we read and how it informed the direction of our work</em></p><p><strong>Social Capital and HCI</strong></p><p>Normally, when we think about assets, or things that can be used to make other things, we think of machinery, workers etc. However, the theory of social capital tells us that the social relationships among people are also important. A “network” of people — who communicate with each other and can trust each other, can accomplish much more than a similarly sized group of strangers, i.e the whole is more than the sum of its parts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Uu77Hycop4p-anRh8t-DQ.jpeg" /><figcaption>Team Lightning hard at work!</figcaption></figure><p>Aldrich and Meyer look at the various ways in which Social Capital can be defined — from the resources we can access through networks of people we know, to the norms, practices and trust that facilitate action and cooperation for mutual benefit at a neighbourhood and community level. [1]</p><p>Further, there are three kinds of social capital, each of which manifest in different ways. [2]</p><p><strong>Bonding</strong> Social Capital deals with the formation of <strong>connections</strong> between people, which directly influences their willingness and ability to support and assist each other.</p><p><strong>Bridging</strong> Social Capital deals with “loose” connections in groups — such as clubs, sports teams etc which may reach across social barriers of class, ethnicity etc.</p><p>Finally, <strong>Linking</strong> Social Capital connects people at different levels of power ( such as a voter and an elected representative).</p><p>Paul Resnick argues that social capital is a necessary precondition for the successful deployment and use of socio-technical systems — i.e technological systems which involve both social/cultural values in addition to user behavior. This is because only after users have developed trust in each other, a shared identity, or some for of social capital that they can use the system without being worried or suspicious. [3]</p><p>He further argues that HCI research can contribute to increasing social capital in two ways:</p><ol><li>Organisations and groups that are large sources of social capital, such as religious organisations, sports bodies etc can use digital technology to coordinate and publicise events</li><li>Conceptualise and develop new <em>kinds</em> of activities that can help increase social capital among participants</li></ol><p><strong>Community Resilience</strong></p><p>Community Resilience is defined as the collective ability of a neighbourhood/geographical defined area to deal with stressors such as natural disasters, political unrest, etc in order to efficiently resume their daily activities [1]. This ability to bounce back quickly arises from co-operation. The foundation for community resilience lies in the community’s participation, cohesion, engagement and belonging.</p><p><strong>Social Capital in a disaster setting</strong></p><p>Through Social Networks, people have access to resources both tangible (loans and gifts for repair) and intangible (performing search and rescue for neighbours, removing debris, caring for children, passing on information). Aldrich and Meyer also show examples of how people with fewer social ties are less likely to be rescued or get the assistance or medical help that they need.</p><p>Finally, there are feelings of mutual trust, that emerge from high social capital, also led to an increase in awareness of the need for disaster management and the willingness to volunteer, which in turn supports preparedness, a collective response from the neighbourhood, and better rates of adaptation and recovery. [1]</p><p><strong>What is truly a smart city?</strong></p><p><em>Show how the technology you envision intertwines with other things.</em></p><p><em>-Philip Agre</em></p><p>Smart Cities are intended to incorporate digital technology to sense activities and respond more quickly to emergencies. Through the evolution from intelligent cities to responsive cities the focus has been mostly on the technological and technical systems rather than the urban ecologies and community cohesion that needs to evolve in parallel with the cities.</p><p>Yigitcanlar et al quote Cugurullo’s argument that that current practice in smart cities is generating a kind of Frankenstein urbanism where different incompatible units in cities has been forced, fueled by technocratic approach that tends to favour the more economically profitable outcome. This discounts other factors that establish a city’s core well being. So, when it comes to planning cities, for a more sustainable approach, planners need to work on building social and human capital on foundations of symbiosis between humans and contextually embedded technologies. [4]</p><p><strong>State of the art review</strong></p><p>Community engagement is a well-known method to engage stakeholders in various urban planning projects. It has been seen in smart cities as well, such as the case of Nottingham in the UK [5]. The issue is that it focuses on the relationship of the state with the citizens (i.e linking social capital) and not the relationships of citizens with each other (bonding and bridging capital). Mainka et al also study various citizen-led innovation initiatives for public libraries in Denmark and Finland, and the 311 phone system in the USA (where citizens can request data on the city from the government) [6]</p><p>One of the most exciting things we came across was PREPHUB — an architectural installation for disaster preparation [7] . PREPHUBs are permanently installed units at regular intervals throughout the city which can be configured differently for different spaces and needs which modular blocks which offer basic amenities like electricity, water and facilities like information display screens, visual communication (photo/video), neighborhood resource map, and pedal-powered DC generators,etc. They act as benign structures which are recognised points which transform into resource centers in times of disaster where the neighbourhood gets together and helps each other by connecting and collaborating humanely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*tAZB8_QgK8VVm_fk" /><figcaption>A sketch demonstrating what Prephub is and how it works</figcaption></figure><p>(Source: <a href="https://prephub.org/)">https://prephub.org/)</a></p><p><strong>Synthesis and Design Principles</strong></p><p>In times of disaster, infrastructures we take for granted such as electricity, internet and so on are usually knocked offline for extended periods of time.</p><p>Any artefact that we design to help community resilience through social capital has to keep that in mind. Relying on digital technology alone risks an over-reliance on a single point of failure, and we need to design keeping in mind broader system and societal dynamics.</p><p>Smart Cities, and the rise of city — as — platform prompts for better decision making tapping into collective Intelligence by businesses, residents and government of the city. However once again these systems are vulnerable to disruption but their core principles can be kept in mind — <strong>how might we design decentralised and citizen-focused artefacts which can operate independently but still use collective intelligence and local knowledge to create a bottom-up network? </strong>Is “smartness” a necessary and sufficient condition for such an artefact? Can we interrogate and question pre-defined notions of “smartness”?</p><p>Finally, the design of the artefact needs to incorporate affordances for collective and collaborative operation. It should act as a “third space” where citizens can congregate and meet with each other. They should be able to share information and request or volunteer help outside of their immediate social circles (i.e bridging social capital) as Adrich and Mayer point out in the case of Hurricane Katrina that this was what allowed some neighbourhoods to recover faster than others. [1] We really like PREPHub for this reason.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*j5MT6BC81osCDGHy" /><figcaption>(Source: <a href="https://prephub.org/)">https://prephub.org/)</a></figcaption></figure><p><strong>Preliminary Evaluation Criteria</strong></p><ul><li>Does it help create a greater number of “bridging” social relationships across class/race lines? Is it accessible to all kinds of users (low literacy, physical disability etc)</li><li>Does it help create more “linking” relationships across power differentials (citizen-government</li><li>Can it operate in adverse weather conditions?</li><li>Can it operate in the absence of internet or electricity supply?</li><li>Can multiple people use it at the same time with different goals and still be able to accomplish what they intend to do?</li></ul><p><strong>References</strong></p><ol><li>Daniel P. Aldrich and Michelle A. Meyer. 2015. Social Capital and Community Resilience. <em>American Behavioral Scientist</em> 59, 2: 254–269. <a href="https://doi.org/10.1177/0002764214550299">https://doi.org/10.1177/0002764214550299</a></li><li>Brian Keeley and OECD. 2007. <em>Human capital how what you know shapes your life</em>. Retrieved August 17, 2019 from <a href="https://doi.org/10.1787/9264029087">https://doi.org/10.1787/9264029087</a></li><li>Paul Resnick, Tora Bikson, Elizabeth Mynatt, Robert Puttnam, Lee Sproull, and Barry Wellman. 2000. Beyond bowling together. In <em>Proceedings of the 2000 ACM conference on Computer supported cooperative work — CSCW ’00</em>, 363. <a href="https://doi.org/10.1145/358916.362079">https://doi.org/10.1145/358916.362079</a></li><li>Tan Yigitcanlar, Marcus Foth, and Md. Kamruzzaman. 2019. Towards Post-Anthropocentric Cities: Reconceptualizing Smart Cities to Evade Urban Ecocide. <em>Journal of Urban Technology</em> 26, 2: 147–152. <a href="https://doi.org/10.1080/10630732.2018.1524249">https://doi.org/10.1080/10630732.2018.1524249</a></li><li>Mazhar, M., Bahareh Kaveh, Marjan Sarshar, Richard Bull, and R. Fayez. “Community Engagement as a Tool to help deliver Smart City Innovation: A Case Study of Nottingham, United Kingdom.” 2017.</li><li>Agnes Mainka, Walter Castelnovo, Virve Miettinen, Sidsel Bech-Petersen, Sarah Hartmann, and Wolfgang G. Stock. 2016. Open innovation in smart cities: Civic participation and co-creation of public services: Open Innovation in Smart Cities: Civic Participation and Co-Creation of Public Services. <em>Proceedings of the Association for Information Science and Technology</em> 53, 1: 1–5. <a href="https://doi.org/10.1002/pra2.2016.14505301006">https://doi.org/10.1002/pra2.2016.14505301006</a></li><li>Miho Mazereeuw and Elizabeth Yarina. 2017. Emergency Preparedness Hub: Designing Decentralized Systems for Disaster Resilience. <em>Journal of Architectural Education</em> 71, 1: 65–72.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb4dd616a9de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/team-lightning/mini-challenge-1-literature-review-bb4dd616a9de">Mini Challenge 1 — Literature Review</a> was originally published in <a href="https://medium.com/team-lightning">Team Lightning</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Studio Reflection: Probing into Services, Systems and Infrastructures]]></title>
            <link>https://medium.com/gigs-service-systems-platforms-and-design/studio-reflection-probing-into-services-systems-and-infrastructures-3f21007bcb86?source=rss-39b85dda25e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f21007bcb86</guid>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[N Chandrasekhar Ramanujan]]></dc:creator>
            <pubDate>Sat, 23 Feb 2019 15:46:38 GMT</pubDate>
            <atom:updated>2019-02-24T10:26:56.255Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>In the recent “Probing into Services, Systems and Infrastructures” Studio at Srishti, our team of students in the M.Des in Human Centred Design Programme looked at the relationship between domestic help and employers within the context of gated community management apps.</p><p>We then helped to develop a tool that we called the “<strong>care rubric</strong>” that helps designers find opportunities and gaps within the structure of services to incorporate “care” as a value. In this context it meant how to <strong>create opportunities for mindful interactions</strong> between customers and employees in a service that fostered kindness, mutual respect, understanding, and diginity. We then tried to apply this to the MyGate mobile application.</p><p>You can read more about our project in our <a href="https://placesjournal.org/article/maintenance-and-care/"><strong>Proposal</strong></a>, <a href="https://medium.com/gigs-service-systems-platforms-and-design/towards-analyzing-care-through-a-multistep-framework-2db8afcd9ad9"><strong>Process Documentation</strong></a>, and <a href="https://medium.com/gigs-service-systems-platforms-and-design/care-rubric-the-first-iteration-74ef4cde40be"><strong>Final Output</strong></a> here on this publication.</p><h3>Defining Service Design</h3><p>The <a href="https://trydesignlab.com/blog/what-is-service-design/">Service Design Network</a> defines it as</p><blockquote>The activity of planning and organizing people, infrastructure, communication and material components of a service in order to improve its quality and the interaction between service provider and customers</blockquote><p>As a student of the HCD programme at Srishti, I was initially a bit confused. Till then I had thought that what I was doing fell under the domain of Interaction Design or HCI. But I came across a <a href="https://articles.uie.com/service_design/">great article</a> by <a href="https://medium.com/u/b90ef6212176">Jared M. Spool</a> with a passage that really helped to clarify my thinking:</p><blockquote>We’re no longer in a world when we can design for just a single isolated online interaction, not thinking about what happened before that interaction or what happens after… We’re now in a world where digital and non-digital are merging. And <strong>we need to be prepared to design in that overall experience</strong>.</blockquote><h3>Our Process</h3><p>We were given a fairly open-ended brief — to look at the design of gated community management application and see what we could do. In the beginning, we did a lot of things - we interviewed maids, residents, security guards, analysed the conversation log of a Whatsapp group of a gated community, and then we established our research question as follows:</p><blockquote>How is “care” practiced and experienced between residents and maids in gated communities? How is this changed by the app? Is it better or worse? What can we as service designers do about it?</blockquote><p>Our single-sentence definition of care, based on reading multiple papers is:</p><blockquote>Being actively mindful about the wellbeing and preservation of the people, things and processes in our lives that affect us and how we affect them in turn.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DnTu93wGB6TLk8Q8x2nHbQ.png" /><figcaption>How the themes from the paper “<em>Designing for Everyday Care in Communities” were used to think about possible outcomes of the studio.</em></figcaption></figure><p>We found <a href="https://hcdd.purdue.edu/everydaycareincommunities/">a paper that was a proposal for a workshop</a> that wanted designers and researchers to envision the future of care in design. We mapped out the themes from the paper and found two important learnings.</p><p><strong>First: </strong>whatever we made would have to be careful not to erase or trivialise the existing pathways through which care was conducted,</p><p><strong>Second</strong>: we should acknowledge how care is implicated in everyday interactions.</p><p>The list of activities that it had also provided a direction for us to proceed towards, which was great for us because it gave us a concrete scaffolding to structure our thought process.</p><p>We then started ideating on ways to get more information — and used the principles of Research through Design or RtD to develop an activity where we handed a “care package” to domestic help that worked in gated communities as a way to get more insight into their lives and attitudes and expectations towards care. You can read more about our activity and what we learned <a href="https://medium.com/gigs-service-systems-platforms-and-design/care-rubric-the-first-iteration-74ef4cde40be">here</a>.</p><p>We mapped out what we learnt from our interactions, and then developed what we called the “<strong>Care Rubric</strong>” : a framework by which we can <strong>identify and assess various opportunities or gaps of care</strong> in a service ecosystem.</p><p>We then applied that rubric to the MyGate app-platform-service and identified “gaps in care” as well as ways to possibly engage with them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Slfouc6e6xbWH9h4GKlwfg.jpeg" /><figcaption>Our Care Rubric that we developed</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4miTKuwruk_bcQ_wcG54Q.png" /><figcaption>Applying the Care Rubric to the MyGate service</figcaption></figure><h3>What I Learnt from the Studio</h3><h4>Service and experience design is not a silo.</h4><p>We cannot design services without at least acknowledging the effect of larger patterns and processes that have shaped the context around which the service exists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r97hFQF0idej9pC_MYFQMA.jpeg" /><figcaption>A visualisation of our Literature Review for this project</figcaption></figure><p>In our literature review above, we had identified a whole host of historical and macro trends that fed into the rise of gated apartment complexes and community management apps. This helped us look at the work we were doing and the contribution we were trying to make as part of a bigger whole, and not an end in itself.</p><h4>The unique contribution that designers can make to understand the world</h4><p>Multiple times, <a href="https://medium.com/u/b7100ff3bec7">Naveen</a> asked us to ask ourselves — what is the work that we are doing, and how is it different from what a sociologist or ethnographer would do? The answer lies in what Nigel Cross calls “Designerly ways of Knowing” — where we create new knowledge about the world by making things and seeing how people react to them. We made a lot of things and we showed them to people — and through their reactions we learned more about the larger processes and dynamics that were at play.</p><p>This also gave me an appreciation for the process of physical, tangible <br><em>making - </em>which gave me, as Jon Kolko puts it in his <a href="http://www.themoderniststudio.com/2018/04/16/the-rise-and-fall-of-corporate-design-education/">article</a>,</p><blockquote>a respect for the medium I was using, an understanding of how important details are, a pattern language of design problems to draw from, <strong>an intuitive sense for how to go about solving a problem</strong></blockquote><p>I cannot emphasise how important this was. The act of making, of physically and visually mapping the processes we saw and the stories we heard, helped to make these concepts clear in our heads in a way that nothing else could.</p><h3>How I grew as a Designer from this Studio</h3><p>This studio was not like any other educational experience that I have been through before. During the course of studio, I found myself grappling with fundamental questions about what design ​<em>is</em>, w​hat it ​<em>does</em>,​ and the ​role​ of designers in society today. While part of that was because of the vast scope of the problem we had chosen, a larger part came down to the fact that for the first time I was forced to think in terms of “systems” and “processes” instead of users and interactions. And that changed a lot of things.</p><p>We now live in an era where, thanks to the amplifying potential of digital technology, a designer’s work can affect the lives of not just tens or hundreds, but millions and billions of people. Designers today are in a position to dictate the ways in which people use technology — and in turn the ways in which they access their money, go to work, talk to their friends and family and myriad other things — and over the course of the studio, I have now come to feel that the ​nature​ of design practice needs to radically change to incorporate not just material, aesthetic or commercial considerations, but also <strong>moral and ethical concerns. </strong>This leads me to my next point.</p><h3>Forget about the Future of Work. Pay Attention to the Right-Now Instead.</h3><p>Building on that, the kinds of labour practices and patterns and processes we establish early on, in the services that we design, will in an age of increasing automation and digitalisation will become the norm for a majority of workers 10 or 20 years from now. While in a sense it pertains to that much bandied-about term the “future of work” — I would argue that designing with care as integral value has real immediate relevance to the “right-now” of work. When I say that I refer the emerging set of labour practices and “unwritten rules’ that are being created by gig economy platforms and services (Dunzo, Swiggy, Uber etc).</p><p>Within them, I see a worrying tendency for the creators of these digital technologies and platforms that are steadily expanding and employing ever-growing legions of people, to try to box human interaction, with all its messy complexity and potential to spark joy and solidarity — into impersonal, give-and-take transactions mediated by a swipe on the screen. I think this is a big problem and that we are not paying enough attention to it.</p><h3>Conclusion</h3><p>There is more to living and working conditions than simply the give and take of wages. Barack Obama said in a <a href="http://nymag.com/intelligencer/2018/07/obama-says-we-live-in-strange-times-in-major-speech.html?gtm=bottom&amp;gtm=top">speech</a> last year:</p><blockquote>“It’s <strong>not just money </strong>that a job provides; it provides dignity and structure and a sense of place and a <strong>sense of purpose</strong>.”</blockquote><p><strong>Can these gig economy platforms and services be designed to incorporate the everyday interactions and kindnesses that make work not just bearable but meaningful?</strong></p><p>I think the answer is yes, and that our care rubric has made a contribution towards the discussion around this.</p><p>I end with a quote from <a href="https://medium.com/u/d063bcc552df">Shannon Mattern</a> from her amazing article “<a href="https://placesjournal.org/article/maintenance-and-care/">Maintenance and Care</a>” who says,</p><blockquote>If we apply “care” as a framework of analysis and imagination for the practitioners who design our material world, the policymakers who regulate it, and the citizens who participate in its democratic platforms,<strong> we might succeed in building more equitable and responsible systems.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f21007bcb86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gigs-service-systems-platforms-and-design/studio-reflection-probing-into-services-systems-and-infrastructures-3f21007bcb86">Studio Reflection: Probing into Services, Systems and Infrastructures</a> was originally published in <a href="https://medium.com/gigs-service-systems-platforms-and-design">Gigs, Service-systems &amp; Platforms, and Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I did and learnt from my ten-day “Sprinternship” at Uncommon]]></title>
            <link>https://medium.com/@NCResq/what-i-did-and-learnt-from-my-ten-day-sprinternship-at-uncommon-8adca93ddbf1?source=rss-39b85dda25e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8adca93ddbf1</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[N Chandrasekhar Ramanujan]]></dc:creator>
            <pubDate>Mon, 03 Dec 2018 18:39:13 GMT</pubDate>
            <atom:updated>2018-12-03T18:39:13.467Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zEfrJU69ON9p2GYoi9ADQQ.jpeg" /></figure><h3>Introduction</h3><p>I saw this tweet from Rahul while my exams were going on at Srishti, where I am studying my Master’s in Human Centred Design</p><h3>Rahul Gonsalves on Twitter</h3><p>Yo, fellow designers: we&#39;re looking for a couple fantastic product designers. Let me buy you a coffee or croissant if you&#39;re either frustrated at your current workplace or you want to work at a progressive, future-looking company working on fun, diverse experiences?</p><p>I was interested, so I looked a bit more at Uncommon’s website, and saw that they were a design studio that seemed working on some really cool problems! I reached out to Rahul with a sample of some work that I did and we had a call, where I wanted to learn more about the opportunities that were available in UX Design and Research.</p><p>As I had my 2 week Diwali break in November, I realised that maybe I could come for 10 days as a quick “preview” and work on a small aspect of a problem. It would be a win-win situation. Uncommon would get some work that was of value to them, while I would gain experience and some stuff that would go on my portfolio!</p><p>I proposed this over the call, and to my surprise and delight, Rahul was interested. He discussed some projects Uncommon was working on, and later that day I sent a proposal outlining my various ideas for things that I could contribute to.</p><p>I joined on 8th November, and the “sprinternship” was conducted over 10 days, from 8th November to 18th November 2018.</p><h3>The Problem Statement</h3><p>Storyweaver is an initiative by Pratham Books. It is an online repository of children’s books in various languages. Its goals are to provide reading resources to young children all over the world, preserve mother tongue reading, as well as dying languages.</p><p>It currently hosts nearly 10,000 stories in over 120 languages.</p><p>Pratham Books is exploring a digital transformation and Storyweaver will be a big part of that. My job was to evaluate both the desktop and mobile platform, and to figure out what features should be in a Storyweaver mobile app.</p><h3>Research</h3><p>I first decided to see for myself. How would a reader go about reading a story on the site?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*43t8Lhe69KPGmWi_hWwTdQ.png" /><figcaption>What the series of screens for reading a book looked like</figcaption></figure><p>Then based on my own understanding of the situation, I mapped out the various reasons as to why people use e-reading products on mobile in general and a storyweaver application on mobile in particular.</p><p>I then looked at media articles and online chatter about Storyweaver on social media sites like twitter, facebook etc. I mapped out its goals as stated on the site, press coverage etc and also listed out stakeholders. I then outlined four possible avenues for an application, and settled on one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HKLLuwcP42jkgf7hy_27Yw.png" /><figcaption>Why do people read stories in general and Storyweaver in particular?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*GH3wmaKrc9zmvfe5OZinSw.png" /><figcaption>Results of further brainstorming</figcaption></figure><h3>Initial Iteration</h3><p>Initially, I thought that the app would focus on the core consumption of stories and flash cards. This was corroborated by my client meeting with Purvi from Storyweaver and Arpit from Datakind. From the meeting, I learned that 65–70 percent of users would access from mobile — and stay on the site for 2–2.5 mins on average, and read less than one story on average.</p><p>The flow on mobile would need to support browsing and quick discovery behaviour. Given limited attention spans, the goals should be to serve content in front of the consumer as quickly as possible. I thus needed to optimise the application for content consumption on the go, as well as make it work on small screens for small groups, and we would thus need to adapt stories to mobile.</p><p>Secondly, Storyweaver understood that the primary purpose of both the desktop and the mobile site is the consumption of content, however we also needed to take into account educators, who are its core target group. The functionality of the proposed app thus would need to include features that are especially useful for educators.</p><p>Below you can see my sketches and notes for the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NzkTpGw6cLC-Sq7K7gt15g.png" /><figcaption>My initial set of sketches and notes for a primarily consumption-based app</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*EEVeYWK5pzy52XgpoQyTtA.png" /><figcaption>Inspired by the NYT app, I explored how the Storyweaver app could quickly connect the reader with the story that they wanted</figcaption></figure><h3>But wait!</h3><p>Everything changed after I interviewed Radhika. She is an educator who conducts workshops with low income children every week to encourage reading. She either finds books through her own social network or through recommendations from teaching forums or Facebook groups.</p><p>She searches for books on Storyweaver and looks at the vocabulary, and context of the story since she works with low income students. She then takes the URLs of the story and curates a lesson plan which is a list of books and associated activities.</p><p>Radhika, while curating her personal list of books and activities — <strong>does this outside of storyweaver.</strong> There is thus an opportunity for Storyweaver’s application to include a lesson planning tool — where users can comment on and tag features of a story.</p><h3>This Changed Everything</h3><p>My interview with Radhika was an eye opener. I realised that my scope of the problem was too small. I had focused only on one feature, and the data I had received had only powered my confirmation bias.</p><p>The actions that Radhika was conducting while putting together a lesson plan could be all under Storyweaver’s ambit. There was no need for a separate document. I also stopped seeing the app only as a consumption platform. It could now also be used for <em>curation</em>.</p><h3>The New App</h3><p>I took in mind everything I had learned to prepare a new series of interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*g0UHuGE0cIUvPP4DDQzUIg.png" /><figcaption>The parent mode was removed, and finally only teacher and child mode was kept</figcaption></figure><p>The app would now contain <strong>four</strong> important features.</p><p><strong>First </strong>— A “child” mode for children to quickly and easily read the book on the app.</p><p><strong>Second</strong> — Reworking how the stories are shown on the app. Since there are a variety of book layouts (horizontal, portrait etc) we defaulted on a vertical infinite scroll. Images would be presented as is, divorced a little bit from the text, with the option to zoom in as required</p><p><strong>Third</strong> — Allowing users to create their own lists of stories and activities</p><p><strong>Fourth</strong> <strong>— </strong>Allowing users to deploy their lists in class based scenarios (this emerged as a feedback during the final presentation to the team)</p><p>I then made several sketches of possible approaches as to how we could change between the various mode, before finalising on a set of interactions which showed how a story could be navigated, and added to a list. I then presented it and my findings to the team, and made a crude prototype of it for the final presentation to the client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vo_bG0STY9NBfUhARnaVjw.png" /><figcaption>Crazy Eight Excercise — 8 possible sketches for the features in the proposed app</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TS2L26sIe-geHhGq1sz0Fw.jpeg" /><figcaption>Sketches showing how to add a story to a list and browsing through different stories</figcaption></figure><p>In my presentation to the team, one piece of feedback I received was that I also had to include the final interaction with the product, which I then worked on while making the final screens.</p><p>The reception to my product during the final presentation was very enthusiastic. In fact, Storyweaver was about to implement a similar list creation function on the website <strong>which was a validation of my design research and thought process!</strong></p><p>However, I have chosen not to share the final screens/mockup here since they contain intellectual property which is proprietary to both Pratham Books and Uncommon. Once the Storyweaver mobile application is released to the public I will add them to this post.</p><h3>What did I learn?</h3><p><strong>A) Design is about getting to the heart of the problem</strong></p><p>In the Design of Everyday Things, Don Norman says:</p><blockquote>Designers have developed a number of techniques to avoid being captured by too facile a solution. <strong>They take the original problem as a suggestion, not as a final statement</strong>, then think broadly about what the issues underlying this problem statement might really be.</blockquote><p>I kept going back and forth, constantly questioning the brief given to me. And when I didn&#39;t, my mentor at Uncommon, <a href="https://medium.com/u/7a19bc0990a3">Wolfram</a> was there to remind me of what I was missing, and also to bring me back on track when I went off the rails.</p><p>I could have chosen to focus just on reworking the reading experience. Instead, through research I realised that there was an overlooked problem that if solved, would make the product a lot more usable to Storyweaver’s intended education audience. The reading experience ended up being just one part of it.</p><p><strong>B) I shouldn’t actually fixate on the tools, themselves, but rather on the <em>processes</em> they support.</strong></p><p>In Behance and Dribble, you are bombarded with pretty screens and flashy animations when you look at portfolios and pages. As a student with not that much exposure to what the industry expects, I expected screen creation to be a more important part of my work. It wasn&#39;t.</p><p>I actually spent a lot of time doing research, figuring out the problem space, and getting to udnerstand what was actually going on. By the time I got around to actually <em>making </em>the screens, my internship was almost over. But because I knew WHY I was making the screen, and WHAT and WHO I was making them for, it took very little time.</p><p>The client also appreciated most off all my reasoning, logic and justification for the features I had chosen to include. From this, I got a better clarity of learning <em>why</em> prototypes are important, what they’re useful for, and how they fit into the overall research/design/testing/iteration cycle.</p><p>I also came to the conclusion that it’s easy to fetishize the artefacts(wireframes, mockups, prototypes, personas, journey maps, all that stuff), <strong>they are all just tools</strong> to facilitate the bigger process of solving the problem.</p><h3>Conclusion</h3><p>Uncommon is a really great place full of stimulating people and conversations. I learnt something new everyday about design and technology just from casually chatting with people and/or overhearing conversations and group discussions. I spent a lot of time browsing through the extensive library of world-class design books and the slack channel that was full of informative talks and articles.</p><p>The “sprinternship” was a resounding success. Both the team at Uncommon were very happy and impressed with the work that I have done. Most of all, I also learnt and grew a lot.</p><p>I had the chance to work on an exciting project, was able to talk to and pick the brains of some of the smartest people around about design, as well as shadow <a href="https://medium.com/u/7a19bc0990a3">Wolfram</a> in his meetings with clients and see how he works and deals with them, in order to better understand the skills it takes to be a professional designer. I am very grateful to <a href="https://medium.com/u/ea879e6c2fcf">Rahul</a> and <a href="https://medium.com/u/7b6fbf6263bc">Dhruv</a> for this opportunity, and look to return to Uncommon for a longer internship in Summer 2019, for which I am very excited to see where it goes :-)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8adca93ddbf1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do the benefits of artificial intelligence outweigh the risks?]]></title>
            <link>https://medium.com/@NCResq/do-the-benefits-of-artificial-intelligence-outweigh-the-risks-ce2876c8bfcf?source=rss-39b85dda25e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce2876c8bfcf</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[futurism]]></category>
            <category><![CDATA[t]]></category>
            <dc:creator><![CDATA[N Chandrasekhar Ramanujan]]></dc:creator>
            <pubDate>Tue, 11 Sep 2018 14:46:28 GMT</pubDate>
            <atom:updated>2018-09-11T14:46:28.274Z</atom:updated>
            <content:encoded><![CDATA[<h3>Do the benefits of artificial intelligence outweigh the risks? My entry for the Economist’s Open Future Essay Competition</h3><p>Widespread fears of AI and automation taking away jobs are overblown, but so is the conceit that AI is only good for automating routine, low level tasks. The truth, as always, lies somewhere in between.</p><p>AI is what Erik Brynjollfson at MIT calls a “general purpose technology” — like electricity or the internal combustion engine before it, it has knock-on effects, where its very presence leads to the creation of entirely new ways of producing goods and services, getting around and living.</p><p>In this case, it allows us to fundamentally rethink what we use computers for and what computers can do for us.</p><p>Before we go any further, its important that we understand what exactly it is that AI, and its most dominant sub-field, deep learning actually does. It essentially allows computers to recognise patterns in data that have been presented to them</p><p>As a deep learning programme is presented with more data about whatever task it has been assigned to do — detecting tumours from MRIs, recognising faces in selfies — the better it gets at that task. It does this through a more than 30 year old technology called “backpropagation” which among other things, allows itself, or its programmers, to retroactively tweak the statistical parameters that it uses to recognise patterns in response to new information or as the use case changes.</p><p>But the question still stands - what can it do? In order to understand that, it is useful to think about what new technologies, more generally can do for us.</p><p>Historians of science and technology note that new “general purpose technologies” bring about three kinds of benefits.</p><p>The first are “<strong>incremental benefits</strong>” where societies can accomplish ongoing activities with a higher level of efficiency — in the case of AI, companies can get better results for questions that they are asking right now with data that they already have.</p><p>One of the main implications of this is, as Ajay Agrawal of the University of Toronto points out in his new book “Prediction Machines”, is that the cost of making predictions — about consumer buying habits, traffic congestion, what viewers are going to watch next on their computers, will fall to the extent similar to how the cost of light fell 400 fold from the 1800s to today.</p><p>Among other things, this enables companies to be leaner and more efficient on a scale that was previously unthinkable. Large stocks gathering dust in warehouses as unsold inventory, for example, could soon become a thing of the past as companies use cheap predictions to produce and ship goods just in time for consumers to buy.</p><p>The second, “<strong>transformational benefit</strong>” to new technologies allows people “new ways to access services and support livelihoods”. What this means, in the context of AI, is that companies can ask new kinds of questions of the data that they already have with them. A lawyer in the discovery stage of a complicated trial, who has to study various precedents and case law, might search for emails which are classified as “angry” or ‘anxious’ or clusters of documents which are classified as anomalous or relevant to the case at hand — work that earlier took an entire team of paralegals weeks to accomplish.</p><p>The third — “<strong>production benefits</strong>” where new categories of economic activity are created thanks to new technologies — apply to AI in the sense that new data types open themselves up to interpretation and analysis by computers — while earlier they could not “read” audio, images or video in the sense that they could analyse the content for meaning and summarise what is happening — they can increasingly do that now.</p><p>At first glance, the implications are obvious, especially in people-heavy industries such as manufacturing and retail. Robots, while often having a very high up-front cost, over time end up paying for themselves since the only expense is maintenance and electricity, as opposed to flesh and blood employees for whom ongoing expenses like salaries and benefits are something these businesses would rather not deal with.</p><p>What a lot of would be AI adopters fail to realise, however, are that most deep learning systems, powerful as they are, are also extremely limited and heavily dependent on the data that they have been fed already. A neural network that recognizes images can be totally stumped when a one single pixel in the picture is changed — or if visual noise that’s invisible to humans is added. Self-driving cars often fail to navigate environments or conditions that they have not encountered before.</p><p>An AI system can be best likened to an idiot savant or a particularly powerful pocket calculator. Deep learning as it currently is used today will not result in a sapient intelligence that abstractly reasons and makes generalized assumptions about the world. As it stands, it is unlikely to automate ordinary human activities by itself.</p><p>Further, a common mistake a lot of people make is to think of careers as a single overarching monolithic entity instead of what they actually are — a collection of discrete tasks each of which are different in terms of difficulty and susceptibility to automation. AI and ML will eliminate some of these “jobs to be done” while also creating entirely new ones. Policymakers and governments need to understand this.</p><p>The fact is — that careers which involve some element of human creativity and imagination will very probably never be fully automated. People who can do stuff that computers cannot do will continue to charge a premium in the job market. Education systems need to respond to this as well. Students don’t need to learn how to add, subtract, or memorise times tables or historical dates. Skills pertaining to communication, working well in remote teams, being able to work independently of supervision — will be increasingly vital.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce2876c8bfcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>