Tag: systems thinking

  • The Multipliers of Clarity: How Some People Multiply Business Value

    The Multipliers of Clarity: How Some People Multiply Business Value

    You’ve probably worked with someone like this. They don’t say much in meetings. They’re rarely in a rush. They don’t fight for credit. And yet, when they’re around, everything just seems to work.

    Projects that used to drag start moving. Conversations feel clearer. Teams find rhythm again. No one can quite explain it — but with them in the mix, the system somehow aligns. It’s not charisma or luck. It’s a way of seeing.

    And before you ask — no, there’s no research paper to prove this. It’s something you notice only after years of watching projects rise and fall. Some people don’t just improve things — they multiply them.

    The People Who See the System

    Every workplace has its visible stars — the quick thinkers, the confident presenters, the ones who light up dashboards. But alongside them exist a few who see differently.

    They understand how things connect. They can sense where friction will appear and quietly smooth it out. They see how one rushed decision in design can create two weeks of rework downstream. They notice when incentives in one team silently create conflict in another.

    And to be clear — they don’t all look the same. Some are loud and visible, others are calm and understated. Some lead teams, others lead thinking. This isn’t about personality. It’s about pattern awareness — the ability to step back, connect dots, and act early.

    They might not always fit traditional molds, but they’re far from outsiders. In fact, they’re often right in the center of things — just focused on how the whole system works, not only their piece of it.

    While most people focus on doing more, these people focus on removing what doesn’t need to be done at all. That’s how they multiply productivity — not through more effort, but through better alignment.

    The Compound Effect of Curiosity

    These people rarely start out as the best performers. What sets them apart is how they learn — slowly, broadly, and constantly. They read across worlds — psychology, mathematics, strategy, philosophy, even fiction. Not to collect facts, but to understand how different systems work and fail.

    Over time, this learning compounds. They start to see patterns that repeat everywhere — in behavior, markets, organizations, even themselves. That steady accumulation of insight slowly turns into foresight.

    What looks like instinct from the outside is actually years of absorbed learning — tested quietly, remembered deeply, and cross-applied intuitively. It’s not hearsay. It’s curiosity that has matured into clarity. And when they speak, it sounds like wisdom — not because they’re preaching, but because they’ve lived the pattern before. They don’t theorize. They recall. This is how constant curiosity becomes practical foresight, and reflection turns into something that feels like intuition.

    Their real gift is anticipation. They sense friction before others feel it. They might quietly adjust a timeline, realign two people before tension surfaces, or tweak a process that’s about to break under pressure. Problems don’t reach them — because they’ve already met them halfway.

    When they’re around, everything feels smoother. But that ease isn’t luck — it’s invisible work, built on pattern recognition and foresight. The fires they prevent never make it into reports. Their impact is hard to measure, but impossible to replace.

    A Different Rhythm, a Deeper Impact

    These people don’t always operate at the same tempo as everyone else. They pause where others rush. They ask questions that momentarily slow the room — but those same questions prevent weeks of rework later.

    They think out loud, explore broadly, and sometimes look like they’re moving slower — but they’re seeing further. In a world that prizes speed, they invest in understanding.

    Their process takes longer to show results, but those results last. What looks like detours become shortcuts later. They’re not inefficient — they’re building clarity that compounds. Their curiosity matures over time into a kind of calm precision.

    How to Recognize Them

    You won’t find them through dashboards or quarterly reviews. You notice them in conversation. They make complex things sound simple — not by dumbing them down, but by getting to the root of what matters. Or they connect dots so far apart that you need a moment to catch up.

    They ask questions that stop the room — the kind that shift the discussion from “how” to “why.” They bring energy that steadies, not noise that distracts. And when they’re empowered, the whole organization starts to move with more coherence, calm, and confidence.

    The Edge That Endures

    Tools and technologies will keep changing — mobile, cloud, AI, and everything that follows. But the people who can see systems early will always stay relevant. When tools change, they learn them. When complexity grows, they simplify it. When the environment shifts, they reframe it until it makes sense again.

    The long time they’ve spent learning and crafting their thoughts stays with them for life. It becomes part of their lens — a quiet foundation that doesn’t age, even when everything else changes.

    They bridge what most people separate — logic and empathy, data and meaning, motion and direction. As AI handles execution, these people become even more vital. Because tools can speed up action, but only humans can see the whole system and guide it forward.

    A Closing Thought

    We talk about productivity as if it’s about doing more. But the kind that truly scales comes from people who help everyone do better.

    They turn curiosity into foresight, reflection into quiet wisdom, and learning into momentum that compounds across the system. They make work smoother, smarter, lighter — not because it’s easy, but because they’ve understood the structure beneath it.

    Every organization has them — visible or quiet, new or seasoned. Spot them. Empower them. Then watch your productivity, energy, and delivery zoom upward.

    Because when you nurture the people who see systems early, you don’t just multiply results — you multiply understanding, flow, and business value that lasts.

  • Engineering Managers: Navigating Complexity and Challenges

    Engineering Managers: Navigating Complexity and Challenges

    Engineering Managers (EMs) operate at the intersection of strategy, execution, and culture. Their role is multifaceted, demanding constant negotiation between high-level organizational goals and granular operational realities. To fully grasp the complexity of this role, we’ll examine it through the lens of Prof. Aswath Damodaran’s Classical Firm Structure, which highlights inherent trust deficits and competing priorities in organizations.

    EMs bridge the gap between diverse stakeholders — ranging from HR and product teams to customers and CTOs. This article unpacks the EM’s role across four critical segments: Leadership and Strategy, Internal Teams, External Stakeholders, and Cross-Functional Relationships. Along the way, we’ll identify blind spots, explore challenges, and offer practical insights to navigate this high-stakes role.

    The Classical Firm Structure and the EM’s Role

    Prof. Damodaran’s theory of the classical firm emphasizes the concept of a trust deficit, stemming from the conflicting priorities of various stakeholders. Shareholders and the Board of Directors seek to maximize wealth, driving growth and profitability. Customers demand reliable, high-quality products and services at a fair price. Governments and regulators focus on compliance with laws, regulations, and ethical standards. Banks and investors expect sound financial management to secure returns and ensure repayment.

    When applied to the Engineering Manager’s (EM) role, this model isn’t just about trust — it’s about navigating complexity. The EM’s job involves constant prioritization, balancing trade-offs, and negotiating between internal and external stakeholders. It’s a tightrope walk, requiring exceptional agility to meet these diverse demands without tipping the balance.

    Segment 1: Leadership and Strategy

    High-Level Goal: Align engineering initiatives with organizational objectives while fostering innovation and growth.

    Challenges:

    • Balancing immediate delivery timelines with long-term technical investments like architecture improvements or tech debt reduction.
    • Navigating conflicting signals from leadership — prioritizing short-term ROI while laying the groundwork for future scalability.

    Blind Spots:

    • Over-focus on metrics like velocity or uptime without considering team morale and sustainability.
    • Failure to advocate for technical initiatives in leadership discussions, leading to eventual burnout or system fragility.

    Practical Insight:

    Create a transparent roadmap that incorporates both strategic milestones and operational necessities. Use this roadmap to advocate for technical priorities while showcasing their long-term business impact.

    Segment 2: Internal Teams

    High-Level Goal: Empower teams to deliver quality software efficiently while maintaining morale and collaboration.

    Challenges:

    • Managing diverse personalities and skill sets within the team.
    • Resolving conflicts between product demands and team capacity.
    • Addressing issues like tech debt without demoralizing the team by overloading them.

    Blind Spots:

    • Misjudging the team’s capacity to adapt to rapid changes, resulting in over commitment or burnout.
    • Failing to create psychological safety, which stifles innovation and candid feedback.

    Practical Insight:

    Hold regular retrospectives focused on team health and process efficiency, not just technical output. Proactively communicate trade-offs to product stakeholders to shield teams from unnecessary pressure.

    Segment 3: External Stakeholders

    High-Level Goal: Deliver high-quality products that meet customer expectations while minimizing escalations.

    Challenges:

    • Managing SLA agreements and prioritizing escalations without derailing ongoing work.
    • Aligning customer needs with organizational capabilities and product roadmaps.

    Blind Spots:

    • Over-prioritizing escalations can create a fire-fighting culture, leaving no room for innovation.
    • Lack of visibility into evolving customer needs due to siloed communication with product teams.

    Practical Insight:

    Build strong relationships with customer success teams and encourage direct feedback loops from customers. Use this feedback to preemptively address common issues in future product releases.

    Segment 4: Cross-Functional Relationships

    High-Level Goal: Foster alignment across departments to enable seamless delivery and innovation.

    Challenges:

    • Bridging the gap between technical and non-technical stakeholders (e.g., translating engineering constraints into business terms).
    • Managing dependencies across teams, particularly during large initiatives.

    Blind Spots:

    • Assuming alignment across departments without validating it through regular check-ins or shared metrics.
    • Ignoring process bottlenecks caused by misaligned priorities.

    Practical Insight:

    Effective cross-functional collaboration relies on regular sync-ups to track progress, resolve roadblocks, and ensure transparency. A clear goal owner should align teams, document risks, and address issues promptly. Before release, a go/no-go meeting ensures alignment and readiness. The focus is on consistent communication, accountability, and proactive risk management, and frameworks like OKRs can also be used to achieve these goals.

    Blind Spots Across the Board

    Across these segments, EMs face blind spots that can hinder their effectiveness:

    1. Neglecting Culture: Overemphasizing delivery without fostering a healthy, collaborative culture.
    2. Ignoring Feedback Loops: Failing to build mechanisms for continuous feedback across teams and stakeholders.
    3. Tunnel Vision: Becoming too focused on either technical or managerial responsibilities, at the expense of the other.

    When Organizations May Not Need EMs

    Not every culture or team structure benefits from the presence of EMs. Flat, self-managed teams with strong collaborative norms may thrive without traditional EMs. For example:

    • Startups with highly autonomous developers and direct access to leadership often minimize the need for EMs.
    • Teams working on narrow, well-defined scopes may not require a formal manager.

    However, as organizations scale and complexity grows, the EM’s role becomes indispensable to manage dependencies, align priorities, and maintain momentum.

    Conclusion: The Tightrope Walk

    The role of an Engineering Manager is one of constant complexity and trade-offs. While the trust deficit described in the classical firm structure doesn’t always apply in modern organizations, the challenges of navigating competing priorities remain central to the role.

    By embracing self-awareness, building robust feedback loops, and fostering alignment across teams and stakeholders, EMs can successfully navigate this complexity. Whether in startups or enterprise environments, the EM’s ability to bridge organizational silos and deliver value is what defines their success.

  • The Cost of Misalignment: A Leadership Tale!

    The Cost of Misalignment: A Leadership Tale!

    In a fast-paced world, whether in healthcare or software development, misaligned priorities and poor communication can derail even the most straightforward plans. This story from a hospital ward — modeled after challenges faced in software organizations — offers valuable insights into leadership, communication, and effective problem-solving.

    A Patient’s Choice

    Mr. Tata, an elderly patient struggling with mobility, sought medical advice at a renowned hospital. After a thorough diagnosis, Dr. Banga and Dr. PK — both experienced surgeons — recommended a minor surgery. The procedure was straightforward, with a quick recovery period, and it promised to restore Mr. Tata’s movement.

    Initially receptive to the idea, Mr. Tata later expressed his hesitation to Jassi, the patient care coordinator. He preferred a medication-based treatment over surgery, citing discomfort and unease. While the doctors did not recommend this approach, Mr. Tata insisted on his choice.

    The Administrative Roadblock

    Jassi, empathetic to the patient’s concerns, approached Chaudhary Jagga, the hospital’s administrator, to arrange for Mr. Tata’s admission and start the alternative treatment. However, Jagga was firm: formalities must be completed before any admission or treatment could proceed.

    Despite the urgency, neither Jassi nor Jagga was willing to compromise. The process stalled, leaving Mr. Tata without treatment and the hospital staff in limbo.

    Leadership Intervention — or Lack Thereof

    Hoping for a resolution, Jassi escalated the issue to Dr. Khoya, the Head of Surgery, and Dr. Patel Managing Director of the Hospital. Instead of addressing the core problem — aligning Jassi and Jagga to admit the patient — Dr. Khoya diverted his focus. He instructed the surgeons, Dr. Banga and Dr. PK, to consult an external expert, Dr. Angad, to validate the proposed treatment plan.

    Meanwhile, the rest of the management team, including Dr. Patel, remained silent. Their lack of engagement compounded the issue, leaving Jassi and Jagga in a stalemate and the surgeons frustrated.

    The Surgeons’ Dilemma

    Reluctantly, Dr. Banga and Dr. PK complied with Dr. Khoya’s directive. Dr. Angad reviewed the case and confirmed that the surgeons’ original plan was appropriate. He was also aligned with alternative treatment that both the Dr. has prepared. However, the consultation did nothing to address the root cause: the misalignment between the patient care coordinator and the hospital administrator.

    The Fallout

    • The Patient: Mr. Tata, left untreated, grew increasingly uncomfortable and lost trust in the hospital’s ability to provide timely care.
    • The Coordinators: Jassi and Jagga remained at odds, unable to break the procedural deadlock.
    • The Surgeons: Dr. Banga and Dr. PK felt demoralized, their focus disrupted by unnecessary directives.
    • The Organization: A simple issue spiraled into a web of inefficiencies due to a lack of coordination, engagement, and decisive leadership.

    Key Takeaways

    Engage Proactively: Leadership must actively engage with escalated issues. A lack of response from key stakeholders, like Dr. Patel, left the team to navigate challenges without support.

    Focus on the Core Problem: Dr. Khoya’s decision to consult Dr. Angad diverted attention from the real blocker — the admission impasse. Leaders must identify and address the actual bottleneck.

    Empower Cross-Functional Collaboration: Misalignment between Jassi and Jagga reflects a broader issue of siloed teams. Clear communication and shared goals are essential for smooth operations.

    Avoid Unnecessary Pressure: Redirecting the surgeons’ attention to a redundant validation task frustrated the team and delayed action. Leaders must prioritize tasks that directly solve problems.

    Stay Customer-Centric: At the center of any organization is its stakeholder — be it a patient, customer, or end-user. Processes should serve their needs, not hinder them.

    Conclusion

    This story highlights the dangers of misaligned priorities, poor communication, and disengaged leadership — whether in healthcare or software development. Teams lose focus, stakeholders suffer, and inefficiencies multiply.

    To prevent such scenarios, leaders must:

    • Engage proactively with escalated issues.
    • Focus on solving root problems.
    • Foster alignment and empower teams to collaborate effectively.

    The question every leader must ask is: Are we addressing the right issues, or are we just adding to the noise?

  • Arbitrage: Where Circles Meet

    Arbitrage: Where Circles Meet

    When most people hear “arbitrage,” they think of the stock market — buying something cheap in one place and selling it for more somewhere else. You know, traders in suits, lots of screens, and numbers flying everywhere. But here’s the thing: this idea isn’t just for finance. It shows up quietly in our everyday lives. At its heart, it’s noticing a difference between two things and using it to create value. That difference could be skills, places, ways of thinking, or even moments in time. We all do it, though we rarely call it that. Once you notice it, the world feels different. Gaps aren’t empty—they’re opportunities waiting to be explored.

    Everyday Gaps: How We Use Them

    Often, we do this without even realizing it. A person who speaks two languages might move effortlessly between home and school, feeling at ease in one place and sharp in another. Someone shares a hobby online, not knowing that someone far away would pay to learn it. A family recipe, carried to a new town, suddenly becomes the highlight of community gatherings. Then there’s the kind we do on purpose. The moments when we see a gap and decide to step in. A designer in a small town works for clients in a big city, earning city-level money while enjoying a simpler life. A professional learns a rare skill, knowing it will be useful later. A business owner notices a service that’s common elsewhere but missing locally, and brings it home. Even nature does it. Mangrove trees grow where land meets sea — a place most plants can’t survive. And yet, they find nutrients in the water, shelter fish, and protect the coast from storms. They don’t just survive there—they thrive, taking value from both land and water to create something new.

    The key is noticing it. When we become aware of the “in-between” spaces we inhabit—whether it’s geography, skills, or perspective—we can turn them into advantages instead of leaving them to chance. This applies in parenting, too. Sometimes we mix lessons from our own childhood with ideas from school or culture, giving our kids both guidance and care. And in decision-making, we often use gut feelings and logic together, without realizing it. Noticing these gaps allows us to do it on purpose, improving our choices in life as naturally as using a skill in work.

    Turning Gaps into Lasting Advantage

    Simple gaps don’t last forever. Once others notice, the edge disappears. In the stock market, this can happen in seconds. In life, it might take months or years. Sometimes, though, a gap can grow into a lasting advantage. This happens when the bridge you build becomes more than a connection—it becomes its own little ecosystem.

    Take someone moving from India to the West for work. They use their skills in a new country, but their family and knowledge of home remain in the East. Over time, they become a bridge—sharing ideas, resources, and opportunities both ways. This early advantage grows into a personal “moat.” They’re trusted in both worlds, understand the subtleties of each, and find opportunities that few others do. The original gap—location and markets—was just the start. The lasting advantage comes when this position is strengthened with trust, relationships, and knowledge others can’t copy.

    Being Careful with Gap

    There’s another side. Gaps can be overused or exploited, sometimes harming others. We see this in finance, when repeated trades destabilize markets. In travel, a charming place can lose its magic if too many people visit. In skills, a rare ability can become common overnight, taking away its value for those who relied on it.

    The pattern is the same: taking too much and giving too little back. Real success comes from noticing gaps, using them, and also helping the space grow. Knowing when to step back is as important as knowing when to act. The best gap-users—whether in money or life—sense not only when to move, but also when to wait and invest elsewhere.

    Conclusion

    You don’t need to be a trader to use gaps. You just need to notice differences—between skills, knowledge, or ideas—and see how they might connect. It’s not about always taking advantage. It’s about curiosity. Ask yourself:

    • Where do I unknowingly live between two worlds—and what value does that give me?
    • Where could I choose to build a bridge between differences and needs?
    • How could I turn a short-term advantage into something lasting?

    Sometimes the bridge we stand on is one we stumbled into. Sometimes it’s one we chose to build. Both can be powerful—but the second gives us control. When we look at the world this way, gaps stop being tricks for fast gain. They become a way to see where things are uneven and how we can move through those spaces carefully. Sometimes the bridge is for ourselves. Sometimes it’s for others. But it always starts with noticing the gap—and imagining what could grow there.

    References

  • Constraint as Catalyst: Turning Limits into Launchpads

    Constraint as Catalyst: Turning Limits into Launchpads

    Constraints are often seen as hurdles—obstacles that slow us down or limit our potential. But what if certain constraints, when used intentionally, could act as strategic triggers for innovation? Just as a matchbox doesn’t illuminate a room but sparks the candle that does, constraints don’t solve the problem directly—they ignite the creative response that does.

    In this article, we explore how the strategic use of constraint—whether of time, tools, resources, or information—can unlock breakthroughs. Not as a permanent state, but as a deliberate ignition point.

    Observations from Different Domains

    Across disciplines and geographies, we see a curious pattern emerge: limitation often precedes ingenuity.

    • ISRO’s Cost-Effective Space Missions: ISRO’s Mars Orbiter Mission, Chandrayaan missions, and other projects have consistently demonstrated how tight budgets can drive innovation. These missions were completed at a fraction of the cost of their global counterparts, pushing the teams to optimize engineering and operational efficiency.
    • Athletics: In high-performance sports like football, players sometimes use techniques like “swish and spit”—tasting specialized carbohydrate solutions without swallowing them—to trick the brain into unlocking stored energy, conserving hydration and digestion.
    • Healthcare: Intermittent fasting, far from being deprivation, is now seen as a strategic pause that triggers metabolic and cellular benefits. Temporary lack leads to long-term gain.
    • Architecture: In desert regions, homes use thick mud walls, minimal openings, and natural ventilation—not expensive materials—to keep interiors cool, reducing energy needs without environmental strain.

    These aren’t stories of survival—they’re examples of thriving under intelligent constraint.

    Common Patterns in Constraint-Driven Innovation

    What links these examples?

    1. Boundary-forced Focus: Limits naturally narrow the field, forcing sharper decisions and eliminating distractions.
    2. Emergence of Core Priorities: When you can’t do everything, you’re forced to ask: What truly matters?
    3. Unconventional Problem Solving: Without access to typical tools or time, teams and individuals often invent new approaches.
    4. Simplicity with Depth: Solutions born of constraint tend to be elegant—not complex, but deeply thought out.

    Recognizing these patterns allows us to apply constraint intentionally rather than reactively.

    The Matchbox and the Candle

    Let’s revisit our metaphor. The candle—representing resources, systems, and capacity—can illuminate a space for hours. But it requires a spark. The matchbox—small, focused, intentionally designed—is the enabler. In the same way, a strategic constraint doesn’t replace abundance; it prepares the ground for it. It’s a starter, not a sustainer.

    There are many ways to trigger innovation. But strategic constraint is a powerful and often underused matchbox in your toolkit.

    Applying the Phenomenon Strategically

    Constraints should not be glorified, nor should they be endured endlessly. But when applied strategically and temporarily, they can serve as a powerful lever for innovation.

    • Individuals: Try a time-bound challenge with fewer tools. Limit your resources to stimulate new methods.
    • Leaders: Frame projects with intentional constraints—limited team size, compressed timelines, fewer dependencies.
    • Teams: Hackathons and “sprint weeks” thrive not despite constraints, but because of them.
    • Governments & Societies: Design contests with sustainability or resource-use caps can yield breakthroughs.

    The goal is not to operate in constraint but to use it as a catalyst, just long enough to spark a shift.

    Conclusion: Use Constraint, Don’t Live in It

    Constraint isn’t the goal. It’s not a philosophy of less, nor a moral statement on frugality. It’s a practical tool—a designed environment that forces clarity, focus, and ingenuity. The challenge is not to seek constraint everywhere but to recognize where and when it can act as a matchbox—the spark that lights the candle, allowing sustained success to follow.

    So next time you feel boxed in, ask: What if this box is not a cage—but a matchbox?

    Appendix

  • The Chess of Progress: Business, Stakeholders, & Society

    The Chess of Progress: Business, Stakeholders, & Society

    A recent tragedy in India revealed more than just fear — it exposed the cold mechanics of markets under stress. This essay explores how crises, consumption, and capitalism intersect, raising uncomfortable but necessary questions about ethics, empathy, and the systems we’ve built. No easy answers — just honest reflection.

    A Tragedy That Shook a Nation

    Recently, India experienced a tragic terrorist attack that deeply shook the nation. Fear spread quickly, prompting thousands to flee the affected area. The surge in demand for travel led to a dramatic spike in flight ticket prices — in some cases, they tripled or even quintupled.

    This price hike, fueled by genuine human distress, left many unsettled. It was a stark reminder that in moments of vulnerability, economic forces can operate with indifference — and sometimes even cruelty. The anger was not only over the expense but over the lack of empathy embedded in the system.

    It wasn’t simply about the price increase. It was about the realization that in times of collective suffering, the systems we rely on can operate without humanity.

    The Broader Pattern: Not Just in Crisis

    This indifference extends far beyond moments of public tragedy. Similar patterns are evident across societal behavior and business practices at large.

    In times of market disruptions, companies, even highly profitable ones, often prioritize short-term profitability by laying off employees instead of redeploying or reskilling talent. In these moments, where empathy and long-term vision could guide leadership, short-term financial metrics often take precedence.

    This behavior mirrors our collective energy consumption, where the threat of climate change looms large. Despite the undeniable environmental risks, short-term incentives — such as cheaper energy or immediate growth — dominate decisions, prioritizing convenience over sustainability and ethical responsibility.

    A similar pattern emerges in credit card consumption, where businesses market loans as “gifts,” promoting instant gratification while encouraging spending beyond one’s means. These models profit from debt, burdening individuals who will ultimately face the consequences of living beyond their financial capacity.

    The same dynamic plays out in investing, where short-term trading is marketed as a quick route to wealth. But the ethical dilemma remains: Is it right to treat investing as a game of instant returns, disconnected from long-term value and real-world consequences?

    Just as price surges during fear or layoffs in tough times reflect short-term profit at the expense of humanity, so does reckless credit consumption and short-term trading.

    Introducing the Parties Involved: A Complex Web

    The situation becomes more complex when we try to identify the actors involved. It’s not just a case of villain versus victim; it’s a web of interconnected players, sometimes invisible at first glance.

    • Businesses and Managers: They balance profitability, operational viability, and public trust. In times of crisis, they must decide whether to prioritize the immediate survival of the business or uphold ethical standards, even at the risk of short-term harm.
    • Investors: Often unseen but highly influential, investors push for returns, resilience, and growth — sometimes demanding results over much shorter timeframes. Their expectations shape corporate behavior, which may lead to decisions that conflict with public interest.
    • Customers and Society: Society demands ethical behavior from businesses while also seeking availability, affordability, and convenience. Businesses must navigate the contradiction between market efficiency and humane behavior.
    • Regulators and Judiciary: These guardians of fairness often react to events rather than anticipate them. Regulations tend to follow reality, not foresee it, struggling to keep pace with rapid changes in the market and the ethical dilemmas they create.
    • Lenders and Financial Institutions: These entities fuel economic growth, embedding expectations of financial discipline and return within the businesses they support. But this can lead to a focus on efficiency and short-term profit, often at the expense of ethical considerations.

    Each of these actors influences and is influenced by others, creating a complex system far more intricate than it might initially appear.

    Acknowledging the Complexity: No Easy Answers

    It’s tempting to seek simple answers: businesses should act more ethically, investors should show more patience, society should be more resilient. But the reality is much more complicated.

    Decisions are not just about ethics; they are interwoven with survival instincts, competitive pressures, human biases, and systemic inertia.

    For instance, a business focusing solely on doing good may not survive long enough to continue making ethical decisions. An investor who demands short-term returns may inadvertently create pressures that lead businesses down morally questionable paths. Regulators may act too quickly, stifling innovation before it can flourish.

    These dilemmas are not new. They have surfaced throughout history, each time testing our collective consciousness in different ways.

    This echoes the moral questions raised in All My Sons by Arthur Miller, where characters are confronted with the consequences of decisions made in the pursuit of self-interest — decisions that have devastating implications for those around them. The businessman in the play justifies his actions as necessary for survival, but at what cost?

    Some may dismiss these as overthinking, believing the market will “self-correct” in the end. But for me, this represents a serious attempt to confront these questions — to understand the uncomfortable realities we face, rather than letting cynicism or blind faith obscure our understanding.

    The Questions That Arise

    In the wake of such events, difficult questions arise — and none have easy answers:

    • Is supply and demand fair when desperation distorts choice? When a family flees danger, is it still a “voluntary transaction” in the spirit of free markets, or is it something far more complex?
    • Should businesses act differently in times of human crisis? Where does pragmatism end and empathy begin? Should businesses place human needs above profitability, even if it risks their long-term survival?
    • What role should regulators and society play? Can we create safeguards to prevent exploitation without stifling innovation? Can we balance ethical behavior with market efficiency?
    • As investors and stakeholders, what expectations should we have? Does the relentless pursuit of ROI — faster, bigger, now — inadvertently foster the very issues we later criticize?
    • How do managers navigate these conflicting imperatives? To lead effectively is to survive, but does survival always require compromise on ideals?
    • Is over-optimization hollowing out the human spirit in our systems? In medicine, real estate, and technology, are we optimizing outcomes at the expense of human connection?
    • If the system eventually self-corrects, is the interim damage justified? Does the pain endured before market forces “correct themselves” leave scars too deep for society to heal quickly?

    These are not rhetorical questions. They are persistent, complex, and disturbingly real — dilemmas that reflect a society growing in self-awareness but still fumbling in practical application.

    A Balanced Take — Step by Step

    Human Progress Exists — But Flaws Persist

    Humanity has made remarkable strides. We’ve solved monumental challenges, created life-saving technologies, and transformed economies. But progress is not without its flaws. The unintended consequences of innovation — exploitation, inequality, and environmental harm — often emerge only after the fact.

    Flaws and Short-Term Manipulations — A Reflection of Human Nature

    In theory, supply and demand should balance itself out. But in practice, moments arise when market forces are manipulated by businesses, investors, or individuals. In these moments, the market doesn’t reflect pure efficiency; it reflects human nature: greed, fear, and urgency.

    Take the flight price hikes after the terrorist attack. While increased demand is expected, was the sharp rise in prices justifiable when lives were at stake? The market responded, but did it serve society?

    Maybe Imperfection is a Necessary Correction

    One way to view these imperfections is as part of the system’s natural self-correcting mechanism. The Universe 25 experiment in 1971 gives us a striking example. Researchers provided rats with everything they needed — food, shelter, and safety. At first, the population thrived. But overabundance led to chaos and eventual extinction.

    This suggests that overabundance and market manipulation can lead to breakdowns, forcing society to face uncomfortable truths. These imperfections, though painful, may catalyze necessary change. It takes time — longer than we may like — but systems do eventually find balance.

    Everyone Walks a Tightrope

    At the heart of these dilemmas is a delicate balance that all parties must navigate:

    • Managers must balance empathy and profitability. Short-term cost reduction might be necessary, but long-term human-centered approaches are essential for sustaining trust.
    • Investors push for faster growth and returns, but do these pressures obscure the societal consequences of their investments? Can they prioritize long-term impact over short-term profit?
    • Regulators face the task of preventing exploitation while allowing growth. Can they keep pace with rapid change? And when intervention happens, is it ever too late?

    Conclusion: A Question, Not an Answer

    Ultimately, we are left with more questions than answers. The intricate relationships between businesses, investors, and society cannot be easily untangled — and perhaps, they shouldn’t be.

    It’s easy to criticize businesses, investors, or society for their actions. But the truth is, we all play a part. While assigning blame is tempting, it’s more necessary to understand these issues in their full complexity.

    The pressures businesses, investors, and regulators face are real. They drive decisions that may not always align with our ideals, but they also foster progress — even if it’s imperfect.

    The real challenge lies in how we respond to these flaws. Do we see them as opportunities to learn and innovate, or let them become barriers to progress?

    Perhaps the challenge is not finding the perfect solution, but navigating the gray areas with integrity, compassion, and awareness. As we continue to grow, the questions will remain. And how we address them will shape the future we create.

  • Applying Maslow’s Hierarchy to Engineering Culture: A Thought Experiment

    Applying Maslow’s Hierarchy to Engineering Culture: A Thought Experiment

    Introduction: The Role of Culture in Engineering Success

    Peter Drucker famously said, “Culture eats strategy for breakfast.” As I reflect on this, I can’t help but acknowledge how crucial a strong engineering culture is to success—but the challenge lies in defining and cultivating it in a way that truly aligns with business goals. Over the years, I’ve tried various approaches to building culture, and what I’ve realized is that culture is often treated as something abstract—something we hope will emerge, but not always something we can proactively shape.

    What if we could think about culture-building as a structured, evolving process? What if we could use a framework like Maslow’s Hierarchy of Needs to guide us? This thought experiment isn’t about offering a definitive framework, but about exploring the possibility of applying a proven model from psychology to engineering culture in a way that aligns with both top-line growth and bottom-line efficiency.

    Rather than focusing on gaps, I propose that we could shift the conversation to: How can we build, contribute to, and measure our engineering culture? By re-imagining Maslow’s five levels for engineering teams, we open up a space to explore how we might nurture an environment where engineers can thrive—and where those thriving engineers can deliver real business impact.

    Maslow’s Hierarchy of Needs: A Brief Overview

    Maslow’s theory of human motivation suggests that individuals progress through five levels of needs, from basic survival to self-actualization. In this thought experiment, we look at how this hierarchy might apply to organizational culture. By using this lens, we can think about what we can prioritize in our engineering teams at each level—what’s critical for moving up the pyramid, and how that progress ties directly to performance and outcomes.

    Engineering Culture Through Maslow’s Lens

    Here’s where we begin to play with how Maslow’s five levels could map onto engineering culture—and what that means for business impact. Each level represents a potential opportunity for leaders to foster specific cultural traits.

    Level 1 &2 : Stability & Psychological Safety (Physiological & Safety Needs)

    • Engineering Equivalent: Reliable infrastructure, predictable processes, clear role expectations, job security, and a psychologically safe environment where engineers can voice concerns without fear.
    • Business Impact: If we get this right, we reduce burnout, improve retention, and build a foundation for predictable delivery. Without it, teams struggle to operate effectively, which ultimately slows everything down.

    Level 3: Teamwork & Belonging (Love & Belonging Needs)

    • Engineering Equivalent: What would happen if we are really invested in communication, mentorship, and inclusivity?
    • Business Impact: Teams become more efficient, silos break down, and knowledge sharing accelerates—leading to faster problem-solving and improved product outcomes.

    Level 4: Growth & Mastery (Esteem Needs)

    • Engineering Equivalent: Imagine engineers continuously evolving, with ample learning opportunities, career progression, challenging projects, and regular recognition of contributions.
    • Business Impact: A growth-oriented environment fuels motivation, innovation, boosts productivity, and creates an environment that retains top talent.

    Level 5: Purpose & Autonomy (Self-Actualization Needs)

    • Engineering Equivalent: Here, we explore what happens when teams are truly empowered—given ownership over projects and aligned with the company’s broader vision.
    • Business Impact: Innovation takes center stage, decision-making becomes more fluid, and the impact on customers grows.

    Beyond Level 5: Legacy & Influence (Transcendence Needs)

    • Engineering Equivalent: What if teams contributed beyond the organization—driving industry change, mentoring others, publish research, and making an impact on the broader tech ecosystem?
    • Business Impact: This not only boosts the company’s brand but attracts top talent and positions the company as a thought leader in the industry.

    Steps Engineering Leadership Can Take

    If we were to explore how leaders can guide teams up this hierarchy, these are some actions worth considering:

    1. Foster Psychological Safety – This could look like clear onboarding, open communication channels, and ensuring a developer-friendly environment.
    2. Enhance Collaboration – This might involve mentorship programs, cross-team learning opportunities, and inclusive rituals that promote belonging.
    3. Prioritize Growth – Could we focus more on internal training, career development frameworks, and challenging engineers with real ownership of complex problems?
    4. Promote Ownership – Here, the goal would be to shift decision-making power to teams, reduce unnecessary bureaucracy, and ensure that work aligns directly with business outcomes.
    5. Empower Influence – How can we help engineers contribute to the broader tech community through open-source projects, speaking engagements, and mentoring the next generation?

    Key KPIs to Track & Manage Culture

    Tracking progress doesn’t have to be abstract. If we took this thought experiment further, here’s how we might track cultural development:

    • Retention & eNPS – Indicates psychological safety and belonging. A high retention rate of and an eNPS score indicate a thriving culture of psychological safety and belonging..
    • Collaboration Metrics – Think about pull request reviews, communication patterns, and inter-team interactions.
    • Learning & Growth – Track internal mobility and participation in skill-building opportunities.
    • Innovation Metrics – Count the number of POCs, patents, or open-source contributions to measure creative output.
    • Business Impact – We could track metrics like engineering efficiency, incident response times, and overall developer productivity(cycle time, lead time, bug rate, deployment frequency, etc.)

    Challenges & Alternative Perspectives

    As with any experiment, there are challenges. This model isn’t the ultimate answer. In fact, some organizations might find frameworks like Daniel Pink’s Motivation Theory(Autonomy, Mastery, Purpose) more aligned with their needs. However, applying Maslow’s hierarchy to engineering culture gives us a progressive, structured way to think about cultural priorities and actions—and that could be a helpful starting point.

    Conclusion: An Evolving Model for Culture

    At the end of the day, culture is an evolving system—something we shape through deliberate actions and constant learning. The thought experiment here isn’t about achieving a perfect formula. Instead, it’s about seeing culture-building as a dynamic process—one that we can measure, iterate on, and continuously improve.

    As with any experiment, the framework needs refining. That’s where your feedback, experiences, and insights come in. What has worked for you in shaping engineering culture? How do you approach this challenge in your teams? I’d love to hear your thoughts and feedback as this idea continues to evolve.

  • From Engineering to Investing: Navigating Fear, Greed, and Wild Swings

    From Engineering to Investing: Navigating Fear, Greed, and Wild Swings

    Stock investing can seem daunting, especially for engineers who are used to solving problems with data-driven, structured approaches. But investing is less about following a rigid formula and more about understanding core principles and applying them thoughtfully over time.

    One of the most rewarding aspects of investing is the development of multi-faceted skills that extend beyond the stock market. The ability to analyze data, manage uncertainty, and control emotions like fear and greed, builds discipline and resilience. These skills are valuable not only for financial growth but also for navigating challenges in your career and personal life.

    As engineers, we excel at structured problem-solving, but the stock market’s dynamic, fluctuating nature requires adaptability. Principles like Margin of Safety provide a steady foundation, but success lies in continuously refining your approach and sharpening your decision-making skills. One of the most effective ways to do this is by adhering to a principle that protects you from downside risk: the Margin of Safety.

    Understanding Value Investing and Its Core Principle: Margin of Safety

    Value investing is a strategy that focuses on buying undervalued stocks—essentially purchasing assets for less than their intrinsic value. The core principle of value investing is finding opportunities where the price of the stock is below its true worth, providing a margin of safety against market fluctuations.

    The concept of Margin of Safety ensures that even if things don’t go as planned, you have a cushion that protects you from significant losses. This approach allows investors to mitigate risk by only buying stocks when they are undervalued, which reduces the likelihood of overpaying for an asset.

    By adhering to the principle of Margin of Safety, investors can better balance the emotional extremes that drive stock market movements. This emotional balance is crucial because the stock market is often ruled by fear and greed, which can lead to market mis pricing—valuing companies too highly during periods of optimism and undervaluing them during periods of pessimism.

    Ben Graham’s Approach: A Value Investor’s Framework

    The concept of Margin of Safety is a guiding principle for all value investors, but perhaps no one embodied this better than Benjamin Graham, the father of value investing. He outlined a framework designed to minimize risk and identify undervalued stocks. Some of his key principles include:

    • P/E Ratio of 10 or Lower: Graham recommended buying stocks with a P/E ratio of 10 or below, believing that these stocks were likely undervalued.
    • Stocks Priced 50% Below 52-Week High: Graham also advocated for buying stocks that were priced at 50% or less of their 52-week high, which often indicated that the stock was undervalued due to market overreaction.
    • Diversified Portfolio of 25-30 Stocks: Graham recommended building a diversified portfolio of 25-30 stocks and holding them for 2-3 years, selling once the stock appreciated by 50% or more.
    • Debt to equity ratio of 50% or less: To ensure company has a satisfactory financial position.

    These principles helped investors minimize risk and take advantage of market overreactions, both during periods of fear and greed.

    The Stock Story: Two Companies in the Same Sector

    While Graham’s strategies focus on minimizing risk through concepts like the P/E ratio, diversification, and margin of safety, these principles also highlight how the market’s emotional swings—rooted in fear and greed—can lead to significant mispricing of stocks.

    Let’s explore how these emotions manifest in the real world. Now, consider the story of two companies in the city gas distribution sector. They seem to have a lot in common at first glance, but the market is valuing them very differently.

    Here’s how they compare:

    Article content
    Company A vs Company B

    Company A is more expensive, with a higher P/E ratio and stronger profit margins. Company B is growing faster, with better revenue and earnings per share (EPS) growth. Yet, the market has given Company A a much higher valuation. Why? The answer lies in market emotions—optimism around Company A’s future, despite Company B‘s stronger current performance.

    But here’s the twist: Company A and Company B are, in fact, the same company—Indraprastha Gas Limited (IGL). The figures presented reflect IGL’s performance in 2019 (Company A) and 2024 (Company B). Despite IGL’s strong performance in 2024, market sentiment shifted, causing the stock price to fall by 40% and the P/E ratio to drop—illustrating how market sentiment, driven by fear and greed, can lead to mispricing, even when fundamentals remain strong.

    My Approach

    The emotional swings in the market—fear and greed—have shaped my journey as an investor. Over time, I’ve adapted my strategy, moving from a large, diversified portfolio to focusing on fewer, bigger, and more infrequent bets. This shift reflects my evolving lifestyle and my available time to manage investments. However, the core principles of value investing, especially the Margin of Safety, remain central to my decision-making.

    Here’s how my stock selection has evolved:

    Focus on Fundamentals: I prioritize companies with strong fundamentals—consistent sales and EPS growth, high return on equity/assets (RoE/RoA), and low debt—as these provide a foundation of financial stability.

    Margin of Safety: I look for stocks that are undervalued, e.g low PE multiple, low EV/EBITDA multiple, price to sales, price at multi year low, etc.

    Long-Term Focus: I look for companies that have strong, consistent performance over multiple years. I prioritize companies that show stable growth, strong fundamentals, and the potential for long-term appreciation.

    Risk Management: I diversify my portfolio across various sectors, include a portion in gold as a hedge, and avoid investing in IPOs or companies with significant promoter pledging or high debt levels.

    Despite this shift, the core principles of value investing, particularly the Margin of Safety, continue to guide my decisions.

    Conclusion: Learn, Adapt, and Grow

    The stock market will always fluctuate, driven by fear and greed, but by focusing on the fundamentals and maintaining discipline, you can navigate these shifts successfully. The story of IGL serves as a reminder that market sentiment can change rapidly, but staying grounded in principles like the Margin of Safety helps investors make rational decisions and focus on long-term success. Investing is not just about money—it’s about developing a mindset that leads to growth, both financially and personally.

    Final Thoughts

    The stock market will test your patience, but with the right mindset and approach, you’ll be better equipped to handle its ups and downs. Keep refining your process, and remember: investing is as much about self-discovery and personal growth as it is about building wealth.

    Resources for Further Learning and Tools for Stock Selection

    To dive deeper into value investing and explore stock selection process, here are some valuable resources:

    Books

    1. The Intelligent Investor (Benjamin Graham): The cornerstone of value investing, emphasizing Margin of Safety, intrinsic value, and long-term discipline.
    2. The Little Book of Value Investing (Christopher H. Browne): A beginner-friendly guide that simplifies value investing with practical strategies.
    3. The Little Book of Behavioral Investing (James Montier): Insights on overcoming emotional traps like overconfidence and herd mentality, emphasizing rational decision-making.
    4. The Little Book That Still Beats the Market (Joel Greenblatt): A systematic approach combining high earnings yield and high return on capital to outperform markets.
    5. One Up on Wall Street (Peter Lynch): Encourages leveraging personal insights and thorough research to identify promising stocks.
    6. What Works on Wall Street (James O’Shaughnessy): Data-backed strategies showing consistent success with factors like low P/E and high dividend yield.
    7. The Superinvestors of Graham-and-Doddsville (Warren Buffett): An essay showcasing how Graham’s principles led to consistent success for disciplined value investors.
    8. Poor Charlie’s Almanack (Charlie Munger): A collection of Munger’s wisdom, focusing on mental models, multidisciplinary thinking, and applying rationality to investing and life decisions.

    Tools for Stock Screening

    To apply the principles of value investing and screen for undervalued stocks, platforms like Screener.in are incredibly helpful. With Screener, you can filter stocks based on various financial metrics like P/E ratio, price-to-book ratio, and earnings growth, aligning perfectly with the concepts discussed by Graham.

  • Scaling Software Engineering: A Journey of Continuous Evolution

    Scaling Software Engineering: A Journey of Continuous Evolution

    In today’s world of software development, scaling a team while maintaining quality, collaboration, and agility can be a daunting task. However, by building a well-thought-out structure and continuously adapting it, we’ve successfully scaled our engineering practices. While we leverage agile methodologies, we’ve also tailored them to our unique needs, ensuring we’re not just scaling agile, but scaling software engineering in a way that fits our organization’s vision.

    Our Agile-Driven Structure

    At the core of our scaling strategy is a combination of agile practices and a structure that ensures both autonomy and alignment. We use the Spotify model with modifications to make it work for our context. Our teams consist of developers, product owners, scrum masters, managers, and principle engineers, all aligned with the squad’s goals.

    Managers play a critical role in coordinating and supporting their teams, addressing both technical and interpersonal needs. Meanwhile, principle engineers guide teams on best practices related to architecture and work estimation. The agile teams are responsible for planning and executing work at a regular cadence to consistently deliver results.

    The structure is designed to be flexible yet efficient. Squads typically consist of eight members: six developers, one product owner, and one scrum master. We balance feature development with maintenance to manage tech debt while keeping pace with new features. Each squad focuses on delivering value regularly, ensuring a steady pace while avoiding burnout.

    Proactive Problem-Solving and Continuous Collaboration

    Scaling is not just about executing tasks; it’s about proactively solving problems, collaborating during development, and ensuring alignment before releasing software. This structure empowers us to anticipate challenges and proactively address them, ensuring that we’re not merely reacting to issues as they arise.

    With clear guidelines and regular touch points, we maintain a culture of trust but verify, where code undergoes thorough peer reviews and checks before being released. This practice helps us bake quality into the development process. We also adopt shift-left practices, using GitFlow branching to enforce standards like lints, unit tests, and security checks.

    Fostering a People Centric Culture

    Behind every technical achievement is a team member contributing their best. To support our people, leadership works closely with individual contributors to align their personal aspirations with organizational goals. Our org actively invest in learning and development by offering both time and budget for courses that require time off, and we regularly assess team morale through pulse checks.

    This approach allows us to scale not just software engineering, but also personal growth. Every team member has the opportunity to improve their skills and feel supported in their development journey.

    Building a Culture of Quality and Continuous Improvement

    While we’ve built a robust structure that supports scaling, it’s crucial to acknowledge that mistakes are inevitable—often due to human error rather than flaws in the process. Even the best systems can’t completely eliminate mistakes, especially in a fast-paced environment.

    What we’ve learned is that strong processes and a supportive culture significantly reduce errors and increase our chances of success. Yet, we also understand that no system is perfect. By continuously improving both process and culture, we can minimize errors and learn from them when they occur. Leadership fosters an environment where mistakes are seen as opportunities to learn and evolve, which allows us to adapt more effectively.

    Quality at Every Step

    Ensuring software quality isn’t just about testing late in the development cycle; it’s integrated throughout. Our teams are empowered with a comprehensive testing framework, including unit tests, API automation, end-to-end automation, and manual testing. We’re experimenting with the test automation pyramid to ensure the right balance of testing at each layer.

    Documentation is key to team alignment. We use ADRs, epics, user stories, high-level designs, and README files to ensure everyone is on the same page. As part of our continuous improvement efforts, we’re moving toward a monorepo setup from a multi-repo configuration to improve transparency, ease of maintenance, and documentation accessibility. This shift enhances visibility and collaboration across teams, fostering a more cohesive engineering culture.

    Leadership and Scaling

    As we continue to grow, the role of leadership becomes increasingly critical. Our leadership group operates its own sprint, staying aligned with the teams while proactively addressing challenges, shifting requirements, and team needs. Leadership is deeply engaged in discussions about infrastructure, talent management, and risk mitigation. This collaborative and transparent approach helps us manage scale effectively while prioritizing the team’s well-being.

    The leadership group works closely with the teams, using tools like SWOT analysis and the skill-will matrix to evaluate talent gaps, proactively address risks, and identify opportunities for growth.

    Overcoming Challenges and Growing Together

    While we’ve faced challenges in scaling—such as balancing feature development with managing technical debt or ensuring cross-team collaboration—each obstacle has been an opportunity to refine our processes. For example, we initially found that teams were spending too much time on new feature development, leading to a growing backlog of tech debt. We adjusted by implementing a more deliberate prioritization strategy, ensuring that both new features and debt management were given the attention they deserved.

    As we continue to grow, we must remain agile—not only in our development processes but also in how we adapt our organizational culture. The ability to learn from mistakes and continuously improve is key.

    Conclusion: A Journey of Scaling and Evolving

    Ultimately, our journey of scaling software engineering is one of continuous evolution. We are not static in our approach; we strive to adapt and improve with each iteration. By leveraging agile principles, investing in our people, and maintaining a flexible yet structured process, we’ve built a scalable and adaptable engineering organization.

    Our structure allows us to grow while ensuring that quality, collaboration, and support are always at the forefront. And while we face challenges along the way, we continue to learn and improve—proving that with the right balance of process, culture, and leadership, scaling engineering success is not only possible but sustainable.

    As you embark on your own scaling journey, remember that success lies in continuous evolution—embracing change, learning from mistakes, and investing in both your people and your processes.