<?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 Noel Braganza on Medium]]></title>
        <description><![CDATA[Stories by Noel Braganza on Medium]]></description>
        <link>https://medium.com/@noelbraganza?source=rss-9c4aa3408084------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*t-hTaGrKV4mOgg7G0wCQag.png</url>
            <title>Stories by Noel Braganza on Medium</title>
            <link>https://medium.com/@noelbraganza?source=rss-9c4aa3408084------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:29:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@noelbraganza/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[Open Letter to Google (and Apple)]]></title>
            <link>https://medium.com/@noelbraganza/open-letter-to-google-and-apple-497f58688e63?source=rss-9c4aa3408084------2</link>
            <guid isPermaLink="false">https://medium.com/p/497f58688e63</guid>
            <category><![CDATA[symptoms]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[open-letter]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[coronavirus]]></category>
            <dc:creator><![CDATA[Noel Braganza]]></dc:creator>
            <pubDate>Sun, 05 Apr 2020 18:58:25 GMT</pubDate>
            <atom:updated>2020-04-05T18:58:25.279Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZURkMSNTJUcNkoiA75fUQ.png" /></figure><h4>‍‘Not compliant’ — Two words that are killing Coronavirus app innovation</h4><p><em>This letter was published on the </em><a href="https://www.mysymptoms.app/open-letter-to-google-apple-my-symptoms-app"><em>My Symptoms App</em></a><em> website as a response and an appeal to both Google and Apple to remove blanket bans on honest developers that are trying to innovate solutions to innovate during this crisis.</em></p><p><strong>Dear Google (and Apple),</strong></p><p>Extraordinary times call for extraordinary measures.</p><p><a href="https://www.nytimes.com/2020/04/01/world/europe/coronavirus-science-research-cooperation.html">Scientists and academics the world over are racing to study the coronavirus</a> — to sequence the genomes of the virus behind it (among other things) so that they can understand how it spreads, design treatments and vaccines for it, and track its evolution.</p><p>Speed is imperative because over three months after<a href="https://www.who.int/csr/don/05-january-2020-pneumonia-of-unkown-cause-china/en/"> China first told the World Health Organisation (WHO)</a> on December 31 that it was treating unusual cases of pneumonia in the city of Wuhan, there are over one million confirmed Covid-19 cases across the world, and the body count is adding up:<a href="https://ncov2019.live/"> 59,188 as on April 4</a>.</p><p>It’s April now and we<a href="https://www.bbc.com/news/health-52006988"> still don’t have answers to so many Covid-19 questions</a> and a<a href="https://www.theguardian.com/world/2020/apr/03/when-will-a-coronavirus-vaccine-be-ready"> vaccine is at least 18 months away</a>.</p><p>In short, this is an emergency. Time costs lives.</p><p>Here’s an example of how scientists and researchers — a notoriously speed-averse community — have changed the way they work.</p><p>The<a href="https://www.nytimes.com/2020/04/01/world/europe/coronavirus-science-research-cooperation.html"> <em>New York Times</em></a> reported on April 1 that scientists at the University of Pittsburgh recently made a discovery that could have implications on animal vaccine testing for Covid-19. Ordinarily, scientists would have started work on an article for an academic journal following this discovery, the report said.</p><p>“‘But you know what? There is going to be plenty of time to get papers published,’” it quoted Paul Duprex, a virologist leading the university’s vaccine research, as saying.</p><p>The article said: “Within two hours, he [Duprex] said, he had shared the findings with scientists around the world on a World Health Organization conference call. ‘It is pretty cool, right? You cut the crap, for lack of a better word, and you get to be part of a global enterprise.’”</p><p>Why has Google then, during this global pandemic, chosen to stick to the rule book and bar global innovators from publishing Covid-19 apps to the Google Play store?</p><blockquote>Understand the urgency, Google.</blockquote><p>But first, let’s get this straight: We understand that both Google (and Apple) must have stringent conditions to control the kinds of apps being uploaded on the Play and App stores to prevent bad actors from profiteering from the fears of people worried about Covid-19.</p><p>A blanket ban on listing apps, however, will do more harm than good. You must assess each application on merit. You must not assess Covid-19 submissions with rules that existed before December 31. These are extraordinary times.</p><p><strong>About </strong><a href="http://www.mysymptoms.app/"><strong>mysymptoms.app</strong></a></p><p>Our bid to list on Google Play an app that we designed over a weekend while in quarantine in Australia and Sweden was met with a boilerplate response. “We don’t allow apps that lack reasonable sensitivity towards or capitalize on a natural disaster, atrocity, conflict, death, or other tragic event,” the email from Google said.</p><p>Our app is a free Coronavirus symptom tracker that is designed keeping three stakeholders at the centre: users, frontline healthcare workers and researchers. It was born from personal experience, of the anxiety that ensued when three family members started showing symptoms and had to go for a drive-in Covid test.</p><p>The app isn’t trying to diagnose people. It simply collects granular data about how certain Covid-19 symptoms manifest in individuals or clusters even before they decide to seek medical help.</p><p>This historical information helps anxious users keep track of symptoms whose details they may not accurately recall a week later.</p><p>A doctor we spoke to said any symptom history information is useful because the date of symptom onset is an important factor in deciding when a Covid patient may be safe to go home, but many patients struggle to remember when their symptoms started.</p><p>Each patient’s symptom history will also hopefully give researchers a clearer understanding of how the virus spreads and how symptoms evolve during infections.</p><p>The app is simple at its core, and keeps the user at its centre. It provides value to users, which is important as that leads to regular usage, which determines the quality and quantity of the data being generated. Apps that provide clear value and utility to users are those that are used again and again, says <a href="https://www.thinkwithgoogle.com/consumer-insights/mobile-app-marketing-insights/">Google’s own research</a>.</p><p>The app has been submitted to a number of Covid-19 hackathons. But as we understand it (and do correct us if we are wrong), we will need government or institutional backing if we want to list this app on the Google Play store.</p><p>We are a motley bunch of designers, developers, journalists, PR professionals and marketers who collaborated across continents to try and do something helpful for society. Between us, we have several years of experience in swiftly shipping digital products, taking them to market and scaling them globally. What we don’t have yet is government or institutional backing. Though we are working on getting this support, we are losing valuable time.</p><p>So, here we are with an app that can possibly help people, frontline healthcare workers and the global research community to understand Covid-19 better, but with no way to even get people to test it on Google Play or the Apple App store.</p><p><strong>My Symptoms vs others</strong></p><p>You may argue that there are other apps that do the same thing as ours — for instance the<a href="https://theconversation.com/our-free-coronavirus-symptom-tracking-app-has-been-used-by-two-million-people-heres-what-were-learning-134923"> COVID-19 Symptom Tracker App</a> developed by King’s College London and the<a href="https://www.howwefeel.org/"> How We Feel app</a> that’s developed in part by the CEO of Pinterest.</p><p>We are excited about the potential of these apps to help in the fight against Covid-19. In our opinion, however, they have some shortcomings. The first is limited to the UK, and both neglect to put the user at the core of the experience, which, in our experience (and Google’s evidently), is what determines whether a user will use it in the first place.</p><p>Additionally, to our knowledge, no apps have so far been designed to solve problems for those at the frontlines of this battle: volunteers, paramedics, nurses and doctors. Old school paper and pen forms are still being passed around drive-through testing centres, for instance, exposing healthcare workers to risk.</p><p>The<a href="https://www.mysymptoms.app/"> mysymptoms</a> app plugs all these holes. It puts the user and healthcare worker at the core of the experience, and is not limited to a geographic area.</p><p>Additionally, we are committed to the following:</p><ol><li>We will not profit from this app. That is, we do not intend to “capitalize on a natural disaster, atrocity, conflict, death, or other tragic event.”</li><li>All data input will be saved on the user’s phone unless they consent to share it.</li><li>All shared data will be free for researchers to access.</li></ol><p>So, don’t stifle innovation, Google. We don’t claim to be doing the important work of scientists, but even you will surely agree that every effort counts. People are dying. The global research community needs any knowledge that can stop Covid-19 in its tracks. Do reconsider your policy and review our application and similar non-profit applications submitted by others. If you don’t, all we would have lost is a few days of our lives. But the world could lose much more.</p><h4>Video: <a href="https://youtu.be/2AIi8j6Lo-c">My Symptoms App</a></h4><h4>Website:<a href="https://www.mysymptoms.app/"> mysymptoms.app</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=497f58688e63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to start projects right]]></title>
            <link>https://medium.com/@noelbraganza/how-to-start-projects-right-8e9734d681?source=rss-9c4aa3408084------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e9734d681</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Noel Braganza]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 12:20:35 GMT</pubDate>
            <atom:updated>2019-08-12T22:02:08.187Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Run a Digital Project Smoothly in 3 Simple Steps</h3><h4><em>Digital projects are covered in a fog of buzzwords and new working methodologies. How do you get everyone on the same page?</em></h4><p><em>This article was originally published on </em><a href="https://www.upstrategylab.com/blog/how-to-start-projects-right"><strong><em>www.upstrategylab.com</em></strong></a></p><p>Digital projects often have a large entourage of cooks. By that I mean multiple stakeholders such as the product development and design team, different client departments, CEOs and others — all of whom want a say in the final delivery (as they should).</p><p>But not all stakeholders are acquainted with product development and design thinking processes. Neither are they necessarily aware of what technology enables. Their opinions about <a href="https://www.upstrategylab.com/blog/how-to-make-a-successful-digital-transformation">digital transformation</a> are also most likely formed by what they have read online, not out of experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v5i94OCdMtOFPDiu.jpg" /></figure><p>Because of this, during the first digital project stakeholder meeting, its participants often tend to pull in different directions. At the end of such meetings, it is common to find that no two stakeholders are on the same wavelength about the project’s deliverables.</p><p>So the question is: If a disparate set of people across a company’s different departments collaborate on a project that deals with a subject many of them are quite unfamiliar with, what is the best way to begin? How can the company ensure that the project is executed most efficiently, and succeeds?</p><p>In my experience as a designer and strategist handling digital innovation in organisations, projects that follow the three-step workflow outlined below are more likely to succeed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z6iKX8W0s5-Nx7MR.jpg" /></figure><p>‍</p><p>‍</p><h4>1. Kickoff — Let’s all get on the same page.</h4><h4>2. The Project — We have a lot to deliver, let’s collaborate well.</h4><h4>3. Retrospective — What did we learn from this project?</h4><p>‍</p><p>‍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j_NRyVv3-uxFl4ET.jpg" /></figure><p>‍</p><p>The beauty of this process is that it can be as granular as you want it to be. You can start with an overview of the whole project, or zoom down to a specific function that you want to work on. Use this process whenever there are multiple stakeholders and expectation management is key.</p><h3>The Kickoff</h3><p>Ensure that a “kickoff” is held as soon as a project is initiated. Holding this meeting will allow you to manage expectations and quickly illustrate which direction you will be heading for the duration of the project. This is why the kickoff must include all stakeholders.</p><p>A kickoff is essentially a knowledge sharing session. For some, it is a day of Post-Its and Sharpies. For others it is a fun break from work routines. Whatever the motivation, its participants must come prepared and share as much of their knowledge during the session so that the project delivery team runs with that information and can deliver value at the end of the project.</p><p>I’m assuming here that the delivery team has already held its own internal meeting and are now well aware of the project goals, stakeholders involved and time-plan to complete the project.</p><h3>So what goes into the kickoff?</h3><p><strong>1. Team introductions </strong>— It’s difficult to work with someone if you don’t know who they are or what their objectives are. Team introductions help fix this. The introductions can be informal with some banter so that all participants get a sense of the energy in the room.</p><p><strong>2. Discuss the initial project offer that led up to this kickoff </strong>— What brought you all to the table to start talking about the project? What was promised and what was discussed about the time-plan and the scope? You don’t need a deep dive into this topic, but it’s good for everyone in the room to get a quick understanding about why they are there.</p><p><strong>3. Understand the goals of each stakeholder involved </strong>— This is an important step. Not everyone at the table has the same goal or vision for the project. Motivations also differ: for some it’s personal KPIs, others have been told to deliver a project by the management, and on occasion the project is initiated because of leftover annual budgets. Whatever the reasons, the project delivery team at the kickoff must ask enough questions to get an understanding of these goals and motivations and identify a way to take into account the stakeholders’ personal goals too by making the upcoming collaboration exciting for everyone.</p><p><strong>4. Collaboration methodology </strong>— It’s important to identify early on what are the tools each team should use to collaborate so that there is no confusion later. This is a crucial yet often ignored part of expectation management. For example, is everyone expected to use Skype for Business or Google Hangouts, or Slack or Google Documents or Microsoft Sharepoint? Specifying what tools will be used early on ensures efficiency in workflows across teams. Basically, any process that can be streamlined to avoid corporate bureaucracy or confusion must be discussed early in the project.</p><p><strong>5. Planning for speed bumps </strong>— All projects will have speed bumps. You could choose to be reactive towards them, or you could preempt them and talk openly about the issues you might encounter during the collaboration. It could be something as mundane as access to content, file-sharing access, or something even more critical such as not getting complete stakeholder buy-in in time.</p><p>‍</p><h3>The Project</h3><p>This broadly refers to the time period during which the project is being executed. Since there are many jobs to be done that are vast and often more complex, a rough project time plan must be set so that a weekly rhythm is set with the project team and stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PYF2SGZlewK83pOH.jpg" /></figure><p>A rough project time plan must be set so that a weekly rhythm is set with the project team and involved stakeholders.</p><p>Weekly “sync meetings” with stakeholders as well as “project gates” with the project delivery team must be defined. These gates can be used to ensure that project owners get the necessary buy-in from all stakeholders at the right time. In order to run projects that have a limited time and budget, it is important that these steps are planned into the workflow.</p><p>In the case of digital projects, a typical project gate would come after the <a href="https://www.interaction-design.org/literature/topics/ux-design">user experience (UX)</a> and prototype testing phase. This is set so that when the user interface design work is ongoing, no one attempts to dig up the foundation (the previous step) as that will simply be inefficient and frustrating for those running the project.</p><h3>So what are the actions one can take to ensure a smooth project phase?</h3><p><strong>1. Weekly syncs and daily stand-ups</strong> — Ensure that weekly meetings are conducted with external stakeholders, and daily stand-ups are conducted with the project delivery team. This allows even those who are not participating in the actual design and development of the project to be involved enough to be able to get their points of view, experience and ideas across to the team running with the project.</p><blockquote>A note of caution: You must ensure that the weekly stakeholder sync meetings do not turn into a weekly delivery meeting. They must be treated as a collaborative work session where the delivery team is not focussing on building presentations for stakeholders. This must be a status meetings leaning more towards open discussions and collective problem solving.</blockquote><p><strong>2. Milestones and checkpoints </strong>— An efficient project plan will often have a few milestones set into the future so that the project is continuously moving towards smaller milestones that the team can build on, measure, and learn from.<strong>‍</strong></p><p><strong>3. Project owners and their responsibilities</strong> — A project owner must be an active part of the implementation team and also of planning. This is to ensure that the project owner, who is responsible for the delivery of the project, can empathise with any problems the team runs into and ensure that the broader vision of the project is in sync with the vision of the upper management. Typically those directly involved in the production/development of the project should rise to this role. But be aware that this role is not necessarily project management. The last thing you want is management leading more management leading more management… you get the drift.</p><p><strong>4. Waterfalls belong in nature </strong>— Ensure that your project team doesn’t work in isolation or in silos. Often, the project delivery team is broken up into smaller teams and assigned a specific task each. When there is a lack of project ownership and understanding of its vision across the delivery team, these smaller teams finish their work without really understanding how their tasks contribute to the success of the entire project. This, naturally, affects the quality of work done. The team that takes over for the next step struggles to incorporate that work into the project. This is not only a waste of time and a blow to efficiency, such situations are often a big risk to the health and success of the project. This is why any good team must not be scared of asking the question “why?” Everyone should know what the big picture is.</p><p><strong>5. Don’t be afraid to pivot</strong> — As many wise entrepreneurs have said, failure isn’t necessarily a bad thing as long as you can realise it and take the necessary steps to regroup. Realising something is failing early on is the only way you can take necessary actions to succeed going forward. You can’t fix an oversalted pot of food by adding more salt. Just throw the dish out and start over already.</p><p>This brings me to my final step.</p><h3>Retrospective</h3><p>Often managers and even team members forget or don’t prioritise this phase of a project. But this is an important step especially when the top management wants a team to take more ownership of their work. Holding a retrospective is also the surest way of knowing if the team worked well together or not. This will help the company in future projects.</p><h3>But what exactly is a retrospective?</h3><p>It is the process through which a team can reflect on their successes and failures while working together. It is a forum that gives team members a chance to acknowledge and voice their understanding of how the project unfolded — both the good and the bad. It will allow the team to grow collectively, move on from their mistakes, and hopefully not make them again.</p><h4>How is it conducted?</h4><p><a href="https://www.atlassian.com/blog/jira-software/5-fun-sprint-retrospective-ideas-templates">There are many techniques available</a>. But if you have followed the process of a project time plan as shown above, draw it out on a whiteboard. Now tackle each phase, asking participants around the room to list what was the “good” and “bad” in each phase. If you don’t want to use the word “bad”, you can use “Areas of improvement” :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w5hpJ0ATvOb-8Crc.jpg" /></figure><p>Retrospectives are a useful way of collectively reflecting as a team</p><p>‍</p><p>The “good” and “bad” listing in a project isn’t necessarily restricted to just the team’s performance, but also the collaboration with the stakeholders and management. It could be about time-plans, budgeting, scoping, delivery pressure among other things.</p><p>Here are four recommendations to get the most value out of a retrospective.</p><p><strong>1. The project lead shouldn’t lead the retrospective </strong>— Someone other than the project lead must lead this meeting as that allows the discussion to be less of a report card session and more of a team discussion aimed at working better going forward.</p><p><strong>2. Ask questions like </strong>— What worked well? What was lacking? What did you learn? What do you long for going forward?</p><p><strong>3. It’s not personal — </strong>Don’t make your comments personal or take any feedback personally. Retrospectives must be a safe space to voice an individual’s concerns or point of view.</p><p><strong>4. Action points and clear next steps — </strong>Don’t just conduct the retrospective and toss all the notes into the post it pile from hell. It is important to document the discussion points and address them at any subsequent kickoffs to ensure that those mistakes are not repeated in future projects.</p><p><a href="http://www.noelbraganza.com/"><em>Noel Braganza</em></a><em> is the Co-founder and Chief Innovation Officer at </em><a href="http://www.upstrategylab.com/"><em>Up Strategy Lab</em></a><em> - </em>a design-driven and customer-centric business laboratory that helps mid-sized companies scale up and digitise .<em>and has a background in Interaction Design and research experience from the </em><a href="https://design.mit.edu/"><em>MIT Design Lab</em></a><em>. He uses a design driven approach as a key methodology to develop digital products within various sectors across IoT systems, Connected spaces, Smart Cities, Automotive &amp; Telematics, FinTech and MedTech industries.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e9734d681" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make a successful digital transformation]]></title>
            <link>https://medium.com/@noelbraganza/how-to-make-a-successful-digital-transformation-b56108b0e2f9?source=rss-9c4aa3408084------2</link>
            <guid isPermaLink="false">https://medium.com/p/b56108b0e2f9</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[digitization]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Noel Braganza]]></dc:creator>
            <pubDate>Sun, 07 Oct 2018 21:22:31 GMT</pubDate>
            <atom:updated>2019-04-15T21:36:22.023Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This was first published on my website </em><a href="http://www.noelbraganza.com/digital-transformation"><em>www.noelbraganza.com</em></a></p><p>In today’s world, staying competitive and innovative seems to be on the tongues of every board room. The term ‘<em>Digitisation</em>’ is sometimes loosely thrown around as the solution to falling profits and staying competitive in the market. Unfortunately to most companies, digitisation simply means, getting online. To the rest… well it still means getting online too.</p><p>But digitisation is more than that. It simply means, the ability to be efficient, rapid and able to adapt in order to stay ahead of the pack using design and technology as enablers. All processes, systems and organisational structures that act against such intentions, will play a huge part in why some digital transformation initiatives will fail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eknuy-FGpNWELOK-vKb9Tg.png" /></figure><p>For digital transformations to be successful, they must permeate through every team and department. The process requires an open minded approach as well as preparation and understanding of how data, design and technology will impact them across teams — HR, finance, purchasing, marketing and even the product team.</p><p>One of the most important factors that contributes towards the success of such a transformation is the company’s ability to handhold and guide the entire team across the organisation on this journey, even if that means taking outside help. Even here, design thinking plays a big role in how to engage the organisation towards a common vision and purpose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p-rG2qUW4EPtyoQja5hNgg.png" /></figure><p>After working at the MIT Design Lab in Massachusetts USA, and in one of Sweden’s most successful Digital Product Design companies, The Techno Creatives, I have advised, inspired and helped different industry players on how to use a few principles of design thinking to their advantage. Along the way, I have learned why some succeed and many fail.</p><h3>A common story</h3><p>Let’s take an example, <strong>Company X </strong>is successful because they create some of the best drilling tools. They have hired some of the best engineers, researchers, analysts, industrial designers, sales managers, marketing, operations and project managers. Now this company has done for years what it does best, which is, provide the best darn drills one can want. Fast forward a few years to today, smarter drills complete with inbuilt sensors and added connectivity flood the market. This makes Company X look outdated and suddenly they are playing catch up to build the necessary framework, processes and systems in order to produce competitive products. They need to catch up or face becoming redundant. Software and user centric design will soon become a big part of the company’s vocabulary. And with this will come a slow and often expensive learning curve.</p><h4>Management rules</h4><p>In comes an order from top management about the requirement to digitise their existing arsenal of robust drills and hardware. Most members of top management understand the benefits of digitisation to stay competitive</p><p>They are fairly convinced albeit ignorant of the true meaning of digitisation (agile, iterative, experimental, data driven …) But older companies are just wired differently. Their expertise and work process still doesn’t support digitisation, since it is based on broad management validation processes that often works in a completely opposite direction to that of digital product development. It’s slow, requires constant stakeholder buy-ins and approvals, and by the time they come in, the technology and product proposition is outdated. The old adage of<em> “Too many cooks…”</em> seems quite apt for such decision making processes. In the end a project that could have been tested and built in a few months takes two years and a budget best not mentioned aloud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-iq3QWBOaU2B2IwpkvrNGw.png" /></figure><h3>Go from nothing to something. We all need quick wins</h3><p>Some companies bring on board strategic consultants, who try to infuse the various different methodologies such as Agile, Workshop, Design Thinking, and Brainstorming into the vocabulary of a company. All these methodologies and techniques are indeed very important for a team to develop an understanding of what digitisation means.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VjdvwH9rtP92pN9X50ORBw.png" /></figure><p>What digitisation truly means is the ability to go from zero to 100 in a short time, with a small budget but a big impact. You spend more of your time doing and making than only thinking. Don’t get me wrong, however. Thinking is extremely important, but if your process ended there, you’re doing it wrong. Partner with those who can help you think and also take you to a point where you have something tangible. Something of a quick win. Don’t end up with great presentations and concepts that will die in a powerpoint somewhere that no one will read.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QlpUQX5QRNvAfCHPkVQkQA.png" /></figure><h3>A few ideas to help you succeed</h3><h4>1. Picking the right team</h4><p>Digitisation needs decision makers who are willing to put their ass on the line. And one can only do that if they truly understand what the medium offers, both from a technical and design point of view. Having a deep rooted knowledge of design thinking and technical limitations and opportunities allows strong decision makers to help product development move forward quickly because that method is iterative and mastered through trial and error, all validated by realtime data, linked to product performance as well as looped back into product development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VN801Nk7Pyam9r3g8fw5DA.png" /></figure><h4>2. Partner with those who help you ’ Think’, but also help you ‘Make’</h4><p>It’s important to hire the right people to lead the digital expansion of your team. That is usually a difficult thing to do especially if the management team themselves don’t know what to look out for while hiring. The easiest thing to do at the start is working with firms that focus on design driven innovation that can help onboard and train your existing team to get a better grasp of how to build a culture of innovation and design by understanding the possibilities technology and user centric design offers your product offering. This way, over time, you can continue to grow expertise within the team and let the knowledge gained circulate within the team itself.</p><p><strong><em>Rule of thumb while growing your own talent</em></strong></p><p>One rule of thumb for hiring the right team especially within digitisation is to ensure you hire problem solvers, quick learners, doers and makers. This field is changing faster than you can say Jack Robinson. Get a team that’s quick to adapt, change and loves learning new things. It’s the Age of the Generalists.</p><p>A team consisting of heavy project management goes nowhere. What you want to develop is project ownership where a few members in the team take on a greater ownership for smaller projects, allowing them to behave as a mini startup that runs fairly autonomously, but still has some connections to the mothership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AThq8nCtxzE3mlENmJnoZQ.png" /></figure><h4>3. Mix a new team with the old team</h4><p>Your current team was organised keeping in mind the older delivery process and working methodology. It’s almost unfair to assume that the existing team can transform overnight, after all they have been a well oiled machine for a long time before software, data and human centric design came along.</p><blockquote>A forceful transformation will only lead to internal resistance to change.</blockquote><p>A newer team that brings in new working and collaboration techniques can help infuse a different and possibly faster way of product development. <em>Workshops, stand-ups, demos, prototyping, problem making, brainstorming, testing, sprints will all become a part of the team’s vocabulary soon</em>. Don’t be afraid to fail. Some of the greatest learnings come from failure.</p><h4>4. Test and validate technical requirements early</h4><p>Let’s go back to Company X. Now they provide a drill that is no longer just a simple drill, it is a drill that needs to communicate with it’s owner, advises them about the drill-bits that need to be used, and also help them order spare parts a the press of a trigger.</p><p>So how does one make that happen? Software of course. But how do you know what knowledge you should build and develop internally and what you should buy off-the-shelf. Along with this, it’s important to quickly realise what actual benefits technology offers your business and what changes are worth transforming for. Not all technology might be relevant for you, and you will realise that not all needs to be developed by you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CHxMCTGZygQjXsngZ7f_6g.png" /></figure><h4><strong>5. Don’t put all your eggs in one basket</strong></h4><p>Don’t allocate all your budget in a single two year long project the way you might have in the past. Allocate smaller chunks of budget to smaller projects with the intention of achieving small quick wins and proof of concepts. The good thing with technology is that you can quite quickly make something work good enough in order to see if you want to spend more money in developing the idea further.</p><h3>So, why do companies fail?</h3><p>I’ve identified many reasons, but two stand out as one of the major issues holding companies back.</p><blockquote><em>1 .Trying to innovate using existing work processes. (Internal resistance, lack of competence, organisational structure)</em></blockquote><blockquote><em>2. Realising you need to hire a team, but then making them innovate within your existing work processes.</em></blockquote><h3>So the question is, can Digitisation take root in bigger, more complex organisations?</h3><p>And the simple answer is, yes of course, if done in the right way with the right partners and internal stakeholders that are in a position to make decisions.</p><p>Digital transformations need not be costly or pointless, it’s a process that’s constantly evolving and it is this process that companies need to be open minded about.</p><p><a href="http://www.noelbraganza.com/"><em>Noel Braganza</em></a><em> is the Co-founder and Chief Innovation Officer at </em><a href="http://www.upstrategylab.com/"><em>Up Strategy Lab </em></a><em>and has a background in Interaction Design and research experience from the </em><a href="https://design.mit.edu/"><em>MIT Design Lab</em></a><em>. He uses a design driven approach as a key methodology to develop digital products within various sectors across IoT systems, Connected spaces, Smart Cities, Automotive &amp; Telematics, FinTech and MedTech industries.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b56108b0e2f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Look ma, no hands!]]></title>
            <link>https://medium.com/@noelbraganza/look-ma-no-hands-d912068c0eac?source=rss-9c4aa3408084------2</link>
            <guid isPermaLink="false">https://medium.com/p/d912068c0eac</guid>
            <category><![CDATA[self-driving-cars]]></category>
            <category><![CDATA[hmi]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Noel Braganza]]></dc:creator>
            <pubDate>Sun, 17 Apr 2016 21:29:26 GMT</pubDate>
            <atom:updated>2016-04-17T21:29:26.064Z</atom:updated>
            <content:encoded><![CDATA[<h4>A quick guide to Autonomous Drive and designing good in-car HMI</h4><p>One of the most challenging things about designing for car HMIs is the assumption that it is just another extension of current day consumer electronics. So the question then arises is, are we still designing HMI for cars to be an extension of your mobile phone? Or are we designing intelligent systems that aid the user to drive cars autonomously?</p><p>The recent past has seen various European car manufacturers and automotive suppliers successfully developing and implementing advanced driver assistance systems. As the trend towards Autonomous Drive (AD) particularly high and full automation grows, it begins representing a promising application of the internet of things in the mobility sector.</p><p>So then are we simply designing extensions of mobile devices or well-integrated systems that can intelligently assist drivers on the road.</p><h4><strong>What are we designing for?</strong></h4><p><em>With features like adaptive cruise control and autonomous drive, designers now need to reimagine the in-car experience</em></p><p>Clusters traditionally would only indicate speed, fuel, engine heat, oil, distance etc., and a recent example proposed by a design studio in London has suggested a simplified version of just that. I can see some value to the design, it’s simplified, contextual and sort of easy to read. But I believe it doesn’t take into account a lot of functions that are an inevitable future of driving.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xpB89Gw3ZFVM8dzB3gS2Pg.jpeg" /><figcaption>Recent redesigns of clusters and infotainment centres.</figcaption></figure><p>The cluster is primarily meant to give drivers feedback about their current activity in the car as well as some additional car specific information that could affect their driving experience and with autonomous driving states those activities are no longer standard and obvious.</p><p>An extreme case in point could be if we think about the driving speed, is it a primary piece of information for the driver or does ‘time taken to destination’ take precedence in such a setup? Or for that matter, functions like presets in the radio player, does it make sense for an HMI to entertain such redundancy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*yBOukVlXyJzgPlsq7MlIvA.jpeg" /><figcaption>Setting presets in radio are now redundant and should be replaced by functions like favourites</figcaption></figure><h4>Contextually aware</h4><p><em>How can drivers be more aware but let disturbed?</em></p><p>While designing a complete experience, the use of various techniques such as lights, sounds, haptic and other feedback mechanisms need to be employed judiciously to ensure that the driver is always aware of his/her surroundings even if the car is doing partially or everything for them. This extension to the experience improves driver response and reaction time in case of emergencies.</p><p>While in autonomous mode, it is also important to look at how one can steer the driver back to controlling the car seamlessly. New innovations in touch sensitive steering wheels offer new ways with which the driver can interact with the car, changing the way we’ve traditionally looked at interaction with the car system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*odwwYQVoBVCin_ISnt-t_w.gif" /><figcaption>The Neonode touch steering has been exploring interactions with regards to Autonomous Drive</figcaption></figure><h4>The Design Medium</h4><p><em>Designing HMI is more than just making it look good on presentations</em></p><p>Are we designing on the desktop for screens being viewed within a car? That is a question we must always keep in mind as we begin working. Clusters and infotainment systems need to be crafted on actual hardware being used within the car. The importance of doing this cannot be stressed more. Retina displays with high colour saturation gives us designers a false sense of colours and contrast, most of which completely fail when actually implemented.</p><p>Often white, superimposed on pastel coloured backgrounds looks nice, but is not the most readable even in the best of conditions. Additional, factors like sunlight, glare and reflections only augment the readability issue, increasing cognitive load especially when driving through bright and shadowy areas such as tunnels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HNxy3mFbo4jFV1rY3BDx6Q.jpeg" /><figcaption>Designing on actual displays gives us a more accurate picture</figcaption></figure><h4><strong>Various points of interactions</strong></h4><p><em>Interactions that go beyond just a touch screen</em></p><p>Multiple input factors need to be taken into account such as steering buttons, dials, buttons and sensors apart from the obvious touch sensitive displays. Navigation within the HMI, needs to be simplified to work with multiple control devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*NY2kHiB01EdugvtGO1hiig.jpeg" /></figure><p>Sensors play a big part within automated cars, and information displayed needs to be showcased contextually in order to increase relevance and reduce distractions.</p><h4><strong>Reimagining connected systems</strong></h4><p>We have been working on new ways to make the interactions within the car more seamless and intuitive. One such challenge was to try and make it easier for drivers to be able to interact with the infotainment or navigation system easily and more intuitively. This exercise helped us imagine new ways with which drivers were able to communicate with the infotainment centres within the car.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*PNhLi1PhmYA0pCY5gqnJoQ.jpeg" /><figcaption>An example of micro ecosystems where a localised WiFi can act as a bridge to communicate with the car.</figcaption></figure><p>For example, by building localised networks within the car ecosystem, we have been able to get car networks to talk with external systems making it easier to push information to and from the infotainment centre. This leaves us with a strong modular framework that allows us to build and test interactions in a matter of weeks. Once interactions are defined and tested we then begin working on the aesthetics that include design, animation and visual feedback.</p><h4><strong>Conclusion</strong></h4><p>Clusters and infotainment systems are just a fraction of the complete driving experience, and a mere restructure of usability upped with better graphics could be a premature delivery of a redesign of an in-car HMI. One must look at a wholesome in-car experience in order to augment the personalisation one experiences within the car.</p><p>The way forward when designing in-car HMI must include features and services that we will see in cars two years from now. We believe in ideas that don’t just tackle isolated challenges but more comprehensive interaction challenges one would face both from a design perspective but as a psychological one. Advancements in consumer electronics can be considered effective catalysts that push the car industry to think of new and better things, but at the same time, the behaviour people exhibit behind owning cars and owning consumer electronics is very different and changes from region to region.</p><p>As designers and innovators we should work towards designing standardised interactions but also push for wildly unique designs for each car that we design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d912068c0eac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One year with the Moto 360]]></title>
            <link>https://medium.com/@noelbraganza/one-year-with-the-moto-360-4c6a46ff471a?source=rss-9c4aa3408084------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c6a46ff471a</guid>
            <category><![CDATA[apple-watch]]></category>
            <category><![CDATA[moto-360]]></category>
            <category><![CDATA[wearables]]></category>
            <dc:creator><![CDATA[Noel Braganza]]></dc:creator>
            <pubDate>Thu, 29 Oct 2015 10:27:02 GMT</pubDate>
            <atom:updated>2015-10-29T10:27:02.993Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MA_L7etsHSh8_7EuVVyVTQ.png" /><figcaption>My Moto 360</figcaption></figure><p>The story of me acquiring the <a href="https://www.motorola.com/us/products/moto-360">Moto 360</a> is quite an interesting one. I was meant to leave the US to join a company in Sweden when Motorola announced the launch of the Moto 360. I, of course wanted to be one of the first to own one, especially after scouring youtube for every possible review prior to the release.</p><p>My move simply meant that I needed to buy one before I left, since Motorola products are less available outside the US.</p><p>After much annoyance and determined persistence, I managed to buy one from the Motorola website. At check out, the delivery date given to me was 3 weeks from the day of purchase which also happened to be the same day I was meant to leave the country. My heart sank knowing that some random stranger walking down my neighbourhood would pick up my parcel and enjoy the shiny piece of metal and Horween leather.</p><p>Fortunately the parcel arrived a week earlier thanks to my desperate cry of help to customer care who were quite amused by my very unique situation.</p><p>Since then, I have only good experiences with my watch.</p><p>I have always been a watch person, but there was a point when I suddenly just stopped wearing one, so when I put on my Moto 360 it was after a six-seven year hiatus.</p><p>The watch fit my wrist perfectly and the metal felt comfortable on the skin. It was much lighter than I imagined, which was a really good thing. So let’s list out some of the broad topics.</p><h4><strong>Design and glitter value</strong></h4><p>The watch has continued to get curious stares and eager touches. Several conversations have been started with random strangers just because of my watch. Most of them are drawn to it like bugs to a lamp, literally. They see the gentle glow of my watch and they immediately ask me, “Is that a smart watch? It’s much prettier than the Apple Watch”, to which i politely reply saying, “Yes it is.”</p><p>I have even got curious stares when they don’t see anything on the screen. Most of them look at the dimmed/off display and say, that’s a strange watch, you don’t have any time showing on it. And then I just move my wrist a bit and they are all gasp in surprise. “Oh my! That’s a beautiful watch”</p><p>The so called “Flat Tyre” has never really been a problem for me, neither for function or aesthetic. I happen to actually like it.</p><h4>Battery life</h4><p>The battery life has been pretty robust for the past year. The frequent software updates improved performance and of course the battery performance too. I never wear my watch to sleep, which means the charging dock at my bedside table was a perfect place to keep my watch whenever I was not wearing it. I almost don’t think about the battery life at all because my watch is always charged when I leave my house in the morning.</p><h4>Voice Recognition</h4><p>I have frequently replied to Whatsapp messages directly from my watch itself. Especially when my phone was away being charged and I was in the kitchen cooking. The preset messages suggested too are quite handy if the voice recognition seems too odd to use, especially when you’re out or at a meeting.</p><h4>Apps</h4><p>The growing number of apps is great, but the thing I probably use the most is my Google Now cards and my Navigation app. I also do end up using the messaging apps without realising it since I get frequent notifications whenever I receive messages or calls. But those are mostly reactionary and not self initiated.</p><p>The health data is quite useful, but I never really set any goals as such. I just wear the watch and let it calculate my activity which I then on occasion analyse on my phone or computer. But that’s probably because I don’t care so much about measuring health information.</p><h4>Navigation</h4><p>The one service I find the most useful is the little haptic buzz and direction information displayed on my watch when I drive or bike around the city. I hear the lady on the phone tell me to turn somewhere and I look at my watch to see what sort of turn it is, a round about an exit or a T-junction. It’s extremely handy.</p><h4>Notifications</h4><p>The other thing that I can’t live without is the ease at which I can access notifications. Just a twist of my wrist and I know if it’s worth taking my phone out if my pocket or not. It also allows me to easily see if someone important is trying to reach me without having to make an effort. If it’s the endless messages coming in from a WhatsApp group I could just ignore it and read the messages later on my phone. The watch notifications have inadvertently lowered the chances of me dropping my phone every time I try taking my phone out of my pocket.</p><h3>Conclusion</h3><p>The watch is everything that I wanted and more. Beautiful design, very very functional and it got me back on having a piece of metal on my wrist. It might already be a year old, but it doesn’t feel outdated in anyway for me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c6a46ff471a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>