Chapter 28: Attitude Over Aptitude

By month seven Maya had read so many résumés that she'd started rating them on a spreadsheet she would never act on.

The VA had bought back her inbox and her calendar, and it had worked. The problem was that buying back two hours a day only revealed how many hours the actual work ate. Delivery was the bottleneck now. The audits, the rewrites, the second drafts after a client pushed back, all of it still ran through Maya's own hands at midnight. She needed a person to do delivery. She had decided that weeks ago. And instead of hiring one, she had built a column in a spreadsheet called "vibe."

There were forty-one rows in the spreadsheet. She had posted the role once, gotten thirty applicants, sourced eleven more from a Slack group, and then stopped sourcing entirely so she could compare the fifty-one she already had. She color-coded them. She made a weighted scoring rubric, adjusted the weights, rescored everyone, and noticed the ranking barely moved. She opened the same three portfolios for the fourth time. She told herself she was being rigorous. The role had been open for nineteen days, and in those nineteen days Maya had personally delivered every single client project, because the safest candidate is the one you never have to pick.

This is the avoidance, and it wears a lab coat. You do not refuse to hire. You screen. You compare. You build the rubric, because comparing is the part with no risk in it. A bad hire could botch a client deliverable with her name on the cover, and a résumé in a spreadsheet can never botch anything. So she stayed in the spreadsheet, and the spreadsheet stayed open, and the role stayed empty, and Maya stayed the bottleneck she'd promised herself she would stop being.

Marcus, when she mentioned she was "deep in hiring," told her he was holding off until he could afford "someone genuinely senior, a real operator." He had not launched. He was, as ever, about to.

She closed the spreadsheet and went back to the council.

They did not let her hide in the comparison for long. The first voice told her the comparison itself was the wrong activity, because she had skipped the step before it. Caleb Ralston:

First, before we hire anybody, let's define what we need. Define your needs before hiring. There's what you need and there's what you want, and we are only going to hire on the prior. A lot of people hire way too quickly and they hire for roles that they think they're going to need. What you want to do is look at your process and what is causing the biggest constraint.

Maya's job post had said "messaging delivery specialist, copywriting experience required." That was a vibe, not a job. She did the delivery herself every day, so she could describe it to the minute: take the discovery notes, draft the homepage in the audit template, run it through the wince test, send a Loom walkthrough, turn one round of edits in 48 hours. She wrote that down. The rubric had been an elaborate way to avoid writing the one paragraph that actually mattered.

Then the council went after the fantasy hiding under her perfectionism, the one Marcus was openly living. EntreLeadership again, blunt:

One of the things you don't want to do with any hire or any process or system is think that it is the magic sauce. There is no magic fairy dust out there that someone has kept secret from you. You are the sauce.

She had been screening for a savior. Some perfect copywriter who would absorb her whole craft in a week and make delivery disappear. No such person existed in a stack of fifty-one PDFs, and waiting for them to appear was just the spreadsheet by another name.

The most-repeated note in the corpus reframed what she was even screening for. She had been ranking portfolios, which is to say ranking skill. The council ranked something else first:

When hiring, look for people with the right attitude. Skills can be taught. Attitude change requires a brain transplant.

Maya looked at her top three. The strongest portfolio belonged to someone whose two emails had both arrived late and slightly annoyed. The cleanest, fastest, most curious replies had come from a candidate whose samples were merely good. She had been about to pick the polish and inherit the attitude. Daymond John told her to stop expecting the spreadsheet to hand her a sure thing at all:

You're going to kiss a shitload of frogs. I do that constantly, 100%. And if you're lucky, you're going to find one person a year that will move up the ladder.

One keeper a year. The number was almost a relief. It meant the goal was never to identify the perfect hire from the page. It was to keep sourcing, keep testing, and accept that most would not work. Certainty was not on the menu. It never had been.

Three forks, and she had to settle all three by where she actually stood.

The first was the one Marcus had picked up and run with: hire a leader, not a helper. Codie Sanchez makes the case hard.

Your first hire shouldn't be an assistant, it should be a CEO, CSO, or a chief of staff. My first hire is always my CEO, who comes with a strategy for overall management. You need mental leverage, not simply operational leverage.

It is real advice for the right phase. The other camp, Dan Martell, framed the hire as time, not org chart:

We don't hire people to grow our business. We hire people to buy back our time, because if we do the second, we get the first.

The deciding variable was who was the bottleneck. Maya's bottleneck was not strategy. She knew exactly what to do and had no hands to do it with. She was still the operator, drowning in delivery she could describe step by step. A chief of staff would sit there with nothing to manage while Maya wrote homepages at midnight. She needed delivery hours back. The leader hire was a real move for a person she was not yet. She filed it where she'd filed acquisition and AI sponsorships: later.

The second fork was speed of judgment. One camp says true performers reveal themselves in days. The other says a hire is a big decision worth a week or two and a real proving period. The deciding variable was reversibility. A delivery role with measurable output and a defined trial was about as reversible as a hire gets, so she did not need a month of agonizing. She needed a test that would settle it in weeks.

Which led to the move that broke the spreadsheet's grip. The council's de-risking mechanism was not a better interview. It was paid real work, and more than one candidate at a time:

I'll typically hire in twos. I'll bring two people, and yes, for a few months I'm paying the salary, but 60, 90 days later I'm keeping the person that I'm more impressed with and the other person I send off. Five things I can't learn from them until I hire them.

This was the toll, and Maya felt it land. Not "wait until you are sure." Pay two people real money to do real client-adjacent work, accept that one of them was a sunk cost from the start, and choose based on what they did instead of what they claimed. It cost more upfront than picking one. It cost less than a botched client and a role open another two months. She picked her top two on attitude: the fast-curious one, and a second whose samples were strong and whose replies were warm. She wrote a scoped, paid trial that mirrored the job exactly: one real audit on a friendly client's homepage, the same template, the same 48-hour edit turn, four hundred dollars each, two weeks.

Before she sent it, she did the thing the council said most failed hires die without. Valuetainment:

Communicate expectations clearly. One of the biggest challenges why an employee didn't work out with me over the years is because the expectations weren't communicated clearly. Grab a sheet of paper: these are my no way in the world I'm willing to negotiate, these are the things I really like, these six things I'm okay with. Make sure everybody knows.

She wrote one page. Non-negotiable: reply within a day, hit the 48-hour edit turn, flag what you do not know. Preferred: a point of view on the copy, not just execution. Flexible: hours, tools, where they worked. She sent it to both. Then she sat in the discomfort of having committed real money to people she was not certain about, which was the entire point.

The trial said in two weeks what nineteen days of screening had not. Candidate A, the strong portfolio, turned in clean work a day late, went quiet when a question came up, and waited to be told. Candidate B asked two sharp questions on day one, hit the edit turn early, and flagged a line she was unsure about instead of hiding it. The samples had ranked them the other way around. The work ranked them honestly. Maya kept B and paid A for the trial with a clear, kind no. One keeper, one pass, exactly the arithmetic Daymond John had quoted.

For the first time, a homepage went out that Maya had not written.

She had a teammate now. A real one, beyond the VA, someone delivering the actual craft. And within a week she discovered the wall behind the hire. Two people plus her, three sets of hands, and no shared rhythm at all. B finished a draft and waited, not knowing it was urgent. The VA flagged a client reply that sat for a day because nobody owned it. Maya answered everything at all hours because she was the only one who knew the whole board. The work was getting done, and it was starting to slip through the gaps between the people doing it.

My verdict. Endless screening is procrastination in a rubric. You tell yourself you're being careful, and what you're actually doing is refusing to choose, because an unchosen candidate can never disappoint you and an empty role keeps the risk theoretical. There is no résumé in the stack that will make you certain, and the keeper you're hunting will not show up on paper anyway. Stop trying to predict who's good. Pay them a little to do the real work for a short window, watch what they actually do, and keep the one whose attitude shows up when nobody's grading. The four-word version: hire attitude, train skill. You already know you can teach the craft. You can't teach someone to care. Test for the thing you can't fix, and let a small paid trial tell you the truth your spreadsheet never will.