An engineer sent me a Slack message with a complex architectural question.

I didn’t even blink. I typed out a three-paragraph solution, hit enter, and felt that hit of dopamine. “I’m a helpful leader,” I told myself.

Five minutes later, it hit me. I had just stolen his job.

I didn’t give him guidance. I gave him an instruction. I didn’t help him grow I just used him as a keyboard to execute my own thoughts.

I was treating leadership as a Noun a position of “The Answer Man.” I had forgotten the Verb.

The Quiet Crisis of the “Order-Taker”

We talk about “Efficiency” and “AI Velocity” like they are the ultimate goals.

But look at your team’s eyes during the next Standup. Do they look like owners?

Or do they look like they’re waiting for the next ticket to tell them they still have a job?

When we provide every answer, we create Moral Technical Debt.

The team stops owning the outcome. They stop being Authors. They become Clerks.

If the system crashes at 2:00 AM, a “Clerk” looks for the manual. An “Author” knows how to fix it because they lived the logic.

How to Practice the Verb: 3 Living Use Cases

To reclaim agency, you have to stop being the hero. Here is how I’ve started practicing the “Verb” of Yielding in the wild:

1. The “Dangerous” Slack Pause

• The Scene: A junior dev pings you: “The API is throwing a 500, what should I do?”

• The Old Way: You check the logs and tell them the fix.

• The Verb: You wait 15 minutes. Even if you know the answer.

• The Result: 60% of the time, they ping back: “Found it! It was a config mismatch.” You didn’t solve a bug; you built a person’s confidence.

2. The “Context-Only” Brief

• The Scene: You need to migrate a database.

• The Old Way: You write a 5-page spec detailing the exact steps.

• The Verb: You write a 1-page “Problem Brief.” You define the outcome (Zero downtime, <50ms latency) and the constraints (Budget, Time). Then you ask: “How would you handle the data integrity?”

• The Result: They might choose a path you didn’t think of. Now, it’s their migration. They will fight for its success in a way they never would for yours.

3. The “AI-Review” Pivot

• The Scene: You see a Pull Request that looks suspiciously “perfect” (clearly LLM-generated).

• The Old Way: You LGTM (Looks Good To Me) and merge.

• The Verb: You leave one comment: “The AI chose a recursive approach here. Tell me why that’s better than an iterative one for our specific memory constraints?”

• The Result: You aren’t “policing” AI you are reclaiming the engineer’s Agency. You are inviting the human back into the pilot’s seat.

The Soul of the Machine

Leadership isn’t about being the smartest person in the room. It’s about creating a room where everyone is invited to be smart.

When you practice the Verb of yielding space, you aren’t being “lazy.”

You are being essential. You are protecting the soul of the people who build the thing.

Are you leading a team of creators, or a team of executors? The difference is in the space you leave between your words.

Who am I?

I’m Diamantino Almeida, and I’ve spent my career at the intersection of high-growth engineering and strategic leadership.

From scaling technical teams to advising CTOs and Founders, my focus is on “Leadership as a Verb“, the idea that leading is an active, evolving practice, not a static title. Having navigated the shifts from manual infrastructure to cloud, and now to Agentic AI, I’m dedicated to helping the next generation of engineers find their footing in a world that is moving faster than ever.

Beyond advisory, I’m an active Top global 9% *mentor on *MentorCruise, where I help developers and leaders bridge the gap between “writing code” and “delivering business value.”

For more insights on leading through the AI shift, follow Practicing the Verb. This is where I write specifically for leaders, offering tactical suggestions, navigating tech-business friction, and sounding the alarm on the hidden risks that slow down growth.

In the early hours of a Tuesday morning, a core payment processing system for a mid-market SaaS platform collapsed. The on-call engineer, bleary-eyed and fueled by caffeine, pulled up the repository to trace the failure. They found a sophisticated block of logic efficient, sleek, and entirely unfamiliar.

They checked the git blame. The code had been committed six months prior, but the “author” hadn’t actually written it. It was the result of a complex prompt interaction between a developer and an LLM. When the engineer tried to debug it, they realized a terrifying truth: Nobody on the current team actually understood why the code worked, so nobody knew how to fix it now that it didn’t.

We are currently living through the “Velocity Trap.”

AI tools like Cursor, Copilot, and specialized agents have made it possible to ship features at a rate previously unimaginable. But we are trading shared understanding for raw output.

As a Tech Leadership Advisor, I see this pattern emerging everywhere, we are scaling individual shortcuts, but we are eroding our systems.

If your team cannot explain the trade-offs baked into your core logic, you don’t own your product; you are simply renting its functionality from an algorithm.

The Erosion of Collective Ownership

Traditionally, software engineering was a social contract. Writing code was only half the job, the other half was building a mental model that could be shared across a team. This happened through whiteboarding, heated debates over architecture, and rigorous peer reviews. These “inefficiencies” were actually the guardrails of accountability.

AI-assisted coding often bypasses these conversations. When a developer uses an AI to generate a 50-line function, they often skip the “struggle” of the logic. That struggle is where the mental model is built. Without it, we create Individual Knowledge Silos. The developer understands the intent, the AI understands the syntax, but the systemic reasoning is lost in the ether.

When collective ownership dies, technical leadership becomes a game of “Whack-a-Mole.” You aren’t managing a codebase you are managing a black box.

Defining the “Accountability Gap”

There is a massive difference between legal responsibility and operational accountability.

• Legally, the CEO and the Board are responsible for the company’s output.

• Operationally, the VP of Engineering is on the hook for uptime.

But mentally, a subtle shift is happening in the trenches. When a bug occurs in AI-generated logic, there is a psychological tendency to shift blame to the tool: “The AI suggested this approach.”

This is the Accountability Gap. It is a hidden “Market-Blocker.”

If you cannot audit your logic, you cannot guarantee:

1. Security: Are there hallucinated dependencies or insecure patterns buried in the speed of delivery?

2. Compliance: Can you prove to a regulator exactly how a data-processing decision was made?

3. Scalability: Can this logic handle a 10x load, or was it optimized only for the immediate prompt?

As an advisor, I tell leadership teams: Technical accountability is not a technical problem; it is a management discipline.

Pillar 1: The “Human-in-the-Loop” Review Framework

To close the accountability gap, we must evolve the Code Review. We can no longer just check if the code “works” (the compiler or the AI already did that). We must check if the human understands it.

The “Explain-Back” Protocol

I advocate for a new standard in Pull Requests (PRs). If a block of logic was substantially generated or assisted by AI, the engineer must provide a “Human Logic Summary.”

This isn’t a comment on the code; it’s a justification of the Reasoning.

• What was the primary trade-off made here?

• What edge cases did the AI miss that I had to manually correct?

• Why is this approach better than the alternative?

If an engineer cannot provide these three answers, the code is not ready to ship. We must prioritize Understandability over Velocity.

Pillar 2: Prompt Governance & Documentation

In the new world of tech leadership, the Prompt is the new System Design.

If the core logic of your application is being dictated by the instructions given to an LLM, then those instructions are just as important as the code itself. Yet, most prompts are ephemeral lost in a chat history or a local IDE session.

Versioning Intent

We need to start versioning our “Intent.” This means documenting the high-level prompts and the architectural decisions that led to them.

• The Tech Ledger: Keep a record of high-risk AI-generated modules. These are areas of the codebase that require “High-Frequency Auditing.”

• Documentation as Code: Use AI to help document, but ensure the human “signs off” on the accuracy. AI-generated documentation that is never read is just more noise in the system.

Pillar 3: Cultivating Humane Tech Leadership

High-performance teams are built on trust and sustainable pace. The “Move Fast and Break Things” mantra has a high cost in the AI era. It leads to burnout when engineers are forced to fix “Black Box” bugs under high pressure.

The Leader’s Role: Rewarding the “Why”

As a leader, you must change what you celebrate. If you only celebrate the “Ship Date,” your team will use every AI shortcut available to hit it, regardless of the technical debt created.

Instead, celebrate System Robustness.

• Reward the engineer who found a flaw in an AI suggestion.

• Reward the team that took an extra day to ensure their AI-assisted refactor was fully understood by the junior members.

The “Calculator Effect” in Mentorship

We face a generational risk.

If junior developers use AI for everything, how do they develop the “Senior Intuition” required to lead in five years? Leadership must carve out “Manual Zones” areas of the product or specific sprints where AI tools are sidelined to ensure the foundational “mental muscles” of the team remain sharp.

Pillar 4: Managing External Tech Partnerships

Many companies rely on external consultants to build their AI initiatives. This is a high-risk area for accountability.

When a consultant leaves, they often take the “prompt intuition” with them. As a Strategic Advisor, I help companies manage these relationships effectively. The goal is to ensure that external consultants don’t just leave behind a “working app,” but a transfer of understanding.

Your rule for consultants: If my internal team can’t maintain the AI agents you built after you leave, the project is a failure, regardless of the ROI on day one.

Strategy-First, AI-Second

In the end the ultimate goal of any tech initiative is to drive measurable business outcomes to remove Market-Blockers and increase ROI.

AI is a breathtakingly powerful tool for reaching those goals, but it is a poor master. Technical accountability is the “Human” anchor that keeps your company from drifting into a sea of unmanageable code and opaque systems.

The Accountability Litmus Test for CEOs: Ask your CTO today: “If our top three developers left tomorrow, could the remaining team explain the trade-offs in our core AI-generated logic by the end of the week?”

If the answer is “No,” you don’t have a technical problem. You have a leadership opportunity.

It’s time to stop hitting “Archive” on our understanding and start building a strategic bench that can actually lead the machines they use.

Who am I?

I’m Diamantino Almeida, and I’ve spent my career at the intersection of high-growth engineering and strategic leadership.

From scaling technical teams to advising CTOs and Founders, my focus is on “Leadership as a Verb“, the idea that leading is an active, evolving practice, not a static title. Having navigated the shifts from manual infrastructure to cloud, and now to Agentic AI, I’m dedicated to helping the next generation of engineers find their footing in a world that is moving faster than ever.

Beyond advisory, I’m an active Top global 9% *mentor on *MentorCruise, where I help developers and leaders bridge the gap between “writing code” and “delivering business value.”

In this series of Practicing the Verb, it’s important that you know that quality matters, true speed is a metric we aim to achieve, but today, I believe going faster might mean leaving mistakes unattended.

If we don't bet on quality, we end up in a Toxic Mirage where metrics look good but the team is actually drowning.

As a manager or leader you must at least prepare a environment where quality is imperative, and time seen as a enabler not has an enemy, to blame people.

We are somehow obsessed with or led to believe that the faster we do things, the better.

It’s like the idea that bigger datacentre, better models. I believe the bigger will be the mess and the price the future generation will have to pay, for something they didn’t ask for.

But in my experience, the faster we go, the more bugs, unfinished work pile up, the more stress we feel, the more mistakes we make.

So why keep rushing, when we now have technology that could give us more time to do things right?

LLMs are very useful, but offloading important tasks to an empty vessel is dangerous. Believing they can replace people is also worrying.

Instead, we should be in a position where we can get real-time feedback, test multiple paths, see the results, and then pursue the best long-term option.

It’s like we’ve lost track of time and keep trying to compress it to unsustainable limits.

Some engineers I coach now say they have to do more and more, yet they still have to review most of what the AI does and fix the errors it creates.

Feels we are no longer working for us, but to sustain a tool.

I haven’t seen true, fully automated LLM solutions like the ones in certain videos for tools like n8n. They completely break when applied to real business challenges and problems. Yes, they help, but they require more tweaking than they should.

“AI” is not a magic pill. It doesn’t know things like we do, so it can’t truly understand our reality.

Now, I train teams to use AI for proof-of-concepts, where our assumptions are validated or debunked. For simple tasks, code can be generated and verified quickly, reducing some of the administrative work we dread.

For well-defined processes with no margin for error, yes, we can apply AI and be confident it will work. But LLMs fail multiple times a day. Some keep trying to “please” us and, in the process, mess everything up.

Quality is the baseline for Humane Architecture. You cannot build a system for humans if the code itself is a source of daily stress.

Trust your people. Use “AI” as a tool to improve communication and facilitate work.

Unless your entire process is like a car assembly line, where nothing changes and automation is suitable, but even there people still verify and help assemble the cars.

But if you view your business workflow as a factory model, nothing as really change…

All of this to tell you that we should pursuit quality, especially now that we have more than enough to pave this practice.

As we move into a world of AI-generated code, the human role shifts from 'writing syntax' to 'stewarding quality.' This is how you stay indispensable.

About the Author
Tino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human one verb at a time.

But if we don’t, they can just add more noise, more confusion, and more distance between people who should be working together.

I fear many companies would see AI, as a replacement for cheaper workforce, the same way companies outsource workforce from other countries where labor is cheaper, nothing wrong with that, but it creates division and a blame culture. No one likes to push a company to new levels of automation, adoption of certain work standards, and such. And in the end we receive a thank you letter and a redundancy package.

1. Custom AI agents as “team experts”

Let’s talk about what these AI agents actually are. They’re not magic. They’re not replacements.

They’re tools that can be shaped to fit the way your team works.

Domain-Specific Agents

Every team has its own way of doing things its own knowledge, its own history, its own quirks.

• DevOps teams have their logs and deployment strategies.

• Security teams have their compliance rules and risk assessments.

• Product teams have their user insights and roadmaps.

Instead of using a generic AI tool that doesn’t get your team, why not train an agent to specifically understand your team’s world?

For example:

A DevOps agent could analyze monitoring logs, suggest fixes based on past incidents, and even draft runbooks. But here’s the key, the agent doesn’t make the final call. It suggests, and a human approves. That way, the team stays in control, but the agent helps them move faster.

A Security agent could offer a “Check for Compliance” service that Product teams can use before launching a new feature. No more waiting for a security review to be scheduled just ask the agent for a quick sanity check.

Self-Service for Other Teams

One of the biggest wastes of time in any company is the back-and-forth between teams. “Hey, can Security review this?” “DevOps, what’s the status on this deployment?”

With custom AI agents, teams can expose certain capabilities like a Slack command or an internal API so other teams can get answers without waiting for a meeting or an email response.

Human Decision Gate

This is non-negotiable, AI should inform, but humans should decide. Always. No exceptions. If an agent suggests a fix, a human review it. If it flags a risk, a human assesses it.

The goal isn’t to remove people from the equation it’s to give them better information so they can make better decisions.

2. AI as a force multiplier for collaboration

AI agents shouldn’t just be about getting things done faster. They should help teams work together better.

This idea of pushing hundreds of lines a second, only create a huge cognitive overload and more things to test and do. Be smart on this one.

Live Documentation & Advisory

How much time do we waste digging through outdated docs or asking, “Wait, how did we set this up again?” An AI agent can keep documentation alive updating API specs, onboarding guides, or architecture notes as the code and discussions evolve.

No more “oops, that wiki page is from 2020.”

Pattern Recognition

Ever feel like you’re solving the same problem over and over? An agent can flag recurring issues like, “Hey, this error looks like the outage we had last month.

Here’s how we fixed it then.” That way, teams spend less time reinventing the wheel and more time actually moving forward.

Process Alignment

AI can also nudge teams toward best practices. Imagine an agent saying, “This change requires a security review should I schedule it for you?” It’s not about policing; it’s about making sure nothing slips through the cracks.

Workflow Integration Map

Here’s where managers come in. You don’t need to control every little thing the AI does, but you do need to define:

• Where does AI fit in? (Input: data, Process: analysis, Output: recommendations)

• Where do humans step in? (Judgment, ethics, prioritization)

Clarity here prevents chaos later.

3. AI for creative and strategic work

This is where things get interesting. AI isn’t just for grunt work it can help with the big stuff, too.

Idea Generation

Stuck on a problem? An agent can brainstorm new features, architectures, or strategies based on your team’s knowledge and industry trends. But and this is important don’t stop there.

Imagination Safeguard

After the AI spits out ideas, the team should run a divergence session no AI allowed. Generate your own ideas, compare them to the AI’s suggestions, and ask: Which ones feel original? Which ones are actually feasible? This keeps the team’s creativity sharp.

Risk Assessment

Before rolling out a big change, an agent can simulate outcomes or flag potential risks. “This change might conflict with Marketing’s campaign should we sync with them first?” It’s like having a second set of eyes that never gets tired.

Creativity Retention

Here’s a rule I swear by: Hold “AI-free” ideation workshops every quarter. No tools, no agents, just people thinking and creating together. It keeps those intuitive, creative muscles strong.

How Managers Can Support Teams (Without Micromanaging AI)

Managers, this one’s for you.

Your job isn’t to control how teams use AI it’s to set them up for success.

1. Set Guardrails, Not Handcuffs

• Define boundaries: What can the agent do? (Draft code? Sure.) What’s off-limits? (Deployment decisions? Absolutely.)

• Ownership model: Assign an “AI steward” in each team someone who handles training, updates, and audits. Keep accountability human.

• Ethics & bias review: Regularly check the agent’s outputs for accuracy, fairness, and alignment with your company’s values.

2. Foster a Culture of Trust and Curiosity

• Encourage experimentation: Let teams test agents in low-risk areas first like documentation or code reviews, before scaling up.

• Transparency: Make sure everyone knows how their agent works what data it uses, what it can’t do. No black boxes.

• Feedback loops: Hold monthly “AI Learnings” sessions. What worked? What failed? Keep the conversation going.

3. Focus on Outcomes, Not Oversight

• Metric-driven autonomy: Don’t measure how much the team uses AI. Measure the impact, like faster onboarding, fewer bugs, or happier teams.

• Cross-team audits: Have Security review DevOps’ agents. Have Product check Data’s insights. Fresh eyes catch blind spots.

• Skill preservation: If human creativity or problem-solving starts to decline, dial back the AI. The goal is to enhance skills, not replace them.

4. Invest in “AI Literacy”

• Training: Run workshops on prompt design, agent tuning, and ethical use. Everyone should know how to work with AI, not just how to turn it on.

• Documentation: Encourage teams to document their agent’s strengths, weaknesses, and “personality.” “Our agent is great at optimization but overly cautious on risk.”

• Skill alignment: AI should reinforce human skills critical thinking, collaboration, ethics not automate them away.

Custom AI agents as a service

Let’s make this concrete. Here’s how it could work in a real team:

How it works:

1. Teams train their agents with their own data and expertise.

2. Other teams interact with them via Slack, APIs, or Jira plugins.

3. Agents provide insights, but humans make the final call.

Key mindset shifts

To make this work, we need to change how we think about AI:

• From “AI as a Tool” to “AI as a Teammate”: Treat agents like tools that guide them, critique them, help them improve.

• From “Control” to “Collaboration”: Managers should empower teams to shape their AI, not police it.

• From “Siloed Expertise” to “Shared Intelligence”: Agents can bridge knowledge gaps between teams, reducing friction and duplicate work.

New dimensions for human-centered adoption

Finally, let’s talk about what really matters:

• Human Decision Gates: No matter what, people make the final calls.

• Imagination Calibration: Regularly compare human ideas vs. AI ideas. Keep your team’s creativity alive.

• Wellbeing & Engagement Metrics: Track how AI use affects motivation and collaboration. If people feel replaced or stressed, adjust.

• Visual Workflow Maps: Make it clear where AI supports, where humans decide, and where skills grow.

A question for you

So, here’s what I want to know.

What’s the first mission you’d assign a custom AI agent?

• Log analysis?

• Documentation updates?

• Security scanning?

• Creative ideation?

Or is there some recurring bottleneck in your team that you’d rather automate first?

Let’s start small, learn fast, and keep the human element at the center.

Because at the end of the day, that’s what this is all about.

Not replacing people empowering them.

About the Author
Tino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human, one verb at a time.

Every problem has an app.

There’s a startup for every inconvenience. A dashboard for every complexity.

A note to leaders and those becoming leaders.

Pay attention.

Not just to your revenue graphs, OKR dashboards, or Slack notifications.
Pay attention to how the convenience of technology is quietly reshaping the way you lead and the way you treat people.

We spend more time looking at screens than looking at faces. More time interpreting spreadsheets than interpreting body language. More time attending to dashboards than attending to discomfort in the room.

On the surface, it feels harmless. After all, these tools make things faster. The AI coach gives you leadership tips in three minutes.

The platform summarizes your meetings so you can “save time.” The workflow app smooths over all the awkward human parts of collaboration.

But convenience has a cost. One we rarely calculate.

Every time we choose efficiency over presence, data over dialogue, we chip away at something essential. Trust. Relationship. The subtle signals that tell us what another human really needs.

Leadership is not about shaving seconds off processes. Leadership is not about automation.

Leadership is, at its core, about attention.

Where you place it. How you hold it. Who gets it.

So before we talk about how tech “broke leadership,” we need to slow down and acknowledge this truth:

If you can’t look your people in the eye, if you can’t stay with their fears or frustrations, if screens mediate every interaction then no tool in the world will make you a better leader.

A chatbot for every emotion.

We’ve been sold a story, for every human ache loneliness, hunger, grief, boredom somewhere, someone in a hoodie is coding the fix.

Someone, probably in a Palo Alto garage or a Berlin co-working space, is quietly "changing the world."

And yet, in spite of all that, we live in a world where the deepest problems poverty, inequality, climate collapse, the slow corrosion of trust in one another remain not just unsolved, but in many ways worsened.

Why? Maybe because there’s no real profit in solving them.

When Crisis Met Tech COVID as the Stress Test

The cracks were always there, but the pandemic made them obvious.

In 2020, when frontline nurses were reusing masks and governments scrambled to secure PPE, where did leaders run? To medical experts? To networks of community care?

No. In many places, they ran to Silicon Valley boardrooms.

Meeting after meeting, governments outsourced leadership to tech:

• contact-tracing apps that most populations never used or couldn’t rely on,

• dashboards that gave the illusion of clarity without context,

• AI models projecting viral spread useful in theory, but near useless for guiding frontline behaviour.

Meanwhile, the people who were actually holding the line bus drivers, care workers, teachers, supermarket shelf-stackers weren’t invited to those conversations.

We have to ask ourselves: was this leadership?

Or was it management outsourced to those best at making things scale whether or not they understood what was being scaled?

It revealed something deeper tech hasn’t just influenced leadership. It’s reshaped it, hollowed it out, and in many ways… broken it.

Leadership, Productised

Watch the next NVIDIA keynote or Apple WWDC demo. You’ll see something eerily close to a religious ceremony.

This isn’t just a presentation. It’s a carefully choreographed revelation.

The CEO doesn’t appear as a steward, but as a visionary saviour. The audience leans in like congregants.

And the message is clear:

"We’ve glimpsed the future and we’re generous enough to let you in on it."

• Steve Jobs didn’t just launch phones; he launched meaning.

• Elon Musk doesn’t just talk rockets he spins existential purpose.

• Sam Altman talks about AI less like a CEO and more like a cautious prophet.

This is the messiah complex, built into corporate form.

And the danger isn’t just the theatre. It’s what that theatre displaces. Instead of leadership rooted in responsibility and accountability, we’re left with a brand of leadership that’s mostly optics: performance, charisma, and the ability to narrate the future compellingly.

The problem?

We, the audience, often buy it. In a world that feels unfixable, we long for certainty. We crave saviours.

But leadership built on salvation without participation is not leadership at all.

It’s marketing.

From Human Messiness to Digital Perfection

Traditional leadership is messy. It requires presence sitting in complexity, listening to people, acknowledging frustration, learning to hold tension.

But in tech culture, messiness is a bug to be eliminated.

Meetings drag? Replace them with an AI notetaker.
Disagreements grind? Let the algorithm calculate the “optimal” decision.
Collaboration feel awkward? Push people into structured workflow apps until talking itself feels unnecessary.

Slowly but surely, tools designed to assist functionality begin to replace relationship itself.

We end up in meetings where people barely speak because “the bot will transcribe anyway.” Participation becomes optional or worse, performative. Suddenly, people aren’t present with one another; they’re avatars, curated projections of themselves.

But here’s the truth relationship is the essence of leadership.

It isn’t found in the decisions, or in the dashboards, but in the space between people.

In trust.

In disagreement managed face-to-face. In a leader seeing your eyes narrow and realising they’ve gone too far.

Presence cannot be automated.

And yet tech culture teaches us that everything important can be outsourced if only you code it cleverly enough.

Leadership, Subscribed

Once upon a time, leadership was practiced. You showed up, you tried, you stumbled, you repaired. You earned trust slowly, by presence and persistence.

Now leadership is transactional. A purchased product.

• Buy the course.

• Subscribe to the AI leadership coach.

• Download a book of CEO hacks.

• Hire a PR firm that polishes your “vision.”

• Use ChatGPT to be a better leader.

Even worse, many so-called leaders no longer lead they defer.

• They wait to see what the metrics say before making a decision.

• They let dashboards and consultants substitute for judgment.

• They benchmark competitors instead of exercising courage.

Employees become reduced to datapoints, nudged, tracked, scored, nudged again.

No wonder workplaces often feel soulless. Layoffs arrive as automated calendar invites. Recognition is reduced to emojis on Slack. Even “culture” itself is delegated to software.

This isn’t leadership.

This is logistics with better branding.

Why It Happened Follow the Incentives

To be fair, this isn’t just personal failure. Tech leaders act this way partly because capital rewards theatre over care.

Wall Street prizes growth curves, not emotional presence. VCs write bigger checks for founders who sound like messiahs, not stewards. Boards hire charismatic futurists, not humble listeners.

Leadership is being contorted because the systems around it insist that is what leadership must look like.

So if leadership looks broken in tech, it’s not just cultural. It’s systemic baked into the economic incentives.

But Tech Hasn’t Only Broken Leadership

Here’s where honesty requires balance.

Technology isn’t only corrosive. It has enabled incredible breakthroughs in how we connect, collaborate, and even survive.

• At the peak of lockdowns, Zoom reported 300 million daily meeting participants, which meant millions of jobs and communities continued to function.

• Telemedicine brought care to patients in rural areas who otherwise might have gone unseen.

• The rapid sequencing and open-source sharing of COVID genomes accelerated vaccine development at unprecedented speed.

So yes, tech flattened relationships in some ways but it also saved many.

The point isn’t that tech is evil. It’s the business models behind it.

It’s that tech culture, when it replaces leadership with metrics and spectacle, creates fragility in the places we most need humanity.

What Leadership Theories Teach Us

We don’t need to reinvent leadership theory to recognise the problem.

We already have models:

• Servant Leadership (Robert Greenleaf): leadership grounded in serving others before oneself, building trust through humility.

• Adaptive Leadership (Ronald Heifetz): leaders must guide people through uncertainty by holding space for discomfort and learning, not by pretending to have all the answers.

• Collective Leadership frameworks: power is shared, not concentrated; decisions are distributed across groups rather than hoarded at the top.

All of these contradict the “saviour founder” myth. And all of them point toward one truth, leadership isn’t performance.

It’s practice.

How We Might Rebuild

Tech broke leadership. But tech, used differently, might also help us rebuild it. Here’s how.

1. Design for Presence, Not Just Productivity

Imagine tools designed not to eliminate meetings but to make them deeper. Tools that prompt pauses, reflection, and check-ins before sprinting into tasks.

What if your calendar rewarded rest as much as hustle? What if project dashboards asked not only “Is the work done?” but also “How is the team doing?”

Presence isn’t inefficient. It’s what makes leadership real.

2. Re-centre Relationship

The best leaders use technology to amplify connection, not outsource it.

• Leave a voice note instead of sending a cold Slack ping.

• End a Zoom meeting not with “next steps,” but with “what’s one thing weighing on you today?”

• Replace top-down OKR templates with collective goal-setting sessions.

Tech should enable human connection, not avoid it.

3. Retire the Saviour Narrtive

Stop waiting for the next Elon, Sam, or Steve to arrive telling us what’s next. That model is bankrupt.

What if the next revolution in leadership wasn’t billion-dollar exits but local teams solving community problems together?

What if leadership was reclaimed not by visionaries at the top, but by engineers, managers, and communities asking deeper questions before building?

The solo-hero story has run its course. The future is collective, distributed, accountable.

4. Build Humane Systems

If we want healthier leadership, we must also change the systems that shape it.

• Do we reward those who coach others or those who shout the loudest?

• Do our boards prize ethical restraint or quarterly hypergrowth?

• Do platforms elevate truth or outrage engineered for clicks?

Culture is code. Incentives are infrastructure. Both can be rewritten. But only if leaders have the courage to say: we got this wrong.

Leadership, Reclaimed

Here’s the hardest truth: tech didn’t just break leadership we did, by buying into the illusion. By worshipping saviours instead of holding them accountable. By equating charisma with wisdom, scale with care.

But this era AI agents, avatars, automation might be the call back to something older, slower, and more human.

Because the future of leadership isn’t another roadmap, app launch, or keynote reveal.

It’s the questions we dare to keep asking:

• Who am I serving?

• Who gets left out when I make this decision?

• How do I build environments where people feel safe, seen, and strong?

The leader of tomorrow won’t necessarily be the loudest, the richest, or the most followed. They’ll be the ones who choose to lead with others, not over them.

The ones who can hold tension, not erase it.

The ones who can ground their nervous system before trying to regulate anyone else’s.

The ones who remember that technology is a tool, not destiny.

And maybe just maybe the next shift in leadership won’t look like a keynote at all.

It will look like a group of people sitting quietly, phones aside, looking each other in the eye, and saying simply:

"Let’s figure this out, together."

About the Author
Tino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously—from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human—one verb at a time.

It was an urgent one not much explanation, apart from the email saying we needed to be in the meeting room near our pods at 6 p.m. It must have been summer, since I remember it was a very hot day. I was nervous even before the meeting started the suspense and lack of additional info were nerve-racking.

We all got into the room and waited for our line manager. He appeared, opened his laptop, connected it to the wall screen, and started showing some metrics how good we were doing and how our KPIs were improving.

Then came the news: our team leader was leaving, and a new one needed to replace him.

We started looking at each other. Some people said, “Tino, you’ll be our next team leader.” I got mad nervous and just nodded, signalling, “That’ll never happen.”

Then our line manager said this:
“Tino, you will be the team leader. I’ve spoken with many people, including your colleagues, and they all confirmed you’re the right person for the job. The way you treat people here is exemplary, and your performance metrics are off the charts.”

After that, I stopped listening. My heart was pounding in my ears. And then I had this urge to say something I completely forgot what it was but I know I shouted it.
Most people told me to lower my voice and giggled a bit.

I felt ashamed.
After that, I went home and couldn’t sleep, replaying in my head what I needed to do and what my life was about to become.

But one thing kept pinging in my head, “Why I’m breathing so fast?”

I didn’t truly begin to understand leadership until I started noticing how I breathed.

Not in some poetic, romanticised way, but in the deeply physical sense. The way my breath would get tight before a difficult conversation.

The way my shoulders would creep up during conflict.

The way I’d clench my jaw in meetings without realising.

For years, I led teams, coached others, built roadmaps, and helped solve organisational dysfunctions all while my own nervous system was on high alert, operating from a place of subtle but constant stress. I thought I was being “professional,” “focused,” or “productive.”

What I was really doing was pushing through, dissociating, masking discomfort until my body could no longer ignore the signs.

What I’ve learned since is simple

You cannot lead others effectively until you’ve learned to regulate and lead yourself especially your nervous system.

Leadership, at its core, is not a performance. It’s not a hat you put on in the morning. It’s not a set of bullet points in a quarterly update or a public talk-style declaration of your team’s values.

That’s the type of behavior or values expected at the corporate level, simply because companies exist to profit and results is what matters.

Should you value, listen, follow leaders that are at the corporate level?

Leadership begins in the body.

It shows up in how you enter a room, how you respond when someone challenges you, how you recover from mistakes, and how you make people feel not just with your words, but with your presence.

If your nervous system is constantly on edge reacting to threat, absorbing stress, masking anxiety that energy leaks out.

It creates ripple effects: tension, confusion, distrust. No matter how many management books you’ve read or frameworks you’ve implemented, if your body is signalling fear, urgency, or defensiveness, your team will pick up on that signal long before they hear what you have to say.

We don’t often talk about the nervous system in leadership circles.

We talk about mindset, tools, outcomes. But your nervous system is your first leadership tool. It governs your capacity to respond instead of react. It influences your tone, your timing, your level of presence.

I remember a few years ago in a “Leadership Workshop Sessions”, and after a session about “soft skills”, and respect your direct reports, most where saying,” what a lot of rubish”, “I don’t need to be polite, to get others to do the work”.

Most of us are taught to ignore or suppress our emotions to power through, be “rational,” stay calm. But here’s the paradox: emotional awareness isn’t weakness. It’s human connection.

Emotions are not the opposite of logic. They’re information about what matters to you, what you fear, and how you interpret your surroundings. If you can’t recognise what you're feeling or if you’re disconnected from how others feel you’re not operating from clarity. You’re leading from confusion and projection.

In my coaching work and leadership journey, I’ve come to understand that “knowing yourself” is not just a philosophical idea.

It’s a practical necessity.

You need to know your emotional patterns, your triggers, your inherited beliefs. You need to know what you tend to avoid, how you defend yourself when you feel small, what stories you’ve been told about power, success, and authority.

These internal patterns often run silently in the background until pressure hits. That’s when they emerge. In times of stress, you don’t rise to your ideals you fall to your level of nervous system training. If you haven’t done the work of knowing and regulating yourself, your leadership will default to instinctive reactions. You’ll either withdraw, dominate, appease, or distract often at the expense of your people and your values.

That’s why I believe emotional awareness and nervous system literacy should be core leadership skills not optional extras. These aren’t “soft skills” as they’re often dismissed.

They’re hard-earned, embodied capacities that determine how trustworthy, grounded, and stable you feel to others.

Teams don’t need perfect leaders. They need leaders who are present. That presence, however, isn’t magic it comes from regulation, reflection, and repair.

Let me say something else that’s rarely acknowledged: your nervous system is not isolated. It’s shaped by your environment. By who’s in the room. By the systems you work in. By the architecture of your calendar, the pressures of your role, the pace of your culture. A constantly overstimulated, performative, surveillance-based workplace will fry even the most emotionally intelligent leaders. That’s why slowing down, connecting with nature, unplugging from the noise these aren’t indulgences. They’re repair strategies.

The way I breathe in a forest is not the same as how I breathe on a deadline-packed Monday. My ability to think clearly, listen deeply, and act intentionally depends on how safe and spacious my environment feels.

The same is true for those I lead. Leadership, then, is not just about regulating yourself it’s about designing environments where others can regulate too.

When I think about what leadership is, I don’t think about status or charisma or metrics. I think about relational presence.

Leadership is relational work not individual conquest.

It’s not about commanding people into action. It’s about creating the conditions where people want to act, together. That requires deep listening, humility, co-regulation, and trust things that don’t come from titles.

They come from consistent human practice. In my view, leadership is something we do with others, not to them. And to lead well, we have to understand what our nervous system is doing in those shared spaces because it is always broadcasting something, even if we stay silent.

I’ve made enough leadership mistakes to know how easy it is to lead from fear especially fear masked as control, overwork, or perfectionism. I’ve been in rooms where everything looked fine on the surface and yet the team was walking on eggshells, waiting for someone to explode or withdraw.

I’ve also seen what happens when a leader takes the time to ground themselves, to pause before reacting, to acknowledge their own tension and come back to the conversation with openness.

That’s the kind of leadership I want to practise and teach.

So here’s my invitation: before you chase the next leadership framework or productivity hack, learn to sit with yourself. Learn to breathe when things get hard.

Learn to name what you’re feeling.

Learn to track the patterns that arise when you feel threatened.

Learn to regulate and not just react. Learn what brings you back to presence, what grounds you, what reminds you of who you are beneath the noise. Spend time in places that calm your body.

Listen to music that softens you. Walk in nature. Speak to people who challenge you without shaming you. Ask for help. Apologise when you need to. Slow down when you can. Not because it’s fashionable but because it’s necessary.

Because here’s the truth

The quality of your leadership is directly related to the quality of your presence.

And the quality of your presence depends on the health of your nervous system. You cannot fake groundedness. You either feel it or you don’t. And when you do, others feel it too. In your tone. In your timing. In your decisions. In your ability to listen without jumping in. In your capacity to hold complexity without collapsing.

I believe leadership is not about having all the answers. It’s about making space for the right questions to emerge. It’s not about being the hero.

It’s about helping others find their voice and act from it. It’s not about avoiding discomfort. It’s about staying with it long enough to find clarity. But none of that is possible if we’re constantly dysregulated, burnt out, or detached from our own inner signals.

How to Know and Regulate Your Emotions

Most of us weren’t taught emotional literacy. We were taught to bottle it, intellectualise it, or bury it under productivity. But leading your nervous system starts with feeling what’s there, not what you think should be there. Emotions are messengers not enemies.

Here’s how I’ve learned (and keep learning) to work with mine:

1. Name it to work with it

If you can’t name what you’re feeling, it owns you. Start simple. Angry. Anxious. Disappointed. Excited. Numb. Sometimes I sit with a pen and just write: “What’s alive in me right now?” And I wait. Just letting the nervous system speak through words.

2. Feel it in your body

Emotions don’t just live in the head they show up as heat in the face, tightness in the chest, butterflies, shallow breath. When something hits me, I ask: Where is it in my body? What does it want me to know? This helps create space between me and the feeling. It becomes something I can relate to, rather than be hijacked by.

3. Slow the hell down

Fast pace amplifies reactivity. When I’m triggered or overwhelmed, the first thing I try to do is pause. That might mean walking to another room, turning off notifications, or literally putting a hand on my chest. You can’t make grounded decisions in a state of panic and you don’t owe anyone a response at the speed of email.

4. Track your patterns over time

What tends to trigger you? What people, situations, or phrases light a fire in you or shut you down completely? Pattern tracking helps you anticipate rather than react. Sometimes the pattern isn’t about the moment it’s about an older story that’s never been questioned.

5. Breathe like your life depends on it (because it does)

When I don’t know what else to do, I breathe. Deep, intentional breaths signal safety to the nervous system. It doesn’t fix everything, but it gives me a fighting chance to respond with clarity instead of instinct. Box breathing. Long exhales. Breathing through the nose while walking. These aren’t hacks. They’re restoration.

6. Build your emotional vocabulary, slowly

Instead of just saying “I feel bad,” try: “I feel exposed,” “I feel dismissed,” “I feel hopeful but cautious.” Language helps precision. Precision helps clarity. Clarity leads to wiser choices. If you’re not sure where to start, keep a log. One emotion a day. One moment that moved you. Over time, you’ll surprise yourself with how emotionally fluent you become.

7. Create a few rituals that ground you

I don’t believe in silver bullets. But I do believe in small, repeatable acts that tell your nervous system: you are safe. That might be a cup of tea before meetings. A 10-minute walk at lunch. Music. Journaling. Gardening. Prayer. These things build emotional resilience not through grand gestures, but through consistency.

What science teaches us about emotions

If you are curious, here’s a bit of what I have experienced so far and learned.

The more I’ve learned about emotional regulation, the more I realise that this isn’t just a leadership tool it’s a survival skill. And science backs this up.

Our brains are wired for emotional response first, logic second. That’s not a flaw. It’s evolutionary design. The part of our brain responsible for emotional reactivity the amygdala is lightning-fast. It evolved to protect us from threats. The problem is that it can’t tell the difference between a tiger and a rude email, between a life-threatening danger and an awkward silence in a boardroom.

The emotional alarm system still fires.

But it’s the prefrontal cortex, sitting right behind your forehead that decides what to do with that emotional alarm. That’s where decision-making, impulse control, empathy, and long-term thinking live.

The prefrontal cortex doesn’t fully mature until around age 25, and even then, it continues to strengthen with reflection, feedback, and practice.

That’s important, because it means emotional maturity is something we grow into and something we can also regress from under stress.

When you’re tired, overwhelmed, or overstimulated, your brain literally reroutes to older, more reactive systems. The same thing happens when you’re constantly bombarded with alerts, polarising content, or high-pressure environments.

Your brain shifts from “consider and respond” to “react and survive.” And this is where technology and leadership power structures get interesting and frankly, concerning.

Because if you know that people are more reactive when they're scared, angry, or uncertain, you can design systems to keep them that way. And that’s what a lot of tech and media does. Social media platforms are engineered to exploit our limbic system to provoke outrage, anxiety, comparison, tribalism because those emotional states keep us hooked.

That’s how the attention economy works.

It’s not a glitch it’s the business model. The more dysregulated and distracted we are, the more predictable and profitable we become.

That’s why I don’t believe in passive consumption anymore. What you read, watch, listen to it shapes your nervous system. It conditions your sense of reality. If your feed is full of stress, urgency, or unattainable ideals, your body starts adapting to that reality. You start comparing yourself not to real humans, but to filtered performances. And the same thing happens with leadership. If all we see are polished, charismatic, never-wrong leaders, we begin to internalise that as the standard.

And we forget to look behind the performance.

This is why critical analysis of leadership matters especially now. We need to look beyond words. How does this leader handle conflict? Who benefits from their decisions? What kind of culture are they modelling? Are they willing to admit when they’re wrong or are they always positioning?

Do they speak with clarity and care or do they manufacture urgency to drive short-term action? These are not surface-level questions. They are diagnostic tools. Because if you can’t assess the emotional state behind leadership, you’re more likely to be manipulated by the performance of it.

I’ve seen this play out in tech leadership time and time again. Charismatic visionaries who talk about innovation but burn out entire teams. “People-first” CEOs who lay off thousands while posting about resilience.

Culture decks full of trust and empathy while the actual environment runs on fear, urgency, and control. And we applaud it because the metrics look good. Because the story sounds nice. Because we’ve been conditioned to think leadership is about style, not substance.

But if you really watch not just listen, but watch you can feel the nervous system underneath. And most of the time, it’s not grounded. It’s reactive, controlling, impatient, or disconnected. And that energy shapes everything beneath it.

This is also why your physical environment matters. You cannot regulate your emotions in a toxic space. If your workplace, home, or digital space constantly signals danger or urgency, your nervous system will adapt to that signal.

You’ll normalise tension. You’ll start bracing even when nothing’s wrong. And over time, that becomes your baseline. That’s why nature is so important to me.

Not just because it’s beautiful but because it reminds my body of a different rhythm. Slower. Quieter. More grounded.

You can’t rush a tree into blooming. You can’t schedule a mountain. When I spend time outside, something in me softens. My prefrontal cortex kicks back in.

I stop reacting, and I start remembering who I actually am not who I perform to be.

So this isn’t just about leadership in the workplace. It’s about leadership as a daily practice one that starts with regulating your own system so you’re not just reacting to fear, following trends, or outsourcing your moral compass. It’s about making space to ask: Is this real? Is this right? Is this mine to carry?

And that takes emotional maturity.

Which isn’t about having all the answers. It’s about being able to stay with discomfort without becoming someone you’re not.

It’s about being led by your values, not your triggers. And it’s about remembering especially in an age of endless performance that integrity is quiet. Often unseen. But always felt.

So before you lead others, start with yourself.

With your breath. Your body. Your emotions. Your blind spots. Your patterns. Because if you can lead yourself through discomfort without fleeing, fixing, or forcing then others will trust you to walk with them through theirs.

And that, to me, is the beginning of real leadership.

That’s leadership as a verb not something you are, but something you practise.

Especially when no one’s watching.

About the Author
Tino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human, one verb at a time.

Subscribe now

Just a queue of tired people holding baskets full of dinner plans and deadlines.

You’re in line at the grocery store. Someone cuts ahead. The cashier looks like she hasn’t blinked in 45 minutes. A toddler drops a yoghurt, and the parent looks like they might do the same with their sanity. Behind you, an old man sighs like it’s his full-time job.

And right then you get a choice.

You can be a bystander. A consumer. A LinkedIn ghost.

Or you can be a leader. Not the loud, branded kind. The human kind.

The Queue Is a Microcosm

The grocery line is society in miniature. It’s where unspoken rules get tested: fairness, patience, dignity.

Everyone’s in a rush. No one wants to be there. Time is short, tempers shorter. But what happens here reveals what we tolerate, what we ignore, and what we quietly allow to rot.

It’s the stage for what I call mundane leadership. Not leadership with capital letters. Not the keynote or the offsite. Just people doing the right thing when it’s inconvenient and unglamorous.

You want to know how someone really leads? Watch them when nobody’s watching. Watch them when someone skips the line, or the card reader crashes, or the cashier starts crying because her manager won’t come over and a Karen is demanding a refund for bananas that were “too ripe.”

The grocery line strips away your job title. Your status. Your fancy frameworks. And leaves you standing there with your behaviour.

The Bystander Reflex

Let’s be honest. Most of us just want to get through the damn queue.

We see something unfair—someone getting verbally abused, an elderly person struggling with bags, a child being spoken to harshly—and we freeze. We say nothing.

Because “it’s not our business.”
Because “I’m not here to start something.”
Because “someone else will do something.”

That’s the bystander reflex.

And it’s not neutral. It’s a form of passive leadership. A silent vote for how things should stay.

We like to think we’re kind people. Ethical. Thoughtful. But character isn’t built in theory—it’s revealed in tension.

When you watch someone get mistreated and say nothing, you’re not being neutral. You’re reinforcing the system that allowed it.

Leadership isn’t about being in charge. It’s about deciding what you’ll stand for—even in aisle seven.

A Personal Example: When I Froze

I’ll admit it. I’ve failed this test before.

Once, in a shop, I watched a customer berate a teenage cashier for moving “too slow.” The kid’s hands were shaking. The manager was nowhere. And I just… stood there.

I told myself the same story we all tell: “It’s not my place. Don’t escalate. Just get through this.”

But here’s what haunted me later: the look on that kid’s face. A mix of humiliation and resignation, like this wasn’t the first time. And maybe he looked around, hoping someone—anyone—would step in.

No one did. Not even me.

That moment taught me something important: silence is not safety. It’s complicity. And the stories we tell ourselves about “not making it worse” often mean we’re comfortable letting someone else absorb the harm.

I didn’t like the person I was in that moment. Which meant I had a choice: pretend it didn’t matter, or practice differently next time.

Small Acts, Big Meaning

The next time, I did.

A few months later, I saw another cashier getting snapped at by an impatient customer. This time, I stepped in—calmly, not aggressively. I just said: “Hey, it looks busy. Let’s give her a minute.”

That was it. Not a heroic speech. Not a confrontation. Just a gentle reminder that dignity matters.

And the air shifted. The customer backed off. The cashier gave me a grateful half-smile. And I walked out of that shop knowing I’d acted more in line with the leader I want to be.

This is what I mean by mundane leadership. The small, ordinary acts:

• The person who gives up their spot to someone clearly more exhausted.

• The customer who says, “Take your time,” and actually means it.

• The stranger who notices the cashier has been standing for hours and says, “You doing okay?”

These aren’t acts that win awards. There’s no clapping. No end-of-year bonus. Just moments where dignity is protected.

This is leadership as verb. Leadership as interruption. Leadership as, “I see you.”

You don’t need a badge to care. You need courage. And clarity that it matters.

Invisible Work, Visible Stress

Zoom out for a second.

Why are so many of these queues full of tension? Why are workers burnt out and customers on edge?

Because the system is designed that way.

Most grocery store employees are underpaid, under-supported, and overworked. Many are on zero-hour contracts or monitored by “efficiency” AI systems that track their every second but have never had to mop up vomit while scanning cucumbers.

We don’t talk about this enough. We glamorise leadership but ignore how systems fail people on the ground.

It’s easy to lead in theory. Harder when the human in front of you is breaking down and you’re late for a meeting. Harder when you realise the cashier isn’t just “slow”—they’re on their third shift this week without a proper break.

Leadership, if it’s worth anything, shows up when power doesn’t.

So while consultants build “human-centred strategies,” the real leadership test is this: Do you treat people with dignity when they can’t do anything for you?

Designing the Line

Here’s the truth: if you’re in tech, in management, in operations, in anything that affects how systems work—you are designing the line.

And if you’re not questioning how the system makes people feel, you’re just optimising oppression.

The grocery queue is an interface. It reflects choices:

• How many tills are open?

• Who gets trained and paid well?

• Is there enough support for elderly or disabled shoppers?

• Do loyalty points matter more than worker dignity?

Leadership isn’t just emotional intelligence. It’s structural intelligence. And it demands we stop treating people like throughput.

The Everyday Test

Let’s ground this. Here’s how to practice leadership in the line:

1. Speak Up – If someone’s being mistreated, say something. Calm, direct, human. You don’t need to be confrontational to set a boundary.

2. Model Patience – Don’t huff and puff. Your breath isn’t a weapon.

3. Notice People – Look the worker in the eye. Thank them sincerely. Human recognition is fuel.

4. Check Your Power – Are you using your position (age, class, language, time) to dominate or to help?

5. Teach Through Action – If your kid is with you, they’re learning what leadership looks like in real time. Show them that kindness is a reflex, not an afterthought.

Most of these don’t require effort. Just intention. Just the refusal to treat others as obstacles or background noise.

From Grocery to Boardroom

You know what’s wild? How often I’ve seen leaders—real ones, in charge of real people—utterly fail this test.

They give keynotes about empathy and then talk down to a barista. They post about justice but yell at customer support over a £2 mistake.

If you can’t lead in the queue, you can’t lead in a crisis.

The habits we build in small moments become the reflexes we rely on in big ones. If you practice humanity at the checkout, you’ll know how to hold it when it really counts.

And if you’re a CEO reading this thinking, “This doesn’t apply to me”—go do your own shopping sometime. No assistant. No perks. Just you, a trolley, and the mirror of your actions.

Lessons I’ve Carried Into My Work

Over the years, I’ve tried to let the queue shape how I lead in the workplace:

• When I run teams – I try to make invisible work visible. The person keeping our servers alive at 2am deserves the same recognition as the one presenting at the town hall.

• When I coach leaders – I remind them that culture isn’t built at the offsite; it’s built in the everyday line: the way you respond to a stressed employee, how you treat your assistant, whether you create room for patience or pile on pressure.

• When I parent – I know my kids are watching me in queues, in traffic, in moments of frustration. They’re learning leadership not from what I say, but from what I model.

The queue is everywhere if you’re paying attention.

No Applause in Aisle Nine

Leadership isn’t something you wait to be invited into. It’s something you practice. In the mess. In the mundane.

No one will give you a trophy for telling someone to stop shouting at a worker. No one will sponsor your TEDx for letting the elderly man go ahead of you. But someone will feel safer. Someone will feel seen.

And maybe, just maybe, someone behind you in the queue will learn a better way to show up.

No applause. Just groceries. And a little more dignity in the world.

That’s leadership. Even in aisle nine.

Final Reflections: Practicing Leadership as a Verb

When I think about leadership today, I don’t think about titles, budgets, or followers. I think about queues.

Because the grocery line asks the same question every crisis does: Will you show up for people when it’s inconvenient?

Leadership is not a noun. It’s not something you are. It’s a verb—something you do, again and again, until it becomes who you are.

And the best way to practice? Start where you are. At the checkout. In traffic. On the phone with customer support.

Every time you choose dignity over indifference, patience over performance, solidarity over silence—you are leading.

Not the loud, branded kind. The human kind.

And that’s the only kind that lasts.

About the Author
Tino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously—from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human—one verb at a time.

Subscribe now

Maybe it was after you helped a colleague through a rough patch at work. Maybe a friend came to you in crisis, and instead of giving them advice, you just sat with them long enough for the fog to lift. Maybe someone said, “I admire your journey,” and you didn’t respond with a highlight reel you told the truth, warts and all.

If any of that rings true, you’ve already started mentoring even if no one gave it a name. Because mentorship doesn’t start with a job title, a website, or a polished résumé. It begins with intent. With curiosity. With the decision to walk alongside someone instead of ahead of them.

But here’s what most people don’t say, mentorship is a practice. It’s messy. It evolves. And it teaches you just as much as it supports the other person.

This isn’t a guide to being a perfect mentor. I’m not here to sell you a framework that guarantees “10x growth” for your mentees. I want to give you something more useful: an invitation to treat mentorship as a living practice one grounded in experimentation, empathy, listening, and presence.

Because mentorship is not a role. It’s a relationship. And the way you practice it will shape not only those you mentor, but the leader you are becoming yourself.

1. Mentorship at Work: A Posture, Not a Position

Organizations love to systematize things. “You’re a senior now; you’ll be assigned mentees.” Or: “Sign up for our mentorship scheme.”

There’s nothing wrong with structure, but the most impactful mentors rarely get their role from HR. They mentor because it’s a posture—a way of being.

Effective Workplace Tips:

• Build Trust and Rapport: Invest the first few meetings in getting to know your mentee—ask about career goals, learning styles, and current struggles. Don’t rush into giving advice; start by listening and building connection.

• Set Clear Expectations: Co-create ground rules. Discuss how often you’ll meet, preferred modes of communication, and what confidentiality means to each of you. Write it down if it helps.

• Use “Micro-Mentoring” Moments: Mentorship often thrives in brief, unplanned moments—a quick debrief after a presentation, a supportive Slack message after a tough week.

• Share Stories, Not Just Solutions: When someone faces a struggle, offer a similar story from your journey rather than just instructing. This invites growth, not dependency.

• Guide, Don’t Direct: Ask open-ended questions that help your mentee think through challenges. “What options have you considered?” is more empowering than “Here’s what you should do”.

• Be Dependable, Not Rigid: Agree on a cadence for check-ins but allow flexibility. Consistency shows care, but it shouldn’t become a burden.

Real-world mentoring at work is as much about presence and noticing as it is about advice.

The best mentors create space for learning, offer honest feedback with empathy, and model humility by sharing their own unfinished edges.

2. Mentorship at Home: Growing Side by Side

At home, you lose your professional mask. Vulnerability and authenticity take center stage—but so do old habits and difficult dynamics.

Home Mentorship Tips (for family, partners, friends):

• Model the Values You Want to Teach: If you want kids or partners to handle disagreement well, show them how you apologize and recover from mistakes.

• Ask Before Advising: Use a simple script: “Do you want advice or just someone to listen?” Respect if they only need to vent.

• Create Meaningful Rituals: Make space for check-ins—Sunday dinner conversations, evening walks, even shared chores—to open doors for honest talk.

• Normalize Growth and Failure: Talk openly about your own failures or learning moments; this creates a family culture of permission.

• Let Loved Ones Teach You: Ask your children (or partner) to show you something they’re good at. Reverse mentorship breeds trust and respect.

• Set Boundaries: If you’re feeling depleted, say so kindly. “I love helping, but right now I need a little recharge. Let’s talk at dinner?” This models self-care for everyone.

Mentorship in families is rarely neat it lives in repetition, patience, showing up during tough times, and letting others outgrow your worldview.

3. Mentorship in Professional Practice: Experiment, Reflect, Adjust

While mentoring outside your usual circle, whether via a program or online, it’s easy to revert to “teacher mode.” But lasting mentorship is always co-created.

Professional Mentoring Tips:

• Co-Define Goals: Spend the first session clarifying “Why are we here?” and “What would success look like, even in small ways?” This frames every exchange with intention.

• Offer Honest, Kind Feedback: Balance challenge with affirmation. Use specific feedback when possible—swap “You need to speak up” with “I noticed you had good points, but waited until others went first. What made you hesitate?”.

• Practice Active Inquiry: Guide mentees to their own insight by asking, “What’s the biggest challenge here for you?”

• Keep Notes, Even Brief Ones: Jot down what you discussed, themes, and follow-ups. This shows you care and helps track growth.

• Be Flexible with Format: Try mixing modes—one month, schedule a call; another, swap voice notes or emails. Respect and adapt to your mentee’s communication style.

• Share Network Opens: Introduce your mentee to someone in your professional circle. A single warm introduction can have a profound long-term effect.

Mentorship is less about “teaching wisdom” and more about practicing vulnerability and learning in public, together.

4. Mentorship in the Digital Age

Today, much mentorship happens online by text, in DMs, over video, or asynchronously in global networks. The shift isn’t negative it expands what’s possible.

Digital Mentoring Tips:

• Open Virtual Meetings with a Human Touch: Share a quick personal “rose/thorn”—something good and something tough. This bridges distance and builds trust.

• Respect Digital Boundaries: Establish office hours or response times. Don’t expect immediate replies or late-night availability.

• Mind the Medium: If nuance is needed, choose voice or video over text. Use emojis or reactions to communicate warmth in chat.

• Document Agreements: Capture goals, next steps, or insights in a shared document or email.

• Send Follow-Ups: After video calls, share a summary or encouragement. This creates continuity and shows care.

• Stay Inclusive: In global teams, rotate meeting times or use asynchronous tools to ensure everyone, regardless of time zone, can participate fully.

In digital mentorship, intentionality and empathy must shine through the “screen.” After all, mentorship unlike advice is not something AI can automate away.

5. Cross-Generational and Reverse Mentorship

Mentorship doesn’t only flow “downhill.” Generational, cultural, or background differences can feed transformative learning in both directions.

Cross-Generational Tips:

• Invite Reverse Mentorship: Ask younger or less-experienced colleagues to share their process, tools, or perspectives. Treat their lessons with curiosity, not defensiveness.

• Acknowledge Blind Spots: Sometimes mentees illuminate your unexamined assumptions. Name and welcome those insights.

• Learn to Listen to Language: Pay attention to new terms, memes, or references from other generations—ask what they mean.

• Bridge Worlds: Offer to help your mentee “translate” their skills to your world; ask them to do the same for you.

• Celebrate Cultural Intelligence: Encourage sharing of holiday customs, rituals, or stories—diversity isn’t a problem to solve, it’s a gift to explore.

Treat difference as fuel for growth, not challenge to authority.

6. Mentorship for Equity and Inclusion

Quality mentorship can disrupt gatekeeping and bias, opening doors for people traditionally locked out of opportunity.

Equity Tips:

• Be an Advocate: Speak the names of underrepresented mentees for stretch assignments, promotions, and visibility.

• Make Space, Then Step Back: Invite input from those who have been excluded in settings—then hold your opinions long enough to let theirs land.

• Name Bias Gently: If you observe bias (yours or others’), call it in with curiosity, not accusation.

• Mentor for Access: Offer insights into the “unwritten rules” of your industry—demystify hidden gatekeeping.

• Get Comfortable with Discomfort: Commit to unlearning as much as you teach. Let mentees educate you about barriers you’ve never experienced.

Mentorship is one way we make “equity” real, person by person.

7. The Inner Work: Boundaries and Avoiding Burnout

It’s easy to cross the line from mentor to fixer, rescuer, or martyr. Sustainable mentorship requires self-awareness and self-care.

Self-Care Tips:

• Define Your Limits Early: Tell your mentee how and when you’re available, and what kinds of help you can offer (and what you can’t).

• Use a Support Network: Reflect with peer mentors—you need a sounding board, too.

• Recognize Burnout Signs: If you start feeling resentful or depleted, pause to address your own needs.

• Celebrate “Just Enough” Impact: Remember: being present—even just listening—can be enough. Don’t feel pressured to solve every problem.

• Practice Detachment: Help, but don’t own outcomes. The journey belongs to the mentee.

Healthy boundaries make mentorship a renewable resource, not an emotional drain.

8. Mentorship as Emotional Practice: Empathy Over Ego

Mentorship is not a knowledge transaction it happens in the emotional landscape: silence, doubt, vulnerability.

Emotional Intelligence Tips:

• Embrace Silence: Allow space for thinking, feeling, and “I don’t knows” in your conversations.

• Let Them Fail Safely: Frame mistakes as learning opportunities. Ask, “What did you notice in yourself afterward?”

• Encourage Reflection: After emotional episodes, invite the mentee to journal or talk through insights.

• Normalize Imperfection: Share your own moments of self-doubt to create psychological safety.

• Say “I’m Here”: Sometimes, your witness is more valuable than your wisdom.

Mentorship’s deepest power comes from its capacity to hold vulnerability without trying to fix it.

9. The Ripple Effect: Why Mentorship Still Matters

We live in a world addicted to scale and speed. Mentorship refuses disposability; it honors the person in front of you.

Amplifying Ripple Effect Tips:

• Celebrate Small Wins: Remind your mentee of their progress with concrete examples.

• Share Success Stories: Tell others about the impact of your mentoring relationship (with permission). This inspires new mentors.

• Encourage Peer Mentorship: Ask your mentee to reach out and support a peer; the ripple starts with one relationship.

• Teach “Pay It Forward”: Build into your final conversations a question: “How will you mentor someone else after this?”

• Document Learnings: Capture and share collective insights with your team or community.

Every act of mentorship shapes the systems we inhabit—one story, one influence, one degree of trajectory at a time.

10. Lifelong Mentorship: Growing With Every Season

Mentorship is not a phase—it is a practice that evolves through life's stages.

Lifelong Mentorship Tips:

• Revisit Your Mentoring Practice: Every few years, review and adjust how, why, and with whom you mentor.

• Stay Curious About New Trends: As industry and generation shift, keep learning.

• Mentor Across Life Domains: Retirement doesn’t end your usefulness—offer to mentor in volunteer, nonprofit, or community groups.

• Invite Feedback for Growth: Go back to your own mentors as a check-in.

• Let Go When Needed: Sometimes, the best next step is helping your mentee “outgrow” you and cheering them on from afar.

Mentorship outlives formal roles; it’s woven into a life well-lived.

11. Practicing the Practice

Mentorship, like muscle, grows best with repetition, stretch, and rest.

Daily Practice Tips:

• Reflect Briefly After Each Session: Ask yourself: What went well? What surprised me?

• Keep a Journal of Growth: Jot notes—not just about the mentee, but your own evolution.

• Observe Others: Notice how great coaches or teachers in your sphere interact; borrow what resonates.

• Mentor Across Differences: Seek out relationships that stretch your perspective.

• Adopt a Learner Mindset: Continue asking, “What am I still learning?” alongside each mentee.

Practice doesn’t make perfect—it makes you present, nimble, and ever more human.

12. Final Words: Start Messy, Stay Human

You don’t need credentials to mentor. You need willingness to listen, a few hard-won stories, and the humility to say, “Let’s figure it out together.”

Mentorship is not about completing someone else—it’s about showing up, again and again.

Start with a colleague, a student, a neighbor, yourself.

Because someone is walking a road you’ve already stumbled down.
And your hand-drawn, messy map might be exactly what they need not to follow, but to know “I am not alone.”

That’s mentorship. Always unfinished. Always alive. Always worth practicing.

About the Author
Tino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously—from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human—one verb at a time.

Subscribe now