<?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 Tabrez Alam on Medium]]></title>
        <description><![CDATA[Stories by Tabrez Alam on Medium]]></description>
        <link>https://medium.com/@alamtabrez?source=rss-62856cbbef84------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*0TCgZATUO-6iEOpE.</url>
            <title>Stories by Tabrez Alam on Medium</title>
            <link>https://medium.com/@alamtabrez?source=rss-62856cbbef84------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:16:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alamtabrez/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[Using AI to Draft Patents: A Practical Guide for Modern Inventors and Attorneys]]></title>
            <link>https://medium.com/@alamtabrez/using-ai-to-draft-patents-a-practical-guide-for-modern-inventors-and-attorneys-ec7ab86a653a?source=rss-62856cbbef84------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec7ab86a653a</guid>
            <category><![CDATA[intellectual-property]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[patents]]></category>
            <dc:creator><![CDATA[Tabrez Alam]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 09:38:22 GMT</pubDate>
            <atom:updated>2026-04-06T09:38:22.491Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What works, what doesn’t, and how the right platform makes the difference</strong></p><p>Patent drafting has historically been one of the most time-intensive and technically demanding tasks in the legal profession. A well-drafted nonprovisional patent application — covering claims, a detailed description, abstract, drawings, and background — can consume 40 to 80 hours of a skilled patent attorney’s time. For independent inventors and small companies, this translates into filing costs ranging from $8,000 to $15,000 per application, often before a single examiner has reviewed a word of it.</p><p>Artificial intelligence is beginning to change this equation. But the change is more nuanced than the headlines suggest. AI does not simply write patents for you. Used correctly, it is a powerful force-multiplier. Used carelessly, it can produce work that is not just wrong — but legally dangerous. The difference largely comes down to which tool you use and how it has been designed.</p><h3>The Problem With Most AI Patent Tools Today</h3><p>When attorneys and inventors first experiment with AI-assisted drafting, they typically reach for general-purpose tools — ChatGPT, Claude, or Gemini. These tools are extraordinarily capable at language. They are not, however, patent attorneys. They have no structural understanding of what a patent application requires, how claims interact with the specification, or what constitutes a fatal written description failure. They produce fluent, plausible text — and in patent law, “plausible” is a liability.</p><p>The second wave of AI patent tools — platforms like SolveIntelligence, Specifio, and PatSnap Eureka — improved on this by adding patent-specific context. They understand claim structure better, can search prior art, and produce more legally coherent language. But most still operate as sophisticated one-shot generators: you put a disclosure in, a draft comes out, and the attorney’s job is to fix what the AI got wrong.</p><p>This model has a structural flaw. The AI is generating content without truly understanding what it is drafting. It is guessing at the gaps in the disclosure rather than asking about them. That is where the real problem begins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P7F8EJBXr3KyCO7Xt8L2OA.jpeg" /><figcaption>Patent Drafting in the Age of AI</figcaption></figure><h3>A Different Approach: eety.ai and the Invention-First Model</h3><p><strong>eety.ai</strong> was built on a different philosophy: before any word of legal text is written, the system must genuinely understand the invention. This is not a cosmetic distinction — it is the architectural decision that separates it from every other tool in the market.</p><p>When an attorney or inventor uploads a disclosure to eety.ai, the platform does not immediately generate claims. Instead, it builds what it calls the <strong>15-Point Brain</strong> — a structured model of the invention that maps 15 distinct dimensions including the inventive concept, the technical problem being solved, the solution mechanism, novelty, non-obviousness, component relationships, claim hierarchy, and prior art differentiation. If any of these dimensions are unclear or underdisclosed, eety.ai asks. It runs an interview-style Q&amp;A to close gaps in understanding before a single claim is drafted.</p><p>This front-end comprehension phase is unglamorous, but it is the single most effective defence against hallucination. The system enforces a <strong>90% confidence gate</strong>: drafting is hard-locked until the invention model reaches sufficient completeness. If the AI does not understand the invention well enough, it cannot proceed. This one rule eliminates the root cause of most AI patent failures — incomplete understanding masquerading as complete disclosure.</p><h3>How eety.ai Manages Each Stage of the Drafting Pipeline</h3><p>eety.ai structures the entire drafting process as a <strong>10-phase pipeline</strong>, with attorney approval required at each transition. This is not how most AI tools work, and the difference matters enormously in practice.</p><p><strong>Phase 1–3: Upload, Analyse, and Build the Brain.</strong> The disclosure is uploaded — PDF, DOCX, images, or any combination. The platform merges multiple files, resolves conflicts, and constructs the 15-point invention model. The attorney reviews and approves this model before anything else happens.</p><p><strong>Phase 4: Style Intelligence.</strong> This is one of eety.ai’s most distinctive capabilities. The attorney uploads a reference patent — one they previously wrote, or one whose style they want to emulate. eety.ai reverse-engineers that patent’s writing DNA: the hedging style, claim structure, preferred transitional phrases, sentence rhythm, and paragraph format. Every subsequent draft is generated in that voice. The output sounds like the attorney wrote it, not like a language model did.</p><p><strong>Phase 5–6: Plan and Draft.</strong> Before writing the specification, eety.ai generates a paragraph-by-paragraph roadmap — a plan that shows exactly what each section will cover. The attorney approves this plan before a word of description is written. When the drafting executes, it follows the approved architecture. This two-step approach — plan then execute — is what keeps the detailed description logically consistent with the approved claims.</p><p><strong>Phase 7–8: AI-Generated Patent Drawings.</strong> eety.ai is one of the first platforms to generate USPTO-compliant patent drawings — block diagrams, flowcharts, system schematics — directly from the invention model and claims. The attorney can regenerate individual figures, request layout changes, or add new drawings through natural language conversation, without leaving the drafting workspace.</p><p><strong>Phase 9–10: Review and Export.</strong> An AI-powered compliance review checks that every claim element has antecedent basis in the description, that figure references are consistent, and that the document meets USPTO formatting requirements. A clean, fully formatted DOCX file is then exported — with embedded drawings, numbered paragraphs, proper claim hierarchy, and compliant section headers — ready for attorney final review and filing.</p><h3>The Hallucination Problem — Why eety.ai’s Architecture Matters</h3><p>AI hallucination in patent drafting is not a nuisance. It is a liability risk. General-purpose models will confidently draft claim elements that are not disclosed in the specification, cite prior art references that do not exist, or generate boilerplate that contradicts what the invention actually is.</p><p>eety.ai addresses this at the architectural level, not the prompt level. Because every draft section is derived from an approved, structured invention model — not generated from raw text in one pass — the system cannot invent facts that were never in the model. If a component was not described in the disclosure and not clarified in the interview phase, it is not in the model, and therefore not in the draft. The chain of custody from disclosure to draft is explicit and traceable.</p><p>Additionally, eety.ai logs every edit, redraft, AI call, and section change with a full timestamp and user attribution. Law firms have a complete audit trail from the original disclosure to the filed draft — which matters both for professional liability and for client billing transparency.</p><h3>Data Security: A Non-Negotiable for Law Firms</h3><p>Patent disclosures contain some of the most commercially sensitive information a client will ever share with their attorney. Every AI platform a firm considers must answer two questions: where does my data go, and is it used to train AI models?</p><p>eety.ai answers both directly. Each law firm receives a <strong>dedicated, isolated Google Cloud Storage bucket</strong> — no file is ever co-mingled with another firm’s data. Client invention disclosures, draft claims, and uploaded PDFs are <strong>never used to train any AI model</strong>, including Gemini, and this guarantee is contractual. All data is encrypted at rest with AES-256 and in transit with TLS 1.3. Every API call is JWT-authenticated and scoped to the specific tenant — cross-firm data access is architecturally impossible, not just policy-controlled.</p><p>For firms operating under professional responsibility rules on client confidentiality, this architecture is the difference between a tool that can be adopted and one that cannot.</p><h3>What Productivity Actually Looks Like</h3><p>Early adopters using eety.ai report reducing first-draft time from 40+ hours to under 4 hours for a complete non-provisional application, including drawings and detailed description. That is not a reduction in quality — it is a reallocation of attorney time from mechanical drafting to substantive review, prosecution strategy, and client value.</p><p>The junior associate who spent three days generating a specification is now free to work on office action responses. The partner who reviewed and rewrote 80% of an AI draft is now reviewing a draft that needs 20% of their attention. The client receives a better application, faster, at a lower cost.</p><h3>The Right Way to Think About AI in Patent Practice</h3><p>AI will not replace patent attorneys. It will restructure how their time is spent — but only if the tool is designed with that goal in mind. A one-shot generator shifts work from drafting to fixing. A genuine assistant, built on deep understanding of what patent drafting requires, shifts work from mechanical production to strategic judgment.</p><p>eety.ai was built by a founder who spent a decade as AVP of the world’s largest IP services company before spending a second decade in AI and machine learning. It is not a tech company that discovered patents. It is a patent platform that mastered AI. That inversion is why the design choices — the 15-point brain, the confidence gate, the style extraction, the phased pipeline — are the right ones. They were made by someone who lived the problem for twenty years before building the solution.</p><p><em>The best AI patent tool is not the one that generates the fastest draft. It is the one that ensures the draft is worth filing.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec7ab86a653a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three things that I learnt about leadership — Episode 1]]></title>
            <link>https://medium.com/@alamtabrez/three-things-that-i-learnt-about-leadership-episode-1-ddb2f4ee7ba6?source=rss-62856cbbef84------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddb2f4ee7ba6</guid>
            <category><![CDATA[first-job]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Tabrez Alam]]></dc:creator>
            <pubDate>Tue, 09 Jul 2019 06:52:00 GMT</pubDate>
            <atom:updated>2019-07-09T06:52:00.158Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*Us-kxnRJCW_XzqeNL8JiUg.jpeg" /></figure><h3>Three things that I learnt about leadership — Episode 1</h3><p>Three things that I learnt at my very first job and from the same person, which shaped the way I think of leadership.</p><p>Episode 1:</p><p>I was a fresher out of college, and after spending a very brief amount of time in training in the corporate headquarters, we were posted to the Delhi office.</p><p>It was one fine evening, when I reached office after a long day of meetings in the sultry Delhi weather. I was a big hungry so I grabbed a patty from a shop just outside our office, and sat on the pavement while eating. Our office building was on the main road, so where I was actually sitting was the edge of a footpath.</p><p>The chairman of the company (who used to sit in the corporate headquarters) was visiting Delhi and he came out of the building. I am not sure of the reason why he came out, but we saw each other. I remembered that all the trainees has a brief session with him in our orientation. This is the point from where the surprises started.</p><ul><li>He called me by my name and asked what was I doing. This was the first surprise, as the company was more than 5000 people strong and I was a new joiner. The chairman knowing my name was already a big thing for me.</li><li>As I was getting up, he asked me to keep sitting. He took off his coat, put it on his arms and came and sat with me (on the broken footpath) and asked for a share of the patty that I was having.</li></ul><p>He kept sitting with me for a while till I finished eating and then together we walked back to the office.</p><p>I learnt two things that day,</p><ul><li>Know who work ‘for’ you — This instantly builds a rapport. You may not know everything, but may be just the name is enough</li><li>Understand that people work ‘with’ you and not ‘for’ you — Make people feel equal. An organisation is a unit working together, with defined responsibilities for everyone and no person’s job is less or more critical that other.</li></ul><p>Each day I strive my best to ‘know’ each of the people who work ‘with’ me to build a team that works like a ‘trust based unit’.</p><p>Episode 2: How I learn to ‘trust’ employees and why it benefitted. (<a href="https://medium.com/@alamtabrez/three-things-that-i-learnt-about-leadership-episode-2-e47f71083bdf">read here</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddb2f4ee7ba6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three things that I learnt about Leadership — Episode 2]]></title>
            <link>https://medium.com/@alamtabrez/three-things-that-i-learnt-about-leadership-episode-2-e47f71083bdf?source=rss-62856cbbef84------2</link>
            <guid isPermaLink="false">https://medium.com/p/e47f71083bdf</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <dc:creator><![CDATA[Tabrez Alam]]></dc:creator>
            <pubDate>Tue, 09 Jul 2019 06:49:46 GMT</pubDate>
            <atom:updated>2019-07-09T06:49:46.266Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*Yk_29_KkX8sDbA4a0c3SLQ.jpeg" /></figure><h3>Three things that I learnt about Leadership — Episode 2</h3><p>Three things that I learnt at my very first job and from the same person, which shaped the way I think of leadership.</p><p>Episode 2:</p><p>My first job was information security sales and consulting and way back in 2004, people were not too exposed to the need of information security. As a result of which, my job in sales was becoming difficult as no-one was willing to even listen to the fact that they may be vulnerable.</p><p>The word security was only synonymous to the guards at the gate. To my disbelief, a lot of guards did not let me in when I told them that I wanted to meet the IT head for Information Security. Somehow, they thought that I was from another security agency and if I got in, there are chances that he may get fired. Anyways, that was my struggle each day.</p><p>One final day, I got an order for a high end firewall from a company; and I was on top of the world. The first thing that I did was to call up my boss and tell him that finally I was able to make a sale.</p><p>I was a 22 year old kid who had made his first sale, so I went on an on for almost 10 minutes describing how difficult was it to get this sale done; and how many meetings I had to do.</p><p>My boss listened to me all this while with complete patience, and when I was done. He congratulated me, and said that I had done a great job as not too many people are able to make their first sale so fast (which I must confess I had taken more than 6 months to do).</p><p>Then he paused for a couple of seconds and asked me, ‘Do you really think this company needs such a high end and sophisticated firewall’? I was amazed at the question, as I did to expect my boss to ask me this. I also took a couple of seconds and said ‘As far as I understand, they do NOT need it’. His next question was, so if you thought they do not need it, did you tell them? I said NO.</p><p>The next few sentences from him again were jewels. He mentioned, when you are making a sale (whether a service or a product), you are not selling the product of service. No where across the world, you sell products or services, you always sell relationships. When a person places an order with you, he trusts you for not just guiding him in the beginning with the sale, but subsequently in deployment, after sale service and a lot more.</p><p>You also have to act in a manner that you gain trust of the person sitting in front of you. Never look for the short term sale, but remember that every person whom you meet has the potential of giving you a million dollar deal in his lifetime.</p><p>When we say, that you should be Customer Centric, this is what customer centricity is.</p><p>In these days, when sales are just numbers, not too many bosses will probably give such an option to their teams, and I am thankful that I was in an environment that I learnt such a valuable lesson.</p><p>Episode 3: Read it <a href="https://medium.com/@alamtabrez/three-things-that-i-learnt-about-leadership-episode-3-e6486e8807c7">here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e47f71083bdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three things that I learnt about Leadership — Episode 3]]></title>
            <link>https://medium.com/@alamtabrez/three-things-that-i-learnt-about-leadership-episode-3-e6486e8807c7?source=rss-62856cbbef84------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6486e8807c7</guid>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Tabrez Alam]]></dc:creator>
            <pubDate>Tue, 09 Jul 2019 06:45:37 GMT</pubDate>
            <atom:updated>2019-07-09T06:45:37.231Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oy2vr8Y5DzQL_E386ZI1ng.jpeg" /></figure><h3>Three things that I learnt about Leadership — Episode 3</h3><p>Three things that I learnt at my very first job and from the same person, which shaped the way I think of leadership.</p><p>Episode 3:</p><p>Let me start this with a story of a typical office that you find. There was a Boss and there were a lot of employees. Let us consider one of the employees as ‘The One’. The One was good at doing some things and not good at doing some other aspects of the work (just like all of us). <em>We have our own strengths and our own weaknesses</em>. So ‘The One’ used to come to office each day and work hard and try to deliver an output that ‘Boss’ expected.</p><p>Unfortunately, for ‘The One’, the things he was not good at, were the things in which Boss was really good at. Let me give an example, ‘The One’ was good at reading data, understanding the data and providing very good analysis. But he was really poor at making presentations. Now, his Boss was really good at making presentations and could really beautify even the worst of them all. As a result of which, the Boss never liked The One’s work.</p><p>All of us can gauge what would happen to ‘the one’ each day in office. He used to get scolded virtually everyday in office. This was so regular that everyday at around 5:00 PM, The One and the entire team would know that he is up for his regular thrashing.</p><p>While this routine was very normal, I saw something odd. ‘The One’ would come back from his meeting, he would be cheerful as usual, chat with us, may be go for a tea break with us and behave as if nothing had happened. So we asked him how did he manage to remain so calm and cool post such ‘sessions’.</p><p>He said, ‘Have you guys ever played a video game? In a video game, if you fight, you hit some, you get hit at times and may be even get killed. However, are you worried after the game is over that you very badly punched and hit in the video game?’. Our answer was obvious, none of us obviously felt bad that we were bashed up in a game. Then came his reply, ‘I do the same thing, I imagine that I was in a video game being punched badly and thrashed, but when I come out of the room; the game is over! So, I resume my work.’</p><p>While some may disagree with the approach that ‘the one’ took, but the fact is that people take their way out.</p><p>This incident took my back to again my initial days in corporate. I was again sitting with my boss and I was worried. It was a monthly review of what had happened in sales over the last month and I knew I had goofed up and missed an opportunity for a big tender (it was a clear oversight from my side and I knew it). I was waiting to be scolded and shouted at, but it never happened.</p><p>Later, I gathered the courage to ask my boss, so I went up to him and asked ‘<em>Why did you not scold me for missing the obvious tender?</em>’. His reply sums up again one of the finest learnings. ‘<em>As a leader, I need to have an understanding of people. When I met you, I automatically realised that you knew about your mistake and were keen that you should not repeat it. The reason for feedback is only one, ‘improvement’ and when you already know that you need to improve, what is the point of me repeating the same thing?</em>’</p><p>The second part of his response was even more important. He said, ‘<em>Raising your voice is like a nuclear weapon in your arsenal. You cannot use a nuclear weapon everyday and every time. When you start raising your voice frequently, the impact of it diminishes very fast. It is just like a mosquito coil, when you use the mosquito coil for a very long time, you would see that the mosquitos are getting used to it and are no longer deterred by the smoke. Do not let your high pitch become the mosquito coil of your team!</em>’</p><p>When we give feedback to people, there are two very important things to remember.</p><p>1) Why are you giving the feedback? The only reason to give a feedback is to bring improvement. Therefore, if you already see that the improvement area has been realised, there is no point to give feedback.</p><p>2) How are you giving feedback? With the above objective in place, your mode of communication should be in a manner that hits the person with a note that makes an impact. When you raise your voice or accuse of a miss, the person automatically goes on a defensive mode. When a person is in a defensive mode, the chances of assimilating your feedback is much lower.</p><p>Ideally when a person goes out of a meeting room, you would want him or her to work with 200% passion rather than 50% of it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6486e8807c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a Truck Driver Taught me what Corporate Trainings could not]]></title>
            <link>https://medium.com/@alamtabrez/how-a-truck-driver-taught-me-what-corporate-trainings-could-not-93cc60ee906?source=rss-62856cbbef84------2</link>
            <guid isPermaLink="false">https://medium.com/p/93cc60ee906</guid>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Tabrez Alam]]></dc:creator>
            <pubDate>Tue, 09 Jul 2019 06:37:19 GMT</pubDate>
            <atom:updated>2019-07-09T06:37:19.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E6X0Xcx4mbLWBXbARLK8NQ.jpeg" /></figure><p>It was a cold winter night in Delhi winters, so anyone who has stayed in Delhi during winters would know how cold and freezing it gets. This was almost a decade back, when the fog cover used to be very thick at night and seeing even 10 meters in front of you used to be difficult.</p><p>We were 3 friends who were sitting together and as usual doing absolutely nothing, when someone said he wanted to have Rajasthani food. I must confess that our group was really an impulsive one, so when one of them wanted to have Rajasthani food, instead of telling him to shut up, we all got up and got into a single car.</p><p>It was almost 2:00 AM, so obviously no restaurants (which could give us Rajasthani food) were open, so we took on to Delhi Jaipur highway, in the hope of finding a Dhaba which could give us Rajasthani food. In heavy fog we kept driving for almost 2 hours but did not enter the Rajasthan border, and by this time our enthusiasm was over. So we decided to stop the any next dhaba, have some good parathas and then head back home.</p><p>We stopped at a dhaba, which was the normal one for truckers. They were having cots all across, with some truck drivers sleeping, so chatting around. We sat down on one of the cots and ordered.</p><p>While we were waiting for our food to arrive, I saw that one of the truck drivers was washing his truck passionately. It was almost 4:00 AM in the morning, the water from the open tank was almost ice and still he was happily washing his truck. At a time when we did not even wash our hands to eat (as it was so cold), someone was washing his complete truck, that too with buckets of water!</p><p>While we were having our food, I think the truck driver got done with washing the truck, so he came and sat on a cot next to our and ordered for food. At 4:00 AM in the morning, at a random dhaba, everyone becomes a friend, so we asked the driver whether he was mad that he was washing his truck at such an hour. He could have done it in the morning as well when there was at least some sunshine. At least he could have had his food and then washed the truck.</p><p>His response was, ‘Sir, it is my own truck and not someone else’s which I am driving. My entire livelihood comes from this truck, so why should I not take care of the truck more than myself?’</p><p>One of the finest attributes of management, taught in a single sentence by a truck driver. We see everywhere that people take really good care of the machinery, you try and find the best air conditioners for your server room, ensure that the temperature does not go above or below a certain level at all time. The reason is that, we know that machinery can break down anytime.</p><p>So what happens to us when our machinery is actually humans? Do we really think that we take care of our human machinery, as well as, we take care of our actual machines? The reason why we may not pay a lot of heed to taking care of human workforce (machinery) is that we know that even if a human machine breaks down, it is self healing. The person may be down for a day or couple of days, but would ‘repair’ itself and be back to normalcy on its own. This ‘self healing’ property of human being may be really good. However, the questions is ‘Should we entirely rely on this fact, and still be casual about taking care of our human resources?’</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93cc60ee906" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Urgent and Critical — Is someone dying?]]></title>
            <link>https://medium.com/@alamtabrez/urgent-and-critical-is-someone-dying-1cf0db78b459?source=rss-62856cbbef84------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cf0db78b459</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[urgency]]></category>
            <dc:creator><![CDATA[Tabrez Alam]]></dc:creator>
            <pubDate>Tue, 09 Jul 2019 06:34:12 GMT</pubDate>
            <atom:updated>2019-07-09T06:34:12.918Z</atom:updated>
            <content:encoded><![CDATA[<h3>Urgent and Critical — Is someone dying?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EmZaqe542X7WnR7GOT8y6A.jpeg" /></figure><p>We all have friend’s from different walk of life and different professions, so do I. I have a friend who is an IPS officer and was stationed in a district as a Superintendent of Police. I have an office in Coimbatore, so whenever I was there, I used to spend the weekend with my friend. I would leave from my office at 6:00 PM on a Friday, spend the weekend with him and be back on a Monday morning.</p><p>As two friends, who were bachelors, we would sit every evening chatting about everything under the sun from politics to start-ups and what not. However, even at 1:00 AM, my friend would always have his cell-phone and the walky-talky with him. I would always leave the phone in the room, as I did not like emails and messages disturbing me when I was sitting with a friend.</p><p>One day, during our discussions, I asked him; why do you always have you phone and the wireless set with you all the time? It has been more than 10 times that I have been here on the weekend and you seldom get calls at this hour or the information on walky talky, you seldom act of them. So that is the point of carrying them everywhere?</p><p>He said, buddy murders and riots do not happen everyday, but when they happen, human lives are lost; which are irrevocable damages. I keep this with me for those days, because I know that my lack of attention or response at the appropriate time, may lead to people dying. Every second counts.</p><p>I completely agreed with him and never questioned again.</p><p>As usual, being a social animal, I have a lot of friends. One fine evening, we were sitting together and having fun. It was almost 11:00 PM at night when his phone rang, it was his boss calling. He say the incoming call, made the phone silent and then we started talking again. I asked him, dude it was your boss calling. There may be something urgent.</p><p>In response to my question, he responded, ‘You know what is my work profile, right? I help big corporations file their patents, maintain them and take actions based on Intellectual Property. Now based on my work profile, can you tell me what can be so pressing at this hour?’ I have also spent almost a decade in the same industry, and I realised that the only pressing matter could have been a missed deadline, or an angry client.</p><p>Then he spoke the golden words, ’Dude, let us not take our work more seriously than it deserves to be. No one is dying because I did not pick up the phone. Any other form of loss is monetary, which is not irrevocable, so why should we pretend that we are firefighters saving lives?’</p><p>While this story may be taken differently by different people, some may say that him not picking up the phone could have lead to a potential million dollar loss to the company. Well, that is a potential, but how often does that happen? In case a company’s million dollars profit and loss are dependent on a single person, then it is the company’s fault entirely that they they not have backups for such critical processes.</p><p>We all have the habit of considering every work and ‘urgent and critical’, but before we decide to mark all of them critical, do we take out a fraction of a second to thing, how critical is the job actually?</p><p>With emails on phones and cellular connectivity making people accessible everywhere, we have increasing stopped to refrain ourselves from calling people post office hours. Was the world not working before cell-phones and emails came into existence? It was working and it was working fine. During those days, we knew that one the person is out of office, he can hardly do anything to help, so we were prepared accordingly. We used to categorise things as critical and urgent only when they actually were!</p><p>So the next time, we pick up the phone to call a colleague or an employee, let us first ask a question to ourselves, ‘If I could not call him/her right now, how would it be managed?’ We may get the following answers:</p><ul><li>‘I would need to do it myself’ — Then go ahead and let us do it ourselves</li><li>‘This could wait till tomorrow morning’ — Go off to sleep in this case</li><li>‘Only employee knows this, and many people would die [pun intended, it is the number of people impacted and the intensity of the impact: be genuine when asking this to yourself — This does not happen more than once in six months in any good organisation] — Go ahead make the call</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cf0db78b459" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>