Published on February 17, 2026

You're in a meeting where your VP says: "We need to move faster." Three developers immediately propose solutions: citizen development of non-critical features, CI/CD pipeline re-optimization, and next-gen intelligent coding tools. All technically sound. All potentially correct.

But you notice what wasn't said: she touched her wedding ring twice while talking about "faster," and her team lead looked down. You ask one question: "What's the timeline pressure coming from?" Turns out the company's biggest client threatened to leave, and the sales team promised features that don't exist yet. The problem isn't technical velocity—it's misaligned expectations between sales and engineering.

You just saved the company six months of architectural work solving the wrong problem. That's what listening is worth in 2035.

Last week, we explored trust-building as the foundation of the SCARRLET framework. Trust opens doors, but listening is what you do once you're through them. And here's the paradox that's reshaping compensation in technical fields: as AI gets better at processing information, human listening becomes more valuable, not less.

Let me explain why, and more importantly, how you can develop this skill to command premium rates in an AI-saturated market.

Why Listening Creates Economic Value in 2035

In a world where AI handles transcription, summarization, and information retrieval, you might wonder what's left for humans. Here's what I've learned: the scarcest resource isn't information processing—it's understanding what information means in context. AI models are rapidly improving their ability to accurately capture and process audio communication - the words that people use - but the ability to capture tone, intent, subtext, and other subtler, non-verbal cues remain elusive. This kind of "informal" information is certainly valuable today, but in the future, being able to precisely and consistently identify and interpret it properly will be the addition that differentiates human from machine value.

Think about your last important meeting. Someone said "that's interesting" in response to your proposal. Did they mean:

•        "I genuinely want to explore this idea further"

•        "I fundamentally disagree but don't want to fight right now"

•        "I'm confused and need you to explain differently"

•        "I have political concerns I can't voice in this setting"

The AI transcript shows the same two words regardless. But the person who can distinguish between these meanings—and respond appropriately—is the one who gets the project approved, builds the coalition, or prevents the six-month detour down the wrong path.

This is the economic gap. When technical skills are abundant, the ability to understand what people actually need, fear, want, and mean becomes the differentiator between commodity rates and premium compensation.

So, what's left for humans to do? Everything that matters. AI can process every word perfectly and still miss the entire point. It can tell you what was said but not really why it matters. It can identify that someone said "that's interesting" but not that they said it in the tone that means "I fundamentally disagree but don't want to fight in this meeting."

Think about your last project review. The AI notes captured every decision, every comment, every stated concern. But did it capture:

• The senior developer who went silent when the new framework was proposed, signaling resistance you'll face in implementation?
• The product manager who asked three different versions of the same question, revealing they don't actually understand the technical tradeoffs?
• The stakeholder who agreed to the timeline but used future tense ("we'll need to...") instead of present commitment ("we're doing...")?

This is the gap where careers are made and clients are won.

When everyone has access to perfect transcription and AI-generated summaries, the person who can actually listen—who can hear what's unsaid, understand what's beneath the surface, and connect implications that span contexts—becomes exponentially more valuable.

Two Sides of the Same Coin: Listening and Empathy Through Humility

Humility controls listening. There are many ways to talk about and practice listening. Popular flavors right now are empathetic listening and active listening. Those are both good, and this discussion employs aspects of both - having empathy is good for improving active listening, and good active listening helps improve empathy. However, they're not the same and one is not dependent on the other. So, before we get tactical, let's establish the foundation: active listening and empathy are expressions of the same thing—humility. And it is humility that makes any kind of listening technique reach its peak effectiveness.

Not humility in the sense of diminishing yourself; humility in the sense of genuinely believing the other person has something valuable to teach you. That their perspective, even when it conflicts with yours, deserves serious attention and might even be based on stronger foundations. That you might be wrong, and being wrong is an opportunity to become right.

A word of caution: don't take this too far. I'm not saying that you automatically have to give up what you think or believe. I'm not saying that the other person will always be right. They won't. I'm also not saying that they will always be wrong. They won't be that either. This is purely about having an attitude that looks for ways that the other person could be right, and letting that perspective guide you to places where more than one thing can be true.

We all see this failure constantly in technical conversations but might not actually notice it. A client describes a problem, and before they finish, the "expert" is mentally drafting their solution. They're not listening—they're waiting for their turn to be clever. Or alternatively, an "experienced" developer says that it can't be done because "we've already tried it before and it didn't work." Neither has really approached the conversation with humility, and both are likely to disappoint.

For those of us who've built careers on being "the person with the answer," this is uncomfortable. You're asking us to slow down, to not immediately prove our value, to risk looking less competent by asking questions instead of providing solutions. AI can generate solutions faster than any human can. Your value isn't in having the quick answer. It's in understanding the real question.

But here's the truth that took me years to learn: people don't pay premium rates for quick answers to surface problems. They pay premium rates for deep understanding of real problems.

The $35K consulting engagement goes to the person who spends the first hour asking questions that help the client see their problem differently. The staff engineer promotion goes to the person who listens to the team's frustrations and identifies the systemic issue everyone else treated as isolated incidents. The trusted advisor role goes to the person who hears what the CTO is worried about but can't say in front of the board.

That requires humility. And humility requires practice.

What You're Actually Listening For (and Why AI Can't)

When AI "listens" to a conversation, it's pattern-matching against training data. When humans listen effectively, we're doing something fundamentally different. We're listening for five things simultaneously:

1. What's not being said

In technical organizations, this is often where the real information lives. The team that doesn't mention testing during sprint planning. The solution architect who doesn't ask about scale during design review. The product owner who describes features but never mentions users.

AI can note absences if you tell it what to look for. But you have to know what should be there to notice it's missing. That requires patience, domain expertise, contextual awareness, and pattern recognition across situations the AI hasn't seen together because it hasn't been documented yet.

2. What they might not be aware of

People often don't fully understand their own situation. On the surface, that could easily sound like condescension, and it might be. But if we go deeper, we see another application of humility: since we all have blind spots, a careful listener might find one that they can offer to make the other person more right. Consider the engineering manager who complains about "communication problems" but doesn't see that their team is actually dealing with unclear requirements. The developer who says they "need better tools" when the real issue is they're overwhelmed by technical debt that hasn't been properly managed.

This is where your experience becomes valuable. Maybe you've seen this pattern before. Not the exact situation—every codebase, every team, every company is different—but the underlying dynamic. Or maybe your humble attitude leads you to ask different questions that raise an important, yet previously unnoticed change in their operating environment. You can hear past what they're saying to what they're experiencing.

3. What's beneath the surface—fear or hope

Technical conversations are often emotional conversations in disguise. The resistance to adopting a new framework isn't really about the framework—it's often about fear of becoming obsolete if they can't learn it fast enough. The push for "perfect" documentation isn't about knowledge transfer—it's about hope that this time, finally, the next team won't leave you with a mess to clean up when you start the next day.

AI can sorta identify emotional tone. But it can't tell you whether the frustration in someone's voice is "I'm angry at this situation," "I'm scared I can't fix this situation," or even "I can't focus because I can't figure out why my daughter is struggling in school." That distinction changes everything about how you respond.

4. What are the implications for you, them, and others

You're listening to a market manager describe their omnichannel marketing plan. AI captures every technical detail. But you hear three implications the AI missed:

• For them: They're moving some services off-prem to 3rd party vendors who will receive customer data, but they operate in a jurisdiction with reduced data privacy regulations. That could have a significant impact on customer satisfaction and net promoter scores, but it doesn't appear in their analysis, and they'll need to rework some parts factor it in.
• For you: You notice that their plan wants to add readiness for "emerging engagement technologies" but there's no indication of what that might mean. Adding the capability isn't really the problem, their lack of focus is, and going back and forth 50 times to help them get clarity isn't the kind of stress that your team needs.
• For others: The shipping/receiving team hasn't been consulted, and the plan's significant anticipated sales growth will double their shipping volume when they're already tight on warehouse space, loading dock capability, and their union is coming up on a likely contentious contract negotiation.

You're not just listening to information. You're listening for impact across a network of relationships and constraints that no single AI model comprehends because it spans technical, organizational, and human systems simultaneously.

5. What you can prepare to show them hospitality in the future

This connects directly to the trust-building we discussed last week. Effective listening isn't just about the current conversation—it's about gathering information that lets you serve them better later.

A client mentions their daughter starts college next year. The team lead mentions they're trying to learn Rust. A stakeholder mentions they're presenting to the board next month. None of this is in the meeting agenda. The AI might note it, but it won't connect it to action.

You will. You'll send an article about Rust patterns in production systems. You'll ask how the board presentation went. You'll remember his tuition stress when having budget discussions and that the team leader went to the same college.

This is listening that builds relationships, not just captures data.

Listening Across Four Futures

Our strategic foresight scenarios reveal how listening creates competitive advantage in different 2035 contexts:

Scenario 1: AI Wonderland – Every consulting firm has AI that analyzes client meetings and generates recommendations. You're competing for a $500K transformation engagement. During discovery, the CTO mentions "our legacy systems" three times in five minutes—each time with slightly different energy. You're the only consultant who asks: "Which legacy system keeps you up at night, and why?"

Turns out there's a 15-year-old monolith that processes payments, written by developers who've all left, that nobody wants to touch, but everyone depends on. Every other firm proposed generic modernization. You proposed a technical strategy that meets their need and a client experience strategy that addresses their actual fear. AI heard "legacy systems." You heard "existential risk we're afraid to admit." You win the contract.

Scenario 2: What Do You Want? – The young devs on your team say they need workstations and sprint teams that are hyper-personalized to them to be able to reach productivity goals. Most managers would push back and point out that senior devs don't have the same hyper-personalization demands, so they don't need it either.

They respond by showing you the results of their work environment AI model that draws on their previous performance and generally accepted science on the relationship between performance and work context factors. It's all algorithmically optimized, all technically sound.

You spend an hour listening to their pitch and asking questions about how the young devs actually work. You discover: workstations and sprint assignments might not be ideal, but they're not the problem. Instead, the young devs are dealing with a steep learning curve in their first interaction with real-world limitations, and they're nervous about being let go if they don't keep up with the senior devs.

The problem isn't technical—it's leadership.

As their supervisor, you didn't send the right messaging about what you expect from them. When they compared themselves to the senior devs, they grew insecure about their position, and started becoming distracted by fears of losing their job in a tight labor market. You design a solution addressing psychological safety, not infrastructure, and reinforce the existing mentorship program.

The young devs start growing faster and the senior devs identify and implement modest changes to assignments that increase everyone's work satisfaction and engagement. The team accelerates productivity, climbs from the 6th of 10 teams to the 2nd for productivity, and other teams begin adopting the new work structures. You solved what the young devs actually needed, not what they asked for. AI optimizes for stated requirements. You listened for real needs.

Scenario 3: Bad Cities, Bad Bosses – Pressure from domineering political figures forces your marketing agency to adopt an AI-recommended content creation framework that makes no sense for your actual work. In the mandate meeting, most staff either complain or comply - some openly plot resignations or revolts. You listen differently: you hear that the deputy director keeps saying "accountability" and "visibility."

You realize this isn't about the framework—it's about their need to demonstrate control to elected officials after a high-profile project failure. You propose implementing the framework for external reporting while rapid-developing a new AI model and metrics designed to capture entirely new layers of data to add broader context to the analysis of the project's results. After all, you have enough internal data to provide a good data set of inputs/outputs for the original practices.

The results indicate that the new practices significantly increase the time-spend to create and review the messaging, and it also makes it clumsy. As the icing on the cake, you've always suspected that the first project succeeded in areas beyond the stated objectives, but you couldn't prove it because they were considered out of scope. The model's expanded scope confirms your belief and gives your director the data she needs to push back - because you heard the political problem beneath the technical mandate. AI solves compliance. You solved politics.

Scenario 4: Status: Home Sick in Bed – Your client's development team has 40% turnover and chronic burnout. Needless to say, their health insurance provider is paying attention to employees' health stress analytics and costs are starting to rise - precipitously. AI analysis shows: workload, deadlines, on-call rotation issues.

Every consultant pitches: better project management, more hiring, rotation optimization. You spend three hours with individual developers. You listen past their complaints about work. You hear: fear. They're terrified they'll miss something critical and someone will get hurt because they're building healthcare software where mistakes have consequences. Maybe worse, they signed on to this company, and this project in particular, because they saw it as a real hope for improving health for seniors - just like their parents and grandparents. But the devs are starting to feel like what was once source of passion is getting trapped and mutated by marketing's preferred messaging, administrative red tape, and deprioritization in favor of projects with a higher anticipated profit margin.

The real problem isn't workload—it's unspoken moral injury from feeling responsible for patient safety without adequate support and feeling slightly betrayed by compromises to the mission. You can't solve administrative red tape or marketing's preferences, but you might be able to redesign some of their processes and the project's features to bring down production costs and increase value add to reach new market segments.

More importantly, you can be the partner who brings in a massage therapist for a day each quarter, relays stories from patients who desperately need their project to succeed, and feeds program managers subtle reminders about how "mission creep" can affect their options in the labor market. The company keeps you on $50K/month retainer because you heard what they couldn't articulate.

Across all scenarios, listening creates value by connecting what's said to what's meant, what's needed to what's asked for, and what's technical to what's human.

Why AI Makes Listening Harder (and More Valuable Once Mastered)

Several forces are making genuine listening more difficult:

Meeting overload and cognitive saturation: You're in 6-8 hours of video calls daily. Your calendar is blocks of back-to-back meetings. AI can help you do the prep work to maintain that kind of pace, but it can't help you stay focused. Your attention is fragmented, your energy depleted. Genuine listening requires cognitive capacity you don't have - and AI keeps you chasing.

The AI dependency trap: Because AI generates meeting summaries, you stop actively listening during meetings. You're half-present, knowing you can "get the notes later." But the notes capture words, not meaning. You're losing the skill through disuse.

Missed connections: More work happens in Slack, tickets, PRs, documents. Less happens in real-time conversation. AI can do a decent job of working out sentiment, but when it's doing that work for you, you're losing the practice of listening to tone, pace, and emphasis—all the paralinguistic information that carries meaning. And it definitely isn't doing anything to help you build trust with colleagues.

Performance pressure: In technical roles, you're evaluated on solutions delivered, velocity maintained, incidents resolved. Nobody measures "listened deeply to understand the real problem." So, you optimize for speed, not understanding. You interrupt with solutions because that's what looks productive.

These forces shrink an already scarce supply of attention in your life: in environments where everyone is partially present and AI is fully transcribing, the person who can give complete attention becomes extraordinarily valuable.

But here's the hard part: you can't fake this. People know when you're really listening versus performing listening while mentally composing your response. Ironically, they don't even have to pay much attention to recognize that you aren't really either. As humans, we can feel when we're being ignored.

What's Next

So how do you actually develop listening as a skill that commands premium compensation? What are the specific techniques that distinguish "AI-augmented note-taking" from "deep human listening"?

That's what we'll tackle next week in Part 2 of this article. I'll share specific practices: how to be quiet and give people space to think, how to listen with all five senses, what Native American listening traditions can teach technical professionals, and what listening sounds like for neurodivergent folks.

These aren't soft skills. They're the techniques that separate short-term contractors from $35K/month advisors.

Until then, here's your reflection question:

Think about the last conversation where you were explaining a complex system or problem. Did the other person actually listen to understand, or were they waiting to offer solutions? How did you know the difference? How did that feel? And more importantly—when was the last time you gave someone that quality of attention?