• Some Days There Is No Recipe

    There are moments when the rules change without asking our permission. Something enters your world unexpectedly, rearranges your priorities, and makes you question what you thought you knew about tomorrow.

    I have been thinking about what it means to lead yourself when you cannot lead the situation. When you cannot fix it. When you cannot control the outcome. When resilience isn’t about overcoming something, but about continuing to live meaningfully alongside it.

    Perhaps that is the hardest form of leadership. Not leading others. Leading yourself.

    For me, this has meant confronting something I never expected to: how easily we can put ourselves into a box labelled “I’m not okay.” Once we’re in that box, we stop living and start waiting. We stop making plans because the future feels uncertain. We begin to believe we have to be okay before we can lead – ourselves, our teams and our lives fully again.

    But perhaps that isn’t true.

    I can be afraid and still be courageous. Exhausted and still find joy. Uncertain and still be present. Not okay, and still okay.

    That realisation led me to write the poem that follows. I began imagining cancer as an unwelcome guest – one who arrived without invitation, took over space in our lives, and refused to leave. A guest we never wanted, and nevertheless learnt to care for. A guest who taught us things we didn’t know we needed: compassion, courage, perseverance, presence. And the discipline to stop asking “Why me?” and instead say, “Try me.”

    Not because we believe we can control everything. But because we can still choose how we show up and that choice, more than any outcome, is what leadership actually is.

    So, this time on LeadershipSpice, there is no recipe. Instead, there is this.

    The Guest Who Wouldn’t Leave

    You came into our lives

    like a piercing arrow – sudden, sharp and unexpected.

    We never invited you

     Yet you walked through the door without knocking,

    without permission, and settled yourself in

    as though you belonged.

    An unwelcome guest.

    A rude, demanding, dominating presence

    who behaved as though you owned the house.

    You thought you would cripple us.

    You thought you would defeat us.

    You thought you would break us –

    our bodies,our minds, our spirit,

    our laughter, our dreams.

    You thought you would turn

    our lives into a waiting room,

    our days into appointments,

    our nights into worry,

    our conversations into whispers.

    You thought, perhaps,

    that once you arrived,

    everything else would become

    less important.

    But we had other plans.

    Despite the trouble you brought,

    We took care of you.

    We learnt your language. We learnt your moods.

    We learnt your demands. We gave you our time,

    our attention,our energy.

    We rearranged our days

    around you.

    We made room for you

    when there was hardly

    any room left to give.

    We even tried

    to make you comfortable

    which seems rather absurd

    when you had made

    our lives so uncomfortable.

    And still you demanded more.

    More patience. More waiting.

    More uncertainty. More courage

    than we thought we had.

    You kept troubling us.

    And then you overstayed.

    Days became weeks.

    Weeks became months.

    Still, you refused to leave.

    You settled deeper

    into our lives,

    as though the invitation

    had been extended indefinitely.

    You never seemed to notice

    the pressure you created.

    The exhaustion. The worry.

    The moments when a smile

    had to be assembled

    before stepping out of the room.

    You didn’t see the tears that were hidden.

    The fears that were swallowed.

    The nights that seemed

    far longer than they should.

    You didn’t see

    how often we said,

    “I’m fine,”

    when what we really meant was,

    “I’m trying.”

    And perhaps that

    was your greatest mistake.

    You mistook our tiredness for defeat.

    You mistook our silence for surrender.

    You mistook our fear for weakness.

    You did not understand

    that people can be afraid

    and still be brave.

    That they can be exhausted

    and still carry on.

    That they can be hurting

    and still laugh.

    That they can be

    not okay and still live.

    Because somewhere along the way,

    you tried to put us

    inside a box.

    A box labelled:

    NOT OKAY.

    Not okay today.

    Not okay tomorrow.

    Not okay until you leave.

    Not okay until everything

    is certain again.

    But we refused

    to live inside that box.

    We discovered

    that “not okay”

    is a moment, not an identity.

    So we stepped outside it.

    We laughed.

    We ate good food.

    We celebrated.

    We met people we loved.

    We made plans.

    We travelled when we could.

    We found joy

    in ridiculously ordinary things.

    We made memories.

    And sometimes,

    you were there too.

    At the edge of the photograph.

    In the background

    of the celebration.

    Sitting quietly

    in the corner of a good day.

    We did not pretend

    you weren’t there.

    We simply refused

    to let you be

    the only thing there.

    You occupied space.

    You did not own it.

    And strangely,

    for all that you took from us,

    you gave us with things

    we never knew we needed.

    You taught us compassion to understand pain

    without asking it to justify itself.

    You taught us tenderness – the quiet kind,

    that needs no words.

    You taught us courage – not the dramatic courage

    of people who know they will win,

    but the quiet courage of showing up

    when you don’t know

    what tomorrow holds.

    You taught us perseverance, to keep going

    without guarantees.

    To find strength in smaller places.

    One morning.

    One meal.

    One conversation.

    One laugh.

    One day at a time.

    You taught us

    to stop postponing joy.

    To stop waiting

    for the perfect day.

    To stop saying,

    “We’ll do it when things are better.”

    Because sometimes

    the imperfect day

    is the day we have.

    And somewhere along the way,

    something inside us changed.

    We stopped asking,

    “Why me?”

    And began asking,

    “Why not me?”

    Then something stronger:

    “Try me.”

    Try to frighten me.

    Try to take away my courage.

    Try to silence my laughter.

    Try to convince me

    that because life is uncertain,

    it isn’t worth living fully.

    Try.

    Because I have learnt

    that courage isn’t

    the absence of fear.

    It is refusing

    to let fear choose

    how I live.

    So yes, Cancer – you may stay longer

    than any guest should.

    You may continue to make demands.

    You may change our plans.

    You may make some days

    harder than others.

    You may even leave scars

    that will never completely disappear.

    But you do not get

    to decide what happens

    inside this house.

    You don’t get

    to decide how much we laugh.

    How much we love.

    How much we celebrate.

    How much life

    we allow ourselves to live.

    You don’t get to turn a family

    into a diagnosis.

    You don’t get to turn a caregiver

    into nothing but caregiving.

    You don’t get to make a woman

    forget that she is more than the person

    who holds everything together.

    You don’t get to take away

    the parts of us that existed before you arrived.

    The dreams.

    The friendships.

    The silliness.

    The music.

    The food.

    The conversations.

    The journeys.

    The joy.

    The person I was before I learnt

    your name.

    That person is still here.

    And perhaps that

    is what you never understood.

    You came into our lives

    expecting to become

    the centre of our world.

    Instead,

    you became a reminder

    of how precious

    the world already was.

    You came to teach us

    about endings.

    We learnt about beginnings.

    You came with fear.

    We found courage.

    You came with uncertainty.

    We found presence.

    You came with pain.

    We found compassion.

    You came expecting

    to break us.

    And instead,

    you revealed

    the places in us

    that could not be broken.

    So stay if you must.

    Make your noise.

    Take your space.

    But know your place.

    You are a guest.

    An unwelcome one.

    A difficult one.

    A guest who stayed

    far beyond your invitation.

    But this is our home.

    These are our days.

    These are our memories.

    This is our life.

    And while you may be

    a part of our story,

    you are not the story.

    You may be

    a chapter we never chose.

    But you do not get

    to write the ending.

    Because the ending

    is not yours to write.

    Until the very last page,

    we will laugh.

    We will love.

    We will live.

    We will have bad days

    and good days.

    We will be frightened

    and brave.

    We will be tired

    and still find joy.

    We will be

    not okay – and still be okay.

    And if you ask us

    what we have learnt

    from having you

    in our lives,

    we will not say defeat.

    We will not say surrender.

    We will not even say

    that we conquered you.

    We will simply say:

    You taught us

    how fragile life is.

    And in teaching us

    how fragile it is,

    you taught us

    how fiercely

    to live it.

    So, Cancer – you came like a piercing arrow.

    You stayed like a rude, relentless guest.

    You thought you had come

    to take something from us.

    But look at us.

    We are still here.

    Still laughing.

    Still loving.

    Still living.

    Still choosing.

    Still saying – Try me.

    A final thought

    We often speak about leadership as the ability to influence people, navigate complexity, drive change and achieve outcomes. But there is another kind of leadership that rarely makes it into leadership frameworks. The leadership required when you cannot change the outcome. When all you can do is decide how you will meet the day. Perhaps that is where self-leadership becomes most real. Not when everything is going well. But when life isn’t. Perhaps the question isn’t always: “How do I fix this?” Sometimes it is simply: “Who do I choose to be while this is happening?”

    That is the question I am still learning to answer.

  • Leadership Needs Time to Marinate

    Recently, I spent two days facilitating a leadership programme for a group of experienced professionals. As I watched the conversations unfold, listened to the questions being asked and observed the expectations participants brought into the room, I found myself thinking about something completely unrelated to leadership. 

    Marination.

    Yes, marination.

    Because the more I thought about it, the more I realised that perhaps leadership development has something important in common with cooking. We often expect transformation to happen while we are sitting in the workshop – much like expecting the flavour of a dish to develop the moment it hits the grill. But some of the most important work happens long before that, and much of it happens when we can’t immediately see it.

    As a facilitator, I walked into the programme with the usual intention of creating a meaningful learning experience. There were frameworks to introduce, conversations to facilitate, activities to create insight and, hopefully, a few moments when participants would see something about themselves or their workplace from a slightly different perspective.

    And there were those moments.

    But I also found myself observing something that I have seen repeatedly in leadership development. People come into a programme with very real workplace challenges, and understandably, they want solutions. They want to know how to deal with the difficult stakeholders, how to manage a challenging team member, how to communicate more effectively, how to become more confident, how to influence without authority, or how to deal with conflict.

    All of these are legitimate questions. But sometimes, beneath the question what we are asking lies another one that is much harder to confront:

    What if the way I am looking at the problem is part of the problem?

    We bring our own recipes into the room

    Every one of us comes into the workplace carrying a personal recipe for how we believe things should work. That recipe is made up of our experiences, our successes and failures, the feedback we have received, the people who have influenced us, our values, our fears, our strengths and the many assumptions we have accumulated along the way.

    The interesting thing is that we don’t usually experience these as assumptions. We experience them as facts.

    If I believe that a good leader should always have the answer, I may find it difficult to say, “I don’t know.” If I have learnt that being assertive gets things done, I may not notice when my assertiveness starts being experienced by others as aggression. If I dislike conflict, I may tell myself that I am being diplomatic when I am actually avoiding a conversation that needs to happen. If I have built my career by being highly dependable and taking responsibility for everything, I may wonder why my team doesn’t take ownership without noticing that I may have inadvertently taught them to depend on me.

    None of these behaviours are necessarily bad. In fact, many of them may have been strengths that helped us succeed. The problem occurs when a behaviour that works in one context becomes our automatic response in every context.

    Over time, our behaviours become habits. Habits become patterns. Patterns become part of our identity. And eventually we say, “That’s just the way I am.”

    That sentence can be one of the biggest barriers to development.

    Because if something is simply “the way I am”, then there is very little reason to change it.

    Knowing your personality is only the beginning

    This is where self-awareness becomes so important, and also why personality assessments can be such powerful tools in leadership development.

    An assessment can help us put a name to something we may have experienced but never quite understood. It can show us tendencies, preferences and behavioural patterns. It can help us understand why we may respond differently from the people around us and why certain situations energise us while others drain us.

    But there is a significant difference between knowing your personality and understanding yourself.

    It is easy to read a personality report and say, “Yes, that’s me.” The harder work begins when we ask, “So what does this mean for the way I lead?”

    If I discover that I am highly analytical, do I recognise that I may sometimes overanalyse when a decision needs to be made? If I discover that I am highly people-oriented, can I see when my desire to maintain relationships stops me from having a difficult conversation? If I discover that I am naturally assertive, can I recognise when that strength is helping me move things forward and when it is unintentionally preventing someone else from being heard?

    Self-awareness isn’t simply the ability to describe ourselves accurately. It is the ability to catch ourselves in action.

    It is that moment when you hear yourself responding in exactly the way you always do and think, “There I go again.” It is noticing the defensive reaction, the need to control, the tendency to withdraw, the urge to interrupt, the assumption you have just made or the conversation you are once again avoiding.

    That moment of recognition is valuable because it creates a choice.

    And choice is where change begins.

    The expectation of the two-day solution

    One of the things I found myself reflecting on during these two days was our expectation that a programme should provide solutions to problems that may have taken years to develop.

    I understand why we have this expectation. If we invest two days in a development programme, we naturally want something tangible in return. We want frameworks, tools, practical answers and perhaps even that wonderful feeling of having finally figured something out.

    But leadership development is not quite that simple.

    A two-day programme can create awareness. It can introduce a new way of looking at an old problem. It can challenge an assumption. It can give someone language for an experience they couldn’t previously articulate. It can create a safe space to practise a new behaviour and discover how difficult it actually is.

    What it cannot do is undo years of conditioning in forty-eight hours.

    It cannot change a deeply embedded mindset simply because we introduced a new model. It cannot turn an insight into a habit without repeated practice. And it certainly cannot do the inner work for us.

    Perhaps this is where we need to change our expectations of leadership development. The purpose of a programme is not necessarily to leave the room with all the answers. Sometimes its real purpose is to leave the room with better questions.

    The workshop is the grill, not the marinade

    And this is where, inevitably, my mind went to food.

    One of the things I love about cooking is that some of the most important work happens before the actual cooking begins. Think about a good Greek Chicken Souvlaki. The final cooking time is relatively short, but the chicken first spends time in a marinade of olive oil, lemon, garlic, oregano and seasoning. The flavours need time to work their way into the chicken before it reaches the grill.

    The grill is important, of course. It cooks the chicken, gives it colour and creates that wonderful charred flavour.

    But the grill isn’t where the flavour begins.

    The flavour begins in the marinade.

    And I think there is something rather beautiful about that as a metaphor for leadership development.

    The workshop is the grill. It is the visible part of the experience: the two days of discussion, activities, frameworks, assessments, conversations and insights.

    But the real development happens in the marination that follows.

    It happens when you go back to work and encounter exactly the situation you were discussing in the workshop. Your colleague challenges your idea. Your stakeholder pushes back. Your team member misses a commitment. Someone becomes defensive when you give feedback. Your instinct is to respond exactly as you have always responded.

    And then you remember the conversation from the programme.

    You pause.

    Perhaps you listen for a little longer. Perhaps you ask a question instead of making an assumption. Perhaps you don’t immediately take over. Perhaps you say what you would previously have avoided saying. Perhaps you recognise that the other person’s behaviour is only one part of the story and that your own response is another.

    It may not work perfectly the first time. In fact, it probably won’t.

    But you notice. You reflect. You try again.

    That is the marination.

    What goes into the leadership marinade?

    If I were to create a Leadership Spice marinade, I wouldn’t need to look very far for the ingredients. They are already at the heart of the SPICE™ model I use in my leadership work: Self-awareness, Presence, Influence, Clarity and Evolution.

    It begins with Self-awareness, because we cannot change what we don’t notice. Without understanding our own patterns, triggers, preferences and assumptions, we can very easily keep repeating behaviours without recognising the impact they have on the people and situations around us. Self-awareness helps us notice, “This is how I usually respond.” And once we can see the pattern, we have a choice about whether we want to continue it.

    But awareness alone isn’t enough. We also need Presence which is nothing but the ability to notice what is happening in the moment rather than operating entirely on autopilot. Presence creates that small but important space between what happens and how we respond. It allows us to pause, listen, regulate our emotions and make a more conscious choice about how we want to show up.

    Then comes Influence, because leadership is ultimately about our impact on others. It asks us to look beyond what we intended and consider what actually landed. How do people experience me? What happens in the room when I speak? Am I creating ownership or dependence? Am I bringing people with me or simply expecting them to follow? Influence reminds us that leadership isn’t only about what we do; it is also about the effect our behaviour has on others.

    Clarity is the next ingredient. Once we become more aware and intentional about our presence and influence, we need to communicate what matters – our thinking, our expectations, our decisions and sometimes the difficult messages that need to be said. Clarity isn’t simply about speaking well. It is about knowing what you want to say, why it matters and making sure the message lands in the way you intended.

    And then comes Evolution – the willingness to keep learning, experimenting and changing. It is recognising that what worked for us yesterday may not necessarily work for us tomorrow, and that leadership isn’t a destination at which we eventually arrive. It is an ongoing process of becoming more effective, more intentional and, hopefully, more authentic.

    But eventually, for the marinade to transform the ingredients, it needs heat, and to me, that heat is discomfort.

    Real development isn’t always comfortable. Sometimes the mirror shows us something we would rather not see. Sometimes we discover that a strength we are proud of has a downside. Sometimes we realise that the behaviour we complain about in others is one we also display under pressure. And sometimes we have to question a belief that has been part of our identity for years.

    That discomfort is not a sign that something has gone wrong. It may actually be a sign that something important is happening.

    The final ingredient is the one that cannot be substituted: time.

    Self-awareness needs time to deepen. Presence needs time to practise. Influence needs time to observe and adjust. Clarity needs time to develop. And Evolution, by its very nature, needs time – because leadership is a continuous journey, not something we ever truly finish.

    That is why I think of SPICE™ not as five competencies to be ticked off, but as ingredients that need to work together along with a little discomfort to activate them and enough time for them to penetrate.

    A two-day programme can introduce the ingredients. It can help you recognise what might be missing from your recipe. It can create the discomfort of seeing yourself differently. It can give you the first taste of what might be possible.

    But the real flavour develops afterwards.

    It develops when you go back to work and catch yourself responding in an old way. When you notice a familiar trigger. When you pause before speaking. When you choose curiosity instead of assumption. When you have the conversation you would previously have avoided. When you experiment with a different way of leading and discover that it works or doesn’t, and you learn from that too.

    Don’t put the recipe card away

    Perhaps that is the biggest reflection I took away from those two days.

    You can leave a programme with ten pages of notes, a personality report, three new frameworks and several powerful insights. You can feel energised and motivated and genuinely believe that something has shifted.

    But then Monday morning arrives. And suddenly it becomes very easy to go back to the same old recipe.

    This is why the real test of a development programme isn’t what you remember when you leave the room. It is what you do when you encounter the same old situation again. So, please allow yourself time to marinade. And because every Leadership Spice story needs an actual recipe, here is the one that inspired this reflection.

    Greek Chicken Souvlaki

    PREP TIME: 15 mins
    MARINATION: 1 hour–overnight
    COOKING TIME: 10–15 mins
    SERVES: 4

    INGREDIENTS

    For the Marinade

    • 500 g boneless chicken, cut into bite-sized pieces
    • 3 tbsp extra-virgin olive oil
    • Juice of 1 lemon
    • 3–4 cloves garlic, finely minced
    • 1 tbsp dried oregano
    • 1 tsp paprika
    • Salt, to taste
    • Freshly ground black pepper

    To Serve

    • Warm pita bread
    • Greek yoghurt or tzatziki
    • Cucumber
    • Lemon wedges
    • Fresh oregano or parsley, optional
    METHOD

    1. Make the marinade
    In a bowl, combine the olive oil, lemon juice, garlic, oregano, paprika, salt and pepper.

    2. Add the chicken
    Add the chicken pieces and toss well, making sure every piece is coated with the marinade.

    3. Let it marinate
    Cover and refrigerate for at least one hour. If you have the time, leave it overnight. This is where the magic happens — the flavours have time to work their way in.

    4. Grill
    Thread the chicken onto skewers and grill or cook over high heat until beautifully browned and cooked through.

    5. Serve
    Serve hot with warm pita, tzatziki or Greek yoghurt, cucumber and a squeeze of fresh lemon.

    And as you enjoy it, think about what the marinade is doing.

  • The Dhansak Principle: The Most Expensive Hiring Mistakes Start with Assumptions

    “The quality of an interview is determined long before the first question is asked.”

    Over the years, I have conducted interviewing skills workshops for hundreds of managers across industries. Some were interviewing for the first time, while others had spent years hiring people and leading teams.

    Yet irrespective of their experience, I noticed something surprisingly consistent. Most interviewers do not struggle because they lack intelligence. They struggle because they are busy. Interviews are squeezed between meetings. Preparation happens at the last minute. The job description is skimmed. Competencies are vaguely understood. Questions are created on the fly.

    And then, within the first ten minutes of meeting a candidate, many interviewers believe they already know whether the person is suitable or not. That is where the problem begins. Because interviews often fail not because of poor candidates, but because of poor interviewing.

    And poor interviewing usually stems from two challenges:

    The inability to probe deeply & the inability to recognize our own biases.

    The Illusion of Understanding

    One of the most common observations I have made while conducting interviewing skills workshops is how quickly interviewers believe they have understood a candidate.

    A few examples are shared. A project is described. A challenge is mentioned. An achievement is highlighted. Within moments, the interviewer begins to form conclusions about leadership capability, stakeholder management, customer focus, or problem-solving ability.

    The confidence with which these conclusions are reached is often surprising. Yet when we pause and examine the evidence more closely, an interesting question emerges: what do we actually know?

    Do we know how significant the challenge was? Do we know the exact role the individual played? Do we understand the decisions they made, the obstacles they encountered, the trade-offs they considered, or the impact they created?

    More often than not, the answer is no. What we have heard is a summary. What we need is evidence.

    The problem is that our minds are naturally inclined to fill in the gaps. We hear a brief description of an achievement and unconsciously create a more complete story. We connect dots that may not exist. We infer competence from confidence, influence from position, and leadership from participation. Without realizing it, we move from observation to evaluation in a matter of seconds.

    This tendency is particularly dangerous in interviews because it creates an illusion of understanding. We believe we know far more about the individual than we actually do. As a result, the interview becomes an exercise in collecting stories rather than uncovering behaviour. The focus shifts from understanding what happened to accepting what was presented.

    This is precisely where effective probing becomes so important. Probing allows interviewers to move beyond assumptions and explore the reality behind the narrative. It transforms broad statements into specific evidence and helps separate perception from fact.

    In many ways, the quality of an interview is determined not by the questions that are asked first, but by the questions that follow.

    The Lost Art of Probing

    If there is one skill that separates average interviewers from exceptional ones, it is the ability to probe. Too often, interviewers ask a question, receive a seemingly convincing answer, and move on. The conversation flows smoothly, but depth is missing.

    The first answer rarely tells the complete story. It is usually a summary of an experience rather than evidence of capability. The real value lies in understanding what actually happened, the role the individual played, the decisions they made, the challenges they faced, and the impact they created.

    This is where many interviews fall short. Interviewers mistake probing for interrogation, when in reality it is simply an expression of curiosity. The purpose is not to challenge the candidate but to understand them better.

    Effective probing helps distinguish participation from ownership, activity from achievement, and confidence from competence. It uncovers the behavioural evidence needed to make sound hiring decisions.

    The challenge is compounded by an overreliance on closed questions, which often confirm facts but reveal little about behaviour. Meaningful insights emerge when interviewers explore context, actions, outcomes, and learning.

    Without probing, interviews collect impressions. With probing, they uncover evidence.

    And in today’s world of polished, AI-assisted responses, that distinction has never been more important.

    In my experience, the quality of a hiring decision is rarely determined by the first question an interviewer asks. It is determined by the curiosity they demonstrate after the answer has been given.

    The New Challenge: When AI Joins the Interview

    Just as interviewers are learning to navigate biases and assumptions, a new challenge has emerged in the world of virtual interviewing. Artificial Intelligence.

    Today, candidates have access to tools that can generate polished responses in real time. Some use AI to prepare for interviews, which is entirely reasonable. Preparation has always been part of the interview process.

    However, the line becomes blurred when candidates begin relying on AI during the interview itself. The challenge is that AI-generated responses often sound impressive. They are often polished, articulate, and well-structured responses that closely mirror what interviewers expect to hear.

    Experienced interviewers often notice that beneath the polish, the answers can lack specificity, personal insight, and the richness that comes from lived experience. This makes probing more important than ever, because while AI can generate an answer, it cannot easily replicate genuine experience.

    Why Smart People Make Poor Hiring Decisions

    An interesting read I often recommend to leaders is The Art of Thinking Clearly by Rolf Dobelli. One of its central messages is both simple and uncomfortable: intelligence does not protect us from bias.

    In fact, some of the smartest and most experienced leaders I have worked with are just as vulnerable to unconscious biases as anyone else.

    Interviews provide a perfect example.

    In a relatively short period of time, we are trying to assess capability, potential, motivation, judgement, values, and fit. Faced with this complexity, the brain naturally looks for shortcuts. We are influenced by first impressions, drawn to people who feel familiar, impressed by prestigious backgrounds, and often tempted to validate our initial opinions rather than challenge them.

    The problem is that once a bias takes hold, it subtly shapes how we listen, what we notice, the questions we ask, and ultimately the conclusions we reach. The interview gradually shifts from a process of discovery to a process of confirmation.

    This is why effective interviewing requires far more discipline than most people realize. The goal is not simply to gather information but to remain objective while gathering it. To recognize when assumptions are influencing judgement. To stay curious when the mind wants certainty. To keep exploring when conclusions would be easier.

    The best interviewers understand that first impressions are only hypotheses, not conclusions. They consciously challenge their own thinking, probe beyond surface-level answers, and look for evidence that supports as well as contradicts their initial views.

    Ultimately, the quality of a hiring decision depends not on how quickly we reach a conclusion, but on how willing we are to question it.

    Moving from Assumptions to Evidence: The Discipline of ORCE

    One framework I frequently introduce during interviewing skills and assessor certification programs is ORCE – Observe, Record, Classify and Evaluate.

    The framework is simple. During the interview, your job is to observe and record. The classifying and evaluating come later.

    Yet this is where many interviewers struggle.

    The moment a candidate begins speaking, the mind starts making judgements. A confident response becomes evidence of leadership. A polished communication style becomes evidence of influence. An impressive achievement is automatically translated into capability. Evaluation begins before sufficient evidence has been gathered.

    ORCE is designed to prevent exactly this.

    It reminds interviewers to separate what they observe from what they conclude. To focus on facts, behaviours, decisions, actions, and outcomes rather than impressions. To remain curious for longer and postpone judgement until enough evidence has been collected.

    This discipline has become even more important in the age of AI. Candidates now have access to tools that can help them craft polished, articulate, and well-structured responses. While these answers may sound impressive, they do not necessarily reflect the depth of the candidate’s experience or capability.

    The antidote is not suspicion. It is evidence.

    Whether the challenge is unconscious bias or AI-assisted responses, the principle remains the same: observe carefully, record diligently, probe deeply, and evaluate only after sufficient evidence has been gathered.

    The real value of ORCE is that it helps interviewers replace “I think I know” with “What else do I need to understand?”

    And that simple shift can dramatically improve the quality of hiring decisions.

    Great Interviewers Stay Curious Longer

    Great interviewing is not about asking clever questions. It is about having the discipline to remain curious.

    The best interviewers prepare thoroughly, take objective notes, and resist the temptation to form opinions too quickly. They understand that every answer is only a starting point, every achievement has a story behind it, and every competency reveals itself through behaviour, decisions, challenges, and outcomes.

    They do not rely on memory alone, knowing that memories are often shaped by impressions and biases. Instead, they capture evidence, probe beyond surface-level responses, and continually test their assumptions.

    Most importantly, they recognize that interviewing is not about validating first impressions. It is about discovering what they do not yet know. Because every candidate is more complex than a résumé, and every hiring decision deserves more than instinct. The most effective interviewers stay curious long enough for the evidence to emerge before deciding what it means.

    Leadership Spice: The Dhansak Principle

    As I reflected on the lessons from interviewing, I realized they are captured perfectly in what I call The Dhansak Principle. A great Dhansak begins long before the cooking starts, with preparation, careful selection of ingredients, and understanding what each ingredient contributes to the final dish. But preparation alone is not enough. A good cook continues to observe, taste, adjust, and understand how the flavours are evolving before deciding what the dish needs next. Great interviewing is no different. It requires thoughtful preparation before the interview, disciplined probing during the interview, and the patience to gather multiple pieces of evidence before reaching a conclusion. The Dhansak Principle reminds us that great hiring decisions are built through preparation, curiosity, and the careful blending of evidence and not through assumptions, first impressions, or the first answer we hear. After all, neither a dish nor a candidate should be judged before their full potential has had a chance to reveal itself.

    Leadership Spice Recipe: Traditional Dhansak

    Before I share the recipe, I must acknowledge my many Parsi friends, through whom I have had the good fortune of discovering and learning this wonderful dish. Over the years, I have enjoyed countless versions of Dhansak, each with its own unique touch, and have come to appreciate not just its rich flavours but also the care, patience, and tradition that go into preparing it. What follows is my version, inspired by those experiences and adapted with a few personal twists of my own.

    Ingredients:

    1 cup toor dal
    ½ cup masoor dal
    1 small brinjal
    1 small sweet potato
    1 cup pumpkin
    1 onion, sliced
    2 tomatoes, chopped
    2 green chillies
    1 tbsp ginger-garlic paste
    2 tbsp dhansak masala (typically a blend of coriander seeds, cumin seeds, dried red chillies, black peppercorns, cinnamon, cloves, cardamom, fenugreek seeds, mustard seeds, and turmeric)
    500 g mutton or chicken (optional)
    Salt to taste
    Fresh coriander

    Method:

    Wash and soak the lentils for 30 minutes. Pressure cook the lentils along with the vegetables, turmeric, tomatoes and green chillies until soft. Blend lightly to create a thick consistency. In another pan, sauté onions until golden brown. Add ginger-garlic paste and cook until aromatic. Add the meat and cook thoroughly. Add dhansak masala and cook for a few minutes. Add the pickle and the jam. Combine the lentil mixture with the meat and simmer gently until all the flavours blend together.

    Garnish with fresh coriander and serve with brown rice.

    Final Reflection

    Dhansak teaches a simple lesson: no single ingredient defines the dish. Hiring is no different.

    A résumé, a first impression, a polished answer, or even a great interview moment can never tell the whole story. The best hiring decisions are made when we resist assumptions, stay curious, and gather enough evidence for the complete picture to emerge. After all, the most expensive hiring mistakes often begin when we mistake one ingredient for the entire dish.

  • The AI-Enhanced Thai Curry Theory of Leadership

    Employee engagement in India is under visible strain.

    According to ADP, engagement levels have dropped to 19% in 2025 from 24% in 2024, marking one of the steepest declines globally. Alongside this, 30% of employees report daily stress, and nearly half the workforce is actively considering a job switch.

    These are not just workforce statistics. They are signals. Signals that something in the way work is experienced is no longer working.

    Employees today are asking for more than compensation and process. They are asking for flexibility, meaning, and more importantly – human connection at work. Yet, many organizations are still operating with structures that haven’t evolved at the same pace.

    This is where the pressure on leadership has fundamentally changed. It is no longer just about delivering results. It is about restoring engagement through human leadership.

    The IDP Paradox: Good Intent, Incomplete Impact

    What I find that in response to growing disengagement, many organizations have doubled down on structured development interventions such as Individual Development Plans (IDPs).

    On paper, this is a strong system. It brings structure to growth conversations. It creates visibility of aspirations. It encourages alignment between employee goals and organizational needs.

    But somewhere between design and experience, a gap appears.

    A significant amount of effort goes into creating templates, running development discussions, and documenting outcomes. Yet when employees move through these cycles, a recurring feedback is that they don’t feel any different. Though the intent exists and the process exists – the impact often does not land. The key reason for this is simple, yet uncomfortable – Leadership involvement is inconsistent, fragmented, or overly transactional. This again goes to show that development does not fail in HR systems but it fails in everyday leadership moments.

    Why Leadership Behaviour Is the Real Intervention

    At the heart of any development conversation are three critical leadership behaviours – authenticity, courage and empathy. When these are missing, even the best-designed IDP becomes a formality and when they are present, even a simple conversation can become transformational. The real opportunity lies not only in redesigning the system further, but in strengthening how leaders show up within it. This is also where AI can enter the picture.

    AI as a Leadership Enabler, Not a Replacement

    AI is already embedded in leadership workflows today without being explicitly named as such.

    Leaders use AI to draft communication, summarize information, structure their thinking, prepare for conversations, and generate ideas. In many ways, it has become a silent thinking partner – helping leaders process complexity faster and work more efficiently.

    Yet, amidst all these applications, one powerful use remains underexplored: using AI as a tool for reflection, self-awareness, and deeper leadership growth.

    However, the one principle that must remain non-negotiable is that AI can support leadership but it cannot substitute it. Because the moment leadership becomes automated, development loses its human depth.

    The value lies in the combination: AI for clarity. Leadership for connection.

    The Deep Layer: Self-Awareness

    Before AI can be used to support employee development, it must first be used to support something even more fundamental and that is Leader self-awareness. Because the quality of any development conversation is directly shaped by the internal patterns of the person leading it.

    • How quickly do they listen vs. respond?
    • What kinds of feedback do they resist?
    • What situations trigger defensiveness?
    • Where do they unconsciously avoid discomfort?

    These patterns often operate below the surface of awareness. This is where AI, interestingly, can act as a mirror.

    Using AI as a Reflection Partner

    Unlike human interactions, AI does not adjust for hierarchy, emotion, or social pressure. It responds directly and without filtering intent based on what is shared with it. But when leaders begin to reflect on situations using AI, something subtle starts to happen.

    A leader may describe a difficult conversation in detail, explain their response and interpretation, and then ask, “What might I not be seeing here?”

    At first, the responses may feel generic. But over time, as the inputs become more honest and specific, patterns begin to emerge. It could be a tendency to close conversations too quickly. A discomfort with disagreement. A habit of interpreting questions as challenges. A need to solve before fully listening.

    And this is where AI becomes interesting. It is not as a replacement for leadership wisdom, coaching, or human connection, but as a mirror that quietly reflects recurring tendencies leaders may not always notice in themselves.

    The more authentic the reflection, the clearer the patterns become. Nothing entirely new but something newly visible and that’s where awareness begins.

    From Self-Awareness to System Impact

    When leaders begin to see themselves more clearly, something shifts externally as well. The IDP conversations become more present and meaningful. Feedback becomes less procedural and more developmental and employees feel seen, not just assessed. And when employees feel seen, engagement begins to rebuild.

    Closing Thought: AI Is Not the Story – Leadership Is

    AI will continue to evolve. Engagement metrics will continue to fluctuate. HR systems will continue to be refined. But the core truth of leadership remains unchanged. People do not disengage from work first. They disengage from how they are led. AI, when used thoughtfully, does not replace that responsibility but it amplifies it. It helps leaders see more clearly – but the choice of how to show up remains entirely human.

    Thai Curry with AI touch

    As always, love to end these blogs with a recipe. This time there’s a touch of AI to this. When I asked AI what to do differently with the curry, it suggested replacing coconut milk with vegetable stock, adding peanut butter for depth and finishing with lime to preserve freshness.

    Then came the interesting part. As I cooked, I realized AI could suggest combinations…but it could not taste. It could recommend balance. But I had to feel when the balance was right. The curry needed slightly more warmth, less sweetness, more basil and less lime.


    This is exactly what leadership with AI looks like. AI can accelerate clarity. It can widen perspective.
    It can offer possibilities we may not immediately see. But leadership, like cooking, still depends on human judgment. Because people are not data points. Teams are not recipes. And culture cannot be automated.

    The best leaders will not be those who reject AI. Nor those who blindly depend on it. They will be the ones who learn how to blend technological intelligence with human sensitivity.

    Just like a good Thai curry. The recipe may come from AI. But the final flavour still depends on the person holding the ladle.

    AI-Enhanced Thai Curry Recipe

    Ingredients

    • 1 tbsp oil
    • 1 tbsp red curry paste
    • 1 cup coconut milk (can be replaced or decreased)
    • ½ cup vegetable stock
    • 1 tsp peanut butter
    • Mixed vegetables (bell peppers, broccoli, carrots, mushrooms)
    • Tofu or chicken
    • 1 tsp jaggery
    • Soy sauce
    • Thai basil
    • Lime juice

    Method

    1. Sauté curry paste in oil.
    2. Add coconut milk and stock.
    3. Stir in peanut butter for depth.
    4. Add vegetables in stages based on cooking time.
    5. Add tofu or chicken.
    6. Balance with jaggery and soy sauce.
    7. Finish with basil and fresh lime juice.

    Serve hot with jasmine rice.

  • Soft Idlis, Strong Leaders: The Quiet Power of Listening

    The other morning, I was making idlis. There is something deeply calming about the process. The batter had fermented overnight, quietly transforming while no one was watching. I poured it gently into the moulds, placed them in the steamer, and closed the lid. And then, there was nothing to do. No stirring. No flipping. No constant checking.

    Just listening.

    The gentle sound of steam slowly building inside the vessel. The quiet rhythm telling you that something is happening, even though you cannot see it. If you open the lid too early, the idlis collapse. If the heat is too high, they dry out. If you ignore the steam, you miss the perfect moment.

    Good idlis require patience. They require presence. They require listening.

    And it struck me that leadership communication is very similar. Listening is not loud. It is not dramatic. But it transforms everything.

    Listening: The Skill Leaders Talk About but Rarely Practice

    In leadership conversations, we often talk about communication. We encourage leaders to be articulate, persuasive, and confident. We admire those who can speak well in town halls, influence stakeholders, and present compelling ideas. And somewhere along the way, communication became synonymous with speaking.

    The leaders who create the deepest impact, however, are often those who listen well. Listening builds trust. It surfaces perspectives that may otherwise remain hidden. It creates psychological safety and encourages ownership. Most importantly, listening helps leaders understand before they decide.

    And understanding is at the heart of meaningful leadership.

    Nelson Mandela: The Power of Speaking Last

    Nelson Mandela was known for his extraordinary listening ability. Those who worked with him often spoke about how he would sit quietly in meetings and allow everyone to share their perspectives, even the most junior members. He would listen without interrupting, absorbing the nuances of each viewpoint. Only after everyone had spoken would Mandela summarize the conversation and gently guide the group toward a decision.

    Mandela often shared that he learned this approach from tribal leadership traditions, where the chief spoke last. The logic was simple yet profound. When the leader speaks first, others begin aligning their views to match the leader’s thinking. But when the leader listens first, people think more independently and speak more honestly.

    Listening, in Mandela’s case, was not passive. It was deliberate leadership. It created trust, encouraged openness, and led to wiser decisions.

    One of the most telling stories about Nelson Mandela’s listening comes from his time during the negotiations to end apartheid. Meetings were often tense, filled with deep mistrust, anger, and fear from all sides. Leaders arrived prepared to defend positions rather than explore solutions.

    In one such meeting, Mandela sat quietly as leaders spoke passionately, sometimes emotionally, about their concerns and fears. Some expected him to intervene early and steer the conversation. But he didn’t. He allowed even those who strongly disagreed with him to speak at length. At one point, a younger leader expressed frustration that progress was too slow and criticized the negotiation approach. Many in the room shifted uncomfortably, unsure how Mandela would react. Instead of responding defensively, Mandela asked him to continue.

    After everyone had spoken, Mandela leaned forward and calmly summarized each viewpoint, including the concerns of those who had criticized him. He acknowledged the fears, the frustrations, and the hopes expressed in the room. Then he said something simple:
    “If we do not understand one another’s fears, we cannot build one another’s future.”

    The tone of the room shifted. People felt heard. The conversation softened. Positions became more flexible. And the meeting moved forward with renewed trust.

    Those who worked with Mandela often said that this was his quiet strength. He did not dominate conversations. He created space for them. And in doing so, he helped transform conflict into collaboration.

    Listening, for Mandela, was not silence. It was leadership in action.

    Satya Nadella: Listening That Transformed Culture

    When Satya Nadella took over as CEO of Microsoft, the company was technically strong but culturally fragmented. Teams were competing internally, and collaboration was limited. Many leaders in this situation might have responded with sweeping announcements and bold directives.

    Nadella chose a different path. He began by listening.

    He spent time meeting employees across levels, hearing their experiences and challenges. He spoke with customers to understand what they valued and what they felt was missing. He engaged partners and stakeholders, gathering insights from different corners of the ecosystem.

    One of the most powerful examples of Satya Nadella’s listening came early in his tenure at Microsoft, when he gathered his senior leadership team for an offsite meeting. Instead of beginning with strategy, numbers, or market share discussions, Nadella did something unexpected. He invited a group exercise on empathy.

    The leaders were asked to read a passage and reflect on how they felt. What followed was telling. Many leaders approached the exercise analytically, focusing on facts rather than emotions. Nadella noticed this and gently pointed out something important – Microsoft had become a company that valued intelligence and expertise, but had lost touch with empathy and listening.

    He then shared a deeply personal story about his son, who was born with severe disabilities. Nadella spoke about how that experience changed him and how he initially focused on “fixing” the situation, but over time learned to listen, understand, and empathize. He spoke about learning to see the world from another person’s perspective.

    The room grew quiet. This wasn’t a typical leadership offsite conversation. But it shifted something fundamental.

    Nadella connected empathy with innovation. He emphasized that if Microsoft wanted to build meaningful products, leaders had to listen – not just to customers, but to each other.

    That conversation became a turning point.

    Leaders began encouraging cross-team collaboration. Silos started breaking down. Conversations became more open. The cultural shift from “know-it-all” to “learn-it-all” began not with strategy, but with listening.

    Nadella later reinforced this message repeatedly that innovation begins with understanding unmet and unarticulated needs. And understanding begins with listening.

    What emerged from these conversations was a shift in mindset. Nadella began emphasizing a “learn-it-all” culture instead of a “know-it-all” one. This seemingly simple shift had a profound impact. Collaboration improved, innovation increased, and employee engagement strengthened.

    Listening, in this case, did not just shape conversations. It reshaped culture.

    Abraham Lincoln: Listening to Dissent

    Abraham Lincoln demonstrated another dimension of listening. He surrounded himself with people who disagreed with him. His cabinet included political rivals, individuals who held strong and often opposing views. Instead of avoiding disagreement, Lincoln encouraged it. He listened carefully to debates, absorbing arguments from multiple perspectives before making decisions.

    This approach helped him navigate one of the most difficult periods in history. By listening to dissenting voices, Lincoln avoided blind spots and strengthened his decision-making. Listening, for him, was not about agreement. It was about wisdom.

    One of the most powerful examples of Abraham Lincoln’s listening came during the discussions around the Emancipation Proclamation.

    Lincoln had already drafted the proclamation that would declare enslaved people in Confederate states free. It was one of the most consequential decisions of his presidency. Many leaders in his position might have simply announced it.

    Instead, Lincoln brought the draft to his cabinet – a group that included political rivals and strong personalities, such as William H. Seward and Salmon P. Chase. He read the document aloud and asked for their views. Some cabinet members supported it strongly. Others were cautious. Seward, in particular, advised Lincoln to delay the announcement. He believed that issuing it at that moment especially when the Union had suffered setbacks might make it appear as an act of desperation rather than strength.

    Lincoln listened carefully. He did not dismiss the advice, even though he had already made up his mind about the direction. Instead, he reflected on Seward’s concern and chose to wait. Months later, after the Union victory at the Battle of Antietam, Lincoln issued the Emancipation Proclamation. The timing gave the decision greater strength and credibility. Lincoln later acknowledged that Seward’s advice had influenced his decision.

    This was listening in action. Lincoln did not surround himself with agreement.
    He surrounded himself with perspective. And by listening to dissent, he made one of the most important leadership decisions in history with greater wisdom and impact.

    Steve Jobs: Learning to Listen

    Steve Jobs, in his early leadership years, was known for his brilliance and intensity. He was also known for dismissing ideas quickly and pushing strongly for his own vision. While this created innovation, it also created friction within teams and contributed to challenges during his first stint at Apple.

    When Jobs returned years later, colleagues noticed a shift. He still had strong opinions, but he listened more carefully. He focused on fewer ideas, engaged more deeply with design teams, and allowed discussions to evolve before making decisions. This evolution helped Apple create some of its most iconic products. Listening did not dilute Jobs’ leadership. It refined it.

    One of the most revealing examples of Steve Jobs’ shift as a listener came during the development of the iMac after his return to Apple. During the iMac development, designers presented multiple prototypes – different colors, shapes, and materials. Instead of immediately declaring his preference, Jobs asked questions. He walked around the models, touched them, and invited the team to explain their thinking.

    One designer later recalled that Jobs spent a long time listening to why translucent colors might make technology feel less intimidating and more approachable for everyday users. This was a different Steve Jobs who was curious, engaged, and willing to explore perspectives.

    Initially, even Jobs wasn’t sure about the bold translucent design. But as he listened to the team’s reasoning and discussed possibilities, he became convinced. The result was the iconic translucent blue iMac which was a radical departure from the beige computers of the time. The iMac went on to become one of Apple’s most successful products and played a major role in reviving the company.

    What changed wasn’t just the design. It was the conversation. Jobs still had strong instincts, but he allowed ideas to develop. He listened long enough for creativity to surface. Listening, in this case, didn’t slow innovation. It made it possible.

    Listening in Everyday Leadership

    In my work with leaders, I often notice that many genuinely believe they are listening. Yet, in reality, they are preparing responses, evaluating ideas, or thinking about the next question. The conversation continues, but the listening is partial.

    I remember working with a senior business leader during a leadership development engagement. He was respected, decisive, and highly experienced. Yet his team consistently gave feedback that he did not listen. His response during our first coaching session was immediate and honest – “I do listen. I just move quickly to solutions.”

    As we explored further, I asked him to reflect on what happened internally when someone brought him a problem. He paused for a moment and then admitted something interesting. The moment someone started speaking, he felt responsible for solving the issue. His mind would immediately begin working on solutions. While the person was still explaining, he was already thinking ahead. He believed that as a leader, he was expected to have answers. Listening, in his mind, meant that he had to respond with a solution. And if he didn’t have one, he worried it would make him appear ineffective.

    Over a few coaching conversations, a deeper fear surfaced. He shared that early in his career, he had built his reputation as someone who solved problems quickly. People relied on him for answers. Over time, that became part of his identity. Slowing down and listening felt risky. What if he did not have the answer? What if silence made him look uncertain?

    This insight changed everything.

    We experimented with small shifts. Instead of responding immediately, he began asking one additional question. Then he began summarizing what he heard before offering suggestions. Sometimes, he simply acknowledged the concern and asked the team member what they thought might work.

    Initially, he described the silence as uncomfortable. But gradually, something interesting happened. His team began speaking more openly. They started bringing more thoughtful ideas. Conversations became richer.

    He later reflected that when he stopped jumping in with answers, his team began thinking more independently. Listening no longer meant solving everything immediately. Instead, it created space for others to explore solutions, take ownership, and contribute more meaningfully.

    True listening requires presence. It requires slowing down. It requires allowing silence.

    Silence, however, can feel uncomfortable. Many leaders feel compelled to fill gaps quickly, fearing that silence may signal uncertainty. Yet, silence often reveals what words do not. A hesitation, a change in tone, or something left unsaid can provide deeper insight than long explanations.

    These are the subtle signals of communication. They are quiet, like steam building inside an idli steamer. But they tell you everything you need to know.

    My Soft Idli Recipe – With Secret Ingredients

    Over time, I discovered that small, thoughtful additions make idlis softer and more flavorful. Two ingredients that I always add are fenugreek seeds and a tablespoon of poha. They work quietly in the background, but the difference is unmistakable – much like listening in leadership.

    Ingredients

    2 cups idli rice
    1 cup urad dal (split, skinless)
    1 teaspoon fenugreek seeds
    1 tablespoon poha (flattened rice)
    Salt to taste
    Water as required

    Preparation Time

    Soaking: 6–8 hours
    Fermentation: 8–10 hours
    Cooking Time: 10–12 minutes

    Method

    Wash and soak the rice in one bowl for 6–8 hours. In a separate bowl, soak the urad dal along with the fenugreek seeds for the same duration. The fenugreek seeds help improve fermentation and add softness to the idlis.

    Just before grinding, soak the poha in a little water for about 5 minutes. This helps it soften and blend smoothly into the batter.

    Grind the urad dal and fenugreek seeds first, adding water gradually to create a smooth and fluffy batter. Transfer it to a large bowl. Then grind the rice to a slightly coarse texture and add it to the same bowl.

    Add the soaked poha and mix everything gently using your hand. Mixing by hand helps incorporate air and supports better fermentation.

    Add salt lightly if you prefer before fermentation, or after fermentation based on your preference. Cover the batter and allow it to ferment overnight in a warm place.

    The next morning, you will notice the batter has risen and become light. Grease the idli moulds lightly, pour the batter, and place them in a steamer.

    Close the lid and allow the idlis to cook in steam for about 10–12 minutes. This is where listening becomes important. The gentle sound of steam tells you the process is working. Avoid opening the lid too early. Allow the idlis to rise quietly.

    Once done, remove gently and allow them to cool slightly before taking them out.

    Soft, fluffy idlis are ready.

    The Leadership Parallel

    Just like fenugreek seeds and poha quietly transform idlis, listening also works quietly in leadership. Curiosity, humility, patience, and empathy are not loud behaviors. But they soften conversations, improve understanding, and create deeper connections.

    Listening allows ideas to ferment. It allows conversations to rise. It creates space for insight.

    Good communication is not about saying more. It is about understanding more.

    Like idlis rising quietly in steam, listening happens without noise. Yet when done well, it transforms conversations, relationships, and leadership.

    Sometimes, the most powerful leadership move is to close the lid, listen to the steam, and allow ideas to rise.

    That is the true spice of leadership.

  • What Kimchi Taught Me About Individual Development Plans

    The other day, I was having kimchi with dinner after completing a full day of Individual Development Plan conversations. It had been one of those long but meaningful days – listening, asking questions, encouraging reflection, and helping people think about their growth.

    As I took the first bite of kimchi, something struck me. Kimchi is not a dish you can make in a hurry. It requires preparation, patience, and time. And suddenly, I started relating how similar that is to Individual Development Plans.

    Showing Up, But Not Always Prepared

    Earlier in the day, I had met several participants for their IDP discussions. Many of them came in open and willing, but not necessarily prepared. Some were still figuring out what they wanted to work on. Others were expecting the conversation to give them clarity. A few were even expecting the coach to help design the entire development journey. This is not unusual. In fact, it’s something I’ve seen across organizations. People don’t resist Individual Development Plans. They go along with them. They attend sessions, engage in conversations, and agree on next steps. But often, the deeper reflection that makes development meaningful has not yet begun.

    The First Step: Preparing the Cabbage

    Making kimchi begins with preparing the cabbage. It is washed, salted, and then left to rest. This resting phase is essential. The cabbage softens slowly, becoming ready to absorb flavor. If this stage is rushed, the kimchi never quite develops the same depth.

    Reflection in Individual Development Plans works the same way. Before goals are discussed, before action plans are created, there needs to be time for individuals to pause and think. What are they experiencing in their roles? What energizes them? Where do they struggle? What feedback have they received? Without this softening stage, development plans often remain surface-level.

    Blending the Ingredients

    Once the cabbage is ready, the spice paste is prepared – garlic, ginger, chili flakes, and other ingredients blended together carefully. Each element contributes to the final flavor. The paste is then mixed thoroughly so every leaf absorbs the seasoning.

    In IDP conversations, this is where feedback, coaching, aspirations, and business context come together. The coach may bring perspective. The organization may bring expectations. But the individual brings their experiences and aspirations. When these elements are thoughtfully blended, the development plan begins to take shape.

    The Quiet Fermentation

    But even then, kimchi is not ready. After mixing, the kimchi is stored and allowed to ferment. Slowly, quietly, transformation happens. The flavors deepen, the character evolves, and over time, something richer emerges.

    Development works the same way. Growth rarely happens in the coaching conversation itself. It happens afterward – when individuals try new behaviors, reflect on outcomes, and gradually build confidence. This quiet, internal fermentation is where real change happens.

    Culture: The Temperature for Growth

    This is also why the way IDPs are introduced in organizations matters so much. If they are driven purely as a top-down process, people participate but may not fully own the journey. Development becomes something that is expected of them rather than something they choose for themselves.

    But when organizations create a culture where growth is valued, where leaders talk about their own development, and where reflection is encouraged, something shifts. People begin to take ownership. The process becomes more meaningful.

    Ownership: Checking the Jar

    The most powerful development journeys I have seen are when individuals return to their plans, revisit their goals, and make adjustments along the way – just like checking on kimchi as it ferments and allowing it to evolve.

    A coach can guide. A framework can support. But development itself cannot be outsourced.

    Individual Development Plans are a lot like kimchi. They require preparation. They need the right ingredients. And most importantly, they need time and ownership for transformation to happen.

    Leadership Spice Recipe: Simple Homemade Kimchi

    Just like development, kimchi is simple in ingredients but powerful in transformation.

    Ingredients

    1 medium Napa cabbage (or regular cabbage if unavailable)
    2 tablespoons salt
    4 cloves garlic, finely chopped
    1 teaspoon grated ginger
    2 tablespoons Korean chili flakes (gochugaru) or red chili flakes
    1 tablespoon soy sauce or fish sauce
    1 teaspoon sugar (optional)
    2 spring onions, chopped
    1 small carrot, julienned (optional)

    Method

    First, cut the cabbage into bite-sized pieces and wash thoroughly. Sprinkle salt over the cabbage and mix well. Let it sit for about 1–2 hours. During this time, the cabbage softens and releases water. This step is important as it prepares the cabbage to absorb flavors.

    Once softened, rinse the cabbage lightly and squeeze out excess water.

    In a separate bowl, mix garlic, ginger, chili flakes, soy sauce (or fish sauce), sugar, spring onions, and carrot. This creates the flavorful paste.

    Now gently mix the cabbage with the spice paste, ensuring every piece is coated well.

    Transfer the mixture into a clean jar and press it down gently. Leave a little space at the top.

    Cover and let it sit at room temperature for 1–2 days, depending on how tangy you like it. Then refrigerate. The flavor deepens over the next few days.

    Like development, kimchi gets better with time.

    Leadership Spice 🌶️

    Development is not something that happens in a conversation.
    It happens in the quiet moments when people reflect, experiment, struggle, and try again.

    Like kimchi, the real transformation is slow, internal, and deeply personal.

    And perhaps that is the real Leadership Spice. Not designing perfect development plans.
    But creating the conditions where people are willing to ferment, evolve, and grow from within.

  • Rising Like a Soufflé: A Woman’s Journey Through Career and Life

    When I look back at my career, I often think of the innumerable stories. What stands out is not the promotions or the achievements. It’s the journey itself. I cherish every challenge, every choice, every small victory, and every moment I doubted myself yet kept showing up.

    Young Mother, Big Dreams and a Tough Start

    I was already working before I got married. My challenges in my career started as a young mother with a 6-month-old baby. My first job was with the hospitality industry. The guilt of leaving a kid at home weighed heavily on me. There were so many instances when I just wanted to quit. Every morning, I hesitated. I wondered if I was doing the right thing. My mother’s voice kept me going:
    “Don’t give in to emotions. Be strong. You are not just building your career but you are shaping your children’s future as well.”

    There were no professional nannies, no extended family support. It was just my husband and me, navigating a world that seemed designed to test us. Domestic help had to be trained, routines had to be established, and endless patience became my constant companion.

    Some days, I went to work with tears hidden behind a smile. Some days, I returned home exhausted. Hospitality was demanding – long hours, rotational shifts, constant pressure but yet I excelled. My work was recognized, and I earned promotions. I learned that perseverance pays, and that leadership begins with showing up, even when it’s hard.

    Second Child, Early Return, and Flexibility

    When my second child arrived, I faced a new set of challenges. Pregnancy and work were demanding. My boss requested, though it was not mandatory, that I return early. He offered flexibility. I could visit home several times during the day. I lived close to the hotel, which allowed me to attend to my newborn. It was a very tough decision for me. I discussed with my husband and we both took charge of managing the kids, household responsibilities, and professional commitments. Those early days taught me resilience, time management, and the art of prioritizing without guilt. I realized that leadership is not just about managing others. It’s about managing yourself under pressure.

    Making Career Choices: Mobility vs. Children’s Education

    A big promotion later required relocation to another city. I stood at a pivotal juncture, knowing that every choice mattered. On one hand, career growth beckoned; on the other, my children’s education and stability were at stake. I chose the latter. Leaving my hospitality career was not easy. However, I knew it was the right choice for my family. It also aligned with my values.

    This was my first lesson in leadership: courage is not only about saying yes. At times, it’s about saying no and staying true to your priorities.

    Retail: Navigating Family Politics

    In my next role in retail, I stepped into a family-owned business. Politics, conflicting opinions, and interference from multiple family members were daily challenges.

    Objectivity and tact became my tools. I listened more than I spoke, assessed situations carefully, and remained consistent in my actions. Slowly, I earned the trust of the Managing Director. Over time, my decisions were respected, even above those of family members.

    It was here that I learned another leadership truth: trust and credibility are built through consistency, fairness, and patience.

    Banking BPO: Breaking Barriers

    Moving into banking BPO brought a new kind of challenge. I inherited a role from a man who refused to give a proper handover. I could have complained, resisted, or waited for someone else to fix it. But I chose to take responsibility.

    I networked with my subordinates, learned from their experiences, and slowly pieced together the gaps. Day by day, I built credibility and established myself as a reliable leader. I took on the role of VP – Learning & Development. This marked a shift in the organization’s approach to leadership appointments.

    Again, in this role, balancing work and home remained challenging. I guided my sons, shared responsibilities with my husband, and navigated office politics. This was a constant reminder that leadership requires not only professional skill but also emotional resilience.

    Consulting and Freelancing: Bold Choices

    After years of climbing the corporate ladder, I made the bold decision to quit and start my own consultancy. Consulting was not easy. I was alone, building teams, managing clients, and establishing credibility without the safety net of a corporate structure.

    It was a time that tested perseverance like never before. I had to be disciplined, resourceful, and patient. My children, now choosing their higher education paths and careers, moved cities. I grew as a leader, a mother, and an individual.

    Today, I thrive as a freelance OD consultant, a grandmother, a mentor, a mother-in-law, and a wife. I am a woman who never shrank from her dreams.

    Leadership Lessons from My Journey

    1. Show Up Every Day – Even when the path is hard or uncertain.
    2. Build Trust Through Consistency – Leadership is credibility in action.
    3. Balance Courage with Care – Career decisions must reflect both ambition and values.
    4. Persevere Through Politics and Pressure – Every organization has challenges; how you navigate them defines your growth.
    5. Celebrate Small Wins – Recognition, mentorship, and small victories fuel resilience.

    Leadership Recipe: Lemon Soufflé

    Life is delicate and layered, like a soufflé. It requires precision, patience, and care. Yet, it rises beautifully when handled with skill.

    Servings: 4
    Prep time: 20 min
    Cook time: 20–25 min

    Ingredients

    • 2 tablespoons unsalted butter (plus extra for greasing ramekins)
    • 2 tablespoons granulated sugar (for coating ramekins)
    • 3 large eggs, separated
    • 1/2 cup granulated sugar
    • 1/2 cup whole milk
    • 1 tablespoon all-purpose flour
    • 1 tablespoon cornstarch
    • Zest of 1 lemon
    • 1/4 cup fresh lemon juice (about 1–2 lemons)
    • Pinch of salt
    • Powdered sugar for dusting

    Method

    Step 1: Prepare Ramekins

    • Preheat oven to 375°F (190°C).
    • Butter 4 ramekins and coat inside with 1–2 teaspoons granulated sugar, shaking out the excess.
    • Place ramekins on a baking tray.

    Step 2: Make the Lemon Base

    • In a small saucepan, heat milk over medium heat until warm (not boiling).
    • In a separate bowl, whisk egg yolks, 1/2 cup sugar, flour, cornstarch, lemon zest, and lemon juice until smooth.
    • Gradually pour warm milk into the egg yolk mixture, whisking constantly.
    • Return mixture to the pan and cook over medium-low heat, stirring continuously until it thickens into a smooth custard.
    • Remove from heat and let it cool slightly.

    Step 3: Beat Egg White

    • In a clean bowl, add a pinch of salt to the egg whites.
    • Beat with a hand mixer or stand mixer until soft peaks form.
    • Gradually add a teaspoon of sugar at a time, continuing to beat until stiff, glossy peaks form.

    Step 4: Fold Whites into Lemon Custard

    • Gently fold 1/3 of the egg whites into the lemon custard to lighten it.
    • Fold in the remaining whites carefully in two additions, maintaining as much air as possible.
    • Be gentle – do not overmix.

    Step 5: Fill Ramekins & Bake

    • Spoon the soufflé mixture into the prepared ramekins, filling almost to the top.
    • Smooth tops lightly with a spatula.
    • Bake in the preheated oven for 20–25 minutes, until soufflés have risen and tops are golden.
    • Do not open the oven door while baking, or the soufflé may collapse.

    Step 6: Serve Immediately

    • Dust lightly with powdered sugar.
    • Serve straight from the oven – delicate, airy, and bursting with lemon flavor.

    Tips for a Perfect Lemon Soufflé

    1. Ensure egg whites are at room temperature for better volume.
    2. Use a clean, grease-free bowl for whipping whites.
    3. Fold gently to keep the soufflé airy.
    4. Serve immediately – soufflés start to deflate as they cool.

    To every woman reading this:

    You don’t need to be fearless, just resilient.
    You don’t need to be perfect, just persistent.
    Your journey, ambition, courage, and care are layers in the life you are building.

    Show up. Keep pushing. Keep rising.
    Your soufflé of resilience will be unforgettable.

  • Leaders, Stop guessing who said it – start tasting the Rasam!

    As a leadership consultant, I’ve facilitated countless 360-degree feedback debriefs. And there’s a pattern I see almost every single time. The leader starts reading the report, nodding along at first. Then a sharp comment arrives. It might be about not being inclusive enough or needing to listen more. Suddenly, the energy shifts. The focus moves away from what the feedback is saying to who might have said it. A developmental opportunity turns into a guessing game.

    The Feedback Paradox

    It is interesting and paradoxical. On one hand, we encourage our teams to give and receive feedback openly as a tool for growth. On the other hand, we create systems like 360-degree reviews that are entirely anonymous. We do this despite knowing that the purpose is development and not evaluation. This contradiction sends mixed signals. Our aim is to promote a culture of psychological safety and direct communication. However, we end up implementing mechanisms that suggest fear or discomfort around honest feedback.

    Anonymity in feedback does have its place, especially where power dynamics or team dysfunctions make it difficult to speak up. But when development is the goal, anonymity can actually dilute trust rather than build it. It creates a veil that makes it harder to have the real conversations necessary for growth.

    Even more concerning is when feedback, especially anonymous, starts to quietly shape decisions about future opportunities. All feedback gives signals. We need to be careful not to let developmental input turn into evaluative judgment. When that line is blurred, people become more guarded. The intent of feedback, which is to enable learning and continuous improvement, gets lost. If we truly want to create a culture of trust, we need a more open feedback model. This approach also supports growth. It should be the kind we’d want our teams to give each other.

    Feedback Should Be Like Rasam

    Which brings me to the kitchen, where I’ve learned many leadership lessons, often with a ladle in hand. If feedback were a dish, I’d say it should be like rasam.

    Rasam is one of those simple, humble recipes that packs a powerful punch. It’s clear, bold, and restorative. You know what’s in it – tamarind, pepper, garlic, coriander, and you can taste each ingredient distinctly. It doesn’t hide or pretend but it does wake you up. Just like great feedback. When feedback is transparent, you don’t need to “decode” it. You can simply take it in, reflect, and grow. But when it’s anonymous, it becomes like drinking rasam blended into a grey soup. This soup has no texture or clarity and leaves a lingering aftertaste of suspicion.

    Rasam recipe for clear feedback

    Here’s my go-to rasam recipe – spicy, soulful, and straightforward. Just like how feedback should be.

    Ingredients:

    • Tamarind pulp – 1 tbsp (or a small lemon-sized ball soaked in warm water)
    • Tomatoes – 2, chopped
    • Garlic – 4 cloves, crushed
    • Black pepper – 1 tsp
    • Cumin seeds – 1 tsp
    • Mustard seeds – ½ tsp
    • Curry leaves – a few
    • Asafoetida – a pinch
    • Coriander – for garnish
    • Salt – to taste
    • Water – 2.5 to 3 cups
    • Ghee or oil – 1 tsp

    Instructions:

    1. Crush pepper and cumin together. Keep aside.
    2. In a pot, add tomatoes, tamarind water, crushed garlic, salt, and 2.5 cups water. Bring to a boil.
    3. Add the crushed pepper-cumin mix. Let it simmer for 5–7 minutes.
    4. In a small pan, heat ghee. Add mustard seeds, curry leaves, and a pinch of asafoetida. Let it splutter.
    5. Pour this tempering into the rasam. Garnish with coriander.
    6. Serve hot — preferably with steamed rice or sip it solo like a feedback cleanse!

    A Bit of History

    Rasam is a centuries-old South Indian dish, originally known as “milagu thanni” (pepper water). It was traditionally made with tamarind, black pepper, and local herbs. It was prized not just for its flavor but also for its medicinal properties. Rasam was meant to warm you up. It clears your sinuses and aids digestion. It can even revive you when you are feeling off-balance.

    Each region and household has its own version, some add garlic, some don’t; some use dal, others keep it light. But what unites them is rasam’s clarity and boldness. You can taste every ingredient. Nothing is hidden, nothing masked.

    Final Spoonful: Leading with Clarity

    If you’re a leader reading this, here are a few pointers:

    • Don’t just receive feedback, invite it.
    • Don’t just analyze it, absorb it.
    • And if you want open cultures, start with yourself. Ask your teams for feedback that isn’t hidden behind systems.

    We don’t need more layers in our rasam, or our leadership.We need clarity, courage, and a little bit of spice.

  • Qubani Ka Meetha and a Lesson in Communication

    One of the most unforgettable moments from my early days in the hospitality industry came during a grand banquet function. Everything was going smoothly. The décor was elegant, the guests were arriving on time, and the kitchen had outdone itself. The final course of the evening was a Hyderabadi classic. It was Qubani ka Meetha, carefully prepared. It was beautifully garnished with fried cashew nuts.

    The dish was picked up from the kitchen and placed on the dessert counter. The aroma and presentation were perfect – or so we thought.

    The first guest, a kind and graceful lady, helped herself to a bowl. She took a spoonful and paused. Her face showed a flicker of surprise – not disgust, just confusion. She was too polite to make a scene. Instead, she quietly called the banquet manager aside. She requested him to taste it.

    To his horror, the dish wasn’t Qubani ka Meetha at all. It was tamarind pulp which was meant for the kitchen, definitely not the dessert counter. Somewhere in the rush, a container had been mislabeled or misidentified, and the wrong dish had been sent out.

    The manager quickly apologized, corrected the mistake, and brought out the actual dessert. The evening was saved, but it left a lasting impression on me.

    The Takeaway: Communication & Responsibility

    In hospitality, like in many other industries – clear communication and checks at every level are vital. One small slip-up in the kitchen or a missed confirmation from the manager can lead to embarrassment and unhappy guests. It’s not just about doing your own job well, but making sure the entire team is aligned. The chef, the manager, the service staff – everyone must communicate effectively to ensure the guest experience is seamless.

    So, What Is Qubani ka Meetha?

    Qubani ka Meetha is a traditional Hyderabadi dessert made from dried apricots (called qubani in Urdu). The dish originated in the Mughal era. It blends the rich flavors of dried fruit with a simple, elegant preparation style.

    The apricots are soaked and simmered. They are sweetened and often topped with fried nuts and fresh cream. My personal favorite is a scoop of vanilla ice cream.

    It’s a dessert that doesn’t rely on fancy techniques -just quality ingredients and patience.

    Simple Qubani Ka Meetha Recipe

    Ingredients:

    • Dried apricots (qubani) – 250 g
    • Sugar – 100–120 g (adjust to taste)
    • Water – enough to soak and cook
    • Cashew nuts or almonds – fried, for garnish
    • Optional: vanilla ice cream or whipped cream for serving

    Instructions:

    1. Soak the dried apricots in water overnight (or at least 6–8 hours).
    2. Remove the seeds (you can break them open and use the kernels for garnish if you like).
    3. Cook the soaked apricots in the same water on low heat until they soften completely.
    4. Add sugar and simmer until it blends well and forms a thick compote-like consistency.
    5. Let it cool slightly before serving.
    6. Garnish with fried cashews or almonds.
    7. Serve warm or chilled, ideally with a scoop of vanilla ice cream.

    Final Thought: That one banquet night taught me more than just kitchen protocol. It reminded me that details matter. The simplest things, like double-checking a label, can be the difference between a disaster and a delight.

    And as for Qubani ka Meetha – get it right, and it’ll never disappoint.

  • Leadership Bites

    Just Like Canapés

    When we think of leadership, we often think of visibility. Big decisions. Strategy decks. Townhalls. Announcements that echo across the organization. I’ve worked with many teams. When I look back at the moments that truly shaped the culture, they were rarely dramatic. They were small. Almost invisible. And yet, they changed everything.

    For me, bite-sized leadership is about those small acts that don’t need to be noticed by anyone. They aren’t designed for applause. They aren’t posted on social media. They are not even always recognized as “leadership.” And yet, they quietly tell people that you matter most.

    That is where culture is actually built.

    The 30-Minute Ritual That Became Culture

    During COVID, like many leaders, I was concerned about output. But more than that, I was concerned about emotional distance. Cameras were off. Energy was lower. Conversations were transactional. People were delivering, but they were not necessarily connecting.

    So I started something simple. Every week, for thirty minutes, we met with no agenda and no work talk. We called it “Fun Time.” Some days we played light online games. Some days someone shared a childhood memory. Some days we simply laughed about routine stories and memories from the past.

    There was no strategic objective written behind it. I wasn’t thinking about engagement metrics or retention numbers. I just felt that we needed something human. And, in that process, we discovered so much about each other.

    Months later, I began noticing subtle shifts. Meetings felt warmer. Disagreements were handled with more ease. People were more patient with each other. Collaboration became smoother. That small weekly ritual, repeated consistently, had quietly shaped how we showed up together.

    It didn’t come from a policy. It came from presence.

    That, to me, is bite-sized leadership.

    Coffee Conversations That Change Trajectories

    Some of the most powerful leadership moments don’t happen in formal reviews. They happen over coffee. Or during lunch. Or in the few unstructured minutes before a meeting begins.

    I have worked with many leaders. They take twenty minutes after lunch to simply check in with someone from their team. Not to discuss deliverables or review targets, but to just connect.

    At first, people are surprised. But gradually, they begin to open up. A parent’s health issue. A child’s exam anxiety. Personal fatigue that hasn’t yet become visible in performance. Adjustments are made early. Support is offered informally. Burnout is prevented before it escalates.

    This is not a retention strategy. It is leadership presence. People stay not because they are managed well but because they feel seen before they feel stressed.

    A Letter That Spoke Volumes

    When I first heard about how Indra Nooyi led during her tenure at PepsiCo, one story stayed with me. She wrote letters to the parents of her senior executives, thanking them for raising exceptional leaders. Just pause and imagine that.

    In the middle of running a global corporation, she took the time to acknowledge the families behind her leadership team. That letter was not a strategy shift. It did not alter market share overnight. But emotionally, it must have landed deeply.

    At dinner tables across the world, parents would have read those letters aloud. Pride would have filled those homes. And the executives themselves would have felt valued in a way that went beyond performance metrics.

    That is bite-sized leadership. A small gesture. A profound imprint.

    The Calm Conversation After Failure

    In sport, we often celebrate aggressive, fiery leadership. If you observe someone like Rahul Dravid, you see a different texture of leadership. This is especially true in his role mentoring young players.

    He is known for sitting quietly with players after difficult matches. No dramatic speeches. No public criticism. Just calm, thoughtful questions. In those moments, he is not just correcting technique. He is building confidence. He is normalizing learning. He is telling a young athlete that one bad day does not define them.

    Those small, repeated conversations build resilience over time. They are not loud. But they are transformative.

    Shifting Culture One Meeting at a Time

    When Satya Nadella became CEO of Microsoft, much has been written about the strategic transformation he led. But what fascinates me is the behavioral shift he modeled. He encouraged curiosity. He asked more questions. He listened more than he spoke. He nudged the culture from “know-it-all” to “learn-it-all.”

    Culture did not change because of one memo. It changed because in meeting after meeting, he demonstrated a different way of showing up. Over time, that behavior cascaded.

    Leadership is contagious. But so are small behaviors.

    The Three-Minute Pause

    I once read about a senior surgeon who had a simple practice before every surgery. He would pause with his team for a few minutes, not just for procedural briefing, but to check in.

    Sometimes that pause surfaced fatigue. Sometimes it clarified an overlooked detail. Sometimes it simply grounded the team. Three minutes. That’s all. And yet, those three minutes prevented errors and strengthened trust.

    What the Makanai Taught Me About Leadership

    There is a lovely Japanese series called The Makanai: Cooking for the Maiko House. It is gentle, unhurried, almost meditative. It revolves around a young girl who cooks for maiko, an apprentice geisha in a traditional house in Kyoto.

    What struck me most while watching it was not the elaborate meals. It was the small ones. The quiet plates that never made a grand announcement but carried deep meaning.

    There is a scene where leftover bread crusts are not discarded. In fact, they were used to celebrate the success of the maiko. They are carefully fried and lightly dusted with powdered sugar. Suddenly, what was ordinary becomes a small delight. Waste becomes a moment of sweetness. Isn’t that leadership too? Taking what feels like a leftover moment in a busy day and turning it into something warm. A five-minute appreciation. A quick check-in. A light joke when energy is dipping. Nothing dramatic. Just a small dusting of sugar on an otherwise ordinary day.

    In another moment, the cook prepares mini egg sandwiches – simple, soft, almost childlike in their comfort. They are not served because of a festival or a major achievement. They are served to celebrate something small. A personal milestone. A quiet success. An effort that deserved acknowledgment.

    Celebration does not always need scale. Sometimes it needs noticing. In organizations, we often wait for big wins to celebrate , the quarterly numbers, major deals, awards. But what if we celebrated the equivalent of a mini egg sandwich moment? The junior team member who handled a difficult client call for the first time. The colleague who spoke up despite being hesitant. The team that stayed steady through a tough week.

    Bite-sized leadership works the same way. It does not seek visibility. It seeks sustenance.

    Fried crusts turn into a sweet treat. Mini egg sandwiches become a quiet celebration. Small leadership acts transform ordinary days into meaningful ones. And perhaps that is the deeper lesson. Leadership is not always about the grand banquet. It is about the daily meal that keeps people going.

    Why Bite-Sized Leadership Works

    Grand gestures inspire. They create momentum. They signal direction. But they are episodic.

    Bite-sized leadership, on the other hand, is rhythmic. It is woven into daily behavior. It is sustainable because it does not demand dramatic energy. It demands consistency.

    A simple appreciation at the start of a meeting. A gentle check-in before diving into tasks. Giving credit in a room where it matters. Protecting a team member from unnecessary escalation. Admitting, “I don’t know.”

    None of these will make headlines. But repeated over months and years, they create psychological safety. And psychological safety, more than any competency framework, shapes performance.

    The Canapé Philosophy

    If leadership were a meal, we often try to serve something exotic and heavy. Such meals are appropriate for visioning sessions, strategy resets, and annual gatherings. However, daily leadership is more like canapés. Small, thoughtfully assembled bites that are easy to absorb and pleasant to revisit.

    They do not overwhelm. They invite. That is how small leadership acts work. They nourish without exhausting.

    Recipe: Cheese, Pineapple & Cherry Canapés

    Since I cannot mention them without sharing the recipe, here it is – simple and timeless.

    All you need are cubes of firm cheese, fresh pineapple cut into small chunks, and glazed cherries. Take a toothpick. Skewer the pineapple first, then the cheese, and crown it with a cherry. Arrange them neatly on a plate and serve chilled.

    That’s it. No elaborate preparation. No complicated technique. Just balance. Intention. A little colour.

    A Gentle Reflection

    When I reflect on the teams I have led and worked with, I rarely remember the big presentations. I remember the laughter during those Friday sessions. and the quiet coffee conversations.

    So the question is not, “What grand leadership act will I perform this quarter?” The better question is, “What small, human act will I repeat consistently?”

    Because culture is not built in marathons. It is built in mindful mouthfuls. And often, the smallest acts leave the deepest imprint.