Whether the confident, authoritative voice that drove the decision got the best outcome - or just the fastest one?
Whether the things that would have made it succeed were left unsaid - not because people didn’t see them, but because it didn’t feel safe, or worth it, to say them?
If you have - you already understand the difference between authority that commands compliance and leadership that earns commitment.
The difference between leading from a place of proving and leading from a place of purpose isn’t visible. But it’s felt. The style doesn’t define the leader. Knowing when to be direct and when to listen, when to push and when to hold back - that’s skill. But the style is just the delivery. What matters is what’s driving it. And when that source is genuine purpose rather than the need to prove - people feel it, even when they can’t name it.
That difference shows up in whether people comply or commit. Whether difficult truths surface early - while something can still be done - or stay hidden until the cost is already paid. Whether teams bring their best thinking to difficult problems, or simply what they think leaders want to hear. In complex organisations, compliance is not enough. In transformation and delivery environments, I’ve seen this difference repeatedly: authority can drive fast decisions, but commitment is what sustains execution when things get hard.
So the question underneath all of it - the one most leaders never stop to ask - is this: where is your leadership actually coming from?
That question is really a question about personal power. Not the formal kind - the title, the authority, the org chart. But the internal kind. The source that determines whether your leadership lands or just occupies space.
Janet Hagberg spent decades researching exactly this. Her model - the Six Stages of Personal Power - gave me language for something I’d been observing in organisations and leadership for years, but had never been able to fully articulate. She defines personal power in a way that immediately reframes the conversation:
“Personal power is the extent to which one is able to link the outer capacity for action with the inner capacity for reflection.”
I came across her work in Leon VanderPol’s A Shift in Being. And what the model maps - six stages through which our relationship with personal power develops - isn’t a hierarchy of better or worse. It’s a mirror. One that shows you where you are, what’s driving you, and whether you’re leading on purpose or on autopilot.
Research is catching up to what many experienced leaders already know. Chris Lipp, writing in Leader to Leader in 2025, argues that the dichotomy between servant leadership and dominance is fabricated - that personal power is an internal state that radiates outward, underlying courage, authority, and trust regardless of leadership style. The source, not the style, is what people respond to.
Hagberg’s model identifies six stages through which our relationship with personal power develops over a lifetime. Each stage isn’t just a mindset - it’s a whole way of being. How you see yourself, how you relate to others, and critically - the source of your power.
You don’t move through these on a fixed timeline. What moves you is awareness and the willingness to look honestly at what’s driving you. Read through and see where you recognise yourself - not to judge, but to see clearly.
Dependence, low self-esteem, a sense of being trapped. Helpless - but not hopeless. The first stirring of power is the recognition that something must change.
Identity is borrowed from others - a mentor, a group, an institution. Power comes from who believes in you and who you stand next to.
The dominant stage in most professional cultures. Ambitious, competitive, relentless. Power is earned through results. This is where the warrior fights hardest - and where many stay indefinitely, mistaking the treadmill for the destination.
A turning inward. The achiever begins to question their own story. More collaborative, more honest, more capable of mentoring. The ego softens enough to actually listen.
The Wall - Moving beyond intellect · Letting go of control · Facing the shadow · A crisis of integrity
Self-accepting, courageous, grounded. Living from a sense of calling rather than a hunger for recognition. The warrior energy remains - but now it serves something larger than the self.
Quiet service. Compassion without agenda. Power without need for recognition. The ego has been thoroughly surrendered; what remains is presence.
Stage 3 - Power by Achievement - is where most ambitious people live. It built something real. The expertise, the results, the drive to deliver. There is genuine power here, and it shouldn’t be dismissed.
But it has a ceiling. And at some point, for almost everyone who has pushed hard enough and long enough, something shifts. VanderPol calls it the inner earthquake - the signal that something needs to change, not in the strategy, but in the source.
Between Stage 4 and Stage 5 sits what Hagberg calls “The Wall.” It cannot be strategised around. It demands something the achievement-oriented leader finds almost unbearable: letting go of the identity that achievement built. VanderPol frames this as a “crisis of integrity” - the moment the gap between the leader you’re performing to be and the leader you actually are becomes impossible to ignore.
What emerges on the other side of The Wall is not weakness. It is a more refined, more durable, and ultimately more powerful version of the warrior. Stage 5 - Power by Purpose - keeps all the courage, commitment, and inner fire of Stage 3. But the energy is no longer pointed at proving. It’s pointed at something worth building.
This is the archetype that speaks to anyone who has felt the pull between ambition and meaning - between doing more and being more.
Authority without purpose is influence people endure. Purpose behind power is something people feel.
This framework doesn’t ask you to stop being a warrior. It doesn’t say ambition is the problem, that achievement is shallow, or that you should want less. It says: there’s more.
The drive, the discipline, the willingness to do hard things - all of that is still present in Stage 5. It’s just pointed at something different. Not at proving. At building something that genuinely matters. And paradoxically, that’s when leadership becomes most powerful. Not power over. Power with.
The warrior who proves and the warrior who leads are not as far apart as they look. The journey between them doesn’t require you to become someone else. It requires you to lead from a deeper place - past the performing, past the need to be the most capable person in the room, toward something your team can actually follow. Whether you’re in Stage 3, at The Wall, or somewhere in between - the question is the same one we started with: where is your leadership actually coming from? And is it getting you the outcomes that matter?
The framework is a mirror. See where you are. See what’s driving your leadership. And then lead - consciously, not by default.
Where is your sense of power coming from today? And is it actually working for you?
Which stage are you at?
Learning to resolve conflict - whether de-escalating high-stakes situations or putting out an emotional fire - is one of the highest-payoff skills you can develop. It’s key to building relationships based on trust and respect, creating high-performing teams, and establishing yourself as a calm, composed presence.
At the heart of this skill is learning how to have honest conversations - ones that are both candid and compassionate. These conversations build credibility, deepen trust, and unlock team potential.
Honest conversations show that you:
When people shy away from these conversations, small issues grow into bigger ones. Misunderstandings linger, performance drifts, and resentment builds quietly.
But leaning in, builds a culture where people feel safe, respected, and accountable.
In this article, I’ll share a practical framework combining Radical Candor, Emotional Intelligence, and problem-focused conversations - tools that turn friction into trust, mistakes into lessons, and tough talks into breakthroughs.
I’ve been using this approach for years, and it has worked for me time and time again.
Read on to learn how to handle difficult conversations while strengthening relationships and driving better outcomes.
Real impact comes when you combine three essential skills:
1 - Radical Candor: Care Personally + Speak Directly
How you frame your words to balance care and honesty.
2 - Emotional Intelligence: Know your emotions and triggers -> Manage yourself -> Act intentionally
How you manage your reactions, notice triggers, and pause before responding.
3 - Focus on Problems, Not People
How you focus on the issue, not the person, and suggest actionable next steps.
Applied together, these tools turn conflict into trust, safety, and innovation, making difficult conversations productive, empowering, and growth-oriented.
We’ll use this scenario throughout the article: Imagine a team member repeatedly submits code with errors that slow down the project. You need to address it, but you want to handle it effectively.
Radical Candor blends empathy and honesty (Scott, 2017). It’s about addressing issues clearly while showing you value the person.
Show respect and belief in the person’s potential. Treat interactions as opportunities to empower, not judge.
Address the issue clearly and honestly, without sugarcoating.
Example: A team member consistently misses small but important details in code reviews. Instead of ignoring it or snapping, you say:
“I see the effort you’re putting in, and I really want you to succeed, and I want to help you. Here are a few key details we need to focus on - let’s work through them together.”
This balances care with challenge, showing Radical Candor in action: addressing the issue clearly while demonstrating belief in the person’s potential.
Conflict is best handled when paired with Emotional Intelligence. Here’s how to make it actionable:
Identify your emotional triggers. Notice how your body, thoughts, or tone change when you’re stressed, frustrated, or defensive. Awareness is the first step.
💡 Practical tip for self-reflection
Set aside 10 - 15 minutes at the end of the day or after a challenging situation.
Write down:
1. What triggered a strong emotional reaction?
2. How did you respond?
3. What could you do differently next time?
Over time, patterns will emerge. You’ll start recognizing your triggers early, anticipate your reactions, and develop strategies to handle them more effectively. This small daily habit can significantly improve your emotional awareness and control.
Pause before reacting. Use micro-breaks, breathing, or self-talk to regulate impulses. If emotions are high, it’s okay to step away or delay a response. Decide whether to respond immediately or address it later in a controlled setting. Small actions - like counting to ten, taking a short walk, or repeating a calming phrase - can help you regain composure.
Respond intentionally, focusing on outcomes, solutions, and collaboration rather than venting emotions.
💡 Practical tip
Prepare a few go-to phrases for situations you frequently face, so you can respond calmly when emotions run high.
Sometimes the best action is to wait and address the issue later - whether one-on-one or in a calmer forum - rather than reacting in the heat of the moment.
Example: During a code review, a repeated error is flagged by another team. Frustration rises, and the stakes feel higher, but instead of snapping:
“Thanks for highlighting this. I’ll work with the team member to fix it and will also escalate this appropriately.”
“I noticed a few details were missed again - we’ve discussed this before. Let’s work through them together, and I’ll escalate with context so we can prevent it from happening again.”
The conversation stays problem-focused, modeling composure, while signaling accountability and follow-up.
Additional reading: Daniel Goleman’s Emotional Intelligence Theory and the 6 Seconds EQ Model.
Separate the problem from the person:
Highlight concrete behaviors or results, not personalities.
Align on goals, not blame.
Example: Using the same code review scenario, instead of saying, “You always miss key details,” you could say:
“I noticed some details in the last review were missed. What if we set up a checklist to ensure we cover these consistently?”
This keeps the conversation productive and moves toward actionable solutions rather than blame.
Applied together, these principles turn conflict into a growth engine:
Psychological Safety: People speak up without fear. Trust: Honest, empathetic feedback strengthens relationships. Innovation: Diverse perspectives surface, get debated, and improve outcomes.
Even tense situations become opportunities for alignment, learning, and better solutions.
Even with the best intentions, conversations don’t always go perfectly. Here’s how to recover and maintain trust:
Acknowledge: If the discussion got tense or your response wasn’t ideal, acknowledge it briefly.
“I realize I may have come across too strongly earlier - thank you for your patience.”
Reset: Clarify your intent and refocus on the outcome.
“My goal is to ensure we’re aligned and can prevent this from recurring.”
Follow-up: Check progress and reinforce accountability.
Schedule a follow-up meeting, or revisit the discussion after the team member has acted on feedback.
Invite perspective: Model openness and learning by asking,
“How did that land for you?”
This encourages dialogue, surfaces misunderstandings, and strengthens trust.
Think back to a recent situation where a conversation didn’t go as well as you’d hoped - maybe a team member missed a deadline, or a meeting left you frustrated.
Take a moment to reflect: How might the outcome have been different if you used these approaches? Consider trying them in your next conversation. Start small, experiment, and notice the difference it makes - not just for results, but for relationships and trust.
Every tough conversation I’ve faced became easier once I combined care, clarity, and focus. Conflict doesn’t have to be scary - Radical Candor + Emotional Intelligence + problem-focused conversations = trust, safety, innovation.
Sprinkle in empathy and intentionality, and your interactions don’t just solve problems - they empower people and strengthen relationships.
That thrill of seeing a website, system, or product come alive, creating something from nothing - was its own reward.
For me, recently, I’ve rediscovered the thrill of building, and I’ve been absolutely loving it. Every working prototype, every experiment reminds me why I fell in love with creating.
Before the Industrial Revolution, artisans controlled every step of their craft. I imagine the mastery of their skill would have been deeply rewarding, each creation a reflection of care, expertise, and pride. Artisans could take delight in every step of their work.
Ikigai, the Japanese concept of finding joy and purpose in one’s work, reminds us that fulfillment comes from such mastery. A vivid example comes from Ken Mogi’s book, where a Michelin sushi chef wakes at 4 a.m. to pick the best fish for his customers - a dedication that embodies mastery and purpose.
Then mass production arrived. Many artisans were replaced, while managers orchestrated systems at scale, and hierarchies shifted. The focus moved from craft and mastery to efficiency and oversight.
Now, AI is rewriting the rules again.
By automating routine work, it is giving us the chance to return to what matters most: craft, mastery, and building things that reflect our skill and creativity.
Leaders can combine hands-on creation with strategic oversight, the new “maker-manager” model.
Jensen Huang: “AI is the greatest technology force of our lifetime. It’s the great equalizer. Everybody can be a programmer now - you just have to say something to the computer.”
Gulf Insider: NVIDIA CEO: AI ‘Greatest Equalizer’ Of Time
Forbes: Artificial Intelligence: The Great Equalizer
Satya Nadella: “Don’t be a know-it-all; be a learn-it-all.” “You don’t get fit by watching others go to the gym. You have to go to the gym.”
Fortune, May 2024
Microsoft Ignite 2017 Keynote
Quote in “Hit Refresh”
This analogy highlights that the same holds true for leadership and creation: you can’t sit on the sidelines - you have to actively build, experiment, and participate.
It is about time. This should not be a surprise - switching back to an IC role, building while leading, or rediscovering the joy of creation, whatever the job title may be, however one chooses to build, should be normal, expected, and celebrated.
It opens up new opportunities and lets us leverage the democratization that AI enables. Why should managers not enjoy the same potential as solo founders, billion-dollar ventures, or new ways to create value? It is a win-win: returning to building or leading and building together amplifies both impact and optionality.
Above all, this is about championing the freedom to create, for leaders and makers alike, without judgement.
What are you building right now? I’m keen to hear.
]]>The conversation around engineering debt usually centers on code quality and refactoring. But in practice, debt takes many forms - messy code, outdated tools, clunky workflows, and even deeper team and ownership issues.
Imagine your engineering organization as a grand old building. You might spot a few cracks in the walls - fragile code, legacy systems, manual release processes - and teams might debate how urgent the repairs are, scramble for funding, or argue over whose responsibility it is to fix them. But sometimes, the real problem is deeper and more structural: the very foundation weakened, not just by technical shortcuts and process pain, but by years of shifting roles, unclear ownership, and blurred accountability.
This is the hidden crisis facing teams moving from project to product. If you don’t spot and fix the full spectrum of engineering debt - technical, process, and organizational - even the best AI-powered features will be built on shaky ground. In the age of AI, these weaknesses are exposed faster and more brutally than ever before.
In this two-part series, you’ll get practical strategies and real-world examples - from Twitter to Netflix and Etsy - to help you:
Part 1 dives deep into how to spot the warning signs and shine a light on the cracks. Part 2 will show you how to fix them for good.
If you want your AI-powered features to deliver real value - not just demos or prototypes - this series is your roadmap.
Across engineering, product, and delivery teams, the pressure to move faster has never been greater. With AI-powered coding assistants and AI technologies accelerating feature development, the gap between rapid delivery and sustainable, reliable systems is wider - and riskier - than ever before.
But what if the biggest thing slowing you down isn’t the AI technology itself, but the hidden engineering debt quietly sabotaging your efforts?
Drawing on respected sources like the DevOps Handbook, Martin Fowler’s technical debt quadrants, and my own two decades in engineering, I’ve found it useful to think of engineering debt as three interlinked categories: technical, process, and organizational. Understanding which one is your biggest bottleneck is essential to prioritizing your cleanup efforts - especially when resources are tight.
Engineering debt isn’t just a technical problem; it’s a complex mix of code shortcuts, broken processes, and misaligned teams that accumulate over time. And it can cripple organizations of any size - from startups to giants.
This article is for you - the leader who needs clarity on:
And if you’re an engineer facing these challenges firsthand, you’ll learn:
Together, we’ll uncover the hidden saboteurs slowing your AI ambitions and explore practical ways to reclaim control.
Because in today’s AI-driven world, building on a shaky foundation won’t just slow you down - it will cause costly outages, lost customers, and frustrated teams.
When Twitter faced a string of major outages in 2022, it wasn’t just bad luck or a few buggy features. Behind the scenes, years of accumulated engineering debt - technical shortcuts, patchy processes, and organizational misalignment - had built up like rust on the engine.
This hidden debt left their system brittle, turning rapid growth into repeated firefighting. The constant firefighting drained resources and slowed innovation, illustrating how hidden debt can paralyze even the most high-profile platforms.
It’s a story many tech leaders know too well: moving fast without fixing the cracks first can bring your whole product to its knees.
When your engineering ship feels like it’s taking on water, it’s tempting to throw everything at the problem. But without focus, you risk sinking faster.
The first step? Understand where the debt lives.
Here’s a quick test:
Engineering debt hides in three key places, each with distinct causes and consequences:
This is the classic “technical debt” as originally popularized by Ward Cunningham and later clarified by Martin Fowler. It lives inside the codebase or tech stack and covers:
Example: Netflix’s microservices sprawl became so complex their teams invested heavily in chaos engineering - intentionally breaking parts of their system to build resilience and combat hidden technical debt.
Process debt arises when your delivery workflows are bogged down by slow, manual deployment steps, painful release processes, or approval gates that add delay without clear value. Common signs include:
Example: Etsy moved from monthly or weekly releases to continuous deployment, releasing dozens of times a day - a cultural revolution that turned process debt into a competitive advantage.
While continuous deployment focuses on improving workflows (process debt), it requires addressing underlying technical debt - like automated tests and reliable pipelines - to enable safe, rapid releases. So, reducing process debt often involves fixing some technical debt along the way.
The most subtle, and often the most crippling - the human and structural issues that slow teams down:
Example: Sometimes the blocker isn’t doing the upgrade - it’s figuring out who’s responsible for doing the upgrade. If your team spends more time chasing ownership than fixing the issue, you’re facing organizational debt.
Spotify’s ‘squad’ model was designed to break down these silos, empowering small, autonomous teams with clear ownership to accelerate delivery and innovation.
Much has been written about technical debt, but organizational debt is the debt you owe your organization to fix - because without it, technical and process improvements won’t stick.
You can’t refactor your way out of a bad org chart.
If ownership and accountability are unclear, no amount of cleaner code or automated tests will save you - because no one will feel responsible for maintaining them.
By tackling organizational debt first, leaders create the environment where teams are motivated and empowered to address technical and process debt effectively.
Remember: What looks like a technical problem often hides an ownership problem. Fix the foundation first, and everything else follows.
If you’re an engineer experiencing these challenges firsthand, start by identifying which category your blocker belongs to.
When you raise concerns, frame them in terms leadership understands:
Be clear, evidence-driven, and constructive - this gives your voice more weight and opens doors for change.
Make ROI part of your case:
Leadership is often persuaded by the tangible return on investment for tackling engineering debt. Try to quantify how fixing the debt will:
The more you can show how tackling debt pays off—whether in dollars saved, time gained, or customer value delivered—the more likely leadership will listen and act.
Not all engineering debt is accidental. Sometimes teams take on intentional debt to move fast, trading short-term speed for long-term cost. This can be a strategic decision - but only if there’s a clear plan to pay it back.
Viewing engineering debt this way empowers leaders to balance speed and quality without fear, treating debt as a tool, not a trap.
Use this quick test to identify your biggest bottleneck.
Q1: If you had all the ownership and approvals you needed, could you fix it without changing how teams are structured? ✓ Yes -> Technical Debt
Q2: Is the main slowdown caused by steps, tools, or approvals that are too slow or manual? ✓ Yes -> Process Debt
Q3: Is the main challenge figuring out who owns the work, or aligning the right people to do it? ✓ Yes -> Organizational Debt
If your engineering feels like this, it’s a red flag that debt is slowing you down - don’t wait for collapse:
If you spot two or more, it’s time to dig deeper.
Start by gathering evidence of where the pain points are. Look for your loudest alarms - these symptoms reveal the kind of debt slowing you down:
| Symptom | Likely Debt Type |
|---|---|
| Frequent bugs, brittle code | Technical Debt |
| Manual workflows, slow pipelines | Process Debt |
| Miscommunication, unclear ownership | Organizational Debt |
Then prioritize what to fix based on impact, feasibility, and potential ROI:
Start small, track progress, and build momentum - each win chips away at your debt and frees your team.
Pro Tip: Apply the Pareto Principle
Often, about 20% of your engineering debt causes 80% of the problems slowing delivery. By identifying and tackling that critical 20%, you unlock disproportionate improvements fast - making the cleanup effort more effective and motivating your team with visible wins.
Sometimes the boundaries blur. For example:
Ultimately, use these categories as practical guides to identify and fix problems - not to get stuck on exact labels.
One of the biggest challenges with engineering debt is that it often hides in plain sight - slowly eroding your systems and processes without obvious warning signs.
You can’t fix what you don’t see - and that’s where tools become your eyes in the dark.
Data doesn’t lie. Let it be your early warning system.
Successful organizations don’t rely on gut feelings alone. They invest in tooling and monitoring to surface hidden problems early, giving them time to act before small issues turn into costly disasters.
These tools generate measurable signals - like warning lights on a car dashboard - that help teams and leaders understand where the real pain points are, whether in code quality, deployment reliability, cloud costs, or team dynamics.
As you add AI-powered features, you’re building on complex layers that demand agility and reliability. If your foundation is shaky, AI won’t speed you up - it will expose weaknesses and slow you down.
AI isn’t magic - it’s a magnifier. It speeds up your good practices and amplifies your mistakes. A turbocharger only works if your engine doesn’t blow up.
Think of AI as a highly skilled but impatient junior developer - producing code fast but without full awareness of reliability, scalability, or security needs.
That’s where seasoned engineers bring judgment and experience, bridging the gap between rapid AI-generated code and stable production systems.
The tools and practices for detecting technical, process, and organizational debt matter now more than ever.
AI is becoming your watchful assistant, able to:
But AI is a turbocharger, not a steering wheel. Skilled engineers and strong leadership still drive the cleanup.
Innovation without a strong foundation is a house of cards.
Your journey to adopt AI features deserves a foundation built to last. By shining a light on technical, process, and organizational debt, you gain the power to untangle the knots slowing your innovation.
Don’t wait until your product falters. Start today: audit your systems, invest in visibility tools, and empower your teams to act boldly.
Ready to lead your team past the hidden threat?
Take a moment to reflect: How strong is your engineering foundation? What hidden debts might be slowing your team’s true potential?
But as I set up a new blog today, the rules are changing. In these agentic times, the question isn’t just “How do humans discover my content?” but also “How do AI agents find and understand it?”
That’s why Dharmesh Shah’s recent post on Agent Index Optimization (AIO) landed exactly the right moment, especially with tools like Comet by Perplexity reshaping how people search. As AI agents increasingly become our intermediaries for search, learning, and decision-making, being agent-readable is becoming just as important as being human-readable.
Dharmesh shares some practical guidance, but two points stood out for me:
1. It’s still about value.
Whether your content is discovered via search engines or AI agents, what ultimately matters is whether it delivers genuine value to people. Without substance, no optimization can save it.
2. Technical steps can help.
From improving your robots.txt to implementing llms.txt, and even setting up an MCP (Model Clarity Protocol) server, there are ways to make your content easier for agents to find, parse, and understand. These steps don’t replace value - they amplify it.
A big thank you to Dharmesh Shah for sharing timely, actionable insights. His work is invaluable for anyone navigating this new space.
This is a space I’m increasingly curious about, particularly as it relates to the evolving AI economy and the democratization of AI.
In the search engine and browser era, monetization wasn’t built in from the start. It was added later through mechanisms like ads and platform-based engagement - what Ben Thompson calls the internet’s “Original Sin”.
In the agentic era, the challenge may be even greater. As AI agents become the primary interface between users and the web, traditional models of value creation and capture may no longer hold. We’ll need to be more intentional about how content is discovered, and how creators are credited, compensated, and trusted in this new paradigm.
Content that combines authentic value + technical clarity will stand the best chance of thriving.
How can creators ensure they remain visible, valuable, and fairly rewarded in an agent-driven web? I’d love to hear your ideas.
]]>After a long break, I’m excited to start sharing again - this time on engineering, AI, coding experiments, and reflections on engineering leadership, growth, and identity.
This will be my space to capture what I’m learning, building, and thinking about.
Whether you’re building, leading, learning, or just curious, I hope you’ll find ideas here that spark inspiration or offer something useful for your own journey.
Stay tuned for stories, experiments, and insights ahead.
]]>