<?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 Girish Subramanian on Medium]]></title>
        <description><![CDATA[Stories by Girish Subramanian on Medium]]></description>
        <link>https://medium.com/@giryer?source=rss-eb5b2df92445------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GSwNjbdUMEU8e2l00_IS_w.png</url>
            <title>Stories by Girish Subramanian on Medium</title>
            <link>https://medium.com/@giryer?source=rss-eb5b2df92445------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:18:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@giryer/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 to Democratize Design Systems]]></title>
            <link>https://medium.com/geekculture/how-to-democratize-design-systems-f9f52be2d4d9?source=rss-eb5b2df92445------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9f52be2d4d9</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[democracy]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[governance]]></category>
            <dc:creator><![CDATA[Girish Subramanian]]></dc:creator>
            <pubDate>Sat, 28 Nov 2020 21:06:24 GMT</pubDate>
            <atom:updated>2021-04-11T15:39:10.032Z</atom:updated>
            <content:encoded><![CDATA[<p>or ‘How to set up a bicameral practice’ or ‘How I learnt to balance power to run a stable form of governance’ or ‘How my idealism failed me at first and then saved me later’.</p><p>A confession before I start. When I started setting up the governance I had no idea that it was headed towards a form of <a href="https://en.wikipedia.org/wiki/Bicameralism">bicameralism</a>. It was an emergent phenomenon based on the push and pull of competing powers and priorities within the organization and that is why I think it is beautiful.</p><p>When I first started setting up the governance model, I had simple idea. A very simple idea. Not values. Not principles. Not laws. Not rules.</p><p>Just a simple idea(and a little idealistic) that people will work together if they have to accomplish big things that cannot be done alone. I just need to set up checks and balances so that the power is distributed and there is no room for autocracy (including myself as the leader)</p><p>I started to build a governance model based on this idea.</p><p>There were 50+ designers spread across 4 major groups. Each group was led by a lead designer and they worked with their product and dev lead counterparts. These design leads reported to the head of design to whom I also reported.</p><p>Product Leads sent requests to Design Leads who in turn assigned them to designers based on priority and capacity. The finished work is then handed off to the Dev leads. Not a very complicated structure. (Simple waterfall operating in a quasi agile aka Dual Sprints like anywhere else. I am oversimplifying it for the benefit of this conversation)</p><h4>Starting trouble</h4><p>I thought it would not be very difficult to set up the basics like colour, typography and iconography because they were driven by brand. I was wrong. The first indication of the storm to come started with the decision for error colour. For most companies it would be an easy decision. Any accessible shade of red would work but for companies with red as their primary brand colour, it was not that simple. Here is (almost) how the first meeting between the senior designers went:</p><p>A: Are we sending wrong signals by associating error with our brand colour?</p><p>B: No! The context is different. People don’t make that kind of connections. Look at brand X and brand Y. They are also red</p><p>A: Can we explore?</p><p>C: How about orange?</p><p>D: We are overthinking this</p><p>A: Lets come up with some options</p><p>Me: I am leaning towards with what B said. It is the norm in all digital ecosystems. People are smarter than to make that association. However it is only my opinion. It may be a good idea for us to explore. Can we come up with some accessible options in the next two days? If all fails, we can go ahead with this shade of red.</p><p>Dev Lead: What should we do now?</p><p>Me: Let’s go ahead with this one for now. We can replace it if we find a better option.</p><p>A: We should get the feedback from all designers. Let’s conduct a poll.</p><p>Me: Erm. I would rather not have a poll. Majoritarianism does not mean good decision. There is at least 75+ years of design experience in this room. We should be able to decide what colour the error message should be.</p><p>A: I still think we should ask everyone.</p><p>Me: Sure. Lets give it a shot.</p><h4>First mistakes</h4><p>That right there was my first mistake. I was too afraid to put down my foot on basic decisions. I wanted to involve everyone that I ‘thought’ was a stakeholder in the decision making process. I wanted consensus.</p><p>After three weeks of back and forth and polling, the consensus was to use (a colour close to) #<a href="https://www.google.com/search?ei=jaHCX5DbCLuw5NoPu9GiuAg&amp;q=%23ee6b24&amp;oq=%23ee6b24&amp;gs_lcp=CgZwc3ktYWIQA1Ca1QFYmtUBYL3XAWgAcAB4AIABf4gBsgOSAQMxLjOYAQCgAQKgAQGqAQdnd3Mtd2l6wAEB&amp;sclient=psy-ab&amp;ved=0ahUKEwjQ1c-s-aXtAhU7GFkFHbuoCIcQ4dUDCA0&amp;uact=5">ee6b24</a> as the error colour. Technically, there was nothing wrong with it but it did not ‘feel right’. We still went ahead with it but deep inside I knew that something was not right with this way of making decisions. (We later updated it to #<a href="https://www.google.com/search?q=%23ca3e00&amp;oq=%23ca3e00&amp;aqs=chrome..69i57.148j0j15&amp;sourceid=chrome&amp;ie=UTF-8">ca3e00</a>. It was a deep orange bordering red)</p><p>More mistakes followed as things got more complex with typescale and buttons. Someone thought H1 was too big and some thought it was too small. Someone thought the buttons were too big. Some thought it was too small.</p><p>Every tiny decision was bandied around and dragged along because there were too many people involved.</p><h4>A hot mess</h4><p>The next few months was a hot mess. I organized ‘Alignment sessions’ every Thursday. We would all meet on Thursdays to look at the rough draft of the solution for a design element (e.g :accordions) sketched by me and critique it, add use cases etc. We would refine the element as a group on the whiteboard (not pixel perfect mock)and agree on some basic ground rules for usage. We would also decide on the next element that needs to be addressed before the end of the session. I would then refine the element per our discussion and present it next week for sign off and also present a rough sketch for the next element.</p><p>The idea was to add elements week after week till all the basic elements were done.</p><p>Where it started falling apart is when some leads could not be present or had no context for feedback during the refinement but would offer all feedback after seeing the final mock. This would slow us down. So I changed the format and started presenting final mocks instead of sketches. But that did not help. We could never reach a total consensus and there was never a perfect ‘sign off’.</p><p>The timelines were fast approaching and we were not able to deliver. Leads started losing interest and they started delegating junior designers. It was a waste of their time. Soon it became a ‘free for all session’ and who ever was free on Thursday afternoon started showing up. The alignment meeting became a madhouse of ego conflicts and a hotbed for confusion with no decisions being made.</p><p>I clearly remember the meeting when I decided that I had to put an end to this. There were 14 designers instead of the 4 (that I had initially invited) and I was trying to maintain civility in the forum. I started dreading Thursdays.</p><p>Then one day, I sent a note cancelling the meeting until further notice. No one complained. I felt like an utter failure.</p><h4>Breakthroughs</h4><p>I had a very frustrating time for an entire year trying to resolve conflicts between people everyday. At first, I could not understand why people did not want to work with each other even thought they wanted the same things. I wanted all of them to be good friends and solve problems together.</p><p>I failed that year, but I had three valuable insights.</p><ol><li>People were not able to align because they needed different design systems. One size does not fit all.</li><li>Aiming for perfection was a trap. I need momentum. I need to be so quick that I should be able to change things in the design system if I made a mistake instead of trying to be prefect and being scared of making a mistake.</li><li>No matter what I do there will be someone who is unhappy. My purpose as a Design System Leader is not to make people happy but to build a system where unhappy people had the opportunity and power to change things that made them unhappy. I was building a democracy among tribes that had learned to live with each other for many years while fiercely guarding their independence.</li></ol><p>The minute I realized this, I developed a ton of empathy for the design leads and I realized that I was approaching it all wrong.</p><p>I decided to pivot on all three fronts.</p><h4>First Light</h4><p>My first light appeared when I started walking back home everyday with my <a href="https://www.linkedin.com/in/ramidahhan/">Design Ops specialist.</a> I would vent to him everyday and bounce my ideas off. He was an extremely nimble system thinker and was the only person around me who saw the beauty in these problems. Lucky for me, he was also a product thinker and started digging into this problem for me. A few days later I received a message from him “Hey Girish, You are not alone. Check this out!”</p><p><a href="https://spotify.design/article/reimagining-design-systems-at-spotify">Reimagining Design Systems at Spotify</a></p><p>I still remember the joy that I experienced when the Spotify article validated my insights.</p><p>“This is exactly what I have been trying to explain. This is amazing!”</p><p>A few days later he sent another message, “I think I have found the solution for your momentum problem.”</p><p><a href="https://basecamp.com/shapeup">Shape Up: Stop Running in Circles and Ship Work that Matters</a></p><p>We were already lean. We were already following an organic form of Shape Up. But Shape Up put a nice scaffolding around our organic process giving it a sense of orderliness. It was love at first sight for me.</p><p>Even though Shape up is not part of the Governance, it is important to understand that for context.</p><h4>Shape Up</h4><p>Over the next six months, we iterated on Shape Up with the help of the <a href="https://www.linkedin.com/in/madhumathi-palanisamy-0b1b60147/">Scrum Master</a> and the <a href="https://www.linkedin.com/in/justin-jun-b9938021/">Dev Lead</a>. They were such amazing partners. We started with a small component (a simple table) as an experiment. I sketched it on a whiteboard with a developer and co-wrote all behaviours down in a confluence document. Then we ‘designed in code’ because the foundational pieces were already available in the system. The output was nearly perfect. We knew that the idea worked. Over the next few sprints we started designing and developing simultaneously in the same format in the same sprint. We called it ‘Build and Iterate’.</p><p>Our first experiment was this:</p><p>Shape Up (requirement gathering)— Build and Iterate(sprint)</p><p>I handed over this process to my team to experiment more. They were amazing partners and they refined it further to match with the Scrum cadence.</p><p>Shape Up —Write Pitch(story writing) — Refine Pitch with Dev and QA (story refinement)— Build and Iterate</p><p>The team also created channels for each component per sprint so that they were readily available for each other and all decisions were taken immediately in channels instead of meetings. This saved enormous amount of time. This was the magic dust that propelled us rapidly because of the clarity and transparency it brought to the team during the sprint.</p><p>We knew that we had solved our momentum problem. Now it was only a matter of building muscle.</p><p>The initial days were met with some resistance from my team and my partners. Every time we hit a roadblock or a conflict, my <a href="https://www.linkedin.com/in/abura/">lead designer</a> would jokingly say, “Gym soreness. No pain. No gain. Don’t worry. We are not abandoning this. We are getting this done” I could not have asked for a better team and partners. They pulled this through and the resulting process doubled our velocity over time. You can read more about it <a href="https://giryer.medium.com/how-to-design-and-develop-in-the-same-sprint-564b7d6f8b22">here</a>.</p><h4>The Design Council (DC)</h4><p>I abandoned our Thursday alignments after the hot mess period. It was an embarrassingly bad model for governance. Instead, I decided to create a council of experts in their chosen field instead of the design leads. This would keep the politics out and this council will truly be a neutral entity whose focus was only on ensuring that good design thrives. The council had experts from the following fields: UX, UI, UX Research, A11Y, Service Design and Front End Development.</p><p>This council would meet once every week to review all the pitches before it was taken up in Build and Iterate to ensure that it met best practices in all these domains. In addition to this, based on the the need, the experts would monitor the channels during Build and Iterate to ensure that the component was being built in the right way.</p><p>This was a great success as the Design Leads respected the experts and knew that everyone was equal in front of the council and no one was giving them the short end of the stick.</p><p>Phew! Things were getting better. Now the process looked like this</p><p>Shape Up — Write Pitch — Design Council Review— Refine Pitch with Dev and QA — Build and Iterate</p><h4>Design System Working Group(DSWG)</h4><p>All pitches were written by designers in the Design System Team. The application designers felt left out of the process. They said they did not know what was happening with the Design Systems at any given point in time. We responded by sharing our sprint calendar. It had zero effect on the problem. Thats when it hit me.</p><p>They did not want visibility. They wanted ownership. This was my second big breakthrough.</p><p>This is so fundamental to the success of any design system. For the designers have a sense of ownership and power to influence direction. It made total sense.</p><p>Currently, the Council was operating like a circle of benevolent elders of the tribe. Though the tribe respected the elders, they felt left out.</p><p>However, I was scarred by the Thursday alignment meetings. I could not bring myself up for another town hall kind of format. (I am not a fan of town halls because they only serve well for broadcasting and not for people to register their thoughts)</p><p>Instead, I requested the leads to nominate a member from their team to represent their interests in the Design System. The leads were too busy and were managing too many threads to do justice to this role. Some leads were thrilled with this idea. Some were skeptical. Some were indifferent. However, they all responded immediately and nominated their best system minds for this experiment.</p><p>I requested the <a href="https://www.linkedin.com/in/codymarshall3/">DS designer </a>and the <a href="https://www.linkedin.com/in/joannakolbe/">Front End Developer</a> (who already was a part of the council) to shepherd this fledgling group till they were ready to take over major responsibilities from the Design Council.</p><p>All pitches now went to the DSWG first, who would evaluate the merit and quality of the request and would help designers to clean up the pitches before it was sent to the council.</p><p>DSWG met every Tuesday and filtered the requests for the DC that met every Thursday. This way, designers know what was happening every week in the Design System world. They could reach out their representative on the DSWG and understand what was happening. The DSWG reps could in turn teach and train the designers on the DS processes.</p><h4>Bicameral Practice</h4><p>In effect, the model now resembled closely the <a href="https://www.courthouselibrary.ca/how-we-can-help/legislation-case-law/guides/legislation/how-bill-becomes-law-canada">process</a> of creating a law in a bicameral democracy. This is how it looked now:</p><ol><li>Designers submit a pitch(proposal) for a new component/to update existing component</li><li>First reading at DSWG</li><li>Second reading at DSWG (if changes were requested in first reading)</li><li>DSWG passes the pitch to DC with comments</li><li>First reading at DC</li><li>Second reading at DC (if changes were requested in first reading)</li><li>Pitch is added to the Design System backlog with comments</li><li>Pitch is picked up by the team during sprint planning</li><li>Build and Iterate</li><li>QA and Release</li></ol><h4>A simple idea that saved the day</h4><p>This is a great case for me where intent turned into practice into theory. The resulting model closely resembles how modern states choose to govern themselves. Like everything else, it was not perfect in the beginning. But like I mentioned before, not trying to be perfect was the first major breakthrough I had. As long there is momentum in the direction of right intent, things will fall into place. It is only a matter of time.</p><p>It all started with just a simple idea(and a little idealistic) that people will work together if they have to accomplish big things that cannot be done alone. I just need to set up checks and balances so that the power is distributed and there is no room for autocracy (including myself as the leader)</p><p>I realized that persistent optimism about an idea is the only secret weapon that I need for the idea to manifest and take form.</p><h4>Thanks</h4><p>Like all my notes on Design System, I owe special thanks to <a href="https://medium.com/eightshapes-llc">Nathan Curtis</a>. Also, <a href="https://spotify.design/article/reimagining-design-systems-at-spotify">Spotify</a> and <a href="https://basecamp.com/shapeup">Basecamp</a> for their spirit of sharing. I owe huge gratitude to these three giants on whose shoulders I stand.</p><p><a href="https://www.linkedin.com/in/ramidahhan/">Rami Dahhan</a>, who is probably the most intelligent person I have met and whose desire to learn and the passion for problem solving is unmatched.</p><p><a href="https://www.linkedin.com/in/abura/">Amir Abura</a>, who can hustle the team out of any tough spot with his unbridled optimism.</p><p><a href="https://www.linkedin.com/in/codymarshall3/">Cody Marshall</a>, the design heavy lifter who possesses an unstoppable energy and infinite strength and can propel the team at a velocity that feels dangerously fast.</p><p><a href="https://www.linkedin.com/in/anabelleva/">Anabel Leva</a>, who has been my partner in crime since day 1 and is the rock that anchors everything in the team.</p><p><a href="https://www.linkedin.com/in/justin-jun-b9938021/">Justin Jun</a>, <a href="https://www.linkedin.com/in/joannakolbe/">Joanna Kolbe</a> and <a href="https://www.linkedin.com/in/umairhafeez/">Umair Hafeez</a>, developers that designers can only dream of. They made it look like all of this was really easy! What amazing people!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9f52be2d4d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/how-to-democratize-design-systems-f9f52be2d4d9">How to Democratize Design Systems</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Double Your Velocity in Sprints?]]></title>
            <link>https://medium.com/geekculture/how-to-design-and-develop-in-the-same-sprint-564b7d6f8b22?source=rss-eb5b2df92445------2</link>
            <guid isPermaLink="false">https://medium.com/p/564b7d6f8b22</guid>
            <category><![CDATA[shape-up]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[designops]]></category>
            <dc:creator><![CDATA[Girish Subramanian]]></dc:creator>
            <pubDate>Fri, 23 Oct 2020 02:45:04 GMT</pubDate>
            <atom:updated>2021-06-02T21:48:47.896Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Design and Develop in the same sprint</h3><p>or ‘How to Double Your Velocity in Sprints?’ or ‘ How to be truly agile’</p><p>Design Thinking and Agile break each other. But they need not. Let’s understand the foundations a little better. I will keep them brief.</p><h4><strong>Design Thinking</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1JtqtZGuMM-RuJMDMDi-iA.png" /><figcaption>Courtesy: <a href="https://www.designcouncil.org.uk/news-opinion/what-framework-innovation-design-councils-evolved-double-diamond">Design Council, UK</a></figcaption></figure><p>Design thinking framework by the Design Council, UK recommends four distinct phases:</p><ul><li><strong>Discover. </strong>The first diamond helps people understand, rather than simply assume, what the problem is. It involves speaking to and spending time with people who are affected by the issues.</li><li><strong>Define.</strong> The insight gathered from the discovery phase can help you to define the challenge in a different way.</li><li><strong>Develop.</strong> The second diamond encourages people to give different answers to the clearly defined problem, seeking inspiration from elsewhere and co-designing with a range of different people.</li><li><strong>Deliver. </strong>Delivery involves testing out different solutions at small-scale, rejecting those that will not work and improving the ones that will.</li></ul><blockquote>Design thinking places importance to Discovery+Definition before Design+Delivery as represented by the Double Diamond</blockquote><h4><strong>Agile + Scrum</strong></h4><p>Now let’s look at Agile. I have worked only in a Scrum methodology and I will talk only about that here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8stkCldFl4gGap0pIXcJw.png" /><figcaption>Courtesy: <a href="https://www.scrum.org/resources/what-is-scrum">scrum.org</a></figcaption></figure><p>Major scrum events that are followed are:</p><ul><li><a href="https://www.scrum.org/resources/what-is-a-sprint-in-scrum">Sprint</a></li><li><a href="https://www.scrum.org/resources/what-is-sprint-planning">Sprint Planning</a></li><li><a href="https://www.scrum.org/resources/what-is-a-daily-scrum">Daily Scrum</a></li><li><a href="https://www.scrum.org/resources/what-is-a-sprint-review">Sprint Review</a></li><li><a href="https://www.scrum.org/resources/what-is-a-sprint-retrospective">Sprint Retrospective</a></li></ul><p>We will focus only on Sprint. The rest are really harmless.</p><blockquote>According to the creators of Scrum, each Sprint has a goal of what is to be built, <strong>a design </strong>and flexible plan that will guide building it, the work, and the resultant product increment.</blockquote><blockquote>Source: <a href="https://www.scrum.org/resources/what-is-a-sprint-in-scrum">https://www.scrum.org/resources/what-is-a-sprint-in-scrum</a></blockquote><h4>Here is where things start falling apart</h4><p>Scrum makes an assumption that the design is done and ready before a sprint starts.</p><p>Because design needs to be completed before coding, a popular solution is a dual track process.</p><p>Development sprint follows Design sprint like a mini waterfall.</p><figure><img alt="Development sprint follows Design sprint like a mini waterfall" src="https://cdn-images-1.medium.com/max/1024/1*A4j64lL7g3_QdU8__wIAMw.png" /><figcaption>Dual Track Scrum</figcaption></figure><p>Designers find asking themselves, “How am I supposed to do all the 4 Ds in this time box? Not all problems can be time boxed. We need some time to figure out what the problem, explore, gather insights etc. How do I account for research? Recruitment for user testing? Design iterations? Testing?”</p><p>What about Design Sprint? you may ask. It promises one week sprint for co-designing a solution with partners. Design sprint is an amazing framework for aligning different stakeholders on the problem and to validate assumptions with end-users. It’s a discovery framework not a production framework. We will cover Design Sprints later in this article.</p><p>Agile is a production framework and it assumes that the Design Sprint is done and the solution is ready to be coded. We are talking about the most impactful way for design to be embedded in dev sprints.</p><p>Dual sprint also has efficiency issues. At any given time a designer works on two sprints. Tasks within this design sprint and dev support for tasks done in the previous sprint.</p><p>This slows down both design and dev, increases rework and creates bad working relationship between partners because they slow each other down and set each other up for failure.</p><p>Expectations vs Reality of the dual track sprints are far apart from each other: <em>(Blue, yellow and green bars represent tasks/stories done in each sprint)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fO7RLZ0McUHSJ6Yuo9eLsg.jpeg" /></figure><p>Designers, Developers and QA constantly interrupt each other because they are working on different problems. They slow each other down and set each other up for failure. There is no ‘flow’ between partners.</p><h4>Discovery vs Production</h4><p>Not acknowledging that design and design production need to be two different things is the main reason why organizations are not able to find efficiencies in their design operations.</p><p>Scrum is a production methodology not a design methodology. But that is not to say that designers cannot work in scrum.</p><p>They can. There is a way to do it.</p><p>Split Design and Design Production into two streams — Discovery Stream and Production Stream. First two/three Ds from the double diamond happens in the discovery stream and only the last D happens in the Production stream.</p><p>But that is not to say that no design happens in production. Tactical design happens in Production and strategic design happens in Discovery.</p><h4>Discovery Stream</h4><p>In this stream, teams follow the first three Ds of the double diamond. The designer along with the product owner, design researcher (and in some cases, the developer) co-create the solution. It is a rough + abstract solution to the problem which captures all data points, edge cases, order of flow, some basic interaction design etc.</p><p>The designer doesn’t create pixel perfect mocks in this phase but there is a general sense of direction for visual design. This is the perfect time for you to do a Design Sprint. It’s very heavy in logistics and can leave you exhausted if you don’t have a good core team . Seek help from your scrum master and Product Owner to help you with logistics. Seek all the help you can get because Design Sprints are the simplest and quickest way to get alignment on a problem statement and a solution approach. Without these two, dev sprint can become a nightmare.</p><p>Alternately, you can be leaner and treat this as ‘refinement’ of your story in a specific format. Basecamp has a great format for this and they call this shape-up. At the end of shape up they create a refined requirement called as a <a href="https://basecamp.com/shapeup/1.5-chapter-06#examples">pitch</a>. You may choose to devise your own format based on your context.</p><p>In this phase, you may also create wireframes and get tested it with your users. The goal is to determine the functional design of the product/feature along with its dependencies and constraints before it can be coded.(again, not pixel perfect mocks)</p><p>This needs to be co-created with your partners. (This is crucial for velocity)</p><p>Here is an example of how this may look. I have used ‘enhancement for filters’ as an example to keep this simple. But it can extend further to more complex flows.</p><figure><img alt="whiteboard sketch of a data filter with data points and behaviours" src="https://cdn-images-1.medium.com/max/1024/1*_d_YsdJmIEzl16BQQztI9A.jpeg" /><figcaption>Shaped up by the PO, Design Lead, Dev Lead, QA Lead and A11Y specialist</figcaption></figure><figure><img alt="screenshot of a document that describes the filter behaviour" src="https://cdn-images-1.medium.com/max/1024/1*7AAQXiOyymcQWk6JKSKKEQ.png" /><figcaption>Partial screenshot of a pitch co-written by PO, Design Lead, Dev Lead, QA Lead and A11Y specialist</figcaption></figure><h4>Production Stream</h4><p>Based on the solution agreed during the discovery phase, the PO, designer, developer, QA and A11Y expert (and other relevant players) enter the sprint.</p><p>Because visual design and development are happening simultaneously, a lot of back and forth is avoided between the teams and it increases the velocity of the teams many fold.</p><p>No more working in two sprints at the same time. All partners are working on the same problem during the sprint. Every decision between the partners is taken as a group during the sprint.</p><p>No more final reviews and feedback and rework and all that headache and heartache.</p><p>Here is a partial screenshot of a chat between a designer, developer and the A11Y expert:</p><figure><img alt="screenshot of chat between designer, developer and accessibility expert discussing potential solutions for a problem" src="https://cdn-images-1.medium.com/max/496/1*xm-rzupSXNB2-IpQj3n4Lg.png" /><figcaption>Screenshot of a designer, developer and A11Y expert ‘co-located’ digitally</figcaption></figure><p>The team co-locates and co-builds within a sprint and they design and develop simultaneously. Because most visual design decisions are captured in design guidelines and/or the Design Systems, the designer and developer are able co-build the solution together.</p><p>Designer and developer share progress every day and conduct daily demos to each other and because of this a lot of visual design fine tuning happens on front end code. The designer immediately updates the mocks to reflect these changes.</p><p>This is how the filters ended up looking. Not bad, huh?</p><figure><img alt="Final version of filter after co-design and co-build" src="https://cdn-images-1.medium.com/max/340/1*YhLeAW8zGlyeDrA6belAag.jpeg" /><figcaption>Finished version of designed and coded filters</figcaption></figure><p>In effect, the whole process looks like this now:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-rors9RZM4iO5SRlnb9qGg.png" /><figcaption>Improved Dual Track</figcaption></figure><figure><img alt="Discovery track is separate from the Production track. UI design and development happen in same sprint during production." src="https://cdn-images-1.medium.com/max/1024/1*kyqowkbkcZPmNMhskVGUiA.jpeg" /><figcaption>A better reality is when Discovery and Production are separated and UI+Dev happens in same sprint</figcaption></figure><p>I have been experimenting with this model with great success from late 2019. The velocity of the team has almost doubled. What used to take almost 2 sprints now takes only one sprint. It is nothing less than a miracle.</p><blockquote>Explore+Shape up first. Build+Iterate later</blockquote><p>However, there are some preconditions for this to happen</p><ul><li>Everyone involved needs to be courageous to experiment — Scrum master, PO, Designer, Developer, QA and other partners</li><li>Only teams with mutual respect and curiosity can do this. Warring factions will never achieve this agile nirvana. (Don’t even try this if your PO, designer and developer can’t see eye to eye)</li><li>There should be <strong>NO APPROVALS or SIGN OFFS</strong>. The teams should be empowered to take decisions and own the risks. Any feedback from leads and management should happen after the sprint and should be taken up as enhancement or bug. The team should be left alone with zero supervision. This is MANDATORY. (Let them do their job. If you don’t trust them, replace them. Just don’t hover over them)</li><li>No scope creep after a pitch is written. Any new requirement or idea should be added as an enhancement (same as agile)</li><li>Read this <a href="https://basecamp.com/shapeup">book</a>. Multiple times. Ask your team to read this. Multiple times. Read till the spirit of ‘shape up’ becomes a natural way of thinking for you.</li></ul><p>A huge thanks to <a href="https://medium.com/@rjs">Ryan Singer</a> for writing all this down in this <a href="https://basecamp.com/shapeup">amazing book</a>. Thanks to <a href="https://www.linkedin.com/in/ramidahhan/">Rami Dahhan</a> for making me read this(multiple times). Thanks to <a href="https://www.linkedin.com/in/abura/">Amir Abura</a>, <a href="https://www.linkedin.com/in/justin-jun-b9938021/">Justin Jun</a>, <a href="https://www.linkedin.com/in/madhumathi-palanisamy-0b1b60147/">Madhumathi Palanisamy</a>, <a href="https://www.linkedin.com/in/joannakolbe/">Joanna Kolbe</a>, <a href="https://www.linkedin.com/in/kuryan/">Ryan Ku</a>, <a href="https://www.linkedin.com/in/codymarshall3/">Cody Marshall</a>, <a href="https://www.linkedin.com/in/ron-pesano-18651a35/">Ron Pesano</a>, <a href="https://www.linkedin.com/in/pranav-shaligram-b5528b13/">Pranav Shaligram</a> and the entire dev + QA team for making this theory into practice. Thanks all 🙏🏾</p><p>If you are curious to know more details about how we managed to accomplish this and want to replicate this, reach out to me on <a href="https://www.linkedin.com/in/giryer/">LinkedIN.</a> Happy to chat and spread the message.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=564b7d6f8b22" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/how-to-design-and-develop-in-the-same-sprint-564b7d6f8b22">How to Double Your Velocity in Sprints?</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things You Need to Know Before You Build a Design System]]></title>
            <link>https://medium.com/swlh/things-you-need-to-know-before-you-build-a-design-system-700e0b020a74?source=rss-eb5b2df92445------2</link>
            <guid isPermaLink="false">https://medium.com/p/700e0b020a74</guid>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Girish Subramanian]]></dc:creator>
            <pubDate>Wed, 14 Oct 2020 22:02:56 GMT</pubDate>
            <atom:updated>2022-12-07T02:15:01.048Z</atom:updated>
            <content:encoded><![CDATA[<p>Context is everything when it comes to creating a design system. There are three things that you need to know before you attempt to build a design system:<br>1. Design maturity of the organization<br>2. Design maturity of the product<br>3. Design maturity of the people — sponsors, stakeholders, partners, and designers</p><p>If we say the measure of maturity is high, medium, and low for each, it is not very difficult to surmise that one size does not fit all.</p><p>For an organization that is undergoing a digital transformation, my guess would be a low-medium on all parameters with some people exhibiting a high maturity. For younger organizations that have always been digital, maturity levels are much higher.</p><p>I have built three design systems thus far and all of them have been experiments born out of my curiosity. The reason why I call them as experiments is because no other word captures the ambiguity better. This is usually an ambiguous task with an unambiguously stated outcome when it starts, for the most part. All my experiments are listed at the end of this article.</p><p>Two biggest challenges for a me when I build Design Systems are to gain clarity based on a good understanding of ground realities (opportunities, rabbit holes and risks) and communicate that to sponsors and stakeholders as soon as I can.</p><p>I am sharing my knowledge as a practical guide to create a design system based on my three experiments:</p><blockquote>Step 0: Read Nathan Curtis’ <a href="https://medium.com/eightshapes-llc/starting-a-design-system-6b909a578325">articles</a> multiple times. I promise you that this is the only resource you need during the first year. Thanks Nathan!</blockquote><p><strong>Identify what kind of Design System you want</strong><br>Most organizations have three kinds of design problems that they solve for and the notion that one design system will address all three needs will be a very costly mistake. You need three design systems — one for each</p><ol><li>Marketing</li><li>Consumer Apps</li><li>Enterprise Solutions</li></ol><p>For example, Polaris and Lightning Design Systems focus on enterprise solutions. Material Design focuses on consumer apps. A quick look at some of the <a href="https://designsystemsrepo.com/design-systems/">popular Design Systems</a> will show this difference.</p><p>However the basic foundations like grid, colours, padding and spacing can be shared between these three. <em>(Type scale should be different). </em>Atom level elements like buttons and form elements can also be shared between these three.</p><p>Depending upon the priority of the business, you can prioritize among these three. If you have budget and the right kind of people, you can start simultaneously on all three. (But please don’t make the rookie mistake of thinking that one size will fit all.)</p><p><strong>Treat Design System as an organic product, that serves other products</strong><br>A design system should be treated as a separate product with a separate roadmap and separate budgets for it to be successful, especially when it serves multiple brands, lines of business and product lines. If it is treated as a side project, it will remain as one.</p><p>Design system should be maintained in perpetual beta for it to be successful in its job.</p><p>If you are unable to secure budget or unable to build a roadmap, there is no need to fret. Start this as a side project. Others will see soon see benefits when you reduce your production time by almost 40%. Not having a Design System is not an option for you.</p><p>Also remember, trying to be perfect is a trap. Aiming for a continuous improvement and gaining momentum is a better idea. Start from where ever you are. Start with whatever you have.</p><p><strong>Identify guiding principles</strong><br>Guiding principles for design systems are different from design principles for the organization or the product. This is very important for all stakeholders to understand from the start. Also you need a metric for success. A Design systems without guiding principles or a success metric would end up in lot of energy wasted over arguments</p><p>There are no two ways about this. You need guiding principles that make sense in your context. I am sharing a set of principles that I created with my partners for one of the design systems that we built.</p><ol><li>Unified over Same: We create a unified experiences across brands and products within our ecosystem. Our attempt is to create unified and cohesive experiences that are meaningful from a user’s perspective and not to create ‘same’ experiences because it is quicker to build.</li><li>Appropriate over Right: Our measure of quality of a solution is its appropriateness in the given context. Not how perfect it is or how fast it can be delivered.</li><li>Trust over Contest: We trust and respect each others talents and abilities. We neither tell the other person how to do their job nor second guess their decision in their field of expertise.</li><li>Momentum over Everything else: We work in harmony and ship every sprint. We improve sprint over sprint.</li></ol><p><strong>Conduct an audit</strong><br>The most critical step that is often overlooked. Never underestimate the power of an audit. Even if you do not have a lot of time or budget, you should always conduct an audit of the most critical parts of the digital ecosystem. you can never go wrong with an audit. It will help you avoid a lot of quicksands, bear traps and rabbit holes.</p><p>Take stock of every pattern that is used in the current eco system.</p><p>Screenshot. Organize. Label. Repeat.</p><p>If you are a content heavy org, then lean on your Content partner and build the content model as well if they already dont have one.</p><p>Talk to your Dev partner to get the conceptual data/domain model as well. (Start <a href="https://alistapart.com/article/content-modelling-a-master-skill/">here</a> and <a href="https://medium.com/business-architected/conceptual-data-modelling-start-with-business-use-cases-10b3f2670d47">here</a> if you are new to modelling. I promise you its worth your to pick up skills to understand these diagrams)</p><p>Why are these important? With these in place, constructing an IA and creating page/flow templates becomes a breeze. Most importantly, you avoid a ton of conflict because everybody is aligned on the concept model of the product/platform.</p><p>Does it feel overwhelming? I repeat, start from where ever you are. Start with whatever you have.</p><p><strong>Build a roadmap (if you can)</strong><br>The reason I say ‘if you can’ is because there is a good possibility that the person in the drivers seat is Business or Technology. They would have goals for which Design Systems is a means to an end. In that case, you cannot push for the design system to be a product of its own without derailing the plans of the sponsor. The only available option is to influence their roadmap to make sure that you are not rendering the design system efforts useless.</p><p>In a year(more or less) they would realize that it is critical to separate the Design System roadmap. Till then you have to evangelize. Good luck.</p><p>Just remember that internal data &gt; external data &gt; complaining.</p><p><strong>Put the digital brand guidelines in place</strong><br>Grids, Colours, Type scale, Iconography are foundational to any digital product but I am not surprised when it is not the case.</p><p>Don’t step an inch forward without resolving these. It is very expensive to change these later. That doesn’t mean that you need answers for everything. Start with what you have. Create placeholders for things that need more information. Your dev partners will probably recommend tokens. Work with whatever your dev partner thinks is the right way to move forward.</p><p>Make sure all foundational elements are A11Y compliant(colour contrast and type scale to start with). In addition to being the right thing to do, early focus on accessibility also has a business advantage. It cuts down Design+Dev+QA churn due to accessibility issues. (A11Y churn can be very expensive)</p><p><strong>Build product agnostic foundational elements</strong><br>Start small. Make sure that you check all the boxes without spending an enormous amount of time. The goal while building the foundational elements should be to create agnostic elements. What I mean is that the foundational elements should be so basic that any digital team in any corner of the world should be able to use them for any brand/product by changing the CSS.</p><p>If you are short on budget and time, reusing Bootstrap or Material Design for foundational elements is a great option (if they work in your organizational context). You can easily find readymade UI Kits and code libraries.</p><p><strong>Pivot till you arrive at a Governance model that makes sense to your organization</strong><br>There is a lot of material available online that can guide you towards building a Governance model for design systems. However, what is important to realize is that we can never force fit something external into our organizational structure. It requires organizational intelligence, a lot of empathy, a lot of partners and a lot of time to build a Governance model that works best for your organization. Just keep in mind that you are building a governance for people and not processes. I have captured my experiences in <a href="https://giryer.medium.com/how-to-democratize-design-systems-f9f52be2d4d9">this article</a>.</p><p><strong>Encourage adoption</strong><br>If steps 1 through 6 are in place, then all that remains is to open the gates of the playground for everybody in the organization and to establish momentum. At this point, the main job the design system team becomes an exercise in Marketing and Project Management.</p><p><strong>Be Resourceful</strong><br>F*** constraints. Don’t complain. Don’t cut corners. Figure out a way to do the right thing and do it the right way. Doing the right thing the right way has immense long term benefits for the organization(and your mental health).</p><p>Here are notes from my experiments:<br><strong>Design System 1:</strong><br><em>Design maturity of the organization: Low<br>Design maturity of the product: Medium low<br>Design maturity of the Sponsors: Low<br>Design maturity of the Business team: Low<br>Design maturity of the Engineering team: Low <br>Design maturity of the Design team: Medium High</em></p><p>The first one was rather easy because it involved curating patterns of an existing product so that that the future releases did not introduce any rogue patterns.</p><p>The reason why we chose to curate patterns for this product was that it was a legacy product and we were not able to support every request that came our way.</p><p>The purpose of this exercise was very simple- to allow POs and Devs to move faster on bugs, minor issues and micro-improvements(with design only providing consultation). The testimony to this fact was that the library was a powerpoint presentation hosted in a common folder that was constantly updated by the lead designer as and when they encountered new use cases.</p><p><strong>Design System 2:<br></strong><em>Design maturity of the organization: Medium<br>Design maturity of the product: High<br>Design maturity of the Sponsors: Medium<br>Design maturity of the Business team: Medium <br>Design maturity of the Engineering team: Medium High <br>Design maturity of the Design team: High</em></p><p>This design system was built for a new product that was being built from scratch. We used bootstrap for all core elements and created five page types — Lists, Forms, Dashboard, Settings and Custom. The resulting component library was very comprehensive and had a high adoption. The reason for its success was that the product and engineering partners trusted the design team and did not see design or the design system as another checkbox in their list.</p><p>The team that built and consumed this was small(~20). The pages and patterns were self explanatory. The product, design and dev teams had lunch everyday at the same table. All of these were the ingredients for its success. When it was completed, it still was a library where the rules of usage and other guiding principles not explicitly written but the rules for usage of patterns were ingrained in the system as a memory. However in retrospect, I feel that we should have spent some more time in formally articulating usage and guidelines to make the system scalable.</p><p><strong>Design System 3:<br></strong><em>Design maturity of the organization: Low<br>Design maturity of the product: Medium Low<br>Design maturity of the Sponsors: Low<br>Design maturity of the Business team: Low<br>Design maturity of the Engineering team: Medium High<br>Design maturity of the Design team: Medium High</em></p><p>By far, this has been the most complex system that I have put together. Four lines of business. Five brands. 30+ applications. Three designers. One A11Y specialist. One Design System.</p><p>What comes to my mind when I think about this experience is this scene from ‘The Wrong Trousers’ featuring Wallace and Gromit :)</p><figure><img alt="Gromit from ‘Wallace and Gromit — The wrong trousers’ laying tracks ahead while the train is moving at full speed" src="https://cdn-images-1.medium.com/max/418/1*W-K10kAi2dOxXtdVHjsSHw.gif" /><figcaption>Building a Design System while the production train is moving at full speed</figcaption></figure><p>The redesign of the website started without any consideration to the design system. When I inherited it, the dev team was slicing off components from mocks and adding them to a code library (The dev team were the quasi-owners of the design systems which for them was only reusable code.)</p><p>Luckily, I had great dev partners who wanted to do it the right way. Together with them, we put in place a governance model that worked for us and that allowed us to move faster than the production train. We became a truly agile team where the design and development were not two teams but two skillsets within one team. We delivered 100+ components serving 5+ brands in the first two years resulting in huge savings. (If you want to know how to be truly agile and design + develop in the same sprint <a href="https://giryer.medium.com/how-to-design-and-develop-in-the-same-sprint-564b7d6f8b22">this</a> might be of interest to you.)</p><p>These are only a few things that you need to keep in mind before you get started. The actual operations of design system is quite complex. It involves figuring out ways for alignment among all stakeholders, buy-ins from designers, team formation, shared ownership, intake process, feedback from consumers, adoption, the contribution model and many other things that I am not listing here, including conflict management strategies.</p><p>Reach out to me on <a href="https://www.linkedin.com/in/giryer/">LinkedIN</a> if you want to see the artefacts or want to chat more about my experiences.</p><h4>Other related articles:</h4><p><a href="https://giryer.medium.com/how-to-democratize-design-systems-f9f52be2d4d9">How to democratize Design Systems?</a></p><p><a href="https://giryer.medium.com/how-to-design-and-develop-in-the-same-sprint-564b7d6f8b22">How to double your velocity in sprints?</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=700e0b020a74" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/things-you-need-to-know-before-you-build-a-design-system-700e0b020a74">Things You Need to Know Before You Build a Design System</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 10 tips on how to interview people for a job]]></title>
            <link>https://giryer.medium.com/top-10-tips-on-how-to-interview-people-627e6b0b1398?source=rss-eb5b2df92445------2</link>
            <guid isPermaLink="false">https://medium.com/p/627e6b0b1398</guid>
            <category><![CDATA[interviewing]]></category>
            <category><![CDATA[right-candidate]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[interview-tips]]></category>
            <dc:creator><![CDATA[Girish Subramanian]]></dc:creator>
            <pubDate>Wed, 07 Jun 2017 20:18:11 GMT</pubDate>
            <atom:updated>2021-06-15T17:56:41.457Z</atom:updated>
            <content:encoded><![CDATA[<p>Its so surprising that the internet is full of tips and tricks and rules on how to prepare for an interview for the interviewee but few for the interviewer. That is a little presumptuous, don’t you think? Why doesn’t anybody talk about it?</p><p>I have been attending interviews for the past few days. A few months before, I was interviewing people. While I was introspecting about my experiences from being on both sides of the table, I noticed some unmistakable patterns. I am sharing a few insights from my experiences of giving and taking interviews.</p><p>Good interviews share a few things in common in addition to the fact that both parties come out feeling good and/or learning something new about themselves.</p><p>A good interview can be a very meaningful and fulfilling interaction with a stranger which is very rare in our everyday lives.</p><p>What triggered this was a particularly bad interview followed by an excellent one. When I call it bad or excellent it has got nothing to do with the outcome. It was the way it was conducted.</p><h4>Do your homework</h4><p>Read the candidates resume. Multiple times. Make notes. Google the organizations where they have worked before. Study their previous work and be prepared with contextual questions.</p><p>Don’t go kicking the tin can as you go along. The candidates can see through that and don’t expect them to respect you or your organization.</p><h4>Be Extra Nice</h4><p>You are talking to a human being. A person sitting on the other side of the table is probably taking the biggest risk of their lives or trying to get themselves out out of a bad situation or both. Imagine the worst case scenario. Probably they had a bad day or a few bad days and all they want is someone to listen to their story or someone to provide a direction. You are probably taking to a person on the edge of despair. Show some empathy.</p><p>Be mindful and gentle. Give them the benefit of doubt. Be extra nice. Treat them like a guest. Make them feel comfortable. Offer them a glass of water or coffee. Smile. Don’t be a their ‘boss’ already.(In fact, don’t be anyone’s boss at all :) Bad attitude is a turn off for both sides. Above all, make them drop their defence in the first few minutes. Irrespective of how they present themselves outwardly, all they want to do is make a good impression. So, smile and make them feel warm and welcome, even if they did not make a good first impression. Give them some space to be their natural selves.</p><p>Just be human. And smile for god’s sake. Please don’t keep staring at your laptop all the time while they are talking to you. I know you are taking notes, but it feels like an interrogation. Spend 10 minutes after the interview to quickly jot things down. If you follow a consistent method of inquiry, it becomes easy to remember the points.</p><h4>Ask the right questions</h4><p>Be prepared with two sets of questions. One, role and skill specific. Two, person specific. It need not be a template but its better if you asked similar questions to all the candidates. Its easier to compare notes later when you are deciding between two candidates.</p><p>And start the interview gently and sincerely. Avoid cliches like, ‘Give me your elevator pitch’. They are not selling anything. Please don’t say that they are selling themselves. That doesn’t sound right. They are not selling themselves. They are looking for a meaningful thing to do with their lives and in return hope to get paid to sustain themselves and their family. Isn’t that what you want too?</p><p>Don’t start with work and skill related inquiries. And don’t start with, “So…Tell me about yourself.” Ask something that will help you know their real motivation for applying for the role. Or the motivation for choosing the profession. Ask questions that will help you know the aptitude and the attitude of the person.</p><p>First let the person speak about their personal journey. This loosens them up for further inquiry. Then check if the person has the skills to do the job. Then check if you can build a relationship with this person. Can you have lunch with this person, everyday? Does the person have any interesting hobbies outside work? And can they speak about it with passion? Can you go out on a Friday evening for a beer with this person? Can the person’s ideologies and experiences enrich you and the organization?</p><p>Some jobs require you to be a well behaved person even if you are not too skilled at what you do. Some jobs can accommodate a$$h01es as long as they extremely skilled at what they do. Are you ready for them? Just be mindful of the impact that they will have on you and your team’s mental health.</p><h4>Listen to their stories</h4><p>Even shy people like talking about themselves if they have the right audience. Be the right audience.</p><p>Encourage them to tell their stories. Everybody has a story and wants to tell them. You just have to gently nudge them.</p><p>Take interest in their life because they came all the way just because you wanted to meet them. They came to tell you their story in their own way.</p><p>Just listen.</p><h4>Be Honest</h4><p>Don’t bullshit and there is no need to feel insecure or judgemental. Respect the intelligence of the candidate. They can see through you if you are being a dishonest person.</p><p>Don’t act like you know everything. You don’t know what the other person knows. It’s alright to say that you don’t know, when you don’t. Don’t fake. Apologize instead of lying. They will respect you for that.</p><p>It’s better to tell the truth about the organization and role upfront than to have a person in the team who feels cheated by you. Also, if you warn the candidate directly or indirectly about the shortcomings of the organization or the challenges within the organization, when they choose to join, they will be mentally prepared.</p><h4>Try not to judge</h4><p>You are not looking at a replaceable part. You are looking at a unique ‘person’. Unless the job requires a customer facing job, you don’t need to worry too much of the personality flaws. Just make sure that they are sociable and the rest of the team can accommodate their quirks. As long as the person is authentic, you don’t need to worry about the intricate details of their personal choices. In fact, its none of your business.</p><h4>Trust your gut</h4><p>It’s like a first date. It need not go well, always.</p><p>We are all too used to high stakes test and we expect people to be on their best when they appear for a challenge. Experience tells that it is not possible.</p><p>Just trust your gut. No matter how hard people try to be ‘different’ in the interviews, their real personalities come through if you apply gentle pressure at the right spots. Stay far away from people who you feel are being dishonest even if they say and do all right things and seem like a perfect fit. People can fake everything. Some people are really good at it. But they can’t cheat your gut instincts.</p><h4>Stay in control</h4><p>Some interviews can go out of control. Don’t let the candidate hijack your agenda. Its your game and it must be your rules. Don’t be a control freak either. It’s a thin line and walk it according your style and your definition of being in control.</p><h4>Help them to accept the outcome</h4><p>I am sorry that the candidate is not that ‘elusive unicorn ninja’ you were looking for. If you did not know already, you will never find the ‘perfect fit’.</p><p>Put yourself in that shoe. If they do not make the cut, let them not feel like a loser. Be nice. Please. Help them accept the outcome. Give meaningful and relevant feedback, if you have any, so that they can improve their chances of finding a job or seek appropriate help. Be nice. Please.</p><p>Also, If you change your mind or by a twist of fate you end up working with them in the future, you will still be able to take it from a there on a positive note. (They might be your manager some day!)</p><h4>Hire them for yourselves</h4><p>Don’t hire them just for the organization. Hire them for yourselves. See it as a great opportunity to expand your own understanding of the world while getting paid for it. Even if they make you a little uncomfortable. It’s alright you know as long as your values align. People respond to earnestness, sincerity, honesty and politeness very well and will respect you for that. For the rest of their lives.</p><h4>Good Karma</h4><p>Don’t see this as an opportunity to validate your own worth or as a hindrance in your busy schedule. It as an opportunity to help a fellow human being and accumulate good karma.</p><p>Disagree with something? Have I forgotten something? Do you like something? Don’t be shy to write a couple of lines.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=627e6b0b1398" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Inscrutable Ego and the Seven Selves]]></title>
            <link>https://giryer.medium.com/my-inscrutable-ego-and-the-seven-selves-d50a184dbf9a?source=rss-eb5b2df92445------2</link>
            <guid isPermaLink="false">https://medium.com/p/d50a184dbf9a</guid>
            <category><![CDATA[waiting]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[conversations-with-self]]></category>
            <category><![CDATA[ego]]></category>
            <dc:creator><![CDATA[Girish Subramanian]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 19:01:31 GMT</pubDate>
            <atom:updated>2017-04-04T22:47:41.452Z</atom:updated>
            <content:encoded><![CDATA[<p>One moment, it all makes sense. Life, I mean. The next, it seems as confusing as before. Sometimes more. All my attempts to seek clarity, momentarily succeed and then leave me more confused.</p><p>This was me a few years ago. I couldn&#39;t stand it anymore. It was draining me from within. I needed a logical explanation for this confusion. Not some metaphysical salve to soothe my internal dissonance. I don’t mind metaphysical explanations to smooth out small imperfections like a putty before painting, as long as the structure is built on something that seems like logic. Yes. I live under the Tyranny of Logic. Sorry, but that’s how it is. It helps me remain calm. At times.</p><p>So…I meditated on this conundrum. Even drank myself silly. Used traditional methods to expand my consciousness. Anything that helped. One early morning at around 3 or 4, in a stupor(of what, I cant recollect), I drew seven concentric circles on my sketchbook and scribbled something illegible within each circle and went back to sleep.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gOiBOIj4A7wEOlVbRDGjrQ.jpeg" /></figure><p>Got up later that day and stared at it. Couldn’t remember a thing. Couldn’t decipher a thing. But there was an internal resolution and peace. I knew I was close to the explanation I sought. But I did not want to rush it.</p><p>I don’t like to force anything except the last bit of the toothpaste out of a tube. Can’t see it going waste. Those are the last bits of my parsimonious mother’s teachings that refuse to be rinsed out of my system.</p><p>Anyway, I did not want to force it out. I was excited and happy like my young self who looked forward to the next issue of his favorite children’s magazine. He knew it was coming. He had to wait and read the latest issue many times over. But he knew that the next issue was on its way.</p><p>I knew that I had to wait. Just like him.</p><p>And then when I was least expecting, it came to me during a conversation with my philosophical friend. He seemed to be pleasantly surprised.</p><p>“Where did you read this?”</p><p>“Nowhere. It came out of right here” I tapped my head.</p><p>He laughed, “Its good. Write about it. It makes sense.”</p><p>That was three years ago.</p><p>I have revisited it multiple times and I feel that the time for it to be written is now. Did I tell you that I don’t like to force things. Not worth it. Not at all.</p><p>So here it is.</p><p>Do you talk to yourself?</p><p>Do you criticize yourself?</p><p>Do you appreciate yourself?</p><p>Do you offer counsel to yourself?</p><p>Do you goad yourself?</p><p>Do you inspire yourself?</p><p>Do you bully yourself?</p><p>How frequently do you do this?</p><p>Have you tried to count how many of you are there?</p><p>I have. Seven. There are seven people(at least) within you. And they bicker with each other all the time. Like siblings living in a small house. They fight with each other for everything. From parent’s attention to a few seconds more in the toilet. They push and pull and argue with each other trying to get the last word in this infinitely long drawn argument that we call life.</p><p>Here are those seven. This is the gist of all that I have read and heard and thought and experienced, but I cant tell when and where. See if you can recognize them.</p><p>1. What I am — Objective self</p><p>2. What I think I am — Subjective Self</p><p>3. What others think I am — Subjective Other</p><p>4. What I think others think of me — Perceived Self</p><p>5. What others think I think of myself — Perceived Other</p><p>6. What I want others to think of me — Projected Self</p><p>7. What others want me to think of myself — Projected Other</p><p>Here is how I explain each of these:</p><p>“He thinks of himself as the ‘Gift of God’ on earth(5). Such an Idiot(3). He should know that he is just as ordinary as anybody else and is no special snowflake(7)”</p><p>“Everybody thinks I am an idiot(4). I want them to think that I am an intelligent person and not an idiot(6). I know they are smarter than me but I don’t think I am a complete idiot(2).”</p><p>I do not know about #1. Not even trying to go anywhere near that. Not at least now. (I am afraid that I will sound like an idiot :))</p><p>I am not going to explain each one in detail but I will leave it to you to form your own narrative around your ‘selves’.</p><p>We constantly engage in an inner struggle with ourselves. One trying to win over the other. Usually one(or two or more) is more dominant than the other, making the person what they are. Compassionate, people-pleaser, an honest but rude ass, dishonest but gentle, Confident Idiot, True Leader and seven billion other flavors.</p><p>There are as many ways of living as there are people inhabiting this world. All these are a result of this internal conflict unique to every person. It is the impurity that gives the glass its color and the person their character. So don’t worry too much about these internal conflicts. Just listen to the interesting conversations that your internal selves have with each other. The person who listens to them with amusement is probably the #1. Who knows?</p><p>Feel the push of the spirit within you. You may choose to do nothing about it and choose to listen to any one of your other selves. It’s alright. Do what comes naturally. Don’t force yourself before you are ready. But listen to the spirit. It will push you back to your path — sooner or later.</p><p>Resist it. Reason with it. Scare it. Ignore it. Plead with it. Do whatever your dominant self wants to do. But eventually the spirit wins the argument. Just by waiting for you to understand what it is trying to tell you.</p><p>You may spend some time listening to your other selves, but it is not time wasted because you were being prepared to understand what the spirit was trying to say. Just as you need to feel the language before you can feel the poetry.</p><p>Don’t force things. Listen to your ‘selves’. Be amused. Its worth the wait.</p><p>Peace.</p><p>Breathe in… Breathe out…Breathe in… Breathe out…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d50a184dbf9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yet another trick to be more Productive and Happy]]></title>
            <link>https://giryer.medium.com/i-am-tired-of-being-productive-and-happy-56cba36969ec?source=rss-eb5b2df92445------2</link>
            <guid isPermaLink="false">https://medium.com/p/56cba36969ec</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[productivity-hacks]]></category>
            <category><![CDATA[purpose]]></category>
            <category><![CDATA[happiness]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Girish Subramanian]]></dc:creator>
            <pubDate>Sun, 02 Apr 2017 16:44:01 GMT</pubDate>
            <atom:updated>2021-09-07T17:31:56.039Z</atom:updated>
            <content:encoded><![CDATA[<p>When was the last time a piece of advice or a tip or a trick was not thrown at you by people and the internet in general on how to be ‘Productive’ and ‘Happy’? It is happening to me everyday now. Every…day!</p><p>Till some time back I was fairly happy and reasonably productive. Or so I thought. I got up on most mornings feeling fairly excited looking forward to my morning rituals followed by my chai laden with ginger and pepper. If either of those did not happen, I would feel very upset. I would whine and my wife would gently nudge.</p><p>“Look outside at all the<em> </em><a href="https://pbs.twimg.com/media/DprQoqRVsAAdvQi.jpg"><em>paarijaatams</em></a>. They are so beautiful. Take that in. Slow down”</p><p>I would then open the windows and take a deep breath of the morning breeze laced with the fragrance of all the fallen <em>paarijaatams</em>. We would then sit near the window, chatting about this and that for about 30–40 minutes before we started our daily grind. We both looked forward to this morning chat. We would talk about all sorts of things. Politics, cinema, her dance, my work, dreams that we remembered from last night. There was no agenda or rules for this morning talk. We just let it flow. Some days are so interesting that we do not realize that we are getting late for work.</p><p>Some days we would get up with a heavy head and heavier heart from previous days fight and not talk to each other in the morning. I would wait in bed till my wife left and I would have my tea alone. Or the other way around depending on our schedules. I don’t like those days when I am fighting with my best friend. They are the worst.</p><p>At work, I have similar days. Really good ones and really bad ones. Like a spectrum. I realized that everybody else around us can sense what we are feeling. They know when we are happy and when we are tired of the place, mainly its people and when we start putting in more bad days than good days.</p><p>This happens with my wife too at her studio as well. She says it’s more obvious as it is a body practice and it is clearly visible on people’s movements. I worked in a place that had an identity crisis (Are we a product company, service company or a consultancy?) and my wife is a performing artist. But we have very similar stories of our workplace joys and pain except that I was paid in a regular frequency and new releases happened every two to three weeks. I receive my pay in regular frequencies. She receives them whenever there is a show. My highs and lows are evenly spread across time (usually coinciding with every major release). Her highs and lows are more intense depending on the success of her shows or more importantly, what she thought of her own performance.</p><p>Overall, my experience tells me that if we could measure highs and lows of our life, they eventually even out despite the frequency.</p><p>So, if you are going to be super productive for 5 years, you will be shit for 5 years, either at one stretch or spread across multiple years. Similarly if you have a truckload of unhappy moments, there is another truckload of happiness, that you have already experienced or is in store for you.</p><p>Yes. Everything eventually cancels out.</p><p>LHS=RHS.</p><p>Equilibrium.</p><p>So here is the thing. Stop trying to be happy and productive.</p><p>Seriously Stop. Yes. Stop. Now. It is safe.</p><p>Here are two better ideas to keep your mind busy — Dharma and Karma.</p><p>Dharma has many meanings, but I choose one: Duty.</p><p>Dharma is my social compass. They are the rules for the social roles that I play. My duty as a son. My duty as a husband. My duty as a brother. My duty as a designer. My duty as a writer. My duty as a citizen. My duty as a wanderer.</p><p>The world expects something from the person playing that role to maintain the equilibrium. And it is my duty to play it well. Without doubts. Without greed. Without being lazy. If you have a duty, stop whining about it. Stop arguing with it. You can leave it if you want to, but if you can’t, just do it already.</p><p>If you hate it so much, choose some other duty. If you can’t, accept it gracefully and be truthful to the task at hand. And try to be nice about it, if you can.</p><p><em>It is better to perform ones own duty and fail, than to perform someone else’s duty really well.</em></p><p>Karma is my personal soup. My shit. It is my tree in the forest that fell when no one was around. As I sow, so I reap. Its my personal equilibrium. I cause a small pain. A small pain returns to me. I give great joy. Great joy comes to me. For every great joy that I experience a great pain is in store for me. In equal measures. There is no multiplication factor involved in it. None whatsoever. It just evens out. So if I am undergoing pain, it means that I am cancelling out a great joy that I have already experienced or I am building credit for a great joy to come.</p><p>Simple as that.</p><p>Body and mind seeks balance. No matter how hard I try, my bodymind (or mindbody, whatever suits you) will find a way of cancelling it out.</p><p>That is why I have been struggling to keep up with my productivity and happiness for some time now. Too many people telling me that I need to be more productive and more happy and my bodymind telling me that I do not.</p><p>I do feel that I need to be more productive or happy. Also, it doesn’t matter as it will cancel out in the end. I feel fine as I am.</p><p>I would rather spend that time to understand the complexities of my own understanding or just simply stare outside the window at all the <em>paarijatams</em> that have fallen last night or read <em>Swami and Friends</em> again or hold my wife’s hands or be silly and clown around the house.</p><p>It all balances out. The more time I waste, the more productive I will get. The more sad I get, the happier I will become.</p><p><em>I may not get what I desire, but I will never escape what I deserve.</em></p><p>So instead of tips and tricks for happiness and productivity, I would rather try and make myself more deserving of the things I wish for.</p><p>That’s my tip to be more productive and happy. The top 10 ‘successful’ people follow this. If you don’t believe me, go find out for yourselves while I look forward to my Sunday afternoon nap.</p><p>Go on now. Its your turn to do something. Or not.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56cba36969ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Quality of Digital User Experience]]></title>
            <link>https://medium.com/geekculture/the-ux-path-8dbaa2e00e0e?source=rss-eb5b2df92445------2</link>
            <guid isPermaLink="false">https://medium.com/p/8dbaa2e00e0e</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[interface-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Girish Subramanian]]></dc:creator>
            <pubDate>Wed, 29 Mar 2017 15:48:43 GMT</pubDate>
            <atom:updated>2021-09-03T20:26:48.390Z</atom:updated>
            <content:encoded><![CDATA[<p>What makes us feel that something is a good digital experience? Is it because the interface was ‘intuitive’ ? Or because the product or a service was ‘user friendly’? Or because it was ‘simple’? Or a combination? What do they all really mean from a users perspective? What place do cultural nuances have in a digital world that is increasingly getting flattened and is there a value to them?</p><p>Much has been said and written about user experience in the past 30 years ever since Prof. Donald Norman coined the word and became the first ‘User Experience Architect’ in the world.</p><p>Here is my contribution to the knowledge base, based on my experiences as a practicing Experience Designer.</p><h3>Aesthetics of Experience</h3><p>When we talk about the need for a User Experience what we are really saying is the need for an ‘Aesthetic Experience’ for someone who is using the product or the service. The nature of an Aesthetic Experience of any kind has four contributing factors:</p><p>1. The nature of the Representation</p><p>2. The nature of the Perception/Taste/Judgement</p><p>3. The nature of the Experience</p><p>4. The nature of the Meaning</p><p><strong>Representation</strong> is the materiality of the Experience. The Form, Colour, Composition, Movement, Notes (in the case of auditory and olfactory expressions) etc.</p><p><strong>Perception</strong> is a person becoming aware of the experience through the senses. Taste is the perception of an experience and the preference of a person for a certain kind of experience over the other. (Cultural contexts play a critical role here)</p><p><strong>Experience</strong> is a tricky word, so let me call John Dewey to my rescue. Dewey’s account of aesthetic experiencing focuses on experience as an interactive relationship between the perceiver and the object. Dewey uses the term ‘experience’ in two ways. The first indicates the interactive relationship between the individuals and the world around them. The second way indicates a special sort of the first kind. This special sort Dewey calls an Experience. An experience is any experience that principally has the characteristic of being unified and complete.[1]</p><p>We are interested in the second kind…the special sort. This experience is what we aim to create for people using any object or a system and I prefer to call this an ‘Integrated Experience’.</p><p><strong>Meaning</strong> is what the source or sender intended to express, communicate or convey to the perceiver, and what the perceiver inferred in the current context.</p><p>For the sake of simplicity, let us assume a linearity of events.</p><p>1. A person sees, hears, feels, smells, tastes the stimulus or representation</p><p>2. The person perceives it in a certain manner based on their memories</p><p>3. The person experiences this</p><p>4. The person derives a meaning out of this experience</p><p>5. This experience updates an old memory or is stored as a new memory</p><p>… and this cycle repeats infinitely.</p><p>Let me remind you that I am assuming linearity so that we remember the events –</p><h4>Representation leads to Perception leads to Experience leads to Meaning.</h4><h3>Towards an Integrated Experience</h3><p>In a good experience, the interface is integrated into the situation and into the act. An interface that sticks out without letting you enjoy an experience or even merely reminding you of its presence is often perceived as a ‘bad’ experience. Bad experiences are stickier than the good ones. Unfortunately, thats how most of us are wired.</p><p>When was the last time you watched a movie in a theater? Do you remember ‘experiencing’ the seat while you were watching the movie? If you did, it was probably because it was a badly designed seat or a badly made movie or both. <em>(There is always a rare edge case, where the design of the seat was so good that you remember it! We are not talking about them. We are talking about the ‘invisible’ ones or the ‘elevating’ ones)</em></p><p>Most of our interfaces and interactions for applications are like theatre seats. They should never come in the way of experience. If anything they should elevate it.</p><blockquote><strong>To elevate any experience, an interface should posses three qualities: Familiarity, Coherence and Fluency.</strong></blockquote><h4>Familiarity:</h4><p>Preferences need no inferences. Familiar things look less threatening. <em>‘Mere Exposure Effect’ </em>tells us that people tend to develop preferences to things merely because they are familiar with them.</p><p>According to Robert Zajonc, affective responses to stimuli happen much more quickly than cognitive responses, and that these responses are often made with much more confidence.</p><p>In the 1960s, a series of laboratory experiments by Robert Zajonc demonstrated that simply exposing subjects to a familiar stimulus led them to rate it more positively than other, similar stimuli which had not been presented. In the beginning of his research, Zajonc looked at language and the frequency of words used. He found that overall positive words received more usage than their negative counterparts. In later years, he moved on to show similar results for a variety of stimuli such as polygons, drawings, photographs of expressions, nonsense words, and idiographs, as well as when being judged by a variety of procedures such as liking, pleasantness, and forced-choice measures.[2]</p><h4>Coherence:</h4><p>Sense of Coherence relates to the resources and the mechanisms and interactions involved in the adaptive capacity of humans.</p><p>Optimal human performance — at home, in school, in the community or at work — requires that a person experience themselves as having a sense of coherence.</p><p>The sense of coherence is comprised of three factors:</p><p>1. A sense of comprehensibility</p><p>2. A sense of Manageability</p><p>3. A sense of Meaningfulness [3]</p><p><strong>A sense of comprehensibility:</strong></p><p>Do you feel that you can understand things, that things make sense and are not confusing?</p><p>Do you feel that things are predictable or can be expected? In other words, do you feel like you know what’s going to happen next, or that you know what’s coming?</p><p><strong>A sense of manageability:</strong></p><p>Do you feel that things are manageable or within your control, that things can be handled or taken care of?</p><p>Do you feel you have the skills or ability, the support, the help, or the resources necessary to take care of things?</p><p><strong>A sense of meaningfulness:</strong></p><p>Do you feel that things are interesting or fascinating, a source of pleasure or satisfaction?</p><p>Do you feel that things are really worth it, that there is good reason or purpose to care about what happens? [4]</p><p>Cultural contexts play a major role in meaning creation. All the questions above are heavily coloured by your cultural exposure.</p><h4>Fluency:</h4><p>When I speak about fluency, I speak about both:</p><p><strong><em>Cognitive fluency and the Operational fluency.</em></strong></p><p>Cognitive fluency is the the perceived ease of usage of a system or an object and the Operational Fluency is the actual fluency that is achieved during operation.</p><p>The earlier one is necessary for the person to confidently approach the interface and start using it without any fear. This leads to a faster learning cycle. The latter is eventually achieved irrespective of the difficulty of the interface by continuous operation. It is when the Operational fluency is achieved that one feels like an ‘Expert’ and the interface becomes ‘Invisible’. The sign of a well designed interface is that the person using the system or the object reaches this state sooner than later.</p><p>Like the previous section, let me again assume linearity for the sake of simplicity and this is what I call as the <strong>The UX Path</strong>:</p><h3>Familiarity leads to Coherence leads to Fluency leads to Integrated Experience.</h3><p>How do we translate these abstract concepts into a procedural reality? What steps should we take to ensure a meaningful integrated experience? How can we truly measure experience? What would a reasonable set of metrics that will help us measure this? How do we translate this into a set of repeatable actions that can be customized to achieve predictable outcomes?</p><p>These are some of the questions that occupy my mind everyday. Connect with me on <a href="https://www.linkedin.com/in/giryer/">LinkedIn</a> if these questions interest you and if you want to solve these issues in your organization. Always happy to chat!</p><p><strong>REFERENCE</strong>:</p><p>[1] Fenner, D. E. (2003). Introducing aesthetics. Westport, CT: Praeger.</p><p>[2] Zajonc, R. B. (1968). Attitudinal Effects Of Mere Exposure. Journal of Personality and Social Psychology, 9(2, Pt.2), 1–27. doi:10.1037/h0025848</p><p>[3] Griffiths, C. A., Ryan, P., &amp; Foster, J. H. (2011). Thematic analysis of Antonovsky’s sense of coherence theory. Scandinavian Journal of Psychology, 52(2), 168–173. doi:10.1111/j.1467–9450.2010.00838.x</p><p>[4] Everyday Psychology: The Sense of Coherence*. (n.d.). Retrieved July 04, 2016, from http://www.everydaypsychology.com/2007/04/sense-of-coherence.html#.V3pB8Vdff0h</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8dbaa2e00e0e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/the-ux-path-8dbaa2e00e0e">On Quality of Digital User Experience</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Jargon]]></title>
            <link>https://medium.com/series/ux-jargon-eca04ccf3d72?source=rss-eb5b2df92445------2</link>
            <guid isPermaLink="false">https://medium.com/p/eca04ccf3d72</guid>
            <dc:creator><![CDATA[Girish Subramanian]]></dc:creator>
            <pubDate>Wed, 29 Mar 2017 14:58:43 GMT</pubDate>
            <atom:updated>2017-03-29T18:37:58.319Z</atom:updated>
            <content:encoded><![CDATA[<h3>Bridging the gap between the theory and practice of Experience Design</h3><h3>A/B Testing</h3><p>Which one is better? This one or that one?</p><p><a href="https://uxjargon.wordpress.com/2014/12/29/ab-testing/">https://uxjargon.wordpress.com/2014/12/29/ab-testing/</a></p><h3>Aesthetic -Usability Effect</h3><p>Attractive things work better.</p><p><a href="https://uxjargon.wordpress.com/2014/12/13/2-aesthetic-usability-effect-attractive-things-work-better/">https://uxjargon.wordpress.com/2014/12/13/2-aesthetic-usability-effect-attractive-things-work-better/</a></p><h3>Affordance</h3><p>Physical appearance of an object that clearly communicates how to use it.</p><p><a href="https://uxjargon.wordpress.com/2014/12/03/3-affordance/">https://uxjargon.wordpress.com/2014/12/03/3-affordance/</a></p><h3>Bauhaus</h3><p>First Modern Design School.</p><p><a href="https://uxjargon.wordpress.com/2014/11/23/4-bauhaus-also-see-vkhtumas-and-ulm/">https://uxjargon.wordpress.com/2014/11/23/4-bauhaus-also-see-vkhtumas-and-ulm/</a></p><h3>Brainstorming</h3><p>Best when done among friends.</p><p><a href="https://uxjargon.wordpress.com/2014/11/13/brainstorming/">https://uxjargon.wordpress.com/2014/11/13/brainstorming/</a></p><h3>Call to Action</h3><p>Do this now.</p><p><a href="https://uxjargon.wordpress.com/2014/11/03/6-call-to-action/">https://uxjargon.wordpress.com/2014/11/03/6-call-to-action/</a></p><h3>Card Sorting</h3><p>Where does this piece belong?</p><p><a href="https://uxjargon.wordpress.com/2014/10/24/7-card-sorting/">https://uxjargon.wordpress.com/2014/10/24/7-card-sorting/</a></p><h3>Chunking</h3><p>Seven plus-or-minus two</p><p><a href="https://uxjargon.wordpress.com/2014/10/14/8-chunking/">https://uxjargon.wordpress.com/2014/10/14/8-chunking/</a></p><h3>Clickstream</h3><p>Record user clicks on a webpage.</p><p><a href="https://uxjargon.wordpress.com/2014/10/04/9-clickstream/">https://uxjargon.wordpress.com/2014/10/04/9-clickstream/</a></p><h3>Cognition</h3><p>Think before you act.</p><p><a href="https://uxjargon.wordpress.com/2014/09/24/10-cognition/">https://uxjargon.wordpress.com/2014/09/24/10-cognition/</a></p><h3>Cognitive Biases</h3><p>No matter how you do it, you may be wrong.</p><p><a href="https://uxjargon.wordpress.com/2014/09/14/11-cognitive-biases/">https://uxjargon.wordpress.com/2014/09/14/11-cognitive-biases/</a></p><h3>Cognitive Dissonance</h3><p>The hours are long, the pay is mediocre, nobody respects my contributions but I LOVE my job!</p><p><a href="https://uxjargon.wordpress.com/2014/09/13/cognitive-dissonance/">https://uxjargon.wordpress.com/2014/09/13/cognitive-dissonance/</a></p><h3>Cognitive Load</h3><p>“TMI”</p><p><a href="https://uxjargon.wordpress.com/2014/09/03/cognitive-load/">https://uxjargon.wordpress.com/2014/09/03/cognitive-load/</a></p><h3>Confidence Interval</h3><p>The range in which a parameter is most likely to appear.</p><p><a href="https://uxjargon.wordpress.com/2014/08/23/confidence-interval/">https://uxjargon.wordpress.com/2014/08/23/confidence-interval/</a></p><h3>Cooperative Principle</h3><p>Truthfulness. Precision. Relevance. Clarity.</p><p><a href="https://uxjargon.wordpress.com/2014/08/14/cooperative-principle/">https://uxjargon.wordpress.com/2014/08/14/cooperative-principle/</a></p><h3>Color Theory</h3><p>Make that button redder. That way people wont miss it.</p><p><a href="https://uxjargon.wordpress.com/2014/08/03/color-theory/">https://uxjargon.wordpress.com/2014/08/03/color-theory/</a></p><h3>Copy</h3><p>Immature artists imitate. Mature artists steal.</p><p><a href="https://uxjargon.wordpress.com/2014/07/31/copy/">https://uxjargon.wordpress.com/2014/07/31/copy/</a></p><h3>Design Patterns</h3><p>. …- . .-. -.– — …. .. -. –. .- .-. — ..- -. -.. ..- … .. … .- .–. .- — — . .-. -.</p><p><a href="https://uxjargon.wordpress.com/2014/07/26/design-patterns/">https://uxjargon.wordpress.com/2014/07/26/design-patterns/</a></p><h3>Data-Ink Ratio</h3><p>Useful Information Vs Junk</p><p><a href="https://uxjargon.wordpress.com/2014/07/23/data-ink-ratio/">https://uxjargon.wordpress.com/2014/07/23/data-ink-ratio/</a></p><h3>Discoverability</h3><p>The ability of something to STAND OUT in its setting.</p><p><a href="https://uxjargon.wordpress.com/2014/07/19/discoverability/">https://uxjargon.wordpress.com/2014/07/19/discoverability/</a></p><h3>Embodiment</h3><p>The mind is in the matter.</p><p><a href="https://uxjargon.wordpress.com/2014/07/11/embodiment/">https://uxjargon.wordpress.com/2014/07/11/embodiment/</a></p><h3>Eye Tracking</h3><p>The holy grail of Usability Studies.</p><p><a href="https://uxjargon.wordpress.com/2014/07/03/eye-tracking/">https://uxjargon.wordpress.com/2014/07/03/eye-tracking/</a></p><h3>Failure</h3><p>Failing is fun.</p><p><a href="https://uxjargon.wordpress.com/2014/06/28/failure/">https://uxjargon.wordpress.com/2014/06/28/failure/</a></p><h3>Fitts’s Law</h3><p>Its quicker to click a big object closer to the cursor.</p><p><a href="https://uxjargon.wordpress.com/2014/06/20/fittss-law/">https://uxjargon.wordpress.com/2014/06/20/fittss-law/</a></p><h3>Five Hat Racks</h3><p>L A T C H</p><p><a href="https://uxjargon.wordpress.com/2014/06/14/five-hat-racks/">https://uxjargon.wordpress.com/2014/06/14/five-hat-racks/</a></p><h3>Flexibility-Usability Trade off</h3><p>More Customizable = Less Usable.</p><p><a href="https://uxjargon.wordpress.com/2014/06/04/flexibility-usability-trade-off/">https://uxjargon.wordpress.com/2014/06/04/flexibility-usability-trade-off/</a></p><h3>Fogg’s Behaviour Model</h3><p>B = mat</p><p><a href="https://uxjargon.wordpress.com/2014/05/29/foggs-behaviour-model/">https://uxjargon.wordpress.com/2014/05/29/foggs-behaviour-model/</a></p><h3>Gestalt Laws</h3><p>The whole is ‘other’ than the sum of all parts.</p><p><a href="https://uxjargon.wordpress.com/2014/05/21/gestalt-laws/">https://uxjargon.wordpress.com/2014/05/21/gestalt-laws/</a></p><h3>Grid</h3><p>The structure that holds your design</p><p><a href="https://uxjargon.wordpress.com/2014/05/12/grid/">https://uxjargon.wordpress.com/2014/05/12/grid/</a></p><h3>Hawthorne Effect</h3><p>Presence of the observer changes the nature of the observed.</p><p><a href="https://uxjargon.wordpress.com/2014/05/06/hawthorne-effect/">https://uxjargon.wordpress.com/2014/05/06/hawthorne-effect/</a></p><h3>Heuristic</h3><p>Rule of thumb, an educated guess, an intuitive judgment, stereotyping, profiling, common sense…</p><p><a href="https://uxjargon.wordpress.com/2014/05/01/heuristic/">https://uxjargon.wordpress.com/2014/05/01/heuristic/</a></p><h3>Heuristic Evaluation</h3><p>Experts tell what is wrong with your product.</p><p><a href="https://uxjargon.wordpress.com/2014/04/24/heuristic-evaluation/">https://uxjargon.wordpress.com/2014/04/24/heuristic-evaluation/</a></p><h3>Hick’s Law</h3><p>More Choices. More Time. Less Choices. Less Time.</p><p><a href="https://uxjargon.wordpress.com/2014/04/16/hicks-law/">https://uxjargon.wordpress.com/2014/04/16/hicks-law/</a></p><h4>More to follow</h4><p>from my blog <a href="http://www.uxjargon.com/">uxjargon.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eca04ccf3d72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Brief History of (UX) Design and the simple reason why people fail to understand what it is all…]]></title>
            <link>https://giryer.medium.com/a-brief-history-of-ux-design-e8e8c34a6764?source=rss-eb5b2df92445------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8e8c34a6764</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[history-of-design]]></category>
            <dc:creator><![CDATA[Girish Subramanian]]></dc:creator>
            <pubDate>Wed, 29 Mar 2017 14:27:56 GMT</pubDate>
            <atom:updated>2018-11-15T15:38:30.886Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The Brief History of (UX) Design and the simple reason why people fail to understand what it is all about</strong></h3><p>Before I start repeating the popular narrative of Taylor-Toyota-Dreyfuss-PARC-Don Norman-Apple, I want to briefly talk about the history of Design and the Process. It was shocking to me that a timeline of design is spreading across the internet without the mention of Bauhuas and Ulm. The history of UX Design is not divorced from the history of design itself. It is a continuation of the same idea. Hence this article:</p><p>All major human activity can be broadly simplified to two distinct categories: Making Tools and Telling Stories.</p><p>It is the result of these two tasks being done continuously since the beginning of civilization that we have the myriad of experiences around us. Ever since the first protohuman chipped the first flint tools or painted the first cave painting, the ‘Idea of Design’ has been in existence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*UOz76Dq9g28w5PKl76-6cg.jpeg" /><figcaption><em>Acheulean handaxe found in Douro valley, Zamora, Spain. [Source: </em><a href="https://en.wikipedia.org/wiki/Stone_tool#/media/File:Hand_axe_spanish.gif"><em>Wikipedia</em></a><em>]</em></figcaption></figure><p>Since then we have been constantly engaged in making houses, objects and graphic arts across ages and cultures. Till the industrial revolution, it was carried out by craftsmen and was artisanal in nature. The processes and styles of different crafts kept evolving with time and the advent of new tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*j-AJQmWg83dBLYqD6TlCNQ.png" /><figcaption><em>A woodcut of Shoemakers, presumably in their guild. [Source: </em><a href="https://en.wikipedia.org/wiki/Guild#/media/File:Shoemaker_Book_of_Trades.png"><em>Wikipedia</em></a><em>]</em></figcaption></figure><p>During these periods the design activity was predominantly carried out by ‘Guilds’ and followed the Master-Apprentice model. Remnants of this model can still be seen today in traditional crafts and in some contemporary artisanal practices.</p><p><strong>BAUHAUS</strong></p><p>With Industrial revolution came mass manufacturing and brought a different set of constraints along with its obvious advantages. Bauhaus(1919–1933) along with Vkhutemas(1920–1930) laid the foundations for modern design thought. They became the first two schools to formally train ‘artist-designers’. With close similarities in intent, organisation and scope, these two schools aimed at merging the traditional craft tradition with modern Technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*HdEC9FLApki4Bw5w7iGElQ.png" /><figcaption>Bauhaus at Dessau [Source: <a href="https://en.wikipedia.org/wiki/Bauhaus#/media/File:Bauhaus.JPG">Wikipedia</a>]</figcaption></figure><p>In his prospectus, Walter Gropius, the founder of Bauhaus, formulates three principal aims:</p><p>1. To unite all arts to allow painters, sculptors and craftsmen to work harmoniously on cooperative projects.</p><p>2. To raise the status of craftsmen practicing applied art and decorative art to the same level as those involved in fine art.</p><p>3. To maintain close liaison with the leaders of the main crafts and industries in the country, to ensure the school operated in line with their basic requirements.</p><p>Bauhaus’ aim was to train artists, architects and designers to accept and anticipate the 20th century needs. Second, it wanted to eliminate traditional boundaries between art, architecture and craft. Third and probably the most critical, it hoped for a marriage between art and industry — a synthesis of design and production. [1]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*UGaVtbpI1-FbW1f4iimZvw.png" /><figcaption><em>Wassily Chair by Marcel Breur — Synthesis of Design and Production [Source: l</em><a href="http://www.lonytt.org/comfy-wassily-chair-for-your-furniture-ideas/original-wassily-chair-breuer-chairs-wassily-chair/"><em>onytt.org</em></a><em>]</em></figcaption></figure><p>After Walter Groupius, his successor Hannes Meyer distanced the discipline of design from any lingering taste of craft and the fine art-ness and famously said,” As a ‘University of Design’, Bauhaus is not an artistic but a social phenomenon.”</p><p>By the time Mies van der Rohe took his place as the director of Bauhaus in 1930’s the political climate in Germany was not suitable for ideas of Architecture and Design that Bauhaus propagated. After a brief ideological struggle with the ruling National-Socialist German Workers’ Party which did not like the idea of ‘Modernism’, Mies van der Rohe decided to shut the school down in 1933.</p><p><strong>ULM</strong></p><p>Hochschule für Gestaltung Ulm or HfG or the Ulm School of Design (1953–1968) started as a continuation of Bauhaus under Max Bill after the World War II, and it quickly abandoned the model to innovate a new model of design- the ‘Ulm Model’ which is the blue print for most design schools even today.</p><p>Founded in the memory of Hans and Sophie Scholl, who were executed by the Nazis as members of the resistance, HfG Ulm was established by their younger sister, Inge Scholl with Otl Aicher and others. [2]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*-QAtOg1fhUp6BbpF854H6Q.png" /><figcaption><em>Ulm School of Design [Source: </em><a href="https://en.wikipedia.org/wiki/Ulm_School_of_Design#/media/File:1955_Foto-HansGConrad_HfGUlm_Architekt-MaxBill.jpg"><em>Wikipedia</em></a><em>]</em></figcaption></figure><p>Under the leadership of Tomas Maldonado, the school dropped the “artist” focus of Max Bill and proposed a new philosophy of education as an “operational science”, a systems-thinking approach which embodied both art and science.[3]</p><p>Maldonado saw the design process as a system embodying both scientific-based and intuitive-based thinking, HfG adopted new way of thinking. Aesthetic considerations were no longer the primary conceptual basis of design. The professional designer would be an “integrator” with responsibility for integrating a large number of specialties in addition to aesthetics, mostly the diverse requirements of materials, manufacturing and context of product use, as well as considerations of usability, identity and marketing.[4]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*beQmcC9qusuuBZE9obDamA.png" /><figcaption>Braun Poducts [Source: <a href="http://d2t44wh9rnwl5y.cloudfront.net/gsc/1HGRQP/57/7b/d2/577bd2f2800f4faf82a0c1b1380302c9/images/history_of_ux/u1289.png?token=dc84851af32a87a0f909f40aeada99c8">uk.braun.com</a>]</figcaption></figure><p>I am reproducing an interview of Dr Rene Spitz by Steven Heller, because I could neither explain it better nor could I find anything explained the ‘Spirit of Ulm’ better.</p><p>“ There are three main characteristics that distinguish HfG from every school of design. First, it was based more than any other school on dealing with the question of what the social responsibility of designers is. Second, it was a strong impulse for the development of design as a research-based activity. Third, the HFG Ulm integrated all disciplines, not only within design, but also humanities, engineering, sciences, politics and economy. The designer should work as a team player, not as an artist.</p><p>The integration of various forms of creative activity was a major feature of the HfG Ulm. The objective was not the technical idiot, but the generalist, based on strong critical judgment and solid experience.</p><p>From 1953 to 1962 there was a mandatory, common first year of study, the so-called Grundlehre. As a result, the students learned to recognize inter-relationships. Only then, the students chose one of the four directions: visual communication, product design, building and information, and later film. But there were also students who changed their discipline. And since the school was small, separation of each other was impossible.</p><p>There were also many collaborations among the lecturers. For example, the work for Braun was a joint project of product and communication design (Hans Gugelot and Otl Aicher).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*ggBjrWwZgPiyuuJaAUYAyQ.png" /><figcaption><em>‘Ulm-Braun-Rams-Apple’ — Tempting in its brevity [Source: </em><a href="http://gizmodo.com/343641/1960s-braun-products-hold-the-secrets-to-apples-future"><em>gizmodo.com</em></a><em>]</em></figcaption></figure><p>There is a new link, which is tempting in its brevity, but also falsifying. Today we are happy about the contribution of design to the economic success of Apple. It is known that Jonathan Ive and Steve Jobs appreciated the work of Dieter Rams. Dieter Rams is considered “Mr. Braun.” And Braun design is unthinkable without the impulse of HfG. So a new stereotype is everywhere: “Ulm-Braun-Rams-Apple.”</p><p>The image of “Ulm” is reduced to this notion, which is too superficial. Ulm is much more. It represents an attitude, an approach that reaches far beyond the formal aesthetic of the surface. It reaches out into society.” [5]</p><p><strong>POPULAR HISTORY</strong></p><p>I call it popular history because this is what google throws at you when you search for ‘History of UX’. A lot can be found about the history of User Experience on the internet and almost all of them, follow the similar narrative, so I am not going to write about it here (now).</p><p><strong>Taylor-Toyota-Dreyfuss-PARC-Don Norman-Apple</strong></p><p>Add a little bit of Ancient Greece, da Vinci and Disney to the mix. The oversimplification and complete neglect of the Design Movements, especially Ulm, makes me think twice about things that I learn from the internet. But let me not rant and genuinely appreciate the people who wrote these blogs so that there is something available for curious people to springboard from.</p><p><a href="https://medium.com/@marcintreder/the-history-of-user-experience-design-5d87d1f81f5a">The History of User Experience Design</a> by Marcin Treder.</p><p>Here is another <a href="https://www.fastcodesign.com/3043024/a-brief-history-of-user-experience-design">well written article</a> by Ali Rushdan Tariq who very aptly also adds Disney to the timeline. I would highly recommend reading this one too.</p><p>Happy reading to you.</p><p><strong>REFERENCE:</strong></p><p>[1] Gardner’s Art through the Ages: The Western Perspective by Fred S. Kleiner]</p><p>[2] <a href="https://monoskop.org/Ulm_School_of_Design">https://monoskop.org/Ulm_School_of_Design</a>, Retrieved on 12 May 2016.</p><p>[3] <a href="https://en.wikipedia.org/wiki/Ulm_School_of_Design">https://en.wikipedia.org/wiki/Ulm_School_of_Design</a>, Retrieved on 12 May 2016.</p><p>[4] Maldonado, Tomás. “New developments in the training industry in product design”, in: “ulm”, 2 October 1958, p. 31</p><p>[5] <a href="http://www.printmag.com/design-education/the-genius-that-was-ulm/">http://www.printmag.com/design-education/the-genius-that-was-ulm/</a>, Retrieved on 12 May 2016.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8e8c34a6764" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>