Values and Ethics in Business Decisions: Choose Growth Without Compromise

The first thing I do is separate two situations that feel identical in the moment: work that is wrong, and work that is merely uncomfortable. My test is whether the objection is to the outcome or to the method. If the outcome itself is the problem, there is nothing to redesign, and any attempt to redesign it is really a negotiation with myself. If the method is the problem, a redesign is usually available and usually better than walking, because the other party still gets what they legitimately needed.

The second test comes straight out of practicing in a regulated profession. Can I write down what I did and why, and would I be comfortable with a stranger reading that file years later with no goodwill toward me? In tax work you assume the file will eventually be read by somebody adversarial. That habit transfers cleanly to business decisions. If the reasoning has to stay verbal, it is not reasoning, it is a rationalization looking for company.

The third thing I have learned is that the gray zone is often not gray, it is unresearched. A surprising share of what presents as an ethical dilemma is a question nobody has actually looked up yet. Doing the work is the cheapest first move, and it frequently converts a values conflict into a factual answer that everyone can live with.

On keeping the relationship intact, two things matter more than the wording. Decline the position rather than the person, and do it early and in writing. Nearly all of the damage in these situations comes from timing rather than from the answer. A no on day two reads as professional judgment. The identical no in week six, after invoices and expectations have accumulated, reads as a betrayal even though nothing about the answer changed.

Then offer the version you can support. People rarely want the specific thing you refused, they want the result, and there is often a documented and defensible path to most of it. That is what an honest redesign looks like. When there is not one, say so plainly and without a lecture.

The clearest signal to walk away is when someone wants your signature more than your advice. Growth that depends on certifying something you do not believe is not growth. It is renting out your license, and the rent is never enough.

The test I use: does this opportunity require me to design incentives that are extractive by structure? If yes, I walk. If no, I redesign the approach or take it.

When we were raising capital, we had several term sheets from funds whose model is token exit timing. They wanted board seats, preferred returns tied to a token launch within 18 months, and terms that essentially meant “build fast, launch token, distribute to insiders, exit.” The capital was real. The valuations were attractive. The problem was structural. Taking that money would have required building for a token event rather than building for users who come back. Those two things optimize for different outcomes, and you cannot serve both at the same time.

We turned down every one of those term sheets and raised $2M from angels instead. The angel structure is conviction capital: long-term aligned, no token launch pressure, no preferred return timeline forcing an event. The door to a token stays open, but the product roadmap is not built around it. That distinction matters. You can build extraction into the architecture, or you can opt out. We opted out.

The question I now ask before every new opportunity: who does this incentive structure serve first? If the answer is “insiders who arrive early and exit during the event,” the opportunity conflicts with what we are trying to build. If the answer is “users who stick around because the product solves a real problem,” then it is worth redesigning the approach to make it work.

Exiting a gray zone while keeping relationships intact is simpler than most founders think. You explain the structural conflict clearly. You do not frame it as rejection. You frame it as misalignment. Most people understand misalignment. We told every fund that passed on us exactly why we were passing on them. None of those relationships broke. Some of those people are now individual angel investors in the round we did close.

The integrity part is easy if the conflict is structural. If you are saying no because of incentive design rather than ego, the explanation lands. The hard part is recognizing the conflict early enough to walk before you have spent six months negotiating terms that were never going to work.

A few years ago I had a partnership on the table that would have doubled my revenue within a quarter. The other party wanted to bundle my audience into a promotional funnel that felt manipulative, targeting people who trusted me with pressure tactics I would use on no one. I liked the people involved. The math was compelling.

So I ran a test I still use today. I wrote out exactly what my customers would experience if I said yes, step by step, from the first email to the final upsell. Then I asked myself whether I would be comfortable if my closest friend went through that sequence without knowing I was behind it. When the answer was no, I decided the structure had to change before I agreed to anything.

I brought the specifics back to my potential partners and proposed removing two of the higher-pressure touchpoints. They declined, and we parted on good terms because I had shown them my reasoning with the actual customer journey laid out rather than a vague objection. Mapping the literal customer experience and pressure-testing it against someone I care about kept me out of that gray zone, and it made the conversation with the other party productive because we were negotiating around concrete steps.

Nearly two decades at large agencies before co-founding Blennd taught me one thing: the gray zone almost always shows up in the brief, not the contract. A client wants growth, but the approach they’re pushing requires us to optimize for metrics that don’t connect to real business outcomes.

My test is simple: can I honestly trace this decision to a result the client will still feel good about six months after launch? When we’ve worked on paid search strategies, the temptation is sometimes to optimize for platform-reported conversions rather than actual pipeline. We’ve had to have blunt conversations where we tell a client their CPA looks great on a dashboard but their sales team can’t close any of it. That’s not growth, that’s noise.

When the approach feels off, I try to redesign before I exit. I’ll lay out what the goal actually is, what I won’t build toward, and what a version that works for both of us looks like. Most clients respect that more than they’d respect someone who just quietly delivers what was asked.

The conversation that unlocks gray zones fastest is: “Here’s what success actually looks like for your business, and here’s where this plan stops serving that.” If someone still wants to chase the wrong metric after that conversation, walking away is usually cleaner for the relationship than delivering something you both know was wrong from the start.

I walk away when the opportunity requires us to hide the real cost of a decision from the person who will carry it later.

In software development, the gray zone usually appears in polite language: compress discovery, skip a security review, promise a fixed scope before the product is understood, or launch an AI feature before the team knows how the output will be checked. None of those requests sound unethical at first. They sound like ambition. I ask whether we would be comfortable showing the same plan, with the same risks, to the client’s CEO, project manager, legal team, and first user after launch.

If the answer is yes, we redesign the approach. We can reduce the first release, separate discovery from implementation, move the riskiest integration to week one, or define the conditions that stop the project before more money is spent. That keeps the growth opportunity alive without pretending uncertainty has disappeared. We’ve had conversations where the client wanted a faster path, and the better answer was a smaller product with fewer commitments. That can feel less impressive in the sales call, but it protects the relationship because everyone knows what is being traded.

If the answer is no, we decline. For me, the line is crossed when the only way to win the work is to make a promise our delivery team would have to apologize for later. A founder can rationalize that for one quarter, especially when the deal looks valuable. The damage usually shows up months later as scope conflict, team burnout, or a client who feels misled.

The conversation that helps most is a pre-mortem before signing: “Imagine this project failed and the client still paid us. What would they fairly say we knew at the start and didn’t say clearly enough?” That question removes the drama. It turns values into specific risks, owners, and decisions.

Redesign first, because many value conflicts are badly shaped deals. Walk away when transparency itself would kill the sale. At that point, I’d rather lose the deal than hand the delivery team a promise we already know is unstable.

The greatest threats to your integrity rarely arrive looking like bad decisions. They arrive looking like great opportunities.

Growth opportunities often come disguised as compromises. The question isn’t whether an opportunity can accelerate your career or business. The real question is whether you’ll still recognize yourself after saying yes.

I’ve coached leaders who were offered roles with greater influence, compensation, and visibility. On paper, they looked like career-defining opportunities. Yet something didn’t feel right.

One executive I worked with was pursuing a senior leadership position that fit exactly with their experience. As we researched the organization, a different picture emerged. Public statements emphasized cooperation and creativity, yet employee feedback and turnover patterns suggested a culture where fear drove decisions and short-term results outweighed people.

Walking away seemed almost irresponsible.

Instead of evaluating the offer, we evaluated alignment.

Every significant leadership decision is ultimately an identity decision.

I asked three questions.

Will success in this role require me to turn into someone I don’t want to be?

Can I influence the culture more than the culture will influence me?

Five years from now, will I be proud of who I had to become to succeed here?

Those questions shifted the conversation from emotion to principle.

The executive realized they weren’t choosing a position. They were choosing the environment that might shape their leadership. They declined the opportunity respectfully, preserving the relationship. Months later, they accepted a different role where the culture aligned with their values, and they’ve since created a successful team.

That experience validated something I’ve seen repeatedly throughout my career. Integrity isn’t tested when the choice is obvious. It’s tested when the opportunity is attractive enough to tempt you to rationalize your values.

One decision test continues to guide both my coaching and my own leadership: If success requires compromising your character, the opportunity is simply too expensive.

Careers recover.

Titles change.

Businesses reinvent themselves.

Character is far more difficult to rebuild once you’ve convinced yourself that compromising it was “just this once.”

The best leaders I’ve known don’t protect every opportunity.

They protect the person they’re becoming while pursuing it.

Growth that costs me a standard doesn’t pay off later. Some bookings push past a turnover clean, into mold work or a hoarder-level mess. I turn those down. My test is simple: could my team handle this safely with the gear and training they have today. If not, the job gets redesigned or referred out, never stretched to fit. A missed booking costs one day of revenue. Taking a job outside scope can cost a cleaner’s safety, or a host’s trust. I keep the conversation direct. I name what’s out of scope and why, then offer exactly what is in scope. Most hosts respect a clear boundary more than a yes that quietly falls short. The relationship holds because I told the truth early instead of scrambling later. My rule after years of turnovers: if winning a job means shrinking your standard, it was never yours to take.

The test is whether I would be comfortable if the person paying me described exactly what they receive, in plain language, to a stranger.

If the honest description sounds like a scam even though the mechanics are legal, I walk. If it merely sounds unusual, I redesign the approach until the plain language version holds up.

The redesign path is almost always the same. Strip the offer down to what can be stood behind without qualifiers, quote that, and let the other side decide whether the honest version is still worth paying for. Most of the time it is. When it is not, that answer was worth having early.

The conversation that makes this survivable is naming the tradeoff out loud rather than quietly delivering less. Saying that a result cannot be promised, and explaining what can be promised instead, keeps the relationship intact even when the deal does not happen.

Gray zones rarely resolve by thinking harder. They resolve by saying the uncomfortable version out loud and seeing whether it still sounds acceptable.

My first instinct was to hand the deposit back and tell him to wait a year. I think that was the wrong call. Founders pay us for introductions to investors and the fundraising work around them, so our gray zone is a founder who wants to raise now when the numbers say wait. Refusing him is clean for me. It also leaves him exactly where he was. So we sold him 6 weeks of nothing going out. He paid roughly a third of the usual fee to get the numbers straight, with nothing sent to an investor in that window.

The test now is whether I would be relaxed if the investor on the other end read our notes on the account. It is not a clean test and you will argue with yourself. Next time I would put the honest version in writing before taking money.

Gray zone decisions become clearer when examined through quality control rather than revenue potential. An opportunity may look promising at the top line, but if it introduces inconsistency in review standards, partner communication, or execution oversight, it creates a delayed loss that rarely appears in the initial discussion. In scaled agency environments, the biggest damage often comes from deals that teach teams to tolerate avoidable ambiguity.

A practical question has helped me repeatedly: what must become true for this to work without exceptions? That shifts the conversation from persuasion to design. If the answer requires unrealistic oversight, selective transparency, or unusually high trust without shared controls, the structure is wrong. We either rebuild the arrangement around measurable accountability or decline it respectfully. Relationships usually stay intact when the reasoning is specific, calm, and grounded in operational fairness.

My test is simple; I imagine the most respected competitor, who would do the same deal, and ask myself if I would call his or her move clever or corrupt. Sometimes the opportunity that is presented seems too good to be true, especially if you are a struggling company that needs the extra funds. The temptation might lead you to rationalize every step that leads to a five-figure deal, or even a half-million-dollar sale. This, however, is where the value of removing the logos comes in. If it would not work for them, it probably does not work for you.

But, turning down an offer is not the only option, and in cases where you have shown interest but are now hesitant, the alternative is a modified proposition. Declining leaves the door closed, but presenting a new option allows both parties to save face. If you find yourself unable to accept based on one term but willing to cooperate on all the rest, modify the initial offer and return within 48 hours. Chances are, most of your counterparts will accept the new conditions without hesitation, but those who do not will show you their true intentions, which is often quite useful information.

When we sense a gray zone, we bring the issue into a room with people who understand the stakes and can challenge our thinking. We ask one direct question. If this decision became the example others followed, would we be proud of the standard it sets? That question shifts our focus from personal convenience to the values we want everyone to follow.

The conversation works because it moves beyond profit and personal preference. It helps us think about the kind of culture we are building together. If the room becomes quiet for the wrong reasons, we pay close attention because it often shows discomfort before anyone says it out loud. Once the standard is clear, the decision becomes easier and the relationship stays respectful.

My approach is to test whether the opportunity asks the business to become louder or become clearer. Loud growth can disguise weak fit for a while, especially in digital channels where attention is easy to buy but harder to hold. Clear growth usually feels less dramatic, though it tends to build stronger loyalty and fewer regrets.

I use a simple room test: if the legal team, the brand team, and the customer support team all heard the plan together, would the same version survive? If not, something is being hidden inside the framing. That is usually the moment to pause and redesign. Integrity stays intact when alignment exists across the parts of the business that absorb the consequences later.

In my book “Transformative Negotiation: Strategies for Everyday Change and Equitable Futures,” I offer a win-win-win framework for dealing with such conundrums. Drawing on justice scholar John Rawls’ work, you think about all those being affected by your decision (value compromise). If you woke up tomorrow as the person or group that gets the worst deal, would you still proceed? If not, then find a way to make it better for them.

We tend to think of these value compromises short term, such as what it will allow us to do or the money we can make this year, rather than as part of the legacy we’re leaving behind. Values are also choices. You can explore what the value is trying to achieve at its core and whether there’s another way to do that. Or, you can also use a future exercise technique where you ask yourself how an older you in 10 years might look back on this decision or how your grandchildren might interpret your decision. This helps us get perspective.

Or you can hear the words of my brilliant high school history teacher who once told me during my own conundrum, “Whenever you make a [moral] compromise, it’s always easier to make the next one.” This means the value compromise might only lead to more compromises.

We often articulate the value conflict as if there is no other way, but most of the time there is. If we get more creative, slow down, and invite more people to the conversation, solutions can often be found. Then we sleep better knowing we’re striving to become better versions of ourselves. This effort improves relationships.

When opportunity conflicts with values, the first mistake is treating it as binary. Many situations improve once the structure changes, even when the headline offer does not. The decision test asks whether the current path rewards behavior that should never scale. If the answer is yes, redesign before deciding whether to proceed.

I like one conversation because it turns tension into something measurable and calm. Ask which part of the deal feels hardest to explain to a trusted customer. That usually surfaces the exact issue hiding inside enthusiasm, urgency, or optimism. From there, adjust terms, expectations, or accountability until the discomfort disappears. If that cannot happen honestly, walking away protects reputation and leaves the relationship respectful.

In aviation, there’s a concept called CRM — Crew Resource Management. It was developed after a series of disasters in the 1970s where planes weren’t going down because of technical failures, but because co-pilots weren’t contradicting their captains. The problem wasn’t competence. It was a hierarchy that silenced the right information at the wrong moment.

The lesson the industry drew wasn’t “communicate more.” It was subtler and more radical: a well-designed system must make it structurally impossible to ignore a critical signal, regardless of who sends it.

That’s what brings me to your question.

When an opportunity conflicts with your values, the conventional response is to treat it as an ethical dilemma — stay or leave, redesign or walk away. But that’s the wrong question, because it assumes you’re capable of evaluating the conflict in the moment you’re living it.

You’re not. Nobody is.

The tension between opportunity and values triggers exactly the same dynamic as that 1970s cockpit: external pressure — the opportunity, the gain, the recognition — takes the captain’s chair. Your values play co-pilot. And co-pilots, under pressure, fall silent.

What I learned — first in aeronautical management, then through developing The 4S Method of Adaptive Intelligence™, then through years of making decisions with reduced energy and resources — is that the right question isn’t what do I do with this conflict, but have I built a system that lets me see it before it becomes an emergency?

Values aren’t a filter you apply at the moment of decision. They’re an architecture you build when you’re not under pressure, precisely because when you are, you can’t trust your real-time judgment.

People without that architecture don’t walk away or redesign. They improvise. And improvisation under pressure tends to reward the opportunity and sacrifice the values — not because the person is dishonest, but because the system wasn’t built to hold.

We decide between walking away and changing our approach by knowing what should stay the same and what can change. Our values stay the same while our methods can change. If an opportunity asks us to give up our values we walk away. If the challenge is about timing, language, or expectations we adjust our approach instead.

That mindset helps us see the difference between a hard choice and a real values issue. We begin the conversation by saying we want the relationship and the outcome to succeed without giving up the standards that guide us. We invite the other person to help find a better way that keeps trust and progress strong. People usually respond better when they feel respected because trust grows when honesty comes first.

Rather than just assuming a client or contact would be mad if I turn down an opportunity, I ask them what they would think. People are often much more understanding than you assume they will be, and you don’t have to assume the worst and then end up compromising your values on something that may not even be important to them.

I was concerned about losing a client because I didn’t want to turn them down, so I actually asked them, “How would you feel if I told you it wasn’t a good fit for me?” They realised that I was being honest and respected it more than if I had done it because I didn’t want to. That talk actually helped the relationship, because they saw that I had standards, and I was honest about them. Many times the relationship conflict is only in your mind until you discuss it.

Sometimes, the decision to walk away or redesign is less about right versus wrong and more about aligning with your core values. I’ve found that clarity comes when I take a moment to pause and assess whether the current path is truly serving the vision or if it’s veering off course. The emotional tug of wanting to salvage what’s in motion can be strong, but it’s critical to recognize when persistence becomes counterproductive.

A crucial test I rely on involves asking myself two questions: “What outcomes am I realistically expecting?” and “At what cost am I pursuing these outcomes?” If the answers reveal unsustainable compromise or misalignment with the bigger picture, it’s time to pivot. Honest conversations with trusted colleagues are also a game-changer; they provide fresh perspectives that can illuminate blind spots.

Integrity remains non-negotiable in these decisions. Maintaining it requires self-awareness to differentiate between fear of failure and a genuine need for change. Relationships are equally vital, so I prioritize transparency and empathy when communicating decisions. Staying grounded in values ensures that whether walking away or redesigning, the decision feels right both professionally and personally.

If a client wants to skip compliance to chase growth, I show them how proper GST and payroll handling actually works in their favor. We had a startup try to cut corners once, but I set the boundaries immediately. After we fixed the books, the compliance issues disappeared and the right clients stuck around. Now I just document the rules upfront so everyone knows the deal.

Med spa owners often get pitched campaigns that look great on paper but ignore patient safety. I just go with my gut. I actually passed on a profitable project recently because it felt risky for patients. If you’re in that spot, speak up. See if you can change the plan. If not, let it go. Protecting your reputation matters more than one paycheck.

The key here is really our business model. We’re built around a distributed, lightweight team, a core software service, and a target market of small, local businesses. Any opportunity that lets us work within that framework is one that I’m going to take. If an opportunity lies outside of that, I’m much more likely to refer it to a networking contact or consider spinning up a whole new business to meet the need.

If a new feature risks privacy, I stop. Even if it helps us grow, I pull the team into a room to find another way that doesn’t mess with user data. We move slower than the startups chasing the next big thing, but that’s fine. People trust us because we don’t cut corners, and keeping that trust is worth the extra time.