<?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 Ajay Shrivastava on Medium]]></title>
        <description><![CDATA[Stories by Ajay Shrivastava on Medium]]></description>
        <link>https://medium.com/@ajay.shrivastava?source=rss-78c0779d2edd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mon_vjRBUn3qqq_mQ5e2XQ.png</url>
            <title>Stories by Ajay Shrivastava on Medium</title>
            <link>https://medium.com/@ajay.shrivastava?source=rss-78c0779d2edd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:25:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ajay.shrivastava/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[Victimhood in organizations: Kills morale, vitiates culture!]]></title>
            <link>https://medium.com/@ajay.shrivastava/victimhood-in-organizations-kills-morale-vitiates-culture-4eb1c39c7789?source=rss-78c0779d2edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4eb1c39c7789</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[victims]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <dc:creator><![CDATA[Ajay Shrivastava]]></dc:creator>
            <pubDate>Thu, 16 Nov 2023 19:17:21 GMT</pubDate>
            <atom:updated>2023-11-16T19:17:21.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0rYLAd6dajlwTpia4QOtRw.jpeg" /></figure><p>Employees and members in all organizations, usually go into the negative spirals of negativity. They will talk about the pathetic state of affairs in the company, or their good work is not recognized, or they are not learning anything etc. These are symptoms of the Victimhood which must be identified and remedied to avoid widespread impact.</p><h3>Victimhood:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pW_RlRXqWtTwl8ms" /></figure><blockquote><strong>Victimhood </strong>is a condition in which one feels that he/she is a victim of the circumstances. He/she is entitled to better conditions and treatment. But does not feel any ownership to make efforts to improve the situation himself.</blockquote><h3>Victimhood is addictive and destructive:</h3><p>The sympathy-gaining and self pity releases hormones gaining which become addictive very fast. Over time, this impacts the quality of victim’s career and personal relationships.</p><h3>Traits of Victimhood:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/0*8sz_tGmISEHJf7jY" /></figure><p>In their minds, the universe is against them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p3Sn8afjXIAT_Zav" /></figure><h3>Double whammy for struggling companies:</h3><p>A company going through tough times is a favourable condition for Victimhood infection careers. They go on an overdrive in spreading the disease to other employees. This is a double whammy for the company, because when the company needs complete focus on goals, the Victimhood digresses focus and slows progress. Thereby putting the company in a downward vicious cycle.</p><h3>Victimhood Impact:</h3><h3>1. Impact on Employees:</h3><ul><li><strong>Victimhood employees start to believe their sad narrative and feel entitled. </strong>The demotivated employees feel entitled to better benefits but take no proactive action to improve the situation. They feel all the problems are from external reasons, which are not under their control. The feeling gets stronger over time making it a firm belief.</li></ul><blockquote>Don’t believe everything you think. Your thinking is the beginning and end of suffering. ~ Joseph Nguyen</blockquote><ul><li><strong>Victim-hood employees are easily maneuvered by political folks. </strong>They prey on the fragile emotional state of victim-hood employees and use them to their own advantage. E.g. The political parties first make communities feel like victims. Then they prey on Victim-hood employee’s insecurities by inciting them against their opposition political parties.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wuW_sVUTq5Y1lZgQ" /></figure><h3>2. Impact on Company:</h3><ul><li><strong>Company loses its focus and killer instinct. </strong>Management spends time pacifying folks rather than engaging in progressive problem solving. More attention feeds more complaints and more time and energy is wasted.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/0*udV7Qn3MpEz6pngK" /></figure><ul><li><strong>Lose-Lose situation for both employees and company. </strong>Root cause of issues doesn’t improve by whining. Only animosity and distrust increases among parties. So, both parties bear all the bad side effects and losses, for nothing in return!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/0*G9OXLPfGzsGgj-hq" /></figure><h3>Basic principles to solve Victimhood:</h3><h3>1. There are no problems, only situations.</h3><p>Situations can be handled well, if approached honestly and with the right attitude.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E9V2st3dtEJKZvKi" /></figure><h3>2. You become what you practice.</h3><p>So by practicing Victimhood, one will become a habitual victim. And after some time, one loses the ability to overcome situations altogether.</p><blockquote>Hardship isn’t the same thing as Victimhood. Hardship is unavoidable. Victimhood is a choice!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/0*fyPBVcg-GZu9n_1-" /></figure><h3>3. Everyone is a Leader. Let’s talk Solutions.</h3><p>When leaders face problems, they instinctively start looking out for solutions, rather than indulging in self pity. The same leadership traits need to be inculcated in each and every employee from top to bottom.</p><blockquote>“If you have time to whine then you have time to find a solution.” — Dee Dee Artner</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*1ueSAjAydNem_uNa" /></figure><p>Every employee (even a fresher) is a leader of his/her assigned area. So the organisation hierarchy is a hierarchy of leaders from top to bottom. So all discussions are leader to leader discussions. Where both leaders are working to find solutions together.</p><h3>Solution to Victimhood and its implementation:</h3><h3><strong>1. Listen and understand the groups and help them realise their Victimhood.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l8G-CrQo2lwCFnOS" /></figure><p>Hear out and understand the Victimhood employee’s point of view. They should know that you have understood the situation well. Then it will be easy to help them understand the difference between a Victims approach vs a Solvers approach. Illustrate the point that the problems grow bigger in mind by overthinking and whining about it. And when start working on solution, the problem minimises in size and vanishes over time. You need to be honest and transparent in your interactions in this step to build trust and rapport to being with.</p><h3>2. Prioritise and Solve items along with the group.</h3><p>Victimhood folks usually think inside the box of the current state of things. They need to realise that the practical world is not as ideal as they are expecting. In addition, the focus should be to get some quick wins, as it helps build positivity and trust in employees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gs4GFcYAIOeTBJdu" /></figure><p>E.g. If complain is non exciting work, then discuss with them allocating say 20% on new innovative pilots, which should be given good visibility across org too.</p><h3>3. Appreciate both “identifying” and “solving” issues.</h3><p>A healthy culture of <strong><em>early identification</em></strong> and <strong><em>quick resolution</em></strong> of Victimhood needs to be cultivated by proper rewards and recognitions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1sPN28Q3_AM8YF0Y" /></figure><h3>4. Isolate and let go of the permanent sources of Victimhood negativity.</h3><p>Habitual whiners in Victimhood need to be cast away so that the organisation regains its health asap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/0*xeMR4dPjkqsgXvPf" /></figure><h3>5. Managers to ensure regular 1:1 with co-workers and reporters.</h3><p>Regular 1:1s helps sustain the focus and detect any victimhood symptoms in employees sooner. It helps nip issues in bud!</p><blockquote>Employees who have regular 1:1 meetings with their managers are 3x more likely to be engaged at work.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/0*6UGWvObg40G_m9fL" /></figure><h3>6. HR team to ensure Victimhood control across the company.</h3><p>HR should plan regular employee connects to have a sense of the pulse on ground. Early detection will lead to nipping the problem in bud itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zcYaB9qf661hz713" /></figure><p>Overall, <strong>Victimhood is the biggest enemy of the much needed “winning culture” in the company</strong>. Keep an eye on it always to maintain happier employees and a healthy growing company.</p><p><strong>Be a </strong><a href="https://www.linkedin.com/pulse/why-cross-functional-team-fails-while-solver-team-ajay-shrivastava/"><strong>Solver</strong></a><strong>. Don’t be a Victim!! </strong><em>#OnwardsAndUpwards</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4eb1c39c7789" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Next orbit of business communication — using AI and Analytics]]></title>
            <link>https://medium.com/@ajay.shrivastava/next-orbit-of-business-communication-using-ai-and-analytics-2132279b42cd?source=rss-78c0779d2edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/2132279b42cd</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Ajay Shrivastava]]></dc:creator>
            <pubDate>Fri, 14 Jul 2017 11:32:27 GMT</pubDate>
            <atom:updated>2017-07-14T11:32:27.936Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJUaIcjWCnS2MNXzXpGncw.jpeg" /></figure><p>Communication has the make or break potential for businesses. Any deviation in communication effectiveness or effort involved has impact on the business performance itself. Let me take you through the past, present and future of the business communications and how it can take your business to next level.</p><h3>Communication is lifeline for all businesses</h3><p>Communication is the lifeline of all kinds of businesses, be it B2C, B2B etc. Following diagram shows the touch points where a company normally interacts with its customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Q6-tzbYpFmYUe6HG.png" /></figure><h3>Previous Orbit — In-House Telephony and Call Centre setup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*uG8WXuUj3NVpn24g.jpg" /></figure><p>In this stage, communication happened on phone by an in-house call centre setup. It needed huge cost in setting up and recurring operating cost. This also comprised building IT/technical capability to run telephony for call centre, irrespective of the business the company is doing. Day to day dealing with idiosyncrasies of different telecom providers (for redundancy), issues and down times etc proved very painful!</p><h3>Current Orbit — Cloud Telephony</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PgaxMoV98k0PsUJE.jpg" /></figure><p>A decade ago, the setup got hosted in cloud and a subscription based SaaS model emerged. This removed the hassles out of business’s life. Knowlarity pioneered the idea in PSTN markets like India and over a period of time various other companies also followed the suit. Today, almost a decade later, this space has become more of less commoditised. Time is ripe for a disruption in communication again!</p><h3>Next Orbit — AI &amp; Analytics in Communications</h3><p>Artificial Intelligence is making the unthinkable possible in communications and data crunching. AI standing on your behalf, to talk personally to your customers and respond to their queries. AI and Analytics tracking your systems 24x7 and alerting immediately when anything anomalous happens. Thus keeping the business on track always.</p><p>This will reduce the workforce and training required for routine and repeated work. Machines don’t get tired and repeat same performance 24 hrs, without mistakes which plague manual processes. Humans would be second rung of escalation when the computer determines that specialised task needs to be done.</p><h3>Magical scenarios possible via AI &amp; Analytics -</h3><ul><li><strong><em>Know what your customers/agents are “talking” about you </em></strong><em>(using Automated Speech Recognition — ASR)</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PNsktbEL8vvZymrE.jpg" /></figure><p>Millions of call recordings in call centres are waste, as no analysis in possible without listening to them. Sampling and listening is too sub-optimal and error prone to be useful. What if computer can listen to ALL recordings and give you most frequent business keywords and also tag sentiments in calls? And if you could also search recordings based on keywords and sentiments? That’s what is possible now!</p><ul><li><strong><em>Search words within voice call recordings </em></strong><em>by text or sentiments.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/0*ZBOlk2UoW4wEW8cF.jpg" /></figure><p>Imagine you can say “show me all recordings in which someone said unhappy” or “show me all recordings with negative sentiment”. Then in result set, you click and go directly to spot in recording where “unhappy” was said. That’s possible now!</p><ul><li><strong><em>Make “personalised contextual automated” calls</em></strong><em> (using Text to Speech — TTS)</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QWdFKjaT90SH34j6.jpg" /></figure><p>Imagine Amitabh Bachchan calls me and says “Hello Ajay, your daughter Aditi is 3 years old and should be vaccinated for pulse polio tomorrow, at the Pioneer Park near your house. Make sure to get her vaccinated”. This cuts through the clutter of generic promotional calls!</p><p>Everything personalised and contextual using the information from databases (say municipal database in example above) and spoken using TTS. That’s possible now!</p><ul><li><strong><em>Have “Voice based IVRs” where computer talks/listens to customers </em></strong><em>(using TTS + ASR)</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wqqvkW4toKdf8TMD.jpg" /></figure><p>To type the IVR options on phone, one has to take off phone from his ears, place in front of his eyes, then type and then quickly put it back on ear to hear next IVR response. Pretty irritating experience!</p><p>Imagine, if you could just speak your choice to proceed and there is no need to move your phone from your ears. That is possible now!</p><ul><li><strong><em>Have “Real time charts and alerts” even for huge/streaming data </em></strong><em>(using Big Data — Analytics)</em></li></ul><p>Imagine, if you are a business owner and you are able to see in “Real Time” live what your customers are talking (say a word cloud dashboard as seen below)? How is your business doing as per your previous records and relative to competition? Get alerts for any deviations from the normal in that very minute?</p><p>Huge terabytes of data crunching at the speed of light. All that is possible now!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/0*Ja5j6QXGHKnyo55h.jpg" /></figure><ul><li><strong><em>“Command the computer in English” to do above business tasks </em></strong><em>(using Natural Language Processing — NLP)</em></li></ul><p>Imagine if you could command your computer in English (verbal and written) to do business tasks like generate reports, build charts, set alerts etc, just as you could talk to a human secretary. Many of you would have experienced services like Amazon Alexa, Apple Siri, Google Assistant etc. Similar NLP services will be your business secretary soon. Yes that’s possible now!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Zg-ejnS1wck2AZEd.jpg" /></figure><p>Overall exciting times ahead, as B2C communication would never be same again in coming months. Stay tuned to the future..</p><p>In case the above future excites you, do reach me @ajayshr on twitter or ajay.shrivastava@knowlarity.com</p><p>Co-Authored with <a href="https://medium.com/u/d0feca626cb">Ambarish Gupta</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2132279b42cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Next orbit of business communication — using AI and Analytics]]></title>
            <link>https://medium.com/@ajay.shrivastava/next-orbit-of-business-communication-using-ai-and-analytics-19a98dd791ec?source=rss-78c0779d2edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/19a98dd791ec</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Ajay Shrivastava]]></dc:creator>
            <pubDate>Thu, 13 Jul 2017 05:30:20 GMT</pubDate>
            <atom:updated>2017-07-13T13:26:58.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJUaIcjWCnS2MNXzXpGncw.jpeg" /></figure><p>Communication has the make or break potential for businesses. Any deviation in communication effectiveness or effort involved has impact on the business performance itself. Let me take you through the past, present and future of the business communications and how it can take your business to next level.</p><h3>Communication is lifeline for all businesses</h3><p>Communication is the lifeline of all kinds of businesses, be it B2C, B2B etc. Following diagram shows the touch points where a company normally interacts with its customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Q6-tzbYpFmYUe6HG.png" /></figure><h3>Previous Orbit — In-House Telephony and Call Centre setup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*uG8WXuUj3NVpn24g.jpg" /></figure><p>In this stage, communication happened on phone by an in-house call centre setup. It needed huge cost in setting up and recurring operating cost. This also comprised building IT/technical capability to run telephony for call centre, irrespective of the business the company is doing. Day to day dealing with idiosyncrasies of different telecom providers (for redundancy), issues and down times etc proved very painful!</p><h3>Current Orbit — Cloud Telephony</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PgaxMoV98k0PsUJE.jpg" /></figure><p>A decade ago, the setup got hosted in cloud and a subscription based SaaS model emerged. This removed the hassles out of business’s life. Knowlarity pioneered the idea in PSTN markets like India and over a period of time various other companies also followed the suit. Today, almost a decade later, this space has become more of less commoditised. Time is ripe for a disruption in communication again!</p><h3>Next Orbit — AI &amp; Analytics in Communications</h3><p>Artificial Intelligence is making the unthinkable possible in communications and data crunching. AI standing on your behalf, to talk personally to your customers and respond to their queries. AI and Analytics tracking your systems 24x7 and alerting immediately when anything anomalous happens. Thus keeping the business on track always.</p><p>This will reduce the workforce and training required for routine and repeated work. Machines don’t get tired and repeat same performance 24 hrs, without mistakes which plague manual processes. Humans would be second rung of escalation when the computer determines that specialised task needs to be done.</p><h3>Magical scenarios possible via AI &amp; Analytics -</h3><ul><li><strong><em>Know what your customers/agents are “talking” about you </em></strong><em>(using Automated Speech Recognition — ASR)</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PNsktbEL8vvZymrE.jpg" /></figure><p>Millions of call recordings in call centres are waste, as no analysis in possible without listening to them. Sampling and listening is too sub-optimal and error prone to be useful. What if computer can listen to ALL recordings and give you most frequent business keywords and also tag sentiments in calls? And if you could also search recordings based on keywords and sentiments? That’s what is possible now!</p><ul><li><strong><em>Search words within voice call recordings </em></strong><em>by text or sentiments.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/0*ZBOlk2UoW4wEW8cF.jpg" /></figure><p>Imagine you can say “show me all recordings in which someone said unhappy” or “show me all recordings with negative sentiment”. Then in result set, you click and go directly to spot in recording where “unhappy” was said. That’s possible now!</p><ul><li><strong><em>Make “personalised contextual automated” calls</em></strong><em> (using Text to Speech — TTS)</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QWdFKjaT90SH34j6.jpg" /></figure><p>Imagine Amitabh Bachchan calls me and says “Hello Ajay, your daughter Aditi is 3 years old and should be vaccinated for pulse polio tomorrow, at the Pioneer Park near your house. Make sure to get her vaccinated”. This cuts through the clutter of generic promotional calls!</p><p>Everything personalised and contextual using the information from databases (say municipal database in example above) and spoken using TTS. That’s possible now!</p><ul><li><strong><em>Have “Voice based IVRs” where computer talks/listens to customers </em></strong><em>(using TTS + ASR)</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wqqvkW4toKdf8TMD.jpg" /></figure><p>To type the IVR options on phone, one has to take off phone from his ears, place in front of his eyes, then type and then quickly put it back on ear to hear next IVR response. Pretty irritating experience!</p><p>Imagine, if you could just speak your choice to proceed and there is no need to move your phone from your ears. That is possible now!</p><ul><li><strong><em>Have “Real time charts and alerts” even for huge/streaming data </em></strong><em>(using Big Data — Analytics)</em></li></ul><p>Imagine, if you are a business owner and you are able to see in “Real Time” live what your customers are talking (say a word cloud dashboard as seen below)? How is your business doing as per your previous records and relative to competition? Get alerts for any deviations from the normal in that very minute?</p><p>Huge terabytes of data crunching at the speed of light. All that is possible now!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/0*Ja5j6QXGHKnyo55h.jpg" /></figure><ul><li><strong><em>“Command the computer in English” to do above business tasks </em></strong><em>(using Natural Language Processing — NLP)</em></li></ul><p>Imagine if you could command your computer in English (verbal and written) to do business tasks like generate reports, build charts, set alerts etc, just as you could talk to a human secretary. Many of you would have experienced services like Amazon Alexa, Apple Siri, Google Assistant etc. Similar NLP services will be your business secretary soon. Yes that’s possible now!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Zg-ejnS1wck2AZEd.jpg" /></figure><p>Overall exciting times ahead, as B2C communication would never be same again in coming months. Stay tuned to the future..</p><p>Co-Authored with <a href="https://medium.com/u/d0feca626cb">Ambarish Gupta</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19a98dd791ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Achieving Hyper Agile & Well Oiled Execution with Solver Teams]]></title>
            <link>https://medium.com/knowlarity-engineering/achieving-hyper-agile-well-oiled-execution-with-solver-teams-d33c5b68344?source=rss-78c0779d2edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d33c5b68344</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Ajay Shrivastava]]></dc:creator>
            <pubDate>Thu, 02 Mar 2017 07:30:03 GMT</pubDate>
            <atom:updated>2017-03-02T07:32:43.805Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*G5ZRCeU67s6gWKT617TDRA.jpeg" /></figure><p>Couple of years ago, at a well known startup valued at nearly half a billion dollars, we built a new model of collaboration in software development that we called the “Solver Teams” approach.</p><p>Over the year we shipped dozens of products and hundreds of features using this methodology. It’s a powerful execution mechanism, that churns out multiple features every week at high speeds, while fostering camaraderie between business, product, design and technology teams.</p><p>The model has helped us scale while building dozens of products, adding hundreds of features, getting tens of millions of daily hits, and growing to thousands of employees rapidly.</p><p>Before we go into what the approach is, let’s look at the common challenges faced by the traditional software development model.</p><h3>Prevalent software development model:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*2s1DytZia4Pj0-yA." /></figure><p>In the prevalent software development model followed by most companies, the onus is on the individuals in upstream teams, to prepare a <em>frozen and locked contract document,</em> which will be the foundation for the plan and the work happening in downstream stages. Any changes to the contract later impacts the plan of all stages downstream, so it is vehemently resisted irrespective of the merits in proposed changes .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/0*fVKgo8EBaKzMauqs." /></figure><p><strong>The Problems with the Prevalent model:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*0_F_jDJGGbgWcd9j." /></figure><ul><li><strong>No team spirit. Your loss is my gain. Blame game:</strong> Any change to the contract can be perceived as incompetence on the part of the person who created it earlier. This gives an opportunity to downstream people to justify delays, and upstream people to justify why their goals were not met.</li><li><strong>Defensive Organization:</strong> The euphoria of shipping features is replaced by the fear of making any mistakes and being blamed for them.</li><li><strong>Analysis paralysis instead of experimentation:</strong> An inordinately long time spent at each stage. An experiment that could have been carried out in a few days would be theoretically debated over presentations for weeks.</li><li><strong>Optimizing subsystem, not the whole. Service provider mentality:</strong> “I did what you asked.” No one bothers whether the goal will be met, as they have a “written document” to blame someone else for any fiasco e.g. even if PRD (Product Requirements Document) has a visible issue, the designer would still create the design according to it “on time” and “in good quality” on which he will be measured on.</li><li><strong>No empathy for each other’s work:</strong> Concerned parties communicate via emails and documents so there is no understanding and empathy of each other’s work complexities. Engineers consider themselves special, business guys think they are being unnecessarily delayed by product and engineers, product managers feel they are unnecessarily brick-batted from both sides.</li><li><strong>Disengaged workforce. Not self-driven:</strong> Omnipresent negativity disengages the workforce. It hampers productivity and the management’s bandwidth is spent in driving the employees and getting work done, rather than adding value.</li><li><strong>Agile methodologies increase frequency of above issues:</strong> Practically everyone runs agile like mini waterfall cycles. As the frequency of releases increase, so does the mutual hate, release after release.</li><li><strong>Peers become the enemy, not the competition:</strong> Diplomatic point scoring becomes the most needed skill to survive in the game. In interviews many candidates flaunt their ‘diplomatic skills’, by saying that business and product persons should never be allowed to meet the engineers and that he is good at handling and keeping them in control and at bay.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ZeXL8kG5I9SMSmQd." /></figure><ul><li><strong>Company loses its killer instinct. Gets disrupted:</strong> Fewer innovations develop at companies that have become large, even when they hire the best talent. They were disruptors at one point when they were small and relatively deprived. They fall in the diplomacy trap and get disrupted by another focused startup and the cycle continues.</li></ul><h3>Solver Teams — Sail and Sink Together:</h3><p>The core idea of solver teams is to put all the parties in the same boat, with a mandate to sail and sink together. They all have a say and own all decisions and execution together. They cross all milestones and stages together as a team. Contrast this with the older model, where an individual alone owned the stage and everyone else was his client finding faults in his work.</p><p>It’s called a “Solver Team” not “Feature Team” because the goal is to solve the problem and not just build a feature. So it’s quite possible that a problem can be solved through a process change rather than necessarily building a feature for it. That’s why the business person is also a part of the Solver Team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*EU1ZPEUaf_j6bBwt." /></figure><ul><li><strong>Solver Team (ST) = Business + Product + Design + Tech members.</strong> Self-sufficient group of experts from different functions who work together on a specific problem end-to-end.</li><li><strong>ST together is accountable from inception to release to impact</strong> to iterations and so on. They sail and sink together. If a project fails to make impact, everyone fails.</li><li><strong>ST together moves through stages one after the other</strong> i.e. from Business Requirements Document (BRD) -&gt; Product Requirements Document (PRD) -&gt; Design Specifications -&gt; Technology execution stages.</li><li><strong>Functional experts in ST own and lead their respective stages.</strong> That person is accountable for completeness and accuracy of the deliverable at that stage. As the entire ST is in that stage together, everyone has an equal opportunity to discuss, suggest or change the course of action. Team members “Disagree and Commit” when needed.</li><li><strong>ST forms a chat group</strong> on WhatsApp/Slack in the beginning to be in continual sync.</li></ul><h3>Advantages of the Solver Teams Approach:</h3><ul><li><strong>Deep understanding of end-to-end flows</strong> in business, product, design and engineering persons.</li><li><strong>Very high speed of execution</strong> and iterations as all decisions are taken without bureaucracy and email chains.</li><li><strong>Strong sense of ownership </strong>as all decisions are taken by them together.</li><li><strong>Focused alignment towards goal. Ready to change plan. </strong>ST ready to course correct and change plan if that helps to solve the problem better.</li><li><strong>Positive energy and ‘Get Shit Done’ attitude</strong> to make the decisions successful.</li><li><strong>Deeper understanding and empathy for each other’s</strong> work complexity.</li><li><strong>Great opportunity to push thinking horizons </strong>far and wide. Logical ST grouping along with physical reporting in their respective functional organizations makes the person well exposed to depth and width of expertise. Members become all-rounders and are better equipped to run a business end-to-end.</li></ul><p>As with any new approach we also had our share of challenges. It needs continuous effort and reiteration to make sure the model doesn’t regress into the older prevalent software development model. Since every new person who joins the team would be familiar with only the older model, without sufficient training or orientation, they would they would follow that by default.</p><p>Finally, I would like to point out that the Solver Teams model does not necessarily have to be restricted to software development. It can be applied whenever more than one team needs to work together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d33c5b68344" width="1" height="1" alt=""><hr><p><a href="https://medium.com/knowlarity-engineering/achieving-hyper-agile-well-oiled-execution-with-solver-teams-d33c5b68344">Achieving Hyper Agile &amp; Well Oiled Execution with Solver Teams</a> was originally published in <a href="https://medium.com/knowlarity-engineering">Knowlarity Engineering Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minimum Viable Technology (MVT) — Move Fast & Keep Shipping]]></title>
            <link>https://medium.com/knowlarity-engineering/minimum-viable-technology-mvt-move-fast-keep-shipping-9e3d9ad89a1d?source=rss-78c0779d2edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e3d9ad89a1d</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Ajay Shrivastava]]></dc:creator>
            <pubDate>Thu, 02 Mar 2017 06:24:49 GMT</pubDate>
            <atom:updated>2017-03-02T07:08:37.717Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*lAldD9W-iolAQYUKxxlDIA.jpeg" /></figure><p>Technology teams can be the biggest asset or worst bottleneck for a growing company. You can see the ‘hidden frustration” in Bezos words below.</p><blockquote>I have asked engineers to be fast acting cowboys, instead of calm clear-headed computer scientists</blockquote><blockquote>Jeff Bezos, Founder &amp; CEO, Amazon</blockquote><p>Future Paranoia — Rampant Problem in Industry: When the task is to build a bike, the product and technology teams would plan for a product, which can later run on a motor, seat four people, sail in the sea and even fly in the future. This hypothetical building of the castle in the air diverts focus from the real problem. This is what Bezos is asking us to refrain from, as it wastes resources and agonizingly delays the time to market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*rQnccf1Z7ImgqKMH.jpg" /></figure><p>Being defensive, the Product/Technology teams usually <em>build a cannon for killing a bird</em>.</p><p><strong>Minimum Viable Product (MVP) philosophy evolved</strong>, to avoid this “unnecessarily over-thinking and over-preparation” problem which plagued product companies. It encouraged building the minimum required at a certain point of time and then iterating and improving it based on user feedback. MVP approach enables much needed <em>fast experimentation</em>, <em>fail fast</em> and <em>invest where needed</em> strategy.</p><p>No such philosophy evolved for Technology. Therefore, the decades-old <em>defensive</em> and <em>paranoid philosophy</em> still prevails (which was much needed during older 1–2-year long waterfall releases). This becomes a competitive disadvantage for startups usually fighting for survival or growing fast.</p><p>The fundamental problem is that most engineers blindly try to copy strategies of large companies. Corporations and startups differ widely on their needs of scale, brand, speed, an impact of a feature, loss by a bug, etc. Startups enjoy more freedom to make mistakes and that they should make the most of it.</p><p><em>Strategies used in big companies are often irrelevant and even detrimental</em> to a small growing company’s interests.</p><p><strong>Minimum Viable Technology:</strong> The solution to the above problems is to <em>Build the Minimum Technology</em>, that makes the product and its foreseeable further iterations <em>Viable</em>. Make it live a.s.a.p. and then iterate and improve it based on feedback from real users. Every company is in a different stage of evolution. Something that is MVT for a big company, can be over-engineering for startups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*yOYJVfcJr28L5iNU.jpg" /></figure><p>If the task is to kill a bird, we should build a catapult/small-gun, to begin with. If that becomes successful and there is a need to kill more or bigger animals, then bigger-guns/cannons should be built as required.</p><blockquote>There is nothing so useless as doing efficiently that which should not be done at all.</blockquote><blockquote>Peter Drucker</blockquote><p>Startups experiment a lot and only a few of them sustain the test of time. As per 80–20 rule, only those 20% successful ones should get deeper technology investments.</p><p><strong>Principles of Minimum Viable Technology (MVT):</strong></p><ul><li><strong>MVP + MVT + Agile is the complete package.</strong></li></ul><p><em>MVP is for product scope minimisation. MVT is for technology scope minimisation. Agile is for iterative technology execution.</em></p><ul><li><strong>Most decisions can be reversed or fixed easily. </strong>Choose wisely by bucketing the decision accurately into reversible or non-reversible. And judiciously decide how much to prepare for that case. (Read Jeff Bezos’ <a href="http://www.businessinsider.in/Jeff-Bezos-There-are-two-types-of-decisions-to-make-and-dont-confuse-them/articleshow/51706758.cms">two types of decisions</a>).</li></ul><blockquote>It’s important to internalise how irreversible, fatal, or non-fatal a decision may be. Very few can’t be undone. — Dave Girouard</blockquote><ul><li><strong>Build MVT — Fast &amp; cost effective</strong>. Build the Minimum Technology that makes the product and their foreseeable iterations <em>Viable</em>. Prefer operational familiarity while choosing technology. Don’t fall for the latest buzzword.</li><li><strong>Refactoring is part of success plan:</strong> Getting to refactor is a sign of success. Only components which are used and evolve fast; become complex over time and need to be refactored. Be ready to re-factor or throw away and rebuild where justified.</li></ul><blockquote>The best code you can write now is the code you will discard in a couple of years time.</blockquote><blockquote>Martin Fowler</blockquote><ul><li><strong>Think long term, act short term:</strong> It’s a fine line between under-engineering and MVT approach. Don’t rush into execution without sufficient analysis, otherwise, it will lead to more resource waste later. Deliberate choices must be there to cut scope. The rule of thumb is to discuss the ideal solution on board and then decide what to take out of scope to make it MVT.</li><li><strong>Speed and Quality must go hand in hand:</strong> Never justify the bad quality of your work by using the speed of execution as an excuse.</li></ul><p><em>MVT is for scope reduction, not for quality reduction.</em></p><ul><li><strong>MVP/MVT is applicable for every iteration/release:</strong> People relate MVP to the <em>First release of the product only</em>. In fact, it applies to every stage. MVP/MVT needs to be chosen from the remaining next tasks at every stage. At no stage, it is ok to waste time and resources.</li></ul><p><strong>Foundations for MVT execution:</strong></p><ul><li><strong>Deep understanding, conviction and confidence are needed for MVT</strong>. Both MVP and MVT approach are about taking bold calls like — “Out of these tasks, only this much is enough to win this stage of game”. While the defensive traditional approach is like — “we can’t win or sustain if we do not do most of the known tasks”.</li><li><strong>Alignment across departments is must for MVT execution.</strong> MVT reduces time to market in 80% of cases, by focusing on the core of what is needed. As per 80–20 rule, only 20% will need re-factoring and re-architecture later. Due to mistrust and friction between departments, they keep blaming each other for mistakes. This leads to engineering (and others) being defensive and therefore over prepare to avoid any mistakes. This is explained and solved in Solver Teams post. In ST approach, all parties are in hot sync and are aware of the trade offs taken while executing. So there is strong understanding and support for such efforts.</li></ul><p><strong>Move Fast. Keep Shipping!!</strong></p><p>* The term “Minimum Viable Technology — MVT” is coined by the author.</p><p>* The article is based on engineering execution done in a startup from scratch.</p><p>* This article has been republished by leading technology/startup media like Tech-In-Asia, Your-Story, Inc-42, I-Am-Wire etc.</p><p>Engage your mind, Inspire your Creativity &amp; Develop your <a href="https://www.knowlarity.com/careers/">career</a> with Knowlarity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e3d9ad89a1d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/knowlarity-engineering/minimum-viable-technology-mvt-move-fast-keep-shipping-9e3d9ad89a1d">Minimum Viable Technology (MVT) — Move Fast &amp; Keep Shipping</a> was originally published in <a href="https://medium.com/knowlarity-engineering">Knowlarity Engineering Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minimum Viable Technology (MVT) — Move Fast & Keep Shipping]]></title>
            <link>https://medium.com/@ajay.shrivastava/minimum-viable-technology-mvt-move-fast-keep-shipping-b1593153969e?source=rss-78c0779d2edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1593153969e</guid>
            <category><![CDATA[mvt]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ajay Shrivastava]]></dc:creator>
            <pubDate>Wed, 02 Nov 2016 17:54:21 GMT</pubDate>
            <atom:updated>2016-12-09T18:36:09.728Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*asWfYMXIfiwUIb1kDP2-GQ.png" /><figcaption>Credits: <a href="http://xkcd.com/974/">http://xkcd.com/974/</a> &amp; Vasundhara Mehra</figcaption></figure><p>Technology teams can be the <em>biggest asset</em> or <em>worst bottleneck</em> for a growing company based on the strategy taken by them. In name of future proofing engineering, the technology teams become a hurdle to company’s goals. You can see the ‘hidden frustration” in Bezos words below ..</p><blockquote>I have asked engineers to be fast acting cowboys, instead of calm clear-headed computer scientists — Jeff Bezos, Founder &amp; CEO, Amazon</blockquote><p><strong>Future Paranoia -Rampant Problem in Industry: </strong>When the task is to build a bike, the product and technology teams would plan for a product, which can later run on motor, seat four people, sail in sea and even fly in the future. This hypothetical building of castle in air, digresses the focus from the real problem to be fixed. This is what Bezos is suggesting to refrain from, as it wastes resources and agonizingly delays the time to market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r9amPLkKVAEu4gnz.jpg" /></figure><p>Being defensive, the Product/Technology teams usually <em>build a cannon for killing a bird</em>.</p><p><strong>Minimum Viable Product (MVP) philosophy evolved,</strong> to avoid this “unnecessarily over-thinking and over-preparation” problem which plagued products in all companies. It encouraged building the minimum required at a certain point of time and then iterating and improving it going forward. MVP approach enables much needed <em>fast experimentation</em>, <em>fail fast</em> and <em>invest where needed</em> strategy.</p><p><strong>No such philosophy evolved for Technology. </strong>Therefore, the decades old <em>defensive</em> and <em>paranoid philosophy</em> still prevails (which was much needed during older 1–2 year long waterfall releases). This becomes competitive disadvantage for startups usually fighting for survival or growing fast.</p><p>Fundamental problem is that the engineers blindly copy the large company’s strategies, considering them to be the standard. Corporate and startups differ widely on their needs of scale, brand, speed, impact of a feature, loss by a bug, etc. Startups enjoy more freedom to make mistakes and that they should exploit to their benefit.</p><p><em>Strategies used in big companies are more often irrelevant and even detrimental</em> to a small growing company’s interests.</p><p><strong>Minimum Viable Technology:</strong> The solution to above problems is to <em>Build</em> the <em>Minimum Technology,</em> that makes the product and its foreseeable further iterations <em>Viable</em>. Make it live a.s.a.p. and then iterate and improve it based on real usage learnings. Every company is in different stage of evolution. Something that is MVT for a big company, can be over-engineering for startups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SD-8d03NIzygZgt1.jpg" /></figure><p>If the task is to kill a bird, we should build a catapult/small-gun to begin with. If that becomes successful and there is a need to kill more or bigger animals, then bigger-guns/cannons should be built as required.</p><blockquote>There is nothing so useless as doing efficiently that which should not be done at all. ~ Peter Drucker</blockquote><p>Startups experiment a lot and only a few of them sustain the test of time. As per 80–20 rule, only those 20% successful ones should get deeper technology investments.</p><h3><strong>Principles of Minimum Viable Technology (MVT):</strong></h3><ul><li><strong>MVP + MVT + Agile is the complete package.</strong></li></ul><blockquote>MVP is for product scope minimisation. MVT is for technology scope minimisation. Agile is for iterative technology execution.</blockquote><ul><li><strong>Most decisions can be reversed or fixed easily. </strong>Choose wisely by bucketing the decision properly into reversible or non-reversible. And judiciously decide how much to prepare for that case. (Read Jeff Bezos’ <a href="http://www.businessinsider.in/Jeff-Bezos-There-are-two-types-of-decisions-to-make-and-dont-confuse-them/articleshow/51706758.cms">two types of decisions</a>).</li></ul><blockquote>It’s important to internalise how irreversible, fatal, or non-fatal a decision may be. Very few can’t be undone. — Dave Girouard</blockquote><ul><li><strong>Build MVT — Fast &amp; cost effective.</strong> Build the <em>Minimum Technology</em> that makes the product and their foreseeable iterations <em>Viable</em>. Prefer operational familiarity while choosing technology. Don’t fall for the latest buzzword (sure sign of inexperience).</li><li><strong>Refactoring is part of success plan:</strong> Getting to refactor is a sign of success. Only components which are used and evolve fast; become complex overtime and need to be refactored. Be ready to re-factor or throw away and rebuild where justified.</li></ul><blockquote>The best code you can write now is the code you will discard in a couple of years time. — Martin Fowler</blockquote><ul><li><strong>Think long term, act short term:</strong> It’s a fine line between under-engineering and MVT approach, that has to be tread properly. Don’t rush into execution without thinking completely, otherwise it will lead to more resource waste later. Thinking has to complete and deliberate choices must be there to cut scope. The rule of thumb, is discuss the ideal solution on board and then decide what to take out of scope to make it MVT.</li><li><strong>Speed and Quality must go hand in hand:</strong> Never justify the bad quality of your work by using the speed of execution as excuse.</li></ul><blockquote>MVT is for scope reduction, not for quality reduction.</blockquote><ul><li><strong>MVP/MVT is applicable for every iteration/release:</strong> People relate MVP to the <em>First release of product</em> only. In fact, it applies to every stage. MVP/MVT needs to be chosen from the remaining next tasks at every stage. At no stage, it is ok to waste time and resources.</li></ul><h3>Foundations for MVT execution:</h3><ul><li><strong>Deep understanding, conviction and confidence is needed for MVT.</strong> Both MVP and MVT approach is about taking bold calls like — “Out of these tasks, only this much is enough to win this stage of game”. While defensive traditional approach is like — “we can’t win or sustain if we do not do most of the known tasks”.</li><li><strong>Alignment across departments is must for MVT execution. </strong>MVT reduces time to market in 80% of cases, by focusing on the core of what is needed. As per 80–20 rule, only 20% will need re-factoring and re-architecture later. Due to mistrust and friction between departments, they keep looking for faults in others. This leads to engineering (and others) being defensive and therefore over prepare to avoid any mistakes. This is explained and solved in <a href="http://www.linkedin.com/pulse/solver-teams-oyo-hyper-agile-well-oiled-execution-ajay?trk=pulse_spock-articles">Solver Teams</a> post. In ST approach, all parties are in hot sync and are aware of trade offs taken while executing. So there is strong understanding and support for such efforts.</li></ul><p><strong>Move Fast. Keep Shipping!!</strong></p><p><em>* The term “Minimum Viable Technology — MVT” is coined by the author.</em></p><p><em>* The article is based on engineering execution done in a startup from scratch.</em></p><p>* <em>Article has been republished by leading technology/startup media like </em><a href="http://www.techinasia.com/talk/case-minimum-viable-technology"><em>Tech In Asia</em></a><em>, </em><a href="http://yourstory.com/2016/11/minimum-viable-technology-startup/"><em>YourStory</em></a><em>, </em><a href="http://www.iamwire.com/2016/11/minimum-viable-technology-mvt%E2%80%8A-%E2%80%8Amove-fast-keep-shipping/145000"><em>I Am Wire</em></a><em> etc..</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1593153969e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What brought you here, won’t take you there!]]></title>
            <link>https://medium.com/@ajay.shrivastava/what-brought-you-here-wont-take-you-there-3167c17e4256?source=rss-78c0779d2edd------2</link>
            <guid isPermaLink="false">https://medium.com/p/3167c17e4256</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[peter-drucker]]></category>
            <dc:creator><![CDATA[Ajay Shrivastava]]></dc:creator>
            <pubDate>Tue, 01 Nov 2016 19:34:06 GMT</pubDate>
            <atom:updated>2016-11-22T04:54:40.474Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*6P1t0zfwj71EHuJR5f4nuA.jpeg" /></figure><p>Very often successful organizations and individuals spiral down in their fortunes and careers. What goes wrong? They have proven record, total commitment, hard work … then?</p><p>The reason is “implicit complacency” and “implicit superiority complex” of being successful. “Implicit” because they don’t know and acknowledge that they are affected by it. They instinctively, repeat their once successful strategies, to face the newer challenges too. And this “implicit” know-it-all attitude, doesn’t allow the much needed “disruptive thinking” to lurk in the vicinity also.</p><blockquote>The greatest danger in times of turbulence is not the turbulence; it is to act with yesterday’s logic. ~Peter Drucker</blockquote><p>What brought you here, is a good recipe for others to reach where you are; but the same recipe won’t take you, where you want to go next. In today’s world, the continuous pursuit of improvement is not an option, but a necessity!</p><blockquote>The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn. ~Toffler</blockquote><p>Any major success is achieved by doing few or all things differently from the norm. This remains equally pertinent, even after being successful also i.e. do things differently from the norm, even when the norm is set by your own success itself!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FqKExmBqUsPlvXG&amp;url=http%3A%2F%2Fwww.slideshare.net%2FAjayShrivastava1%2Fchange-good-to-great%3Fref%3Dhttps%3A%2F%2Fwww.linkedin.com%2Fpost%2Fedit%2F5901336248571691008&amp;image=http%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fa-3-98d2443102932b0f5581a329b07a54ecf4e3506a-140607144207-phpapp02-thumbnail-4.jpg%3Fcb%3D1441380594&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/98973f7642a2ddb3ae6766015d6dc8ae/href">https://medium.com/media/98973f7642a2ddb3ae6766015d6dc8ae/href</a></iframe><p>Disrupt yourself. Make yourself uncomfortable. Look for opportunities to improve, evolve and diversify. Acknowledge merit of thoughts different from yours. Make big hairy audacious goals which most people would suspect or laugh at. Never be complacent, neither explicit nor implicit.</p><p>Remember, if you are not moving forward, you are going backwards.Play or be Played!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3167c17e4256" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>