<?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 Ajayan Subramanian on Medium]]></title>
        <description><![CDATA[Stories by Ajayan Subramanian on Medium]]></description>
        <link>https://medium.com/@n0rbuu?source=rss-b296d47e4af5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*v79DzoyGfvVZKQ6AuRVY3Q.jpeg</url>
            <title>Stories by Ajayan Subramanian on Medium</title>
            <link>https://medium.com/@n0rbuu?source=rss-b296d47e4af5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:44:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@n0rbuu/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[Dissecting the Decision Review System in Cricket]]></title>
            <link>https://medium.com/@n0rbuu/dissecting-the-decision-review-system-in-cricket-ff744cb0a689?source=rss-b296d47e4af5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff744cb0a689</guid>
            <category><![CDATA[cricket]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[sports]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Ajayan Subramanian]]></dc:creator>
            <pubDate>Sat, 09 Jun 2018 14:08:43 GMT</pubDate>
            <atom:updated>2020-12-23T18:22:17.642Z</atom:updated>
            <content:encoded><![CDATA[<h4>How technology complicated an inherently simple sport</h4><p>— written in collaboration with <a href="https://medium.com/u/449cbc87b00e">Sachin Nayak</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RmjXgcUE7jsoxIbQMOi8dg.jpeg" /><figcaption><a href="https://stock.adobe.com/images/scarecrow-pointing/37427601?prev_url=detail">Source</a></figcaption></figure><h4>The Decision Review System (DRS) was meant to improve umpiring in cricket with technology, so players could stop worrying about fairness and concentrate on their game.</h4><p>Almost a decade since its inception the DRS has failed to take the attention away from umpiring—it has arguably introduced a new <strong>subplot</strong> so foreign to the original sport, that it has caused <strong>anxiety</strong> across the cricketing community.</p><p>If you’re unfamiliar with cricket, <a href="https://www.youtube.com/watch?v=lUdwBKFSBpI">watch this video</a> and follow the graphic below for a quick introduction to the DRS. There are more details and rules, but we’ll share them as we go along!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rHEtPBDvfklgroVqaUNL5g.png" /><figcaption>Sources: <a href="https://www.icc-cricket.com/video/312199">1</a>, <a href="https://www.google.com/url?sa=i&amp;source=images&amp;cd=&amp;ved=2ahUKEwi_sp__jpPbAhUB7mMKHeSyAa0Qjxx6BAgBEAI&amp;url=https%3A%2F%2Fwww.theguardian.com%2Fsport%2F2018%2Fjan%2F06%2Fjonny-bairstow-unhappy-drs-mitchell-marsh-ashes&amp;psig=AOvVaw091uua1tvX7snasKOxmD1h&amp;ust=1526865381976988">2</a></figcaption></figure><h4>The creators of the DRS couldn’t anticipate the extent to which they were changing the sport.</h4><p>Cricket is inherently simple. A kid playing on the streets possesses the same level of understanding of the rules, as a veteran of the game. In the graphic above, the items in red are <em>a direct consequence of the DRS, and would not have happened otherwise</em>. It has taken players, viewers, and commentators a long time to come to terms with these changes, and we still experience many 🤷🏽‍♀️ moments!</p><p>If you don’t believe us, we put together a video so you can hear from the cricketers and commentators themselves:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F269427572%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F269427572&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F700357686_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/5221c9766ce0f73215284b6c4dddbd13/href">https://medium.com/media/5221c9766ce0f73215284b6c4dddbd13/href</a></iframe><h4>One seemingly simple rule, in particular, changed the game forever.</h4><p>The general sequence of events had everyone scratching their heads, but the players eventually came around to them. They still haven’t come to terms however, with this one rule, that was meant to curtail the overuse of challenges:</p><p><strong>A team can afford to make only 1 unsuccessful challenge*, after which they cannot challenge any more decisions.</strong> To put this in perspective, consider that there are 300 plays that can potentially be challenged. If you make 1 challenge and fail to get it overturned, your team is at a disadvantage for whatever is remaining of the 300 plays!</p><p>*in test cricket (a longer format of the sport), one can make 2 unsuccessful challenges over about 480 plays.</p><blockquote>Because of the high stakes involved, choosing when to challenge an umpiring decision is a game within a game.</blockquote><h4>We will further explain why this rule shook up cricket. But first, can we just get rid of DRS if it’s problematic? (We can’t, thanks to television.)</h4><p>Umpiring in cricket is a really difficult job, perhaps more so than in any other sport. For each individual play, the umpire has to keep her eyes and ears alert, and retain a sharp memory to perceive:</p><ul><li>The extent to which the ball bounces off the pitch</li><li>The sound generated when the ball comes in contact with the batswoman/ batsman</li><li>The reaction of the surrounding players</li><li>…and much more!</li></ul><p>Television viewers, on the other hand, are privileged with slow motion replays that highlight many of these factors. They cannot empathize with the umpire, who has to <em>perceive all this in real time</em>. So we now have a level of expectation of umpiring, that can only be solved with the use of technology.</p><blockquote>Television has created a gap, that only sports technology can fill.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*HC-E7kwPG-i-KAU8kV9sOg.gif" /><figcaption>As early as the 2000s, viewers had access to this level of detail in replays</figcaption></figure><h4>Other sports also enforce a limited number of decision reviews. Why have they not suffered as much as cricket?</h4><p>To answer this question, let’s look at the successful implementation of decision reviews in some sports, so we can compare them with cricket.</p><p><strong>Tennis</strong></p><ul><li>It had its early <a href="http://www.nzherald.co.nz/sport/news/article.cfm?c_id=4&amp;objectid=10450415">skeptics</a>, but even<em> </em><a href="http://www.tennis.com/pro-game/2015/07/federer-totally-fine-hawk-eye-wants-darkness-rules-changed/55514/"><em>they want more</em></a><em> assistance now!</em></li><li>Each player can make 2 unsuccessful challenges per set.</li><li>Unlike cricket, <em>a player only has herself to answer to</em>, when she makes an unsuccessful challenge.</li></ul><p><strong>NFL</strong></p><ul><li>Unlike cricket, <em>only the coach can challenge close decisions</em>, not the players.</li><li>The NFL does a good job of publishing open stats of overturned decisions over the years, so everyone can look towards improving the system.</li></ul><p><strong>Rugby, NBA</strong></p><ul><li>Only the referees can initiate reviews, not the players.</li><li>There is a central back-office team that monitors every play, anticipating moments when replays might be required, and regularly improving the system.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-xCS-bzCzTrvQOmh8LxOCw.png" /><figcaption>Sources: <a href="http://gamesetmap.com/?p=74">1</a>, <a href="http://o.canada.com/news/nfl-sunday-backup-qbs-to-the-rescue-as-michael-vick-alex-smith-and-jay-cutler-go-down">2</a>, <a href="https://www.google.com/search?q=rugby+tmo+review&amp;client=safari&amp;rls=en&amp;source=lnms&amp;tbm=isch&amp;sa=X&amp;ved=0ahUKEwitkaX80ZTbAhWqr1QKHbJcAWkQ_AUIDCgD&amp;biw=1280&amp;bih=739#imgrc=z8fBjs_tqR1puM:">3</a>, <a href="https://www.usatoday.com/story/sports/nba/2017/11/16/at-replay-center-nba-refs-far-from-the-game-but-right-in-it/107734928/">4</a></figcaption></figure><h4>Cricket is unique in that the responsibility for challenging decisions lies with the players, who already have other responsibilities.</h4><p>We just saw that in most other sports the coach, the referee, or a video assistant may challenge decisions. The creators of the DRS decided to place this burden on the players.</p><p>We have identified 5 types of players who have a key role in the decision review process. Let’s take a look at their original responsibilities, and those added along with the DRS (in red):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7kI914jpAP5bK0zoKiRdHQ.png" /></figure><h4>The DRS was more intricate than anyone expected. But we’ve still not talked about the biggest effect in the sport—the relationship between players.</h4><p>Cricket is a team sport.<em> </em>Players don’t just play for themselves, they <em>wield a considerable influence over each other. </em>The DRS introduced influences and relationships that are not inherently part of the game, which caught everyone by surprise. Here are some examples:</p><ul><li><strong>Striker and non-striker:</strong> Let’s say the striker is a senior player, under pressure to score runs (since that is his responsibility). When he gets out, his instinct is to challenge the decision. But a frivolous challenge could put the rest of his team at a disadvantage. This is where the non-striker steps in, with the responsiblity of following the play to provide an informed opinion. Now imagine that this non-striker is playing his first match. Can he really be unbiased? Would he not be <strong>influenced</strong> by the senior striker to recommend a challenge? Even if we take aside the difference in seniority, wouldn’t past challenges play on their mind? (“I helped you last time so you owe me one.”)</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUjBB3H6hSZA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUjBB3H6hSZA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUjBB3H6hSZA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/10a7b5aa19de1743270498058a3e17f6/href">https://medium.com/media/10a7b5aa19de1743270498058a3e17f6/href</a></iframe><ul><li><strong>Captain and bowler:</strong> Bowlers are responsible for getting players out, and look towards the captain to challenge <strong>every</strong> decision! They have nothing to lose—the DRS has made the captain solely accountable for challenging decisions. Even if the captain is resolute in being objective, imagine the <strong>stress</strong> his teammates put him under, potentially over 300 plays in a single day!</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FgbOxxUvUP7o%3Fstart%3D249%26feature%3Doembed%26start%3D249&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DgbOxxUvUP7o&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FgbOxxUvUP7o%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e8094f45c2bcb58f2509f3a654a646cf/href">https://medium.com/media/e8094f45c2bcb58f2509f3a654a646cf/href</a></iframe><h4>The influences and pressures that players have on each other conflict with their individual responsibilities.</h4><p>Consider professionals in any role. In a perfect world, they rely on two qualities to perform their tasks: skill, and the ability to make decisions. In reality, however, both of these qualities are impaired because of the surrounding <em>culture. </em>They<em> </em>may be under pressure from their boss, for instance, or their co-workers. Similarly, in cricket, players may not perform their tasks to the fullest potential, because of on-field influences.</p><p><strong>Using a cultural diagram, we’ve highlighted the influences these players have on each other:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sqnOKxOxwzOdlgH_cTFq9A.png" /><figcaption>A cultural diagram is useful in showing how stakeholders in a system influence each other.</figcaption></figure><ul><li>Each player is represented as a circle.</li><li>Bullets inside the circle reflect their individual responsibilities.</li><li>Arrows indicate an influence from the source to the destination.</li><li><strong>Breakdowns</strong>, the lightning bolts in red, are the biggest takeaway from this diagram. They indicate places where <em>the system may fall apart, due to the impact of surrounding influences.</em></li></ul><p>Let’s look at the breakdowns:</p><ol><li><strong>Captain’s role</strong>: How can a captain be objective in challenging decisions, keep the team motivated, and maintain an impartial image at the same time?</li><li><strong>Bowler-&gt;Captain:</strong> The bowler’s incessant pressure, in an effort to get wickets, gets in the way of the captain’s fair decision making.</li><li><strong>Striker-&gt;Non-Striker: </strong>The striker’s need to not get out gets in the way of the non-striker’s fair decision making.</li><li><strong>Non-striker’s role: </strong>Just like the captain, the non-striker is put in an unpleasant position, where being impartial is tough</li><li><strong>Team puts pressure: </strong>Ultimately, only the captain and striker can decide to challenge decisions. So they are accountable to the team and supporters.</li><li><strong>Coach’s role (or lack of): </strong>The coach has literally no influence on proceedings, even though she has <em>no conflicting responsibilities during the game.</em></li></ol><p>There are other areas we could’ve looked at—improving decision-making technology, optimizing communication, and better educating players and viewers about the system. Judging by the evolution of video reviews in other sports, we believe solutions to these are inevitable. <strong>But breakdowns in relationships</strong> will still persist.</p><blockquote>Cultural issues are not easy to solve, since they they are not visually apparent.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff744cb0a689" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design reviews: How to please everyone!]]></title>
            <link>https://medium.com/vmware-end-user-computing/design-reviews-how-to-please-everyone-d4a8a5d1f3ef?source=rss-b296d47e4af5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4a8a5d1f3ef</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Ajayan Subramanian]]></dc:creator>
            <pubDate>Tue, 08 May 2018 17:10:11 GMT</pubDate>
            <atom:updated>2018-05-14T14:02:44.352Z</atom:updated>
            <content:encoded><![CDATA[<p>Ushering projects off into the sunset by better planning reviews with PMs, Customers, Developers and Executives</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nmhxtMcPgM2F4n7IHcAKrA.jpeg" /></figure><p>A few months into my first full-time job as a UX designer, a couple of thoughts kept creeping into my mind:</p><h4>If my job is to design for end-users, why am I spending so much time reviewing my work with <em>other co-workers?</em></h4><p>In my grad school program, everyone—professors, classmates and project partners—pushed me to design in a single direction, to create <em>a preferred future state for the user</em>. No matter how varied, conflicting, or brutal the critique, I naturally believed I was always moving forward in the right direction. My path to meeting user’s needs felt as short as this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VNWCJbsrKrZ9xhzCfiEpXA.png" /><figcaption>In grad school we tend to <strong>assume </strong>our work will reach 10,000 users. There’s nothing wrong with it — this allows us to focus on the interaction design. But, it leaves out a large part of our day-to-day work.</figcaption></figure><p>At a large company like VMware, there is a <strong>definitively longer path</strong> to the end-user, and for good reason:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_OuQuySoQ1RAAGpjtLdVyQ.png" /><figcaption>It’s not unusual to work on 2 or 3 parallel paths, at varying stages of completion during the design process.</figcaption></figure><p>However, the problem that presents itself in a larger organization isn’t necessarily the sheer number of eyes on your design, it is that each pair of eyes is <em>interpreting it in their own, unique way</em>.</p><h4>How can I design to meet end-user needs if every stakeholder wants something different?</h4><p>From the outset, it should’ve been obvious to me that each stakeholder I worked with would have a different opinion. Through grad school I was prepared to balance stakeholder concerns and find the sweet spot with a cool Venn diagram. But, it’s one thing to role-play as a PM, developer, or client, and another thing to do it as your singular function at a big company. I was taken aback by some of the questions that came my way, especially when I was confident that my design fulfilled user’s needs. I needed to adapt to this environment, and regain that feeling of <em>moving forward</em>.</p><h4>Navigating stakeholder reviews for better results</h4><p>I decided that if I wanted to be better prepared for stakeholder reviews, I needed to develop a loose framework to help me succeed. Through plenty of introspection and advice from fellow designers, I drafted some simple principles to guide me throughout the design process:</p><ul><li>Be aware of what each stakeholder needs from you to move forward</li><li>Decide what you need from this stakeholder to move forward</li><li>Always stay in control</li></ul><p>Then, I applied these principles across each of the different types of stakeholders I work with every day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jydvTmCpW2Yi9GaX1LxpUg.png" /></figure><h4>Product Managers</h4><p>If you’ve done your job thoroughly, you’ve already previously agreed on a set of user stories. A PM’s fundamental interest is in making sure the design satisfies this, with no gaps. To that end, don’t just pull up artboards from Sketch. Clearly show a <em>sequence of mockups that fulfill each user story</em>. Another point of interest for PMs is how the design varies across the lifecycle of a product—from the first-time user experience and users who’ve been upgraded from a previous version to users with partial access to the product.</p><blockquote>Don’t just pull up artboards from Sketch. Clearly show a sequence of mockups that fulfill each user story.</blockquote><p>If a PM acknowledges that your design is the best way to accomplish those user stories, you’ve just earned tremendous leverage, particularly in moments of disagreement with the development team.</p><h4>Customer Reps</h4><p>They are especially interested in how your design can improve the lives of employees at <em>their companies</em>. In which case, I would only present the scenarios that pertain to<em> these employees</em>. It is tempting to show every user story, especially the ones you’re proud of. But, in my experience, this may cause more harm than good. As customer reps look at each new mockup, they subconsciously think through deployment of these features, and transitioning from existing systems. Avoiding any additional worries could help you <em>steer conversation towards the design, and ensure you remain in control</em>.</p><p>Ultimately, our design also needs to make the company money, and customer buy-in is a step towards achieving that.</p><h4>Developers</h4><p>While these interactions may seem tedious at the outset, they are incredibly valuable. Your design is being vetted by someone highly specialized in thinking through different contexts, form factors, and stages in the product lifecycle. Having previously been a developer myself, I can confirm that it is one of life’s great joys (ok, maybe I’m going overboard) to know that a designer has thought through the “non-happy” path for end-users.</p><blockquote>It is one of life’s great joys to know that a designer has thought through the “non-happy” path for end-users.</blockquote><p>Developers complete the aforementioned path to the end-user. Articulate as many details as possible about the design, and make sure the developers have imbibed them, or your vision will not be realized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19dAzm1NWrpwjOx581x7mA.png" /><figcaption>These are sections in an Invision project for something I worked on. I put some thought into how the Developers and PMs would consume the mockups, and laid them out deliberately in this order.</figcaption></figure><h4>Executives/Managers</h4><p>If you’re going to show anyone your ‘moments of delight,’ this is the audience to do so. Executives do not have the time to actively listen through a complete presentation. They are concerned with how your design takes forward the product/company vision. Beyond that, they are always on the lookout for snippets they can share with other executives, or customers. So, it is probably worth thinking about an elevator pitch for the feature, in the off chance it makes its way into someone’s presentation :-)</p><p>During the design review, make sure you’re checking <em>items off a pre-agreed agenda</em>,<em> </em>so executives don’t momentarily forget which meeting they’re at!</p><p>The path to end-users is long, and stakeholders can at times seem like obstacles. However, keeping stakeholders’ viewpoints in mind during the design process has made me a better designer. Most of the approaches I’ve mentioned in this article—focusing on user stories, articulating details, preparing elevator pitches, thinking through edge cases—are <em>useful tools to improve your design</em>,<em> </em>regardless of your interaction with stakeholders. Thanks for reading, and please share your experiences as you navigate your way in partnering with stakeholders. I would love to hear!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4a8a5d1f3ef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vmware-end-user-computing/design-reviews-how-to-please-everyone-d4a8a5d1f3ef">Design reviews: How to please everyone!</a> was originally published in <a href="https://medium.com/vmware-end-user-computing">VMware 360</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>