Your career runs thirty-plus years across a string of employers who will never meet each other. The gap between what this job builds in you and what your next five jobs will need is yours to close. Nobody else is even looking at it.

That gap is what “investing in yourself” actually means. Everything else is consumption dressed up as growth.

So treat it like the portfolio it is. You have four asset classes, and most people are badly overweight in one and empty in the rest.

1. Development: compounding skill equity

The lazy version of development is consumption. Courses you don’t finish, books you highlight and forget, podcasts on 2x while you do the dishes. It feels like progress because your brain rewards novelty. It produces almost nothing, because a skill you can’t demonstrate is a skill you don’t have.

Real development forces the skill into your hands. You build the thing, ship the thing, get the thing wrong in public, and fix it. Reps, not inputs.

And be ruthless about which skills get your scarce hours. Two filters:

• Does it compound? A compounding skill makes next year’s version of itself easier: writing, judgment, selling, systems thinking. A decaying skill resets every time the tool changes.

• Does it transfer? Mastery of your company’s internal stack dies the day you leave. Mastery of a durable craft follows you out the door.

Spend on the skills that clear both bars. An hour a day is roughly 250 focused hours a year. Three years of that is more deliberate reps than most people accumulate in a decade of passive exposure. The compounding is the whole point, and it is invisible right up until it isn’t.

2. Fill your battery: the maintenance nobody expenses

This is the pillar people skip, and it is load-bearing for the other three. You cannot compound from empty. Energy is the input to development, to challenge, to showing up in hard rooms. Run it to zero and every other investment stalls.

Burnout is not a badge. It is asset destruction. You are liquidating future capacity to hit a near-term number, and the market never pays you back for it.

So protect the inputs like they matter, because they are the inputs to everything you’re trying to build. Sleep. Whatever reliably recovers you, and you know what it is. Hard boundaries around both. The reframe worth internalizing: rest is not the reward for the work. It is part of the work.

3. Challenge yourself: deliberate risk exposure

If the work is easy, you are coasting on stored value. You get paid, you get comfortable, and you get slowly worse relative to everyone who chose discomfort.

Growth lives at the edge of failure. The useful test: what are you working on right now that you are genuinely not sure you can pull off? If the honest answer is nothing, your challenge dial is set too low and you are treading water in warm water.

The key word is deliberate. The stretch your manager assigns arrives on their timeline and serves their needs. The stretch you choose serves your career. Pick the project, the talk, the domain that scares you a little, on purpose, before anyone hands it to you.

4. Be the small fish: proximity is the cheapest tuition

The highest-return move most people avoid, purely out of ego, is putting yourself in rooms where you are the least experienced person there.

It is uncomfortable. It is also the fastest learning environment that exists, because proximity beats content. You absorb judgment, taste, and standards ambiently from people operating a level above you, in a way no course will ever deliver. You learn what “good” even looks like by standing next to it.

If you are the smartest person in every room you’re in, you have optimized for status and starved your growth. Go find rooms where you’re the small fish, or engineer them: a mastermind, a harder team, a community of people clearly ahead of you. Then shut up and pay attention.

So: how are you doing it?

The framing is nice. The audit is what matters. Run these four questions honestly, right now:

1. Development. What can you do today that you couldn’t twelve months ago? If you can’t name something concrete, you consumed, you didn’t develop.

2. Battery. Are you compounding or liquidating? When did you last feel genuinely recovered, not just less tired?

3. Challenge. What are you working on that you might actually fail at?

4. Rooms. Where are you the small fish right now? If the answer is nowhere, that is the first thing to fix this week.

Here’s my own answer, because I won’t hand you an audit I’m dodging myself. This week an invite landed to fly out to San Diego for a three-day mastermind, and I said yes before I could rationalize my way out of it. One rule going in: open mind, learn from everyone. The room was eclectic, which is exactly why it worked, and I took something from nearly every conversation, including the ones I’d have skipped if I were optimizing for “relevant to me.” The part I didn’t expect: being the small fish didn’t mean having nothing to give. I could help a lot of the people in that room too, and that exchange is what turned strangers into real connections, inside the sessions and well outside them. Three days. The compounding has already started.

The market doesn’t reward potential. It rewards what quietly compounded while nobody was watching. That is entirely on you, which is the good news.

Your turn. Which of these four are you winning, and which have you been quietly avoiding? Drop it in the comments, then read what everyone else put down and take something from it. Treat this thread like its own eclectic room: the whole point is to be the small fish and learn from the people in it. Build on what someone else says. Steal what’s useful. That is the portfolio working.

Somewhere in your org right now, there’s someone excellent who’s about to get “meets expectations” while a louder colleague gets the promotion.

The manager isn’t corrupt. They’re not playing favorites. They just can’t describe, in specific terms, what the quiet one actually did this year. And you can’t reward what you can’t describe.

If that stings a little, good. Because the quiet one might be you.

The myth that keeps good people invisible

Most of us are raised on a comforting idea: do great work, and it will speak for itself.

It won’t. Work doesn’t speak. It’s mute. It sits in a closed pull request, a finished deck, a problem that never blew up because you quietly defused it three weeks ago. The better you are at your job, the more of your value is invisible by design: the fire that never started, the escalation that never happened.

We cling to the myth anyway, because the alternative feels gross. Making your work visible sounds like bragging, politics, self-promotion, the stuff we associate with people who talk more than they ship. So we keep our heads down and wait to be noticed.

And then we’re surprised when we’re not.

Visibility isn’t politics. It’s information transfer.

Here’s the reframe: your manager, and your org, are running on a lossy, incomplete model of what you do. They see whatever output happens to land in front of them and infer the rest. That inference is almost always wrong, and almost always in your disfavor, because the hardest, most preventative work is the least observable.

Visibility isn’t spin. It’s closing the gap between what you actually did and what the people who make decisions about you believe you did.

Put it in colder terms: invisible work is work that can’t be rewarded, can’t be defended, and can’t be built on. When the promo case gets made, it isn’t there. When the reorg comes and someone’s redrawing the org chart from memory, it isn’t there. You’re not being humble. You’re carrying a risk alone that you don’t need to carry.

I’ve argued before that revenue isn’t a department: everyone shapes the outcome. Visibility is that same logic pointed back at you: contribution nobody can see doesn’t fully count as contribution. Being legible is part of the job, not a tax on it.

It’s worse now than it used to be

This used to be easier. When everyone sat in the same room, your manager absorbed a low-grade stream of evidence just by proximity: who stayed late, who unblocked whom, who people walked over to when they were stuck.

That stream is gone. Remote and async work means less line-of-sight than at any point in the history of offices. Nobody is watching you work. And at the same time, AI is quietly commoditizing the doing. When everyone can generate a decent draft, a passable analysis, an okay first pass, the differentiator stops being raw output and becomes judgment, ownership, and whether anyone can actually tell what you contributed.

In a world where the work is cheaper to produce, being legible about it is worth more, not less.

How to be visible without becoming that person

This is the part people get wrong, so let’s be specific. Visibility done well isn’t volume. It’s a handful of habits:

• Report outcomes, not activity. Not “worked on the onboarding flow.” Instead: “reworked onboarding; first-week activation went from 48% to 61%, ~40 more paying teams a month.” Every outcome should carry data, and wherever you can, tie it to the three things leadership actually counts: revenue, profit, or cost saved. “Faster” and “smoother” are invisible; “added $200k in pipeline” and “cut cloud spend 18%” get remembered. Managers can only re-tell impact they can restate, so hand them the number.

• Put it in writing. A short weekly note (here’s what moved, here’s what’s next) beats any amount of hallway heroics. Written work travels to rooms you’ll never be in; a great in-person save evaporates the second the meeting ends.

• Attach your work to what leadership already cares about. Frame it in the language of the current priority: revenue, risk, the reorg, whatever’s on the CEO’s mind this quarter. The same work reads as ten times more important when it’s tied to the thing they’re already losing sleep over.

• Keep an impact log. Not for your ego, for the moments that matter later: the review, the promo packet, the layoff conversation you hope never comes. You can’t show what you never bothered to track. (Never done it? Spend twenty minutes reconstructing last quarter. It’s uncomfortable how much you’ve already forgotten.)

• Own the follow-up in the room. Take the notes. Send the recap. Name the next steps and who owns them. It’s visibility that also creates value, the rare kind nobody resents.

• Give other people credit, loudly. This is the cheat code. Nothing makes your own visibility read as generous instead of grabby faster than being the person who names everyone else’s contribution first. It compounds; people give it back.

• Be visible before you need it. Reviews and cuts are lagging indicators. You can’t backfill a reputation in Q4 for a year you spent silent. Visibility is insurance, and like all insurance, it’s useless the day you finally wish you had it.

The line you actually shouldn’t cross

Your discomfort isn’t entirely wrong. There is a version of this that’s gross, and it’s worth naming so you can steer around it.

Performative work (busy, loud, visible, and empty) is not the goal. Neither is claiming other people’s work as your own, or mistaking volume for signal by narrating every keystroke in the team channel. The instinct that recoils from that is correct.

Here’s the test that separates the two: are you transferring information the decision-makers genuinely need, or manufacturing noise to look busy? Legible real work is the first. Self-promotion is the second. The trap is that most good people, terrified of looking like the second, default to invisible. And invisible has a cost they never see coming.

The bottom line

Doing the work and showing the work aren’t two separate jobs, one noble and one dirty. The second is how the first one counts.

Great work that nobody can see isn’t humility. It’s a risk you’re carrying alone. And you don’t have to.

• Learning to draw boxes. With a ruler.

• Turning a physical therapy handout into a calendar system.

• Debugging a race condition in a side project app.

• Fact-checking a health claim before repeating it.

• Building a World Cup prediction model in Excel.

Not one of these looks like “career development.”

All of them are.

Careers Are Built in Ordinary Weeks

I’ve written playbooks for the milestone moments — interviews, negotiations, entering and exiting companies.

But milestones are maybe ten days a year.

The other 350 are ordinary weeks. And ordinary weeks have a signature: the same behaviors show up whether you’re sketching a cube, rehabbing an elbow, or presenting to a board.

So I laid two weeks of my own work side by side and looked for the pattern.

Eight behaviors kept repeating. If you’re early in your career, these are the ones that compound.

1. Interrogate the spec before you execute it

I built a prediction model for World Cup group-stage goals. The original spec had a silent math bug — every prediction was being doubled before a single formula hit the spreadsheet.

Catching it before building took exact-match accuracy from 11% to 50%.

The early-career instinct is to execute instructions fast and faithfully. That feels like the safe move.

It isn’t.

Flawless execution of a broken plan is still a broken outcome. The person who pressure-tests the plan first is worth more than the person who builds it fastest.

2. Learn the rules mechanically before you trust your intuition

I’m learning to draw. Step one wasn’t freehand sketching — it was constructing perspective boxes with a ruler, so I’d know what correct actually looks like before attempting it by feel.

Most people skip straight to freehand. Then they can’t diagnose why their work is off, because they never learned the ground truth.

At work, this is the checklist before the shortcut. The template before the improvisation. Shadowing the senior rep before winging the call.

Scaffold first. Intuition is earned.

3. Ask for the simpler explanation. Out loud.

Mid-lesson on perspective drawing, I stopped and asked for the explanation in middle-school language.

Learning speed went up immediately.

Early in a career, the temptation is to nod along and Google it later. That’s the expensive move — you burn the moment where a real explanation was available.

Optimizing for understanding beats optimizing for looking smart. Every time. Nobody remembers that you asked a basic question. Everybody remembers when you got it wrong because you didn’t.

4. Tight feedback loops beat big reveals

Every ugly drawing attempt got shared and corrected before the next one. The prediction model was measured against a baseline, so “better” was a number — not a feeling.

Show messy work early. Define what improvement means. Measure against something.

Polishing in private is how people waste months.

This is the operating layer under Be Coachable: Listen → Reflect → Act → Iterate only works if the loop is short.

5. Build systems, not resolutions

My physical therapist handed me an 8-week rehab protocol on paper. Paper protocols die in a drawer.

So it became recurring calendar blocks with reminders — stretches layered over meetings where they could coexist, protected time where equipment was required. Designed around my actual schedule, not a fantasy version of it.

Willpower is a terrible project manager.

Consistency comes from making the desired behavior the default behavior. The same logic behind treating your career like a project: nobody else is building the system for you.

6. When the spec has blanks, ask the owner. Don’t guess.

Two fields on that rehab protocol were blank — the parts only the therapist could answer. They got flagged and sent back, not filled in with plausible assumptions.

Guessing feels efficient. It reads as competent.

Right up until it’s wrong.

Early-career people often think surfacing open questions makes them look unsure. It’s the opposite — flagging ambiguity is a senior move. Seniors do it constantly. That’s part of how they got senior.

7. Package your problems so people can actually help

I hit a nasty intermittent bug in a side project — clips playing the right footage with the wrong commentary attached. Classic race condition territory.

My first ask for help stalled completely. Why? I shared file paths instead of the files themselves. The person helping me couldn’t open a thing.

But here’s what I did right: I came with a hypothesis, not just “it’s broken.”

The quality of help you get is proportional to the quality of context you give. A reproducible problem plus a working theory gets you senior-level help. “It doesn’t work” gets you a shrug.

This applies identically to senior engineers, managers, and AI tools.

8. Verify before you repeat

I got a confident, well-reasoned answer to a health question. Before repeating it anywhere, I asked for it to be fact-checked against sources.

One claim got refined. The conclusion held, but a detail was subtly overstated.

Early in your career, you’re often the conduit of information moving upward — the summary, the number in the deck, the “I heard that…” in the meeting.

Your credibility is the asset. Even mostly-right answers carry nuance worth catching before you pass them along. Especially now, when confident-sounding answers are cheaper to generate than ever.

The Pattern Under the Pattern

Look at the list again.

In two weeks I was a beginner artist, a patient, a sports analyst, and a debugger.

That’s not a coincidence. That’s the job.

Careers compound for people who stay comfortable being a novice at something while being expert at other things. The moment you only do what you’re already good at, the compounding stops.

The Challenge: Run Your Own Two-Week Audit

Don’t take my list. Build yours.

1. Open your calendar, your sent folder, and your chat history for the last two weeks.

2. Write down what you actually did — not your job description. The real list.

3. Check it against the eight behaviors above. Circle anything that showed up three or more times.

That circled list is your current operating system. For better or worse.

Then pick one behavior to run deliberately next week. Not eight. One.

Ordinary weeks are where careers are actually built.

Might as well build yours on purpose.

Most meetings are graveyards for momentum. The best operators treat every meeting like an operation: defined objective, tight execution, and a clear output. Here is how to be the person everyone wants in the room—and how to run the room when it’s yours.

A question I keep getting from readers and teammates alike:

“I’m stuck in back-to-back meetings all day and nothing gets done. Half of them don’t even have an agenda. How do I make this stop?”

Here’s the uncomfortable truth: meetings aren’t the problem. Bad operating systems around meetings are the problem.

I’ve sat through thousands of meetings across telecom, airlines, RV marketplaces, and startups. The pattern is always the same. Companies don’t have a “too many meetings” problem—they have a “nobody owns the outcome” problem.

The best operators I’ve worked with don’t just attend meetings. They treat every meeting like a micro-operation: clear objective in, clear deliverable out, everyone accountable. And when they run the meeting? It’s surgical.

Here is the exact system I’ve built over 15+ years of operating in fast-moving, high-chaos environments.

The War Room: Where I Learned That Silence Is a Decision

Early in my career at TELUS, I was pulled into a cross-functional “war room” to manage a major system migration.

The first few meetings were a disaster. Fifteen people in a room. No agenda. The most senior person would talk for 40 minutes. Everyone else would nod, check their phones, and leave without a single decision being made.

Then the project lead quit. And suddenly I was running the room.

Here’s what I did wrong at first: I tried to run the meeting democratically. I’d go around the table, ask everyone for “thoughts,” and let the conversation drift wherever it wanted. Sixty minutes would pass and we’d have generated a ton of discussion and exactly zero commitments.

What I learned—painfully—is that silence in a meeting is a decision. If someone sits through a 30-minute discussion about a deadline and says nothing, then walks out and misses that deadline, they’ve made a choice. They chose to not flag the risk when the room was assembled to hear it.

The shift happened when I stopped treating meetings as discussions and started treating them as decision factories. Every meeting had one job: produce decisions that people could execute against the moment they stood up from the table.

The Operational Principle: A meeting without a stated decision to be made is just a conference call with better lighting. If you can’t name the decision the meeting will produce, cancel it.

The 3-Box Meeting Framework: How to Run a Meeting in 25 Minutes

After years of iteration, I’ve landed on a framework I use for every operational meeting I run. I call it the 3-Box Framework, and it forces structure on even the most chaotic cross-functional rooms.

Here’s what the whiteboard (or shared doc) looks like at the start of every meeting:

1. Pre-Read or Don’t Meet (Before the meeting):
   Every meeting has a one-page pre-read sent 24 hours in advance. It contains: the decision to be made, the 2-3 options on the table, and the relevant data. If you show up without reading it, you observe—you don’t get to slow the room down asking questions that were already answered.
   The Rule: No pre-read, no meeting. Period. If the organizer can’t articulate the decision in writing, they aren’t ready to convene a room.

2. Box 1 — Context (5 minutes max):
   The meeting owner gets exactly 5 minutes to fill in gaps the pre-read didn’t cover. New data that landed overnight. A stakeholder concern that surfaced. This is not a re-read of the document. If the presenter starts reading their own pre-read aloud, cut them off.

3. Box 2 — Tension (10 minutes):
   This is where the meeting earns its existence. Name the disagreement. Put the 2-3 options on the board. Ask the room directly: “Who disagrees with Option A, and why?” Force the tension into the open.
   The Rule: Silence is agreement. If you say nothing during Box 2, you’ve committed to the outcome. No hallway vetoes after the meeting.

4. Box 3 — Commit (10 minutes):
   The decision maker (identified before the meeting starts) makes the call. Write it on the board in real time. Assign an owner. Set a deadline. Identify who needs to be informed.
   The Rule: If the decision can’t be made in the room, the meeting failed. The only acceptable output of Box 3 is either a decision or a specific escalation with a named person and a deadline.

5. The 25-Minute Hard Stop:
   Meetings are 25 minutes, not 30 or 60. The extra 5 minutes are a buffer for humans to get coffee, use the bathroom, and context-switch before the next commitment. Respecting people’s time is an operational discipline, not a courtesy.

The Participant’s Playbook: How to Be the Person Everyone Wants in the Room

Running a great meeting is only half the equation. Most people are terrible meeting participants, and they don’t even know it.

At WestJet, I managed a team where I noticed a clear pattern: the operators who got promoted weren’t the ones who talked the most in meetings. They were the ones who delivered the most signal per minute.

Here’s what I mean. There are five archetypes in every meeting. Four of them are dead weight:

• The Narrator: Restates what everyone already knows. Adds zero new information. Uses meetings as a stage to demonstrate they’re “in the loop.”

• The Tangent Machine: Hijacks the conversation to talk about a loosely related problem they care about. Derails Box 2 every time.

• The Silent Passenger: Says nothing, agrees to everything, then sends a contradictory email 45 minutes later.

• The Politician: Speaks in vague generalities designed to avoid commitment. “We should probably think about maybe exploring that at some point.”

Then there’s the fifth archetype—The Operator:

• Reads the pre-read.

• Arrives with a position. Not a question. A position.

• Speaks only when they have new information, a risk to flag, or a disagreement to surface.

• Names their commitment out loud before leaving the room.

The Operator’s Pre-Meeting Checklist:

Before you walk into any meeting, spend 3 minutes answering these questions in your notebook:

1. What decision is being made? (If you don’t know, ask the organizer before the meeting or decline.)

2. What is my position? (Not “I need to hear more.” You always know enough to have a preliminary stance.)

3. What’s the one thing the room might miss? (A risk, a dependency, a stakeholder who’ll blow up if they’re not consulted.)

4. What am I willing to commit to? (If you can’t commit to anything, you shouldn’t be in the room.)

If you show up having done this work, you’ll be the most valuable person at the table every single time. Not because you talked the most—because you drove toward the outcome.

The 1:1 Exception: The One Meeting That Should Never Have an Agenda

There’s exactly one type of meeting where I throw the 3-Box Framework out the window: the 1:1 with a direct report.

Early in my management career, I ran 1:1s like every other meeting. Tight agenda. Status updates. “What are you working on?” “Any blockers?” Done in 15 minutes. Efficient. And completely useless.

Here’s what I missed: a 1:1 isn’t a status meeting. It’s a relationship maintenance contract.

You already know what your team is working on—you have dashboards, standups, and Slack for that. The 1:1 exists for the things that don’t surface in public channels. The frustration they’re not voicing. The career anxiety they’re sitting on. The early signal that a project is about to go sideways but nobody wants to be the one to say it.

My current 1:1 approach:

1. Their agenda, not yours. They own the first 20 minutes. If they have nothing, sit in silence until they do. The silence creates space for the real conversation.

2. One question you ask every time: “What’s the thing you’re not telling me?” It sounds aggressive on paper. In practice, after two or three 1:1s, people start using that question as permission to surface the hard stuff.

3. Never use a 1:1 to deliver bad news. That’s a separate, scheduled conversation with a clear purpose. Mixing feedback with the trust-building channel poisons both.

4. End with their energy level, not a task list. “On a scale of 1–10, how are you feeling about work this week?” You’re not their therapist. But you are the person responsible for knowing when someone’s about to burn out before the flames are visible.

Operational Takeaways

For Individual Contributors (ICs)

1. Be The Operator, not The Narrator: Before every meeting, write down your position, the one risk the room might miss, and what you’re willing to commit to. If you can’t answer those, decline the meeting.

2. Enforce the “Silence Is Agreement” Rule on yourself: If you disagree with something in a meeting and don’t say it, you’ve lost your right to complain about it later. Speak in the room or commit to the outcome.

3. Decline meetings without a stated decision: If the invite doesn’t name the decision to be made, reply asking for it. If they can’t provide one, you’ve just saved yourself 30 minutes.

For Managers & Team Leaders

1. Adopt the 3-Box Framework: Pre-read, Context → Tension → Commit, 25-minute hard stop. Run it for two weeks and watch your meeting count drop by 40%.

2. Audit your 1:1s: If your 1:1s are status updates, you’re wasting the most important meeting on your calendar. Let your direct report own the agenda and ask the uncomfortable questions.

3. Kill the “Update Meeting”: If the entire purpose is sharing information, send a Loom or a written update. Reserve synchronous time for decisions and tension resolution only.

Community Question

What’s the worst recurring meeting you’ve ever been trapped in and what would you change about it if you had the power?

Have you ever successfully killed a useless meeting? How did you do it?

Share your war stories in the comments below.

“My company is in flux. Great product. New products coming in. One colleague retiring. Trying to figure out how to thrive in this environment.”

This is the messy reality of the corporate world. It’s a shifting puzzle of changing priorities, institutional knowledge walking out the door, and new initiatives being piled on top of daily work.

When flux hits, most people make a fundamental mistake: they spin in the rumor mill.

They spend all their mental load worrying about things they can’t control, hoping they can just freeze the status quo. But keeping your head down is a terrible strategy. In a shifting company, that’s exactly how you get run over.

If you know how to read the system, flux is the single greatest opportunity you will ever have to accelerate your career. Here is the playbook I’ve used across three industries.

The Outdoorsy Autopsy: A Lesson in Asset Utilization Under Fire

When COVID hit in early 2020, travel overnight just disappeared.

At Outdoorsy, an RV rental marketplace, we scaled the team all the way down to a skeleton crew of 5 people. Zero revenue. No visibility on when—or if—it was coming back.

Here’s what I didn’t do: I didn’t spin. I didn’t sit in Slack channels trading rumors about whether we’d survive. I made a bet. I spent those quiet months doing two things:

1. Mapping available capacity in the market. Other companies were cutting their customer service operations. That meant contact centers had trained, idle agents sitting on benches. I started building relationships with those providers.

2. Pre-building the operational playbook. I wrote the training plans, the escalation paths, and the QA frameworks before demand returned—so we could plug people in immediately when the switch flipped.

When RV travel exploded as the safest way to travel in “pods,” we went from 20 to over 160 customer operations staff in an eight-week window. We didn’t recruit, interview, and train 140 people. We activated underutilized assets that already existed in the market.

The Operational Principle: In flux, most people waste mental load on what they can’t control. The operators who win are the ones who audit the environment for underutilized assets—idle talent, unused systems, dormant relationships—and position themselves to activate them the moment conditions shift.

The Black Book Method: Taming Chaos with a Daily “North Star”

Early in my career, I was working at TELUS, a major telecom in Canada.

I was in sales, and a massive technology migration was announced for our department. Most people shied away from it. It represented flux, it was going to break things, and the team wanted to stay far away.

I did the opposite: I volunteered to be the “prime” (the lead point person) representing our department. Suddenly, I was sitting in rooms with engineers, operators, and executives, solving problems far outside my day-to-day quota.

Every morning back then, I sat down at my desk with my black book—we all had them at TELUS—and wrote down my main focus. Today, I’d call it the “North Star.” I would outline what had to get done and start working from the top down.

But early on, I made a massive operational mistake: I would tackle my own complex, multi-hour projects first.

I’d spend six hours straight in deep focus. Meanwhile, my team often sat completely blocked, waiting for a simple sign-off, a quick decision, or a reply from me. I was optimizing for my own deep work, but bottlenecking the velocity of the entire system.

If I were back at TELUS today, I would run a different playbook. Here is the exact daily process I use now to identify my North Star, triage my day, and keep the team unblocked:

The Black Book Method: A Step-by-Step Daily Process

The sequence is non-negotiable:

1. The 10-Minute Morning Triage (First thing I do with an espresso): Before you open Slack, email, or take a meeting, sit down with a physical notebook. Write down the one single outcome that represents success for today—your North Star. The Rule: It must be an outcome, not a task. “Migration plan signed off by engineering” — not “Work on migration plan.”

2. Sort by “Unblockers” vs. “Deep Work”: Underneath your North Star, split your page into two columns. Unblockers: Micro-decisions, sign-offs, email replies, or quick advice that is currently holding someone else up. Deep Work: Multi-hour tasks that require your deep cognitive focus.

3. Run the “Unblocker Sprint” First: Spend your first 30 minutes knocking out every single item in the “Unblocker” column. Send the sign-offs, answer the quick questions, and clear the runway. The Rule: Do not get sucked into conversations. Send the response, close the tab, move to the next item.

4. Protect the Deep Work Block: Once the team is running, close Slack, put your phone in another room, and spend the next block focused solely on your North Star outcome.

5. The Mid-Day Re-Triage: After lunch (yes, take a real lunch and stop working), open your book. Is the North Star complete? If yes, choose the next highest-leverage deep work item. If no, protect another focus block in the afternoon.

By running the unblockers first, you keep the team’s velocity high while protecting your own capacity to execute on what actually matters.

The Shadow Audit: How to Actually Extract a Veteran’s Knowledge

What about when a key veteran leaves or retires?

This happened to me when I joined WestJet. It was a new industry for me (airline), and I was coming in to replace a brilliant leader. Her daughter, who was also brilliant, worked with me previously at another company, so the predecessor’s shadow was massive.

We had a two-week crossover. And honestly? I didn’t use that time effectively because I didn’t know what I didn’t know yet.

Most companies default to one of two approaches, and both fail:

• “Write us some documentation before you go.” → The departing veteran stares at a blank screen. They can’t write what they don’t know is in their head. You get a useless wiki page.

• “Shadow them and take notes.” → You follow them around for a week and nod politely. But you don’t have enough context to know which of the 200 things they do are the ones that actually matter.

Here is the process I’d run now. I call it The Shadow Audit:

Step 1: You Do the Work. They Watch.

Sit at your desk, open the systems, and start doing the job. Let the predecessor watch you fumble through it. Their job is to interrupt you every time you’re about to make a mistake, miss a relationship, or take the slow path.

Step 2: Capture the Edge Cases in Real-Time

As they critique, write down every correction in a specific format:

• “When [situation], always [action] because [reason].”

• Example: “When a delayed flight cascades past 11 PM, always call the hotel coordinator directly—not the help desk—because the help desk queue is 45 minutes and you’ll miss the crew rest window.”

Step 3: Co-Create the “Failure Modes” Checklist

At the end of each session, sit together and distill the edge cases into a one-page checklist of the Top 10 things that will blow up if you don’t know about them. This is the artifact. Not a wiki. Not a procedures manual. A specific list of failure modes and their fixes.

Step 4: Keep the Line Warm

When they leave and say “Reach out if you ever need anything,” actually do it. Retired professionals love sharing their wisdom—I’ve seen this with my parents, my stepdad, and my mentors. Buy them lunch, stay in touch, or pitch a light micro-consulting agreement (5 hours/month) for the first 90 days. The relationship is the long-term safety net; the checklist is the short-term one.

⚡ Operational Takeaways

For Individual Contributors (ICs)

1. Run a Shadow Audit: If you’re taking over a role, don’t ask the departing person to write docs. Do the work in front of them and capture the edge cases as a “Failure Modes” checklist.

2. Volunteer as the “Prime”: When a new, messy tool or process is launched, volunteer to lead it for your team. That’s where the career leverage is.

For Managers & Team Leaders

1. Use the Black Book Method daily: Write the North Star outcome, split unblockers from deep work, and run the Unblocker Sprint before you touch anything else.

2. Budget for knowledge extraction: If a key veteran is retiring, pitch a 90-day micro-consulting agreement to your leadership. 5 hours a month is cheap insurance against institutional knowledge walking out the door.

💬 Community Question

Have you ever inherited a role from a veteran, or had a key teammate retire? How did you manage that crossover period? Did you get a clean handoff—or did you learn everything the hard way?

Share your stories in the comments below

🎧 Prefer to Listen?

Catch the AI-generated podcast version of this issue. Two hosts break down every framework, debate the edge cases, and make it feel like you’re overhearing a conversation you weren’t supposed to hear.

▶️ Listen to the AI Podcast

Most people think about revenue as a sales problem.

Early in my career, I did too. “Just close more deals.” “Just run more ads.” “Just hire more reps.” That was the playbook. And for a while, it seemed to work. Until it didn’t.

The longer I’ve been building and scaling businesses, the more I’ve realized something that changed how I operate: revenue is not a department. It’s a system.

If you’re early in your career, or starting your first business, understanding this will save you years of wasted effort. So I want to break down how I actually think about revenue growth, not as a collection of isolated tactics, but as five levers that only work when they’re connected.

The 5 Levers of Revenue

Most founders and new leaders treat these as separate silos:

• Marketing

• Sales

• Product

• Customer Service

• GTM Strategy

But they’re not separate. They’re one machine. When that machine is aligned, you grow. When it’s not, you burn cash and wonder why nothing is working.

Let me walk through each one.

Marketing

**Your job is to build trust before the conversation starts.**

Marketing is not “running ads.” It’s positioning. It’s the reason someone believes your product might be for them before they ever talk to you.

The challenge I see over and over again is that early-stage companies skip positioning entirely and go straight to tactics. They run Meta ads before they can clearly articulate who they serve and why they’re different. They spend money on awareness before they’ve earned the right to anyone’s attention.

Here’s what I tell first-time founders: if you can’t explain in one sentence why someone should choose you over every alternative (including doing nothing), you’re not ready to spend money on marketing. Get that sentence right first. Everything else flows from it.

Sales

**Your job is to help people make a decision they already want to make.**

Great salespeople don’t convince. They clarify.

If your marketing did its job, the prospect already believes you might be able to help them. Sales is the process of confirming that belief and removing friction. It’s not about pressure. It’s about clarity.

The challenge here is that new business owners tend to fall into one of two traps. Either they avoid sales entirely because it feels “pushy,” or they over-rely on it because they think hustle alone will win. Neither works long-term.

What actually works is building a repeatable process. Understand the three to five objections your buyers always have. Have clear, honest answers for each one. Then make it easy to say yes. Sales shouldn’t feel like convincing. If it does, something upstream (your positioning, your product, your targeting) is broken.

Product

**Your most powerful growth engine, if you let it be.**

Here’s what most people miss: Product IS marketing. Product IS sales.

A product that genuinely solves a problem creates word of mouth. And word of mouth is the highest-converting, lowest-cost growth channel that exists. No ad campaign, no sales team, no influencer partnership will ever outperform a product that people can’t stop talking about.

The challenge is that founders fall in love with features instead of outcomes. Your customer doesn’t care about what your product *does*. They care about who they *become* when they use it. That distinction matters more than most people realize.

Here’s a simple gut check: does your product make your customer’s life measurably better? If yes, double down on that. If you’re not sure, go talk to ten customers this week. Not to sell them anything. Just to listen.

Customer Service

**The most underrated revenue driver in business.**

I’ll say it plainly: how you treat people after they pay you determines whether your business compounds or flatlines.

Retention is revenue. Referrals are revenue. A customer who feels taken care of will buy again, buy more, and tell others. This is not a “nice to have.” This is the math of sustainable growth.

The challenge is that customer service is the first thing that gets deprioritized when you’re “growing fast.” Teams get stretched. Response times slip. The human touch disappears. And that’s exactly when it matters most, because the customers you’re acquiring during a growth phase are forming their first impression of who you are as a company.

The companies that win long-term don’t just acquire customers. They keep them.

GTM Strategy

**The orchestration layer that makes everything else work.**

Go-to-market is not a launch plan. It’s the ongoing strategic answer to four questions:

1. Who are we selling to?

2. Where do they spend their attention?

3. What message will earn their trust?

4. What’s the most efficient path from awareness to purchase?

Your GTM strategy is the connective tissue between marketing, sales, product, and service. Without it, you have four departments doing four different things. With it, you have a unified engine where every function reinforces the others.

The challenge is that GTM requires honesty. You have to admit what’s not working. You have to kill channels that feel productive but aren’t. You have to say no to customers who aren’t your ICP, even when their money is right there. That discipline is what separates companies that scale from companies that stall.

_____

The Biggest Challenge No One Talks About

Alignment.

You can have a great product, strong marketing, and talented salespeople and still struggle to grow. Because if those functions aren’t telling the same story, solving for the same customer, and measuring success the same way, you just have a collection of smart people pulling in different directions.

I’ve seen this happen at startups and I’ve seen it happen at companies doing nine figures. The symptom is always the same: everyone is busy, everyone is working hard, and revenue isn’t moving the way it should.

Revenue doesn’t come from any one of these five levers. It comes from all five working together.

_____

How This Changes By Role

Everything I just described is the system. But how you operate within it depends on where you sit.

**If you’re an AE (or any individual contributor carrying a number):**

Your instinct will be to stay in your lane. Hit quota. Close deals. That’s the job description, and it matters. But the AEs who consistently outperform don’t just sell. They think like owners.

That means understanding why marketing is sending you the leads they’re sending you. It means giving product real feedback from the field, not just “the customer wants a discount,” but “here’s the objection I keep hearing that our product doesn’t answer yet.” It means knowing what customer service is dealing with after you close, because that post-sale experience determines whether your customer becomes a referral source or a churn risk.

The AEs who think in systems build careers. The ones who only think in quota build a ceiling.

**If you’re a manager or leading a team:**

Your job is not to run one of these five levers. Your job is to connect them.

That means sitting in on customer service calls even when it’s not “your department.” It means building a feedback loop between sales and product that actually works, not a Slack channel that nobody reads, but a structured process where field insights change roadmap priorities. It means measuring your marketing team on pipeline quality, not just lead volume, and measuring your sales team on retention outcomes, not just closed-won.

The best managers I’ve worked with don’t optimize their function. They optimize the system. They ask: “Where is the handoff breaking?” Because that’s almost always where the revenue is leaking.

_____

Things to Do That Others Won’t

If you take nothing else from this post, take these three. They’re simple, but almost nobody does them consistently. That’s exactly why they work.

**1. Talk to your customers without an agenda.**

Not a sales call. Not an upsell. Not a survey with a gift card. Just a genuine conversation: “How’s it going? What’s frustrating you right now? What would make your life easier?”

Most companies only talk to customers when something is wrong or when they want something. The companies that grow fastest are the ones that listen when there’s no transaction on the table. You’ll learn more in five of those conversations than in a month of dashboard reviews.

**2. Kill something that’s working “okay.”**

This is the one nobody wants to do. You have a channel, a campaign, a product line, or a process that’s producing mediocre results. It’s not failing, so it survives. It stays on the roadmap. It gets budget. It takes up headcount and attention.

But “okay” is expensive. Every resource you spend maintaining something mediocre is a resource you’re not spending on something that could be great. The best operators I know are ruthless about cutting the middle. They either fix it fast or kill it and reallocate. That willingness to let go of “okay” is what creates room for exceptional.

**3. Write down what you believe about your customer and revisit it every quarter.**

Not your persona doc from two years ago. Not the ICP slide in your pitch deck. I mean a living document that answers: Who is this person? What do they actually care about? What are they afraid of? Where do they go for advice? What would make them tell a friend about us?

Most teams set their customer definition once and never touch it again. But your customer evolves. The market shifts. Your product changes who you attract. If you’re not updating your understanding of your customer on a regular cadence, you’re building on assumptions that might have expired six months ago. The companies that stay close to this question stay ahead.

_____

If You’re Just Starting Out

Here’s the simplest version of everything I just said:

Don’t think in departments. Think in systems.

Ask yourself one question: “Is every part of my business reinforcing the same message to the same customer?”

If the answer is yes, you’ll grow. If the answer is no, now you know where to start.

_____

If this was useful, I’d appreciate you sharing it with someone who’s early in their career or building their first company. These are the kinds of lessons I wish someone had laid out for me plainly when I was starting out.

We cover how trust is built through specificity, why strong professionals speak in outcomes instead of effort, and how small shifts — like removing weak language or using “I” statements — can completely change how you’re received.

At its core, this is about upgrading how you communicate so people see you as clear, confident, and someone they can rely on.

It’s not.

What is unique is who pays attention early, who ignores it, and who actually does something about it.

Right now, it’s AI.

Before that, it was cloud, mobile, the internet, personal computing.

Go back further, and the pattern becomes even clearer.

The Pattern Has Repeated for 150+ Years

1870s–1900s: Railroads & Electricity

The obvious winners were the industrial giants.

But the real opportunity wasn’t just “owning the railroads.”

It was:

• The merchant who expanded distribution because shipping got faster

• The manufacturer who scaled because inputs moved more efficiently

• The towns that grew because they were connected

Same with electricity.

It wasn’t just the companies generating power.

It was:

• Factories that extended working hours

• Businesses that improved productivity

• Operators who redesigned how work got done

The people who understood what it enabled moved ahead.

1920s–1950s: Automobiles & Mass Production

Cars didn’t just create car companies.

They created:

• Suburbs

• Logistics networks

• New retail formats

• Entire job categories

Henry Ford didn’t just build cars. He changed how things were produced.

But thousands of others won by asking:
“What becomes possible because this exists?”

1980s–2000s: Personal Computers & the Internet

You didn’t need to be Microsoft.

You just needed to:

• Learn Excel before your peers

• Use email before others did

• Build a website when most companies didn’t have one

That alone created massive differentiation.

At one point, “good at PowerPoint and Excel” was a competitive edge.

That sounds ridiculous now.

But it wasn’t then.

2010s: Mobile, Cloud, SaaS

Again, same pattern.

The winners weren’t just the founders.

It was:

• Operators who learned CRMs deeply

• Teams who used data instead of gut

• People who automated workflows early

The bar moved.

Some people moved with it.

Some didn’t.

Now: AI

This is another one of those moments.

And it feels like a big one.

Not because it replaces everything overnight.

But because it changes how quickly things can be done, tested, built, and iterated.

Which brings me to the last few days.

What I Actually Did

I didn’t “read about AI.”

I blocked time and built.

In four days, I:

• Rebuilt my entire website

• Created a live resume page

• Built a chatbot trained on my background, tone, and positioning

• Tested workflows that could materially change how work gets done

Here’s what that looks like in practice:

1. A Resume That’s Not Just a PDF

Yes, I still have a resume.

But I also built a live version:
👉 Take a look

Now when someone asks for my background, I send both.

The difference is immediate.

A PDF tells you what I’ve done.
A live page shows you how I think, how I build, and how I operate.

That’s differentiation.

Right now, very few people are doing that.

That won’t last.

2. A Website That Reflects How I Actually Work

I rebuilt my site quickly:
👉 Taccani.com

Not just visually.

Structurally.

Clearer positioning.
Sharper messaging.
More aligned to how I actually deliver value.

This used to take weeks or months. Recently days with Wix and Godaddy.

Now it can take hours if you know how to use the tools.

3. A Chatbot That Represents Me (Properly)

This is where it gets interesting.

I built a chatbot trained on:

• My experience

• My tone

• My perspective

• The types of problems I solve

But more importantly, I constrained it.

I created a framework so it:

• Talks about what I want it to talk about

• Avoids areas I don’t want it speculating on

• Represents me consistently

That’s the difference between:
“Cool demo”
and
“Something actually useful”

The Reality Most People Are Missing

You cannot fake this.

There’s already a pattern emerging.

I heard it directly from an investor who has raised billions:

“I am tired of AI slop being sent to me. I can tell when something is AI-generated, it doesn’t make sense.”

And he’s right.

You can:

• Fake it for a bit

• String together prompts

• Generate something that looks polished

But if it lacks:

• Context

• Judgment

• Real understanding

It falls apart quickly.

And the people who matter can tell.

This Is Where People Get It Wrong

They think AI replaces learning.

It doesn’t.

It amplifies it.

If you:

• Read

• Think

• Build

• Understand systems

You become exponentially more effective.

If you don’t:

You just produce faster, lower-quality output.

That’s the “LLM flop” people are already seeing.

What Actually Creates Advantage

It’s not access to tools.

Everyone has that.

It’s:

• How quickly you learn them

• How deeply you understand the problem

• How well you apply them to real situations

And critically:

How early you do it.

Because right now:

• Most people are still dabbling

• Very few are building real things

• Even fewer are integrating this into how they operate daily

That gap is where opportunity lives.

This Is the Same Pattern, Again

Railroads.
Electricity.
Cars.
Computers.
The internet.
Cloud.

Now AI.

The people who win aren’t always the ones who invent it.

They’re the ones who:

• Recognize it early

• Invest time to understand it

• Apply it to real problems

• Move before it’s obvious

The Part That Actually Matters

This won’t be the last shift.

There will be another one.

And another one after that.

So the real skill isn’t “learning AI.”

It’s building the muscle of:

• Seeing change early

• Leaning into it

• Learning fast

• Applying it to something real

Challenge

Don’t read about this.

Do it.

Block time.

2 days minimum.

Pick something real:

• A workflow you hate

• A process that’s slow

• A problem you haven’t solved

And build something.

Not perfectly.

Just something that works.

Because that’s how you move from:
Watching
to
Participating

And that’s where careers actually change.

BONUS! Below is a guide to getting started and a project if you are new to all this.

What Is Antigravity?

Antigravity is an AI pair programmer that doesn’t just answer questions — it builds with you.

It can:

• Write, edit, and debug code across any language

• Run terminal commands on your machine

• Open and interact with web browsers

• Deploy live applications to the internet

• Read and analyze files, images, and documents

• Generate images and assets

• Manage databases, APIs, and cloud services

• Create reusable “skills” (codified playbooks) that get smarter over time

Think of it less like ChatGPT and more like having a senior full-stack engineer sitting next to you — except it works at machine speed and never gets tired or says that is not on the roadmap.

How It Works (The Basics)

1. You Talk, It Builds

Just describe what you want in plain English. Be specific about the outcome, not the implementation. Let Antigravity figure out the “how.”

Good prompt:

“Build me a personal portfolio website with a dark theme, an about section, a projects section with 3 cards, and a contact form. Make it look premium.”

Weak prompt:

“Make a website.”

2. It Plans Before It Builds

For complex tasks, Antigravity creates an implementation plan and asks for your approval before writing code. Read it. Give feedback. This is your chance to steer.

3. It Uses Real Tools

Antigravity doesn’t just generate text — it creates files, runs servers, opens browsers, takes screenshots, and deploys. Everything it does is real and on your machine.

4. You Stay in Control

• It will ask for permission before running potentially destructive commands

• It creates artifacts (plans, walkthroughs) so you can track what’s happening

• You can redirect it at any time — “Actually, change the color to blue” or “Wait, let’s do X instead”

Key Concepts to Know

Workspace: The folder Antigravity works in. Your code lives here.

Artifacts: Documents Antigravity creates to communicate with you (plans, walkthroughs, reports)

Skills: Reusable playbooks that teach Antigravity how to do specific tasks consistently

Browser Subagent: Antigravity can open a browser, click buttons, fill forms, and take screenshots

Terminal Commands: Antigravity can run commands on your machine (with your approval)

Implementation Plan: A detailed plan it creates before complex work — your chance to review and approve

Walkthrough: A summary it creates after completing work — proof of what was done

Tips for Getting the Most Out of It

1. Be outcome-oriented. Say what you want, not how to build it. Let the AI choose the architecture.

2. Give feedback early. If something looks off in the plan, say so before it starts building.

3. Iterate fast. Don’t aim for perfection on the first pass. Ship something, then refine.

4. Ask it to explain. If you don’t understand something it did, ask “explain what you just did and why.”

5. Think in projects, not prompts. You can have long, multi-step conversations. Build on previous work.

6. Let it debug. If something breaks, don’t try to fix it yourself — tell Antigravity what went wrong and let it investigate.

7. Save your wins as skills. If you build something you’ll want to repeat, ask it to create a reusable skill.

🏆 Your First Challenge: “Zero to Live in 60 Minutes”

Goal: Build and deploy a live, public website with an AI chatbot — from nothing — in under 60 minutes.

This challenge is designed to give you hands-on experience with Antigravity’s most powerful capabilities: file creation, server development, browser testing, and cloud deployment.

The Challenge Brief

Build a personal “About Me” website with an embedded AI chatbot that can answer questions about you.

Requirements:

1. A website (minimum 1 page) that includes:

   • Your name and a short bio

   • What you do / what you’re working on

   • A section with 3 things you’re proud of or interested in

   • Premium design — dark mode, modern typography, subtle animations

2. An AI chatbot embedded on the page that:

   • Pops up as a floating widget in the bottom-right corner

   • Can answer questions about you based on info you provide

   • Has a custom personality/tone you define

3. Deployed live to a public URL anyone can visit

Step-by-Step Walkthrough

Phase 1: The Website (15 min)

Start with this prompt:

“Build me a personal website. My name is [YOUR NAME]. I’m a [YOUR ROLE] who [WHAT YOU DO]. I’m passionate about [2-3 THINGS]. Make it a single-page dark-mode website with premium design — use Inter font, subtle gradients, smooth scroll animations. Include sections for: hero/intro, what I do, 3 things I’m proud of, and a way to contact me. Make it stunning.”

What to watch for:

• Antigravity will create HTML, CSS, and JS files

• It may start a local dev server so you can preview it

• Review the design — ask for changes if anything looks off (”make the hero bigger”, “change the accent color to teal”, “add a subtle particle effect in the background”)

Phase 2: The AI Chatbot (15 min)

Once the website looks good, say:

“Now add an AI chatbot to this website. Use the AI Chatbot skill if available. The chatbot should be powered by Claude. It should know the following about me: [PASTE A PARAGRAPH ABOUT YOURSELF — your background, experience, interests, what you’re working on, how to contact you]. Give the bot a friendly, professional personality. It should engage visitors and suggest they book a meeting with me at [YOUR BOOKING LINK OR EMAIL].”

What to watch for:

• Antigravity will create a Node.js/Express backend server

• It will set up API key management (you’ll need a Claude API key from console.anthropic.com)

• It will embed a floating chat widget on your site

• Test the chatbot locally — ask it questions and see how it responds

Phase 3: Deploy to the Internet (15 min)

Now let’s put it live:

“Deploy this to Render so it’s live on the internet. Walk me through setting up the GitHub repo and connecting it to Render.”

What to watch for:

• Antigravity will help you create a GitHub repository

• It will walk you through connecting to render.com (free tier)

• It will guide you through setting environment variables (your API key)

• Within minutes, you’ll have a live URL

Phase 4: Polish & Share (15 min)

Final touches:

“Review the live site and suggest 3 improvements. Then implement them.”

Then try:

“Create a walkthrough document summarizing everything we built today.”

What You’ll Learn From This Challenge

Working with AI: Giving clear prompts, iterating on feedback, directing the build

HTML/CSS/JS basics: Seeing how a modern website is structured

Node.js servers: Understanding how the chatbot backend works

API key management: Setting up .env files and keeping secrets safe

Git & GitHub: Pushing code to a repository

Cloud deployment: Going from local to live on Render

AI integration: Embedding Claude as a feature in a product

Bonus Challenges

(Once You’ve Completed the First One)

🥈 Challenge 2: “Data Dashboard”

“Build a dashboard that reads data from [a CSV file / Google Sheet / API] and displays it with charts and filters. Deploy it live.”

Teaches: data visualization, API integration, dynamic content

🥇 Challenge 3: “Full Product MVP”

“Build an MVP for [your app idea]. It should have user authentication, a database, and at least 3 features. Deploy it.”

Teaches: full-stack development, database design, authentication, production architecture

💎 Challenge 4: “Automate Your Workflow”

“I spend [X hours/week] on [repetitive task]. Build me a tool that automates it.”

Teaches: workflow automation, API orchestration, custom tooling

Common Questions

Q: Do I need to know how to code? No. Antigravity writes the code. You direct the work. Over time, you’ll naturally start understanding what the code does — but it’s not a prerequisite.

Q: What happens if something breaks? Tell Antigravity. Paste the error message or describe what went wrong. It will debug and fix it. That’s literally what it’s built for.

Q: How is this different from ChatGPT / Copilot? ChatGPT gives you text. Copilot autocompletes lines. Antigravity builds entire projects — it creates files, runs servers, opens browsers, deploys to the cloud, and manages the full lifecycle. It’s not an assistant you chat with; it’s an engineer you work alongside.

Q: Can I use this for my actual business? Yes. Everything in the “What We Built in 4 Days” portfolio was real business output — live websites, production apps, marketing pages, analytics dashboards. This isn’t a toy.

Remember: The point isn’t to learn every technology. The point is to learn how to direct the build. You’re the architect. Antigravity is the construction crew. The faster you learn to describe what you want clearly, the faster it builds.

Start your timer. Open Antigravity. Go. 🚀

Download it here - https://antigravity.google/

Language shapes how people perceive your competence, your leadership, and your potential. In the workplace, the words you choose influence outcomes: promotions, negotiations, trust, and opportunity.

Most professionals underestimate this.

The difference between “doing good work” and “being seen as high-impact” is often language.

Why Language Matters

1. First Impressions Compound

Your language signals how you think.

Clear, structured communication signals clarity of thought.
Rambling or vague language signals uncertainty.

In interviews, meetings, emails, and presentations, people are subconsciously asking:

• Are you confident?

• Are you precise?

• Do you understand the problem?

Your language answers those questions before your résumé does.

2. Language Builds or Erodes Trust

Trust is built through consistency and clarity.

• Overpromising erodes credibility.

• Vague commitments create anxiety.

• Precise language builds confidence.

Instead of:
“I’ll try to get that done.”

Say:
“I’ll have a draft to you by 3pm Thursday.”

Specificity builds trust.

3. Language Controls Conflict

Most workplace conflict is not about intent.
It is about interpretation.

The wrong tone escalates.
The right phrasing de-escalates.

Replace:
“You didn’t communicate this clearly.”

With:
“I may have misunderstood. Can we walk through it again?”

One invites defensiveness.
The other invites alignment.

4. Leaders Speak in Outcomes

Strong leaders communicate in outcomes, not activity.

Weak:
“I’ve been really busy this week.”

Strong:
“This week we reduced onboarding time by 18%.”

Language determines whether you sound overwhelmed or effective.

5. Negotiation Is Framing

In negotiation, framing is everything.

Instead of:
“I need a raise.”

Say:
“Based on the results delivered and market benchmarks, I’d like to align compensation with impact.”

Same goal. Different power.

6. Inclusion Is Intentional

Language either widens the table or narrows it.

Inclusive language signals awareness and professionalism.
Assumptive language signals carelessness.

• Use names and preferred pronouns.

• Avoid stereotypes.

• Choose clarity over slang or insider shorthand.

In modern workplaces, this is not optional.

Practical Communication Upgrades

1. Eliminate Weak Language

Remove:

• “Just”

• “Maybe”

• “Kind of”

• “I think”

Instead of:
“I just wanted to check in.”

Say:
“Following up on the timeline.”

Confidence is heard.

2. Replace Complaints with Ownership

Instead of:
“That’s not my responsibility.”

Say:
“Here’s what I can own, and here’s where I’ll need support.”

Ownership language accelerates careers.

3. Use “I” Statements in Conflict

“I felt blindsided by the timeline change.”

Not:
“You blindsided me.”

It keeps the conversation productive.

4. Adapt to the Audience

Executives want brevity and impact.
Peers want collaboration.
Clients want clarity and reassurance.

Same message. Different delivery.

Professionals who cannot adjust tone plateau.

5. Master Written Communication

Email should be:

• Clear subject line

• One purpose

• Direct ask

• Defined timeline

Long emails are often unclear emails.

Your written communication becomes your reputation when you are not in the room.

6. Verbal Communication Signals Authority

• Speak slightly slower than you think you should.

• Pause instead of filling silence.

• Finish sentences decisively.

Silence feels long to you. It feels confident to others.

Cultural Sensitivity and Global Work

As work becomes global, cultural fluency becomes career leverage.

Do not assume:

• Communication style

• Humor tolerance

• Directness norms

When unsure, ask respectfully.

Curiosity outperforms assumption every time.

The Career Multiplier Effect

Language is not soft.
It is strategic.

The way you:

• Present results

• Ask for help

• Give feedback

• Negotiate

• Disagree

• Lead

…directly influences how fast you advance.

You can do excellent work and stall.

Or you can learn to communicate your value clearly and accelerate.

Language determines which path you take.

TL;DR

Most careers do not stall because of lack of talent. They stall because people misread timing, power, and context at key transitions. How you enter a company, respond to promotions, and exit an organization quietly compounds over time. This piece breaks down how high performers handle each of those moments with intent, protect optionality, and use transitions to accelerate their careers rather than slow them down.

Most people think careers are built by doing good work consistently.

That matters. But it is not the whole story.

Careers are often decided at transitions.
The first few weeks in a new role.
The moment someone gets promoted over you.
The day you decide it is time to leave.

These moments are where momentum is either created or quietly lost. Not because of effort or intelligence, but because of judgment.

This piece is about how to handle those transitions well.

Not perfectly.
Not heroically.
But deliberately.

Part I: Successfully Starting at a New Company

The best start I ever had at a company began with doing something simple but difficult.

I listened.

My leader and peers explicitly told me to take the first couple of days to meet people, have coffees, and get a lay of the land. My calendar filled quickly with reoccurring meetings and onboarding calls with HR, IT and so on, but I protected my time. Declined all of them (except the HR one…).

Two things happened immediately.

First, I showed that I take advice seriously, especially from my boss.
Second, I learned more in two days of listening than I could have learned in weeks of acting.

I took detailed notes. I asked follow-up questions. I did not try to impress anyone.

Only after that did I build a 30 day plan, which then informed my 60 and 90 day plans.

Do not over engineer your start

Unless a 30-60-90 plan is explicitly required, building one before you start is usually wasted effort.

Even great interview processes do not reveal:

• The real power dynamics

• The unwritten rules

• Why things are done the way they are

• Which problems are real versus just loud

Listening first gives you context. Context gives you credibility.

Get close to the customer immediately

No matter your role, get as close to customers and frontline teams as possible.

Sit in on sales calls.
Read support tickets.
Watch how work actually happens.

This grounds you in reality and helps you focus on changes that actually matter.

Respect what existed before you arrived

Early in my career, I thought many things obviously needed to change. Over time, I learned that most systems exist because of constraints you do not see yet.

Showing respect for what came before builds trust with the people who are there now.

Do not judge a company by Day One

One of the best companies I ever worked for had one of the worst first days.

The entire team was on holiday in another country. No one responded to emails or calls. Instead of reacting, I used the quiet to read, explore systems, and understand customers.

That company ended up being one of the best experiences of my career.

A great first day does not guarantee a great company.
A rough first day does not doom it.

The LISTEN framework

• Learn the unwritten rules

• Invest in relationships early

• Sit with customers and frontline teams

• Take advice seriously

• Earn trust before change

• Never judge the company by Day One

Part II: Starting a New Role After a Promotion

Promotions do not change systems. They expose them.

One of the hardest transitions is when a peer becomes your manager or when you become theirs.

I have been on both sides.

Early in my career, I did not get the first management role I wanted. A close peer did. Instead of reacting emotionally, I supported them fully. A few months later, I was promoted into management alongside them.

That outcome was not luck. It was the result of how I handled the moment.

When someone else gets promoted

When this happens, you have two honest options:

Support them and continue building leverage.
Or decide the system no longer supports your goals and plan your exit professionally.

Both can be right. Quiet disengagement is not.

I have also chosen to leave organizations after promotions because I could see my work would enable someone else’s success without creating a path for my own.

That is not bitterness. That is project management.

If your career is a project and the current system no longer leads to your goal, you change the plan.

A mistake I learned from

Once, when someone was promoted over me, I told them the same day that I was going to start looking and leave.

That honesty did not help anyone.

I could have congratulated them, continued contributing, and quietly planned my next move. Instead, I shared information too early and learned a lesson about timing.

RESET after promotions

Every promotion, yours or someone else’s, requires a reset:

• Identity

• Expectations

• Relationships

• Leverage

If you do not reset intentionally, you remain trapped in your old role.

The RESET framework

• Redefine expectations

• Evaluate the system honestly

• Support before you steer

• Establish authority deliberately

• Time your next move

Part III: How to Put in Your Notice and Exit

The worst exit of my career happened because I followed well-intentioned advice.

The executive team was told that if we ever moved on, we should give plenty of notice and the organization would support us and make sure it was a positive smooth path out.

I did exactly that.

What happened instead:

• I was excluded from leadership decisions

• My influence dropped immediately

• My team lost clarity and context for their work

• My impact declined

The leader actually handled it well. The system and broader team did not.

The hard truth about exits

Once you resign, incentives change, regardless of culture.

Companies optimize for continuity.
You must optimize for yourself.

Why long notice often backfires

Giving extended notice can result in:

• Being sidelined immediately

• Losing access or influence

• Damaging your final reputation

Unless you are certain what happens next, give the minimum notice required and no more.

Understand company precedent. If others were walked out early or even the day of giving notice, assume you could be too.

Exit honesty is overrated

Exit interviews rarely drive change. In practice, they exist to manage risk.

Being overly honest does not help you and rarely helps the company.

A clean message is enough:
”This was a great experience. I learned a lot. I am excited for a new challenge and will always speak positively about the company.”.

Do not expect a counteroffer

Resignation is not a negotiation.

Many leaders do not counteroffer. Some explicitly never do. I never do.

Before you resign, decide:
Would you accept a counteroffer?
If yes, what would it truly change?

Then resign with clarity, not hope.

Timing matters

If you have decided to leave:

• Do it at the start of the day

• Do not linger through meetings

• Do not delay the conversation

Dragging it out helps no one.

The CLEAN framework

• Clarify your decision first

• Limit honesty to what is useful

• Expect no counteroffer

• Assume they may walk you out

• Nurture relationships after, not during

Final Thought

Your career is not a loyalty test.
It is a long-term project.

Entering well builds trust.
Promotions test judgment.
Exits reveal maturity.

Handle transitions deliberately and you preserve something more valuable than any title.

Optionality.

That is how careers accelerate.

That framing is why so many people lose negotiations they “should” have won.

Strong negotiators understand something different:

Negotiation is a system of decisions and conversations that start long before the ask and continue long after the agreement.

If you internalize that, everything else becomes easier.

A Simple Negotiation Framework You Can Remember

When people are under pressure, complexity fails. So here is a short framework you can keep in your head in any negotiation:

P.A.C.E.

P – Prepare

• Know what you want.

• Know why it is justified.

• Know what alternatives exist (yours and theirs).

A – Anchor

• Whenever possible, put the first credible number on the table.

• Force the other side to react to your reference point.

C – Collaborate

• Make the other party part of the solution.

• People defend plans they helped create.

E – Execute Over Time

• Especially for internal negotiations, results compound.

• The real negotiation often happens between formal review cycles.

You will see this framework applied differently depending on the situation, but it always holds.

Salary Negotiation, Part 1: Negotiating a New Job Offer

This is the most familiar form of negotiation, and ironically the one people often handle the worst.

Read more

• Most people fail in sales and interviews because they sell their way, not the other person’s way.

• Success comes from reducing friction by matching pace, detail, and framing to their style.

• This is not manipulation. It is strategic empathy—and it materially increases close rates and interview conversions.

• Every interviewer, buyer, or stakeholder typically maps to one of four styles: Analyst, Collaborator, Driver, or Expressive.

• You can adapt quickly by identifying two traits: Assertive vs. Responsive and Task vs. People focused.

One of the most underdeveloped skills in selling (whether you are selling a product, an idea, or yourself in an interview) is the ability to adapt to how the other person communicates and what actually motivates them.

Most people sell the way they like to be sold to.
Top performers sell the way the other person needs to be sold to.

This framework gives you a fast, observable way to do exactly that.

By identifying just two dimensions—Assertiveness and People vs. Task focus—you can adjust your approach in real time and materially improve outcomes across sales calls, interviews, negotiations, and internal conversations.

The Sales (and Interview) Approach Grid

Every person you interact with falls somewhere on two axes:

• Assertive vs. Responsive – how they exert control and make decisions

• Task-Focused vs. People-Focused – what they value when processing information

Those two signals usually place them into one of four styles:

• Analyst

• Collaborator

• Driver

• Expressive

Your job is not to label them permanently.
Your job is to adapt faster than the person across the table.

Axis 1: Assertiveness

How Someone Exerts Control

Assertive

• Decisive, fast-paced, outcome-driven

• Pushes for movement and conclusions

• Comfortable with pressure and risk

Responsive

• Thoughtful, deliberate, reflective

• Values preparation and structure

• Avoids imposing pressure

Axis 2: Task vs. People Focus

How Someone Decides

Task-Focused

• Logic, facts, evidence

• Efficiency over rapport

• Minimal emotional expression

People-Focused

• Trust, intuition, relationships

• Emotional context matters

• Conversation builds confidence

The Four Personality Styles

Analyst (Task + Responsive)

• Values accuracy, structure, and logic

• Prefers written follow-ups and time to think

• Distrusts hype and pressure

Adapt by: being precise, structured, and patient.

Collaborator (People + Responsive)

• Values trust, harmony, and relationships

• Reads emotional tone carefully

• Avoids conflict and pressure

Adapt by: slowing down, listening deeply, and building rapport.

Driver (Task + Assertive)

• Values speed, ownership, and results

• Time-sensitive and decisive

• Little tolerance for inefficiency

Adapt by: being concise, confident, and outcome-oriented.

Expressive (People + Assertive)

• Values energy, vision, and momentum

• Big-picture thinker

• Decides quickly based on instinct

Adapt by: matching enthusiasm, storytelling, and pace.

Why This Wins Interviews

Most candidates prepare answers.
Very few prepare adaptation.

Interviews are human conversations run by overloaded decision-makers. When you match the interviewer’s style, you reduce cognitive friction—and that advantage compounds fast.

Interviewers subconsciously favor candidates who:

• Communicate the way they do

• Think in familiar patterns

• Make decisions feel easier

This framework lets you do that intentionally.

Diagnose the Interviewer in the First few Minutes

Ask yourself:

• Are they structured or conversational?

• Results-focused or relationship-focused?

• Fast-moving or reflective?

• Do they interrupt or listen?

Once you see it, adjust:

• Pace

• Level of detail

• How you frame success

The Real Advantage

This is not about being fake.
It is about being effective.

The best sellers, leaders, and candidates are not the most aggressive or charismatic. They are the most adaptive.

Your challenge this week:

In your next three conversations:

1. Identify the other person’s style

2. Adjust one element—pace, framing, or detail

3. Watch how resistance drops

That is how interviews convert, deals close, and careers compound.

Leave a comment

Not a checklist.
Not a scorecard you hang on the wall.
But the core elements that quietly determine whether people actually trust you—or just comply because you have the title.

Trust isn’t built by being excellent in most areas. It’s built by being consistent in the ones that matter most. And over the years, I’ve seen how a single cracked foundation can undermine everything else a leader does well.

Let me start with a story.

When Consistency Is Missing, Everything Wobbles

I once worked for a leader who nailed many of the foundations of trust. They were smart. Ethical. Strategic. They cared deeply about the team and the mission.

But they could not manage time.

Meetings were unpredictable. Sometimes they showed up late. Sometimes they were distracted. Sometimes they missed them entirely. As a team, we started joking:
“Do we even need to prepare? It’ll probably get canceled or they won’t show.”

Here’s the thing—jokes like that are a warning sign.

Momentum died. Accountability blurred. And the irony? On the rare occasions they did show up on time, punctuality suddenly became a big deal. They’d hold others accountable for being late, even though consistency was missing on their side.

That single crack—reliability—undermined trust across the board.

It didn’t erase their competence or intent.
But it weakened belief in their leadership.

When Discretion Is Broken, Safety Disappears

In another role, I worked with a leader who was exceptional on many fronts. They knew the business. They had earned their role. They were decisive, thoughtful, and respected.

But they couldn’t keep information private.

Everyone knew everything about everyone. Who was struggling. Who was sick. Who was on a performance plan. What should have stayed between a leader and an individual became common knowledge.

And once that line was crossed, something subtle but dangerous happened.

People stopped sharing.
People stopped being honest.
People protected themselves.

If you assume anything you say might be repeated, you don’t open up—you perform. And because the leader modeled this behavior, the team followed suit. Trust didn’t just erode upward; it eroded laterally. People stopped trusting each other, too.

One missing foundation—discretion—made the entire environment feel unsafe.

The Real Lesson: Trust Is Structural

These experiences taught me something critical:

Trust isn’t about intent.
It’s about patterns.

You can be strong in many areas, but trust behaves like a structure. When one foundation weakens, the whole thing becomes unstable.

Here are some of the foundations I’ve seen matter most in leadership:

• Competence – Do people trust that you know what you’re doing?

• Consistency & Reliability – Do your actions match your words, over time?

• Integrity – Do you make the right call even when it costs you?

• Fairness – Do people believe they’re treated equitably?

• Availability & Presence – Are you actually there when it matters?

• Decision Transparency – Do people understand how and why decisions are made?

• Follow-Through – Do commitments mean something?

• Discretion – Can people trust you with sensitive information?

• Constructive Intent – Do people believe your feedback is meant to help, not harm?

• Self-Awareness – Do you know your blind spots—and own them?

You don’t need to be perfect in all of these. But you do need to be honest about where you’re strong and where you’re fragile.

The Leadership Move Most People Avoid: Self-Evaluation

Here’s the uncomfortable part—and the most valuable one.

Most leaders evaluate performance.
Very few evaluate trust.

A real self-evaluation isn’t asking, “Am I a good leader?”
It’s asking:

• Where do people quietly compensate for me?

• Where do jokes hint at frustration?

• Where do people hesitate before speaking?

• Where do I assume trust instead of earning it?

And here’s the key: you can’t self-score this alone.

If you truly want to strengthen your foundations of trust:

• Ask for specific examples, not ratings

• Invite feedback without defending

• Listen for patterns, not outliers

• Look for the one foundation that might be undermining the rest

Often, it’s not the thing you think.

One Foundation at a Time

Trust doesn’t usually collapse all at once. It erodes quietly, one small inconsistency at a time.

The good news?
It’s built the same way.

You don’t need a massive overhaul. Sometimes, strengthening a single foundation—showing up consistently, protecting confidentiality, following through—changes everything.

So as you reflect on your own leadership, ask yourself:

Which foundation, if strengthened, would most improve trust around me?

That’s where the real work starts.

Thanks for reading.
Let’s keep building trust—deliberately, honestly, and one foundation at a time.

It’s that you don’t fully understand how interview decisions are actually made.

Most candidates walk into interviews thinking they’re there to prove competence. In reality, by the time you’re interviewing, competence is assumed. Interviews exist to answer a different question:

“Is this the person we want to work with — and will they make our lives easier or harder?”

Understanding that distinction changes everything.

The Reality Interviewers Are Operating In

Interviewers are overloaded.

In this market, they may:

• Review hundreds of applications

• Conduct 5–10 interviews in a single day

• Participate in multi-stage processes with 3–8 interviewers

• Balance hiring alongside their actual jobs

Even for entry-level and early-career roles, candidates are now facing:

• Recruiter screens

• Hiring manager interviews

• Panel interviews

• Culture-fit interviews

This isn’t because companies enjoy complexity. It’s because hiring is high-risk, and teams are trying to reduce the chance of making a mistake.

Which leads to the most important insight:

Interviews are less about finding the best candidate — and more about avoiding the wrong one.

The Silent Questions Every Interviewer Is Asking

Regardless of role, seniority, or company size, most interviewers are subconsciously asking the same questions:

1. Will I enjoy working with this person?

Not just “are they nice,” but:

• Do they communicate clearly?

• Are they thoughtful in meetings?

• Will they make collaboration easier or harder?

A simple test many interviewers use — whether they admit it or not:

“Would I want to be stuck on a five-day work trip with this person?”

2. Are they still hungry?

This matters especially for:

• Career switchers

• Mid-career professionals

• Candidates who appear “overqualified”

Interviewers are trying to understand:

• Are you willing to do the work this role actually requires?

• Do you respect the level you’re stepping into?

• Or are you already mentally focused on the next job?

Nothing raises risk faster than a candidate who says the right things but signals they don’t want to do the day-to-day work.

3. Will this person make my life easier?

Hiring managers don’t need heroes. They need:

• Reliable execution

• Sound judgment

• Someone who doesn’t require constant oversight

“Easy to work with” is not a soft compliment. It’s a hard differentiator.

Why Skills Rarely Win the Interview

Unless you are in a truly scarce role (for example, bleeding-edge AI engineering), you are not unique on skill alone.

By later interview stages, most candidates are:

• Close enough technically

• Qualified on paper

• Capable of learning what they don’t know

So the decision shifts from capability to confidence and trust.

Interviewers ask themselves:

• Who feels prepared?

• Who understands the business?

• Who sounds like they’ve done this before — or are ready to?

That’s why interviews are not performances.

They are trust-building sessions.

The Cheat Code Most Candidates Never Use

If you’re allowed to ask questions early in the interview, ask this:

“Before we get started, can you describe what your ideal candidate looks like in this role — how they operate, how they communicate, and what success looks like in the first 6–12 months?”

If the interviewer answers, they’ve just told you:

• What they value

• What they’re worried about

• How to tailor every answer you give

Most candidates never ask this. The ones who do instantly stand out.

Common Interview Mistakes That Kill Conversions

These show up constantly — even among strong candidates:

• Rambling instead of being succinct
  Long answers signal lack of judgment.

• Overselling instead of demonstrating confidence
  Confidence feels calm. Ego feels loud.

• Generic answers disconnected from the company
  This tells interviewers you didn’t do the work.

• Talking about ambition without respecting the role
  Especially dangerous for career switchers or “step-back” moves.

• Treating the interview like a stage instead of a working conversation

Remember: interviewers assume this is your best version. If this is 100%, they’re mentally discounting what they’ll actually get day-to-day.

How to Prepare Like a Professional

Pre-Interview Checklist

Before every interview, you should be able to answer:

• Why this company?

• Why this role — right now?

• What problems does this team actually need solved?

• How would I add value in the first 90 days?

• What does success look like in year one?

Go beyond the website:

• Read interview reviews (Glassdoor, Indeed)

• Understand the interview structure

• Talk to customers, sales reps, or support teams

• Use your network to gather context

Preparation is how you reduce perceived risk.

How to Show Up During the Interview

• Be respectful, energetic, and engaged

• Answer the question that was asked — clearly and directly

• Demonstrate judgment in what you emphasize and what you leave out

• Show that you can operate independently and collaborate well

Your goal is not to impress.
Your goal is to make the interviewer feel confident.

Post-Interview: Where Most Candidates Miss the Opportunity

After the interview:

• Send a concise, thoughtful follow-up

• Reinforce alignment with what they said they needed

• Clarify enthusiasm without desperation

A good follow-up says:

“I listened, I understood, and I’m intentional.”

The Bigger Point

When you treat interviews like performances, you optimize for approval.

When you treat interviews like working sessions, you optimize for fit, trust, and long-term success.

This is what it looks like to treat your career like a project:

• Preparation

• Intent

• Strategy

• Consistency

If you do this well, interviews become easier — and more enjoyable — because you’re no longer guessing what matters.

Next up: how to turn offers into employment — including negotiation, leverage, and decision-making when you have options.

That’s where most people leave value on the table.

If you want consistent access to interviews, treat your career like a project — not a lottery.

The Core Principle

If you do what everyone else is doing, you should expect average results.

Mass applying, generic resumes, and hiding behind job boards puts you in the same bucket as thousands of other candidates. The people getting interviews are doing fewer things — better and more intentionally.

What Actually Drives Interviews

1. Referrals and familiarity beat volume
Hiring teams prioritize candidates they already know, or who come recommended. This isn’t favoritism — it’s risk management.

2. Timing matters, but differentiation matters more
Applying early helps. Applying early with context, customization, and connection is what gets noticed.

3. Networking is not optional
Most roles are filled through networks, not postings. Networking is not a personality trait — it’s a professional responsibility.

4. Intent signals seriousness
Customized materials, thoughtful outreach, and genuine curiosity signal that you’re not just “looking for a job” — you’re looking for this job.

The Weekly Career Operating Rhythm

(Do this whether you are actively job searching or not)

If you only do this when you’re desperate, you’re already behind. The goal is to always have one opportunity on deck.

Each Week, Commit to the Following:

1) Research Deeply

• Identify 5 roles or companies you would genuinely consider

• Understand their business, challenges, and what success looks like in the role

• Ask: How could I add value quickly here?

2) Apply Intentionally

• Tailor applications for roles you actually want

• Align your resume and cover letter to the specific outcomes the role is hiring for

• Quality beats volume every time

3) Network With Purpose

• Reach out to 10 industry connections

• No cold asks — lead with insight, curiosity, or contribution

• Alumni, former coworkers, peers, and second-degree connections all count

4) Engage Recruiters Proactively

• Add 5 relevant recruiters on LinkedIn

• Introduce yourself clearly: who you are, what you do well, what roles you’re targeting

• Stay visible so you’re top of mind when roles open

5) Show Real Curiosity

• Use the product

• Book a demo

• Talk to customers or salespeople

• Attend a meetup or community event

People remember candidates who already understand the business — and they refer them.

The Long Game Advantage

Do this consistently and something important happens:

• Recruiters start reaching out to you

• Referrals come faster because relationships already exist

• Interviews feel easier because context is already built

• You stop job searching from a place of urgency

Always having one on deck — a conversation, a warm intro, a recruiter relationship — is one of the most effective ways to reduce career risk and increase leverage.

This isn’t disloyal.
This isn’t transactional.
This is how professionals manage their careers intentionally.

The Bottom Line

Stop doing what everyone else is doing.
Start doing what very few people are willing to do consistently.

That’s how interviews happen.
That’s how offers happen.
That’s how careers compound.

And that’s the real separator.

Michael Jordan said it best:
“My best skill was that I was coachable. I was a sponge and aggressive to learn.”
If the greatest ever believes coachability was his advantage, what does that tell the rest of us trying to build meaningful careers?

For early-career professionals especially, being coachable isn’t optional — it’s the difference between slow progress and explosive growth. It’s also one of the easiest traits to spot. Your leaders notice it immediately, and it shapes the opportunities you get (or don’t get).

The Moment I Wasn’t Coachable—and It Cost Me

Years ago, I pushed back on something simple:
I didn’t want to attend networking events.

I thought they weren’t a good use of time. I felt pride that my work should speak for itself. And honestly, I was a little nervous —those rooms made me uncomfortable.

So I skipped one particular event with the CEO and a few others.

A few weeks later, someone else who did attend that event—someone with practically no leadership experience—walked out with the CEO’s ear. They spent a few days together, built a relationship, and suddenly that person went from my peer’s subordinate… to my boss.

You can imagine the impact.
I didn’t get the promotion and I left shortly after.
The organization suffered.
That leader was eventually let go.

Looking back, the lesson was brutally clear:

Small rooms create big opportunities—if you’re in them.

I wasn’t coachable in that moment.
I defended instead of listening.
I resisted something that was meant to help me grow.
I wasn’t curious — I was closed.

And it cost me.

What Coaching Really Is (And Isn’t)

A lot of early-career professionals (and senior ones too) see coaching as a sign they’re in trouble.
But the opposite is true.

Coaching is proof someone sees potential in you.

Coaching is the process of unlocking that potential — not by giving you answers, but by helping you build awareness, clarity, capability, and confidence. Whether it’s leadership coaching, performance coaching, career coaching, or even sports coaching, the fundamentals don’t change:

A coach helps you see what you can’t see.
A coach challenges you.
A coach accelerates your growth.

And most importantly:
A coach only invests in people who show they can use the investment.

What You Gain When You’re Coachable

When you lean into coaching, everything gets better:

1. You gain clarity on expectations

You suddenly understand what good looks like and how to get there.

2. You learn faster and earn faster

People who implement coaching quickly see new opportunities show up.

3. You build deeper trust with your leader

Leaders invest more in the people who show they can—and will—grow.

4. You improve performance across the board

Communication, execution, prioritization, leadership — all of it.
Every metric trends upward when you’re coachable.

5. You build real momentum in your career

The compounding effect is real:
Coachable people get coached more → grow more → earn more → get more opportunities.

What NOT Being Coachable Looks Like

There are a few instant giveaways:

• Defending instead of listening

• Blaming circumstances or other people

• Rejecting feedback without exploring it

• Needing to be right

• Avoiding discomfort or growth opportunities

When you do these things, here’s what actually happens:
Your leader stops coaching you.

And once that happens, your development slows or stalls.

How to Become More Coachable (Starting Today)

Use this simple framework:

Listen → Reflect → Act → Iterate

1. Listen without defensiveness

2. Reflect on what’s true

3. Act quickly on the feedback

4. Iterate based on what you learn

If you do these four steps consistently, your career will accelerate faster than you can imagine.

The Challenge for This Week

Choose one piece of coaching or feedback you’ve received recently.
Then:

1. Apply it today

2. Track how you executed it.

3. Follow up with your leader:

   • Share how you implemented it

   • Confirm you executed it correctly

   • Ask for a next-level refinement

This is how coachable people operate.
This is how opportunities unlock.
This is how careers accelerate.

Your career isn’t waiting — and neither should you.