Five weeks to October 31. Issue 8 went to the other side of the table. This one comes back.

If you are in a process right now, or about to be, the next five weeks decide whether it closes this year. Everything below is the part almost nobody rehearses: not how to get an offer, but what to do in the ten days after one appears.

If you are hiring, forward this to the person you are trying to close. Half of it is aimed at you anyway.

Deciding on schedule beats deciding on perfect.

The hardest moment in a search is not getting an offer. It is holding one while something else is still three rounds out, and trying to decide whether to wait.

Almost everyone waits too long. The reasoning feels sound, that more information makes a better decision. But the information rarely arrives on your schedule, the offer in hand has a shelf life, and the waiting itself has a cost that nobody counts. You get worse at the process you are still in, because you are half out of it. And the company holding your offer starts reading your silence as doubt, which it sometimes is.

The fix is not deciding faster. It is deciding on a date you set yourself.

The moment you have one real offer, name your own deadline out loud, to yourself and to the other processes. “I need to give an answer by the ninth, so I am asking whether you can get to a decision by then.” That sentence does more work than any negotiation tactic. It accelerates the people who are serious, it surfaces the ones who were never going to move, and it protects you from drifting past the offer you actually had.

The same move works from the hiring side with one change. Give a real deadline with a real reason attached. An exploding offer is a threat and people can feel it. “We want to close this by Friday because the team starts the next project Monday” is context, and candidates respond to context.

The number moves last. Everything around it is still open.

By the time an offer letter exists, the band is mostly set. Bands are precedent, and precedent is what companies guard hardest. So the negotiation most people run, pushing on salary alone, is aimed at the one thing least likely to give.

What does move: scope and title clarity, the reporting line, the first project in writing, a checkpoint at ninety days, the start date. All of it costs nothing and reduces everyone’s risk, which is exactly why it is available.

Stop asking whether they can pay more and start asking whether you can write down exactly what you are owning and how you will both know it is working. You get a clearer job, they get a calmer hire. And if a company will not put the scope in the letter, you have learned something more useful than a number.

There is one exception to the band being fixed and it is worth knowing. A band set before a company’s last round is not a band anymore, it is a leftover. Funding size does not predict what a company pays. What predicts it is who owns the band and when they last opened it. Asking when the range was last reviewed is a fair question, and it occasionally moves things that salary pressure never would.

Equity you cannot value is not compensation. It is a story.

Nearly every startup offer includes an equity number, and most candidates have no way to know what it means. That is not a failure of financial literacy. It is that the three facts you need are frequently not in the letter.

You need the strike price, the current preferred valuation or the most recent 409A, and the total shares outstanding. Without those, a grant of 50,000 options is a number without units.

Then there are the terms that decide whether you ever see any of it. The vesting schedule and cliff. The exercise window after you leave, which at many companies is ninety days and which quietly converts your equity into a bill you have to pay in cash to keep. Whether preferences stack ahead of you in an exit.

Ask for those numbers in writing before you sign, and treat the answer itself as information. Plenty of companies will give you all of it in an afternoon, and that willingness tells you something good. A company that gets uncomfortable has told you something too.

The two honest paths, if you have not started.

There are two paths, and both of them are honest.

One is warm and fast. Put this month into the people who already know your work. That is the one route where a late start can still close this year.

The other is to use the freeze on purpose. January headcount is decided in November, and by the time a January req appears publicly the decision behind it is two months old. So the way to be considered for a January role is not to apply in January. It is to be a name in the room during the November conversation. That means being in touch with the companies you want before they finalize, even when they have nothing open. “I am not asking you for anything, I just want to be on your radar for next year” is a completely normal message and almost nobody sends it.

What does not work is the third path, which is to keep running October at half speed and hope.

None of this is complicated. It is just that the last mile is the part nobody practices, because you only get there a few times in a career and each time it feels like the first.

The one-page close checklist from Issue 7 still holds. What to have written down before you accept, what to ask for that costs the company nothing, and the one question that tells you whether a process is real. Print it or keep the tab open.

Get the close checklist →

In two weeks, Issue 10, written to the founder again: what October actually decides. What still closes this year, what does not, and what waiting until January costs you that nobody puts a number on.

Jeremy

P.S. One ask, one line. If you are holding an offer or about to be, what is the one thing you wish were written into it? Reply and tell me. I read every one.

Seven weeks to October 31. This one is written to the person on the other side of the table.

Consilio News usually speaks to the designer running a search from the candidate’s side. Today it speaks to the person doing the hiring, because most of what decides a design hire happens on your side of the table and almost none of it is visible from theirs.

If you are a designer, forward this to the founder you are talking to. If you are the founder, forward it to the designer you are trying to hire. That is the whole design of this issue.

What we saw when we opened three books in front of the people who made them.

Carl Wheatley and I ran portfolio office hours a few weeks ago. Real portfolios, live, with the designer in the room. Two numbers from that hour have stayed with me.

One designer, eight to ten years in, two companies, one of them acquired. 231 applications over four months. Three intro calls. All 231 went out pointing at a single unchanged version of the same site.

Another designer, same market, same month. Eleven interviews in two to three weeks.

That gap is not talent and it is not the market.

And roughly one in five of the books submitted to us was password-gated, which means the first thing a hiring manager meets is a login screen and a decision about whether that book is worth the friction.

Here is what I said in the room and it is the thing I keep coming back to. It is almost never the craft that is the problem. It is the container.

Strong designers work at companies whose direction they did not choose, on products they never got to shape. That says nothing about whether they can solve your problem. What it removes is the shorthand you were reading for without noticing.

Then Carl named the part founders do not usually admit out loud. A lot of the ones he talks to have never hired a designer before, especially for a founding designer role, and when nobody in the room has hired one, polish is the signal they trust. The beautiful book gets the interview whether or not the thinking underneath earned it.

Both things are true at once, and the gap between them is where your search is leaking. The book that looks resolved gets the call. The book that is resolved does not always look it. It is easy to grade the container and call it craft. I have done it. When that happens, the search is running on the wrong signal.

The read forms earlier than the process suggests.

You land on a view of a candidate fast, often inside the first conversation, and much of what follows is you looking for reasons to confirm it. That is not unfair, and it is not lazy. It is what deciding under uncertainty looks like when the seat matters and the runway is finite.

Once the read settles, you move faster than your own process suggests. The offer appears in days. References get called the same afternoon. A loop that was going to take four weeks collapses into one.

Which is worth knowing about the searches where that has not happened. A company that looks slow is usually a company that has not decided yet.

Reqs do not stall on candidates. They stall on three boring things.

Design roles sit open for months, and the reason is almost never that nobody good applied.

The calendar. Three people who need to be in the same debrief cannot find the same hour, and a week becomes three. Companies rarely lose great candidates to a competitor’s better offer. They lose them to their own scheduling.

The unnamed seat. Nobody decided which job this actually is. Senior is not one job, it is three, and if the seat was never named then every debrief argues a different role. The disagreement looks like a disagreement about the person. It is not. It is a disagreement the team never had with itself.

The stale band. A company with $95 million in the bank offered a senior designer a band thirty thousand below market this year. Not a lowball tactic. The band had been set a while earlier, nobody revisited it after the round closed, and the finance posture never connected the raise to the salary bands.

Funding size feels like it should predict what you pay. It does not. What predicts it is who owns the band and when they last opened it.

One of these is bad luck. Three of them together is usually a process, and a process is something you can fix.

The first ninety days are decided in the offer letter.

By day ninety you will have formed a durable view of this person, and most of it will have formed well before then. That view is rarely written down anywhere, which means the person it is about has been working without it.

They spend their first month solving for a standard they cannot see. You spend it deciding privately whether this is working. You are both running a test that only one of you knows the terms of.

The fix costs twenty minutes and it belongs before the signature. Name the first project. Name who they work with. Name what you will look at in week twelve.

You get a faster ramp, you find out sooner if it is wrong, and you stop losing good hires to a bar that nobody had written down yet.

The arithmetic, because it is September.

Seven weeks to October 31. Four to six weeks from first call to signature when both sides are moving, and that is before anyone takes a week off.

A search that has not started by the third week of September is not closing this year. It is closing in January, against a budget nobody has approved yet.

There is one exception and it is a large one. Warm paths compress. A process that starts with someone who already knows the work can close in two weeks, because the trust step is already done.

September is not early. It is the last month that is still on time.

None of this is a criticism of how you are running it. Most of it only looks obvious from the outside, which is the only reason I can see it at all.

So here is the offer. Take five minutes and write down five things about the req you are about to open, or the one already sitting there. Which of the three seats it is. Who owns the band and when they last opened it. Who is in the debrief and when they are free. The first project. What you will look at in week twelve.

Whichever ones come back blank, send them to me. I will tell you which single one is costing you the search. No pitch attached, and it takes about fifteen minutes.

Send me the blanks →

In two weeks, Issue 9: the last mile. Deciding on schedule, negotiating the role rather than the rate, and the two honest paths if you started late.

Jeremy

The real decisions happen when you are not there. A debrief you never hear. A line that did or did not make the letter. A calendar that told you the truth three weeks ago.

This issue is those three.

The room you are not in

The most contentious debrief I ever sat in was about a designer with no famous companies on his résumé.

Nobody in that room was against him. That is what people get wrong about debriefs. There is rarely a villain. The room was uncertain. Uncertainty is harder to argue with.

They kept circling one question: would the skills transfer at that scale? Fair question. But nobody in the room had taken that risk before. Nobody had a story to point to. A room without a precedent defaults to no.

What made it contentious was not the discussion. It was that I would not let it end.

I argued for the hire. Not because I was certain. I was not. I argued because I could see what the room was doing: easing its own discomfort and calling it a signal about him. From the inside, those two things look identical.

He got the offer. He stayed for years. He did excellent work. He has been successful everywhere since.

His résumé was accurate. The room just could not read it. The shorthand was missing.

When the shorthand is missing, people do not read more carefully. They get uncomfortable. And discomfort gets written down as doubt.

That is not a flaw in hiring managers. It is what time pressure does in a room where a no costs nothing.

So give the room something to repeat. Not a better adjective. A sentence somebody can say out loud when you are not there to say it yourself.

What is still open after the band is set

By the time a letter exists, the number is mostly decided. Bands are precedent. Precedent is what companies guard hardest. So pushing on salary alone aims at the one thing least likely to move.

I have read a lot of these. The things that worry me are never the number.

• A title bigger than the authority. Head of Design with no reports and no budget is a nice word attached to an IC job. Nice words do not survive a reorg.

• A vague reporting line. “Reporting into the product org” almost always means it is unsettled. You will find out who your manager is in month two, and you will have no say.

• Equity with no context. No valuation, no strike, no vesting detail. That is a number without units. It is not a lie, but it is not compensation either.

• A start date that is suspiciously urgent. Sometimes it is a real launch. Often it is a company that has been bleeding on this seat for months. That tells you what your first quarter looks like.

• The exciting parts that never made it into writing. The scope you discussed, the first project, the team you would build. If it was real in the conversation and missing from the letter, it was aspiration.

One of these is noise. Three together is a pattern.

And every one of them is free to fix. That is exactly why it is available. The scope. The reporting line. The first project in writing. A checkpoint at ninety days. The start date. None of it costs the company a dollar. All of it lowers the risk for both sides.

Stop negotiating the number. Start negotiating the job.

You get a clearer job. They get a calmer hire. And if a company will not put the scope in writing, that tells you more than any number.

If you are the one hiring: write the first project down. Name the manager. Put the checkpoint in the letter. Each one is free. Each one removes a reason to say no to you in October.

Real, or only exploring

One question sorts every conversation you are in. Almost nobody asks it, because it feels pushy.

When do you want this person starting?

It is not pushy. It tells you whether a process is real. The answer puts every conversation into one of three piles.

• A date, with a reason behind it. The seat is funded and somebody is accountable for filling it. This is where your best weeks go.

• Vague, but it gets specific when you follow up. Real, but nobody has sequenced it. Worth staying in, worth not organizing your month around.

• No answer at all. You are talking to a company that is exploring. Exploring can go on for two quarters.

All three are useful. Only one of them deserves your best weeks.

In the fall, asking reads as senior, not impatient. Everyone knows what the calendar is doing. And if you are the one hiring and cannot answer it, better to learn that now than six weeks from now.

A req without a date is a wish.

The arithmetic, plainly

Four to six weeks from first call to signature, when both sides are moving. Four if everyone is decisive. Six is more typical.

The math is simple. Ten weeks from today to October 31. A process that has not started by the third week of September is not closing in October. And November means Thanksgiving, budget freezes, and a hiring manager who has stopped answering.

Companies rarely lose great candidates to better offers. They lose them to their own scheduling.

Close the thing

I made a one-page checklist for the last two weeks of a process. What to get in writing. The timeline test. The questions worth asking even when they feel rude. Print it or keep the tab open.

Get the close checklist

Holding something real right now? A live offer, a debrief you cannot read, a process that will not commit. That is what I do all day. Reply to this email and we will find time.

We ran the portfolio office hours with X2Talent on Tuesday. Three books, live. The notes are going into the next issue.

In three weeks, Issue 8: the founder’s read. The first one written to the other side of the table.

Jeremy

P.S. One ask. Reply with one line: what is the one thing you wish had been written into an offer you accepted? I read every reply.

I have had around seventy of these conversations in the past eight weeks. Different people, different companies, different numbers. The same fork keeps showing up, and almost nobody names it out loud before they are standing in front of it.

“Senior designer” hides three different jobs. Same title on the badge. Completely different days, different wins, and different people who are happy in them.

Here is what each one actually looks like, drawn from people currently living in them.

The leader

Your craft becomes other people’s craft. The day is hiring, unblocking, setting direction, and defending design in rooms designers are not in. Your best work stops being a screen and becomes a decision someone else makes correctly without you.

One of the strongest leaders I spoke with this quarter built a design team from nothing to thirteen people, as head of design at an infrastructure company. He left two years ago. He now bills $500 an hour across fractional engagements, fifty to sixty hours a week, and he is not looking for a full-time seat at all.

That is worth sitting with if you are considering the leader track. The seat is real, and it is rare, roughly 8% of the open design roles I track. But the exit from it has become a good business in its own right, and the best people know it.

Here is the part nobody publishes. Design leaders will not tell you what they need to be paid. Seven leaders gave me their time in this window, and two named a cash floor. Senior individual contributors named one 70% of the time. Leaders have run these searches from the other side of the table, and they refuse to anchor themselves.

The principal IC

No reports. The deepest craft in the building. The hardest problems land on your desk and stay yours. You are measured on the work, not on the team, and the leverage comes from being the standard rather than from managing to it.

The clearest version of this I met was a prototyper at a very large company whose total compensation last year was around $500,000. He runs internal workshops teaching other designers to build, and his own work lands as code in the company’s main repository. He has no interest in managing anyone. His base floor for the next thing is $200,000.

If managing people always felt like a tax on the part you love, this is a real senior track and not a consolation prize. It sets you up to be the person other people are hired against.

One caution. This seat is the easiest of the three to lose by accident, because when a company has only one ladder, the reward for being the best IC is being made a manager.

The founding designer

First or only designer, building the first product alongside engineering, end to end, in heavy ambiguity. Some weeks you are doing brand. Some weeks you are in the codebase. Nobody hands you a brief.

Two of the founding designers I spoke with in this window ship production code. Not prototypes in Figma. Code, reviewed by engineers. Across everyone I have a full record on, thirty-eight percent do.

I want to correct something I have said before and heard repeated everywhere. Founding designers do not take a discount. The two most senior founding-track people I screened named floors of $185,000 and $200,000, and neither moved on stage. Equity is a reason to say yes. It has stopped being a reason to say yes for less.

This seat sets you up to run design once the team exists, or to do zero to one again somewhere else, which is a skill almost nobody can prove they have.

The part I did not expect

I assumed the fork ran one direction. It does not.

One designer I spoke with had been head of product design at a large industrial company and is now a senior individual contributor at a small one. He chose that. Another leader I met is deliberately looking at seats below the title she already holds, because the scope is better and the title was never the point.

Meanwhile someone else joined her company as a senior designer eight years ago, became a manager, then a director, and is now looking at senior IC seats again because she wants to be near the work.

Three people, three directions, one title. The ladder is not a ladder anymore. It is a set of doors, and you can walk back through one without it being a failure.

The two tells

Whatever the title says, a company is hiring one of these three. Two questions expose which one.

Ask what the last person in this seat spent their time on.

Ask what the first six months are supposed to produce.

If the answers do not match the title, believe the answers. You are being hired for a job, not for a word.

One designer I worked with this month asked a company how big the design team was before she would go any further, because she had decided she would not be a solo designer again. That single question saved her a five-week process. Nobody thinks to ask it because it feels rude. It is not rude. It is the whole job.

Why the band tells you nothing

The median design salary band posted right now is seventy-five thousand dollars wide.

That is wide enough that the same req reads as a promotion or a pay cut depending where in it you land. It is also why the band cannot tell you which of the three seats you are being offered. Companies post one range for three different jobs.

Ask the two questions instead.

Find your seat

I made a one-page check. Three columns, one true answer per row, and by the bottom you will know which seat you are in and whether it is the one you want. Take it before you read another job description.

Take the one-page check

And if you are weighing something real right now, a live offer, a seat change, a read on the market, that is what I do all day. Reply to this email and we will find time.

In two weeks, Issue 7: the close.

Jeremy

P.S. One ask. Reply with one line: which seat are you in right now, and is it the one you want? I read every reply.

Getting two good offers is the hardest moment in a job search. Not the getting. The choosing.

If you ran the July moves from the last issue, conversations have started. Offers follow conversations, and inside a window that closes October 31, they follow fast. This framework is one to have ready before the moment arrives, not one to build during it.

I watch senior designers freeze right here every season. Not because they lack options. Because two strong paths are hard to tell apart, and the tool everyone reaches for makes it worse. And this year the freeze is expensive. Two stalled weeks is real ground inside a four-month window.

WHY THE NUMBER IS THE WORST INPUT

When both companies are strong, comp is close enough that it stops being the deciding factor. So people build a spreadsheet, weight the rows, and let the salary break the tie, because the salary feels objective.

It is the worst input you have. It feels precise, so you trust it. But within a tier, the gap is small, and you are about to decide two years of your life on a rounding difference. The number tells you what a company will pay. It tells you nothing about what those two years will feel like.

Settle the fit first. Then negotiate the number. Not the other way around.

THE TWO AXES THAT SEPARATE OFFERS

Where do you grow? Not the title. The people. At which company are you the third-smartest person in the room instead of the smartest? The room that stretches you is the room that makes you better. Pick the one where you are a little outmatched.

Whose problems do you want? Every role is a set of problems you agree to carry for two years. Read both offers as which set you want to wake up to on a hard Tuesday. One of them will feel more like yours. That feeling is data, not noise.

Score those two honestly and the offers separate fast. The one that pays slightly less, grows you more, and hands you problems you actually want is rarely the close call it looked like on the spreadsheet.

THE FUTURE-SELF TEST

Here is the question that breaks the tie when the two axes still feel even. Picture yourself eighteen months in at each company. Which version of you learned more, shipped more, and is readier for the role after this one?

You already know. The freeze is not that the answer is hidden. The freeze is that the answer is not the one with the bigger number, and choosing it takes a little nerve.

THE MATRIX

I made you a matrix for exactly this. Two offers, the axes that matter, scored side by side. Fill it in, and the fork stops looking like a tie.

Get the two-offer matrix

In two weeks, Issue 6: leader, principal IC, or founding designer. Three senior seats, how they really differ, and how to tell which one is actually yours.

One ask. Reply with one line: the last time you chose between two good offers, what finally tipped it? I read every reply.

Jeremy

But the move is not one leap you take this month. It is a four-month campaign, and the clock is already running.

Here is the thing about the second half that most designers never clock. Hiring in H2 completes, or is targeted to complete, no later than October 31. After that, Q4 planning freezes headcount, and everyone waits for January. So the window is not six months. It is four. July, August, September, October. That is the whole game.

EACH ROLE GETS ONE GO

Inside that window, every open role basically runs once. The shortlist forms, the calls happen, the offer goes out, the door closes. There is no second pass in November. Which means being open to opportunities is not a strategy. If you are not in the loop when the shortlist forms, and not prepped when the call comes, you are not going to be in a great position. You are not going to be in the conversation at all.

YOU SPENT H1 GETTING READY. THAT WAS THE POINT.

For two months I wrote about the terrain. What founders actually look for. How to read a hiring team in twenty minutes. Where a senior designer has leverage, and where they only think they do. That was not commentary. It was prep. You have the tools now. The second half is when you use them: pick the companies you actually want, then put every tool and every relationship in your network to work getting traction in those rooms.

STUCK, OR COMFORTABLE

Before you commit the four months, run one honest check. These two feel identical from the inside in June. They are not the same thing, and the window is when the difference matters.

Stuck: the work stopped teaching you something a while ago, and you know it.

Comfortable: the work is fine, the people are fine, and leaving is mostly effort.

If you are comfortable, stay, and stay on purpose. That is a real choice and a good one. If you are stuck, the window is open, and it is the only one this year.

THREE MOVES TO MAKE IN JULY

One. Restart the conversations that fizzled in the spring. The founder who was vague in May often has a budget and a start date by July. A two-line note reopens more doors than you would expect.

Two. Get specific about your own position. You cannot weigh an outside offer until you know what staying is worth. Use your mid-year review to surface the real number, not the polite one.

Three. Name your targets. The roles that clear before October 31 are forming right now, weeks before any public post. The designers who land them are already in conversation. Pick the five companies you want and start those conversations this month.

Over the next few issues I will walk through exactly what getting a new role looks like, step by step, from first conversation to signed offer. Consider this the starting gun.

I made you a worksheet for the audit and the three moves. Fill it in once and the four months get a lot clearer.

Get the mid-year move worksheet

In two weeks, Issue #5: two strong offers and how to choose between them, when the spreadsheet ties and the number is the worst input.

One ask. Reply with one line: the company you keep circling but have not approached yet. I read every reply, and the patterns shape what I write next.

Jeremy

Most senior designers don’t know the rubric.

Seniority has one tell

It’s the depth of your answer when someone pushes. Ask an early career candidate about a design decision and you get the what. Ask a senior and you get the what, the tradeoffs, the second-order effects, and what they’d do differently. Same question, more floors underneath. For years that test only ran on craft. Now it runs on AI too.

AI is a graded question now

“How do you use AI?” is no longer small talk. It’s a graded question, and founders read the depth of your answer the way they read every other one. Here is the catch for strong people: you can be three floors deep on design systems and one line deep on AI, and the one-line answer is the one they remember. Depth on craft doesn’t cover for a shallow answer here. The market is splitting on that line, and the premium on the deep side widens every quarter.

Shallow answer, senior answer

Same question, two depths. One reads early career. One reads like the person they’re trying to hire.

How do you use AI?

Early career: “I use ChatGPT and Figma AI to move faster.”

Senior: “I draft research synthesis with a model and spend the saved day on the design. It’s strong on first passes and weak on taste, so I edit it hard and never ship it raw.”

What did AI change about your work?

Early career: “It made me more efficient.”

Senior: “It moved me from defending one idea to showing range. I bring eight options now, so the conversation is about direction, not my ego.”

Where does AI fall short for you?

Early career: “It hallucinates sometimes.”

Senior: “It’s confident when it’s wrong, so I use it where I can verify fast and avoid it where I can’t. Knowing that line is the skill.”

Notice what the senior answers share. Not a longer tool list. A workflow that changed, a tradeoff named, and a second-order effect on the work. Hit those three and you read senior. Name a tool and stop, and you don’t.

Where the depth comes from

You can’t narrate depth about a tool you opened twice. Every senior answer above is downstream of reps, usually some version of these, most days:

• Draft the first version of anything written with a model, then edit it hard.

• Sketch concepts in the conversation, not after it.

• Pressure-test your own decisions against a model before the meeting.

• Build one small tool a month you wouldn’t have built otherwise.

• Hand your inbox triage to an agent, even a rough one.

• Talk about the output you shipped, not the tools you used.

Do three daily for a month, and your answers change on their own.

What I’d bet on

Don’t just go deep on the craft. Go just as deep on how you use AI. It’s a graded function now, and functions get scored on the depth of the answer.

I made you a scorecard for the six reps. Print it, check the ones you already do daily, and work the blank rows next month.

Get the AI-forward scorecard

In two weeks, Issue 4: the mid-year pivot. H1 is closing. What changes for senior designers in July, and how to move before the market does.

One ask. Reply with one line: on which question above would a founder score your answer early career right now? I read every reply.

Jeremy

The thing nobody tells you

Company history is a polished narrative. Funding rounds. Logos. The press releases that survived. It tells you what the company has been. It says nothing about where it is right now.

The real diagnosis is simpler: on the wave, or off it. The wave is the last twelve months of momentum: the market signal, the velocity of decisions, the pace of hiring, the trajectory of the one metric that matters. The season is where the company sits relative to that wave: building toward it, riding it, or past it.

The landscape is moving fast. Some companies are going public on bets they placed two years ago. Others look impressive on paper and have quietly lost the moment they were riding. You won’t see the difference in the history. You’ll see it in the next twenty minutes of conversation.

Five questions to read the wave before you commit

These are the questions I tell candidates to ask in the second-to-last interview. They surface in twenty minutes what you’d otherwise learn at month four. The hard way.

1. What’s the one bet this company is making in the next twelve months? Companies in a strong season name it in one sentence. Companies past their peak give you three vague themes. Companies, before their season, admit they’re still figuring it out. All three are real seasons. The only question is which one you want to join.

2. What’s changed about your business in the last ninety days that wasn’t in the deck? Tests whether the founder is tracking their own momentum. Recent, concrete answers mean the moment is live. Stale answers, or answers that match the deck word for word, mean the moment already passed.

3. Who are the last three people you hired, and what did each of them turn down to say yes? Quality of talent and competitiveness of the offer, in one question. If they’re pulling people away from top companies, it’s a real season. If they’re winning because they were the only offer on the table, it isn’t yet. Both are answerable. Be honest with yourself about which one you’re joining.

4. What did you decide differently this quarter than last? Velocity of strategic change. Companies in their season iterate fast and can name the iteration. Companies pass it, freeze it, and call it focus.

5. If I joined and built one thing in my first six months, what would make it obvious I picked the right wave? The future-self test. It forces the founder to make the bet from your side of the table, not theirs. If they can’t, the trajectory they’re selling is one they want to be on, not one they’re on.

Why this matters more than it did a year ago

The cost of joining the wrong wave went up this year. AI moved the value of the work upward: what used to be junior is now senior, and what used to be senior is now executive. Companies on the wave compound that shift. Companies off it argue about titles while the work that actually matters goes undone.

The candidates who read the moment before they say yes don’t get fewer offers. They get the right ones. And the offers they pass on save them a year.

What I’d bet on

Don’t read the deck. Read the wave. History tells you who they were. The wave tells you who they’re becoming.

I made you a worksheet for the five questions. Print it. Bring it to your next interview. Fill in one column per company you’re talking to. Patterns surface fast.

Get the role diagnostic

In two weeks, Issue #3: what “AI-forward” actually looks like in a candidate, and why most people who claim it don’t have it.

One ask. Reply with one line: a company whose wave you read wrong, and what you’d ask differently next time. I read every reply.

Jeremy

One leader who didn’t last. The leaders who did. The week I tracked my own hours.

Same story, three times

The measurement was the intervention. Not the trying-harder. Not the willpower. The measurement is what changed what happened next.

The failed hire looked like a talent problem. It was a role-clarity problem. The thriving leaders looked like a discipline story. It was a structural-help story. The lost week looked like a focus problem. It was a measurement problem.

In all three, the layer the problem appeared on was not the layer the problem actually lived on.

Here’s how each one read up close.

The one who didn’t last

Post one was about why most failed leadership hires aren’t about the person. They’re about the role.

The company never asked whether the role was hireable. They wrote a wish-list spec, ran a search, picked a candidate. When the candidate left at month fourteen, they acted surprised. The candidate wasn’t. Nobody upstream had asked the actual question.

The hire wasn’t the variable. The role was.

The leaders who did

Post two was about the leaders I’ve placed who thrived. Looking back, what they had in common wasn’t exotic.

Not vision. Not pedigree. Not charisma.

They protected their time for the work only they could do.

For years I coached this as behavior. Set better boundaries. Delegate. Block your calendar. The strategies worked, up to a point. Then I hit the ceiling. Even the most disciplined leader can’t delegate work nobody else can absorb. There was always a baseline of operational overhead nothing in personal practice could remove.

AI agents removed it.

The leaders who thrive now aren’t more virtuous than the rest. They have structural help the rest don’t have.

The week I tracked

Post three was the week I tracked every minute of my own work.

Forty percent of my hours went to tasks that needed no judgment from me. Twelve hours a week, lost for years. The moment I measured, they had a name. Once they had a name, I couldn’t pretend they were unavoidable.

Why this matters more this year

The pace of change at work has shifted again. Tools moved. Org charts moved. Skill premium moved. Comp expectations moved.

Most of us are still optimizing the week from twelve months ago. Assuming what worked then still works now. It doesn’t.

Call it changemaxxing if you want. Most of the discourse is noise. The signal underneath is real. The world stopped rewarding people for being good at work they trained for a decade ago. It now rewards people who re-measure what’s worth doing every few months and pivot.

The whole game

If we were having coffee and you asked me what the most valuable executive skill in 2026 is, here’s what I’d say.

Run a signal-and-pivot loop on your own work. Track what’s yielding ROI. Cut what isn’t. Double down on what is. Re-measure every ninety days. Repeat.

That’s the game.

The people who do this look prescient. They aren’t. They’re just running the loop more often than everyone around them. Earlier signal, earlier action. It compounds.

Two tools for the loop

Coaching is one tool. A good coach surfaces what you’ve been avoiding, so you can name what’s actually yielding and what’s a comfortable distraction. The hard part isn’t motivation. It’s honest perception.

AI agents are another. They force you to write down what you’ve been doing. You can’t build a useful agent for a process you haven’t named. The naming is the measurement. Once it’s named, you can move it off your plate. That’s the pivot.

Coaching makes the human layer legible. AI makes the operational layer legible. The leaders who thrive over the next three years will run the loop relentlessly across both.

What I’d bet on

Don’t optimize harder this quarter. Measure what’s actually working. Then pivot.

Every other Friday I’ll write about one face of this. Hiring. Coaching. The agents we’re building into how an executive search firm actually runs. Three angles on the same practice.

One ask. Reply with a line: what’s one thing in your work right now that you suspect isn’t yielding what it used to, but you haven’t measured to be sure?

I read every reply.

Jeremy