Ajay Nair

Digital dashboards have always bored me but something was different this time, When I joined as Principal P3M for SQEP at MOD. Where we transformed chaos into clarity: • 100+ moving parts • 50+ stakeholders • 20+ critical paths • 1 source of truth Everyone talks about data. Few talk about data storytelling. Turning a 50-page report into a 5-tile dashboard that: • Predicted delays before they happened • Spotted risks before they materialized • Saved countless alignment meetings • Made decisions 3x faster The best dashboards don't just show what's happening. They show what's about to happen. Tech stack? Sure. But it's the insight stack that matters.

5

Anthropic opening a Bengaluru office is a go-to-market decision. A country office exists for four jobs: sell, partner, support, govern. I learned this slightly late in my HP days. When I saw “HP India Sales Pvt Ltd” on the offer letter, I thought what on earth does that mean. Over the course of my time there, I understood it wasn't about legal trivia or a 'national sales office'. It was the operating unit with accountability, leadership depth, and global mobility because India was a real business. It also taught me the practical bit people miss: local clientele needs local execution. Security and legal reviews, contracting, SLAs, procurement, DPDP comfort, integrations, escalation. That’s why the partner set matters. Anthropic is already pointing to India-facing adoption through: • Air India Limited (Claude Code for faster custom software delivery) • Cognizant (rollout to a large employee base; modernisation and client delivery) • Swiggy (MCP integration for commerce workflows inside Claude) I see Anthropic gunning for the level of operational maturity I observed at HP. Anthropic also claims India is one of Claude’s biggest markets. If that’s true, the bottleneck isn’t model quality. It’s execution at scale. Irina Ghose's hire is the tell: they’re building the customer and partner machine, not just adding engineers. Dev hubs build capability. Country orgs build outcomes. I am betting that for Anthropic, It is latter first. Dev hubs will happen. What blocks AI rollouts most in your org: contracting, security review cycles, integrations, or change management?

4

One for the Road ☕️ Magh Mehra’s first client escalation did not come with warning. It came with a subject line marked “Urgent”. Deadlines were questioned. Decisions were challenged. Tone was sharper than usual. For a moment, she felt small. Escalation feels personal when you are new. Like a spotlight on your mistakes. She discussed with her manager. She started drafting a reply. Then stopped. She reread the mail again. Removed emotion. Kept facts. Picked up the phone instead of hiding behind text. The call was not easy. But it was clear. That morning she learnt something powerful. Escalations are not attacks. They are pressure tests. And pressure does not break you. It reveals how you lead. Before you step into work today, ask yourself When things escalate, do you react Or do you rise Until next sip…

7

Layoffs are not sudden. The email comes suddenly — the decision never does. In today’s corporate world, headlines of thousands being laid off don’t just reflect economics — they reflect a new truth: Loyalty may be personal, but decisions are organizational. And very often, before the formal mail arrives, subtle signals start appearing. Many ignore them… until they can’t. 🚩 Red Flags Employees Must Not Miss Leadership suddenly changes tone — distant, formal, guarded. Once-important meetings exclude you, decisions move without you. Key projects quietly shift to others. Pressure to relocate or return-to-office knowing your constraints. Contract employees silently disappear. Micromanagement or sudden “performance focus” begins. HR becomes unusually process-strict & policy-driven in tone. These behaviors don’t always mean layoffs — but they do mean priorities have shifted, and you might not be one of them anymore. In such times, remember: ✅ Never get emotionally married to your job — get committed to your skills, learning, and network. ✅ Build a parallel identity — beyond your visiting card & job title. ✅ Save aggressively, spend consciously, prepare quietly. ✅ Stay future-relevant — especially with AI and strategic thinking. ✅ And above all — stay mentally strong. Getting laid off doesn’t reduce your value. It only changes your direction. -A Reality Check We once believed hard work and loyalty guaranteed safety. Today, relevance, agility, and visibility do. Show up. Upskill. Stay visible. Stay prepared. 🕊️ A Note to Leaders Layoffs may sometimes be unavoidable — but dignity, transparency, and compassion are always a choice. How people exit speaks louder about leadership than how they were hired. 🌱 Final Thought Work with dedication — but build yourself with strategy. Because in today's world: Security is not in a position — it’s in the person. Change becomes painful only when preparation is absent. Stay learning, stay evolving — always. #CareerTruth #CorporateDecoded #WorkRealities #FutureSkillsTalk #WorkplaceSignals #CareerIntelligence #LayoffSignals #LeadershipLens

206

15 Comments

A few days back, I was suddenly added to a new project call — and the follow-up discussion with key stakeholders was scheduled in just 1 hour. What I had: - RFP - The submitted proposal - Old BRDs, LLDs, query logs - Domain documents, past communications... A whole bunch of heavy documents — and no one from the team available to give a quick handover. Yet, in the next call, I was expected to: - Understand the context - Know what we’re building - Define the next steps I knew I couldn't go through everything in time, so I decided to prepare smartly, not exhaustively. Here's what I did: - Started with the objective of the RFP - Glanced over the proposal – focused on the architecture diagram, tech stack, and solution summary - Searched for keywords: “Assumptions” – to know the conditions we’ve built this on “Dependencies” – what we’re waiting on “Out of Scope” – to avoid scope creep - Scanned the query log to understand the unresolved points This gave me enough context and confidence to walk into that meeting, hold the conversation, and align on immediate action items — without a full download from the team. In moments like this, it’s not about reading everything — it’s about knowing what to read and why. Would love to know — how do you handle such last-minute project immersions? #ProductManagement #SmartWork #BusinessAnalysis #StakeholderManagement #CriticalThinking #DecisionMaking #PMLife #Consulting

17

2 Comments

"Sir, we're just glorified code monkeys here." The words hit me like a punch. Two years ago, I walked into a pharma GCC in Bangalore. The team was running reports, supporting analytics from halfway across the world. "We're basically glorified code monkeys," one engineer told me quietly.   Last month, I visited the same GCC. The same engineer was presenting AI-driven real-world evidence models directly to their global CEO. India wasn't just supporting anymore—they were leading.   This isn't an isolated story.   Across 1,900+ GCCs in India, we're witnessing the same transformation: → A retail GCC moved from ETL coding to architecting customer data platforms  → A tech GCC shifted from implementing roadmaps to co-creating global product features  → A fintech GCC evolved from process execution to owning entire innovation mandates   The pattern is clear: Coders → Creators  Followers → Leaders Cost centers → Value engines   50% of new GCCs now position themselves as innovation hubs. The talent war isn't about finding more coders anymore—it's about finding creators who think "WHY" before "HOW." The GCCs making this leap will own the next decade. The ones clinging to the old playbook will become footnotes.   Which story is your GCC writing?   #GCC #Innovation #TalentTransformation #LeadershipHiring #CEOs #AI

86

1 Comment

What No One Tells You About Managing Projects (Until You are Neck Deep in One) Sometimes, the real lessons show up in muddy boots, delayed approvals, or a call that says: “Wait… was that in scope?” So here is what I started doing: Writing field notes, for the things no one warns you about in project kickoff. Field Notes from the Project Frontlines Observations. Missteps. Adjustments. All from the commercial side of real-world execution. #1. “Verbal commitment” is a myth. Everyone nods. Then forgets. Unless it is documented, it did not happen. Send the recap. Every time. Not to cover yourself, but to align expectations. #2. Scope creep does not need a meeting invite. It walks in through casual chats and “quick asks.” Politeness does not mean vagueness. Protect your boundaries early, or spend twice the time fixing them later. #3. The most dangerous phrase is “almost done.” It creates comfort when clarity is needed most. Always ask: What is done? What is blocked? What is still undecided? “Almost” is not a status, it is a stall. #4. Logistics is not Leadership. Getting the rig on-site is not enough. What matters: Did it move us closer to the intended impact? Tasks are part of the job, but outcomes are the real responsibility. #5. Vendor relationships grow in the gaps. Procurement is easy when things are on track. But when the timeline slips or specs change, that is when trust is built. How you show up in those moments defines future collaboration. #6. Progress updates can become project smoke. Plenty of activity. Very little traction. Do not just list what is happening, tie it to decisions, risks, and forward motion. If it does not drive clarity, it is noise. #7. The biggest misalignment? Everyone thinks they are aligned. That is the trap. That is why I reframe meetings like product reviews: Clarify intent, validate outputs, and confirm readiness. I do not pretend to have it all figured out. But these field notes have saved more timelines, conversations, and contracts than any dashboard. What is one quiet project lesson that changed how you lead? Let’s share the ones that do not make the status reports, but shape every outcome. Follow M Usman Arshad for grounded reflections where project delivery meets product thinking. #ProjectLeadership #ProductThinking #LessonsFromTheField

13

13 Comments

I’ve heard Bengaluru has a traffic problem. But to my surprise, this traffic has given me more time to think especially in the moments between meetings, conversations, and decisions that don’t yet have clear answers. Some of my clearest thinking here hasn’t happened in conference rooms or over scheduled calls. It’s happened in the back of auto-rickshaws, watching the city move slowly while my thoughts finally catch up. When you’re stuck in traffic, you’re forced to pause. And when you’re in an auto, you’re not in control of the steering wheel either. That combination creates space space to replay conversations, question assumptions, and think honestly about what you’re building and why. I’ve had more real conversations in autos than in meeting rooms. Conversations about fear, about money running out, about whether the thing I’m building will actually work, and about why I chose this path in the first place. Bengaluru has a quiet way of shaping people. It doesn’t rush you toward certainty. It lets you sit with ambiguity long enough for clarity to emerge naturally. Over time, you realise something important: Bengaluru doesn’t just build businesses. It builds builders. People who learn to think long-term while operating in short bursts of chaos. People who keep building even when nothing feels fully figured out yet. This city doesn’t hand you confidence. It gives you time time to think, time to doubt, and eventually, time to commit anyway. And somewhere between traffic signals and wrong turns, a simple thought starts to feel believable: This might actually work. If you’re building in Bengaluru, you know exactly what I mean.

4

During a late-night discussion with my mentor and leader on how I can become a better consultant, one reference stood out — the movie Margin Call. Over the weekend, I watched it on YouTube and I couldn’t help but reflect on a few learnings that felt extremely relevant in the world of consulting. 1. Models don’t collapse overnight. Assumptions do. 2. Risk is rarely invisible. It’s often uncomfortable to acknowledge. 3. Escalation isn’t about hierarchy. It’s about timing and clarity. 4. The toughest decisions are not technical. They are judgment calls under uncertainty. What stood out most was this: The most valuable people in the room weren’t the smartest. They were the ones who could simplify complexity, ask the hard questions early, and take ownership when answers were incomplete. A reminder I’m taking forward: Consulting impact isn’t about being right in isolation, but about helping leaders act before being right becomes too late. #Consulting ———- I post my perspectives here at Rishab Arya. Curiously learning about what makes systems and people resilient.

28

1 Comment

Adding People ≠ Faster Delivery in Technology Projects. Lessons for MSMEs In one of my consulting engagements, I introduced a tech partner to a mid-sized corporate and joined the initial discussions. The client was insisting on a fixed date implementation. They had already implemented a tech solution which was not fully functional. They were facing challenges in intra-department integration and the workflow wasn’t seamless. They wanted the system to be redesigned using some custom applications and ensure full connectivity. Digital transformation exercises demand proper understanding of processes, workflows and long-term goals. The tech solution was poorly implemented in Phase 1. So one has to really understand what went wrong and not make the same mistake. In the discussions, the tech partner explained the challenges of reworking the system and set milestones that were practically achievable. I also suggested that they stick to these milestones and not give in to unrealistic timelines. Rushing would only mean repeating old mistakes. This is where many MSMEs go wrong too. Many owners assume you can accelerate delivery or cut down lead time simply by adding more resources. But technology doesn’t work that way. Hasty implementation creates more problems than it solves. It also often increases costs. Digital transformation is not about brute speed. It is about clarity, phased execution, and discipline. For MSMEs, the lesson is simple - define the larger vision, break it into milestones and progress steadily. That’s how MSMEs can turn digital transformation into real and lasting growth. Ganapathy Subburathinam #MSME #DigitalTransformation #Growth

27

3 Comments

While hiring, I at times, give case study to create GTM plan for teleportation services (Delhi to SF in 1 second). Most miss that when services fundamentally reshape, business models and use cases evolve too (theaters to YouTube, magazines to social media, Fax to Whatsapp/email). I read an interesting Substack from a16z on similar lines: The future of the web is the history of YouTube. It mentions, how back in 2006, the world already had so much video content (cable/cassetes), how could there possibly be any commercial demand for even more? We now know, in hindsight, that the world was actually short video 15 years ago. The web democratized creation, “anyone” could build. But it wasn’t until LLMs that the definition of “anyone” changed from “developers” to “literally anyone with an idea and a coding agent.” Which also implies that products with smaller TAMs and higher retention (because of niche needs) can now be brought to market. Five years from now, we might look back and realize that the "world was short software", because the only people equipped to build it were engineers. In other words, this is the YouTube moment for the rest of the internet. Infact if you see a significant portion of our generation has aspirations of being a professional YouTuber or TikToker. LLMs enable an entirely new kind of creative persona who might want to build and monetize app ideas. The most successful apps will come from individuals with existing distribution and communities; people building "unboxing videos, but software."

34

4 Comments

It's unreal and uncommon that someone just worked in one company throughout her career for 16 years, without changing or switching companies or careers 🫠 A very rare scenario which I came across while I discovered Moulshri via Amit, working as an Assistant Marketing VP at Zycus, and for her, it is the only company where she worked, learned, experimented, upskilled and built relations over the last 16 years. Usually, we see people in Marketing jobs often change careers to explore and learn new things, but for Moulshri, it was like "When I can learn and experiment with everything here, why shall I change the job?" Perspective which left me wondering how larger companies are built over the years, keeping aside the product, funding and everything else, it's about People who work with you for decades to grow the company. During the conversation, we discussed a lot of things around ✅ Why marketing is ultimately about problem-solving, not platforms ✅ How long-term careers are built through learning, not job hopping ✅ Why attitude and curiosity matter more than technical skills ✅ The role of trust, proof, and relationships in modern B2B marketing ✅ How AI and automation should support marketers, not replace thinking ✅ Common mistakes founders and teams make while launching products ✅ Why selling value matters more than selling features ✅ How marketing, product, and sales must align to win markets ✅ What young marketers often misunderstand about growth and success And the major question was - What actually builds long-term success in B2B marketing tools or thinking? We also discussed how B2B marketing has evolved across regions, why events and relationships still outperform cold outreach, and how marketers can stay relevant by developing judgment, creativity, and a deep understanding of customer problems even in an AI-driven world. Listen to the entire episode on Impactables with Rishav's YouTube Channel (Link is in Comments), also tag or refer someone you know whom I can invite next on my channel.

111

9 Comments

15 minutes. One call. A complete GTM shift. Last week, I hopped on a strategy call with a healthcare diagnostic startup in Bangalore. They had zero structured GTM. Just figuring things out as they went. Their model? Simple but manual. Connect with doctors. Doctors refer patients. Doctors earn commission. Business grows. But scaling from Bangalore to Chennai and Delhi? That's where they were stuck. Here's the lesson: You don't need a perfect system. You need a repeatable one. Manual processes work until they don't. Growth demands structure. Here's what we mapped out in 15 minutes: 1. Scrape doctor directories (Google Maps, Practo, etc.) 2. Identify which tests give highest ROI and which doctors refer those tests 3. Target doctors in serviceable areas (entire city since it's doorstep diagnostics) 4. Filter doctors by ratings to prioritize outreach 5. Segment approach: high-priority famous doctors get in-person meetings or handwritten notes, others get personalized messages 6. Follow up consistently 7. Repeat the playbook This is a high-level framework, not a technical breakdown. Think of it as a skyscraper view - the key moves that matter, not every execution detail. A structured, scalable process they can replicate across cities. The Head of Sales Ops loved it. They're going implementing it. Sometimes you don't need months of planning. You need clarity on what to do next. Have you ever had a conversation that completely shifted how you approach growth?

8

The Biggest Gap in GCCs: Built in India. But Not Decided Here. The Agency Problem. After working closely with GCC leaders across sectors, one pattern keeps surfacing. What holds most GCCs back is not talent, scale, or execution quality. It is simpler and more limiting. Most GCCs still do not get to decide. This matters now because AI has changed how value is created. Earlier, GCCs were rewarded for reliability and scale. If systems worked and releases shipped on time, decision making could sit elsewhere. AI has broken that comfort. AI does not reward effort. It rewards judgment. And it exposes where decisions are slow, fragmented. The Problem: Only about 10–15% of GCCs operate with real agency today. The rest are capable, busy, and constrained. 1) Autonomy is mistaken for agency. Teams control how work gets done, not what gets decided. Problems arrive pre-defined. 2) Execution is strong, but ownership is weak. Activity is measured. Outcomes are not. 3) Decisions sit elsewhere. Roadmaps, funding, and risk are decided offshore. Accountability stops at delivery, and when outcomes fall short, the reasons get lost. The impact: In an AI-driven world, this gap becomes expensive. Decisions slow down. Accountability blurs. Innovation stays shallow. Teams work harder but struggle to explain real business impact. The solution: Agency grows through practical shifts, not culture decks. 1) Own problem spaces, not backlogs. GCCs accountable for business outcomes typically see 20–30% faster delivery as teams make trade-offs locally. 2) Move decision rights deliberately. Clear cost and risk boundaries reduce approval cycles by 30–50% and remove time-zone delays. 3) Design governance for decisions. High-performing GCCs replace review forums with decision clarity, cutting coordination overhead and speeding execution. 4) Measure outcomes, not output. Outcome-based metrics increase trust with global leaders and improve retention of senior talent. 5) Accept mistakes as the cost of relevance. Centres with local accountability course-correct weeks faster because learning stays close to decisions. What this looks like in practice: 1) A global consumer and retail enterprise The India GCC owned a core digital commerce platform and decided feature priorities around seasons and promotions. Decisions stopped waiting for HQ, releases moved faster, and global launches stayed on track. 2) A data-driven supply chain organisation The India centre owned demand forecasting outcomes, not dashboards. Models reached production faster, forecast accuracy improved, and business teams actually used the insights. In both cases, the shift came from : the right to decide, paired with accountability for results.GCCs with agency help shape strategy. The rest will keep building at scale. But they will not be the ones deciding. And that is the biggest gap. #GCC #GlobalCapabilityCenters #Agency #DecisionMaking #EnterpriseAI #AIFirst #GCCStrategy #Leadership #IndiaGCC #FutureOfWork

65

11 Comments

"Dhano abhi naachee nahi hai" (Dhano hasnt danced yet) I heard this statement in a learning program. The year was 2010, the facilitator was K Srini, and the program was on designing performance management systems. Let me explain what he meant: This was an open program and so had professionals from many companies. There were few participants from Meru Cabs - which at that time was doing very well and was the poster child of entrepreneurship. They were doing everything right - solving a customer pain point, bringing structure to an unstructured industry segment, improving the lives of cab drivers, etc. In the program the participants from the company were presenting their PoVs with an air of finality till Srini said the above line. Look what happened to Meru. Not that Srini predicted it but businesses need to understand that they have to be agile and that competition or disruption can come from anywhere. They need to be scanning the horizon, listening to all views (internal/external), analysing data, and strategizing to future proof - everyday. If they dont, they risk obsolescence or "Dhano's dance"!! I dont know if Srini remembers making this statement but it stayed with me all these years and I have often used it to caution business leaders. This is also how learning programs shape participants and their thinking. For the global audience: Dhano is a character in one of India's iconic movie called Sholay. In the movie she is forced to dance on broken glass to save her boyfriend from being killed by Gabbar (the bad guy). #leadership #leadershipdevelopment

29

4 Comments

When I visit different drone companies in Bangalore for product demos, I notice a recurring pattern: talent mobility is extremely high, with many professionals cycling between the major drone firms. This constant churn creates an odd sense of discomfort—both as a customer and as a consumer. 1/ Sales familiarity across companies: Almost every sales employee seems to know their counterparts elsewhere. Customer details and needs are casually passed around, which strips away the freshness of being treated as a “new” customer. 2/ Preemptive customer service pitches: If I’ve had a poor experience with one company, the next sales representative already knows about it. They emphasize customer service heavily, but because they’re aware of my history, it undermines the purpose of approaching them for a fresh perspective. 3/ Lingering bias as a consumer: If I disliked the service at one company, I subconsciously carry that bias forward. It doesn’t help that the new company’s staff often turn out to be acquaintances or ex‑colleagues of the previous team. I recognize this may be a personal bias. Yet for a disgruntled customer, trust is rebuilt either through compensation or by starting afresh. When the new experience feels like a continuation of the old one, it inevitably spoils the chance to restore confidence.

9

2 Comments

You know the IPO party’s heating up when Ashish Kacholia is on the guest list—and the bouncers are called “GMP 21%”. 🧠 Insight: Vikran Engineering, a B2B infra player, just dropped a chunky Rs 772 crore IPO. Not just another brick in the wall—anchor investors are in, and pre-IPO placements hint at serious institutional FOMO. Remember, Kacholia doesn’t just show up for the snacks. 📉 Problem: Retail investors have been burnt before by “hot” IPOs. Zomato’s sizzle, Paytm’s fizzle—we’ve all seen that movie. GMP whispers can disappear faster than your DMAT login during peak hours. 📊 Stat: This IPO’s grey market premium is making noise at 21%. But here’s your reality check: according to Prime Database, 1 in 3 hyped IPOs in India underperform the Nifty 50 after 12 months. “Strong listing” ≠ “strong holding”. 🔍 Unseen truth: Most headlines will shout about the GMP, but few highlight that 60%+ of proceeds are earmarked for debt reduction and working capital. Translation: the business wants breathing room, not just expansion fireworks. ✅ Founder POV: The founders claim this is a “growth unlock moment.” But as we saw with recent infra IPOs (like Kaynes Tech), sustainable returns hinge on order book visibility, not just anchor backing. Mini-framework: Don’t Just Chase the GMP Sizzle • Ask what % of IPO proceeds drive real growth vs. patching old holes • Track anchor investors’ lock-in periods—are they in for a sprint or a marathon? • Compare sector peers’ post-IPO runs—momentum or mirage? • Dig into order book CAGR, not just pre-IPO headlines Final thought: If you’re only in it for the listing pop, remember—stock markets have a long memory (and an even longer list of one-hit wonders). 💬 How do YOU separate real value from IPO hype? Drop your playbook below. #IPO #Investing #VikranEngineering #AshishKacholia #StockMarket #Finance #GMP #IndiaBusiness

2

3 Comments

Abhimanyu broke into the Chakravyuha with courage… But incomplete knowledge cost him everything. That story isn’t just mythology. It’s a strategy warning. In today’s world of #drone #swarms, ISR pipelines, and #AI-driven reconnaissance… even a single missing layer of intelligence can collapse an entire system — just like the gaps inside the Chakravyuha. That’s why I revisited India’s oldest defence science — the Vyūhas. And what I found shocked me. The same principles that shaped formations like: 🔹 Chakra Vyūha (360° perimeter control) 🔹 Garuda Vyūha (wide-front sweeping reconnaissance) 🔹 Krauncha Vyūha (V-shaped long-range efficiency) 🔹 Kurma Vyūha (shielded multi-layer defence) 🔹 Mandala Vyūha (spiral tracking & encirclement) …are the exact geometries we need for modern #drone #swarms. --Multi-layer coordination. --Adaptive formation shifts. --Distributed intelligence. --Gaps sealing dynamically as threats evolve. Everything ancient strategists mastered, #AI can now bring to life. I explored this idea in depth and published two new blogs (links in comments). Not as mythology. But as a future ISR strategy framework. Now I want to hear from you: -- Can ancient battlefield formations inspire next-gen #AI defence? -- Could Vyūha-based swarm intelligence become India’s next leap in ISR? Your view matters — genuinely. Let’s talk in the comments.

181

22 Comments