Category: Technology & Systems

  • 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.