<?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 Satheesh Kumar on Medium]]></title>
        <description><![CDATA[Stories by Satheesh Kumar on Medium]]></description>
        <link>https://medium.com/@satheesh.cdo?source=rss-2919e7b347c3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WvWXXCEYsUclhf6jbLemgQ.jpeg</url>
            <title>Stories by Satheesh Kumar on Medium</title>
            <link>https://medium.com/@satheesh.cdo?source=rss-2919e7b347c3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:43:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@satheesh.cdo/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[ “Accident Zone – Go Slow”: Signboards or Silent Surrender?]]></title>
            <link>https://medium.com/@satheesh.cdo/accident-zone-go-slow-signboards-or-silent-surrender-1a6ea2e48066?source=rss-2919e7b347c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a6ea2e48066</guid>
            <dc:creator><![CDATA[Satheesh Kumar]]></dc:creator>
            <pubDate>Thu, 07 Aug 2025 03:39:46 GMT</pubDate>
            <atom:updated>2025-08-07T03:39:46.884Z</atom:updated>
            <content:encoded><![CDATA[<p>🛑 “Accident Zone – Go Slow”: Signboards or Silent Surrender?<br>You see them everywhere.<br>Bent, rusting, sometimes half-covered in moss or dust.</p><p>&quot;⚠️ Accident Zone – Go Slow&quot;</p><p>At first glance, these signs seem like public service announcements—concerned, preventive, cautionary. But if you pause for a moment and really think about what they imply, a darker truth emerges:</p><p>These boards are not signs of safety.<br>They’re admissions of failure.</p><p>🚧 The Road to Nowhere (Safe)<br>Isn’t it the job of authorities to design roads that are inherently safe?<br>To engineer turns, slopes, intersections, and dividers that prevent accidents, not just warn about them after the damage has been done?</p><p>Then why are we plastering roads with signs like “Accident Zone” instead of:</p><p>Redesigning dangerous curves?</p><p>Fixing blind spots and broken medians?</p><p>Installing proper street lighting?</p><p>Ensuring speed regulation through intelligent systems?</p><p>Because that takes time.<br>And money.<br>And accountability.</p><p>A signboard? That’s cheap, fast, and looks like someone “did something.”</p><p>⚰️ The Casual Cruelty of Normalization<br>When a dangerous zone claims one life, it’s a tragedy.<br>When it claims lives repeatedly, and nothing changes except another signboard being nailed into the ground, it becomes something far worse:</p><p>Institutionalized apathy.</p><p>We have normalized death on our roads by reducing design incompetence to a warning label. It’s no longer “How do we fix this?” but “Let’s warn the next one.”</p><p>What are these signs really telling us?</p><p>“People have died here. You might too. But hey—go slow.”</p><p>🧠 A Failure of Design Thinking<br>In countries with progressive transport policies—like Sweden’s Vision Zero—the goal is simple:</p><p>No loss of life on the road is acceptable.</p><p>They redesign roads and systems with the assumption that humans make mistakes.<br>So they build forgiveness into the system:</p><p>Rumble strips before intersections</p><p>Reduced-speed curves with barriers</p><p>Pedestrian zones separated by height and color</p><p>Data-driven monitoring to tweak layouts</p><p>But in many parts of the world, especially developing nations, what we get instead is:</p><p>Narrow flyovers with zero merge length</p><p>Speed breakers unpainted and unmarked</p><p>Traffic lights hidden behind tree branches</p><p>Slopes that flood during rain, with no drainage</p><p>And then?<br>A sign.<br>&quot;Go Slow.&quot;<br>Good luck.</p><p>📉 Who’s Accountable?<br>Every &quot;Accident Zone&quot; signboard should come with:</p><p>A QR code linking to accident data from that zone</p><p>A contact tag: who designed the road, when it was last audited, what corrective measures were taken</p><p>A public feedback loop inviting redesign ideas from citizens and local engineers</p><p>Instead, they stand like silent tombstones:<br>No names. No history. Just a vague hope that the next vehicle will survive.</p><p>📣 Citizens, Speak Up<br>We must demand:</p><p>Human-centric road design</p><p>Data transparency on accident-prone zones</p><p>Public consultation before major road infrastructure is executed</p><p>Road Safety Audits with real consequences when corners are cut</p><p>Because until then, the system will continue counting dead bodies, while we pretend that signage is a substitute for safety.</p><p>🛑 A Signboard is Not a Safety Feature.<br>It’s a memorial plaque in disguise.</p><p>💬 Share this if you&#39;ve ever slowed down at one of these signs and thought:<br>“Why hasn’t this road been fixed yet?”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a6ea2e48066" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ The Lost Smile: Why India Feels Indifferent — And How We Can Reclaim Our Soul]]></title>
            <link>https://medium.com/@satheesh.cdo/the-lost-smile-why-india-feels-indifferent-and-how-we-can-reclaim-our-soul-7ebb9f0628e7?source=rss-2919e7b347c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ebb9f0628e7</guid>
            <dc:creator><![CDATA[Satheesh Kumar]]></dc:creator>
            <pubDate>Sat, 02 Aug 2025 13:02:04 GMT</pubDate>
            <atom:updated>2025-08-02T13:02:04.218Z</atom:updated>
            <content:encoded><![CDATA[<p>🇮🇳 The Lost Smile: Why India Feels Indifferent — And How We Can Reclaim Our Soul</p><p>A heartfelt call to rebuild connection, dignity, and inclusion in a nation burdened by quiet apathy<br>There was a time—not long ago—when India’s warmth wasn’t just poetic nostalgia. It was real. You could feel it in the eyes of strangers, the folded hands of greeting, the slight tilt of the head in acknowledgement.<br>Today, you’ll be lucky to get eye contact.</p><p>On platforms, in lifts, in colonies and even family functions—people walk past each other with blank stares, or worse, pretend the other doesn’t exist. Smiles are reserved for transactional greetings. Prostrations for power. Outside of need, most people have become invisible to each other.</p><p>What happened?</p><p>😓 The Quiet Exhaustion of Modern India<br>India today is a nation in motion—but motion without meaning. There’s urgency in everything: growth, GDP, job hunts, board exams, upskilling, political outrage, and property purchases. But somewhere in that rush, our emotional bandwidth has collapsed.</p><p>We’re tired. Mentally, spiritually, morally.<br>So we stop seeing.</p><p>Everyday gestures like “good morning”, “can I help?”, or even a glance to acknowledge a disabled person in distress—have vanished from public life. We didn’t become evil. We just became too distracted, too fatigued, too self-protective.</p><p>🎭 The Great Cultural Disconnection<br>India loves to talk about culture. About its 5000-year-old civilisation, its family values, its hospitality.</p><p>But culture is not what you say. It’s what you do.</p><p>We proudly quote Atithi Devo Bhava (The Guest is God), but treat delivery workers and janitors like background furniture. We extol karuna (compassion) and seva (service), but block ambulances for VIP movement. We light lamps for festivals, but don’t light up when we meet people.</p><p>We touch feet for blessings, but won’t bend down to pick up a fallen stranger.<br>We offer garlands in temples, but not space in our daily lives.</p><p>♿️ Disability and the Apathetic State<br>Nothing reveals a society’s soul more than how it treats its most vulnerable.<br>And when it comes to disability, we’re in a national state of denial.</p><p>Public buildings remain largely inaccessible.</p><p>Railway platforms, buses, even government offices have no proper ramps, signage, or support.</p><p>Caregivers face daily humiliation just to access basic services.</p><p>Teachers and employers avoid inclusion under the excuse of &quot;not being equipped&quot;.</p><p>Worse, the public stares—but does nothing.<br>Sympathy is offered in words, but not in design, empathy, or action.<br>Governments run token schemes with no follow-through. Policies exist, but implementation limps—literally.</p><p>This is not an infrastructure issue. It is a reflection issue.</p><p>🔁 The Transactional Mindset: Smile When You Need, Ignore When You Don’t<br>Walk into a bank, a school, or even your own housing society. People are polite when they need something. But otherwise, cold. Dismissive. Or indifferent.</p><p>Our social behavior has been reduced to two modes:</p><p>Charming when in need</p><p>Ghost-mode when self-sufficient</p><p>We’ve turned human relationships into business transactions.<br>And that comes at the cost of basic human warmth.</p><p>🌟 So What Can Be Done? (And Why It’s Urgent)<br>This is not a cynical post. It’s a call to remember who we really are—and who we still can be.</p><p>1. Reclaim Small Civilities<br>Acknowledge people you don’t need.</p><p>Smile without agenda.</p><p>Teach your children to greet, help, and notice others.</p><p>2. Civic Sense as Cultural Heritage<br>Being clean, kind, and fair isn’t &quot;Western&quot;—it’s Indian, when we live up to it.</p><p>Queues, lanes, silence zones, yielding seats—make them everyday practice.</p><p>3. A Disability-Inclusive Revolution (On War Footing)<br>Make every public institution accountable for accessibility.</p><p>Penalise non-compliance.</p><p>Fund support systems for families and caregivers.</p><p>Build inclusive schools, hire inclusively, and train everyone—from clerks to corporates—in disability empathy.</p><p>4. Governance That Reflects Indian Values<br>We don’t need more Sanskrit quotes. We need footpaths.<br>We don’t need more festivals. We need functioning healthcare.<br>We don’t need selfies with “Divyang” citizens. We need ramps that don’t lead to walls.</p><p>5. Citizenry of Conscious Action<br>A democracy isn’t made in polling booths alone. It’s made every day—in how we behave, how we show up, and how we treat the least among us.</p><p>🕉️ India: Not Just a Country, But a Consciousness<br>India isn’t failing because of culture. It’s faltering because of conduct.<br>Because we forgot that dharma is not just about temples—it’s about how we live with others.</p><p>This is still one of the most beautiful places on Earth.<br>Let us not reduce it to a hypergrowth economy with heartless people and hostile public systems.</p><p>India can be a heaven.<br>But not until we look each other in the eye again.</p><p>✍️ If you resonated with this piece, smile at someone today. Ask if they need help. And more importantly—vote, speak, and act for a kinder India. It’s the only one we’ve got.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ebb9f0628e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding “Hands-On”: Why We Need a Clearer Standard in Technology Hiring]]></title>
            <link>https://medium.com/@satheesh.cdo/decoding-hands-on-why-we-need-a-clearer-standard-in-technology-hiring-bc6faa6efa2e?source=rss-2919e7b347c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc6faa6efa2e</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[hands-on]]></category>
            <dc:creator><![CDATA[Satheesh Kumar]]></dc:creator>
            <pubDate>Fri, 25 Jul 2025 15:12:59 GMT</pubDate>
            <atom:updated>2025-07-25T15:26:05.864Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s rapidly evolving technology landscape, one phrase that appears ubiquitously across job descriptions — regardless of domain, seniority, or geography — is <strong>“must be hands-on.”</strong></p><p>While the intent behind this requirement is understandable, the <strong>lack of standardization</strong>, combined with vague or unrealistic expectations, has made “hands-on” one of the most <strong>misunderstood, misapplied, and misused</strong> phrases in modern technology hiring. It has become a <strong>source of misalignment, frustration, and often, unnecessary candidate attrition</strong>.</p><h3>The Problem: One Phrase, Many Interpretations</h3><p>“Hands-on” is now a <strong>catch-all term</strong> — used loosely by hiring managers, HR teams, and automated systems to indicate everything from:</p><ul><li>Ability to write production-level code from scratch</li><li>Familiarity with infrastructure tools like Docker, Airflow, or MLflow</li><li>Leading data science teams with technical credibility</li><li>Performing basic Jupyter Notebook experiments or exploratory analysis</li></ul><p>This ambiguity creates two serious problems:</p><ol><li><strong>Candidates are misjudged or set up for failure</strong>: Highly experienced professionals applying for strategic or leadership roles are often evaluated using frameworks meant for junior or mid-level engineers.</li><li><strong>Organizations miss out on valuable talent</strong>: Misaligned expectations lead to lengthy, fragmented interview processes that waste time, increase attrition, and ultimately compromise hiring goals.</li></ol><h3>The Rise of AI-Driven Screening: Urgency for Standardization</h3><p>The need for clarity has never been more urgent. With the increasing reliance on <strong>AI agents, bots, and automated Applicant Tracking Systems (ATS)</strong> to handle resume filtering, initial screening, and even engagement decisions, the margin for misinterpretation has widened.</p><p>Recruiters, especially in third-party staffing firms, <strong>often have minimal control over how “hands-on” filters are applied</strong> or how engagement evolves with the end-client. In such an environment:</p><blockquote><strong><em>Codifying and communicating the expected “hands-on level” (HOL) is not just a best practice — it is essential to preserve goodwill, reduce mismatched expectations, and avoid months of wasted effort for both sides.</em></strong></blockquote><h3>Introducing Hands-On Levels (HOL): A Standardized Framework</h3><p>Here’s a proposed classification of <strong>Hands-On Levels (HOL)</strong> to define expectations based on <strong>role, context, and industry maturity</strong>:</p><p><strong>Note:</strong> The companies listed are <strong>representative examples</strong> to illustrate typical role expectations and contexts. Their inclusion does <strong>not imply strict alignment</strong> with the described Hands-On Levels (HOL), nor an endorsement of any hiring practice. Roles and expectations may vary within each organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RePYjMZnsGnSc6TyXMKNHw.jpeg" /></figure><h3>Hands-On Expectations Are Role-Specific</h3><p>Let’s clarify with an example:</p><ul><li>A <strong>Partner-track AI Consulting Lead</strong> at a global consulting firm should ideally operate at <strong>HOL-0 to HOL-1</strong>, focusing on business strategy, advisory, stakeholder orchestration, and architectural direction.</li><li>A <strong>Senior Research Scientist</strong> at OpenAI or Google Brain should be <strong>HOL-5</strong>, expected to code from scratch, publish papers, and build custom models in Python, C++, or JAX.</li></ul><p>Confusing one for the other and <strong>running them through the same interview rubric</strong> is a disservice to both the organization and the candidate.</p><h3>The Hidden Damage: Misaligned Panels and Rogue Usage</h3><p>Though senior candidates often intuitively understand that “hands-on” has contextual meaning, <strong>the damage is already done</strong>:</p><ul><li><strong>Interview panels</strong> frequently apply an outdated or irrelevant evaluation framework</li><li><strong>Recruiting teams</strong> may push irrelevant coding tests or programming rounds</li><li><strong>Rogue organizations</strong> misuse “hands-on” to <strong>deliberately run marathon-style interviews</strong>, aiming to filter out experienced candidates by overwhelming them, or replacing senior applicants with cheaper hires under the pretext of technical insufficiency</li></ul><p>This doesn’t just hurt candidates — it creates <strong>reputational damage</strong> for the hiring organization, delays team ramp-ups, and results in <strong>strategic mis-hires</strong>.</p><h3>A Call to Action: Codify, Align, Respect</h3><p>To modernize and humanize the tech hiring process:</p><ol><li><strong>Codify the Hands-On Levels in Every JD</strong><br> Use language like:<br> <em>“Expected Hands-On Level: HOL-2 — Solution Design &amp; Review, Not Day-to-Day Coding”</em><br> This helps everyone — candidate, recruiter, and interviewer — understand what’s expected.</li><li><strong>Align Interview Rounds to the HOL</strong><br> Don’t ask a Director to build a CNN from scratch on a whiteboard. Assess system design, stakeholder alignment, or innovation narratives relevant to their level.</li><li><strong>Respect the Value of Strategic Talent</strong><br> Not every AI leader is — or should be — writing microservices daily. Hands-on credibility is vital, but <strong>leadership, vision, and the ability to drive adoption at scale</strong> are equally important.</li></ol><h3>Conclusion: Let’s Make “Hands-On” Human Again</h3><p>If technology hiring is to evolve alongside the systems and models it builds, <strong>we must redefine what “hands-on” means — not just semantically, but operationally.</strong></p><p>By implementing a standardized, transparent HOL framework, we can:</p><ul><li>Reduce candidate frustration</li><li>Improve hiring precision</li><li>Build goodwill and trust in the ecosystem</li><li>Enable AI-driven screening to be fair, informed, and inclusive</li></ul><p>Let’s not take anyone for a ride. Let’s engineer <strong>a better, smarter, and more dignified hiring future.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc6faa6efa2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taming the Agent: Engineering Accountability in Agentic AI Systems]]></title>
            <link>https://medium.com/@satheesh.cdo/taming-the-agent-engineering-accountability-in-agentic-ai-systems-62b5547f4b5c?source=rss-2919e7b347c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/62b5547f4b5c</guid>
            <category><![CDATA[agentic-ai]]></category>
            <dc:creator><![CDATA[Satheesh Kumar]]></dc:creator>
            <pubDate>Thu, 03 Jul 2025 16:23:23 GMT</pubDate>
            <atom:updated>2025-07-03T16:23:23.187Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hLh2oGBe9J-xUibhWhGTbg.png" /></figure><p>Agentic AI is having its Raspberry Pi moment — accessible, exciting, and everywhere. Everyone’s building agents that browse the web, book meetings, draft emails, debug code, or even write themselves.</p><p>But unlike Raspberry Pi projects, Agentic AI isn’t just tinkering. These systems perceive, reason, and act — autonomously.</p><p>And that autonomy, without accountability, is a loaded gun in a glass house.</p><h3>⚠️ The Problem: Autonomy Without Ethics</h3><p>Raspberry Pi never accidentally leaked your emails, hallucinated financial advice, or triggered an unauthorized API call.</p><p>Agentic AI can — and has.</p><p>We’re giving agents access to sensitive systems, expecting them to behave <em>ethically</em>, <em>securely</em>, and <em>intelligently</em>… when they understand none of those concepts. It’s like giving a well-read toddler the CEO’s calendar and asking it to optimize the quarter.</p><blockquote>The danger isn’t in what the agent can do — it’s in what we forget to prevent it from doing.</blockquote><p>Essentially, Agentic AI is not just another experiment platform. It’s a highly capable, potentially uncontrollable system unless constrained properly. The charm of “Look what my AI agent did!” must be balanced with serious considerations around safety, alignment, explainability, and ethical guardrails.</p><h3>Autonomy without Accountability</h3><p>Agentic systems make decisions — not just follow scripts. When an agent books a meeting, drafts an email, or modifies code, it’s operating with implied trust. But these models don’t have real-world judgment or consequence awareness.</p><blockquote>You’re giving autonomy to something that doesn’t yet understand ethics, context, or long-term consequences.</blockquote><h3>🛠️ The Solution: Engineering Accountability from Day One</h3><p>You don’t <em>hope</em> an airplane flies — you design it not to crash.</p><p>Accountable Agentic AI requires a shift from building “clever workflows” to engineering governed, explainable systems with observability, constraints, and human-in-the-loop failsafes.</p><p>Making Agentic AI accountable requires a multi-layered technical architecture that combines guardrails, observability, control points, and ethical constraints. Unlike static models or single-turn LLMs, agents operate across time, data, tools, and actions — so accountability must be engineered as a first-class principle, not as a patch.</p><p>Here’s how:</p><h3>1. Action Logging &amp; Audit Trails</h3><blockquote><em>✅ </em>“Log every perception, decision, and action.”</blockquote><ul><li>What to implement:</li><li>Tools: LangSmith, OpenLLMetry, Arize, WhyLabs, WandB Traces</li></ul><h3>2. Role-Based Access &amp; Tool Scope Limitation</h3><blockquote><em>✅ </em>“Don’t give your agent the keys to the kingdom.”</blockquote><ul><li>Define scoped permissions — e.g., this agent can read calendars but not send emails</li><li>Use capability sandboxing — agents should explicitly request permissions for risky actions</li><li>Use API gateways with allowlists (e.g., via API proxy like Kong or Envoy)</li><li>Example: Tool definition in LangChain or AutoGen should declare inputs, constraints, and outputs</li></ul><h3>3. Ethical Constraint Models (xAI + Alignment Wrappers)</h3><blockquote><em>✅ </em>“Wrap agents with moral and logical boundaries.”</blockquote><ul><li>Use secondary critique models that validate outputs before they’re executed (Constitutional AI, ReAct-like checks)</li><li>Add Rule-based filters to prevent unsafe or biased actions</li><li>Inject human values or constraints into goal planners (e.g., “Don’t take actions that affect customer data unless reviewed.”)</li><li>Tools: Guardrails AI, OpenAI Function Calling with human-in-the-loop, Anthropic’s Constitutional AI prompt logic</li></ul><h3>4. Simulation &amp; Test Harnessing</h3><blockquote><em>✅ </em>“Test your agent like you’d test an autonomous car.”</blockquote><ul><li>Use dry-run modes with synthetic environments</li><li>Include unit tests and integration tests for agent workflows</li><li>Simulate goal misalignment scenarios and test agent behavior</li><li>Tools: HoneyHive, LangChain Bench, ReAct simulator loops</li></ul><h3>5. Human-in-the-Loop (HITL) for Critical Tasks</h3><blockquote><em>✅ </em>“Decisions with consequences = human checkpoint.”</blockquote><ul><li>For tasks with regulatory, ethical, or financial impact:</li><li>Display reasoning trace and evidence to assist human review</li></ul><h3>6. Explainability Layers</h3><blockquote><em>✅ </em>“Why did it do that?”</blockquote><ul><li>Add modules that generate:</li><li>Tools: OpenAI’s logprobs, DeepEval, TruEra, ExplainLLM</li></ul><h3>7. Time-bound Memory and Identity Isolation</h3><blockquote><em>✅ </em>“Forget what you don’t need. Don’t act like someone else.”</blockquote><ul><li>Use ephemeral memory contexts for short tasks</li><li>Prevent cross-agent contamination or impersonation</li><li>Regulate memory retention through TTL policies or session scoping</li></ul><h3>📌 Final Word</h3><blockquote><em>“From toy projects to transformative systems — Agentic AI is where Raspberry Pi meets enterprise ambition.”</em></blockquote><p>But ambition without control is chaos.</p><p>Let’s stop marveling at what agents <em>can</em> do and start designing what they <em>should</em> — and <em>must never</em> — do.</p><p>If you’re building agent-based systems, don’t just think <em>autonomy</em>. Think accountability.</p><p>Because in the future, your AI won’t just assist you — it may act on your behalf. And when it does, will you know exactly what it did — and why?</p><p>💬 Let’s discuss: What are you doing to make your AI agents safe, secure, and accountable? Drop your thoughts — or your agent’s thoughts (if they’re allowed 😄) — in the comments, Please !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62b5547f4b5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Great teams and Great work places]]></title>
            <link>https://medium.com/@satheesh.cdo/great-teams-and-great-work-places-871fa388c064?source=rss-2919e7b347c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/871fa388c064</guid>
            <category><![CDATA[harmony]]></category>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <dc:creator><![CDATA[Satheesh Kumar]]></dc:creator>
            <pubDate>Wed, 27 Dec 2017 19:17:51 GMT</pubDate>
            <atom:updated>2017-12-27T19:17:51.895Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*6RUIYG6lslFj1M4gC3LZog.jpeg" /></figure><p>In my experience, I feel the key to a great work place is hiring and managing high performing teams.</p><p>Hiring and setting up a team to be a high performing team needs a great amount of energy, clear strategy, effort and time. I am looking forward to write about that in a near future, but now lets look at how to sustain a high performing team in an industry where delivery, cost, timelines, time to market etc are valued as the core pillars and people come as the last item in the managements laundry list — or sometimes don’t come in the list at all.</p><p>In my experience, the most essential part of managing or sustaining a high performing team is communication. That said, what type of communication am I talking about? technical? interpersonal? corporate politics? persuasive?</p><p>All of the above — but primarily interpersonal communication wins hands down and it pretty much covers all the other areas too.</p><p>And this communication need to be in 360 degrees — means from all the levels and hierarchies of the team — as only a few trying to communicate and feel bewildered in petty office politics (sugar-coated as delivery pressure) and deadlines will not be enough to make the team a high performing one rather it will work the contrary and mess up the goals and objectives of the team.</p><p>To enable such a free-flowing communication, we just need to remember the following golden rules:</p><ol><li>Be Kind and Be Nice to everyone. Know the difference between being nice and kind.</li><li>Stop being a cynic. Express your opinions in a decent language and behaviour.</li><li>Set aside the inflated ego and work towards shared goals.</li><li>Stay learnable, and then learn/coach others all the time.</li><li>Don’t look for predictability in people, rather find out what makes you happy among the things you do at work, and spend your energy there — so you can grow.</li></ol><p>Now, let’s see these five goals in detail:</p><p><strong>1. Being nice and being kind are not the same.</strong></p><p>Being nice means you are able to tolerate others for the sake of social harmony and amicable settlement of potential disputes in the political environment at work. But being kind is really showing your kindness to people.</p><p>It’s the ability to forgive yourself and others when situations don’t go as per the expectations, and the last thing you want to do is to show your integrity and settle things positively without fighting your soul out in wrong negotiations and ending up jeopardising your career (and others too) in the process.</p><p>Know when to be nice, and when to be kind — irrespective of people, their ranks, and hierarchies.</p><p><strong>2. Stop playing a cynics role and express your opinions appropriately</strong></p><p>You will be tempted to be a cynic due to negative forces at work, and abusing the people involved, their roles, their assumed powers, their influence circles and who-knows-who-and-hows are all part and parcel of a journey called work, but ensure that you are not falling victim to this pitiable cynic mentality.</p><p>Express your opinions in an appropriate way — appropriate to your office culture, and appropriate in a general way — without seasoning your flurry of words with any four letter words, but use appropriate language, be polite, and express your thoughts.</p><p>Some tips for expressing your ideas without messing up your career:</p><ul><li>Thoughts / Opinions — write down before you speak,</li><li>Complaints — explain whats your idea of a solution to the problem you are complaining about — else its called whining or gossiping,</li><li>Disappointment/Expectation mismatch — talk to the right authority, keep your immediate manager informed all the time, and involve HR and higher management if needed — reach out to support groups in the organization before reaching out to the social media and show your mettle.</li><li>Don’t ever gossip — its for silly, poor people. No water cooler talks, no loose talks with drinks, no affairs with a colleague (most dangerous career breaker), and simply refuse to participate in anything that doesn’t grow you as a good human being.</li><li>Refrain from expressing your personal stories, political preferences, and religious beliefs unless and until asked explicitly by some one. Even in that case, choose to stay neutral and don’t give-in to peoples whimsical needs and waste your time and energy.</li></ul><p><strong>3. Set aside the inflated Ego — yours and others alike.</strong></p><p>Ego is one of the serious killers of productivity, progress, learnability and manageability. Its very easy to get your ego inflated due to various situations at work, and you will face professionals with inflated ego in any work day at office or from your customers side. Please note that most of the time we assume and take it for granted as others ego may be due to their inability in handling various situations, deadlines, and goals/objectives and when you misunderstand this, set an unforgiven attitude, and then act upon it to avenge the opponent in all ways possible, you are sabotaging your own mind, your work, team dynamics, the business and ultimately career at the end.</p><p>When you face such situations, learn to be kind and nice. Thats vey important and its the No:1 Ego killer. With a little practice you will see this is somewhat like a non-violence principle — satyagraha and you will be at peace with yourself — hence with others too.</p><p><strong>4. Stay learnable, and then learn/coach others all the time.</strong></p><p>Keep your mind open, stay approachable by others. This will help you to achieve a lot in life as you will stay learnable and coachable by others. Once you reach this level, you will start coaching others without even being aware of it. Also, don’t find just one mentor, find more of them in each of your area of interest — and learn from them, be an apprentice, put extra efforts irrespective of the age or gender differences, culture, or role/rank in the organization between you and the mentors.</p><p><strong>5. Don’t look for predictability in people</strong></p><p>We always expect some level of predictability with others. There are companies that has predictability as one of their key values. They are so ignorant of the Human Dynamics, and ever-increasing cultural volatility with every new generation of employees, but hope to have some predictability thinking that predictability is the key point in managing people, delivery, and even the growth strategy of the company itself — which is wrong in multiple counts.</p><p>Whenever we see the absence of predictability, we judge people and put them in labelled, colored boxes without ever realizing that the unpredictability is the collection of patterns and not a one-off event at work. We invent and apply patterns to their behaviors to fit into our bell-curve of predictability all the time. May be the unpredictability is the symptom of their inability to comprehend the complexity of the situation/solution/strategy, or some times its due to their physical &amp; mental well being at that point in time. We never know what others are undergoing in their personal/professional lives, so just don’t jump to a conclusion and judge people based on your skewed world-view.</p><p>I am not advocating absolute unpredictability should be acceptable in an organizational setting, rather I am advocating the fact that they are Humans, hence are inherently unpredictable and unprepared to handle the ever increasing complexity in this world, hence handle them with care, else automate whatever you can, and let them not do the mundane trivial work you call it a ‘job’. Coach them in their strengths, and give them a role they can shine, or treat them well by letting them go for good.</p><p>If you are constantly facing unpredictability from the colleagues, customers and management, then find out what makes you happy in the hundreds of things you do/available a work, and then concentrate your energies their instead of becoming a whiner and acquire negativity leading to serious disappointments and downward spirals in your life.</p><p>Let me know your thoughts / comments please.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=871fa388c064" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>