“For some of the costs people carried, yes. There are things I wouldn’t choose to put them through again.”
“And for you?”
I looked across the room at Brian speaking with the manufacturing partner on a video call, at Janet checking a figure before the final release, at people doing useful work without pretending everything was effortless.
“I wouldn’t choose to go back to the arrangement I had before.”
Scott nodded.
“That’s a fair answer.”
Success changed the conversations around me. People who had once described the ownership clause as excessive began calling it visionary. Executives who questioned whether clothing belonged anywhere near Hammond’s business now wanted to participate in product reviews.
I tried not to become distracted by the change in tone.
One afternoon, a director suggested we accelerate expansion by reducing the customer testing period.
“The brand has momentum,” he said. “We should use it.”
“We should protect it,” Brian replied.
The director looked toward me, expecting the final word.
“Brian owns the product recommendation,” I said. “If he says the testing needs more time, it needs more time.”
That was a small decision, but people noticed. Responsibility meant little if the person doing the work could be overruled whenever patience became inconvenient.
I was learning to build the kind of organization I had wanted to work in, and that required more than making speeches about respect.
It also required paying attention when I made mistakes.
During a particularly busy week, I sent a late-night message asking the team for a revised presentation by morning. Maya, our customer-research lead, replied with a simple question.
“Is this needed for a decision tomorrow, or would tomorrow afternoon work?”
My first reaction was irritation. I had asked because I wanted it.
Then I read the message again.
There was no emergency. I was anxious about a meeting and passing that anxiety along as a deadline.
“Tomorrow afternoon works,” I wrote. “Thank you for checking.”
The next day, I told the team they should keep asking that question.
I had spent years confusing availability with commitment. A healthier business needed people capable of doing excellent work over time, not people proving loyalty through exhaustion.
Kevin noticed the change before I did.
“You actually stayed on the phone until we finished talking,” he said one Sunday.
“Was that unusual?”
“For you? Historically significant.”
I laughed.
We arranged a weekend in Denver, and this time I booked the flight before the conversation ended. I told my team when I would be unavailable and made sure they knew who could make decisions without me.
The company continued functioning.
It was a useful discovery.
Justin remained in research throughout those months. I occasionally saw him in the cafeteria or walking between departments. He usually greeted me briefly and kept moving.
I did not seek him out. I also did not ask anyone to make his work unpleasant.
His supervisors reported on his performance through normal channels. At first, he struggled with routine tasks that did not come with an audience. He submitted polished summaries that missed basic details. He was corrected, and the corrections remained in the work instead of being softened because of his mother.
Eventually, the reports changed. His analysis became more careful. He began asking questions before presenting conclusions.
That was encouraging, but it did not erase what had happened.
Patricia asked me once whether I thought he had learned enough.
“Enough for what?”
“Another opportunity.”
“That depends on the opportunity and the evidence. Being related to you can’t be the reason. Feeling sorry for him can’t be the reason either.”
She looked disappointed, then nodded.
“I understand.”
I hoped she did.
Meanwhile, the messages arriving at Executive Edge began changing. Customers still asked about fabric, fit, and deliveries, but they also wrote about their workplaces.
Some described being judged for an accent, an age, a background, or a way of presenting themselves that didn’t match a manager’s expectations. Others had made mistakes and wanted to rebuild their careers without being reduced forever to one bad decision.
We could not solve those problems by selling jackets.
But we could decide what to do with a portion of the success those customers had helped create.
I began discussing a foundation with advisers who had experience in grants, mentorship, and professional development. I wanted something practical, with clear selection criteria and people qualified to administer it.
The idea was to support professionals facing unfair treatment and those rebuilding after setbacks. Grants could help cover training or a transition period. Mentorship could provide the guidance and introductions that a person’s existing workplace had withheld.
I also wanted a separate fellowship path for people who had made serious professional mistakes and could demonstrate genuine accountability.
That provision created the longest discussion.
“People may think you’re creating a route for Justin,” one adviser said.
“Then the process has to be independent enough that I can’t create one.”
We agreed that candidates would be reviewed against published criteria. I would not select recipients whose history involved me directly. No applicant would receive priority because they were useful to the origin story.
The foundation had to be more than a generous ending to a business anecdote.