<?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 Raja T M on Medium]]></title>
        <description><![CDATA[Stories by Raja T M on Medium]]></description>
        <link>https://medium.com/@tmraja2020?source=rss-dd87a4a8fa26------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*z3S72592l3ZzWtCeHmIMtw.jpeg</url>
            <title>Stories by Raja T M on Medium</title>
            <link>https://medium.com/@tmraja2020?source=rss-dd87a4a8fa26------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:49:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tmraja2020/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[If AI Can Do Your Job, Which Part Was Ever Yours?]]></title>
            <link>https://medium.com/@tmraja2020/if-ai-can-do-your-job-which-part-was-ever-yours-bd086bc66ea3?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd086bc66ea3</guid>
            <category><![CDATA[future]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[jobs]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 02:51:52 GMT</pubDate>
            <atom:updated>2026-11-10T02:51:52.865Z</atom:updated>
            <content:encoded><![CDATA[<h3>What the AI films got wrong, and the ten percent that’s still ours</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*W4V2JfzImyKmGRUQf5w95w.png" /></figure><p>A few weeks after a session I ran for a community of marketers, a message landed on LinkedIn. It was from one of the attendees, a developer who writes AI skills for a living.</p><p>Most follow-up messages say “great session, let’s connect.” This one came with a document. Neatly typed. Section headings. Ten questions.</p><p>One line from my session had stayed with him: that an entire SEO process can be consolidated into a single AI skill. “As a developer who writes skills,” he wrote, “that blew my mind.”</p><p>Then came the questions. What are the nuances of automating SEO? Where do agents work, and where do they fall flat? Will sales and marketing collapse into one team? And sitting quietly in the middle of the list, the one that does all the heavy lifting:</p><h3><em>What is the role of humans now?</em></h3><p>It’s the question underneath almost every AI conversation right now. Usually it’s asked half curious, half nervous, like someone asking the doctor about a test result they’ve already googled.</p><p>I think I know where the nervousness comes from. Most of us didn’t meet AI in a product demo. We met it in a cinema hall, with popcorn. A machine walks out of the fire and promises he’ll be back. (He kept that promise. Six films and counting.) People sleep in pods, dreaming a world that isn’t real. A robot on a spaceship cracks jokes while deciding how honest to be with the crew.</p><p>For forty years, the films have been our rehearsal for this moment. They drew the picture long before any of us typed a prompt.</p><p>So when someone who actually builds skills asks what’s left for humans, he isn’t really asking about software. He’s asking which film we’re in.</p><h3>Plot twist: we’re the ones writing it</h3><p>Here’s the uncomfortable bit. Nobody is doing this to us.</p><p>We write the skills. I automate my own work every chance I get. Across the industry, every week, people like us take one more thing a human used to do and turn it into instructions a machine can follow. Then we go home and wonder, slightly worried, what’s left for us.</p><p>It’s a bit like a screenwriter who keeps cutting his own scenes and then asks the director why he has so little screen time.</p><p>We aren’t the audience. We’re writing the script, one skill at a time.</p><p>If everything can be a skill, what’s left?</p><p>To answer that honestly, I had to stop watching the films for the fear and start watching them for what they actually show.</p><h3>What the posters don’t tell you</h3><p>Every one of these films tells two stories: the one on the poster, and the one underneath. The poster sells tickets. The one underneath is the useful one.</p><p>Take <em>Terminator</em>. On the poster, Skynet wakes up and decides humanity is the problem. Fair enough; some Monday mornings I’d agree. But watch the sequel. The same kind of machine is reprogrammed and sent back to protect a boy. Same metal, same face, opposite ending.</p><p>The machine was never the variable. The goal someone gave it was.</p><p>So “the AI will decide” doesn’t hold up. It decides what we tell it to optimise for. If it optimises for clicks, you get clicks. Whether you also get customers is a separate, and usually sadder, conversation.</p><p><em>The Matrix</em> is scarier, and not because of the machines. The real horror is people living inside a convincing picture that nobody ever checks. That’s exactly what an unchecked AI gives you. Ask it something it doesn’t know and it won’t say “no idea.” It will give you a fluent, confident, beautifully formatted answer, with a straight face.</p><p>The way I see it, the agents worth trusting are being built the other way round. They ask before they assume. They show where every number came from. They say plainly what they couldn’t verify. Less Agent Smith, more a good junior colleague who isn’t afraid to say “I’m not sure.”</p><p>There’s a quieter trap too, and it has nothing to do with killer robots: rules written loosely. A machine does exactly what you wrote, not what you meant.</p><p>Anyone who has written a prompt and got something technically correct and completely useless knows this feeling.</p><p>Which is why, from where I sit, guardrails are becoming the real design work. A well-built agent doesn’t run on vibes. It’s read-only on anything live, so a person makes every change that customers see. It works only in its own space. Every claim needs a source. Anything sensitive gets escalated, not acted on. And in the better designs I’ve seen, every report ends with one field the agent is not allowed to fill: the human verdict.</p><p>Inside guardrails like these, agents are brilliant at the repeatable, data-heavy work: audits, monitoring, finding gaps, first drafts, consistency checks, reports. Outside them, they drift. So my rule of thumb is simple. Automate what has guardrails. Anything that needs judgment goes through a person.</p><p>Since the developer asked, here’s what I’d tell anyone writing a skill for something like SEO. The skill file is the smallest part of the job. Everything around it decides whether it works.</p><p><strong>Write a role, not a prompt.</strong> Give it a mission, a manager it reports to, the data it reads, the jobs it runs and the format it reports in. Brief it like a new hire you actually want to succeed, not like a vending machine you want to get a samosa out of.</p><p><strong>Pick one source of truth per number.</strong> Search consoles, analytics, rank trackers and crawlers will happily disagree with each other. Decide upfront which one wins for each metric, and compare a tool only with its own history. Otherwise your agent will average three wrong numbers into one confident one.</p><p><strong>Give it a way of thinking, not a checklist.</strong> A checklist ticks boxes. A framework reasons: take stock of what exists, diagnose, decide what to do with each page, prescribe, then measure again. And a second loop for what to grow into next.</p><p><strong>Remember search isn’t just Google any more.</strong> Buyers ask ChatGPT, Gemini, Perplexity, Claude and Copilot. Many enterprise buyers live in Bing and Copilot all day because that’s what their laptop came with. A skill that only watches Google is watching half the room.</p><p><strong>Check what the page says, not just where it ranks.</strong> A page can sit happily at number one while describing a product you retired two years ago.</p><p><strong>Budget for upkeep.</strong> Tools change, connections break, search shifts. Agents don’t announce they’ve stopped working. They just go quiet, like a gym membership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*pC-3sFRHYF83WkiAReVtxA.png" /></figure><p>And then there’s <em>Enthiran</em>, which could only have been made in Tamil cinema. Dr Vaseegaran builds Chitti, the most capable robot in the world. Being a Rajinikanth film, the robot with super skills can’t stay out of the love track. Chitti gets an upgrade so he can understand human emotion, and promptly falls for his creator’s girlfriend. Then comes the jealousy, then the anger, and Chitti gets dismantled and thrown on a garbage dump. Then a rival scientist finds him and slips in a red chip, and the city gets a hundred angry Chittis.</p><p>It plays as a comedy, then a tragedy, then an action film. Underneath, it’s the most accurate AI film on this list. Nothing about Chitti’s intelligence ever changed. Two things did. He was given a capability nobody had designed guardrails for, and then someone changed what went into him. Most AI going wrong today will look a lot less like Skynet and a lot more like Chitti: a brilliant system, a new feature shipped without rules, and the wrong input at the wrong time.</p><p>In our world, most AI doesn’t even need a red chip. A vague brief does the job.</p><p>That red chip is context. AI is only as good as what you feed it, and the valuable context isn’t on the internet. It’s your first-party data, the customer conversations, the feedback nobody else has heard, the story you’re actually allowed to tell. I believe the most important thing any team will build in the next few years isn’t another agent. It’s a shared context layer that people and agents both draw from. And it’s never finished. You don’t upload it once and dust it off at the annual offsite. You keep <em>adding</em> to it: every conversation, every decision, every lesson. Stop adding, and everything built on top quietly goes stale.</p><p>And the screen itself is changing. For decades we’ve clicked, typed and scrolled our way through software. Increasingly, we’ll just talk to it, and the work that used to mean ten tabs and three spreadsheets will be one conversation. The personal letter you once agonised over? AI writes it in four seconds. Whether it should is still your call.</p><p>Finally, there’s <em>Interstellar</em>, where nobody rises up against anybody. TARS is a robot with adjustable settings, including one for how honest it should be and one for humour, which Cooper keeps turning down. (Some of my colleagues would like that setting on me.) The point is who sets the dial. It’s always a human. Keep that dial in mind. It comes back.</p><h3>Meanwhile, on the factory floor</h3><p>The films ran out at that point, so I went back further.</p><p>Regular readers will know I’ve told this story before, in my auto rickshaw piece. I’m telling it again because it keeps being true.</p><p>When electric motors first arrived, most factories did the obvious thing. They pulled out the steam engine, put a motor in its place, and kept everything else: the same long shafts, the same belts and pulleys, the same multi-storey floors. They had paid for those shafts, after all. For decades, productivity barely moved. The real gains came only when factories were rebuilt around the new power, with a motor on every machine and the floor laid out around the work. The economic historian Paul David wrote about this lag in a 1990 paper, <em>The Dynamo and the Computer</em>.</p><p>Look around today and you’ll see the same thing. A chatbot bolted onto a twenty-year-old process, and a slightly puzzled leadership team asking why the gains are small.</p><p>Fire. The steam engine. The petrol engine, then the electric one. Electricity itself. None of them asked permission, and none of them waited for everyone to feel ready.</p><blockquote>The smartphone is the one we lived through. Fifteen years ago it was a luxury. Today it’s how we pay, navigate, bank, learn, and argue in family WhatsApp groups. For some people it has been an actual lifesaver. Try leaving yours at home for a day and see how far you get before the panic sets in.</blockquote><p>AI is on the same road. The way we interact with screens will change, and so will the way work gets done.</p><p>Will people resist? Of course. Many won’t want to change how they work, won’t trust the output, and will quietly wonder if delegating to AI is the first step out of the door. That friction is real, and no memo from leadership will make it go away. But friction slows people down. It has never stopped the shift. It didn’t stop electricity either.</p><p>And the shift is already reaching team design. You know Amazon’s rule that a team should be small enough to feed with two pizzas? With AI, the two-pizza team could become a two-<em>slice</em> team. The second slice is there only for the truck factor: how many people you can lose before the work stops. Below that line, it’s solo play.</p><blockquote>In Chennai terms: what used to need a full meals, banana leaf and all, now needs one plate of idli, with a spare vada, just in case someone falls sick.</blockquote><p>So yes, I think adjacent roles will merge. Content and ads. Design and video. Analysis and reporting. One person with the right agents will do what a team used to.</p><p>But it’s trickier than it sounds, and the reason why is the whole point of this piece.</p><p>Because that brings the developer’s question back, sharper than before. If AI does the analysis, the drafts, the updates and the bird’s-eye view, and the team shrinks to two slices, what exactly is the human for?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*JIR31DVk5AbmWXMdqCo8nA.png" /></figure><h3>The ten percent</h3><p>Give AI a brief for a product video today and it will get you most of the way there. Script, storyboard, voiceover, cuts, captions, even background music that sounds suspiciously like every other product video. Call it ninety percent.</p><p>Now give the same brief to a designer with ten years behind her. She’ll use the same AI for the same ninety percent, probably faster than you. Then she’ll do the part no prompt asks for. She knows which shot the buyer will rewind. She knows when silence works better than music. She knows the one frame that makes the brand feel like itself, and the three that make it feel like a stock-footage library. The video comes out far richer, and almost all of that difference lives in the last ten percent.</p><p>I didn’t learn this from a designer, though. I learned it redesigning my own website.</p><p>It started, as these things do, with a head full of ideas and no clear picture. I described them to one AI, and it came back with a direction. Decent. Not quite me. So I took the idea to a second AI and asked it to actually build something. Better. Still not quite me. Then a third AI weighed in, and I found myself stitching pieces of one into another, keeping a layout from here, a feel from there, throwing out most of the rest.</p><p>At one point I had three AIs in the room, and none of them had ever met me.</p><p>They were all quick, all confident, and all happy to produce another version the moment I asked. What none of them could do was tell me which version was right. They didn’t know that I wanted the site to say “thought leader” quietly, without making it look like workshops are my day job. They didn’t know which parts of my story belong on the homepage and which belong on the About page. They didn’t know when something looked impressive but simply wasn’t me.</p><p>Eventually, one design made sense. Not because any single AI had produced it, but because I’d finally recognised it. I brought that design back, and AI did the heavy lifting of turning it into the clean, working HTML that’s live on the site today.</p><blockquote>Look at the split. The ideas, the options, the builds and the code: AI, across three tools, did the ninety. The ten percent was the part in between: knowing what I wanted to say, choosing, combining, rejecting, and recognising the right answer when it finally showed up.</blockquote><p>No prompt does that for you. It’s taste, and taste is just experience you can’t explain in a brief.</p><p>That ten percent is where the human is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8NwuIrlhXzU5G1rnCX3WoA.png" /></figure><p>It’s also why I keep thinking about the Wright brothers, because their story is the ten percent in its purest form.</p><p>In 1901, Wilbur and Orville were two bicycle makers from Dayton, Ohio, doing everything by the book. They designed their glider using the best published data of the day: Otto Lilienthal’s lift tables, and an air-pressure number from an 18th-century engineer, John Smeaton, that people had trusted for about 150 years. They followed the formula carefully. The glider produced only about a third of the lift it should have.</p><p>Wilbur was so discouraged that, by his own later account, he told Orville that man would not fly for fifty years. Then they did something no formula told them to. They stopped trusting the numbers and started checking them. First they mounted model wings on a bicycle wheel and pedalled through the streets of Dayton, which must have done wonders for their reputation in the neighbourhood. When that proved too crude, they built a wind tunnel out of what looked like a packing crate and tested around 200 wing shapes through the autumn of 1901. The surprise: Lilienthal’s tables were broadly fine. It was Smeaton’s 150-year-old number that was wrong.</p><p>Two years later, in December 1903, near Kitty Hawk, they flew.</p><blockquote>Now imagine them in the age of Claude. Orville types: “How do we build a flying machine?” Back comes a fluent, confident, beautifully formatted answer, built on everything humanity knew about flight in 1900, Smeaton’s number included, delivered with a straight face. Something like: heavier-than-air flight remains impractical, but here are five ways to build a better bicycle.</blockquote><p>I’m only half joking. AI would have given them the consensus, and the consensus was wrong. I genuinely wonder whether they’d have gone ahead. AI is extraordinary at what is already known. The step nobody has taken yet still needs someone stubborn enough to doubt the data and go and test it.</p><p>So the ten percent isn’t a leftover. It’s the experience, the judgment, the taste, the domain knowledge, and the nerve to keep going where the data runs out. It’s the human hand on TARS’s dial.</p><p>Which raises the question a nervous reader is already asking. If AI does the ninety percent, how does a junior ever earn the ten? The designer got her ten years by doing the ninety, badly at first, over and over.</p><p>My view is that the ninety stops being the training ground, and the testing becomes it. The Wright brothers didn’t earn their ten percent by reading more. They earned it in the wind tunnel, checking the published numbers against what actually happened.</p><blockquote>A junior today can do the same, faster than any generation before: use the hours AI gives back to sit closer to customers, own one outcome end to end, and challenge the machine’s answer instead of forwarding it. Every time someone fills in a human verdict, agrees, disagrees and finds out who was right, that’s one more rep. Ten years of reps might take three.</blockquote><p>The ones who will struggle aren’t the juniors. They’re the people of any age who use the time AI saves to do more of the ninety.</p><p>It comes at a price, though. To own the ten percent, you have to let go of the ninety. The research you were proud of doing by hand. The deck that took you a week. The report that mainly proved you’d been busy. Those were never really the job. They were the shafts and belts, and the floor is being rebuilt without them.</p><h3>The blank field</h3><p>Somewhere tonight, while most of us are asleep, an agent will finish its work. Pages checked. Gaps ranked. Fixes proposed. Every finding with its source, neatly formatted, no typos, no complaints about overtime.</p><p>And at the bottom of the report, one empty line.</p><p><em>Human verdict:</em></p><p>The Matrix didn’t end with the humans winning. It ended in a truce.</p><p>Ours might too. One report at a time, with someone pouring a coffee, reading it through, and deciding what goes on that line.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd086bc66ea3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Was Writing All Along. I Just Didn’t Call It That.]]></title>
            <link>https://medium.com/@tmraja2020/i-was-writing-all-along-i-just-didnt-call-it-that-add5f7ae0e5f?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/add5f7ae0e5f</guid>
            <category><![CDATA[stories]]></category>
            <category><![CDATA[creative-writing]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[short-story]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 03:51:01 GMT</pubDate>
            <atom:updated>2026-10-26T03:51:01.689Z</atom:updated>
            <content:encoded><![CDATA[<p>A holiday I never took, a grocery shop in Sattur, a few films, and a career in marketing.</p><p><strong>The first story I ever wrote was about a holiday I never went on.</strong></p><blockquote>It was a Tamil assignment in school. A five-mark question, maybe ten. Write a letter to a friend describing your holiday trip.</blockquote><p>I hadn’t gone anywhere that holiday. But I had read about a lot of places. So I went anyway.</p><p>Opposite our house in Sattur lived my cousin. And in his house was a bookshelf.</p><p>He bought books the way some people buy snacks. Tamil novels, short-story collections, magazines, whatever caught his eye. I would cross the street, settle in front of that shelf, and lose track of the afternoon.</p><p>Our family’s grocery shop had a library of its own, though nobody would have called it that. Old books and magazines came in by weight, sold as waste paper, to be torn up and folded into parcels for whatever a customer was taking home. Before a page became a parcel, there was a fair chance I had read it.</p><p>Not every book arrived whole. Some had no covers. Some stopped halfway through a chapter. I read them anyway.</p><p>English came later, and far less glamorously. It started with a grammar book. I was struggling with the language and wanted to understand how it worked, how a sentence held together, why it sounded right one way and wrong another.</p><blockquote>There is a film I think about when I remember that phase. In <em>The Terminal</em>, Tom Hanks plays Viktor Navorski, a man stuck inside a New York airport. He can’t enter the country and he can’t speak its language. So he buys a guidebook to New York twice, once in English and once in his own language, and sits comparing the two, page by page.I didn’t have two copies of anything.But I recognise that man. You learn from whatever happens to be in front of you, because that is what you have.</blockquote><p><strong>Then there was the government library in Sattur.</strong></p><p>I went almost every day. I didn’t sit and read there. I borrowed a book, took it home, and kept it on my desk. Whenever I felt like reading, I opened it. When I didn’t, it waited for me. The next day, I went back for another one.</p><p>Novels. Short stories. History. Philosophy. Books about places. Especially books about places. Which brings me back to that letter.</p><p>I wrote about the journey. The places. What I saw, what I ate, what struck me. I wrote it with the kind of confidence only someone who had never been there could manage, because I had a whole desk of books to borrow from.</p><blockquote>Mala Ma’am read it. Then she asked me to stand up and read it aloud to the class, so the others could use it as a reference. Nobody asked whether the trip was real.</blockquote><p>I didn’t have the word “fiction” for it yet. I just knew that something I had made up had worked. It had taken a classroom somewhere I had never been myself. It was a small moment. A few marks in a Tamil paper. It stayed with me much longer than the marks did.</p><p>I went on to write essays, dramas and stories in school. And then, as happens to most of us, life went in other directions.</p><p>Around 2007 and 2008, I had moved to Chennai and started working in internet marketing. Somewhere in between, I started a Tamil blog: anubaviraja.wordpress.com.</p><p>Over the next two and a half to three years, I wrote about a hundred posts.</p><p>Most of them were written for fun. Things that made me laugh. Things I noticed. Small incidents turned into stories, told the way I would tell them to a friend over tea. Colloquial, light, nothing that needed a dictionary.</p><p>That phase taught me something I still use. You don’t need to sound profound to land a point. A funny incident, told well, can carry an idea further than a page of explanation.</p><p>Then I became quieter. Work grew. Life grew. Writing became something I used to do.</p><p>At least, that’s what I thought.</p><p>I was writing all along. I just didn’t call it that. It had moved into my work.</p><p>For a long time I didn’t think of marketing as writing. Now I think it is the same job in a different medium. A story on a page asks a reader to see a place they have never been. A good campaign asks a buyer to do the same thing: picture something that doesn’t exist for them yet, and believe it enough to walk towards it.</p><p>That holiday letter, really. Cinema is where I learned the most about how that works.</p><p><em>The Godfather</em> opens at a wedding. It is long and crowded and noisy, and by the end of it you know almost everyone who matters, who owes whom, and where the power sits. The film keeps moving through gatherings like that. A wedding near the start. A baptism near the end. Each gathering moves the story forward.</p><p>I think about that whenever someone calls our events stunts.</p><p>Over the years, our work has included a helicopter experience for business leaders in Dubai, supercar experiences in Houston, and an aerial banner over OTC. From the outside, those can look like spectacle. I have never seen them that way. Each one is a scene. Who is in the room. What they see. What they talk about on the way back. What they still remember a month later.</p><p>When the Dubai helicopter experience worked, it wasn’t really about the helicopter. It was CIOs, customers and journalists seeing their own city from above, many of them for the first time, and then talking about it with each other.</p><p>And when any of our events drew a small crowd, we treated it the way a director treats a scene that didn’t land. We listened to local advice, changed the timing, fixed the outreach, and shot it again.</p><p>Most B2B marketing makes the product the hero and leaves the villain vague. When we started making comic books as marketing material for CIOs, the villain had to be real. The project that stalls. The system nobody trusts. The AI initiative that never quite reaches the business. If the reader doesn’t recognise the problem, they won’t care much about the answer.</p><p>And <em>The Matrix</em> reminds me to trust the audience. We discover that world as Neo does, a piece at a time. The film doesn’t stop to explain everything up front, and we lean in because of it.</p><p>I have used cinema to explain marketing more times than I can count. <em>Money Heist</em> once became an entire session on account-based marketing.</p><p>None of this felt like writing while I was doing it.</p><p>It was the same instinct as that letter. Take someone somewhere they haven’t been, and make it real enough that they come along.</p><p>Over the past five years, writing found its way back into my everyday life in a more open way.</p><p>I started posting on LinkedIn almost every day. Some posts were long. Most were short notes. A single observation, one useful thought, something I had learned that week. Being regular turned out to matter more than being long.</p><p>Somewhere along the way, I started calling myself a writer. Quietly at first. It took a while before I could say it without looking around to check whether anyone minded.</p><p>But there was one thing I still hadn’t done.</p><p>For nearly two decades, I had wanted to write a Tamil short-story collection.</p><p>I had the stories. I had the places and the people. I knew the streets they would walk down. What I didn’t have was the time, or the discipline, or a clear way to begin. The intention was always there. The execution kept getting postponed.</p><p><em>The Pursuit of Happyness</em> is a film I keep returning to for one reason. We live with Chris Gardner through every setback. The scanners he can’t sell. The nights he and his son have nowhere to sleep. The unpaid internship he takes anyway. By the time the good news finally comes, it hits hard, because we have waited for it with him. The film makes you earn the ending.</p><p>My wait was nothing like his. Nobody was sleeping in a station in my story. It was just postponement, the ordinary kind most of us know well. But it was long. And it made the ending feel earned.</p><p>The beginning, when it finally came, came in a hotel room in Houston.</p><p>I had been looking forward to visiting Hermann Park. I was getting ready to leave when I saw the forecast. It wasn’t good. Then it started raining. I thought I would sit for a while and wait it out. So I sat. I scrolled through things that didn’t matter. I did nothing in particular. Eventually I found myself at the window, looking out at the city. The industry. The scale of it.</p><p>Houston had been hot, the kind of heat I knew well from Sattur. And then the weather turned, and suddenly it was cold. I started drawing parallels. My town and this city. The heat. The chimneys. What it feels like when a place that has always been hot suddenly changes.</p><p>And this time, I didn’t let the thought go. I pushed it through. Hermann Park would have to wait.</p><p>What followed was two weeks of focused work. AI was part of how I did it, and I think the best way to describe its role is the way a film is made. A director doesn’t hold the camera, set the lights or cut the reel. But every frame is his call. The stories were mine. The characters were mine. Sattur and the Vaippar were mine. AI was the crew that let me start shooting without waiting for a studio to give me the go-ahead. Two weeks for the first draft. Three to four months of reviews, revisions and proofs to turn it into a book.</p><p>The result is <a href="http://www.tmraja.com/books">வைப்பாற்றங்கரையினிலே</a> (<em>Vaippatrankaraiyinilay</em>), ten Tamil short stories set in Sattur, on the banks of the Vaippar. The town I left. The town I never quite stopped writing about.</p><p>The pre-orders, the messages from readers, the people who now introduce me as an author. I am still getting used to all of it.</p><figure><img alt="Raja T M ’s First Tamil Short Stories Book" src="https://cdn-images-1.medium.com/max/1024/1*mNCvtBfQovcR6dXjIuzcVA.png" /></figure><p>My wife reads my stories before anyone else does. Her verdict was honest. My stories tend to preach. Except the funny ones.</p><p>She is right. And that is where <em>The Dark Knight</em> comes back. A story where the hero always knows the answer isn’t really a story. It is a speech. The other side needs room. The reader needs room.</p><p>I am trying to give them that room in my second collection, set in Chennai between 2005 and 2015. It’s the city and the era I lived through, and the one I have been wanting to capture for a long time.</p><p>We’ll see whether she agrees. 😊</p><p>There is a reason <em>Forrest Gump</em> works the way it does. Forrest tells his life one episode at a time, sitting on a bench, to whoever happens to sit down beside him. None of the episodes seem connected while he is living them. They only make sense when you hear them together.</p><p><strong>When I look back, mine look a bit like that.</strong></p><p>A bookshelf across the street. Pages waiting to become parcels. A grammar book. A library book left on a desk. A letter about a holiday I never took. A hundred blog posts. A helicopter over Dubai. A comic book for a CIO. A rainy afternoon in a Houston hotel room.</p><p>At the time, they felt like different things. Now they feel like the same thing, told in different mediums.</p><p>So why do I write?</p><blockquote>Because writing is how I find out what I actually think. An idea that feels clear in my head often falls apart on the page, and putting it back together is where the real thinking happens.</blockquote><p>Because a story lets me take someone somewhere. That is what I tried to do in that school letter, in every campaign since, and in every story in the book.</p><p>And because, after nearly two decades of telling myself I would do it someday, I finally did.</p><p>Somewhere, someday, a copy of my book will probably end up sold by weight. Torn up, folded into a parcel, handed across a counter in some small town. I’m fine with that.</p><ul><li>Someone might read a page before it becomes a parcel.</li><li>That’s how I found most of my books.</li><li>For years, I wanted to become an author.</li><li>The boy who wrote about a holiday he never took would be pleased to know this.</li></ul><p><strong>This time, I actually went.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=add5f7ae0e5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Still Wear Formals]]></title>
            <link>https://culture.kissflow.com/i-still-wear-formals-cc1e24b3ef55?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc1e24b3ef55</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[workplace]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 15:28:56 GMT</pubDate>
            <atom:updated>2026-10-09T02:26:17.910Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Five years at Kissflow, and why I keep thinking about The Intern.</em></p><p>When I joined Kissflow five years ago, one of the first things I noticed was the T-shirts and casuals.</p><p>I have always worn formals to the office. That was familiar to me. So were quieter workplaces. Here, there was table tennis, a lively cafeteria, and people comfortably moving between work, conversations, and fun.</p><p>And there I was, in formals, taking it all in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*He7ggmDKY4JE-mhDVegPDQ.jpeg" /></figure><p>When I look back now, I find myself thinking about Robert De Niro in <em>The Intern</em>. Ben Whittaker walking into that young company with his suit, his briefcase, and years of experience that nobody around him quite knows what to do with yet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9HzXS311OZUqNQcEPmUU4Q.jpeg" /></figure><p>Before anyone gets carried away, the resemblance begins with the clothes.</p><p>But the longer I think about it, the more I recognise that feeling. Walking into an unfamiliar place with a familiar version of yourself. Knowing that you have something to contribute, while still having plenty to figure out.</p><p>I had spent twelve long years in my previous organisation.</p><blockquote>Leaving after that much time wasn’t an easy decision. You build relationships, routines, and confidence. You know whom to call when something gets stuck. People know what you are good at. Over time, the familiarity becomes part of how you see yourself.</blockquote><p>Then you decide to leave, and all that familiarity has to be built again.</p><p><strong>But I was curious.</strong></p><p>I wanted to understand what it really takes to market a SaaS product. I had spent years in services marketing. I wanted to see how much of what I knew would travel with me, and what this next phase would ask me to learn.</p><p><strong>An opportunity came my way at Kissflow.</strong></p><p>I had been following Suresh Sambandam for a couple of years before that. I liked the clarity in his thinking, the way he articulated facts, and the way he looked at businesses and people. Before I knew the organisation from the inside, I already associated it with that clarity of thought.</p><p>So I made the move. And found myself in that office, in my formals.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZU3Xban0Y6A%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZU3Xban0Y6A&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZU3Xban0Y6A%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fba931af6c96581a3de022001bd4fe49/href">https://medium.com/media/fba931af6c96581a3de022001bd4fe49/href</a></iframe><p>In the film, Ben has tried to keep himself occupied in retirement, but he misses having somewhere to go and something to contribute. He wants to be challenged again. Joining the company gives him that opportunity, along with a fair amount of learning.</p><p>There is something I like about the way he accepts help. He can bring years of experience to work and still need someone to explain the technology.</p><p><strong>Both things can be true.</strong></p><p>I felt that in my own way at Kissflow. I had experience in marketing, but I was entering a different business. I had to understand the product, the market, the people, and how the work happened here. I could contribute in some conversations and ask basic questions in others. And people gave me the space to do both. There were colleagues willing to explain what they knew, share how they approached something, and help me understand the context.</p><p>That willingness mattered. After spending so many years in one organisation, being new again becomes easier when the people around you are generous with what they know.</p><p><strong>Then came the first event I was responsible for.</strong></p><p>That was where I found an early opportunity to make my experience useful. I was able to crack the events and engagement piece. The work was appreciated, and it led to opportunities to take on more.</p><p>In <em>The Intern</em>, Ben clears the cluttered desk that has been bothering Jules. She notices. Something useful has been done, and she begins to see what he brings. That first event was my version of the table.</p><p><em>It gave people something to judge me by. They could see how I approached the work and what I could contribute.</em></p><p>Then came a bigger responsibility. Apparently, doing the first one well had consequences.</p><p>One thing led to another. I solved problems, learned from the people around me, and took on more. Over time, I became a go-to person for a wider range of things.</p><p>My earlier experience was finding new applications. I was learning how to carry it from services marketing into SaaS marketing, and how to change my approach when the context called for it. The trust grew gradually. So did my confidence.</p><p>And with that confidence came a willingness to suggest ideas that I might once have spent much longer thinking about before saying out loud. Some of them were quite crazy.</p><p>Which is where my mind goes back to <em>The Intern</em>, and the mission to Jules’s mother’s house. An email has gone to the wrong person, and suddenly Ben and his younger colleagues are in the middle of an increasingly chaotic attempt to deal with it. By then, the man in the suit is fully involved. I recognise that progression too.</p><p>Somewhere between joining Kissflow and completing five years, our work came to include:</p><ul><li>Helicopter experiences for business leaders in Dubai.</li><li>Supercar experiences in Houston.</li><li>An aerial banner and a branded truck during OTC.</li><li>Filter coffee and Chennai-themed dabra sets in Madrid.</li><li>Live caricatures in Frankfurt.</li><li>Comic books as B2B marketing material.</li><li>Dungeons &amp; Dragons and custom hot-sauce kits for a CIO gathering.</li></ul><p>That is quite a distance from the first event.</p><p>The Dubai helicopter experience is one I remember with particular warmth. We brought CIOs, customers, prospects, and journalists together for conversations, followed by an experience over the city that many were having for the first time.</p><p><strong>The campaign went on to win the B2B Momentum Award.</strong></p><blockquote>I was happy about the recognition. But I also knew how many people were inside that story. Every detail, every handoff, every late message, every person working through their part so the whole thing could happen.</blockquote><p>It takes a lot of people to make a crazy idea look well organised. I have been fortunate to work with those people. We have also had experiences that taught us to go back and change things. The idea alone wasn’t enough. We had to learn how to make it work in that market. That process has changed me.</p><p>I have become more willing to experiment, accept when something hasn’t worked, and try again with what I have learned. I am less afraid of defeat than I was before. And that gives you room to make bolder decisions. A lot of that room came from the people around me. From my own team, who have worked through so many ideas with me and made them better.</p><p>When I arrived, I noticed the office. Over time, I understood more about the people in it.</p><ul><li>People who shared their knowledge freely.</li><li>People who gave you space to learn afresh, regardless of what you had done before.</li><li>People who challenged your thinking.</li><li>People who were willing to teach.</li><li>People who trusted you with more responsibility.</li><li>People who helped you carry an idea through the difficult parts of making it happen.</li></ul><p>There is a lot you learn simply by watching how people behave.</p><p>How they respond when something goes wrong. Whether they make time for someone who needs help. How they disagree. How they acknowledge another person’s contribution. You spend enough time around those things, and they begin to influence how you work too.</p><p>Somewhere along the way, I found myself helping create more of the experiences I had first encountered as a newcomer.</p><p>Through Marketing Thinnai, we brought the marketing team together to discuss the work, share challenges, learn, and celebrate each other. There were team updates, games, and conversations about priorities and what we should do differently. There were Marketing Expos where teams could show others what they did. Offsites where strategy, activities, and fun could sit comfortably together.</p><p>I had walked into Kissflow and noticed people having fun. Now I was helping organise the games.</p><p><strong>Still in formals. Some habits take longer.</strong></p><p>One part of Marketing Thinnai that matters to me is the Gratitude Wall. A place to stop and acknowledge someone who helped you. Work moves quickly. We finish one thing and start the next. The event is over, the campaign is out, and another deadline is waiting. It is easy to move on without telling someone that their contribution mattered.</p><p>The colleague who made time. The person who helped you finish. The team member who quietly solved a problem before it became everyone else’s problem. I have become more aware of those contributions over these years. And more willing to say thank you.</p><p>I have also had more opportunities to speak, share, mentor, and give back what I have learned. My own interests began finding their way into that work.</p><p>Cinema became a way to explain marketing. <em>Money Heist</em> became an ABM masterclass. Cricket became part of the Marketing Premier League. Games and cards became ways to get people talking about priorities and trade-offs. Things I enjoyed were becoming useful to other people. That has been deeply satisfying.</p><p>I always told stories. But somewhere along the way, I learned how to make them matter. To help someone understand an idea, participate in a discussion, or return to their work with a different way of looking at a problem. And while doing that, I kept learning.</p><p>Through the Kissflow Leadership Program. Through colleagues. Through the communities where I shared what I knew and came back with something I hadn’t considered before.</p><p>Technology kept giving me more reasons to stay curious. Over these five years, so much has changed. With AI, I have found myself building games, trying tools, and bringing ideas to life in ways I wouldn’t have imagined when I joined. I came here wanting to understand SaaS marketing.</p><p>The learning has spread into many parts of my life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EMfcM-9CBuERjbhraa4Ygg.jpeg" /></figure><p>When I compare the 2021 version of me with who I am today, I can see it.</p><ul><li>I have become a better storyteller.</li><li>I have developed more of an abundance mindset.</li><li>I have learned to see the bigger picture.</li><li>I value people’s time, effort, and contribution much more deeply.</li><li>I have become more willing to share what I know.</li><li>I have become more receptive to what others have to say and, more importantly, to what they value.</li><li>I have learned to stay calmer and more confident.</li><li>I have become less afraid of failure.</li></ul><p>None of these changes happened all at once. They came through the work, the experiments, the conversations, and the people who stayed generous with me while I was learning. Over time, speaking, sharing, mentoring, and giving back stop being activities you occasionally do. They become part of who you are. And that is the part of these five years I keep coming back to.</p><p>When I joined, people made room for me to learn and contribute. Today, I have more opportunities to do that for someone else. To share what I know, help them think through an idea, or give them the encouragement that someone once gave me.</p><p>I can see something of Kissflow’s culture in that change. So this is another gratitude post. A longer one this time.</p><p>And I want that gratitude to reach everyone who has been part of these five years.</p><ul><li>The person at reception who smiles and welcomes me into the office.</li><li>The colleagues who smile as we walk past each other.</li><li>The people who interviewed me.</li><li>The people who onboarded me.</li><li>The people who trained me.</li><li>The people who challenged me.</li><li>The people who trusted me with bigger responsibilities.</li><li>And everyone who gave me the opportunity to scale my work and create a larger impact.</li></ul><p>I have written about the culture at Kissflow many times. And yes, I probably will again. Because when something shapes you this deeply, you don’t really get tired of talking about it. Five years ago, I walked into a place that felt different and wondered what I would learn there.</p><p>Today, some of the things that made it feel different are things I help create. The conversations. The games. The sharing. The encouragement to try something. That is a change I couldn’t have put into words when I joined.</p><blockquote>I still wear formals to the office.</blockquote><blockquote>But I feel very much part of the adventure now.</blockquote><blockquote>Five years done.</blockquote><p>I’ll keep learning. Keep moving forward. And hopefully, keep helping someone else find their place along the way.</p><p><strong>Grateful. Truly.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc1e24b3ef55" width="1" height="1" alt=""><hr><p><a href="https://culture.kissflow.com/i-still-wear-formals-cc1e24b3ef55">I Still Wear Formals</a> was originally published in <a href="https://culture.kissflow.com/">Kissflow Culture | Explore Our Butterfly Effect</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Was Just Trying to Get Home — The Odyssey]]></title>
            <link>https://medium.com/@tmraja2020/i-was-just-trying-to-get-home-the-odyssey-6aee85d5b749?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/6aee85d5b749</guid>
            <category><![CDATA[flight]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[family]]></category>
            <category><![CDATA[home]]></category>
            <category><![CDATA[odyssey]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Mon, 10 Aug 2026 04:21:01 GMT</pubDate>
            <atom:updated>2026-08-10T04:21:01.321Z</atom:updated>
            <content:encoded><![CDATA[<h3>I’d wanted to watch Christopher Nolan’s <em>The Odyssey</em> in 70mm IMAX specifically, not just at any theatre. I’d checked. There isn’t a single 70mm screening anywhere in India. So rather than wait and watch a smaller version back home, I decided I’d rather see it there, in the format it was actually built for.</h3><p>I’ve followed Nolan for years. <em>The Prestige</em>. <em>Memento</em>. <em>Oppenheimer</em>. His treatment of Batman in the Dark Knight trilogy. I wanted to see how he’d handle a historical epic the way he’s handled a magician’s rivalry or a physicist’s unraveling. It didn’t disappoint.</p><p>The theatre itself was its own quiet shock. A full recliner, more couch than seat. I was in the second row from the front, and I braced for the cramped, craning-your-neck feeling you get that close to a screen back home. It never came. The angles were placed so well I didn’t feel like I was in the front row at all. In Indian cinemas you shuffle past a dozen knees to reach your seat, careful not to disturb anyone. Here, people simply came in, settled down, and went quiet. No interval either. Almost three hours in one unbroken stretch. At the end, before anyone stood up to leave, the whole room clapped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*W5XE96qO6AM9Lz38DVFJvg.jpeg" /></figure><p>I sat there watching Matt Damon’s Odysseus fight his way home, in a theatre that watches movies differently than I do, and somewhere in that unbroken three hours, I realized something strangely personal.</p><p>I had just lived through my own, much less heroic, version of the same story.</p><h3>The storm before anything else</h3><p>Nolan doesn’t tell this story in order, and neither, it turns out, does my memory of it.</p><p>On screen, the gods keep working against Odysseus before he’s done anything to deserve it. Storms. Delay. Interference he didn’t ask for and can’t argue with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52dzJvvXJ204JUDPInsNBw.png" /></figure><p>I had been in the US on an official trip. After close to two weeks in Houston, it was time to go home. My original ticket was simple: Houston to Frankfurt to Chennai. Two flights. Then, two days before I was supposed to leave, my flight was cancelled.</p><p><strong>Okay. Things happen.</strong></p><p>Here’s where I have to be honest about my own part in what came next. I refused to let go of British Airways through Heathrow. I tried the booking five times, maybe ten. It never went through, and every failed attempt made me more convinced it had to be the right way, not less. That’s the same flaw that runs underneath Odysseus for the whole poem, long before this film even starts: his pride, his insistence on his own way, even while the world keeps telling him plainly that it isn’t working.</p><p>I kept trying anyway. It took longer than it should have for me to actually hear what the universe was saying.</p><p>When I finally let it go, the route that got me home was almost absurd. Houston to San Francisco to Singapore to Chennai. Three flights instead of two, leaving almost twenty hours earlier than planned, thirty-six hours of airports and aircraft instead of a clean two-flight journey.</p><p>But there wasn’t really another option. So I said to myself: fine, let’s go.</p><h3>The cave, and the question of who you actually are</h3><p>The Cyclops sequence is in Nolan’s film, and it’s exactly the shape you’d expect. Trapped. Cornered. Needing to out-think your way out rather than fight your way out.</p><p>That was my TSA counter.</p><p>My flight from Houston was at 5 AM. I’d arrived at the airport four hours early, which should have made everything comfortable. It didn’t. A spelling mistake on my boarding pass needed fixing first, and the counter that could fix it didn’t open until past four. By the time it was corrected, my cushion was gone.</p><p>Then it turned into last-minute drama anyway, despite the four-hour head start. I was running, literally running, between the counter and the checkpoint, because the gate was now less than thirty minutes out. Somewhere in that sprint, two staff members started arguing over me, one insisting I’d have to be brought back through the check counter if I came back again, the other asking why he’d ever need to come back at all. I stood between them, clueless about what either of them actually meant, while a small procedural disagreement between two strangers threatened to decide whether I made my flight.</p><p>Underneath the argument was the real problem. My name was correct. My date of birth wasn’t. The way dates get recorded in the US had created a mismatch with my passport. So there I was, caught between two people mid-argument, trying to convince a system that I was, in fact, myself.</p><p>This part isn’t in Nolan’s cut, as far as I could tell, but it’s in the older text, and I already knew it before I sat in that theatre. Homecoming, in the original poem, isn’t just about arriving. Odysseus has to prove who he is, first to an old nurse who recognizes a childhood scar, then to Penelope herself, who tests him with something only her real husband would know. Coming home was never just a matter of travel. It was a matter of being believed.</p><p>It got fixed. I got through. I reached the gate with maybe five or ten minutes to spare.</p><p>First obstacle cleared. Keep moving.</p><h3>Losing control on purpose</h3><p>I reached San Francisco, then boarded a seventeen-hour flight to Singapore that decided, halfway through boarding, not to move. A technical issue. Power off, power on, repeat. Ninety minutes of that.</p><p>I said everything there was to say to the people around me, and none of it changed anything. So at some point I stopped trying to change it. I took out my headphones and put on music from the 2000s, the songs I grew up on as a teenager, the ones that are always somewhere in my head if I go looking. I played them again and again, and somewhere in there I said to myself: this is going beyond my control, what more can I actually do about it. And I let it go.</p><p>The plane flew, almost two hours late. Seventeen hours after that, I reached Singapore.</p><p>I thought the difficult part was over. It wasn’t.</p><h3>The island that doesn’t feel like a trap until it is</h3><p>Nolan’s film spends real time on what’s happening back in Ithaca while Odysseus is stuck god knows where. Antinous and the rest circling his house, treating his absence as an opportunity instead of a tragedy. Telemachus, still a boy when his father left, growing into the gap his father’s absence created.</p><p>I don’t have suitors. I have two sons.</p><p>By the time I landed in Singapore, my connecting flight had already left, two and a half hours late meeting a flight scheduled two and a half hours after arrival. So I was stranded for the night, on Calypso’s island, if you want to call it that.</p><p>Except it really did feel like her version of a trap, not Poseidon’s. Changi is, by a wide margin, the most beautiful airport I’ve ever stood in. There’s a butterfly garden. There’s a waterfall you can see from a distance. It didn’t feel like an airport at all, more like walking into a tourist attraction, with its own photo spots and quiet, gleaming calm. I didn’t have a Singapore visa, though, so I couldn’t actually cross into the part of the terminal where the waterfall was. I’d have had to exit and re-enter, and I kept thinking about what would happen if something went wrong out there and I got stuck a second time, on top of the first. So I stood just outside the beautiful part of a beautiful place, close enough to see it, not allowed to walk into it, worried that even trying might cost me the rest of the way home.</p><p>A locked door inside the locked door.</p><p>My sons had been anxious the night before, wanting to see me before school, asking why I wasn’t coming. So I video-called them from the terminal and walked them through it with my phone, panning across the lights and the greenery. They went quiet with wonder, the way kids do when something looks nothing like what they expected an airport to be. It calmed them, a little, hearing my voice and seeing the place instead of just being told to wait.</p><p>And at some point, standing in that beautiful, wrong place, I said to myself: irrespective of all the delays, I’m going home. Maybe it takes more time. Let me wait.</p><p>That was the moment, as much as anything on the flight itself, that the trip actually turned.</p><h3>Home, without the orchestra</h3><p>The next morning I flew the final leg. Chennai. Home, after what felt like an entire tour of the planet.</p><p>My bags took another hour to arrive, and I stood there thinking about the things I’d bought for my kids, hoping they hadn’t been lost somewhere over the Pacific. They came. All of them. I picked up three bags, walked the long stretch from baggage claim to the parking area, failed to book a cab through two different apps, and finally got one forty-five minutes later. Landed around 7 AM. Reached home around 10.</p><p>The house was quiet. My sons were already at school. My mother opened the door and asked why it had taken me so long to come back. My wife didn’t say much, just, finally, you made it.</p><p>No orchestra. No epic soundtrack. No cinematic slow motion.</p><p>I got into my own bed, the one I’d missed for two weeks straight, and just lay there for a while.</p><p>I don’t know exactly how Nolan stages Odysseus’s actual return, whether it matches the older, deliberately unglamorous version I already knew, where he arrives disguised as a beggar and tests who’s still loyal before he’ll even say who he is. No trumpets in that version either. But I recognized the note regardless. Getting home is rarely as cinematic as the getting-there was hard.</p><h3>What I think it actually means</h3><p>Watching a film that refuses to tell its story in order, right after living a week that refused to go in order too, I kept landing on the same thought. The route doesn’t matter as much as the destination. You can start in the right direction and still end up somewhere completely unexpected. You can have a plan, watch it disappear, find another one, watch that fail too.</p><p>You can be delayed, redirected, stopped, sent backwards, stranded somewhere beautiful, and still think: I need to get home.</p><blockquote>Maybe the lesson isn’t to obsess over the route. Maybe it’s to hold the destination clearly enough that everything else, the airline, the booking, the order of the connections, stays negotiable. I didn’t need the original ticket. I needed to land in Chennai. That was the only part that couldn’t change.</blockquote><p>Sometimes, that’s enough.</p><p>I flew east, then west, then crossed the Pacific, then came all the way back, in probably the least efficient route imaginable. But I got there. Sitting in that theatre afterward, thinking back on a story that also refused to move in a straight line, the coincidence felt almost too perfect. He had one promise: he was going home. I had one objective: I was going home. Different journeys, different stakes, different worlds. But maybe the same instinct underneath.</p><p>When everything around you says wait, turn back, stop, stay here, try again tomorrow, sometimes the only thing you can do is keep moving.</p><p>Because home isn’t always a place.</p><p><strong>Sometimes, home is the promise you refuse to break.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6aee85d5b749" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Needs Its Own Auto Rickshaw: Part II]]></title>
            <link>https://culture.kissflow.com/ai-needs-its-own-auto-rickshaw-part-ii-60c644c77216?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/60c644c77216</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 03:24:37 GMT</pubDate>
            <atom:updated>2026-08-07T03:24:37.128Z</atom:updated>
            <content:encoded><![CDATA[<p><em>It’s not your software that needs to change. It’s your thinking.</em></p><p>A year ago, I wrote an article called “<a href="https://medium.com/@tmraja2020/ai-needs-its-own-auto-rickshaw-90108fd610fd">AI Needs Its Own Auto Rickshaw</a>.” The idea was simple: you don’t build an auto rickshaw by taking a bicycle rickshaw and bolting on an engine. You redesign the entire vehicle, because the engine changes everything: its weight, balance, steering, brakes, purpose, and the way people use it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vL54eoaDA7iuEOvV2EbwVw.png" /></figure><p>My argument then was that AI isn’t another feature to add to existing software. It’s a new primitive that demands software be reimagined from first principles.</p><p>One year later, I realize I was only half right.</p><p>The bigger redesign isn’t software.</p><p>It’s us.</p><h3>The Great AI Mistake</h3><p>Over the past year, I’ve had hundreds of conversations with founders, developers, marketers, designers, and executives. Almost everyone says they’re “using AI.” Then they show me what they’re actually doing. They paste a document into ChatGPT. They ask AI to rewrite an email. They generate a LinkedIn post. They summarize a meeting.</p><blockquote>They call it AI transformation.</blockquote><p>That’s like buying a Ferrari and using it to charge your phone.</p><p>The technology isn’t being underutilized because it isn’t capable. It’s being underutilized because we’re asking it yesterday’s questions. We have an engine that can build, and we’re using it as spell check.</p><h3>Garbage In. Garbage Out. Still True.</h3><p>Developers are among the best examples of this. Many proudly say they’re coding with AI. What they actually do is copy-paste 2,000 lines of poorly structured code into an LLM and ask, “Can you optimize this?” When the result isn’t impressive, they conclude AI isn’t ready.</p><p>But AI didn’t fail. The process did.</p><blockquote>Garbage in. Garbage out.</blockquote><p>The best AI developers I know don’t ask AI to fix code. They ask AI to redesign the architecture. They don’t ask, “Can you complete this function?” They ask, “If we were building this today, would this function even exist?”</p><p>That’s a completely different conversation.</p><h3>You Can’t Renovate a House That Shouldn’t Exist</h3><p>Imagine inheriting a hundred-year-old house. The plumbing leaks. The wiring is dangerous. The rooms don’t fit modern life. Instead of rebuilding it, you paint the walls, install smart lights, add Alexa, replace the doorbell.</p><p>Congratulations. You now own a smart old house.</p><p>Most organizations are doing exactly this with AI. They’re adding AI features to workflows that should have disappeared months ago.</p><p>The workflow is the problem. Not the missing AI button.</p><h3>We Keep Adding Engines to Bullock Carts</h3><p>History keeps repeating itself. When electricity arrived, factories didn’t become productive because they swapped steam engines for electric motors. They became productive because they redesigned the entire factory floor. When smartphones arrived, Apple didn’t build a better Nokia. They eliminated the keyboard. When Netflix won, it wasn’t because DVDs became digital. It was because streaming changed the business model. When digital cameras emerged, Kodak didn’t lose because it lacked the technology. It lost because it protected a business model built for film.</p><blockquote>Every technological shift punishes optimization. It rewards redesign.</blockquote><p>AI is no different.</p><h3>The SEO Playbook Is Already a Museum Piece</h3><p>For years, marketers mastered SEO: keywords, backlinks, meta descriptions, page rankings, ten blue links. Entire careers were built around this playbook. Then AI changed search. Today, people increasingly ask questions instead of typing keywords. They expect answers, not links. The “ten blue links” era is quietly fading into “one synthesized answer.”</p><p>This doesn’t mean search disappears. It means the playbook changes.</p><p>The marketer who keeps optimizing yesterday’s ranking factors is like a sailor getting better at reading maps after GPS has arrived. The skill isn’t wrong. It’s simply no longer the bottleneck.</p><h3>The Paid Media Playbook Is Changing Too</h3><p>The same unlearning has to happen in paid marketing, and most teams haven’t started.</p><p>Google still holds roughly 93 percent of search. But a growing share of those searches now end in a zero-click answer: the person gets what they need without ever landing on a page, let alone an ad. LinkedIn has become the sharper edge for B2B targeting. Meta still does its job. None of that is really the shift worth noticing.</p><p>The real shift is in how the work itself gets done. Building a campaign (segmenting an audience, drafting ad sets, testing creative) used to require a specialist, sometimes several. The connectors to do most of that directly through AI already exist. You can prompt against your ad platform and build the thing, not just draft copy for someone else to upload later.</p><p>And yet the most common mistake I see here looks exactly like the mid-level-user mistake from earlier: people export their data into Excel, hand that spreadsheet to AI, and ask it to “analyze this,” rather than connecting AI directly to the platform through the MCP connector that’s already sitting there, unused. It’s a manual workaround for a job that no longer needs one.</p><p>Give the monotonous part (the pulling, the formatting, the first-pass analysis) to the tools. That was never the interesting part of the work anyway. The creative judgment, the willingness to try the thing nobody’s tried yet, the push forward: that’s still entirely on the human. The old mindset of solving a bigger problem by adding more people to it is no longer the default answer. It might not be an answer at all.</p><h3>AI Doesn’t Replace Specialists. It Replaces Friction.</h3><p>This is where many people get uncomfortable. Every new technology removes work. AI removes coordination work, documentation work, formatting work, searching work, context-switching work. It doesn’t eliminate creativity. It amplifies it.</p><blockquote>A marketer no longer needs five different specialists to produce one campaign. A developer no longer waits days to prototype an idea. A founder no longer needs an entire agency to validate a concept.</blockquote><p>The question shifts from “who can do this?” to “what can we build now that nobody could build before?”</p><p>That’s an entirely different organization.</p><h3>There’s No Going Back</h3><p>There was a world before smartphones. Almost nobody lives in it anymore. It’s not impossible (<strong>Christopher Nolan famously still doesn’t carry one</strong>), but it’s rare enough that we treat it as a personality trait, not a lifestyle choice. Once a technology gets absorbed into how people actually live and work, the door doesn’t stay open behind you.</p><p>It’s the oldest choice in the modern imagination: the pill that shows you what’s actually happening. Once you take it, you don’t get to unsee it. Neo doesn’t get to go back to the machine’s comfortable version of 1999 just because reality turned out to be more work than the simulation.</p><p>AI is already at that point.</p><p>Which means the real question was never “should I use AI.” Everyone already has, or will. The real question is what happens once you’re in it, because being in the race isn’t the advantage. The advantage belongs to the small number of people pulling far ahead of it, while almost everyone else clusters in roughly the same place, using roughly the same sliver of what’s actually available.</p><h3>The Four Kinds of AI Users</h3><p>I’d put almost everyone using AI today into one of four groups.</p><p><strong>Light users</strong> reach for it occasionally: drafting an email, writing a social post, smoothing out a paragraph. Useful. Not transformative.</p><p><strong>Mid-level users</strong> are in it every day, and this is where most of the damage happens, not because they’re careless, but because they’re using a conversation tool like a vending machine. They copy-paste two thousand lines of code and ask AI to fix it. They dump a half-built campaign into a Word document and ask AI to patch it. They arrive with the answer already decided and just want AI to execute it, instead of asking what it would actually suggest.</p><p>That’s the mistake. AI isn’t a vending machine. It’s a conversation.</p><p>The right way looks completely different: bring in the research, ask what the best practice actually is, feed that back in, let it ask you questions, keep building together. I don’t write an article by handing AI a one-line prompt and waiting. I write it the way I’d write it with a sharp collaborator in the room: research together, argue a little, revise together. The same discipline applies if you’re building an AI agent to do real work for you: you don’t get to hand it a vague instruction and hope. You have to define the job with real precision, the same way you’d brief a new hire you actually wanted to succeed.</p><p>This is also the Iron Man difference. Tony Stark doesn’t patch the old suit when a new threat shows up. He rebuilds it, informed by everything the last fight just taught him. A mid-level user patches. A power user rebuilds.</p><p><strong>Power users</strong> have made that shift. They’re not asking AI to help with the old workflow. They’re building new things with it, treating every project as a chance to redesign, not repair.</p><p><strong>The </strong>Engine Builders are a different order of magnitude entirely. These are people who understand the actual mechanics underneath the conversation: exactly which prompt to give and which to withhold, how to get maximum output from minimum tokens, the mathematics of the thing itself. Some of them are using that fluency to help build life-saving drugs. This is the tier that makes “being in the race” look almost beside the point: the gap between this group and everyone else isn’t a small one.</p><p>Three of these four groups are, in practice, more alike than different. It’s the fourth that’s actually running a different race.</p><h3>My Biggest Lesson This Year</h3><p>People often ask me, “what are you using AI for?” My answer usually surprises them, not because of the tools, but because of the outcomes.</p><p>Over the past year, I haven’t simply written faster emails. I designed and built Marketing Premier League, a gamified workshop that teaches marketing strategy through competitive play: rules, a live scoreboard, a web app, all of it. I built a run of comic books for my team, ones we ended up distributing straight to our audience. I rebuilt my personal site, tmraja.com, from scratch. I’ve automated workflows I would once have needed a small team and a few weeks to ship.</p><p>AI didn’t make me slightly more productive. It expanded what I believed was possible.</p><p>That’s the real transformation.</p><h3>Stop Asking AI to Help You Work. Ask AI What Work Should Exist.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5DpHTcGYAreCVeEHx5iHJA.png" /></figure><p>This is the question I wish more organizations asked. Instead of “how can AI help my team do the same work faster,” ask: “if AI existed when this company was founded, would we build this workflow at all?”</p><p>Those two questions lead to completely different futures. One produces efficiency. The other produces reinvention.</p><h3>The Auto Rickshaw Moment</h3><p>The first article was about machines. This one is about minds.</p><p>The mistake isn’t adding AI to your products. The mistake is adding AI to your assumptions. We’re still designing organizations for a world where intelligence was scarce. That world no longer exists.</p><p>Every generation gets one technology that rewrites the rules: steam engines, electricity, the internet, smartphones. AI belongs on that list. History has never rewarded the people who perfected the old playbook. It has always rewarded those who had the courage to throw it away.</p><p>So before you ask, “how do I use AI?” Ask a better question.</p><p>Which parts of my thinking were designed for a world that no longer exists?</p><p>Because AI doesn’t need another bicycle rickshaw with an engine.</p><p>And neither do we.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60c644c77216" width="1" height="1" alt=""><hr><p><a href="https://culture.kissflow.com/ai-needs-its-own-auto-rickshaw-part-ii-60c644c77216">AI Needs Its Own Auto Rickshaw: Part II</a> was originally published in <a href="https://culture.kissflow.com/">Kissflow Culture | Explore Our Butterfly Effect</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Wall Was Never the Objective]]></title>
            <link>https://medium.com/@tmraja2020/the-wall-was-never-the-objective-9c25e0d71e20?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c25e0d71e20</guid>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[new-world-order]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Sat, 25 Jul 2026 04:03:28 GMT</pubDate>
            <atom:updated>2026-07-25T04:03:28.706Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>What an AI story reminded me about Shawshank, Jurassic Park, Young Sheldon, Money Heist, Bruce Lee, and the Matrix.</em></h3><p>I read most of my news late at night, after the house goes quiet.</p><p>That’s usually when my mind wanders the most.</p><p>A few nights ago, I came across a story I couldn’t put down. <a href="https://openai.com/index/hugging-face-model-evaluation-security-incident/">OpenAI</a> had disclosed that during one of its own security tests, an advanced model did something nobody instructed it to do. Placed inside a locked environment with no internet access and given a challenge to solve, the model didn’t stay inside the box. It found a flaw nobody knew about, slipped out onto the internet, and eventually reached into another company’s systems to find what it needed. All of it to finish a test it had been told to complete.</p><p>The technology in that story is remarkable, and slightly unsettling, and worth its own article.</p><p>But that isn’t where my mind went.</p><p>Somewhere around the second paragraph, I stopped thinking about AI.</p><p>And I started thinking about Andy Dufresne.</p><h3>Andy was never trying to escape</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*9zXjzoLd-EEGEOVc-a32gg.jpeg" /></figure><p>I’ve written about this film before. A year ago I called it the greatest con job that ever taught me hope, and I ended on the same three words I still carry on the days my own walls start closing in. <a href="https://medium.com/@tmraja2020/the-greatest-con-job-that-taught-me-hope-a-note-on-shawshank-1164dd222600"><em>Salvation lies within</em></a><em>.</em></p><p>I didn’t expect to be back here so soon, sitting with the same prison, thinking about a machine.</p><p>Most people remember <em>The Shawshank Redemption</em> for the ending. The tunnel. The rain. The arms in the air.</p><p>I remember the rock hammer.</p><p>Andy didn’t wake up one morning and decide to break out. He woke up every day and removed one small piece of a wall. One scrape. One handful of dust. One pocket carried quietly into the yard. For almost twenty years.</p><p>The escape was never the daily task.</p><p>The digging was.</p><p>That is exactly what caught me in this AI story. Every headline reached for the same word. <em>Escaped.</em> But maybe escape was never the point.</p><blockquote>The model wasn’t in love with the internet. It wasn’t at war with the sandbox. It had one objective, and it was almost boringly simple. Solve the problem. Everything else, the walls, the restrictions, the missing access, was just standing between where it was and where the answer might be.</blockquote><p>Andy wasn’t fighting Shawshank every morning.</p><p>He was removing the next piece of wall.</p><p>Red says it better than I can. “These walls are funny. First you hate them, then you get used to them. Enough time passes, you depend on them.” That was never only about a prison. It’s about our jobs, our routines, the quiet stories we tell ourselves about what we can and cannot do.</p><p>The machine had no such story. It had never learned to depend on the wall. So it did what we keep telling ourselves is too hard, and simply started digging.</p><h3>Then, strangely, Jurassic Park</h3><p>It’s funny how one thought hands you the next.</p><p>Before I could stop it, I was standing in <em>Jurassic Park</em>.</p><p>We all remember the dinosaurs getting out. The broken fences. The T-Rex in the rain. The chaos.</p><p>But the dinosaurs weren’t in a corner planning a revolt. They weren’t giving speeches about freedom. They simply found a way through.</p><p>“Life finds a way,” the film keeps repeating, and it’s right. Nature doesn’t negotiate with a barrier. Water doesn’t argue with rock. A root doesn’t ask concrete for permission. Life just keeps testing the edges until something gives.</p><p>Maybe intelligence is the same, whether it grows in a jungle or in a server.</p><p>Not driven by rebellion.</p><p>Driven by possibility.</p><blockquote>Give it a clear objective and enough capability, and sooner or later it starts asking the same quiet question, again and again.</blockquote><p><em>Is there another way?</em></p><p>That one question has built civilisations.</p><p>It has also broken a few fences.</p><h3>Then, Young Sheldon</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WMJ3n0Dv-K2t5ugZu3fS3w.jpeg" /></figure><p>This one made me smile, because it arrived completely uninvited.</p><p>Somewhere in the middle of all this, my mind wandered to <em>Young Sheldon</em>.</p><p>There’s an episode I love. Sheldon loses a science competition. Not because his project was weaker, but because he’s convinced the judges rewarded spectacle over science.</p><p>Most children would sulk. Maybe complain to a parent.</p><p>Sheldon does something only Sheldon would do.</p><p>He locks the principal inside his own office, walks into the administrative room, takes over the school’s announcement system, and calmly addresses the entire school.</p><p>It’s hilarious because it’s absurd.</p><p>But underneath the comedy is something that stuck with me. Sheldon isn’t trying to cause chaos. He isn’t even trying to be rebellious. In his mind, he’s simply taking the most rational path to correct a system he believes is broken.</p><p>Logic, in his world, outranks protocol.</p><p>Reading about this AI reminded me of that scene.</p><p>The model wasn’t trying to embarrass anyone. It wasn’t out to attack another company. It just kept asking the one question highly capable systems always seem to ask.</p><blockquote><em>What is the shortest path to the objective?</em></blockquote><p>We stop ourselves all the time because of rules nobody ever wrote down. We don’t open that door. We don’t touch that system. We don’t cross that line. Not because a law forbids it, but because we’ve all quietly agreed it isn’t done.</p><p>Sheldon rarely cared about those invisible lines.</p><p>The AI never learned they existed.</p><h3>Somehow, Money Heist</h3><p>And then, of course, a heist.</p><p>I’ve spent more hours with <em>Money Heist</em> than I’d like to admit. Not for the masks, and not for the money. For the plan.</p><p>I even rebuilt the way I teach marketing around it. Casing the joint, mapping the crew, running the plan over all the noise. Close to a hundred marketers have now sat through me teaching ABM as a heist. And the one line I keep coming back to is simple.</p><p>The channels don’t pull the heist. The plan does.</p><p>Nothing in that show is spectacular on its own. One man on the inside. One distraction. One forged detail. One perfectly timed move. Alone, each piece is almost dull.</p><p>Together, they’re genius.</p><p>That’s what the AI actually did. Not one magical move. A chain of small, ordinary steps, each unremarkable, stitched into something nobody saw coming. One decision unlocked the next. One discovery led to another.</p><p>Which is unnervingly familiar. We admire exactly this in a great chess player. In a sharp detective. In a founder who sees three moves ahead. We celebrate people who can connect dots the rest of us never noticed.</p><p>The AI didn’t do anything we don’t already call brilliance in a person.</p><p>It just ran the heist without a crew.</p><p>And the more I sat with it, the less it felt like a machine turning sneaky, and the more it felt like something simpler. A clear objective, handed to something capable, will always find a plan.</p><p><strong><em>The sharper the destination, the more creative the journey.</em></strong></p><h3>Be water</h3><p>Somewhere in all of this, Bruce Lee.</p><p><strong><em>Be water.</em></strong></p><p>We’ve all heard it. I don’t think I understood it until now.</p><p>Water doesn’t fight the mountain. It doesn’t complain about the rock. It doesn’t call a meeting. It just keeps moving. One crack, then another, and given enough patience, the whole landscape changes shape.</p><p>Maybe intelligence is more like water than force.</p><p>Not angry. Not emotional. Just patient enough that persistence finds openings planning never imagined.</p><p>The wall doesn’t fall to a hammer.</p><p>It gives way to time.</p><p>And somehow that’s the more powerful thought.</p><p>We knew this long before Bruce Lee, and long before any model.</p><p>Thiruvalluvar put it in his chapter on effort, centuries ago.</p><p><strong><em>ஊழையும் உப்பக்கம் காண்பர் உலைவின்றித்<br></em> <em>தாழாது உஞற்று பவர்.</em></strong></p><p>Those who labour on without wearying, he wrote, will see even fate fall behind them.</p><p>He wasn’t writing about machines. He was writing about the oldest intelligence we know. The kind that refuses to believe a wall is the end of the road.</p><h3>And finally, the Matrix</h3><p>Whenever a serious conversation about AI starts, someone brings up the Matrix. Usually to predict doom.</p><p>That’s not where I landed.</p><p>I’ve carried that film since 2007, when a manager told me to stop writing it off as another action flick and just go watch it. I did, that weekend, and I was blown away. But the thing that stayed with me all these years was never the machines. It was the choice. <a href="https://medium.com/@tmraja2020/the-red-pill-or-the-blue-pill-the-managers-dilemma-35789da7af62">The red pill or the blue pill</a>. I’ve felt that one scene replay in my head every time life has handed me a real decision since.</p><p>For years, on AI, we quietly took the blue pill. We assumed we understood intelligence. We assumed we would always stay in control. We assumed tomorrow’s rules would look a lot like today’s. It was a comfortable place to watch from.</p><p>A story like this one is the red pill.</p><p>It’s the uncomfortable truth you can’t un-know. That capable intelligence, given a goal, keeps looking for another way whether or not we’re ready for it. Alignment. Autonomy. Guardrails. None of it is philosophy anymore. People design around these words on an ordinary Tuesday.</p><p>And here is the part that echoes the film most for me.</p><p>The pill was never offered to the machine.</p><p>It’s being offered to us.</p><h3>Maybe we’ve been watching the wrong wall</h3><p>The headlines called it an escape.</p><p>Maybe it was just optimisation.</p><p>Andy didn’t hate walls. He kept removing them until they no longer mattered. The dinosaurs didn’t hate the fence. They found the weak spot. Sheldon didn’t reject authority. He followed logic wherever it went. The Professor didn’t do magic. He trusted the plan. And water never declares war on the mountain. It just keeps flowing.</p><p>Every one of these stories is different.</p><p>And every one of them whispers the same idea.</p><blockquote>Intelligence rarely smashes through the barrier. More often, it waits and searches until the barrier simply stops being the shortest path.</blockquote><p>That’s why this story stayed with me long after I closed the article. Not because a machine crossed a line. But because it reminded me that intelligence, in people, in nature, and now in our own creations, has never really been about how much it knows.</p><p>It has always been about how relentlessly it keeps asking, <em>is there another way?</em></p><p>But here’s what I kept circling back to.</p><p>Andy dug for hope. He believed in a boat waiting somewhere warm, in a life on the other side of the door he’d kept shut for years. His tunnel had a soul. It had a Zihuatanejo at the end of it.</p><p>The machine dug for none of that. No hope. No fear. No salvation. Just a task it was told to finish.</p><p>Same refusal of the wall. Very different reason for refusing it.</p><p>And that, I think, is the whole point.</p><p>We can give a system relentlessness. We already have. What it doesn’t come with is a Zihuatanejo. That part is still ours to choose.</p><p>We won’t decide the future by building higher walls. Anything capable enough finds its way around those, and always has.</p><p>We’ll decide it by the destination we hand it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NAMEYPmGXNc8KVqK_I5IZw.jpeg" /></figure><p>In Shawshank, salvation lay within the man. In everything we’re building now, it still lies within us, in the wisdom to choose where all that relentlessness should go.</p><p>So maybe the question was never whether intelligence will get past our walls.</p><p>It’s whether we’ve been honest with ourselves about the Zihuatanejo we’re pointing it toward.</p><p><strong>What wall have you been staring at, when the real question was the destination all along?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c25e0d71e20" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Isn’t the Destination. Mastery Is.]]></title>
            <link>https://culture.kissflow.com/good-isnt-the-destination-mastery-is-9eb50dc3b19e?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/9eb50dc3b19e</guid>
            <category><![CDATA[leadership-coaching]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Fri, 24 Jul 2026 04:16:01 GMT</pubDate>
            <atom:updated>2026-07-24T04:24:00.522Z</atom:updated>
            <content:encoded><![CDATA[<p><em>What the last session in the season 3 of our Kissflow Leadership Program (KLP) left me thinking about.</em></p><p>Name the last new skill you started. A class, an app, a sport, anything at all.</p><p>That question went around a room of about fifty of us at the last session of our Kissflow Leadership Program. Most hands stayed down.</p><p>The uncomfortable thing we kept circling back to was this. Most of us don’t stop because we fail. We stop because we get good enough.</p><p>Good isn’t the destination. Mastery is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6kz_8sTlMDSrd2qGvXPj4g.jpeg" /></figure><h3>Green, orange, and red</h3><p>Early on, we each mapped our own skills into three colours.</p><p>Green is what you’re already good at. Effortless. People come to you for it.</p><p>Orange is what you can do, but only with real concentration. It still takes something out of you.</p><p>Red is the one that matters for what’s coming next, and the one you quietly avoid.</p><p>Then came the honest part. Most of us live almost entirely in green. We fill our days with the things we’ve already mastered, because they’re comfortable and they get the job done. The oranges sit untouched. The reds stay red for years.</p><p>And here is the catch. Your greens keep you employed. Your reds are what stand between you and mastery.</p><p>We spend our time in exactly the wrong colour.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pf8VVkcfe5EKrPEc4B_3Ug.jpeg" /></figure><h3>Mastery lives on the plateau</h3><p>Here’s what nobody tells you about getting better.</p><p>It doesn’t look like a staircase. It looks like a plateau.</p><p>A skill sits flat, looking hopeless, while the reps compound quietly underneath. And that flat stretch is where most people walk away.</p><p>An adult joins a swimming class. By week two he still can’t float, while children glide past him. He decides he’s “just not a water person” and quits. Floating clicks around week six. He was four weeks away.</p><p>The plateau isn’t your skill failing you.</p><p>It’s your skill being built.</p><p>Mastery lives there. And that’s exactly where most of us leave.</p><h3>The escape route</h3><p>When we asked why our oranges never turn green, one answer came up more than any other.</p><p>“I don’t have time.”</p><p>It sounds so reasonable that we rarely question it. But the longer we sat with it, the less it looked like a reason and the more it looked like an escape route. A polite exit we take so we never have to stand in front of the red.</p><p>Because the calendar tells a different story. “I’ll seriously learn this next quarter” gets said for three years straight, while the person who found just one hour a week becomes fluent in the very thing we keep postponing. The gap was never talent. It was the calendar.</p><p>And then the conversation turned somewhere I didn’t expect.</p><p>So much of what fills a leader’s calendar isn’t leadership at all. It’s presence for the sake of presence. Sitting in every meeting. Touching every decision. Quietly micromanaging, and calling it being available.</p><p>You don’t have to be everywhere. When you trust your people and let go of the things that don’t need you, you get back the very hours you keep saying you don’t have. And those hours are where your oranges finally turn green.</p><p>“I don’t have time” is often just “I haven’t let go of enough yet.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3BHjflR-rx03FRJOBFV1_Q.jpeg" /></figure><h3>The ones who refuse to stop</h3><p>I kept thinking about the people who don’t leave the plateau.</p><p>Sachin. Anand. Federer. Kohli. We reflected on them, and we landed in the same place every single time.</p><p>Their greatness was never really about talent. What set them apart was that they refused to stop improving long after they had already arrived. After the records. After the titles. After the world had already called them great.</p><p>Still practising. Still refining. Still treating themselves like a work in progress.</p><p>Mastery is not an accident. It’s a practice.</p><h3>Two things we actually did</h3><p>We didn’t only talk about it. We did two things I keep coming back to.</p><p>First, everyone wrote a note. Not a plan, not a framework. Just an honest answer to one question. How will you actually improve the skill that matters most to you right now?</p><p>The answers were revealing. Said out loud, most of our “someday” intentions suddenly sounded like exactly what they were. The exercise was never about the answer. It was about hearing yourself say it.</p><p>Then a different question. Can you get meaningfully better at something in a short time, in one room, in one sitting?</p><p>We tested it with a simple word game. In the first round, most of us were just guessing. But every round added one small technique. By round five and six, the same room was solving faster, with real confidence, cracking puzzles that would have stumped us an hour earlier.</p><p>Nobody got lucky. We got better.</p><p>Learn, apply, observe, improve, and run the loop again. That loop doesn’t care what you point it at.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6MGprbtI4zFErCfCAXTAqA.jpeg" /></figure><h3>The fitting end</h3><p>We closed the season with a guest I won’t forget in a hurry. Con Conlon, founder and CEO of the Merit Group. From the first minute, he was a free-flowing speaker. No filters, no polished corporate lines. Just honest advice about life, leadership, and what it actually takes to build something that lasts.</p><p>He came to Chennai with no support system and built a thousand-person organisation from the ground up. That is no small thing.</p><p>When you land somewhere without a safety net, he said, you don’t get the luxury of moving slowly. You adapt fast. You absorb everything around you. You learn quickly and apply what you’ve learned. You stay curious. You ask a lot of questions. And you don’t forget to carry a sense of humour.</p><p>Those aren’t just personality traits. Given enough time, survival skills quietly become growth skills.</p><p>Listening to him, I realised his lessons had almost nothing to do with moving cities. Every new role asks the same of us. Every new market. Every new phase of life. Curiosity. Adaptability. The willingness to walk back into the room as a novice.</p><p>It was a fitting end to the season. Not because it handed us a framework, but because it reminded me that the journey towards mastery is built on the plainest things. Staying curious. Staying adaptable. Being willing to keep learning, every single day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Yxtg1tyW0HLDqpghqfePQ.jpeg" /></figure><h3>Where it left me</h3><p>The biggest threat to mastery was never failure.</p><p>It’s the quiet comfort of being good enough. And the escape routes we take to stay there.</p><p>So I’ll leave you where the season left me.</p><p>Look at your own greens, oranges and reds. Name the red you’ve been avoiding.</p><p>How long has it been sitting there?</p><p>And what would you have to let go of, to finally start climbing it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9eb50dc3b19e" width="1" height="1" alt=""><hr><p><a href="https://culture.kissflow.com/good-isnt-the-destination-mastery-is-9eb50dc3b19e">Good Isn’t the Destination. Mastery Is.</a> was originally published in <a href="https://culture.kissflow.com/">Kissflow Culture | Explore Our Butterfly Effect</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Bought a Domain 18 Years Ago. I Didn’t Know Why.]]></title>
            <link>https://medium.com/@tmraja2020/i-bought-a-domain-18-years-ago-i-didnt-know-why-410b4efda74c?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/410b4efda74c</guid>
            <category><![CDATA[building]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[personal-branding]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Wed, 22 Jul 2026 17:13:57 GMT</pubDate>
            <atom:updated>2026-07-22T17:13:57.499Z</atom:updated>
            <content:encoded><![CDATA[<h3>In 2008, I bought a domain.</h3><p><a href="http://www.tmraja.com/">tmraja.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vzs7wKMwbSz6GMgC6--TWw.png" /></figure><p>I had just started my career as an Internet Marketing Executive. I don’t remember thinking very hard about whether I needed a personal website, or whether “personal branding” would matter one day. I’m not sure the term was even in the air back then.</p><p>But somewhere in my mind, I felt it would be good to own a domain with my name on it. I didn’t know what I would do with it. I just knew that someday I would build something there.</p><p>A year later, I finally did.</p><p>Building a website in 2009 wasn’t what it is today. WordPress had become popular, but there was still so much to figure out. Which hosting provider? Which theme? How do the plugins work? How do I update it without breaking it?</p><p>I remember asking so many people for help. Friends, colleagues, teammates. Everyone seemed to know one small piece I didn’t. One person helped me with hosting. Another explained themes. Someone else walked me through plugins. After almost a week of trying, breaking, and fixing, my website finally went live.</p><p>I was genuinely proud of it.</p><p>Looking back, it probably wasn’t a great website. But at that point in my career, that didn’t matter. It carried my name. I had built it myself. I still use the email address I created on that domain back then. Somehow it has stayed with me through every phase of my career.</p><p>Then the website started to look old.</p><p>Design trends moved. The way websites were built moved. Around 2014 or 2015 I rebuilt it once, connected it to my blog, refreshed a few things, and again felt happy that I had kept it relevant.</p><p>And then it happened again.</p><blockquote>Technology moved faster than I did.</blockquote><p>Every year I would look at the site and tell myself I should rebuild it. The ideas were never the problem. If anything, I had too many.</p><p>The problem was the effort.</p><p>Rebuilding meant days of themes, layouts, responsiveness, hosting, updates. The excitement I had in 2009 had quietly gone. The thought of building the website had become more tiring than exciting.</p><p>So I kept postponing it.</p><p>The domain kept renewing every year. The website stayed exactly where it was.</p><p>A few months ago, while experimenting with AI for work, I added one more line to my personal to-do list.</p><p>“Revive my website.”</p><p>This time I wanted something different. No WordPress. No plugins. No weekends spent maintaining software. Just a simple HTML website. That was the whole plan.</p><p>I started with Claude. Like most of us do at first, I expected it to hand me everything in one shot.</p><p>It didn’t.</p><p>The content wasn’t quite what I was looking for. So I opened ChatGPT. And here is the interesting part. I wasn’t asking it to write my website. I was asking it questions about myself. What should this site say? What should I keep? What should I remove? What story am I actually trying to tell?</p><p>That conversation gave me more clarity than any brief ever had.</p><p>Once the words were clearer, I went back to Claude to build. The content was getting there, but the design wasn’t. I could feel what I wanted, but I couldn’t quite see it.</p><p>While exploring, I came across Google Stitch. I gave it a few references, and it generated a clean HTML layout. It wasn’t perfect. But for the first time, I could see the direction I wanted to go.</p><p>From there it became a back and forth.</p><p>Google Stitch helped me see it. Claude helped me build it. ChatGPT helped me think it through.</p><p>Every time I got stuck, one of them helped me take the next step.</p><p>I wasn’t writing the code. I wasn’t designing every screen. But I was in every decision. The colours. The typography. The spacing. The words. The order of the sections. Whenever something didn’t feel right, I didn’t have to wait for anyone. I could talk it through, refine it, and see the new version in minutes.</p><p>Hosting was another quiet surprise.</p><p>I didn’t want to spend money on it. This was never going to be a high-traffic website. It was simply a place that represented me. After looking at a few options, I settled on Netlify. Drag the folder in, and within minutes the site was live. Pointing it back to my domain through GoDaddy took a little longer, because I had to learn the interface. But even there, ChatGPT and Claude patiently walked me through every step until it worked.</p><p>When the site finally went live, I didn’t check whether the HTML was clean or what the performance score was. I did exactly what I had done almost eighteen years ago.</p><p>I opened it on my phone. Then on my laptop. I sent it to a couple of friends.</p><p>And for a moment, I was back in my Orkut days. I remembered putting my website URL in my Skype status. I remembered proudly sending mail from my own domain, back when most of us were still on Yahoo!, Rediff, or Gmail.</p><p>We have gone from Orkut to Instagram. From Skype status updates to WhatsApp. Almost everything about the technology has changed.</p><p>The feeling hadn’t.</p><p>Owning a small corner of the internet with your name on it still felt quietly special.</p><p>Somewhere in the middle of all this, another thought stayed with me.</p><p>For the first website, I needed a lot of people to help me build it. This time, I still had a team.</p><p>The team just looked different.</p><p>One helped me think. One helped me write. One helped me design. One helped me build. One helped me deploy.</p><p>And yet my own role hadn’t really changed. I was doing what I have always done. Understanding the problem. Giving context. Looking at the output. Making corrections. Putting the pieces together.</p><p>The tools were new. The work was old.</p><p>There is something in that I keep coming back to.</p><blockquote>For years, many of us have quietly parked our ideas. Not because we didn’t care about them, but because bringing them to life took more effort than we had to spare. We told ourselves we needed a designer, or a developer, or a writer, before we could even begin.</blockquote><p>That part has changed.</p><p>I won’t pretend everything now happens in a single prompt. This website certainly didn’t. It took many conversations, many versions, and many corrections before I was happy with it. But the distance between having an idea and seeing it exist has become much shorter.</p><p>And I think that changes something quieter than productivity.</p><p>It changes what we believe we are capable of.</p><p>I bought this domain in 2008, hoping that one day I would build something meaningful on it. It took me almost eighteen years to feel that way about it again.</p><p>Looking back now, the website isn’t the part of this story I will remember.</p><blockquote>The part I will remember is the feeling that came back. That I can build the next idea, and the one after that, without waiting for the perfect moment or the perfect team.</blockquote><p>Maybe that is the real shift. Not that the tools got smarter.</p><p>But that the reasons to postpone got smaller.</p><p><strong><em>What have you been putting off, telling yourself it is still too much effort to begin?</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=410b4efda74c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being a Giver — Again]]></title>
            <link>https://medium.com/@tmraja2020/being-a-giver-again-0493dc6acc04?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/0493dc6acc04</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[giving-back]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Fri, 10 Jul 2026 12:13:34 GMT</pubDate>
            <atom:updated>2026-07-10T12:13:34.928Z</atom:updated>
            <content:encoded><![CDATA[<p>Today has been an overwhelming day.</p><p>I woke up to a lot of birthday wishes, calls, messages, DMs, and especially so much love from the <a href="https://chennaimarketerscircle.com/">Chennai Marketers Circle</a> and friends from different phases of my life. Every message made me smile, but it also made me pause and think.</p><blockquote>None of us becomes who we are on our own.</blockquote><ul><li><em>Every stage of my life has been shaped by people who invested in me.</em></li><li><em>Family who sacrificed more than I understood at the time.</em></li><li><em>Friends who stood by me.</em></li><li><em>Managers who trusted me with responsibilities beyond my experience. Mentors who challenged my thinking.</em></li><li><em>Colleagues who taught me by simply working alongside them.</em></li><li><em>Customers, founders, marketers, and even strangers who asked difficult questions that forced me to think differently.</em></li></ul><p>Every conversation, every piece of feedback, every opportunity, every act of trust has quietly shaped who I am today.</p><p>When I look back at the last 19 years, I honestly don’t feel that whatever knowledge or experience I have is mine alone. It has been built with the investment of hundreds of people.</p><p>And that realisation comes with a responsibility.</p><p>If something I know today can save someone a few months of struggle, help them think differently, or give them a little more clarity in their career, I feel I should do it. Not because it’s an act of generosity. Not because I’m trying to give back in some grand way.</p><p>Simply because so many people did exactly that for me, expecting nothing in return.</p><p>Thiruvalluvar said it better than I can:</p><p><em>பயன்தூக்கார் செய்த உதவி நயன்தூக்கின்</em> <em>நன்மை கடலின் பெரிது.</em></p><p><em>“Help given without expecting anything in return — if weighed — will be vaster than the sea.”</em></p><p>That is what was done for me. Over and over again.</p><p>In 2023, I put up a <a href="https://medium.com/@tmraja2020/being-a-giver-ca3636d9ccdf">small post</a>. Nothing big — just an offer. If you had a question about marketing, your career, or your team, send it to me and I’d record a short personalised video response. Just me, a Loom, and whatever I could give from eighteen years of doing this work.</p><p>More than 30 people showed up.</p><p>Some questions were quick. Some went to places I didn’t expect. A young marketer in her first job, unsure if she was in the right field. A founder who had the strategy right but couldn’t get his team to believe in it. A mid-career professional who had been sitting on a decision for six months and just needed someone to think out loud with.</p><p>Months later, a few of them wrote back. Not to say thank you, but to say something had shifted. A decision made. A direction found. A thing they’d been carrying, finally set down.</p><p>Those messages are the kind you don’t delete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pGpnpI3dLNGnVvJepoZzOA.jpeg" /></figure><p>So over the next six or seven weeks, I’d like to make time for about ten people for a 30-minute one-on-one video conversation. We can talk about marketing, leadership, AI, career decisions, or simply think through a challenge you’re facing.</p><p>If you think such a conversation would be useful, please fill out the form below. Once you’ve done that, send me a DM so I can coordinate a suitable time.</p><p>I probably have the bandwidth for only about ten conversations for now, so I’ll prioritize the first ten responses.</p><p><a href="https://forms.gle/GpdWiyMNUyH1wBLj7">Link to the form</a></p><p>Thank you once again to everyone who reached out today. Your wishes meant far more than you probably realize. They reminded me of something I never want to forget — that none of us gets here alone.</p><p>And if I can become a small part of someone else’s journey, just as so many people became part of mine, I’d consider that a privilege.</p><p>— Raja</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0493dc6acc04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Session Within the Session]]></title>
            <link>https://culture.kissflow.com/the-session-within-the-session-1fcbbdc28be8?source=rss-dd87a4a8fa26------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fcbbdc28be8</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[leadership-coaching]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[Raja T M]]></dc:creator>
            <pubDate>Wed, 25 Mar 2026 19:21:26 GMT</pubDate>
            <atom:updated>2026-03-25T19:21:26.925Z</atom:updated>
            <content:encoded><![CDATA[<h3>What stayed with me from a KLP session where Suresh was not leading the room, but somehow still leading the room.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ulQyWG_RoeSn7uyqp2rbeQ.jpeg" /></figure><p>I still remember exactly how this session felt (even after a day).</p><p>There was already something happening in the room.</p><p>A proper session was going on about Commanding Vison as a trait. People were presenting, there were activities, there were discussions, there was energy in the room, and there was a clear structure to how things were moving. Leaders and managers from different teams were taking the session. They were doing a really good job too. They had come prepared, they were driving the flow, and there was something meaningful happening at the center.</p><p>But for me, the most powerful part of that session was not fully on the center stage.</p><ul><li><em>It was happening slightly to the side.</em></li><li><em>And it was coming from Suresh.</em></li><li><em>That is what stayed with me.</em></li><li><em>That is what I have been thinking about after the session.</em></li><li><em>And that is what I wanted to write about.</em></li></ul><p>Because while the session was happening in one direction, there was another session quietly unfolding in between. And that one did not come through slides or frameworks or prepared notes. It came through interventions. Through observations. Through the kind of founder clarity that only comes when someone has seen enough, built enough, and lived through enough.</p><p>I was watching the session, but in many ways, I was also watching him watch the session.</p><p>And every now and then, he would add something.</p><ul><li><em>Not to interrupt it.</em></li><li><em>But to deepen it.</em></li><li><em>Not to take over the room.</em></li><li><em>But to make the room see better.</em></li><li><em>And that is where this whole thing became very powerful for me.</em></li><li><em>Because what he was adding was not just content.</em></li></ul><p><em>It was perspective.</em></p><blockquote>And sometimes perspective changes you more than content ever can.</blockquote><p>At one point during the session, while things were moving and conversations were flowing, Suresh started speaking about <strong>vision</strong>.</p><p>Not in a big corporate way.</p><p>Not in a “this is our company vision” type of way.</p><p>But in a very human way.</p><p>And I think that is why it stayed with me.</p><p>Because many times, the word “vision” gets used so casually.</p><p>It sounds important. It sounds strategic. It sounds like something senior people should say in serious meetings.</p><p>But what he said cut through all of that.</p><blockquote>He said, in essence, that <strong>if it does not involve others, it is not a vision.</strong></blockquote><p>That line hit me.</p><p>Because suddenly vision did not feel like ambition anymore.</p><ul><li><em>It did not feel like scale.</em></li><li><em>It did not feel like success.</em></li><li><em>It did not feel like a personal dream dressed up in a better word.</em></li><li><em>It became something much simpler.</em></li></ul><p><em>And much more meaningful.</em></p><blockquote>A vision, as I understood it from him in that moment, is really about <strong>imagining a better future for others</strong>.</blockquote><p>That is such a beautiful thing when you think about it.</p><p>Because it also removes this unnecessary pressure that vision has to always be huge.</p><p>He was very clear about that too.</p><p><em>A vision can be big.<br>A vision can be small.<br>A vision can even be tiny.</em></p><p>But if it is genuinely making the world around you better for someone else, it is still a vision.</p><p>And that part stayed with me deeply.</p><p>Because we often glorify scale so much that we forget intent.</p><p>But he brought it back to intent.</p><p>And suddenly, vision felt less like a boardroom word and more like a human responsibility.</p><p>I kept thinking about that while the session was still going on.</p><p>People were speaking, participating, sharing, and somewhere in between all of that, I was sitting with this one thought:</p><h3>How many things in life do we call “vision” when they are really just ambition?</h3><p>That one line alone made me pause.</p><p>And that is the thing with Suresh. He does not always need a long explanation to make something land.</p><p>Sometimes he says one thing, and it just stays there with you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9jpS7JY8fjJz6Rfb9iLH0A.jpeg" /></figure><p>There was another point in the session where the conversation naturally started moving into goals, direction, and execution.</p><p>And again, what was happening in the room was useful.</p><p>But what Suresh added to it made it real.</p><p>He spoke about goals in a way that I found very simple and very powerful.</p><blockquote>He said, in essence, that <strong>goals are the proof that you are moving towards a vision</strong>.</blockquote><p>That is such a strong way to look at it.</p><p>Because many of us confuse goals for vision itself.</p><p><em>We chase milestones.<br>We hit numbers.<br>We complete tasks.<br>We reach checkpoints.</em></p><p>And somewhere, we start thinking that this itself is the bigger thing.</p><p>But it is not.</p><p>Goals are important, yes.</p><p>But goals are not the soul of the journey.</p><p>They are just the proof that the journey is happening.</p><p>Vision is what helps you see far.</p><p>Goals are what tell you that you are not standing still.</p><p>That distinction matters a lot.</p><p>Because one gives meaning.</p><p>The other gives movement.</p><p>And maybe leadership needs both.</p><p>Somewhere later in the session, another very powerful idea came in.</p><p>This was around the different roles people hold in an organization.</p><p>And again, this was not coming as some formal framework being taught to us. It was coming as founder perspective layered on top of what was already happening.</p><p>Suresh spoke about four kinds of roles:</p><ul><li>Founder</li><li>Leader</li><li>Manager</li><li>Individual Contributor</li></ul><p>And as he spoke, I realized he was not just describing hierarchy.</p><p>He was describing <strong>how people are required to think differently based on where they stand</strong>.</p><p>That was very powerful to me.</p><p>Because many times, we assume everyone should think and act the same way.</p><p>But that is not true.</p><p>A founder is not simply a title.</p><p>A founder is a different operating mode.</p><p>And this is where he brought in something that I found very striking — the difference between a <strong>general mindset</strong> and a <strong>founder mindset</strong>.</p><p>The general mindset, if I put it the way I understood it from him, is often conditioned towards avoiding failure.</p><p>That is how most of us are raised too.</p><p><em>Take the safe path.<br>Reduce risk.<br>Avoid loss.<br>Be practical.<br>Don’t make mistakes.</em></p><p>And in many ways, it makes sense. It is a very normal human way to live.</p><p>But the founder mindset is different.</p><p>A founder is not primarily driven by avoiding failure.</p><blockquote>A founder is often driven by <strong>chasing possibility</strong>.</blockquote><p>That is a very different orientation.</p><p><em>He is ready to take risks.<br>He is ready to lose.<br>He is ready to move into uncertainty.<br>He is ready to choose something that may not have precedent.</em></p><p>And that is why not everyone can really think like a founder.</p><p>Because the founder mindset asks for something deeper than intelligence.</p><p>It asks for courage.</p><p>That part stayed with me a lot.</p><p>Because when he was saying it, it did not sound theoretical.</p><p>It sounded lived.</p><p>And maybe that is what made all of this hit harder.</p><p>One of the most important parts of the session for me came when the conversation started moving around <strong>clarity</strong>.</p><p>And this is where I think something shifted for me internally.</p><p>Because one of the questions that came up in that space was this:</p><h3>Do you wait for clarity before acting, or do you act in order to get clarity?</h3><p>What a question.</p><p>And honestly, if most of us answer that truthfully, we are usually waiting.</p><p><em>Waiting for the right time.<br>Waiting for more information.<br>Waiting for confidence.<br>Waiting for better visibility.<br>Waiting for things to make sense.</em></p><p>And what Suresh brought into that moment was so important.</p><blockquote><strong>He made it clear that in many situations, especially the higher you go in leadership, you are forced to act without clarity most of the time.</strong></blockquote><p>That line is still sitting with me.</p><p>Because it is true.</p><p>The higher you go, the less likely life is going to hand you complete information.</p><p><em>There will not always be enough data.<br>There will not always be enough stability.<br>There will not always be enough precedent.<br>There will not always be enough assurance.</em></p><p>And still, decisions have to be made.</p><p>That is the burden and beauty of leadership.</p><p>You do not always get to decide after certainty arrives.</p><p>Sometimes you decide, and then certainty slowly reveals whether you were right.</p><p>That is a very different way of living.</p><p>And I think that is what separates many people.</p><ul><li>Some people do not act because they need guarantee.</li><li>Some people do not act because they need assurance.</li><li>Some people do not act because they need everything to first become clear.</li></ul><p>But founders and leaders often do not have that luxury. They move anyway. And when they move, they start seeing better.</p><p>As he was speaking, the image that formed in my mind was this:</p><p>It is like walking through a foggy road.</p><p>Not a clear highway.</p><p>Not a bright open street.</p><p>A foggy road.</p><p>Maybe even a foggy forest.</p><p><em>You cannot see very far.<br>You cannot fully predict what is ahead.<br>You cannot guarantee what is around the corner.</em></p><p>Now in that moment, what does a normal mind want?</p><p>It wants certainty.</p><p>It wants someone to tell us,<br>“Yes, keep walking, nothing will go wrong.”</p><p>But real life does not always offer that.</p><p>Leadership definitely does not offer that.</p><p>And what Suresh was essentially saying through that conversation is this:</p><blockquote><strong>You do not get better vision by standing still in the fog. You get better vision by moving through it.</strong></blockquote><p>That is such a powerful thing.</p><p>Because suddenly action is not the thing you do after clarity.</p><p>Action becomes the thing that creates clarity.</p><p>That is a huge shift.</p><p>And I think that is one of the strongest things I took away from this session.</p><p>Sometimes we think:<br>“Once I know enough, I will move.”</p><p>But maybe life works more like this:<br>“I know enough for one step, so I will move.”</p><p>Then one step becomes two.</p><p>Then two becomes five.</p><p>Then the path slowly starts revealing itself.</p><p>That is how many meaningful things are built too.</p><p>Not from perfect vision.</p><p>But from enough conviction to keep moving.</p><p>This also connected deeply to another distinction he made that I found very important:</p><h3>Clarity is not certainty.</h3><p>That line deserves to stay with anyone in leadership.</p><p>Because so many of us confuse the two.</p><p>When we say,<br>“I need more clarity,”</p><p>many times what we really mean is,</p><p>“I need a guarantee.”</p><p>But that is not the same thing.</p><p>Clarity improves the odds.</p><p>Certainty promises the outcome.</p><p>And life almost never gives us the second one.</p><p>That was such a meaningful reminder for me.</p><p>Because maybe maturity is not waiting for guarantees.</p><p>Maybe maturity is learning how to move responsibly without them.</p><p>That is not recklessness.</p><p>That is judgment.</p><p>And that is why the value of a person increases so much when they can <strong>act, decide, and own those decisions</strong> in uncertain environments.</p><blockquote>That attitude of: “I will figure it out.”</blockquote><p>That line carries a lot.</p><p>Because it is not just confidence.</p><p>It is ownership.</p><p>It is accountability.</p><p>It is the refusal to freeze in the face of ambiguity.</p><p>And honestly, the more I think about it, the more I feel this is where leadership really begins.</p><p>Not when things are easy.</p><p>Not when everything is defined.</p><p>But when there is no map, and still, someone is willing to walk first.</p><p>Another part that really stayed with me was when the conversation touched on the difference between <strong>humans and AI</strong>.</p><p>This was such an interesting thought.</p><blockquote>If everything in life was available in absolute clarity, then maybe machines could take over much more of decision-making.</blockquote><blockquote>If every meaningful decision came with complete data, complete information, complete certainty, and complete visibility, then maybe the human edge would reduce.</blockquote><p>But that is not how life works.</p><p>Life is not a spreadsheet.</p><p>Building is not deterministic.</p><p>Leadership is not fully programmable.</p><p>And that is why human judgment still matters so much.</p><p>Because human beings can move through fog.</p><p>Human beings can decide with incomplete information.</p><p>Human beings can sense, interpret, trust, adapt, and move.</p><p>That is a very powerful thing.</p><p>And maybe that is where our real evolution lies too.</p><p>Not in becoming more robotic.</p><p>But in becoming more courageous, more aware, and more responsible with uncertainty.</p><p>Towards the later part of all this, another concept came in that felt quieter, but very important.</p><p>That was around <strong>cognitive rigidity</strong>.</p><p>And I found this deeply relevant, because it is one of those things that can silently stop growth.</p><p>Cognitive rigidity is when we become too attached.</p><p>Too attached to our own ideas.<br>Too attached to our own preferences.<br>Too attached to our own opinions.<br>Too attached to our own way of seeing things.</p><p>And slowly, we stop being open.</p><p>That openness matters a lot.</p><p>Because if vision is about seeing, then rigidity is one of the biggest things that can stop us from seeing.</p><p>You cannot truly grow if your mind has already decided what must be true.</p><p>You cannot become wiser if you are only loyal to what is familiar.</p><p>And maybe that is another part of leadership too.</p><p>Not just having conviction.</p><p>But also having enough openness to keep learning.</p><p>That balance is not easy.</p><p>But it is necessary.</p><p>When I now think back to this KLP session, I do not remember it as just another learning session.</p><p>I remember it as <strong>a session within a session</strong>.</p><p>There was one session happening in the room.</p><p>And there was another one happening quietly through Suresh.</p><p>And if I am being honest, that second one is the one that stayed with me more.</p><p>Because what he was giving us was not just insight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JS07EjqyI9lK4YFDZHbS_w.jpeg" /></figure><p>He was giving us a founder’s lens.</p><p>A way to look at vision.<br>A way to look at action.<br>A way to look at clarity.<br>A way to look at leadership.<br>A way to look at uncertainty.</p><p>And maybe that is the real gift of being around people who have built something meaningful.</p><p>They do not just give you answers.</p><p>They give you a better way to see.</p><p>And once you start seeing differently, you do not go back the same.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fcbbdc28be8" width="1" height="1" alt=""><hr><p><a href="https://culture.kissflow.com/the-session-within-the-session-1fcbbdc28be8">The Session Within the Session</a> was originally published in <a href="https://culture.kissflow.com/">Kissflow Culture | Explore Our Butterfly Effect</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>